WO2022155125A1 - Procédure de partage de cot pour communications à bande sans licence - Google Patents

Procédure de partage de cot pour communications à bande sans licence Download PDF

Info

Publication number
WO2022155125A1
WO2022155125A1 PCT/US2022/011955 US2022011955W WO2022155125A1 WO 2022155125 A1 WO2022155125 A1 WO 2022155125A1 US 2022011955 W US2022011955 W US 2022011955W WO 2022155125 A1 WO2022155125 A1 WO 2022155125A1
Authority
WO
WIPO (PCT)
Prior art keywords
cot
transmission
ffp
cot sharing
network
Prior art date
Application number
PCT/US2022/011955
Other languages
English (en)
Inventor
Salvatore TALARICO
Sergey PANTELEEV
Debdeep CHATTERJEE
Toufiqul Islam
Original Assignee
Intel Corporation
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 Intel Corporation filed Critical Intel Corporation
Priority to CN202280008110.5A priority Critical patent/CN116636294A/zh
Publication of WO2022155125A1 publication Critical patent/WO2022155125A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0808—Non-scheduled access, e.g. ALOHA using carrier sensing, e.g. carrier sense multiple access [CSMA]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0446—Resources in time domain, e.g. slots or frames
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/14—Spectrum sharing arrangements between different networks

Definitions

  • TECHNICAL FIELD [0006] Aspects pertain to wireless communications. Some aspects relate to wireless networks including 3GPP (Third Generation Partnership Project) networks, 3GPP LTE (Long Term Evolution) networks, 3GPP LTE-A (LTE Advanced) networks, (MulteFire, LTE-U), and fifth-generation (5G) networks and beyond including 5G new radio (NR) (or 5G-NR) networks, 5G-LTE networks such as 5G NR unlicensed spectrum (NR-U) networks and other unlicensed networks including Wi-Fi, CBRS (OnGo), etc.
  • 3GPP Transmission Generation Partnership Project
  • 3GPP LTE Long Term Evolution
  • 3GPP LTE-A Long Term Evolution Advanced
  • MulteFire LTE-U
  • 5G-LTE networks such as 5G NR unlicensed spectrum (NR-U) networks and other unlicensed networks including Wi-Fi, CBRS (OnGo),
  • UE user equipment
  • COT channel occupancy time
  • URLLC ultra-reliable and low latency communication
  • 5G-NR and beyond networks.
  • 5G Fifth-generation
  • Next generation 5G networks are expected to increase throughput, coverage, and robustness and reduce latency and operational and capital expenditures.
  • 5G-NR networks will continue to evolve based on 3GPP LTE- Advanced with additional potential new radio access technologies (RATs) to enrich people’s lives with seamless wireless connectivity solutions delivering fast, rich content and services.
  • RATs new radio access technologies
  • mmWave millimeter wave
  • LTE operation in the unlicensed spectrum includes (and is not limited to) the LTE operation in the unlicensed spectrum via dual connectivity (DC), or DC-based LAA, and the standalone LTE system in the unlicensed spectrum, according to which LTE-based technology solely operates in the unlicensed spectrum without requiring an “anchor” in the licensed spectrum, called MulteFire.
  • Further enhanced operation of LTE and NR systems in the licensed, as well as unlicensed spectrum, is expected in future releases and 5G (and beyond) systems.
  • Such enhanced operations can include techniques to a UE initiating COT sharing procedure for URLLC operating in an unlicensed band in semi-static channel access mode in 5G-NR (and beyond) networks.
  • FIG.1A illustrates an architecture of a network, in accordance with some aspects.
  • FIG.1B and FIG.1C illustrate a non-roaming 5G system architecture in accordance with some aspects.
  • FIG.2, FIG.3, and FIG.4 illustrate various systems, devices, and components that may implement aspects of disclosed embodiments.
  • FIG.5 illustrates a diagram of a first mode of operation for COT sharing by a UE, in accordance with some aspects.
  • FIG.6 illustrates a diagram of a second mode of operation for COT sharing by a UE, in accordance with some aspects.
  • FIG.7 is a diagram illustrating UL-to-DL COT sharing, when the base station is allowed to schedule inter-FFP UL transmissions of other UEs, in accordance with some aspects.
  • FIG.8 is a diagram illustrating UL-to-DL COT sharing, when the base station is allowed to schedule only intra-FFP UL transmissions of other UEs, in accordance with some aspects.
  • FIG.9 is a diagram illustrating a UL-to-DL COT sharing procedure, in accordance with some aspects.
  • FIG.10 illustrates a block diagram of a communication device such as an evolved Node-B (eNB), a new generation Node-B (gNB) (or another RAN node), an access point (AP), a wireless station (STA), a mobile station (MS), or a user equipment (UE), in accordance with some aspects.
  • eNB evolved Node-B
  • gNB new generation Node-B
  • AP access point
  • STA wireless station
  • MS mobile station
  • UE user equipment
  • FIG.1A illustrates an architecture of a network in accordance with some aspects.
  • the network 140A is shown to include user equipment (UE) 101 and UE 102.
  • the UEs 101 and 102 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks) but may also include any mobile or non-mobile computing device, such as Personal Data Assistants (PDAs), pagers, laptop computers, desktop computers, wireless handsets, drones, or any other computing device including a wired and/or wireless communications interface.
  • PDAs Personal Data Assistants
  • the UEs 101 and 102 can be collectively referred to herein as UE 101, and UE 101 can be used to perform one or more of the techniques disclosed herein.
  • any of the radio links described herein may operate according to any exemplary radio communication technology and/or standard.
  • LTE and LTE-Advanced are standards for wireless communications of high-speed data for UE such as mobile telephones.
  • carrier aggregation is a technology according to which multiple carrier signals operating on different frequencies may be used to carry communications for a single UE, thus increasing the bandwidth available to a single device.
  • carrier aggregation may be used where one or more component carriers operate on unlicensed frequencies.
  • aspects described herein can be used in the context of any spectrum management scheme including, for example, dedicated licensed spectrum, unlicensed spectrum, (licensed) shared spectrum (such as Licensed Shared Access (LSA) in 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz, and further frequencies and Spectrum Access System (SAS) in 3.55-3.7 GHz and further frequencies).
  • LSA Licensed Shared Access
  • SAS Spectrum Access System
  • Aspects described herein can also be applied to different Single Carrier or OFDM flavors (CP-OFDM, SC-FDMA, SC-OFDM, filter bank-based multicarrier (FBMC), OFDMA, etc.) and in particular 3GPP NR (New Radio) by allocating the OFDM carrier data bit vectors to the corresponding symbol resources.
  • any of the UEs 101 and 102 can comprise an Internet-of-Things (IoT) UE or a Cellular IoT (CIoT) UE, which can comprise a network access layer designed for low-power IoT applications utilizing short- lived UE connections.
  • IoT Internet-of-Things
  • CIoT Cellular IoT
  • any of the UEs 101 and 102 can include a narrowband (NB) IoT UE (e.g., such as an enhanced NB-IoT (eNB-IoT) UE and Further Enhanced (FeNB-IoT) UE).
  • NB narrowband
  • eNB-IoT enhanced NB-IoT
  • FeNB-IoT Further Enhanced
  • An IoT UE can utilize technologies such as machine-to-machine (M2M) or machine-type communications (MTC) for exchanging data with an MTC server or device via a public land mobile network (PLMN), Proximity-Based Service (ProSe), or device-to-device (D2D) communication, sensor networks, or IoT networks.
  • M2M or MTC exchange of data may be a machine-initiated exchange of data.
  • An IoT network includes interconnecting IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections.
  • the IoT UEs may execute background applications (e.g., keep- alive messages, status updates, etc.) to facilitate the connections of the IoT network.
  • any of the UEs 101 and 102 can include enhanced MTC (eMTC) UEs or further enhanced MTC (FeMTC) UEs.
  • the UEs 101 and 102 may be configured to connect, e.g., communicatively couple, with a radio access network (RAN) 110.
  • the RAN 110 may be, for example, a Universal Mobile Telecommunications System (UMTS), an Evolved Universal Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN.
  • UMTS Universal Mobile Telecommunications System
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • NG RAN NextGen RAN
  • the UEs 101 and 102 utilize connections 103 and 104, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections 103 and 104 are illustrated as an air interface to enable communicative coupling and can be consistent with cellular communications protocols, such as a Global System for Mobile Communications (GSM) protocol, a code-division multiple access (CDMA) network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3GPP Long Term Evolution (LTE) protocol, a fifth-generation (5G) protocol, a New Radio (NR) protocol, and the like.
  • GSM Global System for Mobile Communications
  • CDMA code-division multiple access
  • PTT Push-to-Talk
  • POC PTT over Cellular
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • 5G fifth-generation
  • NR New Radio
  • the UEs 101 and 102 may further directly exchange communication data via a ProSe interface 105.
  • the ProSe interface 105 may alternatively be referred to as a sidelink interface comprising one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and a Physical Sidelink Broadcast Channel (PSBCH).
  • PSCCH Physical Sidelink Control Channel
  • PSSCH Physical Sidelink Shared Channel
  • PSDCH Physical Sidelink Discovery Channel
  • PSBCH Physical Sidelink Broadcast Channel
  • the UE 102 is shown to be configured to access an access point (AP) 106 via connection 107.
  • AP access point
  • the connection 107 can comprise a local wireless connection, such as, for example, a connection consistent with any IEEE 802.11 protocol, according to which the AP 106 can comprise a wireless fidelity (WiFi®) router.
  • WiFi® wireless fidelity
  • the AP 106 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below).
  • the RAN 110 can include one or more access nodes that enable connections 103 and 104.
  • ANs access nodes
  • BSs base stations
  • eNBs evolved NodeBs
  • gNBs Next Generation NodeBs
  • RAN network nodes and the like, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell).
  • the communication nodes 111 and 112 can be transmission/reception points (TRPs).
  • TRPs transmission/reception points
  • the communication nodes 111 and 112 are NodeBs (e.g., eNBs or gNBs)
  • one or more TRPs can function within the communication cell of the NodeBs.
  • the RAN 110 may include one or more RAN nodes for providing macrocells, e.g., macro RAN node 111, and one or more RAN nodes for providing femtocells or picocells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low power (LP) RAN node 112 or an unlicensed spectrum based secondary RAN node 112.
  • LP low power
  • Any of the RAN nodes 111 and 112 can terminate the air interface protocol and can be the first point of contact for the UEs 101 and 102.
  • any of the RAN nodes 111 and 112 can fulfill various logical functions for the RAN 110 including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling, and mobility management.
  • RNC radio network controller
  • any of the nodes 111 and/or 112 can be a new generation Node-B (gNB), an evolved node-B (eNB), or another type of RAN node.
  • gNB Node-B
  • eNB evolved node-B
  • the RAN 110 is shown to be communicatively coupled to a core network (CN) 120 via an S1 interface 113.
  • CN core network
  • the CN 120 may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN (e.g., as illustrated in reference to FIGS.1B-1C).
  • EPC evolved packet core
  • NPC NextGen Packet Core
  • the S1 interface 113 is split into two parts: the S1-U interface 114, which carries user traffic data between the RAN nodes 111 and 112 and the serving gateway (S-GW) 122, and the S1-mobility management entity (MME) interface 115, which is a signaling interface between the RAN nodes 111 and 112 and MMEs 121.
  • S-GW serving gateway
  • MME S1-mobility management entity
  • the CN 120 comprises the MMEs 121, the S-GW 122, the Packet Data Network (PDN) Gateway (P-GW) 123, and a home subscriber server (HSS) 124.
  • the MMEs 121 may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN).
  • the MMEs 121 may manage mobility aspects in access such as gateway selection and tracking area list management.
  • the HSS 124 may comprise a database for network users, including subscription-related information to support the network entities' handling of communication sessions.
  • the CN 120 may comprise one or several HSSs 124, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc.
  • the HSS 124 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.
  • the S-GW 122 may terminate the S1 interface 113 towards the RAN 110, and route data packets between the RAN 110 and the CN 120.
  • the S-GW 122 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities of the S-GW 122 may include lawful intercept, charging, and some policy enforcement.
  • the P-GW 123 may terminate an SGi interface toward a PDN.
  • the P-GW 123 may route data packets between the EPC network 120 and external networks such as a network including the application server 184 (alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface 125.
  • the P-GW 123 can also communicate data to other external networks 131A, which can include the Internet, IP multimedia subsystem (IPS) network, and other networks.
  • the application server 184 may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS Packet Services (PS) domain, LTE PS data services, etc.).
  • PS UMTS Packet Services
  • LTE PS data services etc.
  • the P-GW 123 is shown to be communicatively coupled to an application server 184 via an IP interface 125.
  • the application server 184 can also be configured to support one or more communication services (e.g., Voice-over- Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs 101 and 102 via the CN 120.
  • the P-GW 123 may further be a node for policy enforcement and charging data collection.
  • Policy and Charging Rules Function (PCRF) 126 is the policy and charging control element of the CN 120.
  • PCRF Policy and Charging Rules Function
  • HPLMN Home Public Land Mobile Network
  • IP-CAN Internet Protocol Connectivity Access Network
  • the communication network 140A can be an IoT network or a 5G network, including a 5G new radio network using communications in the licensed (5G NR) and the unlicensed (5G NR-U) spectrum.
  • NB-IoT narrowband-IoT
  • An NG system architecture can include the RAN 110 and a 5G network core (5GC) 120.
  • the NG-RAN 110 can include a plurality of nodes, such as gNBs and NG-eNBs.
  • the core network 120 e.g., a 5G core network or 5GC
  • the AMF and the UPF can be communicatively coupled to the gNBs and the NG-eNBs via NG interfaces. More specifically, in some aspects, the gNBs and the NG-eNBs can be connected to the AMF by NG-C interfaces, and the UPF by NG-U interfaces.
  • the gNBs and the NG-eNBs can be coupled to each other via Xn interfaces.
  • the NG system architecture can use reference points between various nodes as provided by 3GPP Technical Specification (TS) 23.501 (e.g., V15.4.0, 2018-12).
  • TS Technical Specification
  • each of the gNBs and the NG- eNBs can be implemented as a base station, a mobile edge server, a small cell, a home eNB, a RAN network node, and so forth.
  • a gNB can be a master node (MN) and NG-eNB can be a secondary node (SN) in a 5G architecture.
  • MN master node
  • SN secondary node
  • FIG.1B illustrates a non-roaming 5G system architecture in accordance with some aspects.
  • a 5G system architecture 140B in a reference point representation. More specifically, UE 102 can be in communication with RAN 110 as well as one or more other 5G core (5GC) network entities.
  • 5GC 5G core
  • the 5G system architecture 140B includes a plurality of network functions (NFs), such as access and mobility management function (AMF) 132, location management function (LMF) 133, session management function (SMF) 136, policy control function (PCF) 148, application function (AF) 150, user plane function (UPF) 134, network slice selection function (NSSF) 142, authentication server function (AUSF) 144, and unified data management (UDM)/home subscriber server (HSS) 146.
  • the UPF 134 can provide a connection to a data network (DN) 152, which can include, for example, operator services, Internet access, or third-party services.
  • DN data network
  • the AMF 132 can be used to manage access control and mobility and can also include network slice selection functionality.
  • the SMF 136 can be configured to set up and manage various sessions according to network policy.
  • the UPF 134 can be deployed in one or more configurations according to the desired service type.
  • the PCF 148 can be configured to provide a policy framework using network slicing, mobility management, and roaming (similar to PCRF in a 4G communication system).
  • the UDM can be configured to store subscriber profiles and data (similar to an HSS in a 4G communication system).
  • the LMF 133 may be used in connection with 5G positioning functionalities.
  • LMF 133 receives measurements and assistance information from the next generation radio access network (NG- RAN) 110 and the mobile device (e.g., UE 101) via the AMF 132 over the NLs interface to compute the position of the UE 101.
  • NG-RAN next generation radio access network
  • NRPPa NR positioning protocol A
  • NCPa next generation control plane interface
  • LMF 133 configures the UE using the LTE positioning protocol (LPP) via AMF 132.
  • the NG RAN 110 configures the UE 101 using radio resource control (RRC) protocol over LTE-Uu and NR-Uu interfaces.
  • RRC radio resource control
  • the 5G system architecture 140B configures different reference signals to enable positioning measurements.
  • Example reference signals that may be used for positioning measurements include the positioning reference signal (NR PRS) in the downlink and the sounding reference signal (SRS) for positioning in the uplink.
  • the downlink positioning reference signal (PRS) is a reference signal configured to support downlink- based positioning methods.
  • the 5G system architecture 140B includes an IP multimedia subsystem (IMS) 168B as well as a plurality of IP multimedia core network subsystem entities, such as call session control functions (CSCFs).
  • IMS IP multimedia subsystem
  • CSCFs call session control functions
  • the IMS 168B includes a CSCF, which can act as a proxy CSCF (P-CSCF) 162BE, a serving CSCF (S-CSCF) 164B, an emergency CSCF (E-CSCF) (not illustrated in FIG.1B), or interrogating CSCF (I-CSCF) 166B.
  • the P-CSCF 162B can be configured to be the first contact point for the UE 102 within the IM subsystem (IMS) 168B.
  • the S-CSCF 164B can be configured to handle the session states in the network, and the E-CSCF can be configured to handle certain aspects of emergency sessions such as routing an emergency request to the correct emergency center or PSAP.
  • the I-CSCF 166B can be configured to function as the contact point within an operator's network for all IMS connections destined to a subscriber of that network operator, or a roaming subscriber currently located within that network operator's service area.
  • the I-CSCF 166B can be connected to another IP multimedia network 170E, e.g. an IMS operated by a different network operator.
  • the UDM/HSS 146 can be coupled to an application server 160E, which can include a telephony application server (TAS) or another application server (AS).
  • TAS telephony application server
  • AS application server
  • the AS 160B can be coupled to the IMS 168B via the S-CSCF 164B or the I-CSCF 166B.
  • FIG.1B illustrates the following reference points: N1 (between the UE 102 and the AMF 132), N2 (between the RAN 110 and the AMF 132), N3 (between the RAN 110 and the UPF 134), N4 (between the SMF 136 and the UPF 134), N5 (between the PCF 148 and the AF 150, not shown), N6 (between the UPF 134 and the DN 152), N7 (between the SMF 136 and the PCF 148, not shown), N8 (between the UDM 146 and the AMF 132, not shown), N9 (between two UPFs 134, not shown), N10 (between the UDM 146 and the SMF 136, not shown), N11 (between the AMF 132 and the SMF 136, not shown), N12 (between the AUSF 144 and the AMF 132, not shown), N13 (between the AUSF 144 and the UDM 132 and the UDM
  • FIG.1C illustrates a 5G system architecture 140C and a service- based representation.
  • system architecture 140C can also include a network exposure function (NEF) 154 and a network repository function (NRF) 156.
  • NEF network exposure function
  • NRF network repository function
  • 5G system architectures can be service-based and interaction between network functions can be represented by corresponding point-to-point reference points Ni or as service-based interfaces.
  • service-based representations can be used to represent network functions within the control plane that enable other authorized network functions to access their services.
  • 5G system architecture 140C can include the following service- based interfaces: Namf 158H (a service-based interface exhibited by the AMF 132), Nsmf 158I (a service-based interface exhibited by the SMF 136), Nnef 158B (a service-based interface exhibited by the NEF 154), Npcf 158D (a service-based interface exhibited by the PCF 148), a Nudm 158E (a service- based interface exhibited by the UDM 146), Naf 158F (a service-based interface exhibited by the AF 150), Nnrf 158C (a service-based interface exhibited by the NRF 156), Nnssf 158A (a service-based interface exhibited by the NSSF 142), Nausf 158G (a service-based interface exhibited by the AUSF 144).
  • Namf 158H a service-based interface exhibited by the AMF 132
  • Nsmf 158I a service-based interface exhibited by the
  • FIG.2, FIG.3, and FIG.4 illustrate various systems, devices, and components that may implement aspects of disclosed embodiments in different communication systems, such as 5G-NR (and beyond) networks.
  • UEs, base stations (such as gNBs), and/or other nodes (e.g., satellites or other NTN nodes) discussed in connection with FIGS.1A-4 can be configured to perform the disclosed techniques.
  • FIG.2 illustrates a network 200 in accordance with various embodiments.
  • the network 200 may operate in a manner consistent with 3GPP technical specifications for LTE or 5G/NR systems.
  • the network 200 may include a UE 202, which may include any mobile or non-mobile computing device designed to communicate with a RAN 204 via an over-the-air connection.
  • the UE 202 may be, but is not limited to, a smartphone, tablet computer, wearable computing device, desktop computer, laptop computer, in-vehicle infotainment, in-car entertainment device, instrument cluster, head-up display device, onboard diagnostic device, dashtop mobile equipment, mobile data terminal, electronic engine management system, electronic/engine control unit, electronic/engine control module, embedded system, sensor, microcontroller, control module, engine management system, networked appliance, machine-type communication device, M2M or D2D device, IoT device, etc.
  • the network 200 may include a plurality of UEs coupled directly with one another via a sidelink interface.
  • the UEs may be M2M/D2D devices that communicate using physical sidelink channels such as but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.
  • the UE 202 may additionally communicate with an AP 206 via an over-the-air connection.
  • the AP 206 may manage a WLAN connection, which may serve to offload some/all network traffic from the RAN 204.
  • the connection between the UE 202 and the AP 206 may be consistent with any IEEE 802.11 protocol, wherein the AP 206 could be a wireless fidelity (Wi-Fi®) router.
  • Wi-Fi® wireless fidelity
  • the UE 202, RAN 204, and AP 206 may utilize cellular-WLAN aggregation (for example, LWA/LWIP).
  • Cellular-WLAN aggregation may involve the UE 202 being configured by the RAN 204 to utilize both cellular radio resources and WLAN resources.
  • the RAN 204 may include one or more access nodes, for example, access node (AN) 208.
  • AN 208 may terminate air-interface protocols for the UE 202 by providing access stratum protocols including RRC, Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), MAC, and L1 protocols.
  • RRC Radio Resource Control
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • MAC Medium Access Control
  • the AN 208 may enable data/voice connectivity between the core network (CN) 220 and the UE 202.
  • the AN 208 may be implemented in a discrete device or as one or more software entities running on server computers as part of, for example, a virtual network, which may be referred to as a CRAN or virtual baseband unit pool.
  • the AN 208 be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc.
  • the AN 208 may be a macrocell base station or a low-power base station for providing femtocells, picocells, or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.
  • the RAN 204 may be coupled with one another via an X2 interface (if the RAN 204 is an LTE RAN) or an Xn interface (if the RAN 204 is a 5G RAN).
  • the X2/Xn interfaces which may be separated into control/user plane interfaces in some embodiments, may allow the ANs to communicate information related to handovers, data/context transfers, mobility, load management, interference coordination, etc.
  • the ANs of the RAN 204 may each manage one or more cells, cell groups, component carriers, etc. to provide the UE 202 with an air interface for network access.
  • the UE 202 may be simultaneously connected with a plurality of cells provided by the same or different ANs of the RAN 204.
  • the UE 202 and RAN 204 may use carrier aggregation to allow the UE 202 to connect with a plurality of component carriers, each corresponding to a Pcell or Scell.
  • a first AN may be a master node that provides an MCG and a second AN may be a secondary node that provides an SCG.
  • the first/second ANs may be any combination of eNB, gNB, ng-eNB, etc.
  • the RAN 204 may provide the air interface over a licensed spectrum or an unlicensed spectrum.
  • the nodes may use LAA, eLAA, and/or feLAA mechanisms based on CA technology with PCells/Scells.
  • the nodes Before accessing the unlicensed spectrum, the nodes may perform medium/carrier-sensing operations based on, for example, a listen-before-talk (LBT) protocol.
  • LBT listen-before-talk
  • the UE 202 or AN 208 may be or act as a roadside unit (RSU), which may refer to any transportation infrastructure entity used for V2X communications.
  • RSU roadside unit
  • An RSU may be implemented in or by a suitable AN or a stationary (or relatively stationary) UE.
  • An RSU implemented in or by: a UE may be referred to as a “UE-type RSU”; an eNB may be referred to as an “eNB-type RSU”; a gNB may be referred to as a “gNB-type RSU”; and the like.
  • an RSU is a computing device coupled with radio frequency circuitry located on a roadside that provides connectivity support to passing vehicle UEs.
  • the RSU may also include internal data storage circuitry to store intersection map geometry, traffic statistics, media, as well as applications/software to sense and control ongoing vehicular and pedestrian traffic.
  • the RSU may provide very low latency communications required for high-speed events, such as crash avoidance, traffic warnings, and the like. Additionally, or alternatively, the RSU may provide other cellular/WLAN communications services.
  • the components of the RSU may be packaged in a weatherproof enclosure suitable for outdoor installation and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller or a backhaul network.
  • the RAN 204 may be an LTE RAN 210 with eNBs, for example, eNB 212.
  • the LTE RAN 210 may provide an LTE air interface with the following characteristics: sub-carrier spacing (SCS) of 15 kHz; CP-OFDM waveform for downlink (DL) and SC-FDMA waveform for uplink (UL); turbo codes for data and TBCC for control; etc.
  • the LTE air interface may rely on CSI-RS for CSI acquisition and beam management; PDSCH/PDCCH DMRS for PDSCH/PDCCH demodulation; and CRS for cell search and initial acquisition, channel quality measurements, and channel estimation for coherent demodulation/detection at the UE.
  • the LTE air interface may operate on sub-6 GHz bands.
  • the RAN 204 may be an NG-RAN 214 with gNBs, for example, gNB 216, or ng-eNBs, for example, ng-eNB 218.
  • the gNB 216 may connect with 5G-enabled UEs using a 5G NR interface.
  • the gNB 216 may connect with a 5G core through an NG interface, which may include an N2 interface or an N3 interface.
  • the ng-eNB 218 may also connect with the 5G core through an NG interface but may connect with a UE via an LTE air interface.
  • the gNB 216 and the ng-eNB 218 may connect over an Xn interface.
  • the NG interface may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the nodes of the NG-RAN 214 and a UPF 248 (e.g., N3 interface), and an NG control plane (NG-C) interface, which is a signaling interface between the nodes of the NG-RAN214 and an AMF 244 (e.g., N2 interface).
  • NG-U NG user plane
  • N3 interface e.g., N3 interface
  • N-C NG control plane
  • the NG-RAN 214 may provide a 5G-NR air interface with the following characteristics: variable SCS; CP-OFDM for DL, CP-OFDM, and DFT-s-OFDM for UL; polar, repetition, simplex, and Reed-Muller codes for control and LDPC for data.
  • the 5G-NR air interface may rely on CSI-RS, PDSCH/PDCCH DMRS similar to the LTE air interface.
  • the 5G-NR air interface may not use a CRS but may use PBCH DMRS for PBCH demodulation; PTRS for phase tracking for PDSCH and tracking reference signal for time tracking.
  • the 5G-NR air interface may operate on FR1 bands that include sub-6 GHz bands or FR2 bands that include bands from 24.25 GHz to 52.6 GHz.
  • the 5G-NR air interface may include a synchronization signal and physical broadcast channel (SS/PBCH) block (SSB) that is an area of a downlink resource grid that includes PSS/SSS/PBCH.
  • SS/PBCH physical broadcast channel
  • SSB synchronization signal and physical broadcast channel
  • the 5G-NR air interface may utilize BWPs (bandwidth parts) for various purposes.
  • BWP can be used for dynamic adaptation of the SCS.
  • the UE 202 can be configured with multiple BWPs where each BWP configuration has a different SCS.
  • BWP Bandwidth Modulation
  • Another use case example of BWP is related to power saving.
  • multiple BWPs can be configured for the UE 202 with different amounts of frequency resources (for example, PRBs) to support data transmission under different traffic loading scenarios.
  • a BWP containing a smaller number of PRBs can be used for data transmission with a small traffic load while allowing power saving at the UE 202 and in some cases at the gNB 216.
  • a BWP containing a larger number of PRBs can be used for scenarios with higher traffic loads.
  • the RAN 204 is communicatively coupled to CN 220 that includes network elements to provide various functions to support data and telecommunications services to customers/subscribers (for example, users of UE 202).
  • the components of the CN 220 may be implemented in one physical node or separate physical nodes.
  • NFV may be utilized to virtualize any or all of the functions provided by the network elements of the CN 220 onto physical compute/storage resources in servers, switches, etc.
  • a logical instantiation of the CN 220 may be referred to as a network slice, and a logical instantiation of a portion of the CN 220 may be referred to as a network sub- slice.
  • the CN 220 may be connected to the LTE radio network as part of the Enhanced Packet System (EPS) 222, which may also be referred to as an EPC (or enhanced packet core).
  • the EPC 222 may include MME 224, SGW 226, SGSN 228, HSS 230, PGW 232, and PCRF 234 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the EPC 222 may be briefly introduced as follows.
  • the MME 224 may implement mobility management functions to track the current location of the UE 202 to facilitate paging, bearer activation/deactivation, handovers, gateway selection, authentication, etc.
  • the SGW 226 may terminate an S1 interface toward the RAN and route data packets between the RAN and the EPC 222.
  • the SGW 226 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.
  • the SGSN 228 may track the location of the UE 202 and perform security functions and access control. In addition, the SGSN 228 may perform inter-EPC node signaling for mobility between different RAT networks; PDN and S-GW selection as specified by MME 224; MME selection for handovers; etc.
  • the S3 reference point between the MME 224 and the SGSN 228 may enable user and bearer information exchange for inter-3GPP access network mobility in idle/active states.
  • the HSS 230 may include a database for network users, including subscription-related information to support the network entities’ handling of communication sessions.
  • the HSS 230 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.
  • An S6a reference point between the HSS 230 and the MME 224 may enable the transfer of subscription and authentication data for authenticating/authorizing user access to the LTE CN 220.
  • the PGW 232 may terminate an SGi interface toward a data network (DN) 236 that may include an application/content server 238.
  • DN data network
  • the PGW 232 may route data packets between the LTE CN 220 and the data network 236.
  • the PGW 232 may be coupled with the SGW 226 by an S5 reference point to facilitate user plane tunneling and tunnel management.
  • the PGW 232 may further include a node for policy enforcement and charging data collection (for example, PCEF).
  • the SGi reference point between the PGW 232 and the data network 236 may be an operator external public, a private PDN, or an intra-operator packet data network, for example, for provision of IMS services.
  • the PGW 232 may be coupled with a PCRF 234 via a Gx reference point. [0070]
  • the PCRF 234 is the policy and charging control element of the LTE CN 220.
  • the PCRF 234 may be communicatively coupled to the app/content server 238 to determine appropriate QoS and charging parameters for service flows.
  • the PCRF 234 may provision associated rules into a PCEF (via Gx reference point) with appropriate TFT and QCI.
  • the CN 220 may be a 5GC 240.
  • the 5GC 240 may include an AUSF 242, AMF 244, SMF 246, UPF 248, NSSF 250, NEF 252, NRF 254, PCF 256, UDM 258, and AF 260 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the 5GC 240 may be briefly introduced as follows.
  • the AUSF 242 may store data for authentication of UE 202 and handle authentication-related functionality.
  • the AUSF 242 may facilitate a common authentication framework for various access types.
  • the AUSF 242 may exhibit a Nausf service-based interface.
  • the AMF 244 may allow other functions of the 5GC 240 to communicate with the UE 202 and the RAN 204 and to subscribe to notifications about mobility events with respect to the UE 202.
  • the AMF 244 may be responsible for registration management (for example, for registering UE 202), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization.
  • the AMF 244 may provide transport for SM messages between the UE 202 and the SMF 246, and act as a transparent proxy for routing SM messages. AMF 244 may also provide transport for SMS messages between UE 202 and an SMSF. AMF 244 may interact with the AUSF 242 and the UE 202 to perform various security anchor and context management functions. Furthermore, AMF 244 may be a termination point of a RAN CP interface, which may include or be an N2 reference point between the RAN 204 and the AMF 244; and the AMF 244 may be a termination point of NAS (N1) signaling, and perform NAS ciphering and integrity protection. AMF 244 may also support NAS signaling with the UE 202 over an N3 IWF interface.
  • the SMF 246 may be responsible for SM (for example, session establishment, tunnel management between UPF 248 and AN 208); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF 248 to route traffic to proper destination; termination of interfaces toward policy control functions; controlling part of policy enforcement, charging, and QoS; lawful intercept (for SM events and interface to LI system); termination of SM parts of NAS messages; downlink data notification; initiating AN specific SM information, sent via AMF 244 over N2 to AN 208; and determining SSC mode of a session.
  • SM for example, session establishment, tunnel management between UPF 248 and AN 208
  • UE IP address allocation and management including optional authorization
  • selection and control of UP function configuring traffic steering at UPF 248 to route traffic to proper destination; termination of interfaces toward policy control functions; controlling part of policy enforcement, charging, and QoS; lawful intercept (for SM events and interface to LI system); termination of SM parts of
  • the SM may refer to the management of a PDU session, and a PDU session or “session” may refer to a PDU connectivity service that provides or enables the exchange of PDUs between the UE 202 and the data network 236.
  • the UPF 248 may act as an anchor point for intra-RAT and inter- RAT mobility, an external PDU session point of interconnecting to data network 236, and a branching point to support multi-homed PDU sessions.
  • the UPF 248 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane part of policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform QoS handling for a user plane (e.g., packet filtering, gating, UL/DL rate enforcement), perform uplink traffic verification (e.g., SDF-to-QoS flow mapping), transport level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering.
  • UPF 248 may include an uplink classifier to support routing traffic flows to a data network.
  • the NSSF 250 may select a set of network slice instances serving the UE 202.
  • the NSSF 250 may also determine allowed NSSAI and the mapping to the subscribed S-NSSAIs if needed.
  • the NSSF 250 may also determine the AMF set to be used to serve the UE 202, or a list of candidate AMFs based on a suitable configuration and possibly by querying the NRF 254.
  • the selection of a set of network slice instances for the UE 202 may be triggered by the AMF 244 with which the UE 202 is registered by interacting with the NSSF 250, which may lead to a change of AMF.
  • the NSSF 250 may interact with the AMF 244 via an N22 reference point; and may communicate with another NSSF in a visited network via an N31 reference point (not shown).
  • the NSSF 250 may exhibit an Nnssf service-based interface.
  • the NEF 252 may securely expose services and capabilities provided by 3GPP network functions for the third party, internal exposure/re- exposure, AFs (e.g., AF 260), edge computing or fog computing systems, etc.
  • the NEF 252 may authenticate, authorize, or throttle the AFs.
  • NEF 252 may also translate information exchanged with the AF 260 and information exchanged with internal network functions. For example, the NEF 252 may translate between an AF-Service-Identifier and an internal 5GC information. NEF 252 may also receive information from other NFs based on the exposed capabilities of other NFs.
  • This information may be stored at the NEF 252 as structured data, or a data storage NF using standardized interfaces. The stored information can then be re-exposed by the NEF 252 to other NFs and AFs, or used for other purposes such as analytics. Additionally, the NEF 252 may exhibit a Nnef service-based interface. [0078]
  • the NRF 254 may support service discovery functions, receive NF discovery requests from NF instances, and provide the information of the discovered NF instances to the NF instances. NRF 254 also maintains information on available NF instances and their supported services.
  • the terms “instantiate,” “instantiation,” and the like may refer to the creation of an instance, and an “instance” may refer to a concrete occurrence of an object, which may occur, for example, during the execution of program code.
  • the NRF 254 may exhibit the Nnrf service-based interface.
  • the PCF 256 may provide policy rules to control plane functions to enforce them, and may also support a unified policy framework to govern network behavior.
  • the PCF 256 may also implement a front end to access subscription information relevant for policy decisions in a UDR of the UDM 258. In addition to communicating with functions over reference points as shown, the PCF 256 exhibits an Npcf service-based interface.
  • the UDM 258 may handle subscription-related information to support the network entities’ handling of communication sessions and may store the subscription data of UE 202.
  • subscription data may be communicated via an N8 reference point between the UDM 258 and the AMF 244.
  • the UDM 258 may include two parts, an application front end, and a UDR.
  • the UDR may store subscription data and policy data for the UDM 258 and the PCF 256, and/or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 202) for the NEF 252.
  • the Nudr service-based interface may be exhibited by the UDR to allow the UDM 258, PCF 256, and NEF 252 to access a particular set of the stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to the notification of relevant data changes in the UDR.
  • the UDM may include a UDM-FE, which is in charge of processing credentials, location management, subscription management, and so on. Several different front ends may serve the same user in different transactions.
  • the UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification handling, access authorization, registration/mobility management, and subscription management.
  • the UDM 258 may exhibit the Nudm service-based interface.
  • the AF 260 may provide application influence on traffic routing, provide access to NEF, and interact with the policy framework for policy control.
  • the 5GC 240 may enable edge computing by selecting operator/3rd party services to be geographically close to a point that the UE 202 is attached to the network. This may reduce latency and load on the network.
  • the 5GC 240 may select a UPF 248 close to the UE 202 and execute traffic steering from the UPF 248 to data network 236 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 260. In this way, the AF 260 may influence UPF (re)selection and traffic routing.
  • FIG.3 schematically illustrates a wireless network 300 in accordance with various embodiments.
  • the wireless network 300 may include a UE 302 in wireless communication with AN 304.
  • the UE 302 and AN 304 may be similar to, and substantially interchangeable with, like-named components described elsewhere herein.
  • the UE 302 may be communicatively coupled with the AN 304 via connection 306.
  • the connection 306 is illustrated as an air interface to enable communicative coupling and can be consistent with cellular communications protocols such as an LTE protocol or a 5G NR protocol operating at mmWave or sub-6 GHz frequencies.
  • the UE 302 may include a host platform 308 coupled with a modem platform 310.
  • the host platform 308 may include application processing circuitry 312, which may be coupled with protocol processing circuitry 314 of the modem platform 310.
  • the application processing circuitry 312 may run various applications for the UE 302 that source/sink application data.
  • the application processing circuitry 312 may further implement one or more layer operations to transmit/receive application data to/from a data network. These layer operations may include transport (for example UDP) and Internet (for example, IP) operations [0087]
  • the protocol processing circuitry 314 may implement one or more layer operations to facilitate transmission or reception of data over the connection 306.
  • the layer operations implemented by the protocol processing circuitry 314 may include, for example, MAC, RLC, PDCP, RRC, and NAS operations.
  • the modem platform 310 may further include digital baseband circuitry 316 that may implement one or more layer operations that are “below” layer operations performed by the protocol processing circuitry 314 in a network protocol stack.
  • These operations may include, for example, PHY operations including one or more of HARQ-ACK functions, scrambling/descrambling, encoding/decoding, layer mapping/de-mapping, modulation symbol mapping, received symbol/bit metric determination, multi-antenna port precoding/decoding, which may include one or more of space-time, space- frequency or spatial coding, reference signal generation/detection, preamble sequence generation and/or decoding, synchronization sequence generation/detection, control channel signal blind decoding, and other related functions.
  • PHY operations including one or more of HARQ-ACK functions, scrambling/descrambling, encoding/decoding, layer mapping/de-mapping, modulation symbol mapping, received symbol/bit metric determination, multi-antenna port precoding/decoding, which may include one or more of space-time, space- frequency or spatial coding, reference signal generation/detection, preamble sequence generation and/or decoding, synchronization sequence generation/detection,
  • the modem platform 310 may further include transmit circuitry 318, receive circuitry 320, RF circuitry 322, and RF front end (RFFE) 324, which may include or connect to one or more antenna panels 326.
  • the transmit circuitry 318 may include a digital-to-analog converter, mixer, intermediate frequency (IF) components, etc.
  • the receive circuitry 320 may include an analog-to-digital converter, mixer, IF components, etc.
  • the RF circuitry 322 may include a low-noise amplifier, a power amplifier, power tracking components, etc.
  • RFFE 324 may include filters (for example, surface/bulk acoustic wave filters), switches, antenna tuners, beamforming components (for example, phase-array antenna components), etc.
  • transmit/receive components may be specific to details of a specific implementation such as, for example, whether the communication is TDM or FDM, in mmWave or sub-6 GHz frequencies, etc.
  • the transmit/receive components may be arranged in multiple parallel transmit/receive chains, may be disposed of in the same or different chips/modules, etc.
  • the protocol processing circuitry 314 may include one or more instances of control circuitry (not shown) to provide control functions for the transmit/receive components.
  • a UE reception may be established by and via the antenna panels 326, RFFE 324, RF circuitry 322, receive circuitry 320, digital baseband circuitry 316, and protocol processing circuitry 314.
  • the antenna panels 326 may receive a transmission from the AN 304 by receive- beamforming signals received by a plurality of antennas/antenna elements of the one or more antenna panels 326.
  • a UE transmission may be established by and via the protocol processing circuitry 314, digital baseband circuitry 316, transmit circuitry 318, RF circuitry 322, RFFE 324, and antenna panels 326.
  • the transmit components of the UE 302 may apply a spatial filter to the data to be transmitted to form a transmit beam emitted by the antenna elements of the antenna panels 326.
  • the AN 304 may include a host platform 328 coupled with a modem platform 330.
  • the host platform 328 may include application processing circuitry 332 coupled with protocol processing circuitry 334 of the modem platform 330.
  • the modem platform may further include digital baseband circuitry 336, transmit circuitry 338, receive circuitry 340, RF circuitry 342, RFFE circuitry 344, and antenna panels 346.
  • the components of the AN 304 may be similar to and substantially interchangeable with like-named components of the UE 302.
  • FIG.4 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.
  • a machine-readable or computer-readable medium e.g., a non-transitory machine-readable storage medium
  • FIG.4 shows a diagrammatic representation of hardware resources 400 including one or more processors (or processor cores) 410, one or more memory/storage devices 420, and one or more communication resources 430, each of which may be communicatively coupled via a bus 440 or other interface circuitry.
  • processors or processor cores
  • memory/storage devices 420 may be communicatively coupled via a bus 440 or other interface circuitry.
  • a hypervisor 402 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 400.
  • the processors 410 may include, for example, a processor 412 and a processor 414.
  • the processors 410 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radio- frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.
  • the memory/storage devices 420 may include a main memory, disk storage, or any suitable combination thereof.
  • the memory/storage devices 420 may include but are not limited to, any type of volatile, non-volatile, or semi-volatile memory such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, solid-state storage, etc.
  • the communication resources 430 may include interconnection or network interface controllers, components, or other suitable devices to communicate with one or more peripheral devices 404 or one or more databases 406 or other network elements via a network 408.
  • the communication resources 430 may include wired communication components (e.g., for coupling via USB, Ethernet, etc.), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, Wi- Fi® components, and other communication components.
  • Instructions 450 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 410 to perform any one or more of the methodologies discussed herein.
  • the instructions 450 may reside, completely or partially, within at least one of the processors 410 (e.g., within the processor’s cache memory), the memory/storage devices 420, or any suitable combination thereof.
  • any portion of the instructions 450 may be transferred to the hardware resources 400 from any combination of the peripheral devices 404 or the databases 406.
  • the memory of processors 410, the memory/storage devices 420, the peripheral devices 404, and the databases 406 are examples of computer-readable and machine-readable media.
  • at least one of the components outlined in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as outlined in the example sections below.
  • baseband circuitry associated with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below.
  • the term “application” may refer to a complete and deployable package, environment to achieve a certain function in an operational environment.
  • AI/ML application or the like may be an application that contains some artificial intelligence (AI)/machine learning (ML) models and application-level descriptions. In some embodiments, an AI/ML application may be used for configuring or implementing one or more of the disclosed aspects.
  • machine learning or “ML” refers to the use of computer systems implementing algorithms and/or statistical models to perform a specific task(s) without using explicit instructions but instead relying on patterns and inferences.
  • ML algorithms build or estimate mathematical model(s) (referred to as “ML models” or the like) based on sample data (referred to as “training data,” “model training information,” or the like) to make predictions or decisions without being explicitly programmed to perform such tasks.
  • ML algorithm is a computer program that learns from experience with respect to some task and some performance measure, and an ML model may be any object or data structure created after an ML algorithm is trained with one or more training datasets. After training, an ML model may be used to make predictions on new datasets.
  • ML algorithm refers to different concepts than the term “ML model,” these terms as discussed herein may be used interchangeably for the present disclosure.
  • ML model may also refer to ML methods and concepts used by an ML-assisted solution.
  • An “ML-assisted solution” is a solution that addresses a specific use case using ML algorithms during operation.
  • ML models include supervised learning (e.g., linear regression, k-nearest neighbor (KNN), decision tree algorithms, support machine vectors, Bayesian algorithm, ensemble algorithms, etc.) unsupervised learning (e.g., K-means clustering, principal component analysis (PCA), etc.), reinforcement learning (e.g., Q-learning, multi-armed bandit learning, deep RL, etc.), neural networks, and the like.
  • supervised learning e.g., linear regression, k-nearest neighbor (KNN), decision tree algorithms, support machine vectors, Bayesian algorithm, ensemble algorithms, etc.
  • unsupervised learning e.g., K-means clustering, principal component analysis (PCA), etc.
  • reinforcement learning e.g., Q-learning, multi-armed bandit learning, deep
  • An “ML pipeline” is a set of functionalities, functions, or functional entities specific for an ML-assisted solution; an ML pipeline may include one or several data sources in a data pipeline, a model training pipeline, a model evaluation pipeline, and an actor.
  • the “actor” is an entity that hosts an ML-assisted solution using the output of the ML model inference).
  • ML training host refers to an entity, such as a network function, that hosts the training of the model.
  • ML inference host refers to an entity, such as a network function, that hosts the model during inference mode (which includes both the model execution as well as any online learning if applicable).
  • the ML-host informs the actor about the output of the ML algorithm, and the actor decides for an action (an “action” is performed by an actor as a result of the output of an ML-assisted solution).
  • model inference information refers to information used as an input to the ML model for determining inference(s); the data used to train an ML model and the data used to determine inferences may overlap, however, “training data” and “inference data” refer to different concepts. [00103]
  • the achievable latency and reliability performance of NR are keys to support use cases with tighter requirements.
  • Rel-16 NR evolved to support use cases including the following: Release 15 enabled use case improvements (e.g., AR/VR and entertainment industry applications) and new Release 16 use cases with higher requirements (e.g., factory automation, transport industry, and electrical power distribution).
  • Release 15 enabled use case improvements e.g., AR/VR and entertainment industry applications
  • new Release 16 use cases with higher requirements e.g., factory automation, transport industry, and electrical power distribution.
  • a limiting factor is the availability of the spectrum.
  • one of the objectives of Rel. 17 is to identify potential enhancements to ensure Release 16 feature compatibility with unlicensed band ultra-reliable and low latency communications (URLLC) and Industrial Internet-of-Things (IIoT) operation in controlled environments.
  • URLLC unlicensed band ultra-reliable and low latency communications
  • IIoT Industrial Internet-of-Things
  • aspects of the design that can be enhanced when operating in an unlicensed spectrum may be identified.
  • both load-based equipment (LBE) and frame- based equipment (FBE) design can be adopted to accommodate different scenarios and the use of the LBT procedure.
  • LBE load-based equipment
  • FBE frame- based equipment
  • the FBE framework to exemplify the NR-U design, only the gNB can be acting as an initiating device, and the starting positions of the fixed frame periods align with every even frame given that the fixed frame period (FFP) can be one of ⁇ 1ms, 2ms, 2.5ms, 4ms, 5ms, 10ms ⁇ .
  • this mode of operation may lead to long delays when an LBT failure occurs at the gNB at the beginning of an FFP, since in this case all the DL and UL transmissions scheduled within that FFP may need to be postponed to the following FFP for which a gNB can succeed its LBT procedure.
  • this mode of operation may be modified and the single point of failure at the gNB may be removed providing a device with more opportunities to be able to transmit and allow the device to be able to operate as an initiating device and acquire their own channel occupancy time (COT).
  • COT channel occupancy time
  • the UL-to-DL COT sharing procedure can be established if the UE is also operated as an initiating device, and while the UL- to-DL procedure used for LBE can be used as a baseline, the disclosed techniques provide some enhancements to accommodate for the frame-based framework.
  • the UL-to-DL COT sharing procedure defined in Rel.16 provides a level of transparency to the UE itself, given that explicit information is provided by the gNB to the UE regarding the COT sharing procedure, except indicating to the UE the type of channel access type to use, given that the gNB has full control of the scheduled resources.
  • DG dynamic grant
  • FBE framework semi-static channel access mode
  • the disclosed techniques provide details regarding the UL-to-DL COT sharing procedure for a configured grant (CG) UEs and their related signaling.
  • the disclosed techniques also identify enhancements in the information that can be carried in the CG uplink control information (CG-UCI).
  • a UE can operate as an initiating device only when the UE is operated in the LBE framework. Only in this case, a CG UE is allowed to share its COT with its associated gNB. However, based on whether the higher layer parameter ul-toDL-COT-SharingED-Threshold-r16 is provided or not to the UE, then the COT sharing mechanism differs and two different modes of operation (e.g., Mode A and Mode B) can be defined (e.g., as illustrated in FIG.5 and FIG.6). [00111] (A) Mode A.
  • FIG.5 illustrates diagram 500 of a first mode (mode A) of operation for COT sharing by a UE, in accordance with some aspects.
  • mode A a first mode of operation for COT sharing by a UE, in accordance with some aspects.
  • the UE is allowed to share its COT with the gNB.
  • the DL transmission can contain a transmission to the UE that initiated the channel occupancy and can also include non-unicast and /or unicast transmissions, where any unicast transmission includes user plane data is only transmitted to the UE that initiated the channel occupancy.
  • the UE is configured by cg-COT-SharingList-r16 where cg-COT- SharingList-r16 provides a table configured by higher layer signaling, where each row of the table provides jointly the following information: (a) channel access priority class used by the UE when acquiring the COT; (b) slot from where the DL transmission could start, which is identified as x+O, where x is the current slot and O is an offset indicated in terms of slots; and (c) maximum duration of the DL transmission, which is indicated by D, and provided in terms of slots.
  • FIG.5 An illustration of this modality of operation is provided in FIG.5.
  • the cg-COT-SharingList-r16 information element (e.g., as listed in Table 1 below) also includes an entry indicating that no COT sharing would be allowed.
  • TABLE 1 [00115] (B) Mode B.
  • FIG.6 illustrates diagram 600 of a second mode (mode B) of operation for COT sharing by a UE, in accordance with some aspects.
  • 'COT sharing information' i.e., a COT sharing indication
  • the UE is allowed to share its COT only for DL control transmission for the length of 2/4/or 8 OFDM symbol for 15/30 or 60 kHz subcarrier spacing, respectively.
  • the gNB can share the UE channel occupancy and start the DL transmission X symbols from the end of the slot where CG-UCI is detected, where cg-COT-SharingOffset-r16 is provided by higher layer signaling. An illustration of this modality of operation is provided in FIG.6.
  • the following configurations may be used: [00118]
  • (a) The higher layer parameter ul-toDL-COT-SharingED- Threshold-r16 can be introduced for matters of co-existence with other incumbent technologies so that to reduce potential interference and blocking.
  • URLLC/IIoT is operated in the unlicensed band only within controlled environments, where the absence of an incumbent technology is guaranteed in long term.
  • the UE indicates the gNB regarding an offset value which indicates from where the gNB can start the transmission.
  • this offset indication points to the first symbol of the first slot starting from which a gNB is allowed to transmit. This has the drawback that if the UE terminates its UL burst not exactly at the slot level, a gap larger than 16 us will be left between the UL and the DL, meaning that the gNB would need to perform a Cat-2 listen-before-talk (LBT) before transmitting within the UE’s COT.
  • LBT listen-before-talk
  • a gNB is never allowed to configure the higher layer parameter ul-toDL-COT-SharingED-Threshold-r16, and a UE has not expected this RRC parameter.
  • the UE regardless of whether it will share its COT or not, when it operates as an initiating device and acquires a new FFP when performing the CCA procedure it will determine whether a channel is idle or busy using an energy detection (ED) threshold that is calculated only based on its own transmit power and as detailed in TS 37.213 Sec.4.2.3.
  • ED energy detection
  • the UE sharing its COT with a gNB when performing the CCA procedure, will determine whether a channel is idle or busy using an energy detection (ED) threshold that is calculated based on one or more of the following conditions: [00127] (c.1) based on its own transmit power and as detailed in TS 37.213 Sec.4.2.3 if one or more of the following is met: [00128] (c.1.1) when within the shared COT the gNB transmits unicast user plane data or control to the initiating UE; [00129] (c.1.2) when within the shared COT the UL-to-DL is always larger than 16 us and irrespective to what and to whom the gNB will be transmitted to as long as if the transmission is devoted to a UE other than that initiating the FFP, and that UE operates as a DG UEs within the u-FFP that the gNB is sharing and/or within the g-FFP that may overlap with the u-FFP that the gNB
  • ED energy detection
  • both control and data transmissions can be performed by the gNB as long as this contains transmissions per switching point which is dedicated for the UE that initiated that FFP.
  • both control and data transmissions are allowed to be performed by the gNB independently of whether any of the transmissions are meant for the UE that initiated that FFP or not.
  • both control and data transmissions are allowed to be performed by the gNB, but they must be intended for the UE that initiated that FFP.
  • the gNB is allowed to share the UE’s FFP and transmit as long one or more of the following configurations are satisfied: [00135] (a) the gNB’s transmissions (either data or control or both) are only devoted to the UE that initiated the FFP that the gNB is sharing; [00136] (b) the gNB’s transmissions can be addressed to other UEs other than that initiating the FFP as long as one or more of the following conditions are met: [00137] (b.1) per switching point there is at least one transmission which is devoted to the UE that initiated the FFP; [00138] (b.2) Only transmissions containing UE-specific control information and/or UE-specific control and data information are allowed to be addressed to UEs other than that initiating the FPP.
  • the gNB can only perform unicast transmissions to UEs for which the UE’s FFP parameters are provided (Rel.17 UEs) and those will be operating solely as DG UEs within the FFP initiated by the UE, which is shared by the gNB, or within the g-FFP which overlaps with the initiating UE’s FFP, which is shared by the gNB.
  • the bitfield included within the scheduling DCI which contains information related to the channel access information i.e., CP extension, channel access type, and COT initiator
  • the bitfield included within the scheduling DCI which contains information related to the channel access information (i.e., CP extension, channel access type, and COT initiator) would need to be always present within that unicast DL burst, and the content of the channel access information would need to explicitly indicate that the gNB is operating as a responding device (index 3 within the Table 2 is used).
  • the bitfield included within the scheduling DCI which contains information related to the channel access information would need to be always present within that unicast DL burst, and the content of the channel access information would need to explicitly indicate that the gNB is operating as a responding device (index 3 within the Table 2 is used).
  • a switching point e.g., UL to DL and/or DL to UL
  • the device transmitting soon after the switching point may follow one of the following two options: [00146] (a) it does not sense the channel before transmitting and it follows the type
  • a switching point e.g., UL to DL or DL to UL or UL to UL
  • the new scheduled UL transmission scheduled by the gNB when this operates as a responding device, can occur at any time, and even in time domain resources overlapping with the current UE’s FFP with which the gNB shares the FFP.
  • FIG.7 is a diagram 700 illustrating UL-to-DL COT sharing, when the base station is allowed to schedule inter-FFP UL transmissions of other UEs, in accordance with some aspects.
  • the scheduled UL transmissions of other UEs are not allowed within a different UE’s FFP, and UL transmissions for other UE (UEs) can only be scheduled in time domain resources that do not overlap with the current acquired UE’s FFP.
  • FIG. 8 illustrates the case when the gNB is allowed to schedule UL transmissions of another UE (or UEs), only outside of the acquired UE’s FFP.
  • FIG.8 is a diagram 800 illustrating UL-to-DL COT sharing, when the base station is allowed to schedule only intra-FFP UL transmissions of other UEs, in accordance with some aspects.
  • the concept/definition of offset that has been introduced in Rel.16 is modified, so that the offset points always from the first symbol after the end of the UL burst to the first symbol that the gNB can utilize for DL transmission independently on whether this symbol is at the slot boundary or not.
  • the offset may be defined in granularity of symbols/slots/or PUSCH length corresponding to the latest value indicated by the start and length indicator value (SLIV) for the specific UL burst or UL transmission carrying that information.
  • the offset is defined as the elapse of time from the first symbol of the first slot after the end of the UL burst to the first symbol of a slot that the gNB can utilize for DL transmission.
  • the modified behavior can be activated if a separate RRC parameter in a form of a binary flag is present in SIB1 or a dedicated configuration, which enables the modified behavior.
  • the CG-UCI carries COT sharing information that is used by the UE to inform a gNB regarding the unused resources that it can use within a u-FFP.
  • the UE carries ⁇ log2C ⁇ bits as part of the COT sharing information field in the cg-UCI, where C is the number of combinations configured by the RRC parameter cg-COT-SharingList-r16, where cg-COT-SharingList-r16 provides a table where each row indicates jointly the following information: [00156] (a) Channel access priority class used by the UE when acquiring the COT; [00157] (b) Slot from where the DL transmission could start, which is identified as x+O, where x is the current slot and O is an offset indicated in terms of slots; and [00158] (c) Maximum duration of the DL transmission, which is indicated by D, and provided again in terms of slots.
  • CAPC channel access priority class
  • a new optional higher layer parameter is introduced specifically for the case when a semi-static channel access mode is used and the cg-RetransmissionTimer is configured, which provides a table configured by a higher layer, where each row of the table provides joint information on the offset and duration of a specific DL transmission allowed within the acquired UE’s FFP that is shared with a gNB.
  • the UE is allowed to select and indicate a specific row of the table when the CG-UCI is carried in a PUSCH to indicate the gNB on whether UE’s initiated COT sharing is allowed or not, and the specific resources that the gNB can use.
  • the CG-UCI may carry a COT sharing information composed by ⁇ log2 C ⁇ bits, where C is the number of combinations configured.
  • C is the number of combinations configured.
  • a UL or DL transmission that takes place within a UE’s FFP cannot prolong more than the length of that FFP and cannot overlap or extend within the UE’s idle period of the following UE’s FFP.
  • a gNB is not allowed to transmit within the UE’s idle period of the following UE’s FFP, and those resources should be considered invalid.
  • a UE initiates an FFP and shares it with a gNB
  • T_x is the length of a UE’s FFP.
  • the gNB is required to have additional information, and in particular to know all the time domain resources that the UE intends to share with the gNB or that they will remain unused.
  • a UE could indicate the shared resources to the gNB but this could be only provided per each switching point separately.
  • the gNB cannot be informed in advance of the number of switching points allowed, and for each of them the resources that it can potentially use, meaning that the gNB would not be allowed to schedule any UL transmissions to any other UEs within a specific UE’s FFP in another switching point, given that it is unaware of whether other resources would be allowed in separate instances of the UE’s FFP. For this purpose, some further configurations can be performed.
  • a new optional high layer parameter (e.g., as listed in Table 4 below) is introduced for the case when a semi-static channel access mode is used, and the cg-RetransmissionTimer is configured, which provides a table configured by higher layer signaling, where each row of the table provides joint information of the offset and duration of a specific DL transmission allowed within the acquired UE’s FFP that is shared with a gNB, and the number of switching points.
  • the UE is allowed to select and indicate a specific row of the table when the CG-UCI is carried in a PUSCH to indicate the gNB on whether UE’s initiated CT sharing is allowed or not and the specific resources that the gNB can use.
  • the CG-UCI may carry a COT sharing information composed by ⁇ log2 C ⁇ bits, where C is the number of combinations configured.
  • C is the number of combinations configured.
  • the duration and offsets are vectors, where each element indicating the durations and offsets are relative to each switching point. If the optional table is not provided, then Rel.16 behavior is applied.
  • Y Z
  • Y and Z are different.
  • an optional higher layer parameter is introduced specifically for the case when a semi-static channel access mode is used, and the cg-RetransmissionTimer is configured, which provides a table configured by a higher layer, where each row of the table provides joint information of the offset and duration of a specific DL transmission allowed within the acquired UE’s FFP that is shared with a gNB.
  • the UE is allowed to select and indicate a specific row of the table when the CG-UCI is carried in a PUSCH to indicate the gNB on whether UE’s initiated COT sharing is allowed or not, and the specific resources that the gNB can use. Therefore, the CG-UCI may carry a COT sharing information composed by bits, where C is the number of combinations configured.
  • the number of switching points allowed within the UE’s FFP is either separately RRC configured, or dynamically signaled directly within the CG-UCI, which would include a dedicated field. If the optional table is not provided, then Rel.16 behavior is applied.
  • the values of the offset and duration are scalar, and this would apply only to the first switching point, and the value of offset and duration for each of the subsequent switching points would be provided before each of them.
  • the values of the offset and duration are scalar, and these values would be the same and apply to all switching points, meaning that each portion of the UE’s FFP that remains unused would have the same length, and the first slot of each portion that can be shared would be equally spaced by the same amount of resources provided by the offset.
  • the values of the offset and duration are vectors, where each element indicating the durations and offsets are relative to each switching point.
  • the values of the offset and duration are scalar, and an indication of the number switching points, M, is provided via RRC.
  • the UE would carry bits for COT sharing, where each bits would jointly indicate the offset and duration of a specific portion of the UE’s FFP, which can be shared with the gNB and utilized by other UEs scheduled by that gNB.
  • the cg-RetransmissionTimer when the cg-RetransmissionTimer is not configured, and the cg-UCI is not piggybacked within a PUSCH transmission, one of the following procedures could be used: [00185] (a) In some embodiments, it is up to the gNB to schedule the CG resources, and for any resources which are not scheduled for a CG transmission within a UE’s FFP, it is up to gNB to transmit in those resources as a responding device utilizing the UE’s COT.
  • (b) it is left up to UE on whether to share its COT and to indicate the start of the time domain resources which can be used by the gNB within the UE’s FFP as if the gNB operates as a responding device.
  • the UE may only provide information to the gNB on the first slot/symbol/ or CG PUSCH transmission which can be used for DL transmissions, but it is up to gNB to use any of these resources as well as any subsequent time domain resources up to the following CG allocated resources within a specific UE’s FFP, and as long as these time-domain resources lie within the UE’s FFP.
  • a high-level illustration of this concept is provided in FIG.9.
  • FIG.9 is a diagram 900 illustrating a UL-to-DL COT sharing procedure, in accordance with some aspects.
  • the indication of which time-domain resources within a UE’s FFP can be used by the gNB may be provided through a combination of a sharing indication, which informs the gNB of the intention of the UE to share its COT, and an offset ‘X’, which indicates how many symbols/slots/ or CG PUSCH transmissions starting from when the UE has indicated its intention to share its COT the gNB could start performing a DL transmission.
  • the offset ‘X’ could be a fixed value indicated within the specification, which may depend on the subcarrier spacing, or could be RRC configured or equivalent to the minimum gNB’s processing time to decode a CG PUSCH transmission.
  • the sharing indication can be performed implicitly or explicitly using one or multiple of the following options: [00190] (a) The indication of the intention of a UE to share its COT can be implicitly indicated by Cyclic Redundancy Error (CRC) of a TB or a CB/CBG, which is scrambled by a codeword representing the sharing indication.
  • CRC Cyclic Redundancy Error
  • the indication of the intention of a UE to share its COT may be done using a special payload in the encoded CB.
  • the encoded CB payload contains a predefined bit sequence signature, which the gNB would interpret as a sharing indication.
  • the gNB would know that the UE intends to share its COT, and the gNB could utilize for DL transmission the following time-domain resources after ‘X’ amount of time from the end of the PUSCH carrying the current CB.
  • the location of the special payload may be predefined in the specification, e.g., at the beginning of the CB or CBG, or included in the MAC-CE.
  • a logical channel ID (LCID) can be used to distinguish this information from a regular MAC-CE.
  • one of the reserved LCID values is used to distinguish the UCI carrying sharing indication from a regular MAC-CE.
  • N single-symbol or double-symbol DMRS are associated with a PUSCH transmission
  • the PUSCH after nth single-symbol or double- symbol DMRS is interpreted as the PUSCH carrying sharing indication, where ⁇ Q ⁇ 1-1.
  • the gNB identifies no DMRS
  • the gNB would know that the UE intends to share its COT, and the gNB could utilize the following time-domain resources after ‘X’ amount of time from the end of the current PUSCH for DL transmission.
  • the indication of the intention of a UE to share its COT can be indicated by a specific DMRS that is associated with the PUSCH transmission.
  • a specific DMRS that is associated with the PUSCH transmission.
  • two sets of DMRS resources are formed: the first set can be associated with PUSCH transmission, while the second set can be used for sharing indications.
  • the gNB detects the DMRS in the second set of DMRS resources, the gNB would know that the UE intends to share its COT, and the gNB could utilize the following time-domain resources after ‘X’ amount of time from the end of the current PUSCH for DL transmission.
  • the first and second of DMRS resources may be configured by dedicated RRC signaling or DCI or a combination thereof.
  • a frequency shift or time- domain cyclic shift of Y may be configured by RRC signaling, which may be applied by the UE for DMRS which carries the indication of a UE to share its COT.
  • RRC signaling which may be applied by the UE for DMRS which carries the indication of a UE to share its COT.
  • Enhancements to the Content of the CG-UCI may be different than that used in NR-U, and in addition to the fields carried in Rel.16 (i.e., HARQ process number, RV, and NDI), one or more of the following information could be also carried: [00199] (a) ⁇ log 2 C ⁇ bits used for COT sharing information could be carried, which are used as described in the prior embodiment of this disclosure; [00200] (b) One-bit field indicating whether the UE is transmitting within the UE’s F
  • the CG-UCI content may be different than that used in NR-U, and one or more of the following information could be carried: [00204] (a) bits used for COT sharing information could be carried, which are used as described in the prior embodiment of this disclosure; [00205] (b) One-bit field indicating whether the UE is transmitting within the UE’s FFP or gNB’s FFP, which can be used by the gNB to solve the ambiguity in case a UE is allowed to transmit within a valid gNB’s FFP, where a valid FFP is an FFP for which the initiating device has been able to succeed its CCA procedure to acquire that FFP.
  • FIG.10 illustrates a block diagram of a communication device such as an evolved Node-B (eNB), a new generation Node-B (gNB) (or another RAN node), an access point (AP), a wireless station (STA), a mobile station (MS), or a user equipment (UE), in accordance with some aspects and to perform one or more of the techniques disclosed herein.
  • the communication device 1000 may operate as a standalone device or may be connected (e.g., networked) to other communication devices.
  • Circuitry e.g., processing circuitry
  • circuitry is a collection of circuits implemented in tangible entities of the device 1000 that include hardware (e.g., simple circuits, gates, logic, etc.). Circuitry membership may be flexible over time. Circuitries include members that may, alone or in combination, perform specified operations when operating.
  • the hardware of the circuitry may be immutably designed to carry out a specific operation (e.g., hardwired).
  • the hardware of the circuitry may include variably connected physical components (e.g., execution units, transistors, simple circuits, etc.) including a machine-readable medium physically modified (e.g., magnetically, electrically, moveable placement of invariant massed particles, etc.) to encode instructions of the specific operation.
  • the underlying electrical properties of a hardware constituent are changed, for example, from an insulator to a conductor or vice versa.
  • the instructions enable embedded hardware (e.g., the execution units or a loading mechanism) to create members of the circuitry in hardware via the variable connections to carry out portions of the specific operation when in operation.
  • the machine-readable medium elements are part of the circuitry or are communicatively coupled to the other components of the circuitry when the device is operating.
  • any of the physical components may be used in more than one member of more than one circuitry.
  • execution units may be used in a first circuit of a first circuitry at one point in time and reused by a second circuit in the first circuitry, or by a third circuit in a second circuitry at a different time. Additional examples of these components with respect to the device 1000 follow.
  • the device 1000 may operate as a standalone device or may be connected (e.g., networked) to other devices. In a networked deployment, the communication device 1000 may operate in the capacity of a server communication device, a client communication device, or both in server- client network environments. In an example, the communication device 1000 may act as a peer communication device in a peer-to-peer (P2P) (or other distributed) network environment.
  • P2P peer-to-peer
  • the communication device 1000 may be a UE, eNB, PC, a tablet PC, an STB, a PDA, a mobile telephone, a smartphone, a web appliance, a network router, switch or bridge, or any communication device capable of executing instructions (sequential or otherwise) that specify actions to be taken by that communication device.
  • the term "communication device” shall also be taken to include any collection of communication devices that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein, such as cloud computing, software as a service (SaaS), and other computer cluster configurations.
  • Examples, as described herein, may include, or may operate on, logic or a number of components, modules, or mechanisms.
  • Modules are tangible entities (e.g., hardware) capable of performing specified operations and may be configured or arranged in a certain manner.
  • circuits may be arranged (e.g., internally or with respect to external entities such as other circuits) in a specified manner as a module.
  • the whole or part of one or more computer systems e.g., a standalone, client, or server computer system
  • one or more hardware processors may be configured by firmware or software (e.g., instructions, an application portion, or an application) as a module that operates to perform specified operations.
  • the software may reside on a communication device-readable medium.
  • the software when executed by the underlying hardware of the module, causes the hardware to perform the specified operations.
  • module is understood to encompass a tangible entity, be that an entity that is physically constructed, specifically configured (e.g., hardwired), or temporarily (e.g., transitorily) configured (e.g., programmed) to operate in a specified manner or to perform part or all of any operation described herein.
  • each of the modules need not be instantiated at any one moment in time.
  • the modules comprise a general-purpose hardware processor configured using the software
  • the general-purpose hardware processor may be configured as respective different modules at different times.
  • the software may accordingly configure a hardware processor, for example, to constitute a particular module at one instance of time and to constitute a different module at a different instance of time.
  • the communication device e.g., UE 1000 may include a hardware processor 1002 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 1004, a static memory 1006, and a storage device 1007 (e.g., hard drive, tape drive, flash storage, or other block or storage devices), some or all of which may communicate with each other via an interlink (e.g., bus) 1008.
  • a hardware processor 1002 e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof
  • main memory 1004 e.g., main memory 1004
  • static memory 1006 e.g., hard drive, tape drive, flash storage, or other block or storage devices
  • the communication device 1000 may further include a display device 1010, an alphanumeric input device 1012 (e.g., a keyboard), and a user interface (UI) navigation device 1014 (e.g., a mouse).
  • UI user interface
  • the display device 1010, input device 1012, and UI navigation device 1014 may be a touchscreen display.
  • the communication device 1000 may additionally include a signal generation device 1018 (e.g., a speaker), a network interface device 1020, and one or more sensors 1021, such as a global positioning system (GPS) sensor, compass, accelerometer, or another sensor.
  • GPS global positioning system
  • the communication device 1000 may include an output controller 1028, such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).
  • an output controller 1028 such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).
  • the storage device 1007 may include a communication device- readable medium 1022, on which is stored one or more sets of data structures or instructions 1024 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein.
  • registers of the processor 1002, the main memory 1004, the static memory 1006, and/or the storage device 1007 may be, or include (completely or at least partially), the device-readable medium 1022, on which is stored the one or more sets of data structures or instructions 1024, embodying or utilized by any one or more of the techniques or functions described herein.
  • the hardware processor 1002, the main memory 1004, the static memory 1006, or the mass storage 1016 may constitute the device-readable medium 1022.
  • the term "device-readable medium” is interchangeable with “computer-readable medium” or “machine-readable medium”.
  • the term “communication device-readable medium” may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) configured to store the one or more instructions 1024.
  • the term “communication device-readable medium” is inclusive of the terms “machine-readable medium” or “computer-readable medium”, and may include any medium that is capable of storing, encoding, or carrying instructions (e.g., instructions 1024) for execution by the communication device 1000 and that causes the communication device 1000 to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding or carrying data structures used by or associated with such instructions.
  • Non-limiting communication device-readable medium examples may include solid-state memories and optical and magnetic media.
  • Specific examples of communication device-readable media may include non- volatile memory, such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto- optical disks; Random Access Memory (RAM); and CD-ROM and DVD-ROM disks.
  • EPROM Electrically Programmable Read-Only Memory
  • EEPROM Electrically Erasable Programmable Read-Only Memory
  • flash memory devices e.g., Electrically Erasable Programmable Read-Only Memory (EEPROM)
  • flash memory devices e.g., Electrically Erasable Programmable Read-Only Memory (EEPROM)
  • flash memory devices e.g., Electrically Erasable Programmable Read-Only Memory (EEPROM)
  • flash memory devices e.g., Electrically Era
  • Instructions 1024 may further be transmitted or received over a communications network 1026 using a transmission medium via the network interface device 1020 utilizing any one of a number of transfer protocols.
  • the network interface device 1020 may include one or more physical jacks (e.g., Ethernet, coaxial, or phone jacks) or one or more antennas to connect to the communications network 1026.
  • the network interface device 1020 may include a plurality of antennas to wirelessly communicate using at least one of single-input-multiple-output (SIMO), MIMO, or multiple- input-single-output (MISO) techniques.
  • SIMO single-input-multiple-output
  • MISO multiple- input-single-output
  • the network interface device 1020 may wirelessly communicate using Multiple User MIMO techniques.
  • transmission medium shall be taken to include any intangible medium that is capable of storing, encoding, or carrying instructions for execution by the communication device 1000, and includes digital or analog communications signals or another intangible medium to facilitate communication of such software.
  • a transmission medium in the context of this disclosure is a device-readable medium.
  • machine-readable medium means the same thing and may be used interchangeably in this disclosure.
  • the terms are defined to include both machine-storage media and transmission media. Thus, the terms include both storage devices/media and carrier waves/modulated data signals.
  • Example 1 is an apparatus for a user equipment (UE) configured for operation in a semi-static channel access mode in a Fifth Generation New Radio (5G NR) network, the apparatus comprising: processing circuitry, wherein to configure the UE for ultra-reliable and low latency communication (URLLC) in an unlicensed spectrum of the 5G NR network, the processing circuitry is to: decode higher layer signaling received from a base station, the higher layer signaling including channel occupancy time (COT) configuration information with multiple COT sharing combinations, each of the COT sharing combinations specifying a duration and an offset; acquire a fixed frame period (FFP) based on successful completion of a listen-before-talk (LBT) procedure performed by the UE as an initiating device, the FFP comprising a COT and an idle period; encode configured grant (CG) uplink control information (UCI) for transmission to the base station, the CG U
  • CG channel occupancy time
  • Example 2 the subject matter of Example 1 includes subject matter where the DL transmission is received starting at a DL transmission slot that is separated by a number of slots from an end of a transmission of the CG UCI, the number of slots corresponding to the offset of the COT sharing combination.
  • Example 3 the subject matter of Examples 1–2 includes subject matter where to perform the LBT procedure, the processing circuitry is to: perform energy detection of the unlicensed spectrum based on an energy detection threshold.
  • Example 4 the subject matter of Example 3 includes subject matter where the energy detection threshold is based on a maximum transmit power of the UE.
  • Example 5 the subject matter of Examples 1–4 includes subject matter where the DL information comprises one or both of DL data and DL control information dedicated for the UE.
  • Example 6 the subject matter of Examples 1–5 includes subject matter where the processing circuitry is to: complete reception of the DL transmission before an end of the FFP.
  • Example 7 the subject matter of Examples 1–6 includes, transceiver circuitry coupled to the processing circuitry; and one or more antennas coupled to the transceiver circuitry.
  • Example 8 is a computer-readable storage medium that stores instructions for execution by one or more processors of a base station, the instructions to configure the base station for ultra-reliable and low latency communication (URLLC) in an unlicensed spectrum of in a Fifth Generation New Radio (5G NR) network, and to cause the base station to perform operations comprising: encoding higher layer signaling for transmission to a user equipment (UE), the higher layer signaling including channel occupancy time (COT) configuration information with multiple COT sharing combinations, each of the COT sharing combinations specifying a duration and an offset; decoding configured grant (CG) uplink control information (UCI), the CG UCI received during a fixed frame period (FFP) of the UE, the FFP acquired based on successful completion of a listen-before-talk (LBT) procedure performed by the UE as an initiating device, the FFP comprising a COT and an idle period, the CG UCI including a COT sharing indication associated with a COT sharing combination of the multiple COT sharing combinations; and encoding
  • Example 9 the subject matter of Example 8 includes subject matter where the DL transmission is performed starting at a DL transmission slot that is separated by a number of slots from an end of a transmission of the CG UCI, the number of slots corresponding to the offset of the COT sharing combination.
  • Example 10 the subject matter of Examples 8–9 includes subject matter where the DL information comprises one or both of DL data and DL control information dedicated for the UE.
  • Example 11 the subject matter of Examples 8–10 includes, the operations further comprising: completing the DL transmission before an end of the FFP.
  • Example 12 the subject matter of Examples 8–11 includes, the operations further comprising: refraining from sensing a downlink channel before the DL transmission during the COT.
  • Example 13 the subject matter of Example 12 includes, the operations further comprising: refraining from constraining a duration of the DL transmission to 584 us.
  • Example 14 the subject matter of Examples 12–13 includes, the operations further comprising: scheduling during the COT, an uplink (UL) transmission by at least a second UE.
  • UL uplink
  • Example 15 is a computer-readable storage medium that stores instructions for execution by one or more processors of a user equipment (UE), the instructions to configure the UE for ultra-reliable and low latency communication (URLLC) while in a semi-static channel access mode in an unlicensed spectrum of a Fifth Generation New Radio (5G NR) network, and to cause the UE to perform operations comprising: decoding higher layer signaling received from a base station, the higher layer signaling including channel occupancy time (COT) configuration information with multiple COT sharing combinations, each of the COT sharing combinations specifying a duration and an offset; acquiring a fixed frame period (FFP) based on successful completion of a listen-before-talk (LBT) procedure performed by the UE as an initiating device, the FFP comprising a COT and an idle period; encoding configured grant (CG) uplink control information (UCI) for transmission to the base station, the CG UCI including a COT sharing indication associated with a COT sharing combination of the multiple COT sharing combinations; and de
  • COT
  • Example 16 the subject matter of Example 15 includes subject matter where the DL transmission is received starting at a DL transmission slot that is separated by a number of slots from an end of a transmission of the CG UCI, the number of slots corresponding to the offset of the COT sharing combination.
  • Example 17 the subject matter of Examples 15–16 includes subject matter where to perform the LBT procedure, the operations further comprising: performing energy detection of the unlicensed spectrum based on an energy detection threshold.
  • the subject matter of Example 17 includes subject matter where the energy detection threshold is based on a maximum transmit power of the UE.
  • Example 19 the subject matter of Examples 15–18 includes subject matter where the DL information comprises one or both of DL data and DL control information dedicated for the UE.
  • Example 20 the subject matter of Examples 15–19 includes, the operations further comprising: completing reception of the DL transmission before an end of the FFP.
  • Example 21 is at least one machine-readable medium including instructions that, when executed by processing circuitry, cause the processing circuitry to perform operations to implement any of Examples 1–20.
  • Example 22 is an apparatus comprising means to implement any of Examples 1–20.
  • Example 23 is a system to implement any of Examples 1–20.
  • Example 24 is a method to implement any of Examples 1–20.

Landscapes

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

Abstract

Un support de stockage lisible par ordinateur stocke des instructions pour configurer une station de base pour URLLC et pour amener la station de base à coder une signalisation de couche supérieure pour une transmission à un UE. La signalisation de couche supérieure comprend des informations de configuration de COT avec de multiples combinaisons de partage de COT. Chacune des combinaisons de partage de COT spécifie une durée et un décalage. Des UCI CG reçues pendant une FFP de l'UE sont décodées. La FFP comprend un COT et une période inactive. Les UCI CG comprennent une indication de partage de COT associée à l'une des multiples combinaisons de partage de COT. Une transmission DL vers l'UE est réalisée pendant le COT. La transmission DL comprend un certain nombre de créneaux de transmission DL correspondant à la durée de la combinaison de partage de COT.
PCT/US2022/011955 2021-01-13 2022-01-11 Procédure de partage de cot pour communications à bande sans licence WO2022155125A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202280008110.5A CN116636294A (zh) 2021-01-13 2022-01-11 用于免授权频段通信的cot共享过程

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
US202163136740P 2021-01-13 2021-01-13
US63/136,740 2021-01-13
US202163216383P 2021-06-29 2021-06-29
US63/216,383 2021-06-29
US202163247472P 2021-09-23 2021-09-23
US63/247,472 2021-09-23

Publications (1)

Publication Number Publication Date
WO2022155125A1 true WO2022155125A1 (fr) 2022-07-21

Family

ID=82447491

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2022/011955 WO2022155125A1 (fr) 2021-01-13 2022-01-11 Procédure de partage de cot pour communications à bande sans licence

Country Status (1)

Country Link
WO (1) WO2022155125A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024072166A1 (fr) * 2022-09-29 2024-04-04 엘지전자 주식회사 Procédé et dispositif de partage de cot généré dans une bande sans licence
WO2024065071A1 (fr) * 2022-09-26 2024-04-04 Qualcomm Incorporated Structures de détection et priorisation dans un partage de temps d'occupation de canal pour une liaison latérale dans un spectre sans licence

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200045739A1 (en) * 2015-09-17 2020-02-06 Lg Electronics Inc. Method and device for performing lbt process on multiple carriers in wireless access system supporting unlicensed band
WO2020032727A1 (fr) * 2018-08-09 2020-02-13 엘지전자 주식회사 Procédé de transmission d'un rach par un terminal dans un système de communication sans fil et terminal utilisant ledit procédé
US20200280971A1 (en) * 2019-02-28 2020-09-03 Electronics And Telecommunications Research Institute Method and apparatus for transmitting and receiving control information in communication system supporting unlicensed band
WO2020198499A1 (fr) * 2019-03-27 2020-10-01 Idac Holdings, Inc Procédés et appareils de transmission à octroi de ressources configuré dans un spectre sans licence
US20200351919A1 (en) * 2019-05-02 2020-11-05 Samsung Electronics Co., Ltd. Method and apparatus for determining time domain resource area in wireless communication system

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200045739A1 (en) * 2015-09-17 2020-02-06 Lg Electronics Inc. Method and device for performing lbt process on multiple carriers in wireless access system supporting unlicensed band
WO2020032727A1 (fr) * 2018-08-09 2020-02-13 엘지전자 주식회사 Procédé de transmission d'un rach par un terminal dans un système de communication sans fil et terminal utilisant ledit procédé
US20200280971A1 (en) * 2019-02-28 2020-09-03 Electronics And Telecommunications Research Institute Method and apparatus for transmitting and receiving control information in communication system supporting unlicensed band
WO2020198499A1 (fr) * 2019-03-27 2020-10-01 Idac Holdings, Inc Procédés et appareils de transmission à octroi de ressources configuré dans un spectre sans licence
US20200351919A1 (en) * 2019-05-02 2020-11-05 Samsung Electronics Co., Ltd. Method and apparatus for determining time domain resource area in wireless communication system

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024065071A1 (fr) * 2022-09-26 2024-04-04 Qualcomm Incorporated Structures de détection et priorisation dans un partage de temps d'occupation de canal pour une liaison latérale dans un spectre sans licence
WO2024072166A1 (fr) * 2022-09-29 2024-04-04 엘지전자 주식회사 Procédé et dispositif de partage de cot généré dans une bande sans licence

Similar Documents

Publication Publication Date Title
WO2022031544A1 (fr) Dmrs pour des communications nr supérieures à 52,6 ghz
US20210368581A1 (en) Ue-to-ue relay service in 5g systems
KR20230161982A (ko) Redcap 사용자 장비들을 위한 bwp-기반 동작들
WO2022155125A1 (fr) Procédure de partage de cot pour communications à bande sans licence
US11877268B2 (en) Streamlining protocol layers processing, and slotless operation
WO2022087399A1 (fr) Configurations pour des communications de liaison latérale nr ultra-fiables
WO2022087094A1 (fr) Commande de puissance d'émission pour des unités distribuées d'un réseau iab
WO2022026161A1 (fr) Signal de réservation pour communications au-delà de 52,6 ghz
WO2023205029A1 (fr) Transmission et réception améliorées pour dispositifs redcap
WO2023137091A1 (fr) Groupement de cellules pour planification multicellulaire
WO2022086929A1 (fr) Configuration de temps de traitement dans des réseaux nr
WO2022051738A1 (fr) Rétroaction harq pour transmissions de données de liaison descendante
US20240179689A1 (en) Time domain window for joint channel estimation
US20240155603A1 (en) Dl reception and ul transmission overlap for hd-fdd operations
US20240188079A1 (en) Cross-carrier scheduling with different cell numerologies
US20240155607A1 (en) Configuration of multiple component carrier repetition transmissions
US20240154680A1 (en) Beam management for multi-trp operation in wireless networks
US20230388997A1 (en) Techniques for uplink (ul) simultaneous transmission across multi-panels (stxmp)
US20230379839A1 (en) Enhanced sounding reference signal (srs) power control
US20240154723A1 (en) Code block interleaving for dft-s-ofdm waveforms
WO2022155131A1 (fr) Déclenchement et réponse d'indication de dispositif dans des réseaux sans fil
WO2023205201A1 (fr) Configuration et synchronisation à duplexage par répartition dans le temps au niveau d'un répéteur
WO2022150503A1 (fr) Indication de ressource srs et tpmi dans multi-trp
WO2023150373A1 (fr) Configuration de dmrs pour transmissions de petites données
WO2023014884A1 (fr) Améliorations dci pour indication de disponibilité de ressource logicielle

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: 22739929

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 202280008110.5

Country of ref document: CN

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 22739929

Country of ref document: EP

Kind code of ref document: A1