Patent Application
20250113227
The disclosure relates to wireless networks, and more particularly, to methods and a wireless network for managing a gateway function operation.
A control and user plane separation (CUPS) architecture may be adopted in a fourth generation (4G) core network and/or a fifth generation (5G) core network. Alternatively or additionally, the CUPS architecture may be adopted in a gNodeB (gNB) in the 5G core network between a gNB central unit control plane (gNB-CU-CP) and a gNB central unit user plane (gNB-CU-UP). However, the CUPS architecture may not be adopted in a Trusted Non-3rd Generation Partnership Project (Non-3GPP) Gateway Function (TNGF). For example, according to a 3GPP standard, the TNGF may be monolithic. In other words, the TNGF may have a role that may be similar to the role of the gNB in a 5G network. The TNGF and the gNB may have a N2 interface towards an access and mobility management function (AMF) entity and a N3 interface towards a user plane function (UPF). The gNB may be split into the gNB-CU-CP and the gNB-CU-UP. A 3GPP E1 interface may be used between the gNB-CU-CP and the gNB-CU-UP. However, the TNGF may be a single network element. It may be desirable to have the CUPS architecture on the TNGF. Thus, there is a need for a new 3GPP interface (e.g., E11) between a TNGF control plane (TNGF-C) entity and a TNGF user plane (TNGF-U) entity.
Similarly, the CUPS architecture may be adopted in the 4G core network and/the 5G core network. The CUPS architecture may be adopted in the gNB in the 5G core network between the gNB-CU-CP and the gNB-CU-UP. However, the CUPS architecture may not be adopted in a wireline access gateway function (W-AGF). For example, according to a 3GPP standard, the W-AGF may be monolithic. In other words, the W-AGF may have a role that may be similar to the role of the gNB in the 5G network. The W-AGF and the gNB may have a N2 interface towards the AMF entity and a N3 interface towards the UPF entity. The gNB may be split into the gNB-CU-CP and the gNB-CU-UP. A 3GPP E1 interface may be used between the gNB-CU-CP and the gNB-CU-UP. However, the W-AGF may be single network element. It may be desirable to have the CUPS architecture on the W-AGF. Thus, there is a need for a new 3GPP interface (E12) between a W-AGF control plane (W-AGF-C) entity and a W-AGF user plane (W-AGF-U) entity.
There exists a need for further improvements in gateway function operation technology, as the need for interfaces between control plane and user plane entities may be constrained by a lack of adoption of a CUPS architecture. Improvements are presented herein. These improvements may also be applicable to other wireless communication technologies and the telecommunication standards that employ these technologies.
Example embodiments of the present disclosure provide methods and a wireless network for managing a gateway function operation (e.g., trusted non-3GPP gateway function (TNGF) operation, and wireline access gateway function (W-AGF) operation) in the wireless network.
Further, one or more example embodiments of the present disclosure provide control and user plane separation (CUPS) on a TNGF by splitting the TNGF into a TNGF-C entity and a TNGF-U entity.
Further, one or more example embodiments of the present disclosure provide CUPS on a W-AGF by splitting the W-AGF into a W-AGF-C entity and a W-AGF-U entity.
According to an aspect of the disclosure, a method for managing an operation of a wireline access gateway function (W-AGF) in a wireless network is disclosed. The method may comprise transmitting, by a W-AGF control plane (W-AGF-C) entity of the W-AGF to a W-AGF user plane (W-AGF-U) entity of the W-AGF, a performance statistics request message for at least one object. The method may comprise receiving, by the W-AGF-C entity from the W-AGF-U entity, a performance statics response message in response to the performance statistics request message.
According to an aspect of the disclosure, an apparatus for wireline access gateway function (W-AGF) in a wireless network is disclosed. The apparatus may comprise a memory storing instructions; and at least one processor configured to, when executing the instructions, may cause the apparatus to perform operations. The operations may comprise transmitting, by a W-AGF control plane (W-AGF-C) entity of the W-AGF to a W-AGF user plane (W-AGF-U) entity of the W-AGF, a performance statistics request message for at least one object. The operations may comprise receiving, by the W-AGF-C entity from the W-AGF-U entity, a performance statics response message in response to the performance statistics request message.
According to an aspect of the disclosure, a non-transitory computer readable storage medium storing instructions is disclosed. The instructions, when executed by at least one processor of an apparatus for a wireline access gateway function (W-AGF) in a wireless network, may cause the apparatus to perform operations. The operations may comprise transmitting, by a W-AGF control plane (W-AGF-C) entity of the W-AGF to a W-AGF user plane (W-AGF-U) entity of the W-AGF, a performance statistics request message for at least one object. The operations may comprise receiving, by the W-AGF-C entity from the W-AGF-U entity, a performance statics response message in response to the performance statistics request message.
According to an aspect of the disclosure, a method for managing a trusted non-3rd Generation Partnership Project (Non-3GPP) gateway function (TNGF) operation in a wireless network includes splitting a TNGF function as a TNGF control plane (TNGF-C) entity and a TNGF user plane (TNGF-U) entity, performing control plane signalling by the TNGF-C entity, and performing user plane signalling by the TNGF-U entity.
According to an aspect of the disclosure, a TNGF-C entity includes a processor, a memory, and an interface controller, coupled with the processor and the memory, configured to perform control plane signalling of the TNGF-C entity, add an E11 interface between the TNGF-C entity and at least one TNGF-U entity, and monitor at least one of an operation associated with the E11 interface and a service associated with the E11 interface.
According to an aspect of the disclosure, a TNGF-U entity includes a processor, a memory, and an interface controller, coupled with the processor and the memory, configured to perform user plane signalling of the TNGF-U entity, add an E11 interface between a TNGF-C entity and the TNGF-U entity, and monitor at least one of an operation associated with the E11 interface and a service associated with the E11 interface.
According to an aspect of the disclosure, a method for managing a wireline access gateway function (W-AGF) operation in a wireless network includes splitting a W-AGF function as a W-AGF control plane (W-AGF-C) entity and a W-AGF user plane (W-AGF-U) entity, performing control plane signalling by the W-AGF-C entity, and performing user plane signalling by the W-AGF-U entity.
According to an aspect of the disclosure, a W-AGF-C entity includes a processor, a memory, and an interface controller, coupled with the processor and the memory, configured to perform control plane signalling of the W-AGF-C entity, add an E12 interface between the W-AGF-C entity and at least one W-AGF-U entity, and monitor at least one of an operation associated with the E12 interface and a service associated with the E12 interface.
According to an aspect of the disclosure, a W-AGF-U entity includes a processor, a memory, and an interface controller, coupled with the processor and the memory, configured to performing user plane signalling of the W-AGF-U entity, add an E12 interface between a W-AGF-C entity and the W-AGF-U entity, and monitor at least one of an operation associated with the E12 interface and a service associated with the E12 interface.
The above and other aspects of the example embodiments described herein may be apparent when considered in conjunction with the following description and the accompanying drawings. It is to be understood, however, that the following descriptions, while indicating example embodiments and numerous specific details thereof, may be given by way of illustration and not of limitation. Many changes and modifications may be made within the scope of the example embodiments herein without departing from the scope thereof, and the example embodiments herein may include such modifications.
The above and other aspects, features, and advantages of certain embodiments of the present disclosure may be more apparent from the following description taken in conjunction with the accompanying drawings, in which:
The example embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques may be omitted so as to not unnecessarily obscure the embodiments herein. The description herein is intended merely to facilitate an understanding of ways in which the example embodiments herein may be practiced and to further enable those of skill in the art to practice the example embodiments herein. Accordingly, the present disclosure may not be construed as limiting the scope of the example embodiments herein.
For the purposes of interpreting the present disclosure, the descriptions (as used herein) may apply and whenever appropriate the terms used in singular may also include the plural and vice versa. It is to be understood that the terminology used herein is for the purposes of describing particular embodiments only and is not intended to be limiting. The terms “comprising”, “having” and “including” are to be construed as open-ended terms unless otherwise noted.
The words/phrases “exemplary”, “example”, “illustration”, “in an instance”, “and the like”, “and so on”, “etc.”, “etcetera”, “e.g.,”, “i.e.,” are merely used herein to mean “serving as an example, instance, or illustration.” Any embodiment or implementation of the present subject matter described herein using the words/phrases “exemplary”, “example”, “illustration”, “in an instance”, “and the like”, “and so on”, “etc.”, “etcetera”, “e.g.,”, “i.e.”, is not necessarily to be construed as preferred or advantageous over other embodiments.
Embodiments herein may be described and illustrated in terms of blocks which carry out a described function or functions. These blocks, which may be referred to herein as managers, units, modules, hardware components or the like, are physically implemented by analog and/or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits and the like, and may optionally be driven by a firmware. The circuits may, for example, be embodied in one or more semiconductor chips, or on substrate supports such as printed circuit boards and the like. The circuits constituting a block may be implemented by dedicated hardware, or by a processor (e.g., one or more programmed microprocessors and associated circuitry), or by a combination of dedicated hardware to perform some functions of the block and a processor to perform other functions of the block. Each block of the embodiments may be physically separated into two or more interacting and discrete blocks without departing from the scope of the disclosure. Likewise, the blocks of the embodiments may be physically combined into more complex blocks without departing from the scope of the disclosure.
In the present disclosure, the articles “a” and “an” are intended to include one or more items, and may be used interchangeably with “one or more.” Where only one item is intended, the term “one” or similar language is used. For example, the term “a processor” may refer to either a single processor or multiple processors. When a processor is described as carrying out an operation and the processor is referred to perform an additional operation, the multiple operations may be executed by either a single processor or any one or a combination of multiple processors.
It may be noted that elements in the drawings are illustrated for the purposes of this description and for ease of understanding and may not have necessarily been drawn to scale. For example, the flowcharts/sequence diagrams illustrate the method in terms of the steps required for understanding of aspects of the embodiments as disclosed herein. Furthermore, in terms of the construction of the device, one or more components of the device may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the present embodiments so as not to obscure the drawings with details that may be readily apparent to those of ordinary skill in the art having the benefit of the description herein. Furthermore, in terms of the system, one or more components/modules which comprise the system may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the present embodiments so as not to obscure the drawings with details that may be readily apparent to those of ordinary skill in the art having the benefit of the description herein.
It is to be understood that the specific order or hierarchy of blocks in the processes/flowcharts disclosed are an illustration of exemplary approaches. Based upon design preferences, it is understood that the specific order or hierarchy of blocks in the processes/flowcharts may be rearranged. Further, some blocks may be combined or omitted. The accompanying claims present elements of the various blocks in a sample order, and are not meant to be limited to the specific order or hierarchy presented.
The accompanying drawings are used to help easily understand various technical features and it is to be understood that the embodiments presented herein are not limited by the accompanying drawings. As such, the present disclosure may be construed to extend to any modifications, equivalents, and substitutes in addition to those which are particularly set out in the accompanying drawings and the corresponding description. Usage of words such as first, second, third, and the like, to describe components/elements/steps is for the purposes of this description and may not be construed as sequential ordering/placement/occurrence unless specified otherwise.
The embodiments herein may provide methods for managing a Trusted Non-3rd Generation Partnership Project (Non-3GPP) Gateway Function (TNGF) operation in a wireless network. The method may include splitting a TNGF gateway function as a TNGF control plane (TNGF-C) entity and a TNGF user plane (TNGF-U) entity. Further, the method may include handling a control plane signalling by the TNGF-C entity and a user plane signalling by the TNGF-U entity.
Unlike related methods and systems, the proposed method may be used to introduce a control and user plane separation (CUPS) architecture on the TNGF by splitting the TNGF into the TNGF-C entity and the TNGF-U entity and by introducing an interface (e.g., E11 interface) between the TNGF-C entity and the TNGF-U entity.
The embodiments herein may provide methods for managing a wireline access gateway function (W-AGF) operation in a wireless network. The method includes configuring a W-AGF gateway function as a W-AGF control plane (W-AGF-C) entity and a W-AGF user plane (W-AGF-U) entity. Further, the method may include handling a control plane signalling by the W-AGF-C entity and a user plane signalling by the W-AGF-U entity.
Unlike related methods and systems, the proposed method may be used to introduce a CUPS architecture on the W-AGF by splitting the W-AGF into the W-AGF-C entity and the W-AGF-U entity and by introducing an interface (e.g., E12 interface) between the W-AGF-C entity and the W-AGF-U entity.
Referring now to the drawings, and more particularly to
The trusted WLAN access point (112), the TNGF-C entity (114), the TNGF-U entity (116) may operate in the TNAN (120). The TNGF-C entity (114) may communicate with the AMF (102) through a N1 interface and a N2 interface. The TNGF-C entity (114) may communicate with the TNGF-U entity (116) through an E11 interface, where the TNGF-U entity (116) may communicate with the trusted WLAN access point (112) through an YW-U interface. The trusted WLAN access point (112) may communicate with the TNGF-C entity (114) through an YW-C interface. The trusted WLAN access point (112) may also be referred to as a trusted non-3GPP access point (TNAP).
In an embodiment, the TNGF may be divided into the TNGF-C entity (114) and the TNGF-U entity (116). In such an embodiment, the control plane signalling of the TNGF may be handled by the TNGF-C entity (114) and the user plane signalling may be handled by the TNGF-U entity (116). The E11 interface may be established between the TNGF-C entity (114) and the TNGF-U entity (116). An N2 interface may be used between the AMF (102) and the TNGF-C entity (114). An N3 interface may be used between the UPF (108) and the TNGF-U entity (116). The control plane signalling from the UE (106) towards a core network may be handled via the TNGF-C entity (114). The user plane data from the UE (106) towards the data network (110) may be handled via the TNGF-U entity (116).
The TNGF-C entity (114) may select the at least one TNGF-U entity (116) during a protocol data unit (PDU) session establishment procedure based on at least one of a local selection procedure, a hardware capacity of TNGF-U entity (116), a throughput capacity of the TNGF-U entity (116), a performance statistics of the TNGF-U entity (116), peer user plane (UPF) feedback of the TNGF-U entity (116), Internet Protocol Security (IPSec) performance statistics of the TNGF-U entity (116), a peer IPSec (UE) feedback of TNGF-U entity (116). The local selection procedure may be a round-robin procedure and/or may be based on the resource status received from one or more TNGF-Us (116).
Further, the TNGF-C entity (114) may move a UE context from one TNGF-U to another TNGF-U during at least one failure scenario. The failure scenario may be and/or may include, for example, but not be limited to, a TNGF-U E11 setup failure, a TNGF-C E11 setup failure, a TNGF-U configuration update failure, a TNGF-C configuration update failure, a bearer context setup failure, a bearer context modification failure, and a resource status reporting initiation failure.
As shown in
Referring to Table 1, maxnoofIndividualE11ConnectionsToReset may refer to a maximum number of UE-associated logical E11-connections that may be allowed to be reset in one message. For example, the value of maxnoofIndividualE11ConnectionsToReset may be 65,536.
The reset acknowledge message may be sent by both the TNGF-C entity (114) and the TNGF-U entity (116) as a response to the reset message. Information in the reset acknowledge message is shown in the Table 2.
Referring to Table 2, maxnoofIndividualE11ConnectionsToReset may refer to a maximum number of UE-associated logical E11-connections that may be allowed to be reset in one message. For example, the value of maxnoofIndividualE11ConnectionsToReset may be 65,536.
The error indication message may be sent by both the TNGF-C entity (114) and the TNGF-U entity (116) and may be used to indicate that an error has been detected in the node. Information in the error indication message is shown in the Table 3.
The TNGF-U E11 setup request message may be sent by the TNGF-U entity (116) to transfer information for a transport network layer (TNL) association. Information in the TNGF-U E11 setup request message is shown in Table 4.
Referring to Table 4, the maxnoofSPLMNs may indicate the maximum number of supported public land mobile network (PLMN) identifications (IDs). For example, the value of maxnoofSPLMNs may be 12.
Continuing to refer to
Referring to
The TNGF-C E11 setup request message may be sent by the TNGF-C to transfer information for a TNL association. Information in the TNGF-C E11 setup request message is shown in Table 7.
The TNGF-C E11 setup response message may be sent by the TNGF-U entity (116) to transfer information for a TNL association. Information in the TNGF-C E11 setup response message is shown in Table 8.
Referring to Table 8, maxnoofSPLMNs may indicate the maximum number of supported PLMN IDs. For example, the value of maxnoofSPLMNs may be 12.
The TNGF-C E11 setup failure message may be sent by the TNGF-U entity (116) to indicate an E11 setup failure. Information in the TNGF-C E11 setup failure message is shown in Table 9.
The TNGF-U configuration update message may be sent by the TNGF-U to transfer updated information for the TNL association. Information of the TNGF-U configuration update message is shown in Table 10.
Referring to Table 10, maxnoofSPLMNs may indicate the maximum number of supported PLMN IDs, and maxnoofTNLAssociations may indicate the maximum number of TNL associations between the TNGF-U entity (116) and the TNGF-C entity (114). For example, the value of maxnoofSPLMNs may be 12. As another example, the value of maxnoofTNLAssociations may be 32.
The TNGF-U configuration update acknowledge message may be sent by the TNGF-C entity (114) to the TNGF-U entity (114) to acknowledge update of information for the TNL association. Information in the TNGF-U configuration update acknowledge message is shown in Table 11.
The TNGF-U configuration update failure message may be sent by the TNGF-C entity (114) to indicate TNGF-U configuration update failure. Information in the TNGF-U configuration update failure message is shown in Table 12.
The TNGF-C configuration update message may be sent by the TNGF-C entity (114) to transfer updated information for the TNL association. Information in the TNGF-C configuration update message is shown in Table 13.
Referring to Table 13, maxnoofTNLAssociations may indicate the maximum number of TNL associations between the TNGF-C entity (114) and the TNGF-U entity (116). For example, the value of the maxnoofTNLAssociations may be 32.
The TNGF-C configuration update acknowledge message may be sent by the TNGF-U entity (116) to the TNGF-C entity (114) to acknowledge update of information for the TNL association. Information in the TNGF-C configuration update acknowledge message is shown in Table 14.
The TNGF-C configuration update failure message may be sent by the TNGF-U entity (116) to indicate a TNGF-C configuration update failure. Information in the TNGF-C configuration update failure message is shown in Table 15.
The E11 release request message may be sent by both the TNGF-C entity (114) and the TNGF-U entity (116) and may be used to request the release of the E11 interface. Information in the E11 release request message is shown in Table 16.
The E11 release response message may be sent by both the TNGF-C entity (114) and the TNGF-U entity (116) as a response to an E11 RELEASE REQUEST message. Information in the E11 release response message is shown in Table 17.
The TNGF-U status indication message may be sent by the TNGF-U entity (116) to provide overload information to the TNGF-C entity (114). Information in the TNGF-U status indication message is shown in Table 18.
The resource status request message may be sent by a TNGF-C entity (114) to the TNGF-U entity (116) to initiate the requested measurement according to the parameters given in the resource status request message. Information in the resource status request message is shown in Tables 19 and 20.
The resource status response message may be sent by the TNGF-U entity (116) to indicate that the requested measurement may be successfully initiated for all the measurement objects included in the measurement. Information in the resource status response message is shown in Table 21.
The resource status failure message may be sent by the TNGF-U entity (116) to indicate that for any of the requested measurement objects the measurement may not be initiated. Information in the resource status failure message is shown in Tables 22 and 23.
The resource status update message may be sent by TNGF-U entity (116) to the TNGF-C entity (114) to report the results of the requested measurements. Information in the resource status update message is shown in Tables 24 and 25.
The bearer context setup request message may be sent by the TNGF-C entity (114) to request the TNGF-U entity (116) to setup a bearer context. Information in the bearer context setup request message is shown in Table 26.
The bearer context setup response message may be sent by the TNGF-U entity (116) to confirm the setup of the requested bearer context. Information in the bearer context setup response message is shown in Table 27.
The bearer context setup failure message may be sent by the TNGF-U entity (116) to indicate that the setup of the bearer context was unsuccessful (e.g., a failure occurred). Information in the bearer context setup failure message is shown in Table 28.
The bearer context modification request message may be sent by the TNGF-C entity (114) to request the TNGF-U entity (116) to modify a bearer context. Information in the bearer context modification request message is shown in Table 29 and Table 30.
Referring to Tables 29 and 30, the security parameter index (SPI) may refer to an identification tag added to the header while using IPsec for tunnelling the IP traffic. For example, the identification tag may help to discern between two traffic streams where different encryption rules and algorithms may be in use. In an embodiment, the SPI (e.g., as described in “Security Architecture for the Internet Protocol”, RFC 4301, December 2005) may be a required part of an IPsec Security Association (SA) because the SPI may be needed to enable the receiving system to select the SA under which a received packet may be processed.
The bearer context modification response message may be sent by the TNGF-C entity (114) to confirm the modification of the requested bearer context. Information in the bearer context modification response message is shown in Table 31.
Table 32 shows the PDU session resource failed list IE.
Table 33 shows the PDU session resource setup list IE.
Referring to Table 33, maxnoofPDUSessionResource may indicate a maximum number of PDU sessions for a UE and maxnoofSPIs may indicate the maximum number of SPIs for a UE. For example, the value of maxnoofPDUSessionResource may be 256. As another example, the value of maxnoofSPIs may be 64.
Table 34 shows the PDU session resource modified list IE.
Table 35 and Table 36 shows PDU session resource failed to modify list IE.
The bearer context modification failure message may be sent by the TNGF-U entity (116) to indicate that the modification of the bearer context was unsuccessful. Information in the bearer context modification failure message is shown in Table 37.
The bearer context modification required message may be sent by the TNGF-U entity (116) to inform the TNGF-C entity (114) that a modification of a bearer context may be required (e.g., due to local problems at the TNGF-U entity (116)). Information in the bearer context modification required message is shown in Tables 38 and 39.
Table 40 shows the PDU session resource to modify list IE.
Table 41 shows the PDU session resource to remove list IE.
The bearer context modification confirm message may be sent by the TNGF-C entity (114) to confirm the modification of the requested bearer context. The Information in the bearer context modification confirm message is shown in Table 42.
The bearer context release command message may be sent by the TNGF-C entity (114) to command the TNGF-U entity (116) to release an UE-associated logical E11 connection. Information in the bearer context release command message is shown in Table 43.
The bearer context release complete message may be sent by the TNGF-U entity (116) to confirm the release of the UE-associated logical E11 connection. Information in the bearer context release complete message is shown in Table 44.
The heartbeat request message may be sent by the TNGF-C entity (114) or the TNGF-U entity (116) to determine if the peer entity is alive. Information in the heartbeat request message is shown in Table 52.
The heartbeat response message may be sent as a response to a received heartbeat request message by the TNGF-C entity (114) or TNGF-U entity (116). Information in the heartbeat response message is shown in Table 53.
The performance statistics request message may be sent by the TNGF-C entity (114) to the TNGF-U entity (116) to initiate the requested key performance indicators (KPIs) according to parameters given in the performance statistics request message. Information in the performance statistics request message is shown in Tables 54 and 55.
The performance statistics response message may be sent by the TNGF-U entity (116) to indicate that the requested performance statistics (e.g., KPIs), for all the performance statistics objects included in the performance statistics request message, may be successfully initiated. Information in the performance statistics response message is shown in Table 56.
The performance statistics failure message may be sent by the TNGF-U entity (116) to indicate that for any of the requested performance statistics objects the performance statistics may not be initiated. Information in the performance statistics failure message is shown in Tables 57 and 58.
The TNGF-C E11 setup failure message may indicate a total number of TNGF-C E11 setup messages received from the TNGF-C entity 116 and a total number of TNGF-C E11 setup failure messages sent to the TNGF-C entity 116. Information in the TNGF-C E11 setup failure message is shown in Table 60.
The TNGF-C configuration update failure KPI IE may indicate a total number of TNGF-C configuration update messages received from the TNGF-C entity (114) and a total number of TNGF-C configuration update failure messages sent to the TNGF-C entity (114). Information in the configuration update failure KPI IE is shown in Table 61.
The resource status failure KPI IE may indicate a total number of resource status messages received from the TNGF-C entity (114) and a total number of resource status failure messages sent to the TNGF-C entity (114). Information in the resource status failure KPI is shown in Table 62.
The bearer context setup failure KPI IE may indicate a total number of bearer context setup messages received from the TNGF-C entity (114) and a total number of bearer context setup failure messages sent to the TNGF-C entity (114). Information in the bearer context setup failure KPI is shown in Table 63.
The bearer context modification failure KPI IE may indicate a total number of bearer context modification messages received from the TNGF-C entity (114) and a total number of bearer context modification failure messages sent to the TNGF-C entity (114). Information in the bearer context modification failure KPI IE is shown in Table 64.
The performance statistics failure KPI IE may indicate a total number of performance statistics messages received from the TNGF-C entity (114) and a total number of performance statistics failure messages sent to the TNGF-C entity (114). Information in the performance statistics failure KPI IE is shown in Table 65.
The peer user plane feedback failure KPI IE may indicate a total number of peer user plane feedback messages received from the TNGF-C entity (114) and a total number of peer user plane feedback failure messages sent to the TNGF-C entity (114). Information in the peer user plane feedback failure KPI IE is shown in Table 66.
The peer user plane feedback request message may be sent by a TNGF-C entity (114) to the TNGF-U entity (116) to initiate the requested peer user plane feedback according to the parameters given in the peer user plane feedback request message. The UPF may be considered as a user plane peer of the TNGF-U entity (116). Information in the peer user plane feedback request message is shown in Table 67.
The peer user plane feedback response message may be sent by the TNGF-U entity (116) to indicate that the requested peer user plane feedback, for all the peer user plane feedback objects included in the peer user plane feedback, may be successfully initiated. Information in the peer user plane feedback response message is shown in Table 68.
The peer user plane feedback failure message may be sent by the TNGF-U entity (116) to indicate that, for any of the requested peer user plane feedback objects, the peer user plane feedback may not be initiated. Information in the peer user plane feedback failure message is shown in Table 69.
The peer user plane feedback update message may report the results of the requested peer user plane feedback. Information in the peer user plane feedback update message is shown in Tables 70 and 71.
The IPSec performance statistics request message may be sent by a TNGF-C to TNGF-U to initiate the requested IPSec KPIs according to the parameters given in the IPSec performance statistics request message. Information in the IPSec performance statistics request message is shown in Table 72.
The IPSec performance statistics response message may be sent by the TNGF-U entity (116) to indicate that the requested IPSec performance statistics (e.g., KPIs), for all the IPSec performance statistics objects included in the IPSec performance statistics request message, may be successfully initiated. Information in the IPSec performance statistics response message is shown in Table 73.
The IPSec performance statistics failure message may be sent by the TNGF-U entity (116) to indicate that, for any of the requested IPSec performance statistics objects, the IPSec performance statistics may not be initiated. Information in the IPSec performance statistics failure message is shown in Table 74.
The IKE SA establishment failure KPI IE may indicate a total number of IKE SA establishment (e.g. IKE_SA_INIT, IKE_AUTH) messages received from the UE (106) by TNGF-U entity (116) and a total number of IKE SA establishment failure messages sent to the UE (106) by TNGF-U entity (116). Information in the IKE SA establishment failure KPI IE is shown in Tables 76 and 77.
The IKEv2 SA deletion failure KPI IE may indicate a total number of TNGF-U/UE initiated IKEv2 SA deletion messages and a total number of TNGF-U/UE IKEv2 SA deletion failure messages. Information in the IKEv2 SA deletion failure KPI IE is shown in Table 78.
The IPSec SA Creation Failure KPI IE may indicate a total number of IPSec SA Creation messages sent to UE (106) by the TNGF-U entity (116) and a total number of IPSec SA Creation Failure messages received from the UE (106). Information in the IPSec SA Creation Failure KPI IE is shown in Table 79.
The IPSec SA Modification Failure KPI IE may indicate a total number of TNGF-U/UE initiated IPSec SA Modification messages and a total number of TNGF-U/UE IPSec SA Modification Failure messages. Information in the IPSec SA Modification Failure KPI IE is shown in Table 80.
The IPSec SA deletion failure KPI IE may indicate a total number of TNGF-U/UE initiated IPSec SA Deletion messages and a total number of TNGF-U/UE IPSec SA Deletion Failure messages. Information in the IPSec SA Deletion Failure KPI IE is shown in Table 81.
The liveness check failure KPI IE may indicate a total number of TNGF-U/UE initiated liveness check messages and a total number of TNGF-U/UE liveness check failure messages. Information in the liveness check failure KPI IE is shown in Table 82.
The IKE SA rekeying failure KPI IE may indicate a total number of TNGF-U/UE initiated IKE SA Rekeying messages and a total number of TNGF-U/UE IKE SA Rekeying Failure (TEMPORARY_FAILURE) messages. Information in the IKE SA Rekeying Failure KPI IE is shown in Table 83.
The IPSec SA rekeying failure KPI IE may indicate a total number of TNGF-U/UE initiated IPSec SA Rekeying messages and a total number of TNGF-U/UE IPSec SA Rekeying Failure messages. Information in the IPSec SA Rekeying Failure KPI IE is shown in Table 84.
The IPSec performance statistics failure KPI IE may indicate a total number of IPSec Performance Statistics messages received from the TNGF-C entity (114) and a total number of IPSec performance statistics failure messages sent to the TNGF-C entity (114). Information in the IPSec performance statistics failure KPI IE is shown in Table 85.
The peer IPSec feedback failure KPI IE may indicate a total number of Peer IPSec Feedback messages received from the TNGF-C entity (114) and a total number of Peer IPSec feedback failure messages sent to the TNGF-C entity (114). Information in the peer IPSec feedback failure KPI IE is shown in Table 86.
The peer IPSec feedback request message may be sent by the TNGF-C entity (114) to the TNGF-U entity (116) to initiate the requested peer IPSec feedback according to the parameters given in the peer IPSec feedback request message. The UE (106) may be considered as an IPSec peer of the TNGF-U entity (116). Information in the peer IPSec feedback request message is shown in Tables 87 and 88.
The peer IPSec feedback response message may be sent by the TNGF-U entity (116) to indicate that the requested peer IPSec feedback, for all the peer IPSec feedback objects included in the peer IPSec feedback may be successfully initiated. Information in the peer IPSec feedback response message is shown in Table 89
The peer IPSec feedback failure message may be sent by the TNGF-U entity (116) to indicate that, for any of the requested peer IPSec feedback objects, the peer IPSec feedback may not be initiated. Information in the peer IPSec feedback failure message is shown in Tables 90 and 91.
In an embodiment, the TNGF-C entity (114) includes a processor (114a), a communicator (114b), a memory (114c), and an interface controller (114d). The processor (114a) may be communicatively coupled with the communicator (114b), the memory (5114c), and the interface controller (114d).
The interface controller (114d) may split the functionality of the TNGF into the control plane functionality, where the control plane functionality may be handled by the TNGF-C entity (114). Further, the interface controller (114d) may add the interface between the TNGF-C entity (114) and the TNGF-U entity (116). Further, the interface controller (114d) may monitor at least one of the operations associated with the interface and the services associated with the interface.
The interface controller (114d) may be physically implemented by analog and/or digital circuits such as, but not limited to, logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits, or the like, and may optionally be driven by firmware. The interface controller (114d) may be a part of the processor (114a) or may be integrally referred to as at least one processor with the processor (114a).
Further, the processor (114a) may be configured to execute instructions stored in the memory (114c) and to perform various processes of the TNGF-C entity (114). The communicator (114b) may be configured for communicating internally between internal hardware components and with external devices via one or more networks. The memory (114c) may also store instructions to be executed by the processor (114a). The memory (114c) may include non-volatile storage elements. Examples of such non-volatile storage elements may include, but not be limited to, magnetic hard discs, optical discs, floppy discs, flash memories, and/or forms of electrically programmable memories (EPROM) and/or electrically erasable and programmable (EEPROM) memories. The memory (114a) may, in some examples, be considered a non-transitory storage medium. The term “non-transitory” may indicate that the storage medium may not be embodied in a carrier wave or a propagated signal. However, the term “non-transitory” may not be interpreted that the memory (114c) may be non-movable. In certain examples, a non-transitory storage medium may store data that may, over time, change (e.g., in random access memory (RAM) or cache).
In an embodiment, the TNGF-U entity (116) may include a processor (116a), a communicator (116b), a memory (116c), and an interface controller (116d). The processor (116a) may be communicatively coupled with the communicator (116b), the memory (116c), and the interface controller (116d).
The interface controller (116d) may split the functionality of the TNGF into the user plane functionality, where the user plane functionality may be handled by the TNGF-U entity (116). Further, the interface controller (116d) may add an interface between the TNGF-C entity (114) and the TNGF-U entity (116). Further, the interface controller (116d) may monitor at least one of the operations associated with the interface and the services associated with the interface.
The interface controller (116d) may be physically implemented by analog and/or digital circuits such as, but not limited to, logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits, or the like, and may optionally be driven by firmware. The interface controller (116d) may be a part of the processor (116a) or may be integrally referred to as at least one processor with the processor (116a).
The interface controller (e.g., 114d or 116d) may monitor an operation associated with the interface and a service associated with the interface. The operation may be, for example, but not be limited to, the user plane traffic procedure, the interface management procedure, the bearer management procedure, the trace start procedure, the deactivate trace procedure, and/or the load management procedure. The service may be, for example, but not be limited to, a UE-associated service and/or a non UE-associated service.
The interface management procedure may be, for example, but not be limited to, the reset procedure initiated from the TNGF-C entity (114), the reset procedure initiated from the at least one TNGF-U entity (116), the error indication procedure originated at the TNGF-C entity (114), the error indication procedure originated at the at least one TNGF-U entity (116), the TNGF-U E11 setup procedure, the TNGF-C E11 setup procedure, the TNGF-U configuration update procedure, the TNGF-C configuration update procedure, the E11 release procedure, and/or the TNGF-U status indication procedure.
The bearer management procedure may be, for example, but not be limited to, the bearer context setup procedure, the bearer context release request procedure initiated by the at least one TNGF-U entity (116), the bearer context release procedure initiated by the TNGF-C entity (114), the bearer context modification procedure initiated by the TNGF-C entity (114), the bearer context modification required procedure initiated by the at least one TNGF-U entity (116), the bearer context inactivity notification procedure, the data usage report procedure, the DL data notification procedure, and/or the UL data notification procedure. The load management procedure may be, for example, but not be limited to, a resource status reporting initiation procedure and/or a resource status reporting procedure.
Further, the processor (116a) may be configured to execute instructions stored in the memory (116c) and to perform various processes of the TNGF-U entity (116). The processor (114a), the processor (116a), the interface controller (114d) and the interface controller (116d) may be integrally referred to as at least one processor of the TNGF (120).
The communicator (116b) may be configured to communicate internally between internal hardware components and with external devices via one or more networks. The memory (116c) may also store instructions to be executed by the processor (116a). The memory (116c) may include non-volatile storage elements. Examples of such non-volatile storage elements may include, but not be limited to, magnetic hard discs, optical discs, floppy discs, flash memories, and/or forms of EPROM and/or EEPROM. The memory (116c) may, in some examples, be considered a non-transitory storage medium. The term “non-transitory” may indicate that the storage medium may not be embodied in a carrier wave or a propagated signal. However, the term “non-transitory” may not be interpreted that the memory (116c) may be non-movable. In some examples, a non-transitory storage medium may store data that may, over time, change (e.g., in (RAM or cache).
Although
At operation 5202, the method may include configuring (or splitting) the TNGF function as the TNGF-C entity (114) and the TNGF-U entity (116). At operation 5204, the method may include handling the control plane signalling by the TNGF-C entity (114) and the user plane signalling by the TNGF-U entity (116).
The method may be implemented in the CUPS on TNGF by splitting TNGF into the TNGF-C entity (114) and the TNGF-U entity (116) and by introducing the interface (e.g., E11 interface) between the TNGF-C entity (114) and the TNGF-U entity (116).
The 5G core network (5300) may include and/or may be similar in many respects to the wireless network (100) described above with reference to
In an embodiment, the 5G core network (5300) may include the AMF (102), the SMF (104), the UPF (108), the data network (110), a W-AGF-C entity (5302), a W-AGF-U entity (5304) and a wireline 5G access network (W-5GAN) function (5306), and 5G-RG (5308). The operations and functions of the AMF (102), the SMF (104), the UE (106), the UPF (108), the data network (110), and the 3GPP access network (118) may be in accordance with one or more telecommunication standards, such as, but not limited to, 3GPP TS 23.501 and 3GPP TS 23.502. For the sake of brevity, repeated descriptions of these components may be omitted.
The W-AGF-C entity (5302) and the W-AGF-U entity (5304) may be operated in the W-5GAN (5306). The W-AGF-C entity (5302) may communicate with the AMF (102) through a N1 interface and a N2 interface. The W-AGF-C entity (5302) may communicate with the W-AGF-U entity (5304) through an E12 interface.
In an embodiment, the W-AGF may be divided into the W-AGF-C entity (5302) and the W-AGF-U entity (5304). That is, the control plane signalling of the W-5GAN (5306) may be handled by the W-AGF-C entity (5302) and the user plane signalling of the W-5GAN (5306) may be handled by the W-AGF-U entity (5304). The E12 interface may be established between the W-AGF-C entity (5302) and the W-AGF-U entity (5304). An N2 interface may be used between the AMF (102) and the W-AGF-C entity (5302). An N3 interface may be used between the UPF (108) and the W-AGF-U entity (5304). The control plane signalling from the UE (106) towards a core network may be handled via the W-AGF-C entity (5302). The user plane data from the UE (106) towards the data network (110) may be handled via the W-AGF-U entity (5304).
The W-AGF-C entity (5302) may select the at least one W-AGF-U entity (5304) during the PDU session establishment procedure based on at least one of a local selection procedure, a hardware capacity of W-AGF-U entity (5304), a throughput capacity of the W-AGF-U entity (5304), a performance statistics of the W-AGF-U entity (5304), and a peer user plane (UPF) feedback of the W-AGF-U entity (5304). The local selection procedure may be and/or may include a round-robin procedure and/or may be based on the resource status received from one or more W-AGF-Us (5304).
The W-AGF-C (5302) may move the UE context from one W-AGF-U entity (5304) to another W-AGF-U entity (5304) during at least one failure scenario. The failure scenario may be, for example, but not limited to, a W-AGF-U E12 setup failure, a W-AGF-C E12 setup failure, a W-AGF-U configuration update failure, a W-AGF-C configuration update failure, a bearer context setup failure, a bearer context modification failure, and/or a resource status reporting initiation failure.
The W-AGF-C entity (5302) and the W-AGF-U entity (5304) may run (execute) on the E12 stack. The E12 interface may have an E12 application protocol (E12AP) that may run on top of a SCTP. In another embodiment, the E12 interface may have an E12AP that may run on other transport protocols such as, but not limited to, TCP, UDP, or the like. The E12AP may handle UE-associated services and/or non UE-associated services. The non UE-associated services may be described in standard 3GPP procedures. The E12AP may support interface management, bearer management, and/or other features, as needed.
The PDU session ID generated by the 5G-RG may communicate to the AMF (102) by the non-access-stratum (NAS) message which may be transparent to the W-AGF-C (5302). The W-AGF-C entity (5302) may assign a 5G wireless wireline convergence user plane encapsulation (5WE) session ID and may bind the 5WE session ID to the PDU session ID. The 5WE session ID and the PDU session ID binding may be communicated (e.g., transmitted) to the 5G-RG. In the proposed W-AGF CUPS architecture, the control plane protocols may be moved to the W-AGF-C entity (5302). For example, the W-AGF-C entity (5302) may provide support for protocols such as, but not limited to, NAS (FN-RG), NG application protocol (NGAP), general packet radio service (GPRS) tunnelling protocol user plane (GTPU), and the like, which may be existing protocols that may be supported by a standalone W-AGF.
As shown in
As shown in
In the proposed W-AGF CUPS architecture, the user plane protocols may be moved to the W-AGF-U entity (5304).
As shown in
Referring to Table 94, maxnoofIndividualE12ConnectionsToReset may refer to a maximum number of UE-associated logical E12-connections that may be allowed to be reset in one message. For example, the value of maxnoofIndividualE12ConnectionsToReset may be 65536.
The reset acknowledge message may be sent by both the W-AGF-C entity (5302) and the W-AGF-U entity (5304) as a response to the reset message. Information in the reset acknowledge message is shown in the Table 95.
Referring to Table 95, maxnoofIndividualE12ConnectionsToReset may indicate a maximum number of UE-associated logical E12-connections that may be allowed to be reset in one message. For example, the value of maxnoofIndividualE12ConnectionsToReset may be 65536.
The error indication message may be sent by both the W-AGF-C entity (5302) and the W-AGF-U entity (5304) and may be used to indicate that some error has been detected in the node. Information in the error indication message is shown in the Table 96.
The W-AGF-U E12 setup request message may be sent by the W-AGF-U entity (5304) to transfer information for a Transport Network Layer (TNL) association. Information in the W-AGF-U E12 setup request message is shown in Table 97.
Referring to Table 97, maxnoofSPLMNs may indicate the maximum number of supported PLMN IDs. For example, the value of maxnoofSPLMNs may be 12.
The W-AGF-U E12 setup response message may be sent by the W-AGF-C entity (5302) to transfer information for the TNL association. Information in the W-AGF-U E12 setup response message is shown in Table 98.
The W-AGF-U E12 setup failure message may be sent by the W-AGF-C entity (5302) to indicate an E12 setup failure. Information in the W-AGF-U E12 setup failure message is shown in Table 99.
The W-AGF-C E12 setup request message may be sent by the W-AGF-C to transfer information for a TNL association. Information in the W-AGF-C E12 setup request message is shown in Table 100.
The W-AGF-C E12 setup response message may be sent by the W-AGF-U entity (5304) to transfer information for a TNL association. Information in the W-AGF-C E12 setup response message is shown in Table 101.
Referring to Table 101, maxnoofSPLMNs may indicate the maximum number of supported PLMN IDs. For example, the value of maxnoofSPLMNs may be 12.
The W-AGF-C E12 setup failure message may be sent by the W-AGF-U entity (5304) to indicate an E12 setup failure. Information in the W-AGF-C E12 setup failure message is shown in Table 102.
The W-AGF-U configuration update message may be sent by the W-AGF-U to transfer updated information for the TNL association. Information of the W-AGF-U configuration update message is shown in Table 103.
Referring to Table 103, maxnoofSPLMNs may represent the maximum number of supported PLMN IDs, and maxnoofTNLAssociations may represent the maximum number of TNL associations between the W-AGF-U (5304) and the W-AGF-C (5302). For example, the value of maxnoofSPLMNs may be 12. As another example, the value of maxnoofTNLAssociations may be 32.
The W-AGF-U configuration update acknowledge message may be sent by the W-AGF-C entity (5302) to the W-AGF-U entity (5302) to acknowledge update of information for the TNL association. Information in the W-AGF-U configuration update acknowledge message is shown in Table 104.
The W-AGF-U configuration update failure message may be sent by the W-AGF-C entity (5302) to indicate W-AGF-U configuration update failure. Information in the W-AGF-U configuration update failure message is shown in Table 105.
The W-AGF-C configuration update message may be sent by the W-AGF-C entity (5302) to transfer updated information for the TNL association. Information in the W-AGF-C configuration update message is shown in Table 106.
Referring to Table 106, maxnoofNLAssociations may represent the maximum number of TNL Associations between the W-AGF-C entity (5302) and the W-AGF-U entity (5304). For example, the value for maxnoofTNLAssociations may be 32.
The W-AGF-C configuration update acknowledge message may be sent by the W-AGF-U entity (5304) to the W-AGF-C entity (5302) to acknowledge update of information for the TNL association. Information in the W-AGF-C configuration update acknowledge message is shown in Table 107.
The W-AGF-C configuration update failure message may be sent by the W-AGF-U entity (5304) to indicate W-AGF-C Configuration Update failure. Information in the W-AGF-C configuration update failure message is shown in Table 108.
The E12 release request message may be sent by both the W-AGF-C entity (5302) and the W-AGF-U entity (5304) and may be used to request the release of the E12 interface. Information in the E12 release request message is shown in Table 109.
The E12 release response message may be sent by both the W-AGF-C entity (5302) and the W-AGF-U entity (5304) as a response to an E12 RELEASE REQUEST message. Information in the E12 release response message is shown in Table 110.
The W-AGF-U status indication message may be sent by the W-AGF-U entity (5304) to indicate to the W-AGF-C its status of overload. Information in the W-AGF-U status indication message is shown in Table 111.
The resource status request message may be sent by a W-AGF-C entity (5304) to the W-AGF-U entity (5304) to initiate the requested measurement according to the parameters given in the message. Information in the resource status request message is shown in Table 112 and Table 113.
The resource status response message may be sent by the W-AGF-U entity (5304) to indicate that the requested measurement, for all the measurement objects included in the measurement may be successfully initiated. Information in the resource status response message is shown in Table 114.
The resource status failure message may be sent by the W-AGF-U entity (5304) to indicate that, for any of the requested measurement objects, the measurement may not be initiated. Information in the resource status failure message is shown in Table 115 and Table 116.
The resource status update message may be sent by W-AGF-U entity (5304) to the W-AGF-C entity (5302) to report the results of the requested measurements. Information in the resource status update message is shown in Table 117 and Table 118.
The bearer context setup request message may be sent by the W-AGF-C entity (5302) to request the W-AGF-U entity (5304) to setup a bearer context. Information in the bearer context setup request message is shown in Table 119.
The bearer context setup response message may be sent by the W-AGF-U entity (5304) to confirm the setup of the requested bearer context. Information in the bearer context setup response message is shown in Table 120.
The 5GC may inform the AGF of the created PDU session ID in the N2 PDU Session Resource Setup Request. Subsequently the AGF may assign a 5WE session ID and may bind the 5WE session ID to the PDU session ID. The 5WE session ID and the PDU session ID binding may be communicated to the 5G-RG. The 5G-RG may use the 5WE session ID to identify the UP packets of the PDU session. The 5WE Session ID may be used by the W-AGF-C (5302) to create Bearer Context on W-AGF-U as 5WE PDU Session ID for 5G-RG.
The bearer context setup failure message may be sent by the W-AGF-U entity (5304) to indicate that the setup of the bearer context was unsuccessful. Information in the bearer context setup failure message is shown in Table 121.
The bearer context modification request message may be sent by the W-AGF-C entity (5302) to request the W-AGF-U entity (5304) to modify a bearer context. Information in the bearer context modification request message is shown in Table 122 and Table 123.
The bearer context modification response message may be sent by the W-AGF-C (5302) to confirm the modification of the requested bearer context. Information in the bearer context modification response message is shown in Table 124.
Table 125 shows the PDU session resource failed list IE.
Table 126 shows the PDU session resource setup list IE.
Referring to Table 126, maxnoofPDUSessionResource may represent the maximum number of PDU sessions for a UE and maxnoofSPIs may represent the maximum number of SPIs for a UE. For example, the value of maxnoofPDUSessionResource may be 256. As another example, the value of maxnoofSPIs may be 64.
Table 127 shows the PDU session resource modified list IE.
Tables 128 and 129 show PDU session resource failed to modify list IE.
The bearer context modification failure message may be sent by the W-AGF-U entity (5304) to indicate that the modification of the bearer context was unsuccessful. Information in the bearer context modification failure message is shown in Table 130.
The bearer context modification required message may be sent by the W-AGF-U entity (5304) to inform the W-AGF-C entity (5302) that a modification of a bearer context is required (e.g., due to local problems at the W-AGF-U entity (5304)). Information in the bearer context modification required message is shown in Table 131 and Table 132.
Table 133 shows the PDU session resource to modify list IE.
Table 134 shows the PDU session resource to remove list IE.
The bearer context modification confirm message may be sent by the W-AGF-C entity (5302) to confirm the modification of the requested bearer context. The Information in the bearer context modification confirm message is shown in Table 135.
The bearer context release command message may be sent by the W-AGF-C entity (5302) to command the W-AGF-U entity (5304) to release an UE-associated logical E12 connection. Information in the bearer context release command message is shown in Table 136.
The bearer context release complete message may be sent by the W-AGF-U entity (5304) to confirm the release of the UE-associated logical E12 connection. Information in the bearer context release complete message is shown in Table 137.
The heartbeat request message may be sent by the W-AGF-C entity (5302) or the W-AGF-U entity (5304) to find out if the peer entity is alive. Information in the heartbeat request message is shown in Table 145.
The heartbeat response message may be sent as a response to a received heartbeat request message by the W-AGF-C entity (5302) or W-AGF-U entity (5304). Information in the heartbeat response message is shown in Table 146.
The performance statistics request message may be sent by the W-AGF-C entity (5302) to the W-AGF-U entity (5304) to initiate the requested KPIs according to parameters given in the performance statistics request message. Information in the performance statistics request message is shown in Tables 147 and 148.
The performance statistics response message may be sent by the W-AGF-U entity (5304) to indicate that the requested performance statistics (KPIs), for all the performance statistics objects included in the performance statistics message, may be successfully initiated. Information in the performance statistics response message is shown in Table 149.
The performance statistics failure message may be sent by the W-AGF-U (5304) to indicate that, for any of the requested performance statistics objects, the performance statistics may not be initiated. Information in the performance statistics failure message is shown in Tables 150 and 151.
The W-AGF-C E12 Setup Failure message may indicate a total number of W-AGF-C E12 Setup messages received from the W-AGF-C entity (5302) and a total number of W-AGF-C E12 Setup Failure messages sent to the W-AGF-C entity (5302). Information in the W-AGF-C E12 Setup Failure message is shown in Table 153.
The W-AGF-C Configuration Update Failure KPI IE may indicate a total number of W-AGF-C Configuration Update messages received from the W-AGF-C entity (5302) and a total number of W-AGF-C Configuration Update Failure messages sent to the W-AGF-C entity (5302). Information in the Configuration Update Failure KPI IE is shown in Table 154.
The Resource Status Failure KPI IE may indicate a total number of Resource Status messages received from the W-AGF-C entity (5302) and a total number of Resource Status Failure messages sent to the W-AGF-C entity (5302). Information in the Resource Status Failure KPI IE is shown in Table 155.
The Bearer Context Setup Failure KPI IE may indicate a total number of Bearer Context Setup messages received from the W-AGF-C entity (5302) and a total number of Bearer Context Setup Failure messages sent to the W-AGF-C entity (5302). Information in the Bearer Context Setup Failure KPI IE is shown in Table 156.
The Bearer Context Modification Failure KPI IE may indicate a total number of Bearer Context Modification messages received from the W-AGF-C entity (5302) and a total number of Bearer Context Modification Failure messages sent to W-AGF-C entity (5302). Information in the Bearer Context Modification Failure KPI IE is shown in Table 157.
The Performance Statistics Failure KPI IE may indicate a total number of Performance Statistics messages received from the W-AGF-C entity (5302) and a total number of Performance Statistics Failure messages sent to the W-AGF-C entity (5302). Information in the Performance Statistics Failure KPI IE is shown in Table 158.
The Peer User Plane Feedback Failure KPI IE may indicate a total number of Peer User Plane Feedback messages received from the W-AGF-C entity (5302) and a total number of Peer User Plane Feedback Failure messages sent to the W-AGF-C entity (5302). Information in the Peer User Plane Feedback Failure KPI IE is shown in Table 159.
The peer user plane feedback request message may be sent by a W-AGF-C entity (5302) to the W-AGF-U entity (5304) to initiate the requested peer user plane feedback according to the parameters given in the message. The UPF may be considered as W-AGF-U's user plane peer. Information in the peer user plane feedback request message is shown in Table 160.
The peer user plane feedback response message may be sent by the W-AGF-U (5304) to indicate that the requested peer user plane feedback, for all the peer user plane feedback objects included in the peer user plane feedback may be successfully initiated. Information in the peer user plane feedback response message is shown in Table 161.
The peer user plane feedback failure message may be sent by the W-AGF-U (5304) to indicate that, for any of the requested peer user plane feedback objects, the peer user plane feedback may not be initiated. Information in the peer user plane feedback failure message is shown in Table 69.
The peer user plane feedback update message reports the results of the requested peer user plane feedback. Information in the peer user plane feedback update message is shown in Tables 163 and 164.
In an embodiment, the W-AGF-C entity (5302) includes a processor (5302a), a communicator (5302b), a memory (5302c), and an interface controller (5302d). The processor (5302a) may be communicatively coupled with the communicator (5302b), the memory (5302c), and the interface controller (5302d).
The interface controller (5302d) may split the functionality of the W-AGF into the control plane functionality, where the control plane functionality may be handled by the W-AGF-C entity (5302). Further, the interface controller (5302d) may add the interface between the W-AGF-C entity (5302) and the W-AGF-U entity (5304). Further, the interface controller (5302d) may monitor at least one of the operations associated with the interface and the services associated with the interface.
The interface controller (5302d) may be physically implemented by analog and/or digital circuits such as, but not limited to, logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits, or the like, and may optionally be driven by firmware. The interface controller (5302d) may be a part of the processor (5302a) or may be integrally referred to as at least one processor with the processor (5302a).
Further, the processor (5302a) may be configured to execute instructions stored in the memory (5302c) and to perform various processes of the W-AGF-C entity (5302). The communicator (5302b) may be configured for communicating internally between internal hardware components and with external devices via one or more networks. The memory (5302c) may also store instructions to be executed by the processor (5302a). The memory (5302c) may include non-volatile storage elements. Examples of such non-volatile storage elements may include, but not be limited to, magnetic hard discs, optical discs, floppy discs, flash memories, and/or forms of EPROMs and/or EEPROMs. The memory (5302a) may, in some examples, be considered a non-transitory storage medium. The term “non-transitory” may indicate that the storage medium may not be embodied in a carrier wave or a propagated signal. However, the term “non-transitory” may not be interpreted that the memory (5302c) may be non-movable. In certain examples, a non-transitory storage medium may store data that may, over time, change (e.g., in RAM or cache).
In an embodiment, the W-AGF-U entity (5304) may include a processor (5304a), a communicator (5304b), a memory (5304c), and an interface controller (5304d). The processor (5304a) may be communicatively coupled with the communicator (5304b), the memory (5304c), and the interface controller (5304d).
The interface controller (5304d) may split the functionality of the W-AGF into the user plane functionality, where the user plane functionality may be handled by the W-AGF-U entity (5304). Further, the interface controller (5304d) may add an interface between the W-AGF-C entity (5302) and the W-AGF-U entity (5304). Further, the interface controller (5304d) monitors at least one of the operation associated with the interface and the service associated with the interface.
The interface controller (5304d) may be physically implemented by analog and/or digital circuits such as, but not limited to, logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits, or the like, and may optionally be driven by firmware. The interface controller (5304d) may be a part of the processor (5304a) or may be integrally referred to as at least one processor with the processor (5304a).
The interface controller (e.g., 5302d or 5304d) may monitor an operation associated with the interface and/or a service associated with the interface. The operation may be and/or may include, for example, but not be limited to, the user plane traffic procedure, the interface management procedure, the bearer management procedure, the trace start procedure, the deactivate trace procedure, and/or the load management procedure. The service may be and/or may include, for example, but not be limited to, a UE-associated service and/or a non UE-associated service.
The interface management procedure may be, for example, but not be limited to, the reset procedure initiated from the W-AGF-C entity (5302), the reset procedure initiated from the at least one W-AGF-U entity (5304), the error indication procedure originated at the W-AGF-C entity (5302), the error indication procedure originated at the at least one W-AGF-U entity (5304), the W-AGF-U E12 setup procedure, the W-AGF-C E12 setup procedure, the W-AGF-U configuration update procedure, the W-AGF-C configuration update procedure, the E12 release procedure, and/or the W-AGF-U status indication procedure.
The bearer management procedure may be, for example, but not be limited to, the bearer context setup procedure, the bearer context release request procedure initiated by the at least one W-AGF-U entity (5304), the bearer context release procedure initiated by the W-AGF-C entity (5302), the bearer context modification procedure initiated by the W-AGF-C entity (5302), the bearer context modification required procedure initiated by the at least one W-AGF-U entity (5304), the bearer context inactivity notification procedure, the data usage report procedure, the DL data notification procedure, and the UL data notification procedure. The load management procedure may be, for example, but not be limited to, a resource status reporting initiation procedure, resource status reporting procedure.
The interface controller (5304d) may be physically implemented by analog and/or digital circuits such as, but not limited to, logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits, or the like, and may optionally be driven by firmware.
Further, the processor (5304a) may be configured to execute instructions stored in the memory (5304c) and to perform various processes of the W-AGF-U entity (5304). The processor (5302a), the processor (5304a), the interface controller (5302d) and the interface controller (5304d) may be integrally referred to as at least one processor of the W-AGF (5306). The communicator (5304b) may be configured for communicating internally between internal hardware components and with external devices via one or more networks. The memory (5304c) may also store instructions to be executed by the processor (5304a). The memory (5304c) may include non-volatile storage elements. Examples of such non-volatile storage elements may include, but not be limited to, magnetic hard discs, optical discs, floppy discs, flash memories, and/or forms of EPROMs and/or EEPROMs. The memory (5304c) may, in some examples, be considered a non-transitory storage medium. The term “non-transitory” may indicate that the storage medium may not be embodied in a carrier wave or a propagated signal. However, the term “non-transitory” may not be interpreted that the memory (5304c) may be non-movable. In some examples, a non-transitory storage medium may store data that may, over time, change (e.g., in RAM and/or cache).
Although
At operation 10102, the method may include configuring (or splitting) the W-AGF function as the W-AGF-C entity (5302) and the W-AGF-U entity (5304). At operation 10104, the method may include handling the control plane signalling by the W-AGF-C entity (5302) and the user plane signalling by the W-AGF-U entity (5304).
The method may be implemented in the CUPS on W-AGF by splitting W-AGF into the W-AGF-C entity (5302) and the W-AGF-U entity (5304) and by introducing the interface (e.g., E12 interface) between the W-AGF-C entity (5302) and the W-AGF-U entity (5304).
The various actions, acts, blocks, steps, or the like in the flowcharts (e.g., flowcharts 5200 and 10100) may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some of the actions, acts, blocks, steps, or the like may be omitted, added, modified, skipped, or the like without departing from the scope of the present disclosure.
The foregoing description of the specific embodiments may so fully reveal the general nature of the embodiments herein that others may, by applying current knowledge, readily modify and/or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of embodiments, those skilled in the art may recognize that the embodiments herein may be practiced with modification within the spirit and scope of the embodiments as described herein.
| Number | Date | Country | Kind |
|---|---|---|---|
| 202341065649 | Sep 2023 | IN | national |
This application is a continuation of International Application No. PCT/KR2024/002168, designating the United States, filed on Feb. 20, 2024, in the Korean Intellectual Property Receiving Office and claiming priority to Indian Patent Application No. 202341065649, filed on Sep. 29, 2023, in the Indian Patent Office, the disclosures of which are incorporated by reference herein in their entireties.
| Number | Date | Country | |
|---|---|---|---|
| Parent | PCT/KR2024/002168 | Feb 2024 | WO |
| Child | 18618411 | US |
