Method, apparatus and computer program

Abstract

A method, an apparatus and a computer program for providing a control plane entity of a radio access network are provided. The apparatus comprises means for a control plane entity to obtain information of an uplink user plane transport network layer for a user equipment, the information being associated with user plane traffic of the user equipment; based on the information, selecting an instance for performing a user plane network function with a data radio bearer to the user equipment; and communicating with the instance for performing the user plane network function.

Description

Technical Field

[0001] Various examples of the present disclosure relate to methods, apparatuses, and computer programs for communication networks. Background Art

[0002] A communication network can be regarded as a facility that enables communication between two or more communication devices or provides access to a data network for a communication device. A mobile or wireless communication network is an example of a communication network. A communication device can be served by an application server.

[0003] Such communication networks operate according to standards provided by, for example, 3GPP (Third Generation Partnership Project) or ETSI (European Telecommunications Standards Institute). An example of a standard is the so-called 5G (Fifth Generation) standard provided by 3GPP. Summary of the Invention

[0004] Some examples of the present disclosure will be described with respect to certain aspects. These aspects are not intended to indicate the key or fundamental features of the embodiments of the present disclosure, nor are they intended to limit its scope. Given the present disclosure, other features, aspects, and elements / components will be readily apparent to those skilled in the art. For example, it should be understood that further aspects can be provided by a combination of any two or more of the aspects described below.

[0005] According to one aspect, there is provided an apparatus for a control plane entity of a radio access network, the apparatus including components for the control plane entity to perform the following operations: obtaining information of an uplink user plane transport network layer for a user equipment, where the information is associated with the user plane service of the user equipment; based on the information, selecting an instance for performing a user plane network function having a data radio bearer to the user equipment; and communicating with the instance for performing the user plane network function.

[0006] In some examples, the instance for performing the user plane network function is one of the following: a network function instance, or a network function component instance.

[0007] In some examples, the user plane network function is a gNodeB centralized unit user plane or an eNodeB user plane.

[0008] In some examples, the instance for performing the user plane function is within one of a master node or a secondary node of the radio access network, where the data radio access bearer is terminated, and the user equipment is connected to at least both the master node and the secondary node of the radio access network.

[0009] In some examples, the information of the uplink user plane transport network layer includes at least one of the following: a fully qualified tunnel endpoint identifier associated with the user plane function, a multiprotocol label switching label associated with the user plane function, or a segment routing segment identifier associated with the user plane function.

[0010] In some examples, the segment routing segment identifier is an SRv6 segment identifier.

[0011] In some examples, the information is received from an instance for performing core network functions.

[0012] In some examples, the core network function is an access and mobility management function that has selected a session management function for establishing a protocol data unit session, and the instance for performing the user plane network function is the gNodeB centralized unit user plane. In some examples, the information of the uplink user plane transport network layer (the information associated with the user plane service of the user equipment) includes: the uplink user plane transport network layer information for the protocol data unit session of the user equipment.

[0013] In some examples, the core network function is a mobility management entity that has selected a serving gateway and a packet data network gateway for establishing an evolved packet system session, and the instance for performing the user plane network function is the eNodeB user plane.

[0014] In some examples, the information of the uplink user plane transport network layer (the information associated with the user plane service of the user equipment) includes: the uplink user plane transport network layer information for the evolved packet system bearer of the user equipment, and this information allows the uplink service to reach the serving gateway.

[0015] In some examples, the core network function is a network function of a sixth-generation network specified by the 3rd Generation Partnership Project.

[0016] In some examples, the information is received from an instance for performing radio access network functions.

[0017] In some examples, the radio access network function is the gNodeB centralized unit control plane of the master node where the data radio bearer is terminated, the control plane entity is the gNodeB centralized unit control plane of the secondary node through which the data radio bearer is partially or fully forwarded, and the instance for performing the user plane network function is the gNodeB centralized unit user plane of the secondary node. It is the user plane of the secondary node through which the data radio bearer is partially or fully forwarded.

[0018] In some examples, the radio access network function is the eNodeB control plane of the master node where the data radio bearer is terminated, the control plane entity is the eNodeB control plane of the secondary node through which the data radio bearer is partially or fully forwarded, and the instance for performing the user plane network function is the eNodeB user plane of the secondary node.

[0019] In some examples, the radio access network function is the eNodeB control plane of the master node where the data radio bearer is terminated, the control plane entity is the gNodeB centralized unit control plane of the secondary node through which the data radio bearer is partially or fully forwarded, and the instance for performing the user plane network function is the gNodeB centralized unit user plane of the secondary node.

[0020] In some examples, the information of the uplink user plane transport network layer (which is associated with the user plane traffic of the user equipment) includes: the uplink user plane transport network layer information for the data radio bearer of the user equipment.

[0021] In some examples, the radio access network function is a network function of the 6th generation network specified by the 3rd Generation Partnership Project.

[0022] In some examples, the components for selection include: a component for determining, based on the information, another instance for performing the user plane network function, where the other instance has been selected by the entity from which the information is obtained; and a component for selecting, based on the determination, the instance for performing the user plane network function, where the user plane network function is associated with another instance selected by the entity.

[0023] In some examples, the entity is a network entity. In some examples, the entity is one of the following: an instance for performing a core network function, or an instance for performing a radio access network function. In some examples, the information is received from the access and mobility management function in the core network, which has selected a session management function for establishing a protocol data unit session, and the other instance is the core network user plane function for the protocol data unit session of the user equipment.

[0024] In some examples, the information is received from a mobility management entity in a core network that has selected a serving gateway for establishing an evolved packet system session, and another instance is a serving gateway for an evolved packet system session of a user equipment.

[0025] In some examples, the information is received from a gNodeB centralized unit control plane of a master node where a data radio bearer is terminated, and another instance is a gNodeB centralized unit user plane of a master node for carrying the data radio bearer, and the bearer is partially or fully forwarded to a gNodeB centralized unit user plane of a secondary node.

[0026] In some examples, the information is received from an eNodeB control plane of a master node where a data radio bearer is terminated, and another instance is an eNodeB user plane of a master node for carrying the data radio bearer, and the bearer is partially or fully forwarded to an eNodeB user plane of a secondary node.

[0027] In some examples, the information is received from a gNodeB centralized unit control plane of a master node where a data radio bearer is terminated, and another instance is a gNodeB centralized unit user plane of a master node for carrying the data radio bearer, and the bearer is partially or fully forwarded to an eNodeB user plane of a secondary node.

[0028] In some examples, the information is received from a network function of a sixth-generation network specified by the 3rd Generation Partnership Project, and another instance is a network function of a sixth-generation network specified by the 3rd Generation Partnership Project.

[0029] In some examples, the instance for performing a user plane network function is geographically co-located with another instance selected by the entity from which the information is obtained.

[0030] In some examples, the component is used for a control plane entity to perform: for a data radio bearer, disable at least one of the following: service data adaptation protocol processing, or packet data convergence protocol processing.

[0031] In some examples, based on the information, at least one of the following is disabled at a control plane entity: service data adaptation protocol processing, or packet data convergence protocol processing.

[0032] In some examples, the control plane entity is an instance of a centralized unit control plane in a 5th generation next-generation radio access network.

[0033] In some examples, the control plane entity is an instance of an eNodeB control plane in a 4th generation evolved universal terrestrial radio access network.

[0034] In some examples, the control plane entity is an instance in a sixth generation network.

[0035] According to one aspect, a method is provided, which includes: obtaining information of an uplink user plane transport network layer for a user equipment, where the information is associated with the user plane service of the user equipment; based on the information, selecting an instance for performing a user plane network function having a data radio bearer to the user equipment; and communicating with the instance for performing the user plane network function.

[0036] In some examples, the instance for performing the user plane network function is one of the following: a network function instance, or a network function component instance.

[0037] In some examples, the user plane network function is a gNodeB centralized unit user plane or an eNodeB user plane.

[0038] In some examples, the instance for performing the user plane function is within one of a master node or a secondary node of a radio access network, where the data radio access bearer is terminated, and the user equipment is connected to at least both the master node and the secondary node of the radio access network.

[0039] In some examples, the information of the uplink user plane transport network layer includes at least one of the following: a fully qualified tunnel endpoint identifier associated with the user plane function, a multi-protocol label switching label associated with the user plane function, or a segment routing segment identifier associated with the user plane function.

[0040] In some examples, the segment routing segment identifier is an SRv6 segment identifier.

[0041] In some examples, the information is received from an instance for performing a core network function.

[0042] In some examples, the core network function is a mobility management entity, an access and mobility management function, or a sixth generation core network control plane function.

[0043] In some examples, the information is received from an instance for performing a radio access network function.

[0044] In some examples, the selection includes: based on the information, determining another instance for performing the user plane network function, where the another instance has been selected by the entity from which the information is obtained; and based on the determination, selecting the instance for performing the user plane network function, where the user plane network function is associated with the another instance selected by the entity.

[0045] In some examples, the instance for performing user plane network functions is geographically co-located with another instance selected by the entity.

[0046] In some examples, the instance selected by the core network function is the user plane function for a protocol data unit session being established.

[0047] In some examples, the instance selected by the core network function is for a protocol data unit session being established, and the instance for performing user plane network functions is for a protocol data unit session being established. In some examples, the information of the uplink user plane transport network layer (which is associated with the user plane traffic of the user equipment) includes: the uplink user plane transport network layer information for the protocol data unit session of the user equipment.

[0048] In some examples, the method includes: disabling at least one of the following for a data radio bearer: service data adaptation protocol processing, or packet data convergence protocol processing.

[0049] In some examples, the core network function is the access and mobility management function that has selected a session management function for establishing a protocol data unit session, and the instance for performing user plane network functions is the gNodeB centralized unit user plane. In some examples, the information of the uplink user plane transport network layer (which is associated with the user plane traffic of the user equipment) includes: the uplink user plane transport network layer information for the protocol data unit session of the user equipment.

[0050] In some examples, the core network function is the mobility management entity that has selected a serving gateway and a packet data network gateway for establishing an evolved packet system session, and the instance for performing user plane network functions is the eNodeB user plane.

[0051] In some examples, the information of the uplink user plane transport network layer (which is associated with the user plane traffic of the user equipment) includes: the uplink user plane transport network layer information for the evolved packet system bearer of the user equipment, which allows uplink traffic to reach the serving gateway.

[0052] In some examples, the core network function is a network function of a sixth generation network specified by the 3rd Generation Partnership Project.

[0053] In some examples, the radio access network function is the gNodeB centralized unit control plane of the master node where the data radio bearer is terminated, the control plane entity is the gNodeB centralized unit control plane of the secondary node through which the data radio bearer is partially or fully forwarded, and the instance for performing the user plane network function is the gNodeB centralized unit user plane of the secondary node. It is the user plane of the secondary node through which the data radio bearer is partially or fully forwarded.

[0054] In some examples, the radio access network function is the eNodeB control plane of the master node where the data radio bearer is terminated, the control plane entity is the eNodeB control plane of the secondary node through which the data radio bearer is partially or fully forwarded, and the instance for performing the user plane network function is the eNodeB user plane of the secondary node.

[0055] In some examples, the radio access network function is the eNodeB control plane of the master node where the data radio bearer is terminated, the control plane entity is the gNodeB centralized unit control plane of the secondary node through which the data radio bearer is partially or fully forwarded, and the instance for performing the user plane network function is the gNodeB centralized unit user plane of the secondary node.

[0056] In some examples, the entity is a network entity. In some examples, the entity is one of the following: an instance for performing a core network function, or an instance for performing a radio access network function. In some examples, the information is received from the access and mobility management function in the core network that has selected the session management function for establishing a protocol data unit session, and another instance is the core network user plane function for the protocol data unit session of the user equipment.

[0057] In some examples, the information is received from the mobility management entity in the core network that has selected the serving gateway for establishing an evolved packet system session, and another instance is the serving gateway for the evolved packet system session of the user equipment.

[0058] In some examples, the information is received from the gNodeB centralized unit control plane of the master node where the data radio bearer is terminated, and another instance is the gNodeB centralized unit user plane of the master node that bears the data radio bearer, and the bearer is partially or fully forwarded to the gNodeB centralized unit user plane of the secondary node.

[0059] In some examples, the information is received from the eNodeB control plane of the master node where the data radio bearer is terminated, and another instance is the eNodeB user plane of the master node for carrying the data radio bearer, and the bearer is partially or fully forwarded to the eNodeB user plane of the secondary node.

[0060] In some examples, the information is received from the gNodeB centralized unit control plane of the master node where the data radio bearer is terminated, and another instance is the gNodeB centralized unit user plane of the master node for carrying the data radio bearer, and the bearer is partially or fully forwarded to the eNodeB user plane of the secondary node.

[0061] In some examples, the information is received from a network function of a sixth-generation network specified by the 3rd Generation Partnership Project, and another instance is a network function of a sixth-generation network specified by the 3rd Generation Partnership Project.

[0062] In some examples, based on the information, at least one of the following is disabled at the control plane entity: service data adaptation protocol processing, or packet data convergence protocol processing.

[0063] In some examples, the method is performed by a control plane entity.

[0064] In some examples, the control plane entity is an instance of the centralized unit control plane in a 5th generation next-generation radio access network.

[0065] In some examples, the control plane entity is an instance of the eNodeB control plane in a 4th generation evolved universal terrestrial radio access network.

[0066] In some examples, the control plane entity is an instance in a sixth-generation network.

[0067] According to one aspect, there is provided an apparatus for a control plane entity of a radio access network, the apparatus comprising: at least one processor, and at least one memory storing instructions that, when executed by the at least one processor, cause the control plane entity to perform: obtaining information of an uplink user plane transport network layer for a user equipment, wherein the information is associated with user plane traffic of the user equipment; based on the information, selecting an instance for performing a user plane network function having a data radio bearer to the user equipment; and communicating with the instance for performing the user plane network function.

[0068] In some examples, the instance for performing the user plane network function is one of the following: a network function instance, or a network function component instance.

[0069] In some examples, the user plane network function is the gNodeB centralized unit user plane or the eNodeB user plane.

[0070] In some examples, the instance for performing the user plane function is within one of the master node or the secondary node of the radio access network, where the data radio access bearer is terminated, and the user equipment is connected to at least both the master node and the secondary node of the radio access network.

[0071] In some examples, the information of the uplink user plane transport network layer includes at least one of the following: a fully qualified tunnel endpoint identifier associated with the user plane function, a multi-protocol label switching label associated with the user plane function, or a segment routing segment identifier associated with the user plane function.

[0072] In some examples, the segment routing segment identifier is an SRv6 segment identifier.

[0073] In some examples, the information is received from an instance for performing the core network function.

[0074] In some examples, the core network function is a mobility management entity, an access and mobility management function, or a 6th generation core network control plane function.

[0075] In some examples, the information is received from an instance for performing the radio access network function.

[0076] In some examples, the selection includes: based on the information, determining another instance for performing the user plane network function, where the other instance has been selected by the entity from which the information is obtained; and based on the determination, selecting the instance for performing the user plane network function, where the user plane network function is associated with the other instance selected by the entity.

[0077] In some examples, the instance for performing the user plane network function is geographically co-located with the other instance selected by the entity.

[0078] In some examples, the instance selected by the core network function is the user plane function for a protocol data unit session being established.

[0079] In some examples, the instance selected by the core network function is for a protocol data unit session being established, and the instance for performing the user plane network function is for a protocol data unit session being established. In some examples, the information of the uplink user plane transport network layer (the information associated with the user plane traffic of the user equipment) includes: the uplink user plane transport network layer information for the protocol data unit session of the user equipment.

[0080] In some examples, cause a control plane entity to perform: for a data radio bearer, disable at least one of the following: service data adaptation protocol processing, or packet data convergence protocol processing.

[0081] In some examples, based on the information, disable at least one of the following at the control plane entity: service data adaptation protocol processing, or packet data convergence protocol processing.

[0082] In some examples, the core network function is an access and mobility management function that has selected a session management function for establishing a protocol data unit session, and the instance for performing the user plane network function is a gNodeB central unit user plane. In some examples, the information of the uplink user plane transport network layer (the information associated with the user plane traffic of the user equipment) includes: the uplink user plane transport network layer information for the protocol data unit session of the user equipment.

[0083] In some examples, the core network function is a mobility management entity that has selected a serving gateway and a packet data network gateway for establishing an evolved packet system session, and the instance for performing the user plane network function is an eNodeB user plane.

[0084] In some examples, the information of the uplink user plane transport network layer (the information associated with the user plane traffic of the user equipment) includes: the uplink user plane transport network layer information for the evolved packet system bearer of the user equipment, which allows uplink traffic to reach the serving gateway.

[0085] In some examples, the core network function is a network function of a sixth-generation network specified by the 3rd Generation Partnership Project.

[0086] In some examples, the radio access network function is the gNodeB central unit control plane of the master node where the data radio bearer is terminated, the control plane entity is the gNodeB central unit control plane of the secondary node through which the data radio bearer is partially or fully forwarded, and the instance for performing the user plane network function is the gNodeB central unit user plane of the secondary node. It is the user plane of the secondary node through which the data radio bearer is partially or fully forwarded.

[0087] In some examples, the radio access network function is the eNodeB control plane of the master node where the data radio bearer is terminated, the control plane entity is the eNodeB control plane of the secondary node through which the data radio bearer is partially or fully forwarded, and the instance for performing the user plane network function is the eNodeB user plane of the secondary node.

[0088] In some examples, the radio access network function is the eNodeB control plane of the master node where the data radio bearer is terminated, the control plane entity is the gNodeB centralized unit control plane of the secondary node through which the data radio bearer is partially or fully forwarded, and the instance for performing the user plane network function is the gNodeB centralized unit user plane of the secondary node.

[0089] In some examples, the entity is a network entity. In some examples, the entity is one of the following: an instance for performing a core network function, or an instance for performing a radio access network function. In some examples, the information is received from the access and mobility management function in the core network, which has selected the session management function for establishing a protocol data unit session, and another instance is the core network user plane function for the protocol data unit session of the user equipment.

[0090] In some examples, the information is received from the mobility management entity in the core network, which has selected the serving gateway for establishing an evolved packet system session, and another instance is the serving gateway for the evolved packet system session of the user equipment.

[0091] In some examples, the information is received from the gNodeB centralized unit control plane of the master node where the data radio bearer is terminated, and another instance is the gNodeB centralized unit user plane of the master node for carrying the data radio bearer, and the bearer is partially or fully forwarded to the gNodeB centralized unit user plane of the secondary node.

[0092] In some examples, the information is received from the eNodeB control plane of the master node where the data radio bearer is terminated, and another instance is the eNodeB user plane of the master node for carrying the data radio bearer, and the bearer is partially or fully forwarded to the eNodeB user plane of the secondary node.

[0093] In some examples, the information is received from the gNodeB centralized unit control plane of the master node where the data radio bearer is terminated, and another instance is the gNodeB centralized unit user plane of the master node for carrying the data radio bearer, and the bearer is partially or fully forwarded to the eNodeB user plane of the secondary node.

[0094] In some examples, the information is received from the network function of the 6th generation network specified by the 3rd Generation Partnership Project, and another instance is the network function of the 6th generation network specified by the 3rd Generation Partnership Project.

[0095] In some examples, the control plane entity is an instance of the centralized unit control plane in the fifth generation next generation radio access network.

[0096] In some examples, the control plane entity is an instance of the eNodeB control plane in the fourth generation evolved universal terrestrial radio access network.

[0097] In some examples, the control plane entity is an instance in the sixth generation network.

[0098] According to one aspect, there is provided a computer program comprising instructions which, when executed by a device, cause the device to perform at least the following operations: obtaining information of an uplink user plane transport network layer for a user equipment, wherein the information is associated with the user plane traffic of the user equipment; based on the information, selecting an instance for performing a user plane network function having a data radio bearer to the user equipment; and communicating with the instance for performing the user plane network function.

[0099] According to one aspect, there is provided a device comprising: circuitry configured to perform the following operations: obtaining information of an uplink user plane transport network layer for a user equipment, wherein the information is associated with the user plane traffic of the user equipment; circuitry configured to perform the following operations: based on the information, selecting an instance for performing a user plane network function having a data radio bearer to the user equipment; and circuitry configured to perform the following operations: communicating with the instance for performing the user plane network function.

[0100] According to one aspect, there is provided a device for providing a user plane entity of a radio access network, the device comprising components for the user plane entity to perform the following operations: receiving information of an uplink user plane transport network layer, wherein the information is associated with the user plane traffic of the user equipment; and copying at least a portion of the information into another information related to a downlink user plane transport network layer.

[0101] In some examples, the device comprises components for disabling at least one of the following at the user plane entity based on the information: service data adaptation protocol processing, or packet data convergence protocol processing.

[0102] In some examples, the information of the uplink user plane transport network layer comprises at least one of the following: a fully qualified tunnel endpoint identifier associated with a user plane function, a multi-protocol label switching segment routing label associated with a user plane function, or a segment routing segment identifier associated with a user plane function.

[0103] In some examples, the information of the uplink user plane transport network layer is received from a control plane entity.

[0104] In some examples, the user plane entity is one of the following: an instance of a centralized unit user plane, or an instance of a distributed unit.

[0105] According to one aspect, a method is provided, which includes: receiving information of an uplink user plane transport network layer, where the information is associated with the user plane service of a user equipment; and copying at least a part of the information into another information related to a downlink user plane transport network layer.

[0106] In some examples, the method includes: based on the information, disabling at least one of the following at the user plane entity: service data adaptation protocol processing, or packet data convergence protocol processing.

[0107] In some examples, the information of the uplink user plane transport network layer includes at least one of the following: a fully qualified tunnel endpoint identifier associated with a user plane function, a multi-protocol label switching segment routing label associated with a user plane function, or a segment routing segment identifier associated with a user plane function.

[0108] In some examples, the information of the uplink user plane transport network layer is received from a control plane entity.

[0109] In some examples, the user plane entity is one of the following: an instance of a centralized unit user plane, or an instance of a distributed unit.

[0110] In some examples, the method is executed by a user plane entity of a radio access network.

[0111] According to one aspect, a device for providing a user plane entity of a radio access network is provided. The device includes: at least one processor, and at least one memory storing instructions, which when executed by the at least one processor cause the user plane entity to execute: receiving information of an uplink user plane transport network layer, where the information is associated with the user plane service of a user equipment; and copying at least a part of the information into another information related to a downlink user plane transport network layer.

[0112] In some examples, causing the device to execute: based on the information, disabling at least one of the following at the user plane entity: service data adaptation protocol processing, or packet data convergence protocol processing.

[0113] In some examples, the information of the uplink user plane transport network layer includes at least one of the following: a fully qualified tunnel endpoint identifier associated with a user plane function, a multi-protocol label switching segment routing label associated with a user plane function, or a segment routing segment identifier associated with a user plane function.

[0114] In some examples, information of the uplink user plane transport network layer is received from a control plane entity.

[0115] In some examples, the user plane entity is one of the following: an instance of a centralized unit user plane, or an instance of a distributed unit.

[0116] According to one aspect, a computer program is provided, which includes instructions that, when executed by a device, cause the device to at least perform the following operations: receive information of the uplink user plane transport network layer, where the information is associated with the user plane traffic of a user equipment; and copy at least a part of the information into another information related to the downlink user plane transport network layer.

[0117] A computer product, which is stored on a medium, can cause a device to execute the method as described herein.

[0118] A non-transitory computer-readable medium includes program instructions that, when executed by a device, cause the device to execute the method as described herein.

[0119] An electronic device may include a device as described herein.

[0120] Various other aspects and further examples are also described in the following detailed description and the appended claims.

[0121] According to some aspects, the subject matter of the independent claims is provided. Some further aspects are defined in the dependent claims. Examples that do not fall within the scope of the claims should be construed as helpful for understanding the examples of the present disclosure.

[0122] List of Abbreviations:

[0123] AF: Application Function

[0124] AMF: Access and Mobility Management Function

[0125] AN: Access Network

[0126] AUPF: Access and User Plane Function BS: Base Station

[0127] CaaS: Container as a Service

[0128] CN: Core Network

[0129] CP: Control Plane

[0130] CU: Centralized Unit

[0131] DL: Downlink

[0132] DNN: Data Network Name

[0133] DU: Distributed Unit

[0134] eNB: eNodeB F-TEID: Fully Qualified Tunnel Endpoint Identifier gNB: gNodeB GPRS: General Packet Radio Service GTP: GPRS Tunneling Protocol

[0135] IaaS: Infrastructure as a Service

[0136] IIoT: Industrial Internet of Things IPSec: Internet Protocol Security

[0137] K8: Kubernetes LTE: Long Term Evolution

[0138] MAC: Media Access Control

[0139] MS: Mobile Station

[0140] MPLS: Multi-Protocol Label Switching

[0141] NEF: Network Exposure Function NG-RAN: Next Generation Radio Access Network NG-U: NG User Plane (N3) NF: Network Function

[0142] NR: New Radio

[0143] NRF: Network Repository Function

[0144] NW: Network

[0145] PaaS: Platform as a Service

[0146] PDCP: Packet Data Convergence Protocol PDU: Protocol Data Unit PCF Policy Control Function

[0147] PLMN: Public Land Mobile Network RAN: Radio Access Network

[0148] RLC: Radio Link Control

[0149] RRC: Radio Resource Control

[0150] RF: Radio Frequency

[0151] SDAP: Service Data Adaptation Protocol SMF: Session Management Function SRv6: Segment Routing Version 6 TEID: Tunnel Endpoint Identifier

[0152] TNL: Transport Network Layer

[0153] UE: User Equipment

[0154] UDR: Unified Data Repository

[0155] UDM: Unified Data Management

[0156] UL: Uplink

[0157] UP: User Plane

[0158] UPF: User Plane Function

[0159] 3GPP: 3rd Generation Partnership Project

[0160] 5G: 5th Generation

[0161] 5GC: 5G Core Network

[0162] 5G-AN: 5G Radio Access Network

[0163] 5GS: 5G System Description of the Drawings

[0164] Some examples will now be described by way of illustration and non-limiting example only with reference to the accompanying drawings, wherein:

[0165] Figure 1 Shows a schematic representation of a 5G communication system;

[0166] Figure 2 Shows for Figure 1 A schematic representation of an apparatus of a 5G communication system;

[0167] Figure 3 Shows a schematic representation of a communication device;

[0168] Figure 4 Shows a schematic representation of a 5G RAN including a centralized unit and a distributed unit;

[0169] Figure 5 Shows a schematic representation of access and user plane functions within a 5G communication system;

[0170] Figure 6 Shows a schematic representation of the co-location of a RAN centralized unit user plane instance and a user plane function instance within a 5G communication system;

[0171] Figure 7 Shows an example signaling and operation schematic diagram for PDU session establishment in a 5G communication system in which a RAN centralized unit user plane instance and a user plane function instance are co-located;

[0172] Figure 8 Shows an example method flowchart executed by an apparatus; and

[0173] Figure 9A schematic representation of a non - volatile memory medium storing instructions that, when executed by a processor, permit the processor to execute Figure 8 one or more steps of a method. Detailed Description

[0174] In some communication systems (such as, for example, 5G and 6G systems), radio access network (RAN) nodes are split into a central unit (CU) and a distributed unit (DU). In 5G, the RAN node (or base station) is called a gNodeB (gNB). Each gNB is logically divided into two different physical entities, called the CU and the DU. The CU supports the upper layers of the protocol stack, including components such as the service data adaptation protocol (SDAP), the packet data convergence protocol (PDCP), and the radio resource control (RRC). The DU is responsible for handling the lower layers of the protocol stack, such as the radio link control (RLC), the media access control (MAC), and the physical layer. Typically, a single CU is associated with each gNB. A single CU can manage (or supervise) multiple DUs. The communication interface between the CU and the DU is called the F1 interface. Both the NG and Xn - C interfaces for the gNB terminate at the gNB - CU. The F1 interface supports signaling exchange and data transfer between these endpoints, effectively isolating the radio network layer from the transport network layer. The NGAP (Next Generation Application Part) protocol is provided for the control plane between the 5G Core (5GC) and the 5G RAN.

[0175] The gNB CU can be divided into its control plane (CP) part and its user plane (UP) part, which respectively result in the gNB - CU - CP and the gNB - CU - UP. Typically, these network functions are respectively called CU - CP and CU - UP. The interface between the CU - CP and the CU - UP is called the E1 interface, which is mainly dedicated to control plane operations. A gNB can include multiple CU - UP instances. Thus, an instance of the gNB - CU - UP can be selected, for example, when a protocol data unit (PDU) session is established.

[0176] For some implementations, it may be applicable to merge the gNB-CU-UP with the UPF (of the 5GC) to form an AUPF (Access and User Plane Function) in some communication systems. Such a merger may include one or more of the following benefits: avoiding NG-U (N3-U) encoding and decoding between the RAN and the CN, avoiding Internet Protocol Security (IPSec) tunnel protection of NG-U (N3-U) traffic between the RAN and the Security Gateway (SeGW), using a common buffer for PDCP retransmissions for downlink traffic to be acknowledged instead of the buffer in the gNB-CU-UP and allowing lossless handover and another buffer in the UPF (during downlink data notification, also known as paging), avoiding PDCP sequence reset during handover, avoiding ROHCP process / reset during handover, registering the combined entity to the service-based architecture (more specifically, the NRF, notifying the NRF of availability, load, and overload), sharing common PaaS, CaaS, IaaS, lifecycle manager, element manager, CI-CD chain, SW release cycle, product management, R&D, verification, delivery, operation, and other product synergies.

[0177] A next-generation (NG) user plane interface (NG-U) is defined between the 5G RAN node and the UPF. The AUPF can be deployed as a distributed network function at a suitable "far edge" distributed cloud computing data center. Alternatively, the AUPF can be centralized in a large centralized cloud computing data center that benefits from economies of scale. In this case, the AUPF can be owned by a Mobile Network Operator (MNO), an enterprise, or a hyperscaler. A hyperscaler is a large data center that provides a large amount of computing resources and typically takes the form of an elastic cloud platform.

[0178] In some examples, a device provides a control plane entity of a radio access network, the device including components for the control plane entity to perform the following operations:

[0179] Obtain information on the uplink user plane transport network layer for a user equipment, where the information is associated with the user plane traffic of the user equipment;

[0180] Based on the information, select an instance of a user plane network function to perform with a data radio bearer to the user equipment; and

[0181] Communicate with the instance of the user plane network function to be performed.

[0182] Reference will be made below to a 5G communication system including a 5G RAN connected to a 5G core network (e.g., as Figure 1These examples will be discussed in more detail (as shown in Figure 4 ). Detailed illustrative examples of 5G RAN with a CU (which can also be decomposed into CU-CP and multiple CU-UPs) and multiple DU network functions will also be discussed below. Detailed illustrative examples of an AUPF within a communication system (such as, for example, as shown in Figure 5 ) will also be discussed below.

[0183] In the following, various example embodiments of the present disclosure will be described with reference to a communication device capable of communicating via a wireless cellular system and a communication system serving such a communication device. Before describing the various example embodiments in detail, some general aspects of wireless communication systems and communication devices will be briefly described with reference to Figures 1 to 5 to assist in understanding the technology on which the described examples are based. It should be understood that even though some of the following figures are related to 5G systems, the examples of the present disclosure are applicable to other standards, such as, for example, advanced 5G, 6G, etc.

[0184] Figure 1 A schematic representation of a 5G communication system 100 is shown. The wireless communication system 100 includes one or more communication devices 102, such as user equipment (UE) or terminals. The wireless communication system 100 includes a 5G system (5GS). The 5GS includes a 5G radio access network (5G-RAN) 106, a 5G core network (5GC) 104 including one or more network functions (NF), one or more application functions (AF) 108, and one or more data networks (DN) 110.

[0185] The 5G-RAN 106 may include one or more gNodeB (gNB) distributed unit (DU) functions connected to one or more gNodeB (gNB) centralized unit (CU) functions.

[0186] The 5GC 104 includes an access and mobility management function (AMF) 112, a session management function (SMF) 114, an authentication server function (AUSF) 116, a user data management (UDM) 118, a user plane function (UPF) 120, a network exposure function (NEF) 122, and / or other NFs. Some examples as shown below may be applicable to the 3GPP 5G standard. However, some examples may also be applicable to advanced 5G, 4G, 3G, and other 3GPP standards.

[0187] In the wireless communication system 100 (such as Figure 1In the system shown in FIG. [reference number not provided], a communication device 102 (such as, for example, a terminal, a user device, a user equipment (UE), and / or a machine type communication device) is provided with wireless access via at least one base station or a similar wireless transmitting and / or receiving node or point. The communication device 102 is provided with suitable signal receiving and transmitting means to enable communication, for example, to enable access to a communication network or to communicate directly with other devices. The communication device 102 may access a carrier provided by a base station or an access point and transmit and / or receive communications on that carrier.

[0188] Figure 2 FIG. [reference number not provided] illustrates an example of a device 200. The device 200 may be used in Figure 1 a 5G communication system. The device 200 may be used to control the functions of one or more network entities and / or network functions, such as the entities of a 5G-RAN or 5GC as shown in Figure 1 FIG. [reference number not provided]. The device 200 includes at least one random access memory (RAM) 211a, at least one read-only memory (ROM) 211b, at least one processor 212, 213, and an input / output interface 214. The at least one processor 212, 213 is coupled to the RAM 211a and the ROM 211b. The at least one processor 212, 213 may be configured to execute suitable software code 215. The software code 215 may, for example, allow the execution of one or more steps to perform one or more of the proposed aspects or examples. The software code 215 may be stored in the ROM 211b. The device 200 may be interconnected with another device 200 that controls another entity / function of the 5G-AN or 5GC. In some examples, the device 200 may be configured to provide one or more functions of the 5G-AN or 5GC. For example, the device 200 may be configured to perform at least some of the functions of a specific function of the 5G-AN or 5GC. For example, the device 200 may be configured to operate as a specific function of the 5G-AN or 5GC. In an alternative example, the device 200 may be configured to perform at least some of the functions of two or more functions of the 5G-AN and / or 5GC. For example, the device 200 may be configured to operate as two or more functions of the 5G-AN and / or 5GC. The device 200 may include one or more circuits or circuitry (not shown) that may be configured to perform one or more of the proposed aspects or examples.

[0189] Figure 3 FIG. [reference number not provided] illustrates an example of a communication device 300. The communication device 300 may be similar to Figure 1The communication device 102 shown in [description]. The communication device 300 can be provided by any device capable of transmitting and receiving radio signals. Non-limiting and illustrative examples of the communication device 300 are user equipment, terminals, mobile stations (MS) or mobile devices (such as mobile phones or so-called "smartphones"), computers equipped with a wireless interface card or other wireless interface facilities (e.g., USB dongles), personal data assistants (PDAs) or tablets equipped with wireless communication capabilities, machine type communication (MTC) devices, cellular Internet of Things (CIoT) devices, land / sea / air vehicles (such as cars, trucks, ships, airplanes, or drones), or any combination of these or the like. The communication device 300 can, for example, provide data communication for carrying communications. The communication can be one or more of voice, email, text messages, multimedia, data, machine data, etc.

[0190] The communication device 300 can receive signals via a suitable device for reception over the air or radio interface 307, and can transmit signals via a suitable device for transmitting radio signals. In Figure 3 [description], the transceiver device is schematically labeled by block 306. The transceiver device 306 can be provided, for example, by means of a radio part and an associated antenna arrangement. The antenna arrangement can be arranged inside or outside the mobile device.

[0191] The communication device 300 can be provided with at least one processor 301, at least one memory ROM 302a, at least one RAM 302b, and other possible components 303 for use in the assisted execution of the tasks it is designed to perform in software and hardware, including controlling access to and communication with an access system and other communication devices. The at least one processor 301 is coupled to the RAM 302b and the ROM 302a. The at least one processor 301 can be configured to execute suitable software code 308. The software code 308 can, for example, allow the execution of one or more of the proposed aspects. The software code 308 can be stored in the ROM 302a. The communication device 300 can include one or more circuits or circuitry (not shown) that can be configured to perform one or more of the aspects or examples described herein.

[0192] The processor, storage device, and other associated control means can be provided on a suitable circuit board and / or chipset. This feature is labeled by reference numeral 304. The communication device can optionally have a user interface, such as a keyboard 305, a touchscreen or touchpad, a combination thereof, etc. Optionally, depending on the type of device, one or more of a display, a speaker, and a microphone can be provided.

[0193] Figure 4Shows a schematic representation of a 5G RAN including a central unit and distributed units.

[0194] A 5G RAN 401 is provided, which may be referred to as gNB 401. gNB 401 may be similar to Figure 1 the 5G RAN106.

[0195] gNB 401 includes gNB-CU-CP 403 and multiple gNB-CU-UP 405. Each gNB-CU-UP among the multiple gNB-CU-UP 405 may be referred to as an instance of gNB-CU-UP. gNB 401 also includes a first gNB-DU 407 and a second gNB-DU409. In Figure 4 the example, there are two gNB-DUs. In other examples, there may be more than two or fewer than two gNB-DUs.

[0196] The interface between gNB-CU-CP 403 and each gNB-CU-UP among the multiple gNB-CU-UP 405 is called the E1 interface. The E1 interface is mainly dedicated to control plane operations. The interfaces between gNB-CU-CP 403 and the first and second gNB-DUs 407, 409 are called F1-C (F1 - Control Function) interfaces. The corresponding interfaces between gNB-DUs 407, 409 and the multiple gNB-CU-UP 405 are individually called F1-U (F1 - User Function) interfaces. Both the NG and Xn-C interfaces (not shown) for gNB 401 terminate at the gNB-CU. The F1 interface supports signaling exchange and data transfer between these endpoints, thus effectively isolating the radio network layer from the transport network layer.

[0197] gNB-CU-CP 403 hosts the control plane part of the Radio Resource Control (RRC) and PDCP protocols. gNB-CU-CP403 also terminates the E1 interface connected to gNB-CU-UP 405 and the F1-C interface connected to gNB-DUs 407, 409. Each gNB-CU-UP 405 hosts the user plane part of the PDCP protocol for the gNB-CU of gNB 401. Each gNB-CU-UP 405 also hosts the SDAP protocol for the gNB-CU of gNB.

[0198] When establishing a Protocol Data Unit (PDU) session, the gNB-CU-CP 403 receives information from the CN via an N2 PDU session resource establishment request. Within this request, information on the uplink (UL) user plane (UP) transport network layer (TNL) (e.g., uplink user plane transport network layer information / uplink user plane transport network information element (IE)) may be included. For each PDU session, the gNB 401 (e.g., gNB-CU-CP 403 and gNB-CU-UP 405) stores the uplink user plane transport network layer IE. Subsequently, the information of the uplink user plane transport network layer IE is used as the uplink termination point for routing user plane data to the UPF.

[0199] Figure 5 A schematic representation of an Access and User Plane Function (AUPF) within a 5G communication system is shown. Although Figure 5 a 5G system is depicted, it is also considered that the interfaces and functions of the AUPF as described below are equally applicable to other 3GPP specifications, such as, for example, Advanced 5G, 6G, etc.

[0200] A communication system 500 is provided, which has a UE 501 connected to a DU 503 of a gNB. The RAN-CP (or CU-CP) 505 has interfaces with the DU 503 and the AUPF 507. As previously discussed, the AUPF is a combined function of the CU-UP and the UPF. In this way, the UPF is integrated with the CU-UP such that the combination is (logically) part of both the RAN and the mobile core network. In other examples, the UPF and the CU-UP are collocated (or co-located) with each component remaining logically part of the RAN and the mobile core network respectively. It should be understood that in the context of the present disclosure, the terms "collocated" and "co-located" may be used interchangeably. The collocation of the UPF and the RAN-CU-CP may mean that these functions share a location or facility, share common computing resources, and / or are geographically close to each other.

[0201] The CU-CP 505 also has an interface with the core CP 509. This core CP can be the AMF and the SMF, as well as Figure 1Other mobile core network control plane functions in it. The core CP 509 has an N4 interface with the AUPF 507 and can also support an N4 interface with the UPF 511 used when serving the central packet data network (PDN) domain 515. The AUPF 507 has an interface to the local (PDN) domain 513, while the UPF 511 has an interface to the (separate) central PDN domain 515. The AUPF can be connected to the local PDN 513 (e.g., using an edge computing server), and the UE 501 can be anchored at the UPF 511 (e.g., the UE has received an Internet Protocol (IP) address in the subnet announced by the UPF 511) to access the IP Multimedia Subsystem (IMS) or another DN.

[0202] During the PDU session establishment procedure for the UE 501, the UE will provide a request to the DU 503. As part of the PDU session establishment, the core CP 509 (e.g., the SMF) will select a UPF for the PDU session. For example, the core CP 509 can select the UPF 511. After the UPF is selected by the core CP 509, the CU-CP 505 selects the CU-UP for the PDU session. For example, the CU-CP 505 selects the CU-UP of the AUPF 507. The AUPF 507 and the UPF 511 may not be very close to each other. In this way, any communication between these functions may introduce latency / delay.

[0203] In some communication systems, the CU-CP receives information from the core network (CN) in a message (such as the N2 PDU session resource setup request (N2 PDU Session Resource Setup Request)). This request may include at least one of the following: N2 session management (SM) information, information on the UL NG-U UPTNL (e.g., uplink user plane transport network layer IE) included in the PDU session resource setup request transmission IE, (end-to-end encrypted) NAS messages (e.g., PDU session ID, N1 SM container (PDU session establishment acceptance)), or CN-assisted RAN parameter adjustment. The terms "information on the UL UP TNL", "information on the UL NG-U UP TNL", "UL UP TNL information", and "UL NG-U UP TNL information" may be used interchangeably.

[0204] As part of the N2 SM information, for each PDU session, the NG-RAN node (e.g., gNB-CU-CP and gNB-CU-UP) will store the UL NG-U UP TNL IE and use the UL NG-U UP TNL IE as the uplink termination point for user plane data to the CN (e.g., the UPF).

[0205] However, this communication system does not specify how the gNB-CU-CP should select for each PDU session: 1) a gNB-CU-UP instance collocated with a UPF instance (e.g., deployed on the same container as a service (CaaS) instance, but in different servers at the same site), or 2) a combined AUPF instance selected by the SMF, or 3) a femto gateway (GW). A femto GW is a small, low-power cellular base station that is typically designed for use in homes or small businesses. Selecting the most appropriate gNB-CU-CP / AUPF / femto-GW by the gNB-CU-CP will help reduce the latency of the PDU session and improve the user experience.

[0206] Figure 6 A schematic representation of the collocation of a RAN centralized unit user plane instance and a user plane function instance within a 5G communication system is shown.

[0207] A UE 601 capable of communicating with a first RAN 603 and a second RAN 605 (e.g., gNB) is provided. Each of the first and second RANs 603, 605 includes a DU 607, a CU-CP 609, and a CU-UP 611, with respective interfaces therebetween. In addition, there is also a core CP 613, a first UPF 615, and a second UPF 617. The core CP 613 has interfaces with the CU-CP 609, the first UPF 615, and the second UPF 617.

[0208] The first UPF 615 and the CU-UP 611 of the first and second RANs 603, 605 are collocated with each other. The first UPF 615 and the CU-UP 611 together may be referred to as an AUPF 619. There is an interface between the first UPF 615 and the CU-UP 611 of the first and second RANs 603, 605.

[0209] The first UPF 615 of the AUPF 619 is interfaced with a local PDN domain 621. The second UPF 617 is interfaced with a central PDN domain 623. There is also an interface between the first UPF 615 and the second UPF 617.

[0210] The ratio of the UPF instance to the CU-UP instance within the AUPF is not necessarily 1:2 (e.g., as shown in Figure 6 ), or 1:1. In other examples, "N" UPF instances may be collocated with "M" CU-UP NF instances.

[0211] Below in Figure 7The selection of the AUPF for an ongoing PDU session and the resulting benefits for the co-located UPF and CU-UP scenario are shown.

[0212] Figure 7 An example signaling and operation diagram for PDU session establishment in a 5G communication system is shown.

[0213] At S701, the UE provides a request for PDU session establishment to the gNB. In particular, the request is provided to the gNB-CU-CP (or CU-CP) of the gNB. It should be understood that in the following examples, the terms "RAN-CU" and "gNB-CU" can be used interchangeably. The same is true for RAN-DU and gNB-DU.

[0214] The request can be provided in an uplink (UL) radio resource control (RRC) message. The request can include non-access stratum (NAS) session management (SM) information associated with the UE. NAS SM supports handling session management between the UE and the SMF. NAS SM supports user plane PDU session establishment, modification, and release. NAS SM is transmitted via the gNB and is transparent to the gNB.

[0215] The gNB-CU-CP can be referred to as an instance of the gNB-CU-CP, an instance of the gNB-CU-CP, or an instance for performing the gNB-CU-CP function. In the following examples, these terms can be used interchangeably. The same interchangeable terms can be used for other network functions, such as, for example, gNB-CU-UP, gNB-DU, etc. An instance of a network function can be the result of a software program running on a limited number of computing nodes (e.g., servers or virtual machines). For example, for a containerized network function (CNF product), an instance is identified by a Kubernetes (K8s) "Namespace", which contains multiple "K8s Pods". Inside each "K8s Pod" there is an instance of the CNF component with its own IP address. A CNF instance (e.g., a K8s "Namespace") is the result of applying the K8s "kubectl helm install -n $namespace" command on the K8s control plane (master node) and causes "pods" to be deployed on the K8s worker / edge nodes.

[0216] At S702, the gNB provides the request to the AMF of the 5G core. The AMF is part of the core control plane. The request can be provided in a UL NAS message to the AMF on the N2 interface. The request can include the NAS SM provided by the UE.

[0217] At S703, the AMF performs the selection of the SMF or the combined SMF / Service PDN GW control plane (SPGW-C). The selection of the SMF or SMF / SPGW-C can be based on a request received by the AMF and / or the result of consulting the NRF (Network Repository Function). The SMF, SMF / SPGW-C, and NRF are also part of the 5G Core and Core CP.

[0218] At S704, the AMF provides a PDU session creation request to the selected SMF. The PDU session creation request is provided via a service-based interface.

[0219] At S705, the SMF (or combined SMF / SPGW-C) provides a response to the AMF. The response can be a PDU session creation response message.

[0220] At S706, the SMF (or combined SMF / SPGW-C) selects an AUPF instance and / or a UPF instance. The SMF also sets the Quality of Service (QoS) information for the PDU session. After establishing the PDU session, the SMF selects a suitable AUPF instance and / or UPF instance based on at least one of the following: S-NSSAI (Single Network Slice Selection Assistance Information), DNN (Data Network Name), or Tracking Area (TA).

[0221] At S707, the SMF provides a request associated with session establishment to the selected AUPF or UPF instance (selected by the SMF). The request is a session establishment request message on the N4 interface. The request can include information associated with the PDU configuration.

[0222] At S708, the AUPF or UPF receives information associated with the PDU configuration. The AUPF or UPF allocates UL NG-U (Next Generation User Plane) Transport Network Layer (TNL) information (which can also be referred to as information related to UL UP TNL) to the PDU session. The UL NG-U TNL information can include a GTP (GPRS Tunneling Protocol) Fully Qualified Tunnel Endpoint Identifier (F-TEID), which includes an IP address and a TEID. In other examples, the AUPF or UPF allocates a Multiprotocol Label Switching (MPLS) Segment Routing label / MPLS label associated with the AUPF or UPF or a Segment Routing (e.g., SRv6) Segment Identifier associated with the AUPF or UPF as the UL NG-U TNL information.

[0223] At S709, the AUPF or UPF provides a response associated with session establishment to the SMF or SMF / SPGW-C. This response can be a session establishment response message on the N4 interface. The response includes the allocated UL NG-U TNL information, which can carry information (such as a "flag") that can be used by the gNB-CU-CP at S713 to identify the UPF corresponding to the AUPF or the co-located CU-UP and UPF.

[0224] At S710, the SMF or SMF / SPGW-C provides the UL NG-U TNL information to the AMF.

[0225] At S711, the AMF provides an acknowledgement of the received UL NG-U TNL information to the SMF.

[0226] At S712, the AMF provides a response message to the gNB-CU-CP. This response message can be a PDU session establishment response sent on the N2 interface. The response message includes information containing at least one of the following: UL NG-U TNL information, QoS information, or NAS SM. In this way, the gNB-CU-CP can obtain (for the UE) the UL NG-U TNL information, where the UL NG-U TNL information is associated with the user plane traffic of the UE. The UL NG-U TNL information can be used for the PDU session of the UE.

[0227] At S713, the gNB-CU-CP uses the information included in the request message from the AMF to modify its default gNB-CU-UP selection criteria.

[0228] The gNB-CU-CP can determine, based on this information, that the UPF selected by the SMF is associated with the AUPF or UPF. In some examples, the gNB-CU-CP determines, based on this information, which UPF / AUPF has been selected. Further, the gNB-CU-CP selects the gNB-CU-UP associated with the UPF selected by the SMF. In this example, the gNB-CU-UP is associated with the UPF because they are co-located. Examples of co-location include: in the same city, in the same data center, in the same computer rack, or in the same computing node or virtual machine.

[0229] At S714, the gNB-CU-CP provides a request message to the selected gNB-CU-UP. This request message can be a bearer context establishment request message on the E1 interface. The request message can include information containing at least one of the following: UL NG-U TNL information, or PDCPu / SDAP configuration.

[0230] At S715, gNB-CU-UP uses the information provided in S714 to set the PDCP and / or SDAP configuration for the PDU session.

[0231] gNB-CU-UP performs UL F1u TEID selection. F1u is the user plane interface between the DU and the CU-UP.

[0232] gNB-CU-UP sets the downlink (DL) NG-U TEID to the AUPF flag, which can be used by the SMF at S726 to confirm that gNB-CU-UP has been correctly configured as part of the AUPF or configured as co-located CU-UP and UPF.

[0233] At S716, gNB-CU-UP provides a bearer context establishment response to gNB-CU-CP, where the response includes at least one of the following: UL NG-U TEID, QoS information, or NAS SM. The response may also indicate that the DL NG-U TEID has been set to the AUPF flag.

[0234] At S717, gNB-CU-CP provides a UE context establishment request to gNB-DU, where the request includes at least one of the following: UL NG-U TNL information, or DRB configuration.

[0235] At S718, gNB-DU determines the data radio bearer configuration based on the request. gNB-DU performs DL F1u TEID selection based on the request. The selected DL F1u TEID is associated with the data radio bearer.

[0236] At S719, gNB-DU provides a UE context establishment response to gNB-CU-CP, where the response includes the selected DL F1u TEID.

[0237] At S720, gNB-CU-CP provides a bearer context modification request to gNB-CU-UP / AUPF, where the request includes the selected DL F1u TEID.

[0238] At S721, gNB-CU-UP / AUPF provides a bearer context modification response message to gNB-CU-CP.

[0239] At S722, gNB-CU-CP provides an RRC reconfiguration message to the UE.

[0240] At S723, the UE provides an RRC reconfiguration complete message to gNB-CU-CP.

[0241] At S724, the gNB-CU-CP provides a PDU session establishment response to the AMF, where the response includes the DL F1u TEID.

[0242] At S725, the AMF provides a PDU session update request to the SMF. The PDU session update request may indicate the DL NGu TEID.

[0243] At S726, the AUPF confirmation is performed by the SMF.

[0244] At S727, the SMF provides a session modification request to the UPF / AUPF. The session modification request may indicate the DL NGu TEID.

[0245] At S728, the UPF / AUPF provides a session modification response to the SMF.

[0246] At S729, the SMF provides a PDU session update response to the AMF.

[0247] Thus, in some examples, the SMF selects an AUPF or UPF instance for the PDU session being established. Further, information related to the selection of the UPF instance is provided to the gNB / RAN. Then, the gNB / RAN selects the RAN-CU-UP for the PDU session.

[0248] However, in some examples (e.g., as shown in Figure 7 ), the RAN-CU-CP is collocated with the UPF. Thus, if the RAN-CU-CP selected by the gNB is associated with the UPF already selected by the SMF, this is beneficial for reasons such as latency.

[0249] As shown in the above Figure 7 example, the RAN-CU-CP receives information related to the UPF selection by the SMF. Further, the RAN-CU-CP determines and selects the RAN-CU-UP collocated with the AUPF or UPF selected by the SMF.

[0250] When there is an integrated RAN-CU-UP and UPF (forming an AUPF), Figure 7 the process is equally applicable. For the AUPF with an integrated RAN-CU-UP and UPF, the UPF and the RAN-CU-UP are associated with each other.

[0251] During PDU session establishment, the SMF selects a UPF (e.g., as shown in Figure 7 S706) based on information such as network slice, data network name (DNN), tracking area identifier (TAI), etc.

[0252] An instance of the UPF within the AUPF (which can be implemented as a UPF component instance (e.g., a UPF pod)) can have alternative configurations for how to manage downlink packets / frames received from a data network. For example, an instance of the UPF can:

[0253] - Generate N3 GTP-encapsulated traffic for downlink transmission to an external gNB-CU-UP. For example, via a data center gateway and / or a mobile backhaul network; or

[0254] - Provide unencapsulated traffic to a co-located CU-UP instance (e.g., a co-located K8s Pod) for SDAP / PDCP processing; or

[0255] - Perform SDAP and / or PDCP processing and send F1-U GTP-encapsulated traffic to the DU function in an adjacent network function component (NFC). The adjacent network function component is of the "Pod" type (for CNF) or virtual machine (VM) type (for virtualized NF (VNF)). The NFC is a "product" (program), and an NFC instance is the result of its installation / instantiation on a computer or VM; or

[0256] - Perform SDAP and / or PDCP processing and send F1-U GTP-encapsulated traffic to an external gNB-DU. For example, via a data center gateway and a mobile fronthaul / midhaul network.

[0257] In some examples, the user plane NF instance receives first information related to the UL UP TNL (e.g., from the CN) and copies at least a portion of the first information into second information related to the downlink (DL) UP TNL. For example, if the CU-UP determines that the Internet Protocol (IP) address of the first information (e.g., UL N3 GTP F-TEID) for uplink transmission is not routable, the CU-UP selects the same IP address for the second information associated with the DL NG-U UP TNL (e.g., DL N3 GTP F-TEID at the gNB-CU-UP). In this context, the term "not routable" may mean that there is no IP route in the routing information base (RIB) (which is included in the first information) that would be used to reach the IP destination address (subnet). Alternatively or additionally, in other examples, the same TEID is used, the same UDP port is used, the same node MPLS label (representing the AUPF in the N6 data network) is used, etc. In some examples, the gNB-DU will select the same IP address for the third information related to the DL F1-U UP TNL (e.g., DL F1-U GTP F-TEID at the gNB-DU). F1-U is the user plane interface between the CU and DU of the RAN.

[0258] When the CU-UP receives non-routable (or unreachable) first information related to the UL UP TNL, the CU-UP may disable (or enable) SDAP and / or PDCP processing at the CU-UP. In the case of disabling SDAP and / or PDCP processing during SDAP and / or PDCP processing, DL GTP-U traffic is provided to (or passed to) the gNB-DU. The manner of receiving unreachable first information related to the UL UP TNL (e.g., implicitly) indicates that another entity (e.g., the AUPF) is already performing SDAP and / or PDCP processing. Since this other entity is already performing SDAP and / or PDCP processing, the CU-CP does not need to perform such processing and thus disables the processing. In some examples, it may be assumed that SDAP and / or PDCP are disabled (e.g., by default), and the CU-CP enables SDAP and / or PDCP processing accordingly. In some examples where the AUPF is performing SDAP and / or PDCP processing, the AUPF may send PDCP compressed and encrypted traffic to the DL NG-U UP TNL address, which is the TNL address of the gNB-DU. The DL GTP F-TEID may be assigned by the gNB-DU (instead of the RAN-CU-UP).

[0259] In this way, in some examples, at least a portion of the received (first) information related to UL UP TNL is used to disable (or enable) PDCP processing. In some examples, at least a portion of the received (first) information related to UL UP TNL is used to disable (or enable) SDAP processing.

[0260] Some examples may relate to scenarios of dual connectivity (DC) or multi-connectivity (MC) of a single user equipment to multiple RAN nodes. For a RAN bearer terminated at the master node (MN) (e.g., with PDCP and SDAP processing at the MN), the control plane of the MN (e.g., the RAN-CU-CP of the MN, which can be labeled as MN-CU-CP if it is different from the SN-CU-CP) obtains the DL UP TNL information from the secondary node. This allows the CP of the MN to forward the bearer fully or partially (if the bearer is split) to the SN (-CU-UP). The DL UP TNL information is obtained because the RAN-CU-CP (4G RAN-CP) controls both the MN-CU-UP (4G MN-UP) and the SN-CU-UP (4G SN-UP), or because the MN-CU-CP (4G MN-CP) obtains it from the SN-CU-CP (4G SN-CP). For a bearer terminated at the SN, the RAN-CU-CP (4G RAN-CP) obtains the UL TNL information from the MN-CU-UP (4G MN-UP). The selection of the SN (e.g., SN-CU-UP or SN-UP) occurs after the selection at the MN (including MN-CU-UP or MN-UP). Therefore, it may be beneficial for the SN to perform an "intelligent" SN-CU-UP (4G SN-UP) selection. For example, selecting an SN-CU-UP (4G SN-UP) that is collocated or integrated / folded with the MN-CU-UP (4G MN-UP). In this context, "folded" can be the same NF instance, or the same NF component instance (e.g., the same K8s Pod). For a bearer terminated at the MN, it may be beneficial for the RAN-CU-CP (4G RAN-CP) or the SN-CU-CP (4G SN-CP) to select the SN-CU-UP (4G SN-UP) based on the UL UP TNL information allocated by the MN-CU-UP (4G MN-UP). When the bearer is moved to the SN / becomes terminated at the SN, it may be beneficial for the RAN-CU-CP (4G RAN-CP) or the MN-CU-CP (4G MN-CP) to select the MN-CU-UP (4G MN-UP) based on the UL UP TNL information allocated by the SN-CU-UP (4G SN-UP), resulting in the MN-CU-UP (4G MN-UP) being collocated or integrated / folded with the SN-CU-UP (4G SN-UP).

[0261] In some examples, a RAN node (e.g., a CU-UP collocated or collapsed with a UPF) receives uplink F1-UP DCP traffic and does not send uplink N3 GTP-U traffic, but connects the UE to a DN, another UE, or a multi-access edge computing (MEC) server.

[0262] In some examples, a RAN node (e.g., a DU, a CU-UP, and a UPF) receives uplink RLC-MAC traffic from a radio unit (RU) and does not send uplink F1-U GTP-U traffic, but connects the UE to a DN, another UE, or an MEC server.

[0263] In some examples, a CN node (e.g., a gNB-CU-UP and a UPF) receives downlink data traffic (e.g., from SGi / N6) and sends downlink PDCP traffic to a gNB-DU via GTP-U.

[0264] In some examples, a CN node (e.g., a gNB-DU, a gNB-CU-UP, and a UPF) receives downlink data traffic (e.g., from Sgi / N6) and sends downlink RLC / MAC traffic directly to an RU.

[0265] One or more of the above examples have the following advantages: in some communication systems, when a UPF collocated with a RAN node or a deeply combined AUPF is introduced, the 3GPP N4, N2, and E1 protocols are not modified. In this way, the communication system cannot benefit from the UPF collocated with the RAN node or the deeply combined AUPF.

[0266] The UPF passes its identity / identification and whether it performs new functions (e.g., SDAP / PDCP) as an indication (e.g., an implicit indication) to the RAN node through an unmodified protocol. Therefore, eNodeBs, gNodeBs, and 6GnodeBs can be developed to include collocated or deeply integrated UPF functions without any modification to the 5G core. This can accelerate the introduction of advanced 5G packets and 6G for RUs, DUs, CU-CPs, and AUPFs.

[0267] One or more of the above examples can be applied to modernize existing E-UTRAN and NG-RAN (e.g., as an incentive for containerizing them) and introduce low-latency UE-to-UE and UE-to-MEC services that require highly distributed UPFs at the far edge.

[0268] When there are co-located or collocated CU-UP and UPF, one or more examples can also reduce the latency of a PDU session because the CU-UP is selected based on the information received from the 5GC, thus selecting the best instance of RAN-CU-UP. For example, the latency of data traffic to another UE or to the DN of a UPF that is attached (via N6) to an AUPF or co-located with gNB-DU-UP can be reduced. For example, a CU-UP that is co-located or integrated with the UPF selected by the 5GC for the PDU session is selected. Since the path for communication is shorter, the latency can be reduced.

[0269] Figure 8 An example method flow executed by a device is shown. In some examples, the device may be configured to provide a control plane entity of a radio access network. For example, the device may be configured to perform at least some functions of a control plane entity of a radio access network. For example, the device may be configured to operate as a control plane entity of a radio access network. In alternative examples, the device may be configured to perform: at least some functions of a control plane entity of a radio access network, at least some functions of one or more other functions of a radio access network, and / or at least some functions of one or more functions of a core network. For example, device 200 may be configured to operate as: a control plane entity of a radio access network, one or more other functions of a radio access network; and / or one or more functions of a core network.

[0270] In some examples, the device includes components for a control plane entity to perform Figure 8 the features. The device may provide a control plane entity of a radio access network. In some examples, the device includes at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the device to perform Figure 8 the features.

[0271] The control plane entity may be an instance of CU-CP in a 5G RAN. The control plane entity may be an instance of the eNodeB control plane in a 4G evolved universal terrestrial radio access network. The control plane entity may be an instance in a 6G network.

[0272] In S801, the method includes obtaining information about the uplink user plane transport network layer for a user equipment, where the information is associated with the user plane traffic of the user equipment.

[0273] In S803, the method includes selecting, based on the information, an instance of a user plane network function for performing a data radio bearer to the user equipment.

[0274] In S805, the method includes communicating with the instance of the user plane network function for performing.

[0275] Figure 9 shows a schematic representation of non - volatile storage media 900a (e.g., Blu - ray Disc (BD), computer disc (CD), or digital versatile disc (DVD)) and 900b (e.g., flash memory, solid - state drive (SSD), universal serial bus (USB) memory stick) that store instructions and / or parameters 902 which, when executed by a processor, allow the processor to perform Figure 8 one or more steps of the method).

[0276] Note that while the above describes example embodiments, several variations and modifications can be made to the disclosed solutions without departing from the scope of the present disclosure.

[0277] Accordingly, the examples can vary within the scope of the appended claims. In general, some example embodiments can be implemented using hardware or dedicated circuitry, software, logic, or any combination thereof. For example, some aspects can be implemented using hardware, while other aspects can be implemented using firmware or software executable by a controller, microprocessor, or other computing device, but the embodiments are not limited thereto. Although the various embodiments can be illustrated and described as block diagrams, flowcharts, or using some other graphical representation, it is well understood that, by way of non - limiting and illustrative example, the blocks, devices, systems, techniques, or methods described herein can be implemented using hardware, software, firmware, dedicated circuitry or logic, general - purpose hardware or controllers, or other computing devices, or some combination thereof.

[0278] The examples can be implemented by computer software stored in a memory and executable by at least one data processor of the entities involved, or by hardware, or by a combination of software and hardware. Further, in this regard, it should be noted that any process can represent program steps, or interconnected logic circuits, blocks, and functions, or a combination of program steps and logic circuits, blocks, and functions. The software can be stored on a physical medium such as: a storage chip, or a storage block implemented within a processor, magnetic media (such as a hard disk or a floppy disk), and optical media (such as, for example, a DVD and its data variants, a CD).

[0279] As used herein, the term “non - transitory” is a limitation on the medium itself (i.e., tangible, rather than a signal), rather than a limitation on the persistence of data storage (e.g., RAM versus ROM).

[0280] As used herein, "at least one of the following: <list of two or more elements / components>" and "at least one of the following: <list of two or more elements / components>" and similar phrases (where the list of two or more elements / components is joined by "and" or "or") mean at least any one of the elements / components, or at least any two or more of the elements / components, or at least all of the elements / components. Similarly, the phrase "and / or" includes any one of the listed terms and all combinations thereof, including any one of the elements / components, any two or more of the elements / components, and all of the elements / components.

[0281] As used herein, the terms "first X" and "second X" include the options where "first X" is the same as "second X" and where "first X" is different from "second X", unless otherwise specified. These terms are only used to distinguish one element / component from another and do not denote a temporal relationship, unless it is apparent from the disclosure.

[0282] As used herein, the term "or" means a non-exclusive "or", unless otherwise indicated (e.g., by using "otherwise" or "alternatively").

[0283] As used herein, unless explicitly stated, performing the step "in response to A" does not mean that the step is performed immediately after A occurs, but may include one or more intermediate steps. Similarly, performing a step or function "based on A" does not mean that the step or function is performed only based on A, as one or more additional conditions may be included.

[0284] The memory can be of any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as semiconductor-based storage devices, magnetic storage devices and systems, optical storage devices and systems, fixed memory, and removable memory. The data processor can be of any type suitable for the local technical environment and, by way of non-limiting example, can include one or more of the following: general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), gate-level circuits, and processors based on multi-core processor architectures.

[0285] In some examples, the term "component for..." or "component configured to perform..." (or similar terms) can be any component suitable for performing that feature. A "component" can be configured to perform one or more of the previously described functions and / or method steps. For example, a "component" can include one or more of the following: at least one processor, at least one memory, transceiver circuitry, antenna circuitry, etc. It should be understood that these "components" are provided as non-limiting and illustrative examples.

[0286] Alternatively or additionally, some examples can be implemented using circuitry. The circuitry can be configured to perform one or more of the previously described functions and / or method steps. The circuitry can be provided in a base station and / or a communication device.

[0287] As used herein, the term "circuitry" can refer to one or more or all of the following:

[0288] (a) Only hardware circuitry implementations (such as only analog and / or digital circuitry implementations);

[0289] (b) A combination of hardware circuitry and software, such as:

[0290] (i) A combination of analog and / or digital hardware circuitry and software / firmware; and

[0291] (ii) Any part of a hardware processor (including a digital signal processor), software, and memory with the software

[0292] working together to cause a device such as a communication device or a base station to perform the various functions previously described; and

[0293] (c) Hardware circuitry and / or a processor, such as a microprocessor or a part of a microprocessor, that requires software (e.g., firmware) to operate but can be without software when it does not need to operate.

[0294] This definition of "circuitry" applies to the use of the term "component" herein. As another example, as used herein, the term "circuitry" also encompasses implementations of only hardware circuitry or a processor (or processors) or a part of a hardware circuitry or a processor along with its accompanying software and / or firmware. The term "circuitry" also encompasses, for example, integrated devices. The term "circuitry" also encompasses (e.g., and if applicable to a particular claim element) a baseband integrated circuit or a processor integrated circuit for a mobile device, or a similar integrated circuit in a server, a cellular network device, or other computing or network devices.

[0295] The foregoing description has provided a complete and informative description of some embodiments by way of non-limiting and illustrative examples. However, various modifications and adaptations may become apparent to those skilled in the relevant art upon reading the foregoing description in conjunction with the drawings and the claims. However, all such and similar modifications of the teachings will still fall within the scope of the present disclosure. For example, further example embodiments may be provided by a combination of any two or more of the various example embodiments described above.

Claims

1. An apparatus configured to provide a control plane entity of a radio access network, the apparatus comprising means for the control plane entity to perform the following operations: Obtaining information of an uplink user plane transmission network layer for a user equipment, wherein: The information is associated with a user plane service of the user equipment; selecting, based on the information, an instance of a user plane network function for performing a data radio bearer to the user equipment; as well as Communicating with the instance for performing the user plane network function.

2. The device according to claim 1, wherein: The instance for executing the user plane network function is one of the following: a network function instance, or a network function component instance.

3. The device according to claim 1 or 2, wherein: The user plane network function is a gNodeB centralized unit user plane or an eNodeB user plane.

4. The device according to any one of claims 1 to 3, wherein: The instance for performing the user plane function is within one of a primary node or a secondary node of the radio access network, Therein, the data radio access bearer is terminated and the user equipment is connected to at least both the primary node and the secondary node of the radio access network.

5. The device according to any one of claims 1 to 4, wherein: The information of the uplink user plane transport network layer includes at least one of: a fully qualified tunnel endpoint identifier associated with a user plane function, a multi-protocol label switching label associated with a user plane function, or a segment routing segment identifier associated with a user plane function.

6. A method comprising: Obtaining, for a user equipment, information of an uplink user plane transmission network layer, wherein the information is associated with a user plane service of the user equipment; selecting, based on the information, an instance of a user plane network function for performing a data radio bearer to the user equipment; and Communicating with the instance for performing the user plane network function.

7. The method according to claim 6, wherein: The instance for executing the user plane network function is one of the following: a network function instance, or a network function component instance.

8. The method according to claim 6 or 7, wherein: The user plane network function is a gNodeB centralized unit user plane or an eNodeB user plane.

9. The method according to any one of claims 6 to 8, wherein: The instance for performing the user plane function is within one of a primary node or a secondary node of the radio access network, Therein, the data radio access bearer is terminated and the user equipment is connected to at least both the primary node and the secondary node of the radio access network.

10. The method according to any one of claims 6 to 9, wherein: The information of the uplink user plane transport network layer includes at least one of: a fully qualified tunnel endpoint identifier associated with a user plane function, a multi-protocol label switching label associated with a user plane function, or a segment routing segment identifier associated with a user plane function.

11. A computer program comprising instructions which, when executed by a device, cause the device to at least perform the following operations: Obtaining information of an uplink user plane transmission network layer for a user equipment, wherein: The information is associated with a user plane service of the user equipment; selecting, based on the information, an instance of a user plane network function for performing a data radio bearer to the user equipment; as well as Communicating with the instance for performing the user plane network function.

Images