Extended reality user plane design

Abstract

According to some embodiments, a method is performed by a first network node for operation where the new radio (NR) user plane supports non-homogenous deployment of user plane additions. The method comprises constructing a General Packet Radio Service (GPRS) Tunnelling Protocol User Plane (GTP-U) packet comprising an Extension Header comprising a Protocol Data Unit (PDU) Set Container. The PDU Set Container comprises an indication that a second network node may ignore the PDU Set Container when the second network node does not support PDU Set functionality. The method further comprises transmitting the GTP-U packet to the second network node.

Description

Extended Reality User Plane DesignTECHNICAL FIELD

[0001] The present disclosure generally relates to communication networks, and more specifically to extended reality (XR) user plane design.BACKGROUND

[0002] Third Generation Partnership Project (3 GPP) specifications include application protocols specifying open network interfaces (such as Next Generation Application Protocol (NGAP), SI Application Protocol (S1AP), Xn Application Protocol (XnAP), etc.) and a mechanism by which the sender can control the receiver’s behavior when “comprehension” is “critical” to control.

[0003] Each elementary procedure (EP) and each information element (IE) contained within a message of an elementary procedure is assigned with a "criticality." The three criticalities defined are "reject," "ignore" and "ignore and notify." Only "reject" and "ignore" have been used throughout third generation (3G), fourth generation (4G) and fifth generation (5G) networks.

[0004] Criticality “reject” is only used when the receiving node cannot continue with the execution of the requested function. When adding functions to existing procedures, in most cases criticality “ignore” is assigned to new IES. Also the "ignore and notify" is not used in the 3GPP specifications. Therefore, the use of criticalities can be limiting.

[0005] Over 3GPP user plane, how to deal with unknown data packages is not clear. In, e.g., 3GPP TS 38.415 chapter 5.6 “Handling of unknown, unforeseen and erroneous protocol data,” the specification is empty. There are certain requirements on interworking with protocol entities that have not implemented protocol additions in a way that a receiving node not having implemented protocol additions “ignore” those additions while executing functions related to legacy protocol information and not discard the whole user plane protocol data unit (PDU).

[0006] 3GPP is also working on standardizing extended reality (XR) applications. For example, 3GPP has discussed the issue of non-homogeneous deployments of next generation radio access network (NG-RAN) nodes supporting PDU Set based handling and agreed to the requirements below (CR S2-2308246 vs. TS 23.501.5.7.7.1 GeneralPDU Set QoS Parameters are used to support PDU Set based QoS handling in the NG-RAN. At least one PDU Set QoS Parameter shall be sent to the NG-RAN to enable PDU Set based QoS handling.The followings are the PDU Set specific QoS characteristics:1. PDU Set Delay Budget (PSDB).2. PDU Set Error Rate (PSER).3. PDU Set Integrated Handling Information (PSIHI).For a QoS Flow supporting PDU Set based QoS handling, the QoS Profile includes the PDU Set QoS Parameters described in this clause (see clause 5.7.1.2). The PCF determines the PDU Set QoS Parameters based on information provided by AF and / or local configuration. The PDU Set QoS parameters are sent to the SMF as part of PCC rule. The SMF sends them to NG-RAN as part of the QoS Profile.If the NG-RAN receives PDU Set QoS Parameters and supports them, it applies PDU Set QoS Parameters as described in this clause.5.37.5.x Non-homogenous support of PDU set based handling in NG-RANBy sending at least one PDU Set QoS parameter to the NG-RAN, the SMF requests the NG- RAN to activate PDU Set QoS handling for a given QoS flow and the NG-RAN provides the SMF with an indication of whether the PDU Set QoS parameter is accepted or not. At NG-RAN Xn handover and N2 handover, the target NG-RAN provides to the SMF with an indication of whether the target NG-RAN node supports PDU Set based handling, as specified in TS 38.413. Based on the NG-RAN indications, the SMF configures the PSA UPF to activate / deactivate the PDU Set identification and marking.In the case where the PSA UPF identifies and marks PDUs with PDU Set information in GTP-U header it shall start doing so from a complete PDU Set.

[0007] The rationale of the change request (CR) is that the “PDU set based QoS handling” feature needs not to be homogenously supported in the network. The session management function (SMF) is informed whether an NG-RAN node supports the PDU Set based Quality of Service (QoS) handling feature and only if NG-RAN supports the feature, the SMF triggers activation- of PDU Set identification in the user plane function (UPF), because this feature consumes processing capacity and should only be used when the NG-RAN actually uses the information.

[0008] The New Radio (NR) User Plane Protocol is located in the user plane of the radio network layer (RNL) above the transport network layer (TNL) of the interface.

[0009] The General Packet Radio Service (GPRS) Tunnelling Protocol User Plane (GTP-U) defines two “GTP-U Container” GTP-U Extension Header. One is “NR RAN Container”, defined for X2-U, Xn-U and Fl-U user plane interfaces, within NG-RAN and, for Evolved UniversalTerrestrial Radio Access (E-UTRAN) New Radio - Dual Connectivity (EN-DC), within E- UTRAN. The content of the “NR RAN Container” is specified in 3GPP TS 38.425.

[0010] Another is “PDU Session Container”, defined for N3 / N9 user plane interfaces, between NG-RAN and User Plane Function (UPF), or between two UPFs and for N3mb / N19mb user plane interfaces between the MB-UPF and NG-RAN, or between the MB-UPF and UPF. The content of the “PDU Session Container” is specified in 3GPP TS 38.415.

[0011] During inter-NG-RAN node mobility from a “PDU set based QoS handling” supporting NG-RAN node to a non-supporting NG-RAN node, in the course of data forwarding, the source node may or may not know whether the target NG-RAN node supports “PDU set based QoS handling.” If the source node does know (based on not receiving support information from the target NG-RAN node), the source node could modify the content of the GTP-U “PDU Session Container” extension container to strip off non-supported protocol information before forwarding the user plane packet to the target node, however, this requires additional and costly processing capacities because the GTP-U “PDU Session Container” extension container is specified in 3GPP TS 29.281, while the content of the “PDU Session Container” is specified in 3GPP TS 38.415.

[0012] For non-aggregated NG-RAN deployment, as specified in 3GPP TS 38.401 , user plane data between the gNB-CU and the gNB-DU is transported via the Fl -U interface, which is based on GTP-U with user plane protocol information included within the GTP-U “NR RAN container” extension container, as specified in 3GPP TS 29.281, the content of the NR RAN container” is specified in 3GPP TS 38.425. The GTP-U “NR RAN container” extension container is also used on the Xn-U interface for multiple radio access technology (RAT) dual connectivity (MR-DC).

[0013] With this structure, when new features are introduced, the impacts on the X2-U, Xn- U and Fl-U interface are introduced to the “NR RAN Container.” The impacts on N3 / N9 interface are introduced to the “PDU Session Container.” See 3GPP TS 29.281.

[0014] There currently exist certain challenges. For example, the XR feature has introduced the PDU Set concept. The User Plane should contain XR PDU Set related parameters defined as “PDU Set Information” in 3GPP. The PDU Set Information UP includes the following: PDU Set Sequence Number (the PDU Set Identifier); Indication of End PDU of the PDU Set (Optional); PDU Sequence Number within a PDU Set (Optional); PDU Set Size in bytes; and PDU Set Importance, which identifies the relative importance of a PDU Set compared to other PDU Sets within a QoS Flow (Optional).

[0015] 3GPP also specifies that XR traffic should support non-homogenous support of PDU set based handling in NG-RAN.

[0016] Thus, the XR User Plane has to be designed in a way that a node receiving PDU Set Information within the user plane packets is able to cope with protocol additions without being forced to discard the whole User Plane packet, so that data forwarding from source to target NG- RAN node is possible when the source node is supporting “PDU set based QoS handling” while the target is not.

[0017] During dual connectivity operation, the deployment should be homogenous. However, if non-homogenous deployment is allowed, the XR user plane has to be designed to make it work.

[0018] Currently neither the PDU Session User Plane protocol (TS 38.415) nor the NR User Plane protocol (TS 38.425) support non-homogenous deployments of (user plane) protocol additions, as requested in XR.

[0019] As used herein, supporting node refers the node that supports XR service. Non supporting node refers to the node that does not support XR service.SUMMARY

[0020] As described above, certain challenges currently exist with extended reality (XR) user plane design for non-homogenous deployments. Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. For example, particular embodiments support the non-homogenous XR User Plane. The protocol data unit (PDU) Set related information in the user plane is defined in a backwards compatible way, so that when PDU Set related information is sent to the node that does not understand this set of parameters, the node may ignore the set and proceed as the node is handling the normal New Radio (NR) data payload (i.e., without XR feature). In the non-homogenous dual connectivity deployment, the PDU Set related information may be removed in the user plane when the next generation radio access network (NG-RAN) node or the corresponding nodes does not support XR feature.

[0021] According to some embodiments, a method is performed by a first network node for operation where the NR user plane supports non-homogenous deployment of user plane additions. The method comprises constructing a General Packet Radio Service (GPRS) Tunnelling Protocol User Plane (GTP-U) packet comprising an Extension Header comprising a PDU Set Container. The PDU Set Container comprises an indication that a second network node may ignore the PDUSet Container when the second network node does not support PDU Set functionality. The method further comprises transmitting the GTP-U packet to the second network node.

[0022] In particular embodiments, the indication is part of the Next Extension Header Type field of the GTP-U Extension Header. The indication may comprise two bits of the Next Extension Header Type field of the GTP-U Extension Header.

[0023] In particular embodiments, the method further comprises using GTP-U Extension Header PDU Session Container for data payload transfer.

[0024] In particular embodiments, the first network node comprises a radio access network (RAN) node and the second network node comprises one of a RAN node and a User Plane Function (UPF) node.

[0025] According to some embodiments, a method is performed by a first network node for operation where the NR user plane supports non-homogenous deployment of user plane addition. The method comprises receiving, from a second network node, a GTP-U packet comprising an Extension Header comprising a PDU Set Container. The PDU Set Container comprises an indication that the first network node may ignore the PDU Set Container when the first network node does not support PDU Set functionality. Based on the indication, the method further comprises: forwarding the GTP-U packet with the PDU Set Container to a third network node; or forwarding the GTP-U packet without the PDU Set Container to the third network node.

[0026] In particular embodiments, the indication is part of the Next Extension Header Type field of the GTP-U Extension Header. The indication may comprise two bits of the Next Extension Header Type field of the GTP-U Extension Header.

[0027] In particular embodiments, the method further comprises using GTP-U Extension Header PDU Session Container for data payload transfer.

[0028] In particular embodiments, the first network node comprises a radio access network (RAN) node and the second network node comprises a RAN node.

[0029] According to some embodiments, a method is performed by a gNB central unit control plane (gNB-CU-CP) first network node for operation where the NR user plane supports non- homogenous deployment of user plane additions. The method comprises determining that a second network node does not support PDU Set functionality and transmitting, to a gNB central unit user plane (gNB-CU-UP) associated with the gNB-CU-CP, an indication to remove PDU Set associated information from a packet before transmitting the packet to the second network node.

[0030] In particular embodiments, the PDU Set associated information comprises a GTP-U Extension Header comprising a PDU Set Container.

[0031] In particular embodiments, the PDU Set associated information comprises a GTP-U Extension Header comprising a PDU Session Container.

[0032] In particular embodiments, the first network node is operating in dual connectivity and the second network node comprises a secondary network node.

[0033] According to some embodiments, a method is performed by a gNB-CU-UP first network node for operation where the NR user plane supports non-homogenous deployment of user plane additions. The method comprises receiving, from a gNB-CU-CP associated with the gNB-CU-UP, an indication to remove PDU Set associated information from a packet before transmitting the packet to the second network node and transmitting the packet with the removed PDU Set associated information to the second network node.

[0034] In particular embodiments, the PDU Set associated information comprises a GTP-U Extension Header comprising a PDU Set Container.

[0035] In particular embodiments, the PDU Set associated information comprises a GTP-U Extension Header comprising a PDU Session Container.

[0036] In particular embodiments, the first network node is operating in dual connectivity and the second network node comprises a secondary network node.

[0037] According to some embodiments, a network node comprises processing circuitry operable to perform any of the network node methods described above.

[0038] Also disclosed is a computer program product comprising a non-transitory computer readable medium storing computer readable program code, the computer readable program code operable, when executed by processing circuitry to perform any of the methods performed by the network nodes described above.

[0039] Certain embodiments may provide one or more of the following technical advantages. For example, particular embodiments support XR PDU Set handling in User Plane for non- homogeneous RAN deployment and support of XR feature.BRIEF DESCRIPTION OF THE DRAWINGS

[0040] The present disclosure may be best understood by way of example with reference to the following description and accompanying drawings that are used to illustrate embodiments of the present disclosure. In the drawings:Figure 1 illustrates the GTP-U Extension Header “PDU Set Container” byte structure;Figure 2 is a flow diagram illustrating successful transfer of downlink PDU Set Information;Figure 3 is a flow diagram illustrating successful transfer of uplink PDU Set Information;Figure 4 illustrates an example frame format;Figure 5 is a flow diagram illustrating successful transfer of PDU Set RAN Container;Figure 6 illustrates another example frame format;Figure 7 illustrates the respective downlink PDU SESSION INFORMATION frame;Figure 8 illustrates the respective downlink USER DATA frame;Figure 9 shows an example of a communication system, according to certain embodiments;Figure 10 shows a user equipment (UE), according to certain embodiments;Figure 11 shows a network node, according to certain embodiments;Figure 12 is a block diagram of a host, according to certain embodiments;Figure 13 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized;Figure 14 shows a communication diagram of a host communicating via a network node with a UE over a partially wireless connection in accordance with some embodiments;Figure 15 is a flowchart illustrating an example method in a network node, according to certain embodiments;Figure 16 is a flowchart illustrating another example method in a network node, according to certain embodiments;Figure 17 is a flowchart illustrating an example method in a gNB central unit control plane (gNB-CU-CP) network node, according to certain embodiments; andFigure 18 is a flowchart illustrating an example method in a gNB central unit user plane (gNB-CU-UP) network node, according to certain embodiments.DETAILED DESCRIPTION

[0041] As described above, certain challenges currently exist with extended reality (XR) user plane design for non-homogenous deployments. Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. For example, particular embodiments support the non-homogenous XR User Plane. The protocol data unit (PDU) Set related information in the user plane is defined in a backwards compatible way, so that when PDU Set related information is sent to the node that does not understand this set of parameters, the node may ignore the set and proceed as the node is handling the normal New Radio (NR) data payload (i.e., without XR feature). In the non-homogenous dual connectivity deployment, the PDU Set related information may be removed in the user plane when the next generation radio access network (NG-RAN) node or the corresponding nodes does not support XR feature.

[0042] Particular embodiments are described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0043] Particular embodiments ensure that the NR user plane supports non-homogenous deployment. The PDU Set related information is introduced as anew General Packet Radio Service (GPRS) Tunnelling Protocol User Plane (GTP-U) Extension Header, for example defined as “PDU Set Container”.

[0044] 3GPP TS 29.281 defines the new GTP-U Extension Header as “PDU Set Container.” Its content may either be specified in TS 38.415, TS 38.425 or a new specification.

[0045] For a PDU Set Container in TS 38.415, the extension header may be transmitted in a G-PDU over the Xn-U and Fl-U user plane interfaces, within NG-RAN. The extension header may be transmitted in a G-PDUs over the N3 and N9 user plane interfaces, between NG-RAN and User Plane Function (UPF), or between two UPFs.

[0046] The PDU Set Container has a variable length and its content is specified in 3GPP TS 38.415. An example is illustrated in Figure 1.

[0047] The PDU Session User Plane protocol is located in the User Plane of the Radio Network Layer (RNL) above the Transport Network Layer (TNL) of the interface. Each PDU session User Plane protocol instance is associated to one PDU Session.

[0048] In the current specification, the PDU session user plane protocol data is conveyed by GTP-U protocol means, more specifically, by means of the "GTP-U Container" GTP-U Extension Header “PDU Session Container” as defined in 3GPP TS 29.281.

[0049] 3GPP TS 38.415 may include a new chapter to describe the “PDU Set Container.” An example is illustrated below.The PDU Set UP layer expects the following services from the Transport Network Uayer:- Transfer of PDU Set User Plane PDUs.6.1 Elementary procedures6.1.1 Transfer of DE PDU Set Information6.1. 1.1 Successful operationThe purpose of the Transfer of DL PDU Set Information procedure is to send control information elements related to the PDU Set from UPF / NG-RAN to NG-RAN.Figure 6.-1: Successful Transfer of DL PDU Set Information is reproduced as Figure 2.6.1.2 Transfer of UL PDU Set Information6.1.2.1 Successful operationThe purpose of the Transfer of UL PDU Set Information procedure is to send control information elements related to the PDU Set from NG-RAN to UPF.Figure 6.-2: Successful Transfer of UL PDU Set Information is reproduced as Figure 3.6.2 Elements for the PDU Set user plane protocol6.2.1 GeneralIn the present document the structure of frames is specified by using figures similar to figure 5.5. 1-1.Figure 5.5. 1-1: Example frame format is reproduced as Figure 4.

[0050] 3GPP TS 38.425 may include a new chapter to describe the “PDU Set RAN Container.” An example is illustrated below.NR user plane protocol data is conveyed by GTP-U protocol means, more specifically, by means of the "PDU Set RAN Container" GTP-U extension header as defined in TS 29.281.Transfer of PDU Set RAN Container6.3.1.x Successful operationThe purpose of the Transfer of PDU Set RAN Container procedure is to provide NR-U specific PDU Set information at the transfer of user data carrying a DL NR PDCP PDU Set Information from the node hosting the NR PDCP entity to the corresponding node.The node hosting the NR PDCP entity can indicate to the corresponding node to either discard all NR PDCP PDU Sets up to and including a defined DL discard NR PDCP PDU Set SN or discard one or a number of blocks of downlink NR PDCP PDU Sets.Figure 6.3.1.X-1: Successful Transfer of PDU Set RAN Container reproduced as Figure 5.6.4 Elements for the NR user plane protocol for PDU Set Information transfer 6.4.1 GeneralIn the present document the structure of frames is specified as illustrated in Figure 6.

[0051] For the “PDU Set container,” the bits 7 and 8 of the Next Extension Header Type shall be defined for the recipient to handle the unknown Extension Type.

[0052] In one embodiment, bit 7 is 0 and bit 8 is set to zero, meaning that comprehension of the extension header is not required. An Intermediate Node shall forward it to any Receiver Endpoint according to GTP-U protocol. This is to support the non-homogenous deployment with “supporting Node -> Non- Supporting Node -> Supporting Node, for example during inter session management function (SMF) handover.

[0053] In another embodiment, bit 7 is 1 and bit 8 is set to zero, meaning comprehension of the extension header is not required. An Intermediate Node shall discard the Extension Header Content and not forward it to any Receiver Endpoint. Other extension headers shall be treated independently of the extension header according to GTP-U protocol. In this case, if any nonsupporting node is involved as Intermediate Node, the PDU Set related parameters are discarded.

[0054] In particular embodiments, the non-homogenous deployment by 3GPP specification that when the new GTP-U Extension Header “PDU Set Container” is used, GTP-U Extension Header PDU Session Container shall be used when the operation is related to data payload transfer. So when the data payload is sent from the supporting Node to the non-supporting node, the nonsupporting node may ignore the PDU Set Container and use the PDU Session container as a fallback.

[0055] 3GPP TS 29.281 or TS 38.415 specifies that when the new GTP-U Extension Header “PDU Set Container” is used, GTP-U Extension Header PDU Session Container shall be used during data payload transfer.

[0056] In some embodiments, to support the non-homogenous deployment in Dual Connectivity, e.g., when the master node (MN) supports XR operation and the secondary node (SN) does not support XR operation, the supporting node’s gNB-CU-UP is indicated by gNB-CU- CP to remove the GTP-U Extension Header “PDU Set Container.” This is to reduce the processing in the non-supporting node and increase the data payload handling speed.

[0057] An example of the implementation is over El AP, the gNB-CU-CP indicates to gNB- CU-UP to remove the “PDU Set Container.”

[0058] In some embodiments, if the PDU Set related information is introduced in the existing GTP-U Extension Header, e.g. “PDU Session Container,” the solution described above for the handling of the non-homogenous deployment in Dual Connectivity shall be applied for Xn and NG based handover in the supporting source NG-RAN node.

[0059] For example, in below the PDU Set related information is included in “DL PDU SESSION INFORMATION (PDU Type 0)” within the existing PDU Session Container.

[0060] The PDU Set related information may be introduced in TS 38.415 in PDU Type 0. This frame format is defined to enable the NG-RAN to receive control information elements that are associated with the transfer of a packet over the interface.

[0061] Figure 7 illustrates the respective downlink PDU SESSION INFORMATION frame.

[0062] If the XR User Plane is designed as above, the supporting gNB-CU-CP shall indicate to gNB-CU-UP to remove the “PDU Set Related” information from DL PDU SESSION INFORMATION (PDU Type 0), when sending the data to the non-supporting node.

[0063] The same is specified in TS 38.425 for the information signaled from NG-RAN to another NG-RAN via Xn-U.

[0064] The frame format for the NR user plane protocol (DL USER DATA (PDU Type 0)) is defined, e.g., to enable the corresponding node to detect lostNR-U packets and may be associated with the transfer of a downlink Packet Data Convergence Protocol (PDCP) PDU.

[0065] Figure 8 illustrates the respective downlink USER DATA frame. All information elements defined in the following table are also applicable to E-UTRA PDCP. With this understanding, each instance of NR PDCP may be replaced by E-UTRA PDCP.

[0066] Figure 9 shows an example of a communication system 100 in accordance with some embodiments. In the example, the communication system 100 includes a telecommunication network 102 that includes an access network 104, such as a radio access network (RAN), and a core network 106, which includes one or more core network nodes 108. The access network 104includes one or more access network nodes, such as network nodes 110a and 110b (one or more of which may be generally referred to as network nodes 110), or any other similar 3rdGeneration Partnership Project (3GPP) access node or non-3GPP access point. The network nodes 110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 112a, 112b, 112c, and 112d (one or more of which may be generally referred to as UEs 112) to the core network 106 over one or more wireless connections.

[0067] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0068] The UEs 112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 110 and other communication devices. Similarly, the network nodes 110 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 112 and / or with other network nodes or equipment in the telecommunication network 102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network 102.

[0069] In the depicted example, the core network 106 connects the network nodes 110 to one or more hosts, such as host 116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 106 includes one more core network nodes (e.g., core network node 108) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 108. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF),Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0070] The host 116 may be under the ownership or control of a service provider other than an operator or provider of the access network 104 and / or the telecommunication network 102, and may be operated by the service provider or on behalf of the service provider. The host 116 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0071] As a whole, the communication system 100 of Figure 9 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.

[0072] In some examples, the telecommunication network 102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 102. For example, the telecommunications network 102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC)ZMassive loT services to yet further UEs.

[0073] In some examples, the UEs 112 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 104 on a predetermined schedule, when triggered by an internal or externalevent, or in response to requests from the access network 104. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi -radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0074] In the example, the hub 114 communicates with the access network 104 to facilitate indirect communication between one or more UEs (e.g., UE 112c and / or 112d) and network nodes (e.g., network node 110b). In some examples, the hub 114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 114 may be a broadband router enabling access to the core network 106 for the UEs. As another example, the hub 114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 110, or by executable code, script, process, or other instructions in the hub 114. As another example, the hub 114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 114 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy loT devices.

[0075] The hub 114 may have a constant / persistent or intermittent connection to the network node 110b. The hub 114 may also allow for a different communication scheme and / or schedule between the hub 114 and UEs (e.g., UE 112c and / or 112d), and between the hub 114 and the core network 106. In other examples, the hub 114 is connected to the core network 106 and / or one or more UEs via a wired connection. Moreover, the hub 114 may be configured to connect to an M2M service provider over the access network 104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 110 while still connected via the hub 114 via a wired or wireless connection. In some embodiments, the hub 114 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 110b. In other embodiments, the hub 114 may be a nondedicated hub - that is, a device which is capable of operating to route communications betweenthe UEs and network node 110b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0076] Figure 10 shows a UE 200 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0077] A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to- everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0078] The UE 200 includes processing circuitry 202 that is operatively coupled via a bus 204 to an input / output interface 206, a power source 208, a memory 210, a communication interface 212, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 2. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0079] The processing circuitry 202 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 210. The processing circuitry 202 may be implemented as one or more hardware -implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 202 may include multiple central processing units (CPUs).

[0080] In the example, the input / output interface 206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 200. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0081] In some embodiments, the power source 208 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 208 may further include power circuitry for delivering power from the power source 208 itself, and / or an external power source, to the various parts of the UE 200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 208. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 208 to make the power suitable for the respective components of the UE 200 to which power is supplied.

[0082] The memory 210 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 210 includes one or more application programs 214,such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 216. The memory 210 may store, for use by the UE 200, any of a variety of various operating systems or combinations of operating systems.

[0083] The memory 210 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 210 may allow the UE 200 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 210, which may be or comprise a device -readable storage medium.

[0084] The processing circuitry 202 may be configured to communicate with an access network or other network using the communication interface 212. The communication interface 212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 222. The communication interface 212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 218 and / or a receiver 220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 218 and receiver 220 may be coupled to one or more antennas (e.g., antenna 222) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0085] In the illustrated embodiment, communication functions of the communication interface 212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short- range communications such as Bluetooth, near-field communication, location-basedcommunication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / intemet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0086] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 212, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0087] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0088] A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or itemtracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned AerialVehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 200 shown in Figure 2.

[0089] As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another UE and / or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0090] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0091] Figure 11 shows a network node 300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NRNodeBs (gNBs)).

[0092] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and / or remote radio units (RRUs), sometimes referred to as RemoteRadio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0093] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0094] The network node 300 includes a processing circuitry 302, a memory 304, a communication interface 306, and a power source 308. The network node 300 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 300 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 304 for different RATs) and some components may be reused (e.g., a same antenna 310 may be shared by different RATs). The network node 300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 300.

[0095] The processing circuitry 302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operableto provide, either alone or in conjunction with other network node 300 components, such as the memory 304, to provide network node 300 functionality.

[0096] In some embodiments, the processing circuitry 302 includes a system on a chip (SOC). In some embodiments, the processing circuitry 302 includes one or more of radio frequency (RF) transceiver circuitry 312 and baseband processing circuitry 314. In some embodiments, the radio frequency (RF) transceiver circuitry 312 and the baseband processing circuitry 314 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 312 and baseband processing circuitry 314 may be on the same chip or set of chips, boards, or units.

[0097] The memory 304 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 302. The memory 304 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 302 and utilized by the network node 300. The memory 304 may be used to store any calculations made by the processing circuitry 302 and / or any data received via the communication interface 306. In some embodiments, the processing circuitry 302 and memory 304 is integrated.

[0098] The communication interface 306 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface 306 comprises port(s) / terminal(s) 316 to send and receive data, for example to and from a network over a wired connection. The communication interface 306 also includes radio front-end circuitry 318 that may be coupled to, or in certain embodiments a part of, the antenna 310. Radio front-end circuitry 318 comprises fdters 320 and amplifiers 322. The radio front-end circuitry 318 may be connected to an antenna 310 and processing circuitry 302. The radio front-end circuitry may be configured to condition signals communicated between antenna 310 and processing circuitry 302. The radio front-end circuitry 318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-endcircuitry 318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of fdters 320 and / or amplifiers 322. The radio signal may then be transmitted via the antenna 310. Similarly, when receiving data, the antenna 310 may collect radio signals which are then converted into digital data by the radio front-end circuitry 318. The digital data may be passed to the processing circuitry 302. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0099] In certain alternative embodiments, the network node 300 does not include separate radio front-end circuitry 318, instead, the processing circuitry 302 includes radio front-end circuitry and is connected to the antenna 310. Similarly, in some embodiments, all or some of the RF transceiver circuitry 312 is part of the communication interface 306. In still other embodiments, the communication interface 306 includes one or more ports or terminals 316, the radio front-end circuitry 318, and the RF transceiver circuitry 312, as part of a radio unit (not shown), and the communication interface 306 communicates with the baseband processing circuitry 314, which is part of a digital unit (not shown).

[0100] The antenna 310 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 310 may be coupled to the radio front-end circuitry 318 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 310 is separate from the network node 300 and connectable to the network node 300 through an interface or port.

[0101] The antenna 310, communication interface 306, and / or the processing circuitry 302 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 310, the communication interface 306, and / or the processing circuitry 302 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0102] The power source 308 provides power to the various components of network node 300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 300 with power forperforming the functionality described herein. For example, the network node 300 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 308. As a further example, the power source 308 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0103] Embodiments of the network node 300 may include additional components beyond those shown in Figure 11 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 300 may include user interface equipment to allow input of information into the network node 300 and to allow output of information from the network node 300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 300.

[0104] Figure 12 is a block diagram of a host 400, which may be an embodiment of the host 116 of Figure 1, in accordance with various aspects described herein. As used herein, the host 400 may be or comprise various combinations hardware and / or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host 400 may provide one or more services to one or more UEs.

[0105] The host 400 includes processing circuitry 402 that is operatively coupled via a bus 404 to an input / output interface 406, a network interface 408, a power source 410, and a memory 412. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 10 and 3, such that the descriptions thereof are generally applicable to the corresponding components of host 400.

[0106] The memory 412 may include one or more computer programs including one or more host application programs 414 and data 416, which may include user data, e.g., data generated by a UE for the host 400 or data generated by the host 400 for a UE. Embodiments of the host 400 may utilize only a subset or all of the components shown. The host application programs 414 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding(AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs 414 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host 400 may select and / or indicate a different host for over-the-top services for a UE. The host application programs 414 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.

[0107] Figure 13 is a block diagram illustrating a virtualization environment 500 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized.

[0108] Applications 502 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0109] Hardware 504 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 508a and 508b (one or more of which may be generally referred to as VMs 508), and / or perform any of thefunctions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 506 may present a virtual operating platform that appears like networking hardware to the VMs 508.

[0110] The VMs 508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 506. Different embodiments of the instance of a virtual appliance 502 may be implemented on one or more of VMs 508, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.[oni] In the context of NFV, a VM 508 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 508, and that part of hardware 504 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 508 on top of the hardware 504 and corresponds to the application 502.

[0112] Hardware 504 may be implemented in a standalone network node with generic or specific components. Hardware 504 may implement some functions via virtualization. Alternatively, hardware 504 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 510, which, among others, oversees lifecycle management of applications 502. In some embodiments, hardware 504 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 512 which may alternatively be used for communication between hardware nodes and radio units.

[0113] Figure 14 shows a communication diagram of ahost 602 communicating via anetwork node 604 with a UE 606 over a partially wireless connection in accordance with someembodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE 112a of Figure 9 and / or UE 200 of Figure 10), network node (such as network node 110a of Figure 9 and / or network node 300 of Figure 11), and host (such as host 116 of Figure 9 and / or host 400 of Figure 12) discussed in the preceding paragraphs will now be described with reference to Figure 13.

[0114] Like host 400, embodiments of host 602 include hardware, such as a communication interface, processing circuitry, and memory. The host 602 also includes software, which is stored in or accessible by the host 602 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE 606 connecting via an over-the-top (OTT) connection 650 extending between the UE 606 and host 602. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 650.

[0115] The network node 604 includes hardware enabling it to communicate with the host 602 and UE 606. The connection 660 may be direct or pass through a core network (like core network 106 of Figure 1) and / or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet.

[0116] The UE 606 includes hardware and software, which is stored in or accessible by UE 606 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 606 with the support of the host 602. In the host 602, an executing host application may communicate with the executing client application via the OTT connection 650 terminating at the UE 606 and host 602. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection 650 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection 650.

[0117] The OTT connection 650 may extend via a connection 660 between the host 602 and the network node 604 and via a wireless connection 670 between the network node 604 and the UE 606 to provide the connection between the host 602 and the UE 606. The connection 660 and wireless connection 670, over which the OTT connection 650 may be provided, have been drawn abstractly to illustrate the communication between the host 602 and the UE 606 via the networknode 604, without explicit reference to any intermediary devices and the precise routing of messages via these devices.

[0118] As an example of transmitting data via the OTT connection 650, in step 608, the host 602 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE 606. In other embodiments, the user data is associated with a UE 606 that shares data with the host 602 without explicit human interaction. In step 610, the host 602 initiates a transmission carrying the user data towards the UE 606. The host 602 may initiate the transmission responsive to a request transmitted by the UE 606. The request may be caused by human interaction with the UE 606 or by operation of the client application executing on the UE 606. The transmission may pass via the network node 604, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 612, the network node 604 transmits to the UE 606 the user data that was carried in the transmission that the host 602 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 614, the UE 606 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 606 associated with the host application executed by the host 602.

[0119] In some examples, the UE 606 executes a client application which provides user data to the host 602. The user data may be provided in reaction or response to the data received from the host 602. Accordingly, in step 616, the UE 606 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input / output interface of the UE 606. Regardless of the specific manner in which the user data was provided, the UE 606 initiates, in step 618, transmission of the user data towards the host 602 via the network node 604. In step 620, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 604 receives user data from the UE 606 and initiates transmission of the received user data towards the host 602. In step 622, the host 602 receives the user data carried in the transmission initiated by the UE 606.

[0120] One or more of the various embodiments improve the performance of OTT services provided to the UE 606 using the OTT connection 650, in which the wireless connection 670 forms the last segment. More precisely, the teachings of these embodiments may improve the data rate and latency and thereby provide benefits such as reduced user waiting time, better responsiveness, and better QoE.

[0121] In an example scenario, factory status information may be collected and analyzed by the host 602. As another example, the host 602 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 602 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 602 may store surveillance video uploaded by a UE. As another example, the host 602 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host 602 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and / or transmitting data.

[0122] In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 650 between the host 602 and UE 606, in response to variations in the measurement results. The measurement procedure and / or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 602 and / or UE 606. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 650 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 650 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 604. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 602. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 650 while monitoring propagation times, errors, etc.

[0123] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or softwareneeded to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0124] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer- readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

[0125] FIGURE 15 is a flowchart illustrating an example method in a network node, according to certain embodiments. In particular embodiments, one or more steps of FIGURE 15 may be performed by network node 300 described with respect to FIGURE 11. The network node is for operation where the NR user plane supports non-homogenous deployment of user plane additions.

[0126] The method begins at step 1512, where the first network node (e.g., network node 300) constructs a General Packet Radio Service (GPRS) Tunnelling Protocol User Plane (GTP-U) packet comprising an Extension Header comprising a PDU Set Container. The PDU Set Container comprises an indication that a second network node may ignore the PDU Set Container when the second network node does not support PDU Set functionality.

[0127] In particular embodiments, the indication is part of the Next Extension Header Type field of the GTP-U Extension Header. The indication may comprise two bits of the Next Extension Header Type field of the GTP-U Extension Header.

[0128] In particular embodiments, the method further comprises using GTP-U Extension Header PDU Session Container for data payload transfer.

[0129] In particular embodiments, the first network node comprises a radio access network (RAN) node and the second network node comprises one of a RAN node and a User Plane Function (UPF) node.

[0130] At step 1514, the first network node transmits the GTP-U packet to the second network node.

[0131] Modifications, additions, or omissions may be made to method 1500 of FIGURE 15. Additionally, one or more steps in the method of FIGURE 15 may be performed in parallel or in any suitable order.

[0132] FIGURE 16 is a flowchart illustrating another example method in a network node, according to certain embodiments. In particular embodiments, one or more steps of FIGURE 16 may be performed by network node 300 described with respect to FIGURE 11. The network node is for operation where the NR user plane supports non-homogenous deployment of user plane additions.

[0133] The method begins at step 1612, where the first network node (e.g., network node 300) receives, from a second network node, a GTP-U packet comprising an Extension Header comprising a PDU Set Container. The PDU Set Container comprises an indication that the first network node may ignore the PDU Set Container when the first network node does not support PDU Set functionality.

[0134] At step 1614, the first network node, based on the indication, either forwards the GTP- U packet with the PDU Set Container to a third network node; or forwards the GTP-U packet without the PDU Set Container to the third network node.

[0135] In particular embodiments, the first network node comprises a radio access network (RAN) node and the second network node comprises a RAN node.

[0136] In this example, the first network node may refer to the second network node described with respect to Figure 15, and the second network node may refer to the first network node described with respect to Figure 15.

[0137] Modifications, additions, or omissions may be made to method 1600 of FIGURE 16. Additionally, one or more steps in the method of FIGURE 16 may be performed in parallel or in any suitable order.

[0138] FIGURE 17 is a flowchart illustrating an example method in a gNB central unit control plane (gNB-CU-CP) network node, according to certain embodiments. In particular embodiments, one or more steps of FIGURE 17 may be performed by network node 300 described with respect to FIGURE 11. The network node is for operation where the NR user plane supports non- homogenous deployment of user plane additions.

[0139] The method begins at step 1712, where the first network node (e.g., network node 300) determines that a second network node does not support PDU Set functionality.

[0140] At step 1714, the network node transmits, to a gNB central unit user plane (gNB-CU- UP) associated with the gNB-CU-CP, an indication to remove PDU Set associated information from a packet before transmitting the packet to the second network node.

[0141] In particular embodiments, the first network node is operating in dual connectivity and the second network node comprises a secondary network node.

[0142] Modifications, additions, or omissions may be made to method 1700 of FIGURE 17. Additionally, one or more steps in the method of FIGURE 17 may be performed in parallel or in any suitable order.

[0143] FIGURE 18 is a flowchart illustrating an example method in a gNB central unit user plane (gNB-CU-UP) network node, according to certain embodiments. In particular embodiments, one or more steps of FIGURE 18 may be performed by network node 300 described with respect to FIGURE 11. The network node is for operation where the NR user plane supports non- homogenous deployment of user plane additions.

[0144] The method begins at step 1812, where the network node (e.g., network node 300) receives, from a gNB-CU-CP associated with the gNB-CU-UP, an indication to remove PDU Set associated information from a packet before transmitting the packet to a second network node.

[0145] At step 1814, the network node transmits the packet with the removed PDU Set associated information to the second network node.

[0146] In particular embodiments, the first network node is operating in dual connectivity and the second network node comprises a secondary network node.

[0147] Modifications, additions, or omissions may be made to method 1800 of FIGURE 18. Additionally, one or more steps in the method of FIGURE 18 may be performed in parallel or in any suitable order.

[0148] The foregoing description sets forth numerous specific details. It is understood, however, that embodiments may be practiced without these specific details. In other instances, well-known circuits, structures and techniques have not been shown in detail in order not to obscure the understanding of this description. Those of ordinary skill in the art, with the included descriptions, will be able to implement appropriate functionality without undue experimentation.

[0149] References in the specification to “one embodiment,” “an embodiment,” “an example embodiment,” etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to implement such feature, structure, or characteristic in connection with other embodiments, whether or not explicitly described.

[0150] Although this disclosure has been described in terms of certain embodiments, alterations and permutations of the embodiments will be apparent to those skilled in the art. Accordingly, the above description of the embodiments does not constrain this disclosure. Other changes, substitutions, and alterations are possible without departing from the scope of this disclosure, as defined by the claims below.

[0151] Some example embodiments are described below.Group A Embodiments1. A method performed by a wireless device, the method comprising:- any of the wireless device steps, features, or functions described above, either alone or in combination with other steps, features, or functions described above.. The method of the previous embodiment, further comprising one or more additional wireless device steps, features or functions described above.3. The method of any of the previous embodiments, further comprising:- providing user data; and- forwarding the user data to a host computer via the transmission to the base station.Group B Embodiments4. A method performed by a base station for operation where the new radio (NR) user plane supports non-homogenous deployment, the method comprising:- transmitting a GTP-U packet comprising an extension header with a PDU Set Container as defined herein.5. A method performed by a base station for operation where the new radio (NR) user plane supports non-homogenous deployment, the method comprising:- receiving a GTP-U packet comprising an extension header with a PDU Set Container as defined herein.6. A method performed by a base station, the method comprising:- any of the steps, features, or functions described above with respect to base station, either alone or in combination with other steps, features, or functions described above.7. The method of the previous embodiment, further comprising one or more additional base station steps, features or functions described above.8. The method of any of the previous embodiments, further comprising:- obtaining user data; and- forwarding the user data to a host computer or a wireless device.Group C Embodiments9. A mobile terminal comprising:- processing circuitry configured to perform any of the steps of any of the Group A embodiments; and- power supply circuitry configured to supply power to the wireless device.10. A base station comprising:- processing circuitry configured to perform any of the steps of any of the Group B embodiments;- power supply circuitry configured to supply power to the wireless device.11. A user equipment (UE) comprising:- an antenna configured to send and receive wireless signals;- radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry;- the processing circuitry being configured to perform any of the steps of any of the Group A embodiments;- an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry;- an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and- a battery connected to the processing circuitry and configured to supply power to the UE.12. A communication system including a host computer comprising:- processing circuitry configured to provide user data; and- a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE),- wherein the cellular network comprises a base station having a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments.The communication system of the pervious embodiment further including the base station. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station. The communication system of the previous 3 embodiments, wherein:- the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and- the UE comprises processing circuitry configured to execute a client application associated with the host application. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:- at the host computer, providing user data; and- at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the base station performs any of the steps of any of the Group B embodiments. The method of the previous embodiment, further comprising, at the base station, transmitting the user data. The method of the previous 2 embodiments, wherein the user data is provided at the host computer by executing a host application, the method further comprising, at the UE, executing a client application associated with the host application. A user equipment (UE) configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to performs any of the previous 3 embodiments. A communication system including a host computer comprising:- processing circuitry configured to provide user data; and- a communication interface configured to forward user data to a cellular network for transmission to a user equipment (UE),- wherein the UE comprises a radio interface and processing circuitry, the UE’s components configured to perform any of the steps of any of the Group A embodiments. The communication system of the previous embodiment, wherein the cellular network further includes a base station configured to communicate with the UE. The communication system of the previous 2 embodiments, wherein:- the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and- the UE’s processing circuitry is configured to execute a client application associated with the host application. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:- at the host computer, providing user data; and- at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the UE performs any of the steps of any of the Group A embodiments. The method of the previous embodiment, further comprising at the UE, receiving the user data from the base station. A communication system including a host computer comprising:- communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station,- wherein the UE comprises a radio interface and processing circuitry, the UE’s processing circuitry configured to perform any of the steps of any of the Group A embodiments.The communication system of the previous embodiment, further including the UE. The communication system of the previous 2 embodiments, further including the base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station. The communication system of the previous 3 embodiments, wherein:- the processing circuitry of the host computer is configured to execute a host application; and- the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data. The communication system of the previous 4 embodiments, wherein:- the processing circuitry of the host computer is configured to execute a host application, thereby providing request data; and- the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:- at the host computer, receiving user data transmitted to the base station from the UE, wherein the UE performs any of the steps of any of the Group A embodiments. The method of the previous embodiment, further comprising, at the UE, providing the user data to the base station. The method of the previous 2 embodiments, further comprising:- at the UE, executing a client application, thereby providing the user data to be transmitted; and- at the host computer, executing a host application associated with the clientapplication. The method of the previous 3 embodiments, further comprising:- at the UE, executing a client application; and- at the UE, receiving input data to the client application, the input data being provided at the host computer by executing a host application associated with the client application,- wherein the user data to be transmitted is provided by the client application in response to the input data. A communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments. The communication system of the previous embodiment further including the base station. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station. The communication system of the previous 3 embodiments, wherein:- the processing circuitry of the host computer is configured to execute a host application;- the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:- at the host computer, receiving, from the base station, user data originating from a transmission which the base station has received from the UE, wherein the UE performs any of the steps of any of the Group A embodiments.The method of the previous embodiment, further comprising at the base station, receiving the user data from the UE. The method of the previous 2 embodiments, further comprising at the base station, initiating a transmission of the received user data to the host computer.

Claims

Claims1. A method performed by a first network node for operation where the new radio (NR) user plane supports non-homogenous deployment of user plane additions, the method comprising : constructing (1512) a General Packet Radio Service (GPRS) Tunnelling Protocol User Plane (GTP-U) packet comprising an Extension Header comprising a Protocol Data Unit (PDU) Set Container, the PDU Set Container comprising an indication that a second network node may ignore the PDU Set Container when the second network node does not support PDU Set functionality; and transmitting (1514) the GTP-U packet to the second network node.

2. The method of claim 1, wherein the indication is part of the Next Extension Header Type field of the GTP-U Extension Header.

3. The method of claim 2, wherein the indication comprises two bits of the Next Extension Header Type field of the GTP-U Extension Header.

4. The method of any one of claims 1-3, further comprising using GTP-U Extension Header PDU Session Container for data payload transfer.

5. The method of any one of claims 1 -4, wherein the first network node comprises a radio access network (RAN) node and the second network node comprises one of a RAN node and a User Plane Function (UPF) node.

6. A network node (300) comprising processing circuitry (302) operable to perform the steps of any one of claims 1-5.

7. A method performed by a first network node for operation where the new radio (NR) user plane supports non-homogenous deployment of user plane additions, the method comprising : receiving (1612), from a second network node, a General Packet Radio Service (GPRS) Tunnelling Protocol User Plane (GTP-U) packet comprising an Extension Header comprising a Protocol Data Unit (PDU) Set Container, the PDU Set Container comprising an indication thatthe first network node may ignore the PDU Set Container when the first network node does not support PDU Set functionality; and based on the indication: forwarding (1614) the GTP-U packet with the PDU Set Container to a third network node; or forwarding (1614) the GTP-U packet without the PDU Set Container to the third network node.

8. The method of claim 7, wherein the indication is part of the Next Extension Header Type field of the GTP-U Extension Header.

9. The method of claim 8, wherein the indication comprises two bits of the Next Extension Header Type field of the GTP-U Extension Header.

10. The method of any one of claims 7-9, further comprising using GTP-U Extension Header PDU Session Container for data payload transfer.

11. The method of any one of claims 7-10, wherein the first network node comprises a radio access network (RAN) node and the second network node comprises a RAN node.

12. A network node (300) comprising processing circuitry (302) operable to perform the steps of any one of claims 7-11.

13. A method performed by a gNB central unit control plane (gNB-CU-CP) first network node for operation where the new radio (NR) user plane supports non-homogenous deployment of user plane additions, the method comprising: determining (1712) that a second network node does not support Protocol Data Unit (PDU) Set functionality; and transmitting (1714), to a gNB central unit user plane (gNB-CU-UP) associated with the gNB-CU-CP, an indication to remove PDU Set associated information from a packet before transmitting the packet to the second network node.

14. The method of claim 13, wherein the PDU Set associated information comprises a General Packet Radio Service (GPRS) Tunnelling Protocol User Plane (GTP-U) Extension Header comprising a Protocol Data Unit (PDU) Set Container.

15. The method of claim 13, wherein the PDU Set associated information comprises a General Packet Radio Service (GPRS) Tunnelling Protocol User Plane (GTP-U) Extension Header comprising a PDU Session Container.

16. The method of any one of claims 13-15, wherein the first network node is operating in dual connectivity and the second network node comprises a secondary network node.

17. A network node (300) comprising processing circuitry (302) operable to perform the steps of any one of claims 13-16.

18. A method performed by a gNB central unit user plane (gNB-CU-UP) first network node for operation where the new radio (NR) user plane supports non-homogenous deployment of user plane additions, the method comprising: receiving (1812), from a gNB central unit control plane (gNB-CU-CP) associated with the gNB-CU-UP, an indication to remove PDU Set associated information from a packet before transmitting the packet to the second network node; and transmitting (1814) the packet with the removed PDU Set associated information to the second network node.

19. The method of claim 18, wherein the PDU Set associated information comprises a General Packet Radio Service (GPRS) Tunnelling Protocol User Plane (GTP-U) Extension Header comprising a Protocol Data Unit (PDU) Set Container.

20. The method of claim 18, wherein the PDU Set associated information comprises a General Packet Radio Service (GPRS) Tunnelling Protocol User Plane (GTP-U) Extension Header comprising a PDU Session Container.

21. The method of any one of claims 18-20, wherein the first network node is operating indual connectivity and the second network node comprises a secondary network node.

22. A network node (300) comprising processing circuitry (302) operable to perform the steps of any one of claims 18-21.

Images