Augmented reality user plane design

Abstract

According to some embodiments, a method is performed by a first network node for operations of non-homogeneous deployment of new radio (NR) user plane support user plane additions. The method includes constructing a General Packet Radio Service (GPRS) Tunneling Protocol User Plane (GTP-U) packet including an extended header, the extended header including a Protocol Data Unit (PDU) set container. The PDU set container includes an indication that the second network node can ignore the PDU set container when the second network node does not support PDU set functionality. The method further includes transmitting the GTP-U packet to the second network node.

Description

Technical Field

[0001] This disclosure generally relates to communication networks, and more specifically, to extended reality (XR) user plane design. Background Technology

[0002] The 3GPP specifications include application protocols that specify open network interfaces (such as Next Generation Application Protocol (NGAP), S1 Application Protocol (S1AP), Xn Application Protocol (XnAP), etc.) and mechanisms that the sender can use to control the behavior of the receiver when “understanding” is crucial for control.

[0003] Each basic process (EP) and each information element (IE) contained within the message of the basic process is assigned a "criticality". The three criticalities are defined as "reject", "ignore", and "ignore and notify". Across third-generation (3G), fourth-generation (4G), and fifth-generation (5G) networks, only "reject" and "ignore" have been used.

[0004] The critical "deny" is used only when the receiving node is unable to continue performing the requested function. When adding functionality to an existing process, the critical "ignore" is assigned to the new IE in most cases. Furthermore, "ignore and notify" is not used in the 3GPP specification. Therefore, the use of criticality can be restrictive.

[0005] On the 3GPP user plane, the handling of unknown data packets is unclear. For example, in section 5.6 "Handling of Unknown, Unpredictable, and Erroneous Protocol Data" of 3GPP TS 38.415, the specification is empty. There are certain requirements for interoperability with protocol entities that have not yet implemented protocol additions, namely, that receiving nodes that have not yet implemented protocol additions should "ignore" these additions when performing functions related to legacy protocol information, and should not discard entire user plane protocol data units (PDUs).

[0006] 3GPP is also working on standardizing Extended Reality (XR) applications. For example, 3GPP has discussed the non-homogeneous deployment of Next-Generation Radio Access Network (NG-RAN) nodes supporting PDU-based processing and has agreed on the following requirements (CRS2-2308246 and TS 23.501). ******************************************************************************

[0007] 5.7.7.1 Overview

[0008] PDU set QoS parameters are used to support PDU set-based QoS processing in NG-RAN. At least one PDU set QoS parameter should be sent to NG-RAN to enable PDU set-based QoS processing.

[0009] The following are specific QoS features of the PDU set:

[0010] 1. PDU set delay budget (PSDB).

[0011] 2. PDU set error rate (PSER).

[0012] 3. PDU Integrated Processing Information (PSIHI).

[0013] For QoS flows that support QoS processing based on PDU sets, 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 the AF and / or local configuration. The PDU set QoS parameters are sent to the SMF as part of the PCC rules. The SMF sends them to the NG-RAN as part of the QoS profile.

[0014] If the NG-RAN receives the PDU set QoS parameters and supports them, it applies the PDU set QoS parameters as described in this clause.

[0015] Non-homogeneous support for PDU-based processing in NG-RAN 5.37.5.x

[0016] By sending at least one PDU set QoS parameter to the NG-RAN, the SMF requests the NG-RAN to activate PDU set QoS processing for a given QoS flow, and the NG-RAN provides the SMF with an indication of whether it accepts the PDU set QoS parameters. During NG-RAN Xn and N2 handovers, the target NG-RAN provides the SMF with an indication of whether the target NG-RAN node supports PDU set-based processing as specified in TS 38.413. Based on the NG-RAN indication, the SMF configures the PSA UPF to activate / deactivate the PDU set identifier and tag.

[0017] When PSA UPF uses PDU set information in the GTP-U header to identify and tag PDUs, it should do so starting with the complete PDU set.

[0018] The rationale for the Change Request (CR) is that the "PDU set-based QoS processing" feature does not need to be uniformly supported across the network. The Session Management Function (SMF) informs NG-RAN nodes whether they support the PDU set-based QoS processing feature, and the SMF only triggers the activation of the PDU set identifier in the User Plane Function (UPF) if the NG-RAN supports the feature, because this feature consumes processing power and should only be used when the NG-RAN actually uses the information.

[0019] The New Radio (NR) user plane protocol resides in the user plane of the Radio Network Layer (RNL) above the Transport Network Layer (TNL) of the interface.

[0020] The General Packet Radio Service (GPRS) Tunneling Protocol User Plane (GTP-U) defines two “GTP-U containers” and GTP-U extended headers. One is the “NR RAN container,” defined within NG-RAN for the X2-U, Xn-U, and F1-U user plane interfaces, and within Evolved Universal Terrestrial Radio Access (E-UTRAN) for E-UTRAN New Radio-Dual Connectivity (EN-DC). The contents of the “NR RAN container” are specified in 3GPP TS 38.425.

[0021] The other is the "PDU session container," which is defined for the N3 / N9 user plane interface between NG-RAN and User Plane Functions (UPFs) or between two UPFs, and for the N3mb / N19mb user plane interface between MB-UPF and NG-RAN or between MB-UPF and UPF. The contents of the "PDU session container" are specified in 3GPP TS 38.415.

[0022] During the movement of a PDU-based QoS processing support NG-RAN node to a non-NG-RAN node, the source node may or may not know whether the target NG-RAN node supports PDU-based QoS processing during data forwarding. If the source node knows (based on not receiving support information from the target NG-RAN node), it can modify the contents of the GTP-U PDU session container extension container to strip unsupported protocol information before forwarding user plane packets to the target node. However, this requires additional and expensive processing power, as the GTP-U PDU session container extension container is specified in 3GPP TS 29.281, while the contents of the PDU session container are specified in 3GPP TS 38.415.

[0023] For non-converged NG-RAN deployments as specified in 3GPP TS 38.401, user plane data between gNB-CU and gNB-DU is transmitted via the GTP-U-based F1-U interface. User plane protocol information is included within the GTP-U “NR RAN Container” extension container as specified in 3GPP TS 29.281, the contents of which are 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).

[0024] With this structure, when new features are introduced, the impact on the X2-U, Xn-U, and F1-U interfaces is incorporated into the "NRRAN container." The impact on the N3 / N9 interfaces is incorporated into the "PDU session container." See 3GPP TS 29.281.

[0025] Several challenges exist. For example, the XR feature has introduced the concept of PDU sets. The user plane should include XR PDU set-related parameters as defined in 3GPP's "PDU Set Information". The PDU set information UP includes the following items: PDU set sequence number (PDU set identifier); indication of the last PDU in the PDU set (optional); PDU sequence numbers within the PDU set (optional); PDU set size (in bytes); and PDU set importance, which indicates the relative importance of the PDU set compared to other PDU sets within the QoS flow (optional).

[0026] 3GPP also specified that XR services should support non-homogeneous support based on PDU sets in NG-RAN.

[0027] Therefore, the XR user plane must be designed in the following way: the node receiving PDU set information in the user plane packet can process protocol additions without being forced to discard the entire user plane packet, so that when the source node supports "QoS processing based on PDU set" but the target node does not, the data can be forwarded from the source node to the target NG-RAN node.

[0028] During dual-connectivity operations, deployments should be homogeneous. However, if non-homogeneous deployments are permitted, the XR user plane must be designed to make it work.

[0029] Neither the PDU Session User Plane Protocol (TS 38.415) nor the NR User Plane Protocol (TS 38.425) currently supports the non-homogeneous deployment required by XR for the (user plane) protocol addition.

[0030] As used in this article, a supported node refers to a node that supports XR services. A non-supported node refers to a node that does not support XR services. Summary of the Invention

[0031] As described above, current extended reality (XR) user plane designs for non-homogeneous deployments present certain challenges. Certain aspects of this disclosure and embodiments thereof can provide solutions to these or other challenges. For example, specific embodiments support non-homogeneous XR user planes. Protocol Data Unit (PDU) set information in the user plane is defined in a backward-compatible manner such that when PDU set information is sent to a node that does not understand the parameter set, the node can ignore the parameter set and continue processing as if it were processing a normal radio (NR) data payload (i.e., without XR features). In non-homogeneous dual-connectivity deployments, PDU set information can be removed from the user plane when Next Generation Radio Access Network (NG-RAN) nodes or their corresponding nodes do not support XR features.

[0032] According to some embodiments, the method is performed by a first network node for operations that support non-homogeneous deployments added to the NR user plane. The method includes: constructing a General Packet Radio Service (GPRS) Tunneling Protocol User Plane (GTP-U) packet including an extended header that includes a PDU set container. The PDU set container includes an indication that the second network node can ignore the PDU set container if it does not support PDU set functionality. The method also includes sending the GTP-U packet to the second network node.

[0033] In a particular embodiment, the indication is part of the Next Extended Header Type field of the GTP-U Extended Header. The indication may include two bits of the Next Extended Header Type field of the GTP-U Extended Header.

[0034] In a particular embodiment, the method further includes transmitting data payload using a GTP-U extended header PDU session container.

[0035] In a particular embodiment, the first network node includes a radio access network (RAN) node, and the second network node includes one of a RAN node and a user plane function (UPF) node.

[0036] According to some embodiments, the method is performed by a first network node for operations that support non-homogeneous deployments added to the NR user plane. The method includes receiving a GTP-U packet from a second network node, the extended header including a PDU set container. The PDU set container includes an indication that the first network node can ignore the PDU set container when it does not support PDU set functionality. Based on this indication, the method further includes: forwarding the GTP-U packet with the PDU set container to a third network node; or forwarding a GTP-U packet without a PDU set container to the third network node.

[0037] In a particular embodiment, the indication is part of the Next Extended Header Type field of the GTP-U Extended Header. The indication may include two bits of the Next Extended Header Type field of the GTP-U Extended Header.

[0038] In a particular embodiment, the method further includes transmitting data payload using a GTP-U extended header PDU session container.

[0039] In a particular embodiment, the first network node includes a radio access network (RAN) node, and the second network node includes a RAN node.

[0040] According to some embodiments, the method is performed by a first network node in the gNB Central Unit Control Plane (gNB-CU-CP) for NR user plane support of operations involving non-homogeneous deployments added by the user plane. The method includes: determining that a second network node does not support PDU set functionality, and sending an instruction to the gNB Central Unit User Plane (gNB-CU-UP) associated with the gNB-CU-CP to remove PDU set association information from the packet before sending the packet to the second network node.

[0041] In a particular embodiment, the PDU set association information includes a GTP-U extended header, which includes a PDU set container.

[0042] In a particular embodiment, the PDU set association information includes a GTP-U extended header, which includes a PDU session container.

[0043] In a particular embodiment, the first network node operates under dual connectivity, and the second network node includes a secondary network node.

[0044] According to some embodiments, the method is performed by a first network node (gNB-CU-UP) for NR user plane support of adding non-homogeneous deployments. The method includes: receiving from a gNB-CU-CP associated with the gNB-CU-UP an instruction to remove PDU set association information from a packet before sending the packet to a second network node, and sending a packet with the removed PDU set association information to the second network node.

[0045] In a particular embodiment, the PDU set association information includes a GTP-U extended header, which includes a PDU set container.

[0046] In a particular embodiment, the PDU set association information includes a GTP-U extended header, which includes a PDU session container.

[0047] In a particular embodiment, the first network node operates under dual connectivity, and the second network node includes a secondary network node.

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

[0049] A computer program product is also disclosed, comprising a non-transitory computer-readable medium storing computer-readable program code that, when executed by processing circuitry, is operable to perform any method executed by the aforementioned network node.

[0050] Certain embodiments may provide one or more of the following technical advantages. For example, certain embodiments support XR PDU set processing in the user plane for non-homogeneous RAN deployments and support XR features. Attached Figure Description

[0051] This disclosure can be best understood by referring to the following description and accompanying drawings, which illustrate embodiments of this disclosure. In the drawings:

[0052] Figure 1 The byte structure of the GTP-U extended header "PDU set container" is shown;

[0053] Figure 2 This is a flowchart illustrating the successful transmission of downlink PDU set information;

[0054] Figure 3 This is a flowchart illustrating the successful transmission of uplink PDU set information;

[0055] Figure 4 An example frame format is shown;

[0056] Figure 5This is a flowchart illustrating the successful transmission of a PDU set RAN container;

[0057] Figure 6 Another example frame format is shown;

[0058] Figure 7 The corresponding downlink PDU session information frame is shown;

[0059] Figure 8 The corresponding downlink user data frame is shown;

[0060] Figure 9 Examples of communication systems according to certain embodiments are shown;

[0061] Figure 10 A user equipment (UE) is shown according to certain embodiments;

[0062] Figure 11 A network node according to some embodiments is shown;

[0063] Figure 12 This is a block diagram of a host according to certain embodiments;

[0064] Figure 13 This is a block diagram illustrating a virtualized environment that can virtualize functionality implemented by some embodiments;

[0065] Figure 14 A communication diagram is shown, illustrating communication between a host and a UE via a network node through a partial wireless connection according to some embodiments;

[0066] Figure 15 This is a flowchart illustrating example methods in a network node according to certain embodiments;

[0067] Figure 16 This is a flowchart illustrating another example method in a network node according to certain embodiments;

[0068] Figure 17 This is a flowchart illustrating an example method in a gNB central unit control plane (gNB-CU-CP) network node according to certain embodiments; and

[0069] Figure 18 This is a flowchart illustrating an example method in a gNB Central Unit User Plane (gNB-CU-UP) network node according to certain embodiments. Detailed Implementation

[0070] As described above, current extended reality (XR) user plane designs for non-homogeneous deployments present certain challenges. Certain aspects of this disclosure and embodiments thereof can provide solutions to these or other challenges. For example, specific embodiments support non-homogeneous XR user planes. Protocol Data Unit (PDU) set information in the user plane is defined in a backward-compatible manner such that when PDU set information is sent to a node that does not understand the parameter set, the node can ignore the parameter set and continue processing as if it were processing a normal radio (NR) data payload (i.e., without XR features). In non-homogeneous dual-connectivity deployments, PDU set information can be removed from the user plane when Next Generation Radio Access Network (NG-RAN) nodes or their corresponding nodes do not support XR features.

[0071] Specific embodiments are described more fully with reference to the accompanying drawings. The embodiments are provided by way of example only to convey the scope of the subject matter to those skilled in the art.

[0072] Specific implementations ensure that the NR user plane supports non-homogeneous deployments. PDU set-related information is introduced as an extension header to the New General Packet Radio Service (GPRS) Tunneling Protocol User Plane (GTP-U), and is defined, for example, as a "PDU set container".

[0073] 3GPP TS 29.281 defines the new GTP-U extension header as a "PDU set container". Its contents can be specified in TS 38.415, TS 38.425 or newer specifications.

[0074] For the PDU set container in TS 38.415, within the NG-RAN, extended headers can be sent in the G-PDU via the Xn-U and F1-U user plane interfaces. Extended headers can also be sent in the G-PDU via the N3 and N9 user plane interfaces between the NG-RAN and a User Plane Function (UPF) or between two UPFs.

[0075] The PDU collection container has a variable length, and its contents are specified in 3GPP TS 38.415. Figure 1 An example is shown in the image.

[0076] The PDU session user plane protocol resides 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 with one PDU session.

[0077] In the current specification, PDU session user plane protocol data is transmitted via the GTP-U protocol (more specifically, via the “GTP-U container” GTP-U extended header “PDU session container” as defined in 3GPP TS 29.281).

[0078] 3GPP TS 38.415 may include a new section to describe "PDU set containers". An example is shown below. *****************************************************************************

[0079] The PDU set UP layer expects the following services to come from the transport network layer:

[0080] - PDU set: Transmission of user plane PDUs.

[0081] 6.1 Basic Process

[0082] 6.1.1 Transmission of DL PDU Collection Information

[0083] 6.1.1.1 Successful operation

[0084] The purpose of the DL PDU set information transmission process is to send control information elements related to the PDU set from UPF / NG-RAN to NG-RAN.

[0085] Figure 6 -1: The successful transmission of DL PDU set information was reproduced as Figure 2 .

[0086] 6.1.2 Transmission of Information from UL PDU

[0087] 6.1.2.1 Successful operation

[0088] The purpose of the UL PDU set information transmission process is to send control information elements related to the PDU set from the NG-RAN to the UPF.

[0089] Figure 6 .-2: The successful transmission of UL PDU collection information was reproduced as Figure 3 .

[0090] 6.2 PDU Set of User Plane Protocol Elements

[0091] 6.2.1 Overview

[0092] In this document, the structure of a frame is described using a method similar to Figure 5 The diagram in .5.1-1 is used to specify this.

[0093] Figure 5 5.1-1: The example frame format is reproduced as follows Figure 4*****************************************************************************

[0094] 3GPP TS 38.425 may include a new section to describe "PDU Set RAN Containers". An example is shown below. *****************************************************************************

[0095] NR user plane protocol data is transmitted via the GTP-U protocol (more specifically, via the “PDU set RAN container” GTP-U extended header as defined in TS 29.281).

[0096] PDU collection RAN container transmission

[0097] Operation successful in version 6.3.1.x

[0098] The purpose of the PDU set RAN container transmission process is to provide NR-U specific PDU set information when sending user data carrying DL NR PDCP PDU set information from the node hosting the NR PDCP entity to the corresponding node.

[0099] The node hosting the NR PDCP entity can instruct the corresponding node to discard all NR PDCP PDU sets (up to and including the defined DL discard NR PDCP PDU set SN) or discard one or more blocks of the downlink NR PDCP PDU set.

[0100] Figure 6 3.1.x-1: Successful transmission of the PDU set RAN container was reproduced as follows Figure 5 .

[0101] 6.4 Elements of the NR User Plane Protocol for PDU Set Information Transmission

[0102] 6.4.1 Overview

[0103] In this document, the structure of a frame is as follows: Figure 6 As shown in the diagram, please specify. *********************************************************************************

[0104] For a "PDU set container", bits 7 and 8 of the next extended header type should be defined so that the receiver can handle unknown extended types.

[0105] In one embodiment, bit 7 is 0 and bit 8 is set to zero, meaning that the extended header does not need to be understood. The intermediate node should forward it to any receiving endpoint according to the GTP-U protocol. This is to support non-homogeneous deployments such as "supporting node -> non-supporting node -> supporting node" during handover between Session Management Functions (SMFs).

[0106] In another embodiment, bit 7 is 1 and bit 8 is set to zero, meaning that the extended header does not need to be understood. Intermediate nodes should discard the extended header content and not forward it to any receiver endpoint. Other extended headers should be processed independently of this extended header according to the GTP-U protocol. In this case, if any non-supporting node participates as an intermediate node, the PDU set-related parameters are discarded.

[0107] In certain embodiments, 3GPP's non-homogeneous deployment specifies that when using the new GTP-U extended header "PDU set container," the GTP-U extended header PDU session container should be used when operations are related to data payload transmission. Therefore, when sending data payloads from a supporting node to a non-supporting node, the non-supporting node can ignore the PDU set container and use the PDU session container as a fallback.

[0108] 3GPP TS 29.281 or TS 38.415 specifies that when using the new GTP-U extended header “PDU Set Container”, the GTP-U extended header PDU session container should be used during data payload transmission.

[0109] In some embodiments, to support non-homogeneous deployments under dual connectivity, such as when the primary node (MN) supports XR operations while the secondary node (SN) does not, gNB-CU-CP instructs the supporting node's gNB-CU-UP to remove the GTP-U extended header "PDU set container". This reduces processing in the non-supporting node and increases the speed of data payload processing.

[0110] An example of this implementation is that gNB-CU-CP instructs gNB-CU-UP to remove the "PDU set container" via E1AP.

[0111] In some embodiments, if PDU set information is introduced into the existing GTP-U extended header (e.g., “PDU session container”), the scheme described above for handling non-homogeneous deployments under dual connectivity should be applied to support Xn- and NG-based handover in the source NG-RAN node.

[0112] For example, below, PDU set-related information is included in "DL PDU Session Information (PDU Type 0)" within the existing PDU session container.

[0113] PDU set information can be introduced in PDU type 0 of TS 38.415. This frame format is defined to enable NG-RAN to receive control information elements associated with packets transmitted through the interface.

[0114] Figure 7 The corresponding downlink PDU session information frame is shown.

[0115] If the XR user plane is designed as described above, when sending data to non-supported nodes, the supporting gNB-CU-CP should instruct gNB-CU-UP to remove the "PDU set related" information from the DL PDU session information (PDU type 0).

[0116] The same specification is made in TS 38.425 for information transmitted from NG-RAN to another NG-RAN via Xn-U using a signal.

[0117] The frame format of the NR user plane protocol (DL user data (PDU type 0)) is defined, for example, to enable the corresponding node to detect lost NR-U packets and can be associated with the transmission of downlink packet data convergence protocol (PDCP) PDUs.

[0118] Figure 8 The corresponding downlink user data frames are shown. All information elements defined in the table below also apply to E-UTRA PDCP. With this understanding, each instance of NR PDCP can be replaced by E-UTRA PDCP.

[0119] Figure 9 An example of a communication system 100 according to some embodiments is shown. In this example, the communication system 100 includes: a telecommunications network 102, including an access network 104 such as a radio access network (RAN); and a core network 106, including one or more core network nodes 108. The access network 104 includes one or more access network nodes, such as network nodes 110a and 110b (one or more of which may generally be referred to as network node 110), or any other similar 3GPP access node or non-3GPP access point. Network node 110 facilitates direct or indirect connections of user equipment (UEs), such as connecting UEs 112a, 112b, 112c, and 112d (one or more of which may generally be referred to as UE 112) to the core network 106 via one or more wireless connections.

[0120] Examples of wireless communication via wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for transmitting information without using wiring, cables, or other conductors. Furthermore, in various embodiments, communication system 100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that can facilitate or participate in the communication of data and / or signals (whether via wired or wireless connections). Communication system 100 may include any type of communication, telecommunications, data, cellular, radio network, and / or other similar system, and / or interface with any type of communication, telecommunications, data, cellular, radio network, and / or other similar system.

[0121] UE 112 can be any of a variety of communication devices, including wireless devices that are arranged, configured, and / or operable to communicate wirelessly with network node 110 and other communication devices. Similarly, network node 110 is arranged, capable, configured, and / or operable to communicate directly or indirectly with UE 112 and / or with other network nodes or devices in telecommunication network 102 to implement and / or provide network access (e.g., wireless network access) and / or to perform other functions in telecommunication network 102 (e.g., management).

[0122] In the depicted example, core network 106 connects network node 110 to one or more hosts (such as host 116). These connections can be direct connections or indirect connections via one or more intermediate networks or devices. In other examples, network nodes may be directly coupled to hosts. Core network 106 includes one or more core network nodes (e.g., core network node 108) that are formed together with hardware and software components. The characteristics of these components may be substantially similar to those described with respect to UEs, network nodes, and / or hosts, such that the description is generally applicable to the corresponding components of core network node 108. Example core network nodes include the functions of one or more of the following: 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 Unhiding Function (SIDF), Unified Data Management (UDM), Security Edge Protection Agent (SEPP), Network Open Function (NEF), and / or User Plane Function (UPF).

[0123] Host 116 may be owned or under the control of a service provider other than the operator or provider of access network 104 and / or telecommunications network 102, and may be operated by or on behalf of the service provider. Host 116 may host a variety of applications to provide one or more services. Examples of such applications include real-time and pre-recorded audio / video content, data collection services (e.g., retrieving and compiling data about various environmental conditions detected by multiple UEs), analytics functions, social media, functions for controlling or otherwise interacting with remote devices, functions for alarms and monitoring centers, or any other such functions performed by a server.

[0124] As a whole, Figure 9 The communication system 100 enables connections between the UE, network nodes, and hosts. In this sense, the communication system can be configured to operate according to predefined rules or procedures, such as specific standards, including but 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 standard (WiFi); and / or any other suitable wireless communication standards, such as Global Microwave Access Interoperability (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.

[0125] In some examples, telecommunications network 102 is a cellular network implementing 3GPP standardized features. Therefore, telecommunications network 102 can support network slicing to provide different logical networks to different devices connected to it. For example, telecommunications network 102 can 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) / massive IoT services to yet another UE.

[0126] In some examples, UE 112 is configured to send and / or receive information without direct human interaction. For example, the UE may be designed to send information to access network 104 according to a predetermined schedule when triggered by internal or external events or in response to a request from access network 104. Additionally, the UE may be configured to operate in single-RAT mode, multi-RAT mode, or multi-standard mode. For example, the UE may operate using any one or a combination of Wi-Fi, NR (New Radio), and LTE, i.e., configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved UMTS Terrestrial Radio Access Network) New Radio Dual Connectivity (EN-DC).

[0127] In this example, hub 114 communicates with 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, hub 114 may be a controller, router, content source and analyzer, or any other communication device described herein relating to the UE. For example, hub 114 may be a broadband router that enables the UE to access core network 106. As another example, hub 114 may be a controller that sends commands or instructions to one or more actuators of the UE. Commands or instructions may be received from the UE, network node 110, or via executable code, scripts, procedures, or other instructions in hub 114. As another example, hub 114 may be a data collector that acts as a temporary storage device for UE data, and in some embodiments, data analysis or other processing may be performed. As another example, hub 114 may be a content source. For example, for a UE acting as a VR headset, display, speaker, or other media delivery device, hub 114 can retrieve VR assets, video, audio, or other media or data related to perceived information via a network node, and then provide them directly to the UE after performing local processing and / or adding additional local content. In yet another example, hub 114 acts as a proxy server or orchestrator for the UE, particularly if one or more UEs are low-power IoT devices.

[0128] Hub 114 may have a persistent / persistent or intermittent connection to network node 110b. Hub 114 may also allow different communication schemes and / or scheduling between hub 114 and UEs (e.g., UEs 112c and / or 112d) and between hub 114 and core network 106. In other examples, hub 114 is connected to core network 106 and / or one or more UEs via a wired connection. Furthermore, hub 114 may be configured to connect to an M2M service provider via access network 104 and / or to another UE via a direct connection. In some scenarios, a UE may establish a wireless connection with network node 110 while still being connected via hub 114 through a wired or wireless connection. In some embodiments, hub 114 may be a dedicated hub, i.e., a hub whose primary function is to route communication from network node 110b to UE / to network node 110b. In other embodiments, hub 114 may be a non-dedicated hub, i.e., a device capable of operating to route communication between the UE and network node 110b, but additionally capable of operating as a communication start point and / or endpoint for certain data channels.

[0129] Figure 10 A UE 200 according to some embodiments is illustrated. As used herein, a UE refers to a device capable of, configured, positioned, and / or operable to wirelessly communicate with network nodes and / or other UEs. Examples of UEs include, but are not limited to, smartphones, mobile phones, cellular phones, Voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, gaming consoles or devices, music storage devices, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablet computers, laptop computers, laptop embedded devices (LEEs), laptop-mounted devices (LMEs), smart devices, wireless client devices (CPEs), vehicle-mounted or vehicle-embedded / integrated wireless devices, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including Narrowband Internet of Things (NB-IoT) UEs, Machine Type Communication (MTC) UEs, and / or Enhanced MTC (eMTC) UEs.

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

[0131] UE 200 includes processing circuitry 202, which is operatively coupled via bus 204 to input / output interface 206, power supply 208, memory 210, communication interface 212, and / or any other component or any combination thereof. Some UEs may utilize... Figure 2 The components shown may be all or a subset. The level of integration between components can vary depending on the UE. Furthermore, some UEs may include multiple instances of components, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0132] Processing circuitry 202 is configured to process instructions and data and can be configured to implement any sequential state machine operable to execute instructions stored in memory 210 as machine-readable computer processes. Processing circuitry 202 can be implemented as: one or more hardware-implemented state machines (e.g., implemented with discrete logic, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer processes, general-purpose processors (e.g., microprocessors or digital signal processors (DSPs)) together with appropriate software; or any combination of the foregoing. For example, processing circuitry 202 may include multiple central processing units (CPUs).

[0133] In the example, input / output interface 206 can be configured to provide one or more interfaces to input devices, output devices, or one or more input and / or output devices. Examples of output devices include speakers, sound cards, video cards, displays, monitors, printers, actuators, transmitters, smart cards, other output devices, or any combination thereof. Input devices can allow users to capture information into UE 200. Examples of input devices include touch-sensitive or presence-sensitive displays, cameras (e.g., digital cameras, digital camcorders, webcams, etc.), microphones, sensors, mice, trackballs, directional keyboards, touchpads, scroll wheels, smart cards, etc. Presence-sensitive displays may include capacitive or resistive touch sensors to sense input from the user. Sensors may be, for example, accelerometers, gyroscopes, tilt sensors, force sensors, magnetometers, optical sensors, proximity sensors, biometric sensors, etc., or any combination thereof. Output devices can use the same type of interface port as input devices. For example, a Universal Serial Bus (USB) port can be used to provide both input and output devices.

[0134] In some embodiments, power supply 208 is configured as a battery or battery pack. Other types of power sources can be used, such as external power sources (e.g., power outlets), photovoltaic devices, or batteries. Power supply 208 may also include power supply circuitry for delivering power from power supply 208 itself and / or external power sources to various parts of UE 200 via input circuitry or an interface such as a power cable. Power delivery may be used, for example, for charging power supply 208. The power supply circuitry may perform any formatting, conversion, or other modifications on the power from power supply 208 to suit the power for the respective components of UE 200 to which it is supplied power.

[0135] 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), disk, optical disk, hard disk, removable magnetic tape, flash drive, etc. In one example, memory 210 includes one or more application processes 214, such as an operating system, web browser application, widgets, utility engines, or other applications, and corresponding data 216. Memory 210 may store any one or a combination of various operating systems used by UE 200.

[0136] Memory 210 can be configured to include multiple physical drive units, such as a redundant array of independent disks (RAID), flash memory, a USB flash drive, an external hard drive, a thumb drive, a pen drive, a key drive, a high-density digital multifunction optical disc (HD-DVD) drive, an internal hard drive, a Blu-ray disc drive, a holographic digital data storage (HDDS) disc drive, an external mini dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro DIMM SDRAM, smart card memory (e.g., a tamper-proof module in the form of a universal integrated circuit card (UICC), including one or more subscriber identification modules (SIMs), such as USIM and / or ISIM), other memory, or any combination thereof. The UICC may be, for example, an embedded UICC (eUICC), an integrated UICC (iUICC), or a removable UICC commonly referred to as a "SIM card." Memory 210 can allow UE 200 to access instructions, applications, etc., stored on temporary or non-temporary storage media to offload or upload data. Articles such as those utilizing communication systems may be tangibly embodied in or contained in memory 210, which may be or include a device-readable storage medium.

[0137] Processing circuitry 202 can be configured to communicate with an access network or other network using communication interface 212. Communication interface 212 may include one or more communication subsystems and may include antenna 222 or be communicatively coupled to antenna 222. Communication interface 212 may include one or more transceivers for communication, such as communication with one or more remote transceivers capable of wireless communication (e.g., another UE or a network node in the access network). Each transceiver may include a transmitter 218 and / or a receiver 220 suitable for providing network communication (e.g., optical, electrical, frequency allocation, etc.). Furthermore, transmitter 218 and receiver 220 may be coupled to one or more antennas (e.g., antenna 222) and may share circuitry, software, or firmware, or alternatively, be implemented separately.

[0138] In the illustrated embodiment, the communication functions of the communication interface 212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, near-field communication, location-based communication (e.g., using a Global Positioning System (GPS) to determine location), another type of communication function, or any combination thereof. Communication may be implemented according to one or more communication protocols and / or standards (e.g., IEEE 802.11, Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, Transmission Control Protocol / Internet Protocol (TCP / IP), Synchronous Optical Network (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), etc.).

[0139] Regardless of the type of sensor, the UE can provide the output of data captured by its sensors via its communication interface 212 through a wireless connection with a network node. Data captured by the UE's sensors can be transmitted via another UE through the same wireless connection. The output can be periodic (e.g., every 15 minutes if it reports the sensed temperature), random (e.g., to balance the load of reports from several sensors), responsive to a triggering event (e.g., sending an alarm when humidity is detected), responsive to a request (e.g., a user-initiated request), or a continuous stream (e.g., real-time video feed of a patient).

[0140] As another example, the UE includes actuators, motors, or switches associated with a communication interface configured to receive wireless input from a network node via a wireless connection. The state of the actuator, motor, or switch can change in response to the received wireless input. For example, the UE may include a motor that adjusts the control surfaces or rotors of a flying drone based on the received input, or adjusts a robotic arm performing a medical procedure based on the received input.

[0141] When the UE is in the form of an Internet of Things (IoT) device, the UE can be a device used in one or more application areas, including but not limited to urban wearable technology, extended industrial applications, and healthcare. Non-limiting examples of such IoT devices include or embedded in the following devices: connected refrigerators or freezers, televisions, connected lighting devices, electricity meters, robotic vacuum cleaners, voice-controlled smart speakers, home security cameras, motion detectors, thermostats, smoke detectors, door and window sensors, flood / humidity sensors, electronic door locks, connected doorbells, air conditioning systems (such as heat pumps), autonomous vehicles, surveillance systems, weather monitoring devices, vehicle parking monitoring devices, electric vehicle charging stations, smartwatches, fitness trackers, head-mounted displays for augmented reality (AR) or virtual reality (VR), wearable devices for haptic or sensory enhancement, sprinklers, animal or item tracking devices, sensors for monitoring plants or animals, industrial robots, unmanned aerial vehicles (UAVs), and any kind of medical device (such as heart rate monitors or remote-controlled surgical robots). In addition to the above... Figure 2 In addition to the other components described in UE 200 shown, UEs in the form of IoT devices also include circuitry and / or software depending on the intended application of the IoT device.

[0142] As another specific example, in an IoT scenario, a UE can represent a machine or other device that performs monitoring and / or measurement and sends the results of such monitoring and / or measurement to another UE and / or network node. In this case, the UE can be an M2M device, which can be referred to as an MTC device in the 3GPP context. As a specific example, this UE can implement the 3GPP NB-IoT standard. In other scenarios, a UE can represent a vehicle (e.g., a car, bus, truck, ship, and aircraft) or other device capable of monitoring and / or reporting its operational status or other functions associated with its operation.

[0143] In practice, any number of UEs can be used together for a single use case. For example, the first UE can be a drone or integrated into a drone, and provides the drone's speed information (obtained via a speed sensor) to a second UE, which is a remote controller for operating the drone. When the user makes a change from the remote controller, the first UE can adjust the throttle on the drone (e.g., by controlling the actuator) to increase or decrease the drone's speed. The first UE and / or the second UE can also include more than one of the functions described above. For example, the UE can include sensors and actuators, and handle data communication between both the speed sensor and the actuator.

[0144] Figure 11A network node 300 according to some embodiments is illustrated. As used herein, a network node refers to a device that is capable of, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or devices in a telecommunications network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points) and base stations (BSs) (e.g., radio base stations, NodeBs, evolved NodeBs (eNBs) and NR NodeBs (gNBs)).

[0145] Base stations can be classified based on the coverage they provide (or, in other words, their transmission power levels); therefore, depending on the coverage provided, a base station can be called a femtobase, picobase, microbase, or macrobase. A base station can be a relay node or a relay donor for control relays. Network nodes can also include one or more (or all) portions of a distributed radio base station, such as centralized digital units and / or remote radio units (RRUs), sometimes referred to as remote radio headends (RRHs). These remote radio units can be integrated with antennas to form an antenna-integrated radio, or they can be independent of antenna integration. A portion of a distributed radio base station can also be referred to as a node in a distributed antenna system (DAS).

[0146] Other examples of network nodes include multi-transmitter point (multi-TRP) 5G access nodes, multi-standard radio (MSR) devices (e.g., MSR BS), network controllers (e.g., radio network controllers (RNC) or base station controllers (BSC)), base transceiver stations (BTS), transmitter points, transmitter nodes, multi-cell / multicast coordination entities (MCE), operations and maintenance (O&M) nodes, operations support system (OSS) nodes, self-organizing network (SON) nodes, location nodes (e.g., evolved Serving Mobility Location Center (E-SMLC)) and / or minimized drive test (MDT).

[0147] Network node 300 includes processing circuitry 302, memory 304, communication interface 306, and power supply 308. Network node 300 may consist of multiple physically separate components (e.g., Node B components and RNC components, BTS components and BSC components, etc.), each with its own corresponding components. In some scenarios where network node 300 includes multiple separate components (e.g., BTS and BSC components), one or more separate components may be shared among several network nodes. For example, a single RNC can control multiple NodeBs. In such scenarios, each unique “NodeB and RNC pair” can be considered a single, separate network node in some cases. In some embodiments, network node 300 may be configured to support multiple Radio Access Technologies (RATs). In such embodiments, some components may be replicated (e.g., separate memory 304 exists for different RATs) and some components may be reused (e.g., the same antenna 310 may be shared by different RATs). Network node 300 may also include multiple sets of various components shown for different wireless technologies (e.g., GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, RFID, or Bluetooth wireless technologies). These wireless technologies may be integrated into the same or different chips or chipsets and other components within network node 300.

[0148] The processing circuitry 302 may include one or more of the following: a microprocessor, a controller, a central processing unit, a digital signal processor, an application-specific integrated circuit, a field-programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or coding logic, operable to provide network node 300 functionality, either alone or in combination with other network node 300 components (e.g., memory 304).

[0149] 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 a radio frequency (RF) transceiver circuitry 312 and a baseband processing circuitry 314. In some embodiments, the RF transceiver circuitry 312 and the baseband processing circuitry 314 may be on separate chips (or chipsets), boards, or units (e.g., radio units and digital units). In alternative embodiments, some or all of the RF transceiver circuitry 312 and the baseband processing circuitry 314 may be on the same chip or chipset, board, or unit group.

[0150] Memory 304 may include any form of volatile or non-volatile computer-readable memory, including but not limited to permanent storage devices, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drives, optical discs (CDs), or digital video discs (DVDs)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory device that stores information, data, and / or instructions that can be used by processing circuitry 302. Memory 304 may store any suitable instructions, data, or information, including computer processes, software, applications including logic, rules, codes, tables, and / or other instructions that can be executed by processing circuitry 302 and used by network node 300. Memory 304 may be used to store any calculations performed by processing circuitry 302 and / or any data received via communication interface 306. In some embodiments, processing circuitry 302 and memory 304 are integrated together.

[0151] Communication interface 306 is used for wired or wireless communication of signaling and / or data between network nodes, access networks, and / or UEs. As shown, communication interface 306 includes a port / terminal 316 for transmitting and receiving data to and from the network, for example, via a wired connection. Communication interface 306 also includes radio front-end circuitry 318, which may be coupled to antenna 310, or in some embodiments to a portion of antenna 310. Radio front-end circuitry 318 includes a filter 320 and an amplifier 322. Radio front-end circuitry 318 may be connected to antenna 310 and processing circuitry 302. Radio front-end circuitry 318 may be configured to modulate the signal transmitted between antenna 310 and processing circuitry 302. Radio front-end circuitry 318 may receive digital data to be transmitted to other network nodes or UEs via a wireless connection. Radio front-end circuitry 318 may use a combination of filter 320 and / or amplifier 322 to convert the digital data into a radio signal with appropriate channel and bandwidth parameters. The radio signal may then be transmitted via antenna 310. Similarly, when data is received, antenna 310 can collect radio signals, which are then converted into digital data by radio front-end circuitry 318. The digital data can then be passed to processing circuitry 302. In other embodiments, the communication interface may include different components and / or different combinations of components.

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

[0153] Antenna 310 may include one or more antennas or antenna arrays configured to transmit and / or receive wireless signals. Antenna 310 may be coupled to radio front-end circuitry 318 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In some embodiments, antenna 310 is decoupled from network node 300 and may be connected to network node 300 via an interface or port.

[0154] Antenna 310, communication interface 306, and / or processing circuitry 302 can be configured to perform any receive operation and / or certain acquire operation described herein by a network node. Any information, data, and / or signals can be received from the UE, another network node, and / or any other network device. Similarly, antenna 310, communication interface 306, and / or processing circuitry 302 can be configured to perform any transmit operation described herein by a network node. Any information, data, and / or signals can be transmitted to the UE, another network node, and / or any other network device.

[0155] Power supply 308 provides power to the various components of network node 300 in a form suitable for the various components (e.g., at the voltage and current levels required by each respective component). Power supply 308 may also include or be coupled to power management circuitry to supply power to the components of network node 300 for performing the functions described herein. For example, network node 300 may be connected to an external power source (e.g., mains, power outlet) via input circuitry or an interface (e.g., cable), thereby supplying power to the power circuitry of power supply 308. As another example, power supply 308 may include a power source in the form of a battery or battery pack, which is connected to or integrated into the power circuitry. The battery can provide backup power if the external power source fails.

[0156] Embodiments of network node 300 may include more than Figure 11Additional components shown are provided to offer certain aspects of the functionality of the network node, including any of the functions described herein and / or any functionality required to support the topics described herein. For example, network node 300 may include a user interface device to allow information to be input into and output from network node 300. This allows users to perform diagnostic, maintenance, repair, and other management functions on network node 300.

[0157] Figure 12 The block diagram of host 400 is based on the various aspects described herein, and host 400 may be... Figure 1 The embodiment of host 116. As used herein, host 400 can be or include various combinations of hardware and / or software, including processing resources in a standalone server, blade server, cloud-implemented server, distributed server, virtual machine, container, or server cluster. Host 400 can provide one or more services to one or more UEs.

[0158] Host 400 includes processing circuitry 402 operably coupled via bus 404 to input / output interface 406, network interface 408, power supply 410, and memory 412. Other components may be included in other embodiments. The features of these components may be substantially similar to those with respect to the previous figures (e.g., Figure 10 and Figure 3 The characteristics described for the device make its description generally applicable to the corresponding components of host 400.

[0159] Memory 412 may include one or more computer programs, including data 416 and one or more host applications 414. Data 416 may include user data, such as data generated by the UE for the host 400, or data generated by the host 400 for the UE. Embodiments of host 400 may utilize only a subset or all of the illustrated components. Host application 414 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Universal 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 various categories, types, or implementations of UEs (e.g., mobile phones, desktop computers, wearable display systems, head-up display systems). Host application 414 may also provide user authentication and authorization checks and may periodically report health status, routing, and content availability to a central node (such as a device in the core network or a device at the edge of the core network). Therefore, host 400 can select and / or indicate different hosts for the UE to use for over-the-top services. Host application 414 can support various protocols, such as HTTP Live Streaming (HLS), Real-time Messaging Protocol (RTMP), Real-time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.

[0160] Figure 13 This is a block diagram illustrating a virtualization environment 500 in which functionality implemented by some embodiments can be virtualized. In this context, virtualization means creating a virtual version of an apparatus or device that may include a virtualization hardware platform, storage devices, and network resources. As used herein, virtualization can be applied to any device or component thereof described herein, and involves at least a portion of its functionality being implemented as an implementation of one or more virtual components. Some or all of the functionality described herein can be implemented as virtual components executed by one or more virtual machines (VMs) in one or more virtual environments 500 hosted by one or more hardware nodes (e.g., hardware computing devices operating as network nodes, UEs, core network nodes, or hosts). Furthermore, in embodiments where virtual nodes do not require radio connectivity (e.g., core network nodes or hosts), the nodes can be fully virtualized.

[0161] Application 502 (which may alternatively be referred to as a software instance, virtual device, network function, virtual node, virtual network function, etc.) operates in a virtualized environment Q400 to implement some of the features, functions, and / or benefits of some embodiments disclosed herein.

[0162] Hardware 504 includes processing circuitry, memory storing software and / or instructions executable by the hardware processing circuitry, and / or other hardware devices described herein (such as network interfaces, input / output interfaces, etc.). The software can 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 generally be referred to as VM 508), and / or perform any functions, features, and / or benefits described in relation to some embodiments described herein. Virtualization layer 506 can present a virtual operating platform to VM 508, which appears as network hardware.

[0163] VM 508 includes virtual processing, virtual memory, virtual network or interface, and virtual storage, and can be operated by a corresponding virtualization layer 506. Different embodiments of instances of virtual device 502 can be implemented on one or more VMs 508, and these implementations can be carried out in different ways. In some contexts, hardware virtualization is referred to as Network Functions Virtualization (NFV). NFV can be used to unify numerous network device types onto industry-standard high-capacity server hardware, physical switches, and physical storage that can reside in data centers and customer premises equipment (CPE).

[0164] In the context of NFV, VM 508 can be a software implementation of a physical machine, whose operating procedures are executed as if on a physical, non-virtualized machine. Each VM 508, along with the hardware portion of hardware 504 that executes that VM (whether it is dedicated hardware for that VM and / or hardware shared by that VM with other VMs), forms a separate virtual network element. Still within the context of NFV, the virtual network function is responsible for handling the specific network functions operating within one or more VMs 508 on top of hardware 504 and corresponding to application 502.

[0165] Hardware 504 can be implemented in a standalone network node with general or specific components. Hardware 504 may implement some functions via virtualization. Alternatively, hardware 504 may be part of a larger hardware cluster (e.g., in a data center or CPE) where many hardware nodes work together and are managed by management and orchestration 510, which in particular oversees the lifecycle management of application 502. In some embodiments, hardware 504 is coupled to one or more radio units, each radio unit including one or more transmitters and one or more receivers that can be coupled to one or more antennas. The radio units may communicate directly with other hardware nodes via one or more suitable network interfaces and may be used in conjunction with virtual components to provide radio capabilities to virtual nodes (e.g., radio access nodes or base stations). In some embodiments, some signaling may be provided by using a control system 512, which may alternatively be used for communication between hardware nodes and radio units.

[0166] Figure 14 A communication diagram is shown showing host 602 communicating with UE 606 via network node 604 through a partial wireless connection according to some embodiments. Reference will now be made to... Figure 13 Describe the UE discussed in the preceding paragraphs (e.g., Figure 9 UE 112a and / or Figure 10 UE 200), network nodes (e.g., Figure 9 Network node 110a and / or Figure 11 Network node 300) and host (e.g., Figure 9 Host 116 and / or Figure 12 Example implementations of the host 400 according to various embodiments.

[0167] Similar to host 400, embodiments of host 602 include hardware such as a communication interface, processing circuitry, and memory. Host 602 also includes software stored in or accessible by host 602 and executable by the processing circuitry. This software includes a host application operable to provide services to a remote user, such as UE 606 connected via an over-the-top (OTT) connection 650 extending between UE 606 and host 602. When providing services to a remote user, the host application can provide user data transmitted using OTT connection 650.

[0168] Network node 604 includes hardware that enables it to communicate with host 602 and UE 606. Connection 660 can be a direct connection or via a core network (such as...). Figure 1The connection to the core network (106) and / or one or more other intermediate networks (e.g., one or more public, private, or hosted networks). For example, an intermediate network could be a backbone network or the Internet.

[0169] UE 606 includes hardware and software, the software being stored in or accessible by UE 606 and executable by the UE's processing circuitry. This software includes client applications (e.g., web browsers or carrier-specific "applications") operable to provide services to human or non-human users via UE 606, supported by host 602. In host 602, the executing host application can communicate with the executing client application via OTT connection 650, which terminates between UE 606 and host 602. When providing services to a user, the UE's client application can receive request data from the host application of the host and, in response to the request data, provide user data. OTT connection 650 can send both request data and user data. The UE's client application can interact with the user to generate user data provided to the host application via OTT connection 650.

[0170] OTT connection 650 can extend via connection 660 between host 602 and network node 604 and via wireless connection 670 between network node 604 and UE 606 to provide connectivity between host 602 and UE 606. Connection 660 and wireless connection 670, which provide OTT connection 650, have been abstractly drawn to illustrate communication between host 602 and UE 606 via network node 604, without explicitly involving any intermediate devices and the precise routing of messages via these devices.

[0171] As an example of sending data via OTT connection 650, in step 608, host 602 provides user data, which can be performed by executing a host application. In some embodiments, the user data is associated with a specific human user interacting with UE 606. In other embodiments, the user data is associated with UE 606, which shares data with host 602 without explicit human interaction. In step 610, host 602 initiates a transmission to UE 606 carrying the user data. Host 602 may initiate the transmission in response to a request sent by UE 606. This request may be caused by human interaction with UE 606 or by the operation of a client application executed on UE 606. In accordance with the teachings of the embodiments described throughout this disclosure, this transmission may be carried out via network node 604. Therefore, in step 612, in accordance with the teachings of the embodiments described throughout this disclosure, network node 604 sends the user data carried in the transmission initiated by host 602 to UE 606. In step 614, UE 606 receives user data carried in the transmission, which can be performed by a client application running on UE 606, which is associated with a host application running by host 602.

[0172] In some examples, UE 606 executes a client application that provides user data to host 602. User data can be provided as a response to data received from host 602. Therefore, in step 616, UE 606 can provide user data, which can be done by executing the client application. When providing user data, the client application may also consider user input received from a user via the input / output interface of UE 606. Regardless of the specific manner in which user data is provided, in step 618, UE 606 initiates a transmission of user data to host 602 via network node 604. In step 620, in accordance with the teachings of the embodiments described throughout this disclosure, network node 604 receives user data from UE 606 and initiates transmission of the received user data to host 602. In step 622, host 602 receives the user data carried in the transmission initiated by UE 606.

[0173] One or more embodiments in various implementations improve the performance of OTT services provided to UE 606 using OTT connection 650, in which wireless connection 670 forms the final part. More specifically, the teachings of these embodiments can improve data rates and latency, thereby providing benefits such as reduced user wait time, better responsiveness, and better QoE.

[0174] In the example scenario, host 602 can collect and analyze plant status information. As another example, host 602 can process audio and video data that may have been retrieved from the UE for creating mappings. As another example, host 602 can collect and analyze real-time data to help control vehicle congestion (e.g., control service lights). As another example, host 602 can store surveillance video uploaded by the UE. As another example, host 602 can store or control access to media content such as video, audio, VR, or AR, which can be broadcast, multicast, or unicast to the UE. As other examples, host 602 can be used for energy pricing, remote control of non-time-critical power loads to balance generation demand, location services, presentation services (e.g., compiling charts based on data collected from remote devices), or any other function that collects, retrieves, stores, analyzes, and / or transmits data.

[0175] In some examples, a measurement process may be provided for the purpose of monitoring improved data rates, latency, and other factors in one or more embodiments. Optional network functions may also be present for reconfiguring the OTT connection 650 between host 602 and UE 606 in response to changes in measurement results. The measurement process and / or the network functions for reconfiguring the OTT connection may be implemented in the software and hardware of host 602 and / or UE 606. In some embodiments, sensors (not shown) may be deployed in or associated with other devices traversed by the OTT connection 650; the sensors may participate in the measurement process by providing values ​​of the monitored quantities exemplified above or by providing values ​​of other physical quantities from which the software can calculate or estimate the monitored quantities. Reconfiguration of the OTT connection 650 may include message formatting, retransmission settings, preferred routing, etc.; reconfiguration does not require a direct change in the operation of network node 604. Such processes and functions may be known and practiced in the art. In some embodiments, the measurement may involve proprietary UE signaling that facilitates host 602's measurement of throughput, propagation time, latency, etc. Measurements can be achieved by having the software use an OTT connection 650 to send messages (especially empty or “virtual” messages) while monitoring propagation time, errors, etc.

[0176] While the computing devices described herein (e.g., UE, network node, host) may include combinations of the hardware components shown, other embodiments may include computing devices with different combinations of components. It should be understood that these computing devices may include any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. The determination, calculation, acquisition, or similar operations described herein may be performed by processing circuitry that processes information in ways such as: converting acquired information into other information, comparing the acquired or converted information with information stored in a network node, and / or performing one or more operations based on the acquired or converted information, and making determinations based on the results of said processing. Furthermore, although components are depicted as single boxes located within larger boxes or nested within multiple boxes, in practice, a computing device may include multiple different physical components constituting a single illustrated component, and functionality may be partitioned between individual components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of a component may be partitioned between processing circuitry and the communication interface. In another example, the non-computationally intensive functions of any such component may be implemented in software or firmware, and the computationally intensive functions may be implemented in hardware.

[0177] In some embodiments, some or all of the functions described herein may be provided by processing circuitry that executes instructions stored in memory, which in some 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 functions may be provided by the processing circuitry, for example, in a hard-wired manner, without executing instructions stored on a separate or discrete device-readable storage medium. In any of these particular embodiments, the processing circuitry may be configured to perform the described functions regardless of whether instructions stored on a non-transitory computer-readable storage medium are executed. The benefits provided by such functions are not limited to the individual processing circuitry or other components of the computing device, but are enjoyed holistically by the computing device and / or generally by the end user and wireless network.

[0178] Figure 15 This is a flowchart illustrating example methods in a network node according to certain embodiments. In a particular embodiment, Figure 15 One or more steps can be made by regarding Figure 11 The network node 300 described is used for execution. This network node is used in the NR user plane to support operations of non-homogeneous deployments added to the user plane.

[0179] The method begins at step 1512, where a first network node (e.g., network node 300) constructs a General Packet Radio Service (GPRS) Tunneling Protocol User Plane (GTP-U) packet including an extended header that includes a PDU set container. The PDU set container includes an indication that the second network node can ignore the PDU set container if the second network node does not support PDU set functionality.

[0180] In a particular embodiment, the indication is part of the Next Extended Header Type field of the GTP-U Extended Header. The indication may include two bits of the Next Extended Header Type field of the GTP-U Extended Header.

[0181] In a particular embodiment, the method further includes transmitting data payload using a GTP-U extended header PDU session container.

[0182] In a particular embodiment, the first network node includes a radio access network (RAN) node, and the second network node includes one of a RAN node and a user plane function (UPF) node.

[0183] At step 1514, the first network node sends a GTP-U packet to the second network node.

[0184] Can be Figure 15 Method 1500 can be modified, added to, or omitted. Additionally, Figure 15 One or more steps in the method can be executed in parallel or in any suitable order.

[0185] Figure 16 This is a flowchart illustrating another example method in a network node according to certain embodiments. In a particular embodiment, Figure 16 One or more steps can be made by regarding Figure 11 The network node 300 described is used for execution. This network node is used in the NR user plane to support operations of non-homogeneous deployments added to the user plane.

[0186] The method begins at step 1612, where a first network node (e.g., network node 300) receives a GTP-U packet from a second network node, including an extended header that includes a PDU set container. The PDU set container includes an indication that the first network node can ignore the PDU set container if it does not support PDU set functionality.

[0187] At step 1614, based on this instruction, the first network node forwards GTP-U packets with PDU set containers to the third network node; or forwards GTP-U packets without PDU set containers to the third network node.

[0188] In a particular embodiment, the first network node includes a radio access network (RAN) node, and the second network node includes a RAN node.

[0189] In this example, the first network node can refer to... Figure 15 The second network node is described, and the second network node can refer to... Figure 15 The first network node described.

[0190] Can be Figure 16 Method 1600 can be modified, added to, or omitted. Additionally, Figure 16 One or more steps in the method can be executed in parallel or in any suitable order.

[0191] Figure 17 This is a flowchart illustrating an example method in a gNB central unit control plane (gNB-CU-CP) network node according to certain embodiments. In a particular embodiment, Figure 17 One or more steps can be made by regarding Figure 11 The network node 300 described is used for execution. This network node is used in the NR user plane to support operations of non-homogeneous deployments added to the user plane.

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

[0193] At step 1714, the network node sends an instruction to the gNB central unit user plane (gNB-CU-UP) associated with gNB-CU-CP to remove PDU set association information from the packet before sending the packet to the second network node.

[0194] In a particular embodiment, the first network node operates under dual connectivity, and the second network node includes a secondary network node.

[0195] Can be Figure 17 Method 1700 can be modified, added to, or omitted. Additionally, Figure 17 One or more steps in the method can be executed in parallel or in any suitable order.

[0196] Figure 18 This is a flowchart illustrating an example method in a gNB Central Unit User Plane (gNB-CU-UP) network node according to certain embodiments. In a particular embodiment, Figure 18 One or more steps can be made by regarding Figure 11 The network node 300 described is used for execution. This network node is used in the NR user plane to support operations of non-homogeneous deployments added to the user plane.

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

[0198] At step 1814, the network node sends a packet to the second network node containing the packet containing the removed PDU set association information.

[0199] In a particular embodiment, the first network node operates under dual connectivity, and the second network node includes a secondary network node.

[0200] Can be Figure 18 Method 1800 can be modified, added to, or omitted. Additionally, Figure 18 One or more steps in the method can be executed in parallel or in any suitable order.

[0201] The foregoing description sets forth many specific details. However, it should be understood that embodiments can be implemented without these specific details. In other instances, well-known circuits, structures, and techniques have not been shown in detail so as not to obscure the understanding of this description. Using the included description, those skilled in the art will be able to achieve appropriate functionality without excessive experimentation.

[0202] References to "an embodiment," "embodiment," "example embodiment," etc., in the specification indicate that the described embodiment may include a particular feature, structure, or characteristic, but each embodiment may not necessarily include that particular feature, structure, or characteristic. Furthermore, these phrases do not necessarily refer to the same embodiment. Moreover, when a particular feature, structure, or characteristic is described in connection with an embodiment, it should be considered that implementing such a feature, structure, or characteristic in conjunction with other embodiments (whether explicitly described or not) is within the knowledge of those skilled in the art.

[0203] Although this disclosure has been described with reference to specific embodiments, changes and arrangements of the embodiments will be apparent to those skilled in the art. Therefore, the above description of the embodiments does not limit this disclosure. Other changes, substitutions, and modifications may also be made without departing from the scope of this disclosure as defined by the appended claims.

[0204] Some example implementations are described below.

[0205] Group A Examples

[0206] 1. A method performed by a wireless device, the method comprising:

[0207] - Any of the wireless device steps, features, or functions described above, whether alone or in combination with the other steps, features, or functions described above.

[0208] 2. The method according to any of the foregoing embodiments further includes one or more of the additional wireless device steps, features, or functions described above.

[0209] 3. The method according to any of the foregoing embodiments further includes:

[0210] -Provide user data; and

[0211] - User data is forwarded to the host computer via transmission to the base station.

[0212] Group B Implementation Examples

[0213] 4. A method performed by a base station for operating a new radio (NR) user plane to support non-homogeneous deployment, the method comprising:

[0214] - Send GTP-U packets including an extended header with a PDU set container as defined herein.

[0215] 5. A method performed by a base station for operating a new radio (NR) user plane to support non-homogeneous deployment, the method comprising:

[0216] - Receive GTP-U packets including an extended header with a PDU set container as defined herein.

[0217] 6. A method performed by a base station, the method comprising:

[0218] -Any step, feature, or function described above regarding the base station, whether alone or in combination with the other steps, features, or functions described above.

[0219] 7. The method according to the foregoing embodiments further includes one or more of the above-described additional base station steps, features, or functions.

[0220] 8. The method according to any of the foregoing embodiments further includes:

[0221] - Obtaining user data; and

[0222] - Forward user data to the host computer or wireless device.

[0223] Group C Implementation Examples

[0224] 9. A mobile terminal, comprising:

[0225] - Processing circuitry, configured to perform any of the steps described in any of the Group B embodiments; and

[0226] - Power supply circuit, configured to supply power to wireless devices.

[0227] 10. A base station, comprising:

[0228] - Processing circuitry, configured to perform any of the steps described in any of the Group B embodiments;

[0229] - Power supply circuit, configured to supply power to wireless devices.

[0230] 11. A user equipment (UE), comprising:

[0231] - Antenna, configured to transmit and receive wireless signals;

[0232] - Radio front-end circuitry, connected to the antenna and processing circuitry and configured to modulate the signal transmitted between the antenna and processing circuitry;

[0233] - Processing circuitry, configured to perform any of the steps described in any of the Group B embodiments;

[0234] - An input interface, connected to the processing circuitry and configured to allow information to be input into the UE for processing by the processing circuitry;

[0235] - An output interface, connected to the processing circuitry and configured to output information already processed by the processing circuitry from the UE; and

[0236] - A battery, connected to the processing circuitry and configured to power the UE.

[0237] 12. A communication system including a host computer, the host computer comprising:

[0238] - Processing circuitry, configured to provide user data; and

[0239] - The communication interface is configured to forward user data to the cellular network for transmission to the User Equipment (UE).

[0240] -The cellular network includes a base station having a radio interface and processing circuitry, the processing circuitry of which is configured to perform any of the steps described in any of the Group B embodiments.

[0241] 13. The communication system according to the foregoing embodiments further includes the base station.

[0242] 14. The communication system according to the foregoing two embodiments further includes the UE, wherein the UE is configured to communicate with the base station.

[0243] 15. The communication system according to the foregoing three embodiments, wherein:

[0244] - The host computer's processing circuitry is configured to execute host applications, thereby providing user data; and

[0245] - The UE includes processing circuitry configured to execute client applications associated with the host application.

[0246] 16. A method implemented in a communication system including a host computer, a base station, and a user equipment (UE), the method comprising:

[0247] - Provide user data at the host computer; and

[0248] - At the host computer, transmission of bearer user data to the UE is initiated via a cellular network including a base station, wherein the base station performs any of the steps described in any of the Group B embodiments.

[0249] 17. The method according to the foregoing embodiments further includes: transmitting user data at the base station.

[0250] 18. The method according to the foregoing two embodiments, wherein user data is provided at a host computer by executing a host application, the method further includes: executing a client application associated with the host application at the UE.

[0251] 19. A user equipment (UE) configured to communicate with a base station, the UE including a radio interface and processing circuitry configured to perform any of the steps described in any of the preceding three embodiments.

[0252] 20. A communication system including a host computer, the host computer comprising:

[0253] - Processing circuitry, configured to provide user data; and

[0254] - The communication interface is configured to forward user data to the cellular network for transmission to the user equipment (UE).

[0255] -The UE includes a radio interface and processing circuitry, and the components of the UE are configured to perform any of the steps described in any of the Group B embodiments.

[0256] 21. The communication system according to the foregoing embodiments, wherein the cellular network further includes a base station configured to communicate with the UE.

[0257] 22. The communication system according to the foregoing two embodiments, wherein:

[0258] - The host computer's processing circuitry is configured to execute host applications, thereby providing user data; and

[0259] - The UE's processing circuitry is configured to execute client applications associated with the host application.

[0260] 23. A method implemented in a communication system including a host computer, a base station, and a user equipment (UE), the method comprising:

[0261] - Provide user data at the host computer; and

[0262] - At the host computer, transmission of bearer user data to the UE via a cellular network including a base station is initiated, wherein the UE is configured to perform any of the steps described in any of the Group B embodiments.

[0263] 24. The method according to the foregoing embodiments further includes: receiving user data from the base station at the UE.

[0264] 25. A communication system including a host computer, the host computer comprising:

[0265] - A communication interface configured to receive user data, the data source of which is the transmission from the user equipment (UE) to the base station.

[0266] -The UE includes a radio interface and processing circuitry, the processing circuitry of which is configured to perform any of the steps described in any of the Group B embodiments.

[0267] 26. The communication system according to the foregoing embodiments further includes the UE.

[0268] 27. The communication system according to the foregoing two embodiments further includes the base station, wherein the base station includes: a radio interface configured to communicate with the UE; and a communication interface configured to forward user data carried by transmissions from the UE to the base station to a host computer.

[0269] 28. The communication system according to the foregoing three embodiments, wherein:

[0270] - The host computer's processing circuitry is configured to execute host applications; and

[0271] - The UE's processing circuitry is configured to execute client applications associated with the host application, thereby providing user data.

[0272] 29. The communication system according to the foregoing four embodiments, wherein:

[0273] - The host computer's processing circuitry is configured to execute host applications, thereby providing requested data; and

[0274] - The UE's processing circuitry is configured to execute client applications associated with the host application, thereby providing user data in response to requested data.

[0275] 30. A method implemented in a communication system including a host computer, a base station, and a user equipment (UE), the method comprising:

[0276] - At the host computer, user data sent from the UE to the base station is received, wherein the UE performs any of the steps described in any of the Group B embodiments.

[0277] 31. The method according to the foregoing embodiments further includes: providing user data to the base station at the UE.

[0278] 32. The method according to the foregoing two embodiments further includes:

[0279] - At the UE, the client application is executed, thereby providing the user data to be sent; and

[0280] - On the host computer, execute the host application associated with the client application.

[0281] 33. The method according to the foregoing three embodiments further includes:

[0282] - At the UE (User Equipment) level, execute the client application; and

[0283] - At the UE, input data for the client application is received, which is provided at the host computer by executing a host application associated with the client application.

[0284] The user data to be sent is provided by the client application in response to the input data.

[0285] 34. A communication system including a host computer, the host computer including 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 includes a radio interface and processing circuitry configured to perform any of the steps described in any of the Group B embodiments.

[0286] 35. The communication system according to the foregoing embodiments further includes the base station.

[0287] 36. The communication system according to the foregoing two embodiments further includes the UE, wherein the UE is configured to communicate with the base station.

[0288] 37. The communication system according to the foregoing three embodiments, wherein:

[0289] - The host computer's processing circuitry is configured to execute host applications;

[0290] - The UE is configured to execute a client application associated with a host application, thereby providing user data to be received by the host computer.

[0291] 38. A method implemented in a communication system including a host computer, a base station, and a user equipment (UE), the method comprising:

[0292] - At the host computer, user data originating from the base station that has been transmitted from the UE is received from the base station, wherein the UE performs any of the steps described in any of the Group B embodiments.

[0293] 39. The method according to the foregoing embodiments further includes: receiving user data from the UE at the base station.

[0294] 40. The method according to the foregoing two embodiments further includes: at the base station, initiating the transmission of the received user data to the host computer.

Claims

1. A method executed by a first network node for operating a new radio NR user plane to support the addition of a non-homogeneous deployment of the user plane, the method comprising: Construct (1512) a General Packet Radio Service (GPRS) Tunneling Protocol User Plane GTP-U packet including an extended header, the extended header including a Protocol Data Unit (PDU) set container, the PDU set container including an indication that the second network node can ignore the PDU set container when the second network node does not support the PDU set function; and Send the GTP-U packet (1514) to the second network node.

2. The method according to claim 1, wherein, The indication is part of the next extended header type field of the GTP-U extended header.

3. The method according to claim 2, wherein, The indication includes two bits of the next extended header type field of the GTP-U extended header.

4. The method according to any one of claims 1 to 3 further includes using a GTP-U extended header PDU session container for data payload transmission.

5. The method according to any one of claims 1 to 4, wherein, The first network node includes a Radio Access Network (RAN) node, and the second network node includes one of a RAN node and a User Plane Function (UPF) node.

6. A network node (300) including processing circuitry (302) capable of performing the steps according to any one of claims 1 to 5.

7. A method performed by a first network node for operating a new radio NR user plane to support the addition of a non-homogeneous deployment of the user plane, the method comprising: Receive (1612) a General Packet Radio Service GPRS Tunneling Protocol User Plane GTP-U packet including an extended header, the extended header including a Protocol Data Unit (PDU) set container, the PDU set container including an indication that the first network node may ignore the PDU set container when the first network node does not support the PDU set function; as well as Based on the aforementioned instructions: Forward (1614) the GTP-U packet with the PDU set container to the third network node; or Forward (1614) GTP-U packets without the PDU set container to the third network node.

8. The method according to claim 7, wherein, The indication is part of the next extended header type field of the GTP-U extended header.

9. The method according to claim 8, wherein, The indication includes two bits of the next extended header type field of the GTP-U extended header.

10. The method according to any one of claims 7 to 9, further comprising using a GTP-U extended header PDU session container for data payload transmission.

11. The method according to any one of claims 7 to 10, wherein, The first network node includes a Radio Access Network (RAN) node, and the second network node includes a RAN node.

12. A network node (300) including processing circuitry (302) capable of performing the steps according to any one of claims 7 to 11.

13. A method executed by a first network node of the gNB-CU-CP central unit control plane for operation of a new radio NR user plane supporting the addition of a non-homogeneous deployment of the user plane, the method comprising: It was determined (1712) that the second network node does not support the Protocol Data Unit (PDU) set function; as well as Send (1714) an instruction to the gNB central unit user plane gNB-CU-UP associated with the gNB-CU-CP to remove PDU set association information from the packet before sending the packet to the second network node.

14. The method according to claim 13, wherein, The PDU set association information includes the General Packet Radio Service (GPRS) Tunneling Protocol User Plane (GTP-U) extended header, which includes a Protocol Data Unit (PDU) set container.

15. The method according to claim 13, wherein, The PDU set association information includes the General Packet Radio Service (GPRS) Tunneling Protocol User Plane (GTP-U) extended header, which includes the PDU session container.

16. The method according to any one of claims 13 to 15, wherein, The first network node operates under dual connectivity, and the second network node includes a secondary network node.

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

18. A method performed by a first network node of the gNB-CU-UP user plane in the gNB central unit user plane for operations supporting the addition of a non-homogeneous deployment of a new radio NR user plane, the method comprising: Receive (1812) an instruction from the gNB-CU-CP, the gNB central unit control plane associated with the gNB-CU-UP, to remove PDU set association information from the packet before sending the packet to the second network node; and Send a packet (1814) containing the removed PDU set association information to the second network node.

19. The method according to claim 18, wherein, The PDU set association information includes the General Packet Radio Service (GPRS) Tunneling Protocol User Plane (GTP-U) extended header, which includes a Protocol Data Unit (PDU) set container.

20. The method according to claim 18, wherein, The PDU set association information includes the General Packet Radio Service (GPRS) Tunneling Protocol User Plane (GTP-U) extended header, which includes the PDU session container.

21. The method according to any one of claims 18 to 20, wherein, The first network node operates under dual connectivity, and the second network node includes a secondary network node.

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

Images