Enhanced inter du interface
By using a UEID field in the message application header of the IP/UDP protocol, the challenge of UE identification across distributed units is addressed, enhancing network efficiency and service delivery in open wireless communication architectures.
Patent Information
- Application Number
- PCT/IB2026/054481
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-07
- Filing Date
- 2026-05-06
- Publication Date
- 2026-11-12
AI Technical Summary
Existing wireless communication networks face challenges in efficiently identifying user equipment (UE) across multiple distributed units, particularly in open network architectures where different vendors provide distributed units, necessitating improved mechanisms for UE identification in inter-DU interfaces.
Incorporating a UE identifier (UEID) field in the message application header of the IP/UDP protocol to identify UEs, allowing efficient processing and routing of messages across distributed units, and supporting various network functions like carrier aggregation and coordinated multipoint techniques.
Facilitates efficient coordination and optimization of network functions by accurately identifying UEs, enabling better service delivery and network efficiency through UE-specific handling and prioritization, particularly for public safety and emergency responses.
Smart Images

Figure IB2026054481_12112026_PF_FP_ABST
Abstract
Description
ENHANCED INTER DU INTERFACEFIELD OF INVENTION
[0001] The present disclosure relates to wireless communication networks, and more particularly to methods and apparatus for identifying user equipment in messages communicated between distributed units over an inter distributed unit interface in a radio access network.BACKGROUND
[0002] Wireless communication networks continue to evolve to meet increasing demands for data throughput, reduced latency, and improved service quality. Modern radio access networks (RANs) employ various architectural approaches to distribute network functions across multiple nodes. For example, in some network architectures, base station functionality may be disaggregated into separate units, such as central units and distributed units, which communicate with each other over defined interfaces.
[0003] Open network architectures are becoming more prevalent as network providers seek flexibility and interoperability between equipment and software from different vendors. Organizations such as the O-RAN Alliance produce open network architecture standards for radio communications networks that facilitate multi-vendor deployments. In such architectures, distributed units (DUs) may be provided by different vendors and may communicate with each other to support various network functions.
[0004] Figure 1 is schematic diagram of an example O-RAN architecture 100. This example O-RAN architecture includes (1) an SMO framework 100, which comprises a component that oversees orchestration, management, and automation of RAN elements, and supports the 01, Al, and 02 interfaces; (2) a near-RT RIC 104, which comprises a logical function that enables near-real-time control and optimization of O-RAN elements and resources via finegrained data collection and actions over an E2 interface; (3) a non-RT RIC 102, which comprises a logical function that enables non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) / ML workflow including model training and updates, and policy-based guidance of applications / features in near-RT RIC; (4) an O-RAN Central Unit (O-CU) 114, which comprises a logical node hosting radio resource controls (RRC), service data adaptation protocol (SDAP) and packet data convergence protocol (PDCP) protocols; (5) an O-RAN Central Unit - Control Plane (O-CU-CP) 108, which comprises a logical node hosting the RRC and the control plane part of the PDCPprotocol; (6) an O-RAN Central Unit - User Plane (O-CU-UP) 110, which comprises a logical node hosting the user plane part of the PDCP protocol and the SDAP protocol; (7) an O-RAN Distributed Unit (O-DU) 112, which comprises a logical node hosting radio link control (RLC) / medium access control (MAC)ZHigh-physical (PHY) layers based on a lower layer functional split; (8) an O-RAN Radio Unit (O-RU) 114, which comprises a logical node hosting Low-PHY layer and radio frequency (RF) processing based on a lower layer functional split. This is similar, for example, to the Third Generation Partnership Project (3GPP’s) transmission / reception points (“TRP”) or remote radio head (“RRH”) but more specific in including the Low-PHY layer (fast Fourier transform (FFT)Zinverse FFT (iFFT), physical random access channel (PRACH) extraction); (9) an xAPP (not depicted) comprises a network function which, for example, can be an independent software plug-in to the Near-RT RIC 104 platform to provide functional extensibility to a RAN by third parties; (10) an rAPP (not depicted) comprises a network function which, for example, can be an independent software plug-in to the Non-RT RIC 102 platform to provide functional extensibility to the RAN by third parties; (11) a network node 106, which comprises, for example, an open evolved nodeB (O-eNB); and (12) an O-Cloud 116, which comprises hardware and / or software components that can provide cloud computing capabilities to execute RAN network functions.
[0005] Carrier aggregation is a technique used in wireless networks to increase data rates by combining multiple component carriers. In some scenarios, carrier aggregation may involve coordination between multiple distributed units, each serving different cells or component carriers. Similarly, coordinated multipoint (CoMP) techniques may involve coordination between multiple network nodes to improve coverage and throughput, particularly at cell edges.
[0006] When multiple distributed units coordinate to provide services to a user equipment (UE), the distributed units may exchange messages over an inter-DU interface. These messages may carry control information, scheduling information, and user data. To facilitate such coordination, the distributed units may benefit from mechanisms to identify which UE is associated with a particular message or data flow.
[0007] Various transport layer protocols may be used for communication between distributed units. Some protocols include features for identifying data flows or tunnels, while other protocols may rely on different mechanisms for associating messages with particular user equipment or services. The selection of transport layer protocols and the design of message headers may affect how efficiently distributed units can identify andprocess messages for different user equipment and different network functions.
[0008] As network architectures continue to evolve and support additional inter-DU network functions, there may be benefits to approaches that facilitate identification of user equipment across multiple distributed units in a manner that supports various applications and services.
[0009] Recently, O-RAN Alliance has started a work item (WI) called D2 WI, which is specifying a new inter O-DU interface to enable multi-vendor carrier aggregation. As of now, only general aspects and principles of this new interface are defined. For example, the interface connects MAC layers residing in different O-DUs in a 5G RAN to each other. The main application of this new interface is to support NR carrier aggregation and that is the scope of this WI. Discussions are ongoing regarding the underlying transport layer for the D2 interface (specifically, D2-U interface carrying user plane data). Other companies have proposed using GTP. The argument used for GTP is that the TEID in GTP can be used to identify UE data flow and that if in future additional use cases (applications) of D2 interface emerge (such as CoMP), the transport layer based TEID can be used to identify the UE across different applications (e.g., TEID= 1234 can be associated to a single UE and then based on application layer protocol, application could be inter O-DU carrier aggregation or UL CoMP).
[0010] However, use of GTP as transport protocol for D2-U is unnecessary. Instead, IP / UDP suffices for transport layer needs of D2-U. The only argument made by proponents for GTP is use of its TEID feature for a specific UE identification. But additional information is still needed in the application layer (running on top of GTP) to identify UE, bearer and SCells. And for this reason alone use of GTP is unjustified. At the same time, D2 may be used for other future inter DU network functions or applications (other than carrier aggregation or, for example, CoMP) and there may be benefits to identifying a UE for use with such other future inter DU network functions. Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges.SUMMARY
[0011] This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.
[0012] According to an aspect of the present disclosure, a method is provided that is performed by a network node operating as a first Distributed Unit (DU) in a radio access network. The method includes receiving, over an inter DU interface, a message from a network node operating as a second DU in the radio access network. The message is received as part of an inter DU network function performed for a User Equipment (UE) and contains a message application header that includes information that identifies the UE to the first DU. The method further includes decoding the message application header of the received message to obtain the information identifying the UE. The method also includes referencing the information identifying the UE included in the message application header when performing the inter DU network function.
[0013] In one embodiment, a IP / UDP protocol may be used to identify the inter DU interface (e.g., with an IP address and UDP port). The message application header may include a UEID field, which can be 16 or 32 bits (or other lengths) with some bits identifying the UE, and other bits identifying other related information.
[0014] By including UE identification information in a message application header communicated over an inter DU interface, the first DU can efficiently identify which UE is associated with a received message without relying on transport layer mechanisms. This approach facilitates coordination between distributed units when performing inter DU network functions, enabling the first DU to properly process and route messages for the correct UE.
[0015] The identification of such UEs can help respective optimizations for a specific UE. For example, a UE can simultaneously use UL CoMP across cells from different O-DUs while at the same time using a D2 interface for Inter O-DU carrier aggregation. In this scenario, based on implementation, there are advantages to group processing related to a single UE in one processor instance (of respective O-DUs).
[0016] According to other aspects of the present disclosure, the UE may be part of a group of UEs categorized with a particular Quality of Service (QoS) profile.
[0017] Categorizing UEs into groups based on QoS profiles allows the distributed units to apply appropriate handling and prioritization for messages associated with UEs having similar service requirements, thereby improving network efficiency and service delivery. In one embodiment, for example, a FWA group of UEs can have lower scheduling priority for inter O-DU carrier aggregation or a specific SCell can be prioritized for such UEs. As another example, public safety or emergency use UEs can have higher priority across some or all SCells for inter O-DU CA.
[0018] According to other aspects of the present disclosure, the message application headermay further include information identifying the group of UEs. The information may identify the group of UEs to the first DU.
[0019] According to other aspects of the present disclosure, the group of UEs may be used for public safety and / or emergency response.
[0020] According to other aspects of the present disclosure, the message application header may further include information identifying the inter DU network function type.
[0021] Including the inter DU network function type in the message application header may allow the first DU to determine how to process the message and which network function procedures to apply, enabling support for multiple different inter DU network functions over the same interface.
[0022] According to other aspects of the present disclosure, the message application header may further include information identifying a radio bearer associated with the UE.
[0023] According to other aspects of the present disclosure, the message application header may further include information identifying one or more cells hosted by the first DU and / or the second DU.
[0024] According to other aspects of the present disclosure, the inter DU network function may include carrier aggregation in an uplink (UL) and / or a downlink (DL), and / or Coordinated Multipoint (CoMP) in an UL and / or DL.
[0025] According to other aspects of the present disclosure, performing the inter DU network function may include exchanging spectrum sharing information with the second DU over the inter DU interface.
[0026] According to other aspects of the present disclosure, the message may include a User Datagram Protocol (UDP) header, with the message application header and an associated payload being encapsulated by the UDP header.
[0027] According to other aspects of the present disclosure, the inter DU interface may be a D2 interface that complies with an Open Radio Access Network (O-RAN) standard specification.
[0028] According to other aspects of the present disclosure, the information identifying the UE may comprise a UE identifier (UEID) field having a plurality of bits, wherein a first set of bits of the plurality of bits uniquely identifies the UE across a plurality of DUs.
[0029] According to other aspects of the present disclosure, referencing the information identifying the UE when performing the inter DU network function may comprise associating the UE with the inter DU network function in a locally stored record.
[0030] According to another aspect of the present disclosure, a method is provided that is performed by a network node operating as a first Distributed Unit (DU) in a radio accessnetwork. The method includes attaching a message application header to a message, the message application header including information that identifies a User Equipment (UE) to a network node operating as a second DU in the radio access network. The method further includes sending, over an inter DU interface, the message to the second DU in the radio access network, the message being sent as part of an inter DU network function performed for the UE. The method also includes referencing the information identifying the UE when performing the inter DU network function.
[0031] According to another aspect of the present disclosure, a network node is provided that is configured to operate as a first Distributed Unit (DU) in a radio access network. The network node includes a communication interface configured to receive, over an inter DU interface, a message from a network node operating as a second DU in the radio access network. The message is received as part of an inter DU network function performed for a User Equipment (UE) and contains a message application header that includes information that identifies the UE to the first DU. The network node further includes processing circuitry configured to decode the message application header of the received message to obtain the information identifying the UE, and to reference the information identifying the UE included in the message application header when performing the inter DU network function.
[0032] According to another aspect of the present disclosure, the network node includes processing circuitry configured to attach a message application header to a message, the message application header including information that identifies a User Equipment (UE) to a network node operating as a second DU in the radio access network, and to reference the information identifying the UE when performing an inter DU network function. The network node further includes a communication interface configured to send, over an inter DU interface, the message to the second DU in the radio access network, the message being sent as part of the inter DU network function performed for the UE.
[0033] The foregoing general description of the illustrative embodiments and the following detailed description thereof are merely exemplary aspects of the teachings of this disclosure and are not restrictive.BRIEF DESCRIPTION OF FIGURES
[0034] Non-limiting and non-exhaustive examples are described with reference to the following figures.
[0035] FIG. 1 illustrates a schematic diagram of an example O-RAN architecture, according to aspects of the present disclosure.
[0036] FIG. 2 illustrates a schematic diagram of a portion of an O-RAN architecture withmultiple distributed units communicating over an inter DU interface, according to aspects of the present disclosure.
[0037] FIG. 3 illustrates a diagram of an example message including a message application header, according to aspects of the present disclosure.
[0038] FIG. 4 illustrates a flowchart for a method performed by a network node operating as a first distributed unit for receiving a message over an inter DU interface, according to aspects of the present disclosure.
[0039] FIG. 5 illustrates a flowchart for a method performed by a network node operating as a first distributed unit for sending a message over an inter DU interface, according to aspects of the present disclosure.
[0040] FIG. 6 illustrates a communication system, according to aspects of the present disclosure.
[0041] FIG. 7 illustrates a user equipment, according to aspects of the present disclosure.
[0042] FIG. 8 illustrates a network node, according to aspects of the present disclosure.
[0043] FIG. 9 illustrates a virtualization environment, according to aspects of the present disclosure.DETAILED DESCRIPTION
[0044] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.
[0045] Figure 2 is schematic diagram of a relevant portion of the O-RAN architecture 100 in which multiple O-DUs 112 communicate over an inter DU interface 210. The O-DUs (or network nodes implementing functionality similar to an O-DU, such as a gNB-DU, or a gNB) may use an inter DU interface 210 that substantially comports with an O-RAN standard specification as defined by the O-RAN Alliance organization and / or other standard specifications, such as a 3GPP standard specification. Such an interface is referred to in current O-RAN standards as a D2 interface, but the embodiments disclosed herein are applicable to similar interfaces with functionality for facilitating interoperation of multiple DUs or O-DUs. Moreover, each O-DU may interface with many O-RUs 114 or with a single O-RU 114, as shown.
[0046] In one embodiment, IP / UDP is used to identify the D2 interface (e.g., an IP address and information identifying a UDP port). A message application header or layer of a message sent across the D2 interface may include a UEID field. In certainembodiments, the UEID field is 16 or 32 bits (or other lengths). Some bits may identify the UE while other bits identify other related information.
[0047] Figure 3 is a diagram showing an example D2 message 300 including at least some of its headers. For example, the D2 message includes at least one or more D2 payloads, a message application header, and a UDP / IP header. Depicted below the example D2 message is a more detailed view of the structure of a message application header of the D2 message, according to one embodiment.
[0048] In an example message application header, an application type field and one or more instances of a UEID field are included. Each of the one or more instances of a UEID field corresponds to an individual UE and to an associated one of one or more instances of the D2 payload. The application type field may identify the application or inter DU network function (e.g., CA, CoMP, spectrum sharing) that is being performed by the DUs in communication over the D2 interface for an associated one or more UEs. Thus, the message application header may correspond to one or more instances of a UEID and a corresponding D2 payload, but one application type common to all UEIDs in the message. In some embodiments, the application type field may be used as a basis for filtering packets to route them to respective application layers. The UEID field may also be used to do a lookup inside an O-DU (or create an association) to associate or tie the data for the two (or more) applications to the same UE. Alternatively, at least some bits in the UEID field (e.g., most significant bits) can be used to identify a UE (and optionally its category, slice, or other group attribute) and thus process packets on a UE basis (e.g., to tie a UE to an application).
[0049] Although only one UEID field is shown, the message may contain multiple UEID fields corresponding to multiple different UEs. Moreover, each application of network function may have its own ‘common header’ , meaning applications are not multiplexed in a single message at the IP / UDP layer. For example, if one UE is participating in UL CoMP and CA and needs to exchange information in a single slot, two IP / UDP messages may be created, one for the CoMP application and another for the CA application.
[0050] In the UEID field, a first set of bits (e.g., bits 1:4) may include information that at least partially identifies a group that the UE belongs to. Example groups of UEs are groups in which the UEs share certain functional attributes in common, e.g., UEs that provide FWA, UE used for emergency services, UEs that send or receive broadcasts, etc.
[0051] The UEID field may contain additional sets of bits. For example, a second set of bits, (e.g., bits 5:20) uniquely identify a UE across multiple O-DUs (irrespective ofinvolved cells). In some embodiments, the second set of bits uniquely identify the UE within a group of UEs and the first and second sets of bits are needed to uniquely identify the UE across multiple groups of UEs. A third set of bits (e.g., bits 21:25) indicate a bearer ID for a radio bearer associated with the UE. A fourth set of bits (e.g., bits 26-32) may uniquely identify (respective) cells in the two DUs communicating over the D2 interface.
[0052] As shown in Figure 4, certain embodiments of the present disclosure include a method 400 in which a network node, operating as a first DU, receives a message over an inter DU interface from another network node operating as a second DU in furtherance of an inter DU network function or application performed for a UE. The method 400 includes a network node in a radio access network operating as a first DU receiving 410, over an inter DU interface, a message from the network node operating as the second DU in the radio access network. The message is received as part of an inter-DU network function performed for a UE and contains a message application header. Then, at step 420, the message application header of the received message is decoded. The message application header includes information that identifies the UE to the first DU. The first DU references 430 the information included in the message application header when performing the inter-DU network function in connection with the second DU. For example, the first DU associates the UE with the inter-DU network function in a locally stored record.
[0053] As shown in Figure 5, certain embodiments of the present disclosure include another method 500 in which a network node, operating as a first DU, sends a message over an inter DU interface to another network node operating as a second DU in furtherance of an inter DU network function or application performed for a UE. The method 500 includes attaching 510 a message application header to a message, the message application header including information that identifies a UE to a network node operating as a second DU in the radio access network. The method 500 further includes sending 520, over a D2 interface, the message to the second DU in the radio access network, the message being sent as part of an inter-DU network function performed for the UE. The first DU references 530 the information included in the message application header when performing the inter-DU network function in connection with the second DU. For example, the first DU associates the UE with the inter-DU network function in a locally stored record.
[0054] In certain embodiments, the UE is part of a group of UEs in a common category associated with a particular service level agreement or QoS profile or set of attributes (e.g., scheduling priority, latency priority, a specific SCell to be used). An example group of UEs that could benefit from being associated into a common category or group is agroup of UEs used for public safety or emergency response. The message application header may include information identifying the group of UEs. For example, the UEID may include a portion that identifies the group of UEs. The message application header may also include information identifying the inter DU network function type, a radio bearer associated with the UE, spectrum sharing information, and / or one or more cells hosted by the first DU and / or the second DU. The inter DU network function may be a CA service in the UL and / or DL, a CoMP service in the UL and / or DL, or a spectrum sharing service for UL and / or DL. The message may have a UDP header that encapsulates the message application header and an associated payload of the message.
[0055] Figure 6 shows an example of a communication system 600 in accordance with some embodiments. In the example, the communication system 600 includes a telecommunication network 602 that includes an access network 604, such as a radio access network (RAN), and a core network 606, which includes one or more core network nodes 608. The access network 604 includes one or more access network nodes, such as network nodes 610a and 610b (one or more of which may be generally referred to as network nodes 610), or any other similar 3rd Generation Partnership Project (3GPP) access nodes or non-3GPP access points. Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network 602 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 602 that supports an ORAN specification (e.g., a specification published by the ORAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network 602, including one or more network nodes 610 and / or core network nodes 608.
[0056] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (nearreal time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORANspecification).
[0057] The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the ORAN Alliance or comparable technologies. The network nodes 610 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 612a, 612b, 612c, and 612d (one or more of which may be generally referred to as UEs 612) to the core network 606 over one or more wireless connections.
[0058] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 600 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 600 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.
[0059] The UEs 612 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / 5 or operable to communicate wirelessly with the network nodes 610 and other communication devices. Similarly, the network nodes 610 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 612 and / or with other network nodes or equipment in the telecommunication network 602 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network 602.
[0060] In the depicted example, the core network 606 connects the network nodes 610 to one or more host computing systems, such as host 616. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 606 includes one more corenetwork nodes (e.g., core network node 608) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 608. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier Deconcealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).
[0061] The host 616 may be under the ownership or control of a service provider other than an operator or provider of the access network 604 and / or the telecommunication network 602. The host 616 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.
[0062] As a whole, the communication system 600 of Figure 6 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.
[0063] In some examples, the telecommunication network 602 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 602 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 602. For example, thetelecommunications network 602 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive loT services to yet further UEs.
[0064] In some examples, the UEs 612 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 604 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 604. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).
[0065] In the example, the hub 614 communicates with the access network 604 to facilitate indirect communication between one or more UEs (e.g., UE 612c and / or 612d) and network nodes (e.g., network node 610b). In some examples, the hub 614 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 614 may be a broadband router enabling access to the core network 606 for the UEs. As another example, the hub 614 may be a controller that sends commands or instructions to one or more actuators in the UEs.
[0066] Commands or instructions may be received from the UEs, network nodes 610, or by executable code, script, process, or other instructions in the hub 614. As another example, the hub 614 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 614 may be a content source. For example, for a UE that is a VR device, display, loudspeaker, or other media delivery device, the hub 614 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 614 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 614 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.
[0067] The hub 614 may have a constant / persistent or intermittent connection to the network node 610b. The hub 614 may also allow for a different communication schemeand / or schedule between the hub 614 and UEs (e.g., UE 612c and / or 612d), and between the hub 614 and the core network 606. In other examples, the hub 614 is connected to the core network 606 and / or one or more UEs via a wired connection. Moreover, the hub 614 may be configured to connect to an M2M service provider over the access network 604 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 610 while still connected via the hub 614 via a wired or wireless connection. In some embodiments, the hub 614 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 610b. In other embodiments, the hub 614 may be a nondedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 610b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.
[0068] Figure 7 shows a UE 700 in accordance with some embodiments. The UE 700 presents additional details of some embodiments of the UE 612 of Figure 1. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage / playback device, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), an Augmented Reality (AR) or Virtual Reality (VR) device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NBIoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.
[0069] A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is notintended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).
[0070] The UE 700 includes processing circuitry 702 that is operatively coupled via a bus 704 to an input / output interface 706, a power source 708, a memory 710, a communication interface 712, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 7. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
[0071] The processing circuitry 702 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine -readable computer programs in the memory 710. The processing circuitry 702 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 702 may include multiple central processing units (CPUs).
[0072] In the example, the input / output interface 706 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 700. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.
[0073] In some embodiments, the power source 708 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 708 may further include power circuitry for delivering power from the power source 708 itself, and / or an external power source, to the various parts of the UE 700 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 708. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 708 to make the power suitable for the respective components of the UE 700 to which power is supplied.
[0074] The memory 710 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 710 includes one or more application programs 714, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 716. The memory 710 may store, for use by the UE 700, any of a variety of various operating systems or combinations of operating systems.
[0075] The memory 710 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof.
[0076] The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 710 may allow the UE 700 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 710, which may be or comprise a device-readable storage medium.
[0077] The processing circuitry 702 may be configured to communicate with an access network or other network using the communication interface 712. The communication interface 712 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 722. The communication interface 712 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 718 and / or a receiver 720 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 718 and receiver 720 may be coupled to one or more antennas (e.g., antenna 722) and may share circuit components, software or firmware, or alternatively be implemented separately.
[0078] In the illustrated embodiment, communication functions of the communication interface 712 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof.
[0079] Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.
[0080] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 712, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).
[0081] As another example, a UE comprises an actuator, a motor, or a switch, related to acommunication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.
[0082] A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 700 shown in Figure 7.
[0083] As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another UE and / or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.
[0084] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller,the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.
[0085] Figure 8 shows a network node 800 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).
[0086] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).
[0087] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multicell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).
[0088] The network node 800 includes a processing circuitry 802, a memory 804, a communication interface 806, and a power source 808. The network node 800 may be composed of multiple physically separate components (e.g., a NodeB component and aRNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 800 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 800 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 804 for different RATs) and some components may be reused (e.g., a same antenna 810 may be shared by different RATs). The network node 800 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 800, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 800.
[0089] The processing circuitry 802 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other network node 800 components, such as the memory 804, to provide network node 800 functionality.
[0090] In some embodiments, the processing circuitry 802 includes a system on a chip (SOC). In some embodiments, the processing circuitry 802 includes one or more of radio frequency (RF) transceiver circuitry 812 and baseband processing circuitry 814. In some embodiments, the radio frequency (RF) transceiver circuitry 812 and the baseband processing circuitry 814 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 812 and baseband processing circuitry 814 may be on the same chip or set of chips, boards, or units.
[0091] The memory 804 may comprise any form of volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a DigitalVideo Disk (DVD)), and / or any other volatile or non-volatile, non-transitory devicereadable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 802. The memory 804 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 802 and utilized by the network node 800. The memory 804 may be used to store any calculations made by the processing circuitry 802 and / or any data received via the communication interface 806. In some embodiments, the processing circuitry 802 and memory 804 is integrated.
[0092] The communication interface 806 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface 806 comprises port(s) / terminal(s) 816 to send and receive data, for example to and from a network over a wired connection. The communication interface 806 also includes radio front-end circuitry 818 that may be coupled to, or in certain embodiments a part of, the antenna 810. Radio front-end circuitry 818 comprises filters 820 and amplifiers 822. The radio front-end circuitry 818 may be connected to an antenna 810 and processing circuitry 802. The radio front-end circuitry may be configured to condition signals communicated between antenna 810 and processing circuitry 802. The radio front-end circuitry 818 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 818 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 820 and / or amplifiers 822. The radio signal may then be transmitted via the antenna 810. Similarly, when receiving data, the antenna 810 may collect radio signals which are then converted into digital data by the radio front-end circuitry 818. The digital data may be passed to the processing circuitry 802. In other embodiments, the communication interface may comprise different components and / or different combinations of components.
[0093] In certain alternative embodiments, the network node 800 does not include separate radio front-end circuitry 818, instead, the processing circuitry 802 includes radio front-end circuitry and is connected to the antenna 810. Similarly, in some embodiments, all or some of the RF transceiver circuitry 812 is part of the communication interface 806. In still other embodiments, the communication interface 806 includes one or more ports or terminals 816, the radio front-end circuitry 818, and the RF transceiver circuitry 812, as part of a radio unit (not shown), and the communication interface 806 communicateswith the baseband processing circuitry 814, which is part of a digital unit (not shown).
[0094] The antenna 810 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 810 may be coupled to the radio front-end circuitry 818 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 810 is separate from the network node 800 and connectable to the network node 800 through an interface or port.
[0095] The antenna 810, communication interface 806, and / or the processing circuitry 802 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 810, the communication interface 806, and / or the processing circuitry 802 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.
[0096] The power source 808 provides power to the various components of network node 800 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 808 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 800 with power for performing the functionality described herein. For example, the network node 800 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 808. As a further example, the power source 808 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.
[0097] Embodiments of the network node 800 may include additional components beyond those shown in Figure 8 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 800 may include user interface equipment to allow input of information into the network node 800 and to allow output of information from the network node 800. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions forthe network node 800. In some embodiments providing a core network node, such as core network node 108 of FIG. 6, some components, such as the radio front-end circuitry 818 and the RF transceiver circuitry 812 may be omitted.
[0098] Figure 9 is a block diagram illustrating a virtualization environment 900 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 900 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 900 includes components defined by the 5 O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface. Virtualization may facilitate distributed implementations of a network node, UE, core network node, or host.
[0099] Applications 902 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.
[0100] Hardware 904 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 906 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 908a and 908b (one or more of which may be generally referred to as VMs 908), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 906 may present a virtual operating platform that appears like networking hardware to the VMs 908.
[0101] The VMs 908 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 906. Different embodiments of the instance of a virtual appliance 902 may be implemented on one or more of VMs 908, and the implementations may be made in different ways.Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.
[0102] In the context of NFV, a VM 908 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non virtualized machine. Each of the VMs 908, and that part of hardware 904 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 908 on top of the hardware 904 and corresponds to the application 902.
[0103] Hardware 904 may be implemented in a standalone network node with generic or specific components. Hardware 904 may implement some functions via virtualization. Alternatively, hardware 904 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 910, which, among others, oversees lifecycle management of applications 902. In some embodiments, hardware 904 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 912 which may alternatively be used for communication between hardware nodes and radio units.
[0104] Although the computing devices described herein (e.g., UEs, network nodes) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations describedherein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.
[0105] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.
[0106] The following is a list of example embodiments:
[0107] 1. A method performed by a network node operating as a first Distributed Unit (DU) in a radio access network, the method comprising: receiving, over an inter DU interface, a message from a network node operating as a second DU in the radio access network, the message being received as part of an inter DU network function performed for a User Equipment (UE) and containing a message application header that includes information that identifies the UE to the first DU ; decoding the message application header of the received message to obtain the information identifying the UE; andreferencing the information identifying the UE included in the message application header when performing the inter DU network function.
[0108] 2. The method of embodiment 1 , wherein the UE is part of a group of UEs categorized with a particular QoS profile.
[0109] 3. The method of embodiment 2, wherein the message application header further includes information identifying the group of UEs.
[0110] 4. The method of embodiment 2, wherein the information that identifies the UE to the first DU also identifies the group of UEs to the first DU.
[0111] 5. The method of embodiment 2, wherein the QoS profile includes a scheduling priority.
[0112] 6. The method of embodiment 2, wherein the QoS profile includes use of a specific SCell.
[0113] 7. The method of embodiment 2, wherein the group of UEs are used for public safety and / or emergency response.
[0114] 8. The method of any one of the previous embodiments, wherein the message application header further includes information identifying the inter DU network function type.
[0115] 9. The method of any one of the previous embodiments, wherein the message application header further includes information identifying a radio bearer associated with the UE.
[0116] 10. The method of any one of the previous embodiments, wherein the message application header further includes information identifying one or more cells hosted by the first DU and / or the second DU.
[0117] 11. The method of any one of the previous embodiments, wherein the inter DU network function includes carrier aggregation in the UL and / or the DL.
[0118] 12. The method of any one of the previous embodiments, wherein the inter DU network function includes CoMP in the UL and / or the DL.
[0119] 13. The method of any one of the previous embodiments, wherein performing the inter-DU network function includes exchanging spectrum sharing information with the second DU over the inter DU interface.
[0120] 14. The method of any one of the previous embodiments, wherein the message includes a UDP header, the message application header and an associated payload being encapsulated by the UDP header.
[0121] 15. The method of any one of the previous embodiments, wherein the inter DUinterface is a D2 interface that complies with an O-RAN standard specification.
[0122] 16. A method performed by a network node operating as a first Distributed Unit (DU) in a radio access network, the method comprising: attaching a message application header to a message, the message application header including information that identifies a UE to a network node operating as a second DU in the radio access network; sending, over an inter DU interface, the message to the second DU in the radio access network, the message being sent as part of an inter DU network function performed for the UE; and referencing the information identifying the UE when performing the inter DU network function.
[0123] 17. The method of embodiment 16, wherein the UE is part of a group of UEs categorized with a particular QoS profile.
[0124] 18. The method of embodiment 17, wherein the message application header further includes information identifying the group of UEs.
[0125] 19. The method of embodiment 17, wherein the information that identifies the UE to the first DU also identifies the group of UEs to the first DU.
[0126] 20. The method of embodiment 17, wherein the QoS profile includes a scheduling priority.
[0127] 21. The method of embodiment 17, wherein the QoS profile includes use of a specific SCell.
[0128] 22. The method of embodiment 17, wherein the group of UEs are used for public safety and / or emergency response.
[0129] 23. The method of any one of embodiments 16-22, wherein the message application header further includes information identifying the inter DU network function type.
[0130] 24. The method of any one of embodiments 16-23, wherein the message application header further includes information identifying a radio bearer associated with the UE.
[0131] 25. The method of any one of embodiments 16-24, wherein the message application header further includes information identifying one or more cells hosted by the first DU and / or the second DU.
[0132] 26. The method of any one of embodiments 16-25, wherein the inter DU network function includes carrier aggregation in the UL and / or the DL.
[0133] 27. The method of any one of embodiments 16-26, wherein the inter DU network function includes CoMP in the UL and / or the DL.
[0134] 28. The method of any one of embodiments 16-27, wherein performing the inter-DU network function includes exchanging spectrum sharing information with the second DU over the inter DU interface.
[0135] 29. The method of any one of embodiments 16-28, wherein the message includes a UDP header, the message application header and an associated payload being encapsulated by the UDP header.
[0136] 30. The method of any one of embodiments 16-29, wherein the inter DU interface is a D2 interface that complies with an O-RAN standard specification.
[0137] 31. A network node comprising: processing circuitry configured to perform the steps of either one of embodiments 1 or 16; power supply circuitry configured to supply power to the processing circuitry.
Claims
CLAIMS1. A method (400) performed by a network node (800) operating as a first Distributed Unit, DU, (112) in a radio access network, the method comprising:receiving (410), over an inter DU interface (210), a message from a network node operating as a second DU in the radio access network, the message being received as part of an inter DU network function performed for a User Equipment, UE, (700) and containing a message application header that includes information that identifies the UE to the first DU;decoding (420) the message application header of the received message to obtain the information identifying the UE; andreferencing (430) the information identifying the UE included in the message application header when performing the inter DU network function.
2. The method of claim 1, wherein the UE is part of a group of UEs categorized with a particular Quality of Service, QoS, profile.
3. The method of claim 2, wherein the message application header further includes information identifying the group of UEs.
4. The method of claim 2, wherein the information that identifies the UE to the first DU also identifies the group of UEs to the first DU.
5. The method of any one of claims 2-4, wherein the group of UEs are used for public safety and / or emergency response.
6. The method of any one of claims 1-4, wherein the message application header further includes information identifying the inter DU network function type.
7. The method of any one of claims 1-4, wherein the message application header further includes information identifying a radio bearer associated with the UE.
8. The method of any one of claims 1-4, wherein the message application header further includes information identifying one or more cells hosted by the first DU and / or the second DU.
9. The method of any one of claims 1-4, wherein the inter DU network function includes carrier aggregation in an uplink, UL, and / or a downlink, DL.
10. The method of any one of claims 1-4, wherein the inter DU network function includes Coordinated Multipoint, CoMP, in an uplink, UL, and / or a downlink, DL.
11. The method of any one of claims 1-4, wherein performing the inter DU network function includes exchanging spectrum sharing information with the second DU over the inter DU interface.
12. The method of any one of claims 1-4, wherein the message includes a User Datagram Protocol, UDP, header, the message application header and an associated payload being encapsulated by the UDP header.
13. The method of any one of claims 1-4, wherein the inter DU interface is a D2 interface that complies with an Open Radio Access Network, O-RAN, standard specification.
14. The method of any one of claims 1-4, wherein the information identifying the UE comprises a UE identifier, UEID, field having a plurality of bits, wherein a first set of bits of the plurality of bits uniquely identifies the UE across a plurality of DUs.
15. The method of any one of claims 1-4, wherein referencing the information identifying the UE when performing the inter DU network function comprises associating the UE with the inter DU network function in a locally stored record.
16. A method (500) performed by a network node (800) operating as a first Distributed Unit, DU, (112) in a radio access network, the method comprising:attaching (510) a message application header to a message, the message application header including information that identifies a User Equipment, UE, (700) to a network node operating as a second DU in the radio access network;sending (520), over an inter DU interface (210), the message to the second DU in the radio access network, the message being sent as part of an inter DU network function performed for the UE; andreferencing (530) the information identifying the UE when performing the inter DU network function.
17. The method of claim 16, wherein the UE is part of a group of UEs categorized with a particular Quality of Service, QoS, profile.
18. The method of claim 17, wherein the message application header further includes information identifying the group of UEs.
19. The method of claim 17, wherein the information that identifies the UE to the second DU also identifies the group of UEs to the second DU.
20. The method of any one of claims 17-19, wherein the group of UEs are used for public safety and / or emergency response.
21. The method of any one of claims 16-19, wherein the message application header further includes information identifying the inter DU network function type.
22. The method of any one of claims 16-19, wherein the message application header further includes information identifying a radio bearer associated with the UE.
23. The method of any one of claims 16-19, wherein the message application header further includes information identifying one or more cells hosted by the first DU and / or the second DU.
24. The method of any one of claims 16-19, wherein the inter DU network function includes carrier aggregation in an uplink, UL, and / or a downlink, DL.
25. The method of any one of claims 16-19, wherein the inter DU network function includes Coordinated Multipoint, CoMP, in an uplink, UL, and / or a downlink, DL.
26. The method of any one of claims 16-19, wherein performing the inter DU network function includes exchanging spectrum sharing information with the second DU over the inter DU interface.
27. The method of any one of claims 16-19, wherein the message includes a User Datagram Protocol, UDP, header, the message application header and an associated payload being encapsulated by the UDP header.
28. The method of any one of claims 16-19, wherein the inter DU interface is a D2 interface that complies with an Open Radio Access Network, O-RAN, standard specification.
29. The method of any one of claims 16-19, wherein the information identifying the UE comprises a UE identifier, UEID, field having a plurality of bits, wherein a first set of bits of the plurality of bits uniquely identifies the UE across a plurality of DUs.
30. The method of any one of claims 16-19, wherein referencing the information identifying the UE when performing the inter DU network function comprises associating the UE with the inter DU network function in a locally stored record.
31. A network node (800) configured to operate as a first Distributed Unit, DU, (112) in a radio access network, the network node comprising:a communication interface (806) configured to receive, over an inter DU interface (210), a message from a network node operating as a second DU in the radio access network, the message being received as part of an inter DU network function performed for a User Equipment, UE, (700) and containing a message application header that includes information that identifies the UE to the first DU; andprocessing circuitry (802) configured to:decode the message application header of the received message to obtain the information identifying the UE; andreference the information identifying the UE included in the message application header when performing the inter DU network function.
32. The network node of claim 31, wherein the processing circuitry is further configured to perform the methods of any one of claims 2-15.
33. A network node (800) configured to operate as a first Distributed Unit, DU, (112) in a radio access network, the network node comprising:processing circuitry (802) configured to attach a message application header to a message, the message application header including information that identifies a User Equipment, UE, (700) to a network node operating as a second DU in the radio access network, and to reference the information identifying the UE when performing an inter DU network function; anda communication interface (806) configured to send, over an inter DU interface (210), the message to the second DU in the radio access network, the message being sent as part of the inter DU network function performed for the UE.
34. The network node of claim 32, wherein the processing circuitry is further configured to perform the methods of any one of claims 17-30.
