WO2023148335A1 - Configurabilité améliorée pour planification semi-persistante et autorisations configurées - Google Patents

Configurabilité améliorée pour planification semi-persistante et autorisations configurées Download PDF

Info

Publication number
WO2023148335A1
WO2023148335A1 PCT/EP2023/052695 EP2023052695W WO2023148335A1 WO 2023148335 A1 WO2023148335 A1 WO 2023148335A1 EP 2023052695 W EP2023052695 W EP 2023052695W WO 2023148335 A1 WO2023148335 A1 WO 2023148335A1
Authority
WO
WIPO (PCT)
Prior art keywords
application data
resources
applicable
configurations
allocation
Prior art date
Application number
PCT/EP2023/052695
Other languages
English (en)
Inventor
Giuseppe CASO
Du Ho KANG
Jose Luis Pradas
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2023148335A1 publication Critical patent/WO2023148335A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation

Definitions

  • the present disclosure relates generally to wireless communication networks, and more specifically to techniques for reducing communication latency or delay over such networks for applications (e.g., extended reality (XR) and cloud gaming) needing guaranteed low latency.
  • applications e.g., extended reality (XR) and cloud gaming
  • NR New Radio
  • 3GPP Third-Generation Partnership Project
  • eMBB enhanced mobile broadband
  • MTC machine type communications
  • URLLC ultra-reliable low latency communications
  • D2D side-link device-to-device
  • FIG. 1 illustrates an exemplary high-level view of the 5G network architecture, consisting of a Next Generation RAN (NG-RAN) 199 and a 5G Core (5GC) 198.
  • NG-RAN 199 can include a set of gNodeB’s (gNBs) connected to the 5GC via one or more NG interfaces, such as gNBs 100, 150 connected via interfaces 102, 152, respectively.
  • the gNBs can be connected to each other via one or more Xn interfaces, such as Xn interface 140 between gNBs 100 and 150.
  • gNBs On the NR interface toward user equipment (UEs), each of the gNBs can support frequency division duplexing (FDD), time division duplexing (TDD), or a combination thereof.
  • FDD frequency division duplexing
  • TDD time division duplexing
  • NG-RAN 199 is layered into a Radio Network Layer (RNL) and a Transport Network Layer (TNL).
  • RNL Radio Network Layer
  • TNL Transport Network Layer
  • the TNL For each NG-RAN interface (NG, Xn, Fl), the TNL provides services for user plane transport and signaling transport.
  • the NG RAN logical nodes shown in Figure 1 include a central (or centralized) unit (CU or gNB-CU) and one or more distributed (or decentralized) units (DU or gNB-DU).
  • gNB 100 includes gNB-CU 110 and gNB-DUs 120 and 130.
  • CUs e.g., gNB-CU 110
  • CUs are logical nodes that host higher-layer protocols and perform various gNB functions such controlling the operation of DUs.
  • Each DU is a logical node that hosts lower-layer protocols and can include, depending on the functional split, various subsets of the gNB functions.
  • each of the CUs and DUs can include various circuitry needed to perform their respective functions, including processing circuitry, transceiver circuitry (e.g., for communication), and power supply circuitry.
  • a gNB-CU connects to gNB-DUs over respective Fl logical interfaces, such as interfaces 122 and 132 shown in Figure 1.
  • the gNB-CU and connected gNB-DUs are only visible to other gNBs and the 5GC as a gNB. In other words, the Fl interface is not visible beyond gNB-CU.
  • uplink (UL, i.e., UE to RAN) and downlink (DL, i.e., RAN to UE) data transmissions can take place with or without an explicit grant or assignment of resources by the network (e.g., gNB).
  • UL transmissions are usually referred to as being “granted” by the network (i.e., “UL grant”), while DL transmissions are usually referred to as taking place on resources that are “assigned” by the network i.e., “DL assignment”).
  • DCI downlink control information
  • a transmission without an explicit grant/assignment is typically configured to occur with a defined periodicity.
  • the UE can then initiate a data transmission and/or receive data according to a predefined configuration.
  • Such transmissions can be referred to as semi-persistent scheduling (SPS, for DL), configured grant (CG, for UL), or grant-free transmissions.
  • SPS/CG functionality has been specified primarily with specific scenarios or use cases.
  • URLLC services in industrial Internet of Things (IIoT) applications which in general require periodic transmission of fixed and small-sized data packets under rather stable system conditions (e.g., static devices).
  • Type-1 are configured via radio resource control (RRC) signaling only, while for Type-2, some parameters are configured via RRC signaling and some PHY parameters are dynamically indicated via DCI that also activates/deactivates the grant.
  • RRC configuration of a UL configured grant includes various parameters, including a configuredGrantTimer value used for controlling operation of hybrid ARQ (HARQ) processes in the UL via a controlled grant timer (“CG timer”) in the UE.
  • CG timer controlled grant timer
  • the UE acknowledges activation/deactivation of a Type-2 UL CG by sending a medium access control (MAC) Control Element (CE).
  • MAC medium access control
  • CE Control Element
  • a related feature is Autonomous Uplink (AUL), which can support autonomous HARQ retransmissions using an UL CG.
  • DL SPS operates in a similar manner as Type-2 UL CG.
  • RRC configuration of SPS includes periodicity of the assignment, resource allocation in time and frequency, etc.
  • NR Release 16 includes various enhancements to UL CG and DL SPS, including reduced periodicity (e.g., from 10 ms to one DL slot for SPS) and the use of multiple SPSs/CGs in parallel by a single UE.
  • reduced periodicity e.g., from 10 ms to one DL slot for SPS
  • Each SPS/CG requires a dedicated DCI/RRC message exchange for its activation, but multiple SPS/CGs can be deactivated simultaneously.
  • XR Extended Reality
  • Cloud Gaming are important 5G media applications now under consideration in the industry.
  • XR is an umbrella term that refers to all real-and-virtual combined environments and human-machine interactions generated by computer technology and wearables.
  • XR includes Augmented Reality (AR), Mixed Reality (MR), and Virtual Reality (VR), as well as various other types that span or sit between these examples.
  • AR Augmented Reality
  • MR Mixed Reality
  • VR Virtual Reality
  • the term “XR” also refers to cloud gaming and related applications.
  • data traffic for XR applications is a mixture of heterogeneous UL/DL data flows, including video, audio, and control traffic. More specifically, XR traffic includes a mixture of pose, control, and video from/to the same XR device, varying video frame size over time, and quasi-periodic packet arrival with application jitter after IP segmentation.
  • Video traffic is typically associated with a video frame rate (also referred to as “frame refresh rate”).
  • frame refresh rate also referred to as “frame refresh rate”.
  • the inter-arrival time of video frames is the reciprocal of the frame refresh rate.
  • Typical frame refresh rates are 30, 60, 90, and 120 Hz, with the specific rate being dependent on application needs and the capabilities of the video source and destination (e.g., VR headset).
  • DL/UL video to/from the XR device may have the same or different frame rates. Note that the video frame rate is generally independent of, or unrelated to, the NR radio interface timing.
  • Pose refers generally to the orientation and/or positioning of the user of the XR device or of another object. Pose information can be determined or estimated by identifying, locating, and tracking various keypoints on the user or other object. Object keypoints include comers or other notable features, while human keypoints can include major joints such as elbow, shoulder, wrist, ankle, knee, etc.
  • the main XR performance indicator is latency defined in terms of Packet Delay Budget (PDB).
  • PDB Packet Delay Budget
  • XR latency requirements are not as strict as latency requirements for URLLC services, but it needs to be satisfied for traffic having significantly higher data rates than URLLC traffic. As such, XR is usually considered a mixed URLLC/eMBB service requiring specific enhancements for full support in 5G NR networks and beyond.
  • Embodiments of the present disclosure provide specific improvements to communication between UEs and network nodes in a wireless network, such as by providing, enabling, and/or facilitating solutions to overcome exemplary problems summarized above and described in more detail below.
  • Embodiments include methods (e.g., procedures) for a UE configured to transmit and receive application data in a wireless network.
  • These exemplary methods can include receiving, from a RAN node, an allocation of resources for transmission or reception of periodically arriving application data.
  • the allocation is based on a plurality of configurations of periodic resources, and the plurality of configurations are applicable during a respective plurality of non-overlapping time periods.
  • These exemplary methods can also include transmitting or receiving the periodically arriving application data with the RAN node using the allocated resources. Each arrival of application data is transmitted or received using periodic resources from a configuration that is applicable at the time of the transmission or reception.
  • each configuration includes the following:
  • At least two of the plurality of configurations have different lengths and/or different periodicities.
  • the plurality of configurations are arranged in an ordered list.
  • Each configuration in the ordered list is applicable immediately after a time period when an immediately preceding configuration the ordered list is applicable, except that an initial configuration in the ordered list is applicable immediately after a time period when a last configuration in the ordered list is applicable.
  • the allocation of resources also includes one or more of the following: an indication of a validity duration for the allocation, and an offset that indicates which configuration in the ordered list is initially applicable for transmitting or receiving the periodically arriving application data.
  • the validity duration can be indicated by a number of repetitions of the ordered list and the periodically arriving application data is transmitted or received only during the validity duration, which is equal to a product of the indicated number of repetitions and a sum of the lengths of the time periods when the respective configurations are applicable.
  • one or more of the following is an integer multiple of the arrival period of the application data: the validity duration, and the sum of the lengths of the time periods when the respective configurations are applicable.
  • transmitting or receiving the periodically arriving application data can include, in response to receiving a deactivation signal from the RAN node during the validity duration, refraining from transmitting or receiving the periodically arriving application data with the RAN node for the remainder of the validity duration.
  • the allocation is received in an RRC message, which also activates the allocation for transmitting or receiving the periodically arriving application data.
  • at least a portion of the allocation is received in an RRC message and the exemplary methods can also include receiving, from the RAN node, DCI that activates the allocation.
  • one or more of the following is included in the DCI or the RRC message: an indication of a validity duration for the allocation, and an offset that indicates which configuration in the ordered list is initially applicable for transmitting or receiving the periodically arriving application data.
  • the DCI or the RRC message includes an activation bitfield comprising a plurality of bits, with each bit indicating whether a corresponding one of the configurations is activated.
  • transmitting or receiving the periodically arriving application data can include, when one or more of the bits indicates that corresponding one or more configurations are not activated, refraining from transmitting or receiving the periodically arriving application data with the RAN node during time periods when the one or more nonactivated configurations are applicable.
  • the RAN utilizes TDD comprising periodic timeslots with UL resources and a plurality of timeslots with only DL resources intervening between successive timeslots with UL resources. Moreover, the allocation of resources are in the timeslots with UL resources.
  • the periodically arriving application data i.e., at the UE
  • each configuration includes:
  • application data has an arrival period that is a non-integer multiple of one or more of the following:
  • these exemplary methods can also include sending one of the following to the RAN node: an indication of whether all of the configurations are accepted and will be used, or a plurality of indications of whether the respective configurations are accepted and will be used.
  • transmitting or receiving the periodically arriving application data can include, when one or more of the plurality of indications indicates that corresponding one or more configurations are not accepted, refraining from transmitting or receiving the periodically arriving application data with the RAN node during time periods when the one or more non-accepted configurations are applicable.
  • the allocation of resources comprises one of the following: a type-1 CG for UL transmission by the UE; a type-2 CG for UL transmission by the UE; or an SPS assignment for DL reception by the UE.
  • inventions include exemplary methods (e.g., procedures) for a RAN node configured to transmit and receive application data with a UE.
  • These exemplary methods can include transmitting, to the UE, an allocation of resources for transmission or reception of periodically arriving application data.
  • the allocation is based on a plurality of configurations of periodic resources, and the plurality of configurations are applicable during a respective plurality of non-overlapping time periods.
  • These exemplary methods can also include transmitting or receiving the periodically arriving application data with the UE using the allocated resources. Each arrival of application data is transmitted or received using periodic resources from a configuration that is applicable at the time of the transmission or reception.
  • the plurality of configurations can have the same content, be arranged in the same manner, and/or be applied according to the same rules/conditions as summarized above for the UE embodiments.
  • transmitting or receiving the periodically arriving application data can include, in response to transmitting a deactivation signal to the UE during a validity duration for the allocation, refraining from transmitting or receiving the periodically arriving application data with the UE for the remainder of the validity duration.
  • the allocation is transmitted in an RRC message, which also activates the allocation for transmitting or receiving the periodically arriving application data.
  • at least a portion of the allocation is transmitted in an RRC message and the exemplary method can also include transmitting, to the UE, DCI that activates the allocation.
  • one or more of the following is included in the DCI or the RRC message: an indication of a validity duration for the allocation, and an offset that indicates which configuration in the ordered list is initially applicable for transmitting or receiving the periodically arriving application data.
  • the DCI or the RRC message includes an activation bitfield comprising a plurality of bits, with each bit indicating whether a corresponding one of the configurations is activated.
  • transmitting or receiving the periodically arriving application data can include, when one or more of the bits indicates that corresponding one or more configurations are not activated, refraining from transmitting or receiving the periodically arriving application data with the UE during time periods when the one or more non-activated configurations are applicable.
  • the RAN utilizes TDD comprising periodic timeslots with UL resources and a plurality of timeslots with only DL resources intervening between successive timeslots with UL resources. Moreover, the allocation of resources are in the timeslots with UL resources.
  • the periodically arriving application data includes one of the following: pose or control packets, or BSRs related to video frames.
  • application data has an arrival period that is a non-integer multiple of one or more of the following:
  • these exemplary methods can also include receiving one of the following from the UE: an indication of whether all of the configurations are accepted and will be used, or a plurality of indications of whether the respective configurations are accepted and will be used.
  • transmitting or receiving the periodically arriving application data can include, when one or more of the plurality of indications indicates that corresponding one or more configurations are not accepted, refraining from transmitting or receiving the periodically arriving application data with the UE during time periods when the one or more non-accepted configurations are applicable.
  • the allocation of resources comprises one of the following: a type-1 CG for UL transmission by the UE; a type-2 CG for UL transmission by the UE; or an SPS assignment for DL reception by the UE.
  • UEs e.g., wireless devices
  • RAN nodes e.g., base stations, eNBs, gNBs, ng-eNBs, etc., or components thereof
  • Other embodiments include non-transitory, computer-readable media storing program instructions that, when executed by processing circuitry, configure such UEs or RAN nodes to perform operations corresponding to any of the exemplary methods described herein.
  • Embodiments described herein provide flexible and efficient techniques that improve configurability of SPS/CG in a lightweight manner, to be able to handle traffic (e.g., XR pose/control and scene traffic) that has intrinsic timing misalignment with SPS/CG periodicities and network TDD transmission patterns, thus avoiding undesirable delay or latency accumulation.
  • Embodiments can facilitate more efficient and flexible SPS/CG configurations that better adapt to traffic characteristics, requirements, and system/network conditions. This can reduce application transmission latency and improve quality of experience (QoE), including for XR applications.
  • Embodiments can also avoid resource overprovisioning and increased signaling that are characteristics of conventional solutions.
  • Figures 1-2 illustrate two high-level views of an exemplary 5G/NR network architecture.
  • Figure 3 shows an exemplary configuration of NR user plane (UP) and control plane (CP) protocol stacks.
  • UP user plane
  • CP control plane
  • Figure 4 shows an exemplary flowchart of UE usage of a Type-2 CG based on an ordered list of multiple configurations, according to various embodiments of the present disclosure.
  • Figures 5-6 show timelines for transmission of pose/control packets based on an ordered list of two configurations, according to various embodiments of the present disclosure.
  • FIGS 7-8 show timelines for transmission of buffer status reports (BSRs) based on an order list of two configurations, according to various embodiments of the present disclosure.
  • Figure 9 shows a flow diagram of an exemplary method for a UE (e.g., wireless device), according to various embodiments of the present disclosure.
  • a UE e.g., wireless device
  • Figure 10 shows a flow diagram of an exemplary method for a RAN node (e.g., base station, eNB, gNB, ng-eNB, etc.), according to various embodiments of the present disclosure.
  • a RAN node e.g., base station, eNB, gNB, ng-eNB, etc.
  • Figure 11 shows a communication system according to various embodiments of the present disclosure.
  • Figure 12 shows a UE according to various embodiments of the present disclosure.
  • Figure 13 shows a network node according to various embodiments of the present disclosure.
  • Figure 14 shows host computing system according to various embodiments of the present disclosure.
  • Figure 15 is a block diagram of a virtualization environment in which functions implemented by some embodiments of the present disclosure may be virtualized.
  • Figure 16 illustrates communication between a host computing system, a network node, and a UE via multiple connections, at least one of which is wireless, according to various embodiments of the present disclosure.
  • Radio Access Node As used herein, a “radio access node” (or equivalently “radio network node,” “radio access network node,” or “RAN node”) can be any node in a radio access network (RAN) that operates to wirelessly transmit and/or receive signals.
  • RAN radio access network
  • a radio access node examples include, but are not limited to, a base station (e.g., gNB in a 3 GPP 5G/NR network or an enhanced or eNB in a 3GPP LTE network), base station distributed components (e.g., CU and DU), a high-power or macro base station, a low-power base station (e.g., micro, pico, femto, or home base station, or the like), an integrated access backhaul (IAB) node, a transmission point (TP), a transmission reception point (TRP), a remote radio unit (RRU or RRH), and a relay node.
  • a base station e.g., gNB in a 3 GPP 5G/NR network or an enhanced or eNB in a 3GPP LTE network
  • base station distributed components e.g., CU and DU
  • a high-power or macro base station e.g., a low-power base station (e.g., micro
  • a “core network node” is any type of node in a core network.
  • Some examples of a core network node include, e.g., a Mobility Management Entity (MME), a serving gateway (SGW), a PDN Gateway (P-GW), a Policy and Charging Rules Function (PCRF), an access and mobility management function (AMF), a session management function (SMF), a user plane function (UPF), a Charging Function (CHF), a Policy Control Function (PCF), an Authentication Server Function (AUSF), a location management function (LMF), or the like.
  • MME Mobility Management Entity
  • SGW serving gateway
  • P-GW PDN Gateway
  • PCRF Policy and Charging Rules Function
  • AMF access and mobility management function
  • SMF session management function
  • UPF user plane function
  • Charging Function CHF
  • PCF Policy Control Function
  • AUSF Authentication Server Function
  • LMF location management function
  • Wireless Device As used herein, a “wireless device” (or “WD” for short) is any type of device that is capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices. Communicating wirelessly can involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air.
  • wireless device is used interchangeably herein with the term “user equipment” (or “UE” for short), with both of these terms having a different meaning than the term “network node”.
  • Radio Node can be either a “radio access node” (or equivalent term) or a “wireless device.”
  • Network Node is any node that is either part of the radio access network (e.g., a radio access node or equivalent term) or of the core network (e.g., a core network node discussed above) of a cellular communications network.
  • a network node is equipment capable, configured, arranged, and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the cellular communications network, to enable and/or provide wireless access to the wireless device, and/or to perform other functions (e.g., administration) in the cellular communications network.
  • Base station may comprise a physical or a logical node transmitting or controlling the transmission of radio signals, e.g., eNB, gNB, ng-eNB, en- gNB, centralized unit (CU)/distributed unit (DU), transmitting radio network node, transmission point (TP), transmission reception point (TRP), remote radio head (RRH), remote radio unit (RRU), Distributed Antenna System (DAS), relay, etc.
  • eNB e.g., eNB, gNB, ng-eNB, en- gNB, centralized unit (CU)/distributed unit (DU), transmitting radio network node, transmission point (TP), transmission reception point (TRP), remote radio head (RRH), remote radio unit (RRU), Distributed Antenna System (DAS), relay, etc.
  • node can be any type of node that can in or with a wireless network (including RAN and/or core network), including a radio access node (or equivalent term), core network node, or wireless device.
  • a wireless network including RAN and/or core network
  • radio access node or equivalent term
  • core network node or wireless device.
  • node may be limited to a particular type (e.g., radio access node) based on its specific characteristics in any given context.
  • FIG. 2 shows another high-level view of an exemplary 5G network architecture, including NG-RAN 299 and 5GC 298.
  • NG-RAN 299 can include gNBs (e.g., 210a,b) and ng-eNBs (e.g., 220a, b) that are interconnected with each other via respective Xn interfaces.
  • the gNBs and ng-eNBs are also connected via the NG interfaces to 5GC 298, more specifically to the Access and Mobility Management Function (AMF, e.g., 230a,b) via respective NG-C interfaces and to the User Plane Function (UPF, e.g., 240a, b) via respective NG-U interfaces.
  • AMFs 230a,b can communicate with one or more policy control functions (PCFs, e.g., 250a, b) and network exposure functions (NEFs, e.g., 260a, b).
  • PCFs policy control functions
  • Each of the gNBs can support the NR radio interface including frequency division duplexing (FDD), time division duplexing (TDD), or a combination thereof.
  • Each of ng-eNBs can support the fourth generation (4G) Long-Term Evolution (LTE) radio interface. Unlike conventional LTE eNBs, however, ng-eNBs connect to the 5GC via the NG interface.
  • Each of the gNBs and ng-eNBs can serve a geographic coverage area including one more cells, such as cells 21 la-b and 221a-b shown in Figure 2.
  • a UE 205 can communicate with the gNB or ng-eNB serving that cell via the NR or LTE radio interface, respectively.
  • Figure 2 shows gNBs and ng-eNBs separately, it is also possible that a single NG-RAN node provides both types of functionality.
  • NR uses CP-OFDM (Cyclic Prefix Orthogonal Frequency Division Multiplexing) in the DL and both CP-OFDM and DFT-spread OFDM (DFT-S-OFDM) in the UL.
  • CP-OFDM Cyclic Prefix Orthogonal Frequency Division Multiplexing
  • DFT-S-OFDM DFT-spread OFDM
  • NR DL and UL physical resources are organized into equal-sized 1-ms subframes. A subframe is further divided into multiple slots of equal duration, with each slot including multiple OFDM-based symbols.
  • time-frequency resources can be configured much more flexibly for an NR cell than for an LTE cell.
  • NR networks also provide coverage via “beams.”
  • a DL “beam” is a coverage area of a network-transmitted reference signal (RS) that may be measured/monitored by a UE.
  • RS network-transmitted reference signal
  • Figure 3 shows an exemplary configuration of NR user plane (UP) and control plane (CP) protocol stacks between a UE (310), a gNB (320), and an AMF (330), such as those shown in Figures 1-2.
  • the Physical (PHY), Medium Access Control (MAC), Radio Link Control (RLC), and Packet Data Convergence Protocol (PDCP) layers between the UE and the gNB are common to UP and CP.
  • the PDCP layer provides ciphering/deciphering, integrity protection, sequence numbering, reordering, and duplicate detection for both CP and UP.
  • PDCP provides header compression and retransmission for UP data.
  • IP Internet protocol
  • SDU service data units
  • PDU protocol data units
  • the RLC layer transfers PDCP PDUs to the MAC through logical channels (LCH).
  • LCH logical channels
  • RLC provides error detection/correction, concatenation, segmentation/reassembly, sequence numbering, reordering of data transferred to/from the upper layers. If RLC receives a discard indication from associated with a PDCP PDU, it will discard the corresponding RLC SDU (or any segment thereof) if it has not been sent to lower layers.
  • the MAC layer provides mapping between LCHs and PHY transport channels, LCH prioritization, multiplexing into or demultiplexing from transport blocks (TBs), hybrid ARQ (HARQ) error correction, and dynamic scheduling (on gNB side).
  • the PHY layer provides transport channel services to the MAC layer and handles transfer over the NR radio interface, e.g., via modulation, coding, antenna mapping, and beam forming.
  • the Service Data Adaptation Protocol (SDAP) layer handles quality-of-service (QoS). This includes mapping between QoS flows and Data Radio Bearers (DRBs) and marking QoS flow identifiers (QFI) in UL and DL packets.
  • QoS quality-of-service
  • DRBs Data Radio Bearers
  • QFI QoS flow identifiers
  • the non-access stratum (NAS) layer is between UE and AMF and handles UE/gNB authentication, mobility management, and security control.
  • the RRC layer sits below NAS in the UE but terminates in the gNB rather than the AMF.
  • RRC controls communications between UE and gNB at the radio interface as well as the mobility of a UE between cells in the NG-RAN.
  • RRC also broadcasts system information (SI) and performs establishment, configuration, maintenance, and release of DRBs and Signaling Radio Bearers (SRBs) and used by UEs.
  • SI system information
  • SRBs Signaling Radio Bearers
  • RRC controls addition, modification, and release of carrier aggregation (CA) and dual -connectivity (DC) configurations for UEs.
  • CA carrier aggregation
  • DC dual -connectivity
  • RRC also performs various security functions such as key management.
  • RRC IDLE state After a UE is powered ON it will be in the RRC IDLE state until an RRC connection is established with the network, at which time the UE will transition to RRC CONNECTED state (e.g., where data transfer can occur). The UE returns to RRC IDLE after the connection with the network is released.
  • RRC IDLE state the UE’s radio is active on a discontinuous reception (DRX) schedule configured by upper layers.
  • DRX active periods also referred to as “DRX On durations”
  • an RRC IDLE UE receives SI broadcast in the cell where the UE is camping, performs measurements of neighbor cells to support cell reselection, and monitors a paging channel on PDCCH for pages from 5GC via gNB.
  • NR RRC includes an RRC_INACTIVE state in which a UE is known (e.g., via UE context) by the serving gNB.
  • RRC INACTIVE has some properties similar to a “suspended” condition used in LTE.
  • NR DL and UL physical resources are organized into equal-sized 1-ms subframes.
  • a subframe is further divided into multiple slots of equal duration, with each slot including multiple OFDM-based symbols.
  • An NR slot can include 14 OFDM symbols for normal cyclic prefix and 12 symbols for extended cyclic prefix.
  • a resource block (RB) consists of a group of 12 contiguous OFDM subcarriers for a duration of a 12- or 14-symbol slot.
  • a resource element (RE) corresponds to one OFDM subcarrier during one OFDM symbol interval.
  • a UE can be configured with up to four carrier bandwidth parts (BWPs) in the DL with a single DL BWP being active at a given time.
  • BWPs carrier bandwidth parts
  • a UE can be configured with up to four BWPs in the UL with a single UL BWP being active at a given time.
  • the UE can be configured with up to four additional BWPs in the supplementary UL, with a single supplementary UL BWP being active at a given time.
  • Common RBs are numbered from 0 to the end of the carrier bandwidth.
  • Each BWP configured for a UE has a common reference of CRBO, such that a configured BWP may start at a CRB greater than zero.
  • CRBO can be identified by one of the following parameters provided by the network, as further defined in 3GPP TS 38.211 section 4.4:
  • PCell e.g., PCell or PSCell
  • a UE can be configured with a narrow BWP (e.g., 10 MHz) and a wide BWP (e.g., 100 MHz), each starting at a particular CRB, but only one BWP can be active for the UE at a given point in time.
  • BWP narrow BWP
  • 100 MHz wide BWP
  • PRBs are defined and numbered in the frequency domain from 0 to “1 , where i is the index of the particular BWP for the carrier.
  • 3 GPP Release 17 includes a study item (SI) on XR Evaluations for NR.
  • SI study item
  • the main objectives are to identify the traffic model for each application of interest and the evaluation methodology and the key performance indicators of interest for relevant deployment scenarios, and to carry out performance evaluations accordingly in order to investigate possible standardization enhancements in potential follow-up SI or work item (WI).
  • the main XR performance indicator is latency defined in terms of Packet Delay Budget (PDB).
  • PDB Packet Delay Budget
  • XR latency requirements are not as strict as latency requirements for URLLC services, but they need to be satisfied for traffic having significantly higher data rates than URLLC traffic.
  • XR is usually considered a mixed URLLC/eMBB service requiring specific enhancements for full support in 5G NR networks and beyond.
  • Table 2 below shows the main XR traffic characteristics and requirements currently identified by 3GPP
  • Table 2 also highlights that XR traffic is periodic, being represented by a packet rate in frames per second (fps). This is one reason why periodic SPS/CG are being considered for use in XR applications.
  • fps frames per second
  • SPS/CG provide resources that are static in size and strictly periodic.
  • SPS/CG periodicity e.g., in Rel-15 and Rel-16
  • TDD Time Division Duplex
  • CG-based transmission of pose/control traffic and CG-based transmission of Buffer State Reports (BSRs) generated by the UE to inform the network about resources needed for transmitting incoming scene frames.
  • BSRs Buffer State Reports
  • Both use cases minimize the challenges related to large size and variability, since pose/control and BSR traffic have small, fixed sizes and do not require dynamic resource adaptation. For example, this traffic will generally fit in a single Transport Block (TB) (and thus a single UL slot) independent of the MCS and PRBs allocated for each CG occasion.
  • TB Transport Block
  • pose/control is not expected to be affected by jitter, while jitter models for scene traffic is still under discussion by 3GPP.
  • a reasonable UL CG periodicity is one CG occasion every ninth UL slot (i.e., a CG slot is followed by eight unconfigured UL slots).
  • seven UL slots are available between the first two scene frames.
  • a reasonable UL CG periodicity is one CG occasion every seventh UL slot (i.e., a CG slot is followed by six unconfigured UL slots).
  • Table 4 below shows how the transmission timeframe would look like for these TDD patterns.
  • BSRs for scene traffic cannot be optimally transmitted on the available CG slots.
  • BSRs experience increasing delays that negatively impact the entire transmission and eventually hinder the possibility to meet the 30-ms PDB (according to Table 2, above).
  • both solutions can lead to excess network signaling.
  • activation of multiple CGs with different starting times requires dedicated signaling for each CG.
  • the network could deactivate CGs when not needed and re-activate them when needed.
  • this deactivation/reactivation also increases the network signaling load.
  • current solutions require undesirable compromises between resource overprovisioning and excess network signaling.
  • embodiments of the present disclosure provide flexible and efficient techniques to enhance configurability of an SPS/CG by activating it with an ordered list of multiple configurations, rather than a unique configuration as currently specified by 3GPP.
  • the configurations in the ordered list may grant different resources in term of MCS, PRBs, periodicity, etc., thereby improving configurability of the corresponding SPS/CG.
  • the configurations in the ordered list can include or be set with an expiration indication so that the UE knows when a currently used configuration expires and is replaced by the next configuration in the list.
  • the ordered list of configurations defining the SPS/CG can be active until expiration of a timer provided in the activation message and/or until a deactivation DCI is sent to the UE.
  • the UE may acknowledge (e.g., via MAC CE) the complete list of configurations or a subset of the configurations comprising the list. In the latter case, the UE must maintain time alignment with the entire list of configurations, thus avoiding the use of CG occurrences made available by configurations it did not select.
  • Embodiments of the present disclosure provide various benefits and/or advantages.
  • embodiments improve the configurability of SPS/CG in a lightweight manner, to be able to handle traffic (e.g., XR pose/control and scene traffic) that has intrinsic timing misalignment with SPS/CG periodicities and network TDD transmission patterns, thus avoiding undesirable delay accumulation.
  • traffic e.g., XR pose/control and scene traffic
  • Embodiments also facilitate more efficient and flexible SPS/CG configurations that better adapt to traffic characteristics, requirements, and system/network conditions.
  • Embodiments can also avoid resource overprovisioning and increased signaling that are characteristics of conventional solutions.
  • SPS and CG are activated via DCI and RRC messages with a single set of configuration parameters. For example, with SPS and CG Type 2, periodicity is provided in the RRC message while other parameters such as MCS, PRBs, etc. are provided in DCI. This set of parameters completely defines an SPS/CG and indicates to the UE how to use the corresponding resources. A new SPS or CG must be activated if different resources are needed. As discussed above, a single set of configuration parameters limits the adaptability of the SPS/CG and results in issues for use cases such UL transmissions of pose/control data and BSRs for scene traffic.
  • Embodiments of the present disclosure involve RRC configuration of a list of a plurality of SPS/CG configurations, enhanced DCI to carry additional dynamic information related to the SPS/CG configurations of the list, and MAC CE messages for activating the list and acknowledging list activation and/or specific configurations within the list.
  • each configuration of the list When a list is activated, each configuration of the list will be activated individually only for an associated period of time. After that defined period, the next configuration in the list will be activated for another associated period of time. When the activation period for the last has ended, the first configuration in the list is re-activated for the associated period, with the process repeating until the entire list is deactivated.
  • an SPS/CG may be activated to use a list of configurations, with the order of the configurations in the list corresponding to the order in which they are activated/used.
  • Each configuration may grant different resources.
  • each configuration includes or is associated with an expiration indication, i.e., of when the configuration expires and the next configuration in the list is activated.
  • the list is circular, such that the first configuration is used when the last configuration expires while the SPS/CG is still active (i.e., has not been deactivated by the network).
  • the entire list corresponding to the SPS/CG may have an expiration, a so-called “global expiration.”
  • the network can inform the UE about the global expiration by an indication (“global expiration indication”) in the SPS/CG activation messages (i.e., in DCI or RRC, depending on implementation choice).
  • the global expiration indication can be defined, for example, in terms of the total number of DL/UL slots or number of list cycles during which the SPS/CG is active and after which the SPS/CG is considered inactive. Otherwise, SPS/CG deactivation can use existing mechanisms, such as deactivation DCI sent to the UE.
  • a configuration offset may be provided when activating (or reactivating) the ordered list of configurations for an SPS/CG.
  • a configuration offset of zero (which may be a default value) may be used when the SPS/CG is activated for the first time, thus indicating that the first configuration in the list corresponds to the first configuration to be used.
  • a non-zero offset may be used when the SPS/CG is re-activated, indicating which configuration in the list is the first configuration to be used.
  • a UE responds to an SPS/CG activation via MAC CE, in which the UE indicates whether the entire list of configurations is accepted and will be used (which can be default) or that only some of the configurations are accepted and will be used. In the latter case, the UE can indicate the accepted configurations in the MAC CE. Even if the UE does not accept the entire list, the UE must maintain time alignment with the entire list while using the SPS/CG, thus avoiding the use of SPS/CG occasions made available by unaccepted configurations.
  • a new field can be added to CG Type 2 activation DCI so that UE can differentiate the legacy CG Type 2 activation from the new CG with the ordered list, depending on the indicated DCI bit location. It is also possible the DCI can further indicate the selection of activated multiple CG configurations in the ordered list. As a specific example, four bits of new DCI field can correspond to respective four configurations in the list. If a bit is set to “0”, a UE should skip the corresponding configuration even though it is included in the order list. When a bit is set to “1”, a UE will activate the corresponding configuration in the order specified by the list.
  • a similar field can be added to an RRC message that configures and activates CG Type 1, with the UE interpreting bit values in a similar manner.
  • #ID-CG-X a Type-2 CG
  • the activating message may also provide an expiration indication for each configuration.
  • #ID-CG-X If #ID-CG-X is active, #ID-Config-n must be used for Npxp-uL-siot-config-n consecutive UL slots. #ID-Config-n+ ⁇ must replace #ID-Config-n from slot NEXP-UL-siot-config-n+) and be used io NEXP-uL-siot-config-n+i consecutive UL slots.
  • #ID-Config-N config used for NEXP-uL-siot-config-Nconfig consecutive UL slots and #ID-CG- A is still active, a new list cycle starts and configuration #ID-Config-1 should be used for NEXP-uL-siot-config-1 consecutive UL slots starting in slot NEXP-uL-siot-config-Nconfig+ i-
  • the (RRC or DCI) activation message can also include the number of list cycles N cy cie during which #ID-CG-X is active and after which it is inactive. Based on this information, the UE can construct the following usage rule for #ID-CG-X.
  • Figure 4 shows an exemplary flowchart of UE usage of a Type-2 CG based on an ordered list of multiple configurations.
  • the exemplary flowchart is based on the three usage rules defined above and the assumption that the UE acknowledges the entire list of configurations via MAC CE.
  • CG deactivation is based on the number of list cycles, N cy de.
  • the (RRC or DCI) activation message can also include a periodicity value for each configuration in the list (e.g., #ID-CG-X).
  • the activation message may contain an ordered list of Nconfig periodicities, where the n th periodicity maps with the n th configuration of the list (i.e., periodicities in same order as configurations).
  • the n th periodicity may indicate that the n th configuration of #ID-CG-X is active in every UL slot, in every other UL slot, etc.
  • #ID-CG-X has a periodicity of NpER-uL-siot-config-n UL slots. Given this information, the UE can construct the following usage rule for each configuration #ID-Config-n of #ID-CG-X'.
  • #ID-CG-X has a periodicity of NpER-uL-siot-config-n UL slots.
  • the UE acknowledges both configurations via MAC CE, and the UE alternates between #ID-Config-1 and #ID-Config-2 with zero offset (i.e., #ID-Config-1 is initially used) until the expiration (if indicated) or a deactivation DCI is received.
  • Figure 5 shows transmission of ten (10) pose/control packets according to this solution.
  • #ID-Config-1 is used during 3 of 6 UL slots for transmitting pose/control packets 1-3.
  • #ID-Config-2 is used during the next two UL slots for transmitting packets 4-5. This arrangement avoids waiting until the next (i.e., ninth) UL slot to transmit packet 5, which would be needed if #ID-Config-1 were in use at that time.
  • the same time alignment is obtained for subsequent packets (e.g., 6, 7, etc.), making it possible to avoid delay accumulation. Note that the legend shown in Figure 5 also applies to Figures 6-8, discussed below.
  • #ID-Config-2 providing minimum resources for transmitting one pose/control packet in one slot.
  • #ID-Config-1 is used during 1 of 2 consecutive UL slots for transmitting the pose/control packet 1. Note that the grant provided by #ID-Config-1 is larger than needed for this initial packet, since it allows for transmitting two packets. Next, #ID-Config-2 is used during 3 of 6 consecutive UL slots for transmitting the packets 2-4.
  • #ID-Config-1 is re-activated and is used to transmit packets 5-6 in the same UL slot.
  • #ID-Config-2 is re-activated and is used to transmit packets 7-9.
  • #ID-Config-1 is re-activated and is used to transmit packets 10-11 in the same UL slot. This alternating sequence avoids accumulating delay as in conventional approaches.
  • #ID-Config-2 providing minimum resources for transmitting a BSR in one slot.
  • the UE acknowledges both configurations via MAC CE, and the UE alternates between #ID-Config-1 and #ID-Config-2 with zero offset (i.e., #ID-Config-1 is initially used) until the expiration (if indicated) or a deactivation DCI is received.
  • Figure 7 shows transmission of BSRs for seven (7) scene frames according to this solution.
  • #ID-Config-1 is used in one of the first nine UL slots for transmitting BSR 1.
  • #ID-Config-2 is used in the 10 th and 18 th available UL slots for transmitting BSRs 2-3.
  • #ID- Config-1 is then re-activated, the CG occasion is fully time-aligned with arrival of BSR 4. This alternating sequence avoids accumulating delay as in conventional approaches.
  • #ID-Config-2 providing minimum resources for transmitting a BSR in one slot.
  • the UE acknowledges both configurations via MAC CE, and the UE alternates between #ID-Config-1 and #ID-Config-2 with zero offset (i.e., #ID-Config-1 is initially used) until the expiration (if indicated) or a deactivation DCI is received.
  • Figure 8 shows transmission of BSRs for seven (7) scene frames according to this solution.
  • #ID-Config-1 is used in two of the first 14 UL slots for transmitting BSRs 1-2.
  • #ID-Config-2 is used in the 15 th available UL slots for transmitting BSR 3.
  • #ID-Config-1 is then re-activated, the CG occasion is fully time-aligned with arrival of BSR 4. This alternating sequence avoids accumulating delay as in conventional approaches.
  • Figures 9-10 show exemplary methods (e.g., procedures) for a UE and a RAN node, respectively.
  • exemplary methods e.g., procedures
  • various features of the operations described below correspond to various embodiments described above.
  • the exemplary methods shown in Figures 9-10 can be used cooperatively to provide various benefits, advantages, and/or solutions to problems described herein.
  • Figures 9-10 show specific blocks in particular orders, the operations of the exemplary methods can be performed in different orders than shown and can be combined and/or divided into blocks having different functionality than shown. Optional blocks or operations are indicated by dashed lines.
  • Figure 9 shows an exemplary method (e.g., procedure) for a UE configured to transmit and receive application data in a RAN, according to various embodiments of the present disclosure.
  • the exemplary method can be performed by a UE (e.g., wireless device, loT device, etc.) such as described elsewhere herein.
  • a UE e.g., wireless device, loT device, etc.
  • the exemplary method can include the operations of block 910, where the UE can receive, from a RAN node, an allocation of resources for transmission or reception of periodically arriving application data.
  • the allocation is based on a plurality of configurations of periodic resources, and the plurality of configurations are applicable during a respective plurality of nonoverlapping time periods.
  • the exemplary method can also include the operations of block 940, where the UE can transmit or receive the periodically arriving application data with the RAN node using the allocated resources. Each arrival of application data is transmitted or received using periodic resources from a configuration that is applicable at the time of the transmission or reception.
  • each configuration includes the following:
  • At least two of the plurality of configurations have different lengths and/or different periodicities.
  • the plurality of configurations are arranged in an ordered list.
  • Each configuration in the ordered list is applicable immediately after a time period when an immediately preceding configuration the ordered list is applicable, except that an initial configuration in the ordered list is applicable immediately after a time period when a last configuration in the ordered list is applicable. Examples of these embodiments include certain rules discussed above.
  • the allocation of resources also includes one or more of the following: an indication of a validity duration for the allocation, and an offset that indicates which configuration in the ordered list is initially applicable for transmitting or receiving the periodically arriving application data.
  • the validity duration can be indicated by a number of repetitions of the ordered list and the periodically arriving application data is transmitted or received only during the validity duration, which is equal to a product of the indicated number of repetitions and a sum of the lengths of the time periods when the respective configurations are applicable.
  • one or more of the following is an integer multiple of the arrival period of the application data: the validity duration, and the sum of the lengths of the time periods when the respective configurations are applicable.
  • transmitting or receiving the periodically arriving application data in block 940 can include the operations of sub-block 941, where the UE can, in response to receiving a deactivation signal from the RAN node during the validity duration, refrain from transmitting or receiving the periodically arriving application data with the RAN node for the remainder of the validity duration.
  • the allocation is received in an RRC message, which also activates the allocation for transmitting or receiving the periodically arriving application data.
  • at least a portion of the allocation is received in an RRC message and the method also includes the operations of block 930, where the UE can receive, from the RAN node, DCI that activates the allocation.
  • one or more of the following is included in the DCI or the RRC message: an indication of a validity duration for the allocation, and an offset that indicates which configuration in the ordered list is initially applicable for transmitting or receiving the periodically arriving application data.
  • the DCI or the RRC message includes an activation bitfield comprising a plurality of bits, with each bit indicating whether a corresponding one of the configurations is activated.
  • transmitting or receiving the periodically arriving application data in block 940 can include the operations of sub-block 942, where the UE can, when one or more of the bits indicates that corresponding one or more configurations are not activated, refrain from transmitting or receiving the periodically arriving application data with the RAN node during time periods when the one or more non-activated configurations are applicable.
  • the RAN utilizes TDD comprising periodic timeslots with UL resources and a plurality of timeslots with only DL resources intervening between successive timeslots with UL resources. Moreover, the allocation of resources are in the timeslots with UL resources.
  • the periodically arriving application data i.e., at the UE
  • each configuration includes:
  • application data has an arrival period that is a non-integer multiple of one or more of the following:
  • the exemplary method can also include the operations of block 920, where the UE can send one of the following to the RAN node: an indication of whether all of the configurations are accepted and will be used, or a plurality of indications of whether the respective configurations are accepted and will be used. For example, the UE can send this information in a MAC CE, as discussed above.
  • transmitting or receiving the periodically arriving application data in block 940 can include the operations of sub-block 943, where the UE can, when one or more of the plurality of indications indicates that corresponding one or more configurations are not accepted, refrain from transmitting or receiving the periodically arriving application data with the RAN node during time periods when the one or more non-accepted configurations are applicable.
  • the allocation of resources comprises one of the following:
  • Figure 10 shows an exemplary method (e.g., procedure) for a RAN node configured to transmit and receive application data with a UE, according to various embodiments of the present disclosure.
  • the exemplary method can be performed by a RAN node (e.g., base station, eNB, gNB, ng-eNB, etc., or component thereof) such as described elsewhere herein.
  • a RAN node e.g., base station, eNB, gNB, ng-eNB, etc., or component thereof
  • the exemplary method can include the operations of block 1010, where the RAN node can transmit, to the UE, an allocation of resources for transmission or reception of periodically arriving application data.
  • the allocation is based on a plurality of configurations of periodic resources, and the plurality of configurations are applicable during a respective plurality of nonoverlapping time periods.
  • the exemplary method can also include the operations of block 1040, where the RAN node can transmit or receive the periodically arriving application data with the UE using the allocated resources. Each arrival of application data is transmitted or received using periodic resources from a configuration that is applicable at the time of the transmission or reception
  • each configuration includes the following:
  • At least two of the plurality of configurations have different lengths and/or different periodicities.
  • the plurality of configurations are arranged in an ordered list.
  • Each configuration in the ordered list is applicable immediately after a time period when an immediately preceding configuration the ordered list is applicable, except that an initial configuration in the ordered list is applicable immediately after a time period when a last configuration in the ordered list is applicable. Examples of these embodiments include certain rules discussed above.
  • the allocation of resources also includes one or more of the following: an indication of a validity duration for the allocation, and an offset that indicates which configuration in the ordered list is initially applicable for transmitting or receiving the periodically arriving application data.
  • the validity duration can be indicated by a number of repetitions of the ordered list and the periodically arriving application data is transmitted or received only during the validity duration, which is equal to a product of the indicated number of repetitions and a sum of the lengths of the time periods when the respective configurations are applicable.
  • one or more of the following is an integer multiple of the arrival period of the application data: the validity duration, and the sum of the lengths of the time periods when the respective configurations are applicable.
  • transmitting or receiving the periodically arriving application data in block 1040 can include the operations of sub-block 1041, where the RAN node can, in response to transmitting a deactivation signal to the UE during the validity duration, refrain from transmitting or receiving the periodically arriving application data with the UE for the remainder of the validity duration.
  • the allocation is transmitted in an RRC message, which also activates the allocation for transmitting or receiving the periodically arriving application data.
  • at least a portion of the allocation is transmitted in an RRC message and the method also includes the operations of block 1030, where the RAN node can transmit, to the UE, DCI that activates the allocation.
  • one or more of the following is included in the DCI or the RRC message: an indication of a validity duration for the allocation, and an offset that indicates which configuration in the ordered list is initially applicable for transmitting or receiving the periodically arriving application data.
  • the DCI or the RRC message includes an activation bitfield comprising a plurality of bits, with each bit indicating whether a corresponding one of the configurations is activated.
  • transmitting or receiving the periodically arriving application data in block 1040 can include the operations of sub-block 1042, where the RAN node can, when one or more of the bits indicates that corresponding one or more configurations are not activated, refrain from transmitting or receiving the periodically arriving application data with the UE during time periods when the one or more non-activated configurations are applicable.
  • the RAN utilizes TDD comprising periodic timeslots with UL resources and a plurality of timeslots with only DL resources intervening between successive timeslots with UL resources. Moreover, the allocation of resources are in the timeslots with UL resources.
  • the periodically arriving application data i.e., at the UE
  • each configuration includes:
  • application data has an arrival period that is a non-integer multiple of one or more of the following:
  • the exemplary method can also include the operations of block 1020, where the RAN node can receive one of the following from the UE: an indication of whether all of the configurations are accepted and will be used, or a plurality of indications of whether the respective configurations are accepted and will be used.
  • the RAN node can receive this information in a MAC CE, as discussed above.
  • transmitting or receiving the periodically arriving application data in block 1040 can include the operations of sub-block 1043, where the RAN node can, when one or more of the plurality of indications indicates that corresponding one or more configurations are not accepted, refrain from transmitting or receiving the periodically arriving application data with the UE during time periods when the one or more non-accepted configurations are applicable.
  • the allocation of resources comprises one of the following:
  • some embodiments of the present disclosure can be part of RAN scheduling operations.
  • RUs Radio Units
  • DUs Distributed Units
  • CU Central Units
  • DUs hosted in edge nodes and/or co-located with the RUs
  • CUs e.g., hosted in the cloud
  • embodiments can include L1/L2 and RRC operations that can be implemented in 0-RAN DUs (O-DUs) and O- RAN CUs (O-CUs), respectively.
  • O-DUs and O-CUs interact with the O-RAN near-real-time RAN Intelligent Controller (near-RT RIC) component, which can be used to further improve operation of various embodiments (e.g., by traffic prediction, efficient SPS/CG activation/deactivation/reconfiguration, etc.).
  • Figure 11 shows an example of a communication system 1100 in accordance with some embodiments.
  • the communication system 1100 includes a telecommunication network 1102 that includes an access network 1104 (e.g., RAN) and a core network 1106, which includes one or more core network nodes 1108.
  • Access network 1104 includes one or more access network nodes, such as network nodes 11 lOa-b (one or more of which may be generally referred to as network nodes 1110), or any other similar 3 GPP access node or non-3GPP access point.
  • Network nodes 1110 facilitate direct or indirect connection of UEs, such as by connecting UEs 1112a-d (one or more of which may be generally referred to as UEs 1112) to core network 1106 over one or more wireless connections.
  • 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.
  • the communication system 1100 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 1100 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
  • UEs 1112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with network nodes 1110 and other communication devices.
  • network nodes 1110 are arranged, capable, configured, and/or operable to communicate directly or indirectly with UEs 1112 and/or with other network nodes or equipment in telecommunication network 1102 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in telecommunication network 1102.
  • core network 1106 connects network nodes 1110 to one or more hosts, such as host 1116. 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.
  • Core network 1106 includes one more core network nodes (e.g., core network node 1108) 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 1108.
  • Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF).
  • MSC Mobile Switching Center
  • MME Mobility Management Entity
  • HSS Home Subscriber Server
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • AUSF Authentication Server Function
  • SIDF Subscription Identifier De-concealing function
  • UDM Unified Data Management
  • SEPP Security Edge Protection Proxy
  • NEF Network Exposure Function
  • UPF User Plane Function
  • Host 1116 may be under the ownership or control of a service provider other than an operator or provider of access network 1104 and/or telecommunication network 1102, and may be operated by the service provider or on behalf of the service provider.
  • Host 1116 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.
  • the communication system 1100 of Figure 11 enables connectivity between the UEs, network nodes, and hosts.
  • 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.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • telecommunication network 1102 is a cellular network that implements 3 GPP standardized features. Accordingly, telecommunication network 1102 may support network slicing to provide different logical networks to different devices that are connected to telecommunication network 1102. For example, telecommunication network 1102 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.
  • URLLC Ultra Reliable Low Latency Communication
  • eMBB Enhanced Mobile Broadband
  • mMTC Massive Machine Type Communication
  • UEs 1112 are configured to transmit and/or receive information without direct human interaction.
  • a UE may be designed to transmit information to access network 1104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from access network 1104.
  • a UE may be configured for operating in single- or multi-RAT or multi-standard mode.
  • 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).
  • MR-DC multi-radio dual connectivity
  • hub 1114 communicates with access network 1104 to facilitate indirect communication between one or more UEs (e.g., UE 1112c and/or 1112d) and network nodes (e.g., network node 1110b).
  • hub 1114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs.
  • hub 1114 may be a broadband router enabling access to core network 1106 for the UEs.
  • hub 1114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 1110, or by executable code, script, process, or other instructions in hub 1114.
  • hub 1114 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.
  • hub 1114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, hub 1114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which hub 1114 then provides to the UE either directly, after performing local processing, and/or after adding additional local content.
  • hub 1114 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy loT devices.
  • Hub 1114 may have a constant/persistent or intermittent connection to the network node 1110b. Hub 1114 may also allow for a different communication scheme and/or schedule between hub 1114 and UEs (e.g., UE 1112c and/or 1112d), and between hub 1114 and core network 1106. In other examples, hub 1114 is connected to core network 1106 and/or one or more UEs via a wired connection. Moreover, hub 1114 may be configured to connect to an M2M service provider over access network 1104 and/or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with network nodes 1110 while still connected via hub 1114 via a wired or wireless connection.
  • UEs may establish a wireless connection with network nodes 1110 while still connected via hub 1114 via a wired or wireless connection.
  • hub 1114 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 1110b.
  • hub 1114 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 1110b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.
  • FIG. 12 shows a UE 1200 in accordance with some embodiments.
  • a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded/integrated wireless device, etc.
  • Other examples include any UE identified by 3 GPP, including a narrow band internet of things (NB-IoT) LIE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • NB-IoT narrow band internet of things
  • MTC machine type communication
  • eMTC enhanced MTC
  • 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).
  • D2D device-to-device
  • DSRC Dedicated Short-Range Communication
  • V2V vehicle-to-vehicle
  • V2I vehicle-to-infrastructure
  • V2X vehicle-to-everything
  • a UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device.
  • 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).
  • a UE may represent a device that is not intended for sale
  • UE 1200 includes processing circuitry 1202 that is operatively coupled via a bus 1204 to an input/output interface 1206, a power source 1208, a memory 1210, a communication interface 1212, and/or any other component, or any combination thereof.
  • processing circuitry 1202 that is operatively coupled via a bus 1204 to an input/output interface 1206, a power source 1208, a memory 1210, a communication interface 1212, and/or any other component, or any combination thereof.
  • Certain UEs may utilize all or a subset of the components shown in Figure 12. 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.
  • Processing circuitry 1202 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 memory 1210.
  • Processing circuitry 1202 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.
  • processing circuitry 1202 may include multiple central processing units (CPUs).
  • the input/output interface 1206 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 UE 1200.
  • 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.
  • USB Universal Serial Bus
  • power source 1208 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. Power source 1208 may further include power circuitry for delivering power from power source 1208 itself, and/or an external power source, to the various parts of UE 1200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of power source 1208. Power circuitry may perform any formatting, converting, or other modification to the power from power source 1208 to make the power suitable for the respective components of UE 1200 to which power is supplied.
  • an external power source e.g., an electricity outlet
  • Photovoltaic device e.g., or power cell
  • Power source 1208 may further include power circuitry for delivering power from power source 1208 itself, and/or an external power source, to the various parts of UE 1200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example,
  • Memory 1210 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.
  • memory 1210 includes one or more application programs 1214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1216.
  • Memory 1210 may store, for use by UE 1200, any of a variety of various operating systems or combinations of operating systems.
  • Memory 1210 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.
  • RAID redundant array of independent disks
  • HD-DVD high-density digital versatile disc
  • HDDS holographic digital data storage
  • DIMM external mini-dual in-line memory module
  • SDRAM synchronous dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • the UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’
  • Memory 1210 may allow UE 1200 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 memory 1210, which may be or comprise a device-readable storage medium.
  • Processing circuitry 1202 may be configured to communicate with an access network or other network using communication interface 1212.
  • Communication interface 1212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1222.
  • Communication interface 1212 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 1218 and/or a receiver 1220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth).
  • transmitter 1218 and receiver 1220 may be coupled to one or more antennas (e.g., antenna 1222) and may share circuit components, software or firmware, or alternatively be implemented separately.
  • communication functions of communication interface 1212 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.
  • 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.
  • a UE may provide an output of data captured by its sensors, through its communication interface 1212, 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., an alert is sent when moisture is detected), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).
  • 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.
  • the states of the actuator, the motor, or the switch may change.
  • 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.
  • 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.
  • loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door/window sensor, a flood/moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-t
  • AR Augmented
  • 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 3 GPP context be referred to as an MTC device.
  • the UE may implement the 3GPP NB-IoT standard.
  • 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.
  • 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.
  • 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.
  • a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.
  • Figure 13 shows a network node 1300 in accordance with some embodiments. Examples of network nodes include, but are not limited to, access points (e.g., radio access points) and base stations (e.g., radio base stations, Node Bs, eNBs, and gNBs).
  • Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations.
  • a base station may be a relay node or a relay donor node controlling a relay.
  • a network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio.
  • RRUs remote radio units
  • RRHs Remote Radio Heads
  • 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).
  • DAS distributed antenna system
  • network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and/or Minimization of Drive Tests (MDTs).
  • MSR multi-standard radio
  • RNCs radio network controllers
  • BSCs base station controllers
  • BTSs base transceiver stations
  • OFDM Operation and Maintenance
  • OSS Operations Support System
  • SON Self-Organizing Network
  • positioning nodes e.g., Evolved Serving Mobile Location Centers (E-SMLCs)
  • Network node 1300 includes a processing circuitry 1302, a memory 1304, a communication interface 1306, and a power source 1308.
  • Network node 1300 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.
  • network node 1300 comprises multiple separate components (e.g., BTS and BSC components)
  • one or more of the separate components may be shared among several network nodes.
  • a single RNC may control multiple NodeBs.
  • each unique NodeB and RNC pair may in some instances be considered a single separate network node.
  • network node 1300 may be configured to support multiple radio access technologies (RATs).
  • RATs radio access technologies
  • some components may be duplicated (e.g., separate memory 1304 for different RATs) and some components may be reused (e.g., a same antenna 1310 may be shared by different RATs).
  • Network node 1300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1300, 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 1300.
  • RFID Radio Frequency Identification
  • Processing circuitry 1302 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 1300 components, such as memory 1304, to provide network node 1300 functionality.
  • processing circuitry 1302 includes a system on a chip (SOC). In some embodiments, processing circuitry 1302 includes one or more of radio frequency (RF) transceiver circuitry 1312 and baseband processing circuitry 1314. In some embodiments, RF transceiver circuitry 1312 and baseband processing circuitry 1314 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 1312 and baseband processing circuitry 1314 may be on the same chip or set of chips, boards, or units.
  • SOC system on a chip
  • processing circuitry 1302 includes one or more of radio frequency (RF) transceiver circuitry 1312 and baseband processing circuitry 1314.
  • RF transceiver circuitry 1312 and baseband processing circuitry 1314 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 1312 and baseband processing
  • Memory 1304 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device-readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 1302.
  • volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-vola
  • Memory 1304 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 (collectively denoted computer program product 1304a) capable of being executed by processing circuitry 1302 and utilized by network node 1300. Memory 1304 may be used to store any calculations made by processing circuitry 1302 and/or any data received via communication interface 1306. In some embodiments, processing circuitry 1302 and memory 1304 is integrated.
  • Communication interface 1306 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE. As illustrated, communication interface 1306 comprises port(s)/terminal(s) 1316 to send and receive data, for example to and from a network over a wired connection. Communication interface 1306 also includes radio frontend circuitry 1318 that may be coupled to, or in certain embodiments a part of, antenna 1310. Radio front-end circuitry 1318 comprises filters 1320 and amplifiers 1322. Radio front-end circuitry 1318 may be connected to an antenna 1310 and processing circuitry 1302. The radio front-end circuitry may be configured to condition signals communicated between antenna 1310 and processing circuitry 1302.
  • Radio front-end circuitry 1318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. Radio front-end circuitry 1318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1320 and/or amplifiers 1322. The radio signal may then be transmitted via antenna 1310. Similarly, when receiving data, antenna 1310 may collect radio signals which are then converted into digital data by radio front-end circuitry 1318. The digital data may be passed to processing circuitry 1302. In other embodiments, the communication interface may comprise different components and/or different combinations of components.
  • network node 1300 does not include separate radio front-end circuitry 1318, instead, processing circuitry 1302 includes radio front-end circuitry and is connected to antenna 1310.
  • processing circuitry 1302 includes radio front-end circuitry and is connected to antenna 1310.
  • all or some of RF transceiver circuitry 1312 is part of communication interface 1306.
  • communication interface 1306 includes one or more ports or terminals 1316, radio front-end circuitry 1318, and RF transceiver circuitry 1312, as part of a radio unit (not shown), and communication interface 1306 communicates with baseband processing circuitry 1314, which is part of a digital unit (not shown).
  • Antenna 1310 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • Antenna 1310 may be coupled to radio front-end circuitry 1318 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.
  • antenna 1310 is separate from network node 1300 and connectable to network node 1300 through an interface or port.
  • Antenna 1310, communication interface 1306, and/or processing circuitry 1302 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, antenna 1310, communication interface 1306, and/or processing circuitry 1302 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.
  • Power source 1308 provides power to the various components of network node 1300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source 1308 may further comprise, or be coupled to, power management circuitry to supply the components of network node 1300 with power for performing the functionality described herein.
  • network node 1300 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 power source 1308.
  • power source 1308 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.
  • Embodiments of network node 1300 may include additional components beyond those shown in Figure 13 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.
  • network node 1300 may include user interface equipment to allow input of information into network node 1300 and to allow output of information from network node 1300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 1300.
  • FIG 14 is a block diagram of a host 1400, which may be an embodiment of host 1116 of Figure 11, in accordance with various aspects described herein.
  • Host 1400 may be or comprise various combinations hardware and/or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm.
  • Host 1400 may provide one or more services to one or more UEs.
  • Host 1400 includes processing circuitry 1402 that is operatively coupled via a bus 1404 to an input/output interface 1406, a network interface 1408, a power source 1410, and a memory 1412.
  • Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 12 and 13, such that the descriptions thereof are generally applicable to the corresponding components of host 1400.
  • Memory 1412 may include one or more computer programs including one or more host application programs 1414 and data 1416, which may include user data, e.g., data generated by a UE for host 1400 or data generated by host 1400 for a UE.
  • host 1400 may utilize only a subset or all of the components shown.
  • Host application programs 1414 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems).
  • Host application programs 1414 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network.
  • host 1400 may select and/or indicate a different host for over-the-top services for a UE.
  • Host application programs 1414 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real- Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.
  • HTTP Live Streaming HLS
  • RTMP Real-Time Messaging Protocol
  • RTSP Real- Time Streaming Protocol
  • MPEG-DASH Dynamic Adaptive Streaming over HTTP
  • FIG. 15 is a block diagram illustrating a virtualization environment 1500 in which functions implemented by some embodiments may be virtualized.
  • virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources.
  • 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 1500 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.
  • VMs virtual machines
  • the node may be entirely virtualized.
  • Applications 1502 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 1500 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
  • Hardware 1504 includes processing circuitry, memory that stores software and/or instructions (collectively denoted computer program product 1504a) 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 1506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1508a-b (one or more of which may be generally referred to as VMs 1508), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein.
  • Virtualization layer 1506 may present a virtual operating platform that appears like networking hardware to VMs 1508.
  • VMs 1508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1506.
  • VMs 1502 may be implemented on one or more of VMs 1508, 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.
  • NFV network function virtualization
  • each VM 1508 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine.
  • Each VM 1508, and that part of hardware 1504 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.
  • a virtual network function is responsible for handling specific network functions that run in one or more VMs 1508 on top of the hardware 1504 and corresponds to the application 1502.
  • Hardware 1504 may be implemented in a standalone network node with generic or specific components. Hardware 1504 may implement some functions via virtualization. Alternatively, hardware 1504 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 1510, which, among others, oversees lifecycle management of applications 1502.
  • hardware 1504 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.
  • some signaling can be provided with the use of a control system 1512 which may alternatively be used for communication between hardware nodes and radio units.
  • Figure 16 shows a communication diagram of a host 1602 communicating via a network node 1604 with a UE 1606 over a partially wireless connection in accordance with some embodiments.
  • host 1602 Like host 1400, embodiments of host 1602 include hardware, such as a communication interface, processing circuitry, and memory. Host 1602 also includes software, which is stored in or accessible by host 1602 and executable by the processing circuitry.
  • the software includes a host application that may be operable to provide a service to a remote user, such as UE 1606 connecting via an over-the-top (OTT) connection 1650 extending between UE 1606 and host 1602.
  • OTT over-the-top
  • Network node 1604 includes hardware enabling it to communicate with host 1602 and UE 1606. Connection 1660 may be direct or pass through a core network (like core network 1106 of Figure 11) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks.
  • an intermediate network may be a backbone network or the Internet.
  • UE 1606 includes hardware and software, which is stored in or accessible by UE 1606 and executable by the UE’s processing circuitry.
  • the software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 1606 with the support of host 1602.
  • client application such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 1606 with the support of host 1602.
  • an executing host application may communicate with the executing client application via OTT connection 1650 terminating at UE 1606 and host 1602.
  • the UE's client application may receive request data from the host's host application and provide user data in response to the request data.
  • OTT connection 1650 may transfer both the request data and the user data.
  • the UE's client application may interact with the user to generate the user data that it provides to the host application through OTT connection 1650.
  • OTT connection 1650 may extend via a connection 1660 between host 1602 and network node 1604 and via a wireless connection 1670 between network node 1604 and UE 1606 to provide the connection between host 1602 and UE 1606.
  • Connection 1660 and wireless connection 1670, over which OTT connection 1650 may be provided, have been drawn abstractly to illustrate the communication between host 1602 and UE 1606 via network node 1604, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • host 1602 provides user data, which may be performed by executing a host application.
  • the user data is associated with a particular human user interacting with UE 1606.
  • the user data is associated with a UE 1606 that shares data with host 1602 without explicit human interaction.
  • host 1602 initiates a transmission carrying the user data towards UE 1606.
  • Host 1602 may initiate the transmission responsive to a request transmitted by UE 1606. The request may be caused by human interaction with UE 1606 or by operation of the client application executing on UE 1606.
  • the transmission may pass via network node 1604, in accordance with the teachings of the embodiments described throughout this disclosure.
  • network node 1604 transmits to UE 1606 the user data that was carried in the transmission that host 1602 initiated, in accordance with the teachings of the embodiments described throughout this disclosure.
  • UE 1606 receives the user data carried in the transmission, which may be performed by a client application executed on UE 1606 associated with the host application executed by host 1602.
  • UE 1606 executes a client application which provides user data to host 1602.
  • the user data may be provided in reaction or response to the data received from host 1602.
  • UE 1606 may provide user data, which may be performed by executing the client application.
  • the client application may further consider user input received from the user via an input/output interface of UE 1606.
  • UE 1606 initiates, in step 1618, transmission of the user data towards host 1602 via network node 1604.
  • network node 1604 receives user data from UE 1606 and initiates transmission of the received user data towards host 1602.
  • host 1602 receives the user data carried in the transmission initiated by UE 1606.
  • One or more of the various embodiments improve the performance of OTT services provided to UE 1606 using OTT connection 1650, in which wireless connection 1670 forms the last segment. More precisely, embodiments described herein provide flexible and efficient techniques that improve configurability of SPS/CG in a lightweight manner, to be able to handle traffic (e.g., XR pose/control and scene traffic) that has intrinsic timing misalignment with SPS/CG periodicities and network TDD transmission patterns, thus avoiding undesirable delay or latency accumulation. Embodiments can also avoid resource overprovisioning and increased signaling that are characteristics of conventional solutions. Embodiments can facilitate more efficient and flexible SPS/CG configurations that better adapt to traffic characteristics, requirements, and system/network conditions. This can reduce application transmission latency and improve quality of experience (QoE), including for XR applications. This increases the value of such applications to both end users and OTT service providers.
  • QoE quality of experience
  • factory status information may be collected and analyzed by host 1602.
  • host 1602 may process audio and video data which may have been retrieved from a UE for use in creating maps.
  • host 1602 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights).
  • host 1602 may store surveillance video uploaded by a UE.
  • host 1602 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs.
  • host 1602 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc.
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of host 1602 and/or UE 1606.
  • sensors may be deployed in or in association with other devices through which OTT connection 1650 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities.
  • the reconfiguring of OTT connection 1650 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of network node 1604. Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by host 1602. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection 1650 while monitoring propagation times, errors, etc.
  • the term unit can have conventional meaning in the field of electronics, electrical devices and/or electronic devices and can include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.
  • any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses.
  • Each virtual apparatus may comprise a number of these functional units.
  • These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include Digital Signal Processor (DSPs), special-purpose digital logic, and the like.
  • the processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as Read Only Memory (ROM), Random Access Memory (RAM), cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein.
  • the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.
  • device and/or apparatus can be represented by a semiconductor chip, a chipset, or a (hardware) module comprising such chip or chipset; this, however, does not exclude the possibility that a functionality of a device or apparatus, instead of being hardware implemented, be implemented as a software module such as a computer program or a computer program product comprising executable software code portions for execution or being run on a processor.
  • functionality of a device or apparatus can be implemented by any combination of hardware and software.
  • a device or apparatus can also be regarded as an assembly of multiple devices and/or apparatuses, whether functionally in cooperation with or independently of each other.
  • devices and apparatuses can be implemented in a distributed fashion throughout a system, so long as the functionality of the device or apparatus is preserved. Such and similar principles are considered as known to a skilled person.
  • Embodiments of the techniques and apparatus described herein also include, but are not limited to, the following enumerated examples: Al .
  • each configuration includes the following: a periodicity of the allocated resources during a time period when the configuration is applicable; and a length of the time period when the configuration is applicable.
  • allocation of resources also includes one or more of the following: an indication of a validity duration for the allocation, and an offset that indicates which configuration in the ordered list is initially applicable for transmitting or receiving the periodically arriving application data.
  • A7 The method of any of embodiments A5-A6, wherein one or more of the following is an integer multiple of the arrival period of the application data: the validity duration, and the sum of the lengths of the time periods when the respective configurations are applicable.
  • transmitting or receiving the periodically arriving application data comprises, in response to receiving a deactivation signal from the RAN node during the validity duration, refraining from transmitting or receiving the periodically arriving application data with the RAN node for the remainder of the validity duration.
  • the allocation is received in a radio resource control (RRC) message, which also activates the allocation for transmitting or receiving the periodically arriving application data; or at least a portion of the allocation is received in an RRC message, and the method further comprises receiving, from the RAN node, downlink control information (DCI) that activates the allocation.
  • RRC radio resource control
  • DCI downlink control information
  • the DCI or the RRC message includes an activation bitfield comprising a plurality of bits, with each bit indicating whether a corresponding one of the configurations is activated; and transmitting or receiving the periodically arriving application data comprises, when one or more of the bits indicates that corresponding one or more configurations are not activated, refraining from transmitting or receiving the periodically arriving application data with the RAN node during time periods when the one or more non-activated configurations are applicable.
  • TDD time-division duplexing
  • A13 The method of embodiment A12, wherein the periodically arriving application data includes one of the following: pose or control packets, or buffer status reports (BSRs) related to video frames.
  • BSRs buffer status reports
  • each configuration includes: a first number of successive timeslots with UL resources, representing the periodicity of the allocated resources during the time period when the configuration is applicable; and a second number of successive timeslots with UL resources, representing the length of the time period when the configuration is applicable.
  • A15 The method of any of embodiments A12-A14, wherein the periodically arriving application data has an arrival period that is a non-integer multiple of one or more of the following: the periodicity of timeslots with UL resources, the respective periodicities of the allocated resources during the time periods when the respective configurations are applicable, and the respective lengths of the time periods when the respective configurations are applicable.
  • Al 6 The method of any of embodiments Al -Al 5, further comprising sending one of the following to the RAN node: an indication of whether all of the configurations are accepted and will be used, or a plurality of indications of whether the respective configurations are accepted and will be used.
  • Al 7. The method of embodiment Al 6, wherein transmitting or receiving the periodically arriving application data comprises, when one or more of the plurality of indications indicates that corresponding one or more configurations are not accepted, refraining from transmitting or receiving the periodically arriving application data with the RAN node during time periods when the one or more non-accepted configurations are applicable.
  • A18 The method of any of embodiments A1-A17, wherein the allocation of resources comprises one of the following: a type-1 configured grant (CG) for uplink (UL) transmission by the UE; a type-2 CG for UL transmission by the UE; or a semi-persistent scheduling (SPS) assignment for downlink (DL) reception by the UE.
  • CG type-1 configured grant
  • SPS semi-persistent scheduling
  • a method for a radio access network (RAN) node configured to transmit and receive application data with a user equipment (UE), the method comprising: sending, to the UE, an allocation of resources for transmission or reception of periodically arriving application data, wherein: the allocation is based on a plurality of configurations of periodic resources, and the plurality of configurations are applicable during a respective plurality of nonoverlapping time periods; and transmitting or receiving the periodically arriving application data with the UE using the allocated resources, wherein each arrival of application data is transmitted or received using periodic resources from a configuration that is applicable at the time of the transmission or reception.
  • RAN radio access network
  • UE user equipment
  • each configuration includes the following: a a periodicity of the allocated resources during a time period when the configuration is applicable; and a length of the time period when the configuration is applicable.
  • allocation of resources also includes one or more of the following: an indication of a validity duration for the allocation, and an offset that indicates which configuration in the ordered list is initially applicable for transmitting or receiving the periodically arriving application data.
  • transmitting or receiving the periodically arriving application data comprises, in response to transmitting a deactivation signal to the UE during the validity duration, refraining from transmitting or receiving the periodically arriving application data with the UE for the remainder of the validity duration.
  • the DCI or the RRC message includes an activation bitfield comprising a plurality of bits, with each bit indicating whether a corresponding one of the configurations is activated; and transmitting or receiving the periodically arriving application data comprises, when one or more of the bits indicates that corresponding one or more configurations are not activated, refraining from transmitting or receiving the periodically arriving application data with the UE during time periods when the one or more nonactivated configurations are applicable.
  • TDD time-division duplexing
  • each configuration includes: a first number of successive timeslots with UL resources, representing the periodicity of the allocated resources during the time period when the configuration is applicable; and a second number of successive timeslots with UL resources, representing the length of the time period when the configuration is applicable.
  • Bl 5 The method of any of embodiments B12-B14, wherein the periodically arriving application data has an arrival period that is a non-integer multiple of one or more of the following: the periodicity of timeslots with UL resources, the respective periodicities of the allocated resources during the time periods when the respective configurations are applicable, and the respective lengths of the time periods when the respective configurations are applicable.
  • Bl 6 The method of any of embodiments Bl -Bl 5, further comprising receiving one of the following from the UE: an indication of whether all of the configurations are accepted and will be used, or a plurality of indications of whether the respective configurations are accepted and will be used.
  • transmitting or receiving the periodically arriving application data comprises, when one or more of the plurality of indications indicates that corresponding one or more configurations are not accepted, refraining from transmitting or receiving the periodically arriving application data with the UE during time periods when the one or more non-accepted configurations are applicable.
  • Bl 8 The method of any of embodiments Bl -Bl 7, wherein the allocation of resources comprises one of the following: a type-1 configured grant (CG) for uplink (UL) transmission by the UE; a type-2 CG for UL transmission by the UE; or a semi-persistent scheduling (SPS) assignment for downlink (DL) reception by the UE.
  • CG type-1 configured grant
  • SPS semi-persistent scheduling
  • a user equipment (UE) configured to transmit and receive application data in a radio access network (RAN), the UE comprising: communication interface circuitry configured to communicate with a RAN node; and processing circuitry operatively coupled to the communication interface circuitry, whereby the processing circuitry and the communication interface circuitry are configured to perform operations corresponding to any of the methods of embodiments A1-A18.
  • RAN radio access network
  • a user equipment (UE) configured to transmit and receive application data in a radio access network (RAN), the UE being further configured to perform operations corresponding to any of the methods of embodiments A1-A18.
  • a non-transitory, computer-readable medium storing computer-executable instructions that, when executed by processing circuitry of a user equipment (UE) configured to transmit and receive application data in a radio access network (RAN), configure the UE to perform operations corresponding to any of the methods of embodiments A1-A18.
  • UE user equipment
  • RAN radio access network
  • a computer program product comprising computer-executable instructions that, when executed by processing circuitry of a user equipment (UE) configured to transmit and receive application data in a radio access network (RAN), configure the UE to perform operations corresponding to any of the methods of embodiments A1-A18.
  • UE user equipment
  • RAN radio access network
  • a radio access network (RAN) node configured to transmit and receive application data with a user equipment (UE), the RAN node comprising: communication interface circuitry configured to communicate with the UE; and processing circuitry operatively coupled to the communication interface circuitry, whereby the processing circuitry and the communication interface circuitry are configured to perform operations corresponding to any of the methods of embodiments Bl -Bl 8.
  • RAN radio access network
  • a radio access network (RAN) node configured to transmit and receive application data with a user equipment (UE), the RAN node being further configured to perform operations corresponding to any of the methods of embodiments Bl -Bl 8.
  • a non-transitory, computer-readable medium storing computer-executable instructions that, when executed by processing circuitry of a radio access network (RAN) node configured to transmit and receive application data with a user equipment (UE), configure the network node to perform operations corresponding to any of the methods of embodiments Bl -Bl 8.
  • RAN radio access network
  • UE user equipment
  • a computer program product comprising computer-executable instructions that, when executed by processing circuitry of a radio access network (RAN) node configured to transmit and receive application data with a user equipment (UE), configure the network node to perform operations corresponding to any of the methods of embodiments Bl -Bl 8.
  • RAN radio access network
  • UE user equipment

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Des modes de réalisation comprennent des procédés permettant à un équipement d'utilisateur (UE) configuré de transmettre et recevoir des données d'application dans un réseau d'accès radioélectrique (RAN). De tels procédés consistent à recevoir d'un nœud RAN une attribution de ressources pour la transmission ou la réception de données d'application arrivant périodiquement. L'attribution est basée sur une pluralité de configurations de ressources périodiques, qui sont applicables pendant une pluralité respective de périodes de temps qui ne se chevauchent pas. De tels procédés consistent à transmettre ou à recevoir les données d'application arrivant périodiquement avec le nœud RAN à l'aide des ressources attribuées. Chaque arrivée de données d'application est transmise ou reçue à l'aide de ressources périodiques à partir d'une configuration qui est applicable au moment de la transmission ou de la réception. D'autres modes de réalisation comprennent des procédés complémentaires pour un nœud RAN, ainsi que des UE et des nœuds RAN configurés pour effectuer de tels procédés.
PCT/EP2023/052695 2022-02-03 2023-02-03 Configurabilité améliorée pour planification semi-persistante et autorisations configurées WO2023148335A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202263306217P 2022-02-03 2022-02-03
US63/306,217 2022-02-03

Publications (1)

Publication Number Publication Date
WO2023148335A1 true WO2023148335A1 (fr) 2023-08-10

Family

ID=85175714

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2023/052695 WO2023148335A1 (fr) 2022-02-03 2023-02-03 Configurabilité améliorée pour planification semi-persistante et autorisations configurées

Country Status (1)

Country Link
WO (1) WO2023148335A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020223448A1 (fr) * 2019-04-30 2020-11-05 Idac Holdings, Inc. Procédés et appareil de multiplexage et de priorisation de liaison montante (ul) dans une communication nouvelle radio (nr)
WO2020222486A1 (fr) * 2019-05-02 2020-11-05 Lg Electronics Inc. Procédé et appareil permettant d'arrêter un temporisateur d'autorisation configuré avant expiration dans un système de communication sans fil
EP3783989A1 (fr) * 2018-08-09 2021-02-24 LG Electronics Inc. Procédé de transmission de canal physique partagé de liaison montante d'un terminal dans une bande sans licence et dispositif utilisant ledit procédé
US20210307036A1 (en) * 2018-08-09 2021-09-30 Lg Electronics Inc. Method by which terminal transmits uplink control information in unlicensed band, and device using method
EP3926872A1 (fr) * 2019-04-07 2021-12-22 LG Electronics Inc. Procédé de fonctionnement d'un équipement utilisateur (ue) pour communication de liaison latérale et rétroaction dans un système de communication sans fil

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3783989A1 (fr) * 2018-08-09 2021-02-24 LG Electronics Inc. Procédé de transmission de canal physique partagé de liaison montante d'un terminal dans une bande sans licence et dispositif utilisant ledit procédé
US20210307036A1 (en) * 2018-08-09 2021-09-30 Lg Electronics Inc. Method by which terminal transmits uplink control information in unlicensed band, and device using method
EP3926872A1 (fr) * 2019-04-07 2021-12-22 LG Electronics Inc. Procédé de fonctionnement d'un équipement utilisateur (ue) pour communication de liaison latérale et rétroaction dans un système de communication sans fil
WO2020223448A1 (fr) * 2019-04-30 2020-11-05 Idac Holdings, Inc. Procédés et appareil de multiplexage et de priorisation de liaison montante (ul) dans une communication nouvelle radio (nr)
WO2020222486A1 (fr) * 2019-05-02 2020-11-05 Lg Electronics Inc. Procédé et appareil permettant d'arrêter un temporisateur d'autorisation configuré avant expiration dans un système de communication sans fil

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HUAWEI ET AL: "Transmission with configured grant in NR unlicensed band", vol. RAN WG1, no. Reno, USA; 20190513 - 20190517, 13 May 2019 (2019-05-13), XP051727504, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings%5F3GPP%5FSYNC/RAN1/Docs/R1%2D1906047%2Ezip> [retrieved on 20190513] *

Similar Documents

Publication Publication Date Title
WO2023148335A1 (fr) Configurabilité améliorée pour planification semi-persistante et autorisations configurées
TWI827287B (zh) 基於混合arq考量之控制通道監控
WO2023067478A1 (fr) Canal physique de commande de liaison descendante (pdcch) semi-permanent
WO2023052049A1 (fr) Indication de prise en charge de réseau de diverses fonctionnalités de liaison latérale (sl)
WO2023281302A1 (fr) Ressources de liaison montante pouvant être reconfigurées de manière dynamique
WO2024043817A1 (fr) Association de ports de signal de référence de démodulation (dmrs) pour un équipement utilisateur de transmission multi-panneau simultanée
WO2024104953A1 (fr) Déclenchement de rapport d&#39;état de tampon d&#39;équipement utilisateur pour services xr
WO2023132776A1 (fr) Mesures de couche radio et de couche application alignées dans le temps
WO2023170664A1 (fr) États de tci unifiés pour pdsch à multiples trp
WO2024028840A1 (fr) Rapport d&#39;informations d&#39;assistance d&#39;équipement utilisateur pour faciliter des économies d&#39;énergie de réseau d&#39;accès radio
WO2023224527A1 (fr) Distribution de mesures de qoe visibles par ran
WO2023011806A1 (fr) Gestion d&#39;entité de commande d&#39;accès au support (mac) pendant une désactivation/réactivation de groupe de cellules secondaire (scg)
WO2023249529A1 (fr) Gestion de problèmes de coexistence dans un dispositif
WO2023080818A1 (fr) Détection et récupération de défaillance de faisceau pour un groupe de cellules secondaires (scg) désactivé
WO2023027619A1 (fr) Gestion de mesures de couche d&#39;application configurées pendant un transfert intercellulaire
WO2023055284A1 (fr) Détection contiguë étendue lors d&#39;une réception discontinue de liaison latérale (sl-drx)
WO2023014254A1 (fr) Rapport de libération de réseau initiée par un ue
WO2023113670A1 (fr) Fonctionnement d&#39;un équipement utilisateur (ue) avec une configuration d&#39;économie d&#39;énergie d&#39;une station de base
WO2022229235A1 (fr) Procédés de prédiction et de signalisation d&#39;état et de migration de trafic
WO2023128854A1 (fr) Activation d&#39;un groupe de cellules secondaires (scg) déclenchée par un équipement utilisateur (ue) avec des informations radio
WO2023022645A1 (fr) Gestion de mesures de couche d&#39;application configurées en réponse à un message d&#39;établissement de connexion
WO2023166498A1 (fr) Systèmes et procédés d&#39;association implicite entre une transmission pusch à trp multiples et des états tci unifiés
WO2024005702A1 (fr) Mesures de couche radio et de couche application alignées dans le temps pour connectivité double
WO2024099921A1 (fr) Procédé de transmission d&#39;informations de commande de liaison montante et dispositif de communication
EP4371368A1 (fr) Prévention de désadaptation d&#39;états de contrôle de ressources radio (rrc) entre un réseau et un équipement utilisateur

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23703565

Country of ref document: EP

Kind code of ref document: A1