HARQ feedback over inter du interface for scell o-dus
By implementing a retransmission intent indication in HARQ feedback between distributed units, the method addresses inefficiencies in HARQ retransmission control, enhancing memory management and resource usage in wireless communication systems.
Patent Information
- Application Number
- PCT/IB2026/054484
- 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
In wireless communication systems with disaggregated architectures, coordinating HARQ feedback and retransmissions between distributed units from different vendors is challenging, leading to inefficient memory usage and degraded user equipment throughput due to unclear responsibilities in HARQ retransmission control.
A method where a primary cell distributed unit provides a retransmission intent indication in a HARQ information message to a secondary cell distributed unit, enabling informed memory management and HARQ process handling, thereby improving coordination and resource usage.
This approach enhances memory and resource utilization by allowing timely release of stored data and HARQ processes, improving user throughput and reducing unnecessary memory consumption.
Smart Images

Figure IB2026054484_12112026_PF_FP_ABST
Abstract
Description
HARQ FEEDBACK OVER INTER DU INTERFACE FOR SCELL O-DUsFIELD OF INVENTION
[0001] The present disclosure relates to wireless communication systems, and more particularly to managing hybrid automatic repeat request (HARQ) feedback and retransmission coordination between distributed units in a radio access network.BACKGROUND
[0002] Wireless communication systems continue to evolve to meet increasing demands for data throughput and network flexibility. Modern radio access networks may employ disaggregated architectures in which network functions are distributed across multiple nodes. For example, a radio access network may include distributed units that host cells for user equipment and coordinate with one another to provide wireless services.
[0003] Carrier aggregation is a technique that allows a user equipment to simultaneously use multiple component carriers to increase data throughput. In some network architectures, carrier aggregation may involve a primary cell and one or more secondary cells. The primary cell may be hosted by a first distributed unit, while a secondary cell may be hosted by a second distributed unit. When distributed units from different vendors are involved, coordination between the distributed units may be facilitated through interdistributed unit interfaces. Such interfaces are sometimes referred to as D2 interfaces. The D2 interface is an interface for connecting multi-vendor O-DUs and is being defined in O-RAN Alliance.
[0004] Hybrid automatic repeat request (HARQ) is a mechanism used in wireless communication systems to improve reliability of data transmission. When a data message, such as a transport block, is transmitted to a user equipment, the user equipment may provide feedback indicating whether the transmission was successfully received. If the transmission was unsuccessful, the data message may be retransmitted. To facilitate retransmission, a distributed unit that transmits a data message may store the data message in memory so that it can be retransmitted without receiving the data message again from another network node.
[0005] In scenarios where carrier aggregation involves multiple distributed units, coordination of HARQ processes may present challenges. For instance, when a secondary cell distributed unit transmits a data message to a user equipment, the HARQ feedbackfrom the user equipment may be received by a primary cell distributed unit. The primary cell distributed unit may then determine whether retransmission of the data message is appropriate. However, the secondary cell distributed unit may not have visibility into whether or when a retransmission will be requested, which may affect how long the secondary cell distributed unit stores the data message in memory and maintains the associated HARQ process.
[0006] Open network architecture is becoming more important as network providers demand flexibility and interoperability between equipment / software providers. O-RAN Alliance is an organization that produces open network architecture standards for radio communications networks. 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.
[0007] 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 PDCP protocol; (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 layerfunctional 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.
[0008] Today, to enable carrier aggregation (CA) in an O-RAN context, a common requirement from the network perspective is that all relevant SCells are controlled by a single O-DU. When implemented in O-RAN, this service is called Intra O-DU CA and a schematic diagram of an example O-RAN architecture 210 that provides such a service is shown in Figure 2 (left side). Different component carriers are transmitted to (or received from) a UE using different O-RUs. However, the different O-RUs are connected to a single O-DU.
[0009] Some vendors have deployed proprietary solutions where CA can involve SCells controlled by different O-DUs. However, there is no open multi-vendor Inter O-DU CA solution where CA can be provided across cells controlled by different vendors. In October 2024, O-RAN Alliance started work in WG5 to specify an interface interconnecting two O-DUs to enable carrier aggregation. The O-DUs connected by this Inter O-DU interface, termed as D2, can be sourced from different vendors, as shown in the schematic diagram of an example O-RAN architecture 220 in Figure 2 (right side).
[0010] In March 2025, O-RAN WG5 published its first technical specification for D2, describing General Aspects and Principles (D2 GAP). While D2 GAP TS laid out general principles and functions of the D2 interface to enable DL CA across multi-vendor O-DUs, one open question remains to determine how much role does a PCell O-DU (pDU) have in scheduling transmission over SCells controlled by an SCell O-DU (sDU). It has been agreed that a pDU can indicate the desired slots on which an sDU should attempt scheduling. It remains open what is the role of a pDU in HARQ retransmissions on D2 SCells (cells served by the sDU). In particular, when non-positive HARQ feedback isreceived from UE for which DL CA is performed, it remains an open question whether the pDU has at least some control of retransmission or if the responsibility should be placed entirely on the sDU.
[0011] In pDU driven HARQ retransmission control, pDUs make decision on whether to attempt retransmission (on sDU cells), and when the scheduling attempt can be made by the sDU (e.g., the pDU conveys to the sDU a range of slots). In sDU-driven HARQ retransmission control, these decisions entirely reside in the sDU.
[0012] As noted above, in pDU driven HARQ retransmission control for D2, when an initial transmission by an sDU (on D2 SCells) is unsuccessful, a pDU makes a decision on whether to attempt retransmission (on sDU cells) and when the scheduling attempt can be made by the sDU (e.g., the pDU conveys a range of slots to the sDU). Typically, when an sDU makes the first transmission, it saves the transmitted transport block (TB). This eliminates the requirement of re-transferring the same TB from the pDU for subsequent HARQ retransmissions. In this approach, the sDU has no knowledge when or if the pDU will ask it to attempt retransmission(s). In the worst-case scenario, the pDU continues to request only additional new data transmissions as well as requesting retransmission for previously failed TBs. If the sDU stores the transmitted TB that it earlier received from the pDU, then it will continue storing it in memory and will also block the HARQ PID associated with the initial transmission. Not only does this result in unnecessary memory wastage, but blockage of a HARQ PID degrades UE throughput.
[0013] Accordingly, there is a general desire for improved techniques for coordinating HARQ feedback and retransmission decisions between distributed units in a radio access network.SUMMARY
[0014] 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.
[0015] According to an aspect of the present disclosure, a method performed by a first distributed unit hosting a primary cell for a user equipment in a radio access network is provided. The method includes receiving hybrid automatic repeat request (HARQ) feedback associated with a data message transmitted by a second distributed unit to the user equipment, the second distributed unit hosting a secondary cell for the userequipment. Responsive to the HARQ feedback, the method includes determining whether to include a retransmission intent indication in a HARQ information message to be transmitted to the second distributed unit, the retransmission intent indication being indicative of whether the data message associated with the HARQ feedback is to be retransmitted. The method further includes transmitting the HARQ information message to the second distributed unit.
[0016] By providing a retransmission intent indication in the HARQ information message, the first distributed unit may enable the second distributed unit to make informed decisions about memory management and HARQ process handling, thereby improving coordination between distributed units in a disaggregated radio access network architecture. For example, communicating the retransmission intent from the pDU to the sDU at substantially the same time as sharing the HARQ feedback facilitates may free up memory and free up the associated HARQ process in the sDU. Accordingly, the memory and HARQ process may be used more quickly for a future new data transmission, thereby improving resource usage and user throughput. Moreover, sharing the HARQ process information with the sDU may give better observability for the sDU because it may get an immediate and fast indication of the received HARQ feedback even when a retransmission is not processed.
[0017] According to other aspects of the present disclosure, determining whether to include the retransmission intent indication in the HARQ information message may include determining whether the data message is to be retransmitted.
[0018] According to other aspects of the present disclosure, determining whether the data message is to be retransmitted may include one or more of: determining that the HARQ feedback does not include an acknowledgment; evaluating a signal strength characteristic associated with the data message; or determining whether a HARQ process timer associated with the data message has elapsed.
[0019] According to other aspects of the present disclosure, the retransmission intent indication may be included in the HARQ information message and may indicate to the second distributed unit to delete the data message from memory. According to other aspects of the present disclosure, the retransmission intent indication may further indicate to the second distributed unit to release a HARQ process associated with the data message.
[0020] According to other aspects of the present disclosure, the HARQ information message may include the HARQ feedback received by the first distributed unit.
[0021] According to other aspects of the present disclosure, when the HARQ information message does not include the retransmission intent indication and the first distributed unit does not transmit a retransmission request within a predetermined period of time after transmitting the HARQ information message, the first distributed unit may assume the second distributed unit will clear the stored data message from memory. This timer-based approach may provide a fallback mechanism for memory management at the second distributed unit, reducing the risk of indefinite memory consumption when retransmission decisions are delayed or not communicated.
[0022] According to other aspects of the present disclosure, the retransmission intent indication may be included in the HARQ information message and may provide an indication of an intent to subsequently transmit a retransmission request to the second distributed unit for retransmission of the data message.
[0023] According to other aspects of the present disclosure, if the first distributed unit does not transmit the retransmission request within a predetermined period of time after transmitting the HARQ information message, the first distributed unit may assume the second distributed unit will clear the stored data message from memory and release the HARQ process. This timer-based assumption may enable coordinated resource management between the distributed units without requiring additional signaling, thereby reducing signaling overhead while maintaining predictable behavior.
[0024] According to other aspects of the present disclosure, the predetermined period of time may be configured by the first distributed unit.
[0025] According to other aspects of the present disclosure, the HARQ information message may be transmitted over a D2 interface between the first distributed unit and the second distributed unit.
[0026] According to another aspect of the present disclosure, a network node comprising a first distributed unit hosting a primary cell for a user equipment in a radio access network is provided. The network node includes a receiver, a transmitter, and a processor that are collectively configured to carry out the methods outlined above that are performed by a distributed unit hosting a primary cell.
[0027] According to another aspect of the present disclosure, a method performed by a first distributed unit hosting a secondary cell for a user equipment in a radio access network is provided. The method includes transmitting a data message associated with a HARQ process to the user equipment. The method includes storing the data message in memory. The method includes receiving a feedback message associated with the HARQprocess from a second distributed unit hosting a primary cell for the user equipment. Responsive to the feedback message, the method includes determining whether to clear the stored data message from the memory or whether to release the HARQ process.
[0028] By receiving a feedback message from the second distributed unit and determining whether to clear the stored data message or release the HARQ process, the first distributed unit may manage memory and HARQ process resources based on information from the second distributed unit, thereby improving coordination in a disaggregated radio access network architecture.
[0029] According to another aspect of the present disclosure, a network node comprising a first distributed unit hosting a primary cell for a user equipment in a radio access network is provided. The network node includes a receiver, a transmitter, and a processor that are collectively configured to carry out the methods outlined above that are performed by a distributed unit hosting a secondary cell.
[0030] 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
[0031] Non-limiting and non-exhaustive examples are described with reference to the following figures.
[0032] FIG. 1 illustrates a block diagram of an O-RAN architecture, according to aspects of the present disclosure.
[0033] FIG. 2 illustrates network architectures for carrier aggregation in an O-RAN context, according to aspects of the present disclosure.
[0034] FIG. 3 illustrates a sequence diagram for inter O-DU carrier aggregation communication, according to aspects of the present disclosure.
[0035] FIG. 4 illustrates a flowchart for a method performed by a distributed unit hosting a primary cell, according to aspects of the present disclosure.
[0036] FIG. 5 illustrates a flowchart for a method performed by a distributed unit hosting a secondary cell, according to aspects of the present disclosure.
[0037] FIG. 6 illustrates a communication system, according to aspects of the present disclosure.
[0038] FIG. 7 illustrates a block diagram of a user equipment, according to aspects of the present disclosure.
[0039] FIG. 8 illustrates a block diagram of a network node, according to aspects of the present disclosure.
[0040] FIG. 9 illustrates a block diagram of a virtualization environment, according to aspects of the present disclosure.DETAILED DESCRIPTION
[0041] 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.
[0042] In one embodiment, a pDU, upon reception of HARQ feedback from a UE receiving an initial TB transmission from an sDU, will make a decision on whether retransmission in the sDU should be attempted and will convey this decision to the sDU. The decision may be conveyed as part of a message that includes HARQ process information. This information from the pDU will help the sDU to determine whether to keep or clear the stored TB of the initial transmission (by the sDU). If the pDU communicates an indication of an intent for retransmission (actual scheduling request indicating desired slots for retransmission may stay separate from this intent to retransmit indication), the sDU will keep the TB (and HARQ PID) for future retransmissions. If no retransmission intent is communicated, the sDU will clear the stored TB from memory and release the associated HARQ process.
[0043] According to an example method shown in Figure 3, a sequence of steps described below may be carried out by a pDU, sDU, and a UE during an Inter O-DU CA operation. At step 1, upon transmission of a transport block (TB) from the sDU, the sDU saves the transmitted TB. Then, at step 2, the UE sends feedback (ACK / NACK) on a PCell uplink to the pDU. The pDU decodes and interprets this feedback as ACK, NACK or DTX (missed downlink DCI or failed uplink processing). At step 3, the pDU shares this per HARQ process information with the sDU. At step 4, in case of NACK or DTX, the pDU may also share its intent to retransmit the TB in a future slot. This retransmission intent can be in the form of clear flag, for example. A value of “1” for the clear flag may indicate to the sDU to empty the memory storing the TB and free up the HARQ PID (i.e., no retransmission for this HARQ process). Finally, in a step that is not shown, the pDU makes a decision about whether to send a new transmission request or a retransmission request to the sDU.
[0044] An example method 400 implemented in a pDU is illustrated in Figure 4. Inmethod 400, a network node, operating as a first DU hosting a PCell for a UE, i.e., a pDU, in a radio access network receives (410) a message containing HARQ feedback associated with a data message (e.g., a transport block) transmitted by another network node operating as a second DU hosting an SCell, i.e., an sDU, in the radio access network. The data message associated with the HARQ feedback is a data message that was previously transmitted by the sDU in an initial transmission. The pDU then generates a HARQ information message to send to the sDU and determines (420) whether to include a retransmission intent indication in the HARQ information message. The determination of whether to include the retransmission intent indication may be based on a determination of whether to request the sDU to retransmit the data message. The determination of whether to request retransmission may include, for example, determining that the HARQ feedback does not include an ACK, evaluating a signal strength characteristic associated with the data message, and / or determining whether a HARQ process timer associated with the data message has elapsed. The HARQ information message is then transmitted (430) to the sDU. The transmission may occur over an inter DU interface. The method 400 optionally includes a step of transmitting (440) a retransmission request to the sDU over the inter DU interface.
[0045] The inter DU interface may be an interface 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, although reference is made herein to network nodes operating as O-DUs hosting a PCell or an SCell for a UE, any network node with one or more functions similar to an O-DU, such as a gNB-DU, or a gNB, may instead be used.
[0046] An example method 500 implemented in an sDU is illustrated in Figure 5. In method 500 a network node, operating as a first DU hosting an SCell, i.e., an sDU, in a radio access network transmits (510) a data message to a UE. The sDU associates the data message in memory with a HARQ process. The data message may then be stored (520) in memory accessible to the sDU. The sDU then receives (530) a feedback message associated with the HARQ process from a pDU. The sDU may receive the feedback message over an inter DU interface, which may be a D2 interface. The sDU then determines (540), responsive to the feedback message, whether to clear the storeddata message from the memory and / or whether to release the associated HARQ process. In one embodiment applicable to both methods 400 and 500, the retransmission intent indication is included in the HARQ information message and explicitly indicates to the sDU to delete the data message from memory and / or release the HARQ process associated with the data message. Alternatively, the retransmission intent indication may provide an indication of an intent to subsequently carry out the transmitting step (440) of method 400, i.e., transmit a retransmission request to the sDU for retransmission of the data message by the sDU. However, in one embodiment the pDU may ultimately not transmit the retransmission request. If the retransmission request is not transmitted within a predetermined period of time after transmitting the HARQ information message, the pDU assumes the sDU will clear the stored data message from the memory and / or release the HARQ process.
[0047] In another embodiment applicable to both methods 400 and 500, the HARQ information message includes the HARQ feedback received by the pDU. When the HARQ information message does not include the retransmission intent indication and the pDU does not transmit a retransmission request within a predetermined period of time after transmitting the HARQ feedback in the HARQ information message, the sDU clears the stored data message from the memory and / or release the HARQ process. Moreover, the pDU assumes that the sDU will clear the data message and / or release the HARQ process after the predetermined period of time lapses without transmitting a retransmission request.
[0048] The predetermined period of time referenced above may be configured by the pDU and may be general to a plurality of sDUs. Alternatively, the predetermined period of time may be configured differently for various different sDUs, i.e., specific to the sDU. Alternatively, the predetermined period of time may be configured differently for various different SCells hosted by the sDU, i.e., specific to the SCell. In one embodiment applicable to both methods 400 and 500, the predetermined period of time is a fixed number of slots and may be configured by indicating the fixed number. The fixed number of slots may be specified according to a subcarrier spacing in use by the SCell.
[0049] 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 asnetwork 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.
[0050] 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 ORAN specification).
[0051] 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 O-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.
[0052] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infraredwaves, 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.
[0053] 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.
[0054] 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 core network 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 (SIDE), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).
[0055] 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.
[0056] 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.
[0057] 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, the telecommunications 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.
[0058] 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).
[0059] In the example, the hub 614 communicates with the access network 604 tofacilitate 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.
[0060] 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.
[0061] 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 scheme and / 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.
[0062] 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 usedherein, 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.
[0063] A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).
[0064] 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.
[0065] 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), applicationspecific 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).
[0066] 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.
[0067] 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.
[0068] 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 710includes 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.
[0069] 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.
[0070] 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.
[0071] 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.
[0072] In the illustrated embodiment, communication functions of the communication interface 712 may include cellular communication, Wi-Fi communication, LPWANcommunication, 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.
[0073] 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.
[0074] 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).
[0075] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.
[0076] 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, avehicle 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.
[0077] 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.
[0078] 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.
[0079] 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).
[0080] 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).
[0081] 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).
[0082] 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 a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 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 thesame or different chip or set of chips and other components within network node 800.
[0083] 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.
[0084] 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.
[0085] The memory 804 may comprise any form of volatile or non-volatile computerreadable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory 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.
[0086] 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 incertain 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.
[0087] 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 communicates with the baseband processing circuitry 814, which is part of a digital unit (not shown).
[0088] 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.
[0089] 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 / orsignals may be transmitted to a UE, another network node and / or any other network equipment.
[0090] 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.
[0091] 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 for the 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.
[0092] 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 nodedoes 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 0-2 interface. Virtualization may facilitate distributed implementations of a network node, UE, core network node, or host.
[0093] 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.
[0094] 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.
[0095] 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.
[0096] 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 ormore VMs 908 on top of the hardware 904 and corresponds to the application 902.
[0097] 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.
[0098] 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 described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.
[0099] 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.
[0100] The following is a list of example embodiments:
[0101] 1. A method performed by a network node operating as a first Distributed Unit (DU) hosting a PCell (pDU) for a UE in a radio access network, the method comprising: receiving HARQ feedback associated with a data message transmitted by a network node to the UE, the network node operating as a second Distributed Unit (DU) hosting an SCell (sDU) in the radio access network; responsive to the HARQ feedback, determining whether to include a retransmission intent indication in a HARQ information message to be transmitted to the sDU, the retransmission intent indication being indicative of whether the data message associated with the HARQ feedback should be retransmitted; and transmitting the HARQ information message to the sDU.
[0102] 2. The method of embodiment 1 , wherein determining, responsive to the HARQ feedback, whether to include the retransmission intent indication in the HARQ information message includes determining whether the data message should be retransmitted.
[0103] 3. The method of embodiment 2, wherein determining whether the data message should be retransmitted includes one or more of: determining that the HARQ feedback does not include an ACK; evaluating a signal strength characteristic associated with the data message; or determining whether a HARQ process timer associated with the data message has elapsed.
[0104] 4. The method of any of the previous embodiments, wherein the data message is a transport block.
[0105] 5. The method of any of the previous embodiments, wherein the retransmissionintent indication is included in the HARQ information message and explicitly indicates to the sDU to delete the data message from memory and / or release the HARQ process associated with the data message.
[0106] 6. The method of any one of embodiments 1-4, wherein the HARQ information message includes the HARQ feedback received by the pDU.
[0107] 7. The method of embodiment 6, wherein when the HARQ information message does not include the retransmission intent indication and the pDU does not transmit a retransmission request within a predetermined period of time after transmitting the HARQ information message including the HARQ feedback, the pDU assumes the sDU will clear the stored data message from the memory and / or release the HARQ process.
[0108] 8. The method of any one of embodiments 1-4, wherein the retransmission intent indication is included in the HARQ information message and provides an indication of an intent to subsequently transmit a retransmission request to the sDU for retransmission of the data message by the sDU.
[0109] 9. The method of embodiment 8, the method further comprising: transmitting the retransmission request to the sDU.
[0110] 10. The method of embodiment 8, wherein if the pDU does not transmit the retransmission request within a predetermined period of time after transmitting the HARQ information message, the pDU assumes the sDU will clear the stored data message from the memory and / or release the HARQ process.
[0111] 11. The method of embodiment 7 or 10, wherein the predetermined period of time is configured by the pDU.
[0112] 12. The method of embodiment 11, wherein the predetermined period of time is configured specific to the sDU.
[0113] 13. The method of embodiment 11, wherein the predetermined period of time is configured specific to the SCell hosted by the sDU.
[0114] 14. The method of embodiment 11, wherein the predetermined period of time is configured by indicating a fixed number of slots.
[0115] 15. The method of embodiment 14, wherein the fixed number of slots are specified according to a subcarrier spacing in use by the SCell.
[0116] 16. The method of any one of the previous embodiments, wherein the HARQ information message is transmitted over a D2 interface between the pDU and the sDU.
[0117] 17. A method performed by a network node operating as a Distributed Unit (DU) hosting an SCell (sDU) for a UE in a radio access network, the method comprising:transmitting a data message associated with a HARQ process to the UE; storing the data message in memory; receiving a feedback message associated with the HARQ process from a Distributed Unit (DU) hosting a PCell (pDU) in the radio access network; and responsive to the feedback message, determining whether to clear the stored data message from the memory and / or whether to release the HARQ process.
[0118] 18. The method of embodiment 17, wherein the feedback message includes an indication of a retransmission intent that indicates to the sDU that the pDU intends to send a retransmission request to the sDU to retransmit the data message.
[0119] 19. The method of embodiment 18, wherein if no retransmission request is received a predetermined period of time after receiving the indication of the retransmission intent, clearing the stored data message from the memory and / or releasing the HARQ process.
[0120] 20. The method of embodiment 19, wherein the predetermined period of time is configured by the pDU.
[0121] 21. The method of embodiment 20, wherein the predetermined period of time is configured specific to the sDU.
[0122] 22. The method of embodiment 21, wherein the predetermined period of time is configured specific to the SCell hosted by the sDU.
[0123] 23. The method of embodiment 21, wherein the predetermined period of time is configured by indicating a fixed number of slots.
[0124] 24. The method of embodiment 23, wherein the fixed number of slots are specified according to a subcarrier spacing in use by the SCell.
[0125] 25. The method of embodiment 17, wherein the feedback message explicitly indicates to the sDU to delete the stored data message and / or release the HARQ process.
[0126] 26. A network node comprising: processing circuitry configured to perform the steps of either one of embodiments 1 or 17; power supply circuitry configured to supply power to the processing circuitry.
Claims
CLAIMS1. A method (400) performed by a first distributed unit hosting a primary cell for a user equipment in a radio access network, the method comprising:receiving (410) hybrid automatic repeat request (HARQ) feedback associated with a data message transmitted by a second distributed unit to the user equipment, the second distributed unit hosting a secondary cell for the user equipment;responsive to the HARQ feedback, determining (420) whether to include a retransmission intent indication in a HARQ information message to be transmitted to the second distributed unit, the retransmission intent indication being indicative of whether the data message associated with the HARQ feedback is to be retransmitted; and transmitting (430) the HARQ information message to the second distributed unit.
2. The method of claim 1, wherein determining whether to include the retransmission intent indication in the HARQ information message includes determining whether the data message is to be retransmitted.
3. The method of claim 2, wherein determining whether the data message is to be retransmitted includes one or more of:determining that the HARQ feedback does not include an acknowledgment; evaluating a signal strength characteristic associated with the data message; or determining whether a HARQ process timer associated with the data message has elapsed.
4. The method of any of claims 1-3, wherein the data message is a transport block.
5. The method of any of claims 1-4, wherein the retransmission intent indication is included in the HARQ information message and indicates to the second distributed unit to delete the data message from memory.
6. The method of claim 5, wherein the retransmission intent indication further indicates to the second distributed unit to release a HARQ process associated with the data message.
7. The method of any of claims 1-4, wherein the HARQ information message includes the HARQ feedback received by the first distributed unit.
8. The method of claim 7, wherein when the HARQ information message does not include the retransmission intent indication and the first distributed unit does not transmit a retransmission request within a predetermined period of time after transmitting the HARQ information message, the first distributed unit assumes the second distributed unit will clear the stored data message from memory.
9. The method of any of claims 1-4, wherein the retransmission intent indication is included in the HARQ information message and provides an indication of an intent to subsequently transmit a retransmission request to the second distributed unit for retransmission of the data message.
10. The method of claim 9, further comprising:transmitting (440) the retransmission request to the second distributed unit.
11. The method of claim 9, wherein if the first distributed unit does not transmit the retransmission request within a predetermined period of time after transmitting the HARQ information message, the first distributed unit assumes the second distributed unit will clear the stored data message from memory and release the HARQ process.
12. The method of claim 8 or 11, wherein the predetermined period of time is configured by the first distributed unit.
13. The method of claim 12, wherein the predetermined period of time is configured specific to the second distributed unit.
14. The method of claim 12, wherein the predetermined period of time is configured specific to the secondary cell hosted by the second distributed unit.
15. The method of claim 12, wherein the predetermined period of time is configured by indicating a fixed number of slots.
16. The method of claim 15, wherein the fixed number of slots is specified according to a subcarrier spacing in use by the secondary cell.
17. The method of any of claims 1-16, wherein the HARQ information message is transmitted over a D2 interface between the first distributed unit and the second distributed unit.
18. A method (500) performed by a first distributed unit hosting a secondary cell for a user equipment in a radio access network, the method comprising:transmitting (510) a data message associated with a HARQ process to the user equipment;storing (520) the data message in memory;receiving (530) a feedback message associated with the HARQ process from a second distributed unit hosting a primary cell for the user equipment; and responsive to the feedback message, determining (540) whether to clear the stored data message from the memory or whether to release the HARQ process.
19. The method of claim 18, wherein the feedback message includes an indication of a retransmission intent that indicates to the first distributed unit that the second distributed unit intends to send a retransmission request to the first distributed unit to retransmit the data message.
20. The method of claim 19, wherein if no retransmission request is received within a predetermined period of time after receiving the indication of the retransmission intent, clearing the stored data message from the memory and releasing the HARQ process.
21. The method of claim 20, wherein the predetermined period of time is configured by the second distributed unit.
22. The method of claim 21, wherein the predetermined period of time is configured by indicating a fixed number of slots specified according to a subcarrier spacing in use by the secondary cell.
23. The method of claim 18, wherein the feedback message includes a clear indicationthat indicates to the first distributed unit to delete the stored data message and release the HARQ process.
24. A network node configured to operate as a first distributed unit hosting a primary cell for a user equipment in a radio access network, the network node comprising:a receiver configured to receive hybrid automatic repeat request (HARQ) feedback associated with a data message transmitted by a second distributed unit to the user equipment, the second distributed unit hosting a secondary cell for the user equipment;a processor configured to, responsive to the HARQ feedback, determine whether to include a retransmission intent indication in a HARQ information message to be transmitted to the second distributed unit, the retransmission intent indication being indicative of whether the data message associated with the HARQ feedback is to be retransmitted; anda transmitter configured to transmit the HARQ information message to the second distributed unit.
25. The network node of claim 24, wherein the processor is further configured to determine whether to include the retransmission intent indication in the HARQ information message by determining whether the data message is to be retransmitted.
26. The network node of claim 25, wherein the processor is configured to determine whether the data message is to be retransmitted by one or more of:determining that the HARQ feedback does not include an acknowledgment; evaluating a signal strength characteristic associated with the data message; or determining whether a HARQ process timer associated with the data message has elapsed.
27. The network node of any of claims 24-26, wherein the data message is a transport block.
28. The network node of any of claims 24-27, wherein the retransmission intent indication is included in the HARQ information message and indicates to the second distributed unit to delete the data message from memory.
29. The network node of claim 28, wherein the retransmission intent indication further indicates to the second distributed unit to release a HARQ process associated with the data message.
30. The network node of any of claims 24-27, wherein the HARQ information message includes the HARQ feedback received by the receiver.
31. The network node of claim 30, wherein when the HARQ information message does not include the retransmission intent indication and the transmitter does not transmit a retransmission request within a predetermined period of time after transmitting the HARQ information message, the processor is configured to assume the second distributed unit will clear the stored data message from memory.
32. The network node of any of claims 24-27, wherein the retransmission intent indication is included in the HARQ information message and provides an indication of an intent to subsequently transmit a retransmission request to the second distributed unit for retransmission of the data message.
33. The network node of claim 32, wherein the transmitter is further configured to transmit the retransmission request to the second distributed unit.
34. The network node of claim 32, wherein if the transmitter does not transmit the retransmission request within a predetermined period of time after transmitting the HARQ information message, the processor is configured to assume the second distributed unit will clear the stored data message from memory and release the HARQ process.
35. The network node of claim 31 or 34, wherein the predetermined period of time is configured by the processor.
36. A network node configured to operate as a first distributed unit hosting a secondary cell for a user equipment in a radio access network, the network node comprising:a transmitter configured to transmit a data message associated with a HARQ process to the user equipment;a memory configured to store the data message;a receiver configured to receive a feedback message associated with the HARQ process from a second distributed unit hosting a primary cell for the user equipment; and a processor configured to, responsive to the feedback message, determine whether to clear the stored data message from the memory or whether to release the HARQ process.
37. The network node of claim 36, wherein the feedback message includes an indication of a retransmission intent that indicates to the first distributed unit that the second distributed unit intends to send a retransmission request to the first distributed unit to retransmit the data message.
38. The network node of claim 37, wherein if no retransmission request is received within a predetermined period of time after receiving the indication of the retransmission intent, the processor is configured to clear the stored data message from the memory and release the HARQ process.
39. The network node of claim 38, wherein the predetermined period of time is configured by the second distributed unit.
40. The network node of claim 39, wherein the predetermined period of time is configured by indicating a fixed number of slots specified according to a subcarrier spacing in use by the secondary cell.
41. The network node of claim 36, wherein the feedback message includes a clear indication that indicates to the first distributed unit to delete the stored data message and release the HARQ process.
