WO2022087399A1 - Configurations pour des communications de liaison latérale nr ultra-fiables - Google Patents

Configurations pour des communications de liaison latérale nr ultra-fiables Download PDF

Info

Publication number
WO2022087399A1
WO2022087399A1 PCT/US2021/056238 US2021056238W WO2022087399A1 WO 2022087399 A1 WO2022087399 A1 WO 2022087399A1 US 2021056238 W US2021056238 W US 2021056238W WO 2022087399 A1 WO2022087399 A1 WO 2022087399A1
Authority
WO
WIPO (PCT)
Prior art keywords
sidelink
transmission
resources
network
sci
Prior art date
Application number
PCT/US2021/056238
Other languages
English (en)
Inventor
Alexey Khoryaev
Mikhail Shilov
Sergey PANTELEEV
Artyom LOMAYEV
Kilian Peter Anton ROTH
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
Publication of WO2022087399A1 publication Critical patent/WO2022087399A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/1607—Details of the supervisory signal
    • H04L1/1657—Implicit acknowledgement of correct or incorrect reception, e.g. with a moving window
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/18—Interfaces between hierarchically similar devices between terminal devices

Definitions

  • wireless communications Some aspects relate to wireless networks such as 3 GPP (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 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.
  • 5G networks such as 3 GPP (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 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.
  • 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 systems. Such enhanced operations can include techniques for sidelink communications in 5G-NR networks.
  • FIG. 1 A 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 block diagram of NR vehicle-to-everything
  • V2X sensing and resource selection, according to some embodiments.
  • FIG. 6 illustrates a block diagram of NR V2X sidelink communications, according to some embodiments.
  • FIG. 7 illustrates a block diagram of sidelink communication protocols with a sidelink scheduling request (SS-REQ), a sidelink scheduling response (SS-RSP), and data communication according to some embodiments.
  • SS-REQ sidelink scheduling request
  • SS-RSP sidelink scheduling response
  • FIG. 8 illustrates a block diagram of indication of identified sidelink half-duplex resources by a target receiver (RX) UE, according to some embodiments.
  • FIG. 9 illustrates a block diagram of indication of a candidate resource set by a target RX UE, according to some embodiments.
  • FIG. 10 illustrates a block diagram of enhancement of NR V2X sensing and resource selection procedures to support sharing of candidate resource sets from RX UEs, according to some embodiments.
  • FIG. 11 illustrates a block diagram of receiver-based resource allocation for a transmitter (TX), according to some embodiments.
  • FIG. 12 illustrates a block diagram of enhancement of NR V2X sensing and resource selection procedures to support sharing of RX-based scheduling information, according to some embodiments.
  • FIG. 13 illustrates a block diagram of relaying by a UE RX-A sidelink reservations made by a UE TX-B, according to some embodiments.
  • FIG. 14 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. 1 A illustrates an architecture of a network in accordance with some aspects.
  • the network 140A is shown to include user equipment (UE)
  • UE user equipment
  • 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 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
  • pagers pagers
  • laptop computers desktop computers
  • wireless handsets wireless handsets
  • drones or any other computing device including a wired and/or wireless communications interface.
  • UE 101 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 cany 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
  • any of the UEs 101 and 102 can comprise an Intemet-of-Things (loT) UE or a Cellular loT (CIoT) UE, which can comprise a network access layer designed for low-power loT applications utilizing shortlived UE connections.
  • any of the UEs 101 and 102 can include a narrowband (NB) loT 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 loT 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 loT networks.
  • M2M or MTC exchange of data may be a machine-initiated exchange of data.
  • An loT network includes interconnecting loT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections.
  • the loT UEs may execute background applications (e.g., keepalive messages, status updates, etc.) to facilitate the connections of the loT network.
  • any of the UEs 101 and 102 can include enhanced MTC (eMTC) UEs or further enhanced MTC (FeMTC) UEs.
  • eMTC enhanced MTC
  • FeMTC enhanced MTC
  • 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.
  • 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.
  • These access nodes can be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), Next Generation NodeBs (gNBs), 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). In instances when 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.
  • TRPs transmission/reception points
  • 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 SI interface 113.
  • 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 SI interface 113 is split into two parts: the Sl-U interface 114, which carries user traffic data between the RAN nodes 111 and 112 and the serving gateway (S-GW) 122, and the SI -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 SI -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 SI 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 131 A, 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
  • 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.
  • VoIP Voice-over- Internet Protocol
  • 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 PCRF 126 may be communicatively coupled to the application server 184 via the P-GW 123.
  • the communication network 140A can be an loT 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.
  • a 5G new radio network using communications in the licensed (5G NR) and the unlicensed (5G NR-U) spectrum.
  • One of the current enablers of loT is the narrowband-IoT (NB-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 to 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 3GPP 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.
  • the master/primary node may operate in a licensed band and the secondary node may operate in an unlicensed band.
  • 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
  • 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
  • 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 (NGRAN) 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.
  • NGRAN 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 downlinkbased 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.
  • P-CSCF proxy CSCF
  • S-CSCF serving CSCF
  • E-CSCF emergency CSCF
  • I-CSCF interrogating CSCF
  • 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).
  • 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 servicebased 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 servicebased interfaces: Namf 158H (a service-based interface exhibited by the AMF 132), Nsmf 1581 (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 servicebased 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
  • FIGS. 1 A-4 illustrate various systems, devices, and components that may implement aspects of disclosed embodiments in different communication systems, such as 5G-NR networks including 5G non-terrestrial networks (NTNs).
  • 5G-NR networks including 5G non-terrestrial networks (NTNs).
  • UEs, base stations (such as gNBs), and/or other nodes (e.g., satellites or other NTN nodes) discussed in connection with FIGS. 1 A-4 can be configured to perform the disclosed techniques.
  • NTNs non-terrestrial networks
  • 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.
  • 3GPP technical specifications for LTE or 5G/NR systems 3GPP technical specifications for LTE or 5G/NR systems.
  • the example embodiments are not limited in this regard and the described embodiments may apply to other networks that benefit from the principles described herein, such as future 3GPP systems, or the like.
  • 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, loT 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.
  • 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 LI protocols.
  • RRC Radio Resource Control
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • MAC Medium Access Control
  • LI protocols Low Latency 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 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 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;
  • SCS sub-carrier spacing
  • the LTE air interface may rely on CSI-RS for CSI acquisition and beam management;
  • 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
  • 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. When a BWP change is indicated to the UE 202, the SCS of the transmission is changed as well.
  • 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
  • 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 subslice.
  • 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 SI 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-3 GPP 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.
  • 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.
  • 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.
  • 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 (Nl) 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 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). Additionally, the NSSF 250 may exhibit an Nnssf service-based interface.
  • the NEF 252 may securely expose services and capabilities provided by 3 GPP 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 NF s 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.
  • 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. As used herein, 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. Additionally, 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.
  • 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.
  • the network operator may permit AF 260 to interact directly with relevant NFs. Additionally, the AF 260 may exhibit a Naf service-based interface.
  • the data network 236 may represent various network operator services, Internet access, or third-party services that may be provided by one or more servers including, for example, application/content server 238.
  • 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 circuitiy 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
  • 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, spacefrequency 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
  • 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 receivebeamforming 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
  • 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. In addition to performing data transmi ssion/reception as described above, the components of the AN 304 may perform various logical functions that include, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.
  • 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.
  • 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.
  • 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 radiofrequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.
  • CPU central processing unit
  • RISC reduced instruction set computing
  • CISC complex instruction set computing
  • GPU graphics processing unit
  • DSP such as a baseband processor, an ASIC, an FPGA, a radiofrequency 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.
  • DRAM dynamic random access memory
  • SRAM static random access memory
  • EPROM erasable programmable read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • 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, WiFi® 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.
  • circuitry associated with a UE, base station, satellite, network element, etc. as described above in connection 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 in the example section.
  • AI/ML 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.
  • AI/ML application may be used for configuring or implementing one or more of the disclosed aspects.
  • machine learning 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.
  • an ML algorithm is a computer program that learns from experience with respect to some task and some performance measure
  • 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-leaming, multi-armed bandit learning, deep RL, etc.), neural networks, and the like.
  • 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.
  • non-terrestrial networks indicates networks, or segments of networks, using an airborne or space-borne vehicle configured as a transmission equipment relay node or a base station.
  • a non-terrestrial network may use RF resources onboard a satellite (or unmanned aircraft system (UAS) platform).
  • UAS unmanned aircraft system
  • the disclosed techniques may be used to provide sidelink power saving, reduced latency, and increased reliability.
  • the disclosed techniques include receiver (Rx)-assistance methods for enhancement of the NR- V2X sidelink designs based on transmitter (Tx)-only sensing.
  • the disclosed techniques may be used to increase the reliability of NR sidelink communications and overcome drawbacks associated with Tx-only sensing, such as reliability issues due to half-duplex and hidden node problems.
  • NR V2X sidelink communication is based on transmitter sensing-based solutions for resource selection.
  • the sidelink communications may be optimized for periodic and aperiodic traffic for unicast, groupcast, and broadcast communication types.
  • the TX sensing-based protocol implements distributed system architecture where all UEs have equal rights for channel access. The more favored channel access and propagation conditions are supported based on assignment sidelink transmission priority.
  • Example channel access procedures for NR V2X sidelink communications are shown in FIG. 5.
  • FIG. 5 illustrates a block diagram 500 of NR vehicle-to- everything (V2X) sensing and resource selection, according to some embodiments.
  • FIG. 6 illustrates a block diagram 600 of NR V2X sidelink communications, according to some embodiments.
  • V2X vehicle-to- everything
  • sidelink communication can include the following procedures: transmitter-based sensing, resource exclusion to form candidate resource set, resource selection w/ randomization, selected resource re- evaluation, and actual sidelink transmission with reservation indication.
  • Inter-UE coordination may be used as one of the techniques to further optimize the performance of NR sidelink for V2X or other applications.
  • the disclosed techniques may include using a set of resources (e.g., at a Tx UE, also referred to as UE-B or Tx-B) which are determined at the Rx UE (also referred to as UE-A or RX-A).
  • This set of available resources e.g., time/frequency resources
  • UE-B considers the communicated available resources by UE-A dining the resource selection for its transmission.
  • Some challenges in distributed communication systems include half-duplex issues, hidden node issues, and persistent collisions.
  • the existing solution is transparent to communication type in terms of sensing and resource selection procedure.
  • the UE (re)-selecting resources performs resource exclusion procedure without distinguishing whether sensed resources cany transmissions to the UE reselecting resources (i.e., comes from target transmitter) that may increase the probability of half- duplex since these resources may become part of candidate resource set.
  • the disclosed techniques may be used to detect and distinguish the following resource types:
  • Type 1 resources (slots) reserved by TX (UE-B) for transmissions to RX (UE-A);
  • Type 2 resources (slots) reserved by TX (UE-B) for transmissions to other UEs (e.g., group members or for broadcast transmission). Type-2 may be excluded if the RX (UE-A) wants to communicate with the TX (UE-B).
  • Type 3 resources (slots) used for transmission by RX (UE-A) to target unicast TXs (UE-B), to members) of the group, and/or to all UEs (e.g., via broadcast).
  • Type-3 resources can be excluded directly by the TX UEs through sidelink control information (SCI) processing subject to sidelink transmission priority and reference signal received power (RSRP) threshold comparison.
  • SCI sidelink control information
  • RSRP reference signal received power
  • the RX (UE-A) can decode SCIs from TX(s) (UE-B or other group members) and exclude half-duplex resources using source and destination IDs carried over the air.
  • Source and destination IDs can be used to determine resources carrying transmission of target RX and/or TX.
  • SCI-based resource reservation signaling can serve as an example of Solution 2.
  • the number of resources reserved by single SCI transmission can be further increased.
  • FIG. 7 illustrates a block diagram 700 of sidelink communication protocols with a sidelink scheduling request (SS-REQ), a sidelink scheduling response (SS-RSP), and data communication according to some embodiments.
  • SS-REQ sidelink scheduling request
  • SS-RSP sidelink scheduling response
  • the SS-REQ may also be referred to as S-SR or as a sidelink feedback request (S-FR).
  • the receiver-based assistance for sidelink resource selection may need to support a three-step sidelink protocol as shown in FIG. 7, where the following processing can be performed:
  • Step 1 SS-REQ is transmitted by TX UE-B to RX UE-A and includes a request to provide RX assistance information.
  • the SS-REQ may be accompanied by initial data transmission.
  • SS-REQ may be based on at least one of the following signaling mechanisms: SCI Stage - 1 (physical sidelink control channel, or PSCCH), SCI Stage - 2, physical sidelink shared channel (PSSCH) carrying sidelink media access control (MAC) control element (CE), PSSCH carrying sidelink RRC signaling, and/or new signaling mapped onto physical sidelink feedback channel (PSFCH) resources.
  • PSSCH physical sidelink shared channel
  • CE media access control element
  • PSSCH carrying sidelink RRC signaling
  • new signaling mapped onto physical sidelink feedback channel (PSFCH) resources may be skipped in certain scenarios/design options as discussed herein below.
  • Step 2 Sidelink scheduling response (SS-RSP) (also referred to as sidelink scheduling feedback, or S-SF) is transmitted by the RX UE-A to the TX UE-B, and responds with the RX assistance information (e.g., information of available sidelink time/frequency resources as detected/ sensed by the UE-A).
  • SS-RSP sidelink scheduling response
  • RX assistance information e.g., information of available sidelink time/frequency resources as detected/ sensed by the UE-A.
  • SS-RSP may be based on at least one of the following signaling mechanisms: SCI Stage - 1 (PSCCH), SCI Stage - 2, PSSCH carrying sidelink MAC CE, and/or PSSCH carrying sidelink RRC.
  • Step 3 Data transmission (or retransmission).
  • SS-REQ and SS-RSP can be monitored by all UEs and information contained inside of these messages can be used for enhanced sensing and resource selection procedures.
  • the following signaling options may be configured.
  • Option 1 Indication of half-duplex resources (i.e., resources reserved for transmission by RX (UE-A).
  • FIG. 8 illustrates a block diagram 800 of indication of identified sidelink half-duplex resources by a target receiver (RX) UE, according to some embodiments.
  • two types of half-duplex resources may be carried in SS-RSP: Type 3: resources (slots) reserved (selected) for transmissions by RX(UE-A) to TX(UE-B); and Type 4: resources(slots) reserved (selected) for transmissions by RX(UE-A) to other UEs.
  • TX can decode all SCIs from RX (UE- A) and exclude half-duplex resources of both types. Therefore, such processing can be supported by ReL 16 with minor enhancement on slot-based exclusion/preemption in case of detected half-duplex issues.
  • Option 2 Indication of candidate resource set for reception and/or transmission.
  • FIG. 9 illustrates a block diagram 900 of indication of a candidate resource set by a target RX UE, according to some embodiments.
  • RX UE-A can signal information on candidate resource set in SS-RSP.
  • the candidate resource set for reception may be different from the candidate resource set for transmission.
  • different procedures may be used to form different candidate resource sets for reception and transmission by a UE (e.g., for the handling of half-duplex resources and priority considerations).
  • the candidate resource set (CRS) for TX is not equal to CRS for RX since the following parameters need to be provided to RX UE that may be different.
  • Required parameters to form candidate resource set(s) for reception and/or transmission may include: 1) reference resource size in subchannels, 2) reference start slot, 3) reference resource selection window duration, 4) resource pool ID, 5) information on the priority of sidelink transmission, 6) RSRP thresholds for exclusion procedure, 7) reference period, and 8) threshold for min candidate resource set size may need to be provided/configured to form candidate resource set by RX UE and can be signaled by Target TX or gNB/NW towards target RX UE. In other embodiments, these parameters can be automatically determined by a UE.
  • the candidate resource set formed by a UE may also exclude half-duplex resources (slots) subject to priority conditions and RSRP thresholds, i.e. Solution 1 may be implemented.
  • the following halfduplex resources may be excluded: Type 3: resources reserved (selected) for transmissions by RX (UE-A) to TX (UE-B); Type 4: resources reserved (selected) for transmissions by RX (UE-A) to other UEs. If the candidate resource set includes half-duplex resources (slots), the identified half-duplex resources (slots) may be reported separately.
  • the following techniques may be used to determine/select assisting UEs when a candidate resource set is generated. If a UE takes into account CRSs from all UEs, then the UE may not see any nonoccupied resource, and information from a subset of assisting UEs may be considered.
  • the following criteria can be used to select assisting UE: assisting UE is a target unicast RX, assisting UE is a member of the same group and is target RX, assisting UE is within a target pre-configured communication range [RSRP1, RSRP2], and assisting UE is within a target pre-configured distance range [D1, D2],
  • the distance range could be specified relative to some specified reference point.
  • the reference point could be Alternative 1: Location of the Target Transmitter, or Alternative 2: Location of the Target Receivers). In the case of a group of target receivers, the reference point could be a function of the target receiver's coordinates.
  • candidate resource sets may be reported together with information on measured SL-RSRP/priority values on resources of candidate resource set. This additional information can be used to further improve resource exclusion and resource selection procedures.
  • a UE may report a set of excluded resources, or resources with an RSRP threshold above the preconfigured threshold together with information on priority values on reported resources and their position in the spectrum. This information can be carried in SS-RSP.
  • FIG. 10 illustrates a block diagram 1000 of enhancement of NR V2X sensing and resource selection procedures to support sharing of candidate resource sets from RX UEs, according to some embodiments.
  • FIG. 11 illustrates a block diagram 1100 of receiver-based resource allocation for a transmitter (TX), according to some embodiments.
  • Option 1 Receiver-based scheduling.
  • RX (UE-A) can transmit SCI or use other types of signaling that reserve specific resources (slots) for TXs (e.g. UE-B in case of unicast or group members).
  • the RX UE can use SS-RSP for that purpose.
  • the regular sensing and resource selection procedure (or with described enhancements) running at target Rx UE can be used to identify resources for target TX UE (e.g., as illustrated in FG. 12).
  • FIG. 12 illustrates a block diagram 1200 of enhancement of NR V2X sensing and resource selection procedures to support sharing of RX-based scheduling information, according to some embodiments.
  • TXs may respect resources (slots) reserved by RX (UE-A) and signaled over the air. For instance, TXs can use this information to avoid half-duplex issues subject to priority/RSRP information that can be used for preemption purposes.
  • the reserved by RX resources and announced over air can be decoded by UEs selecting resources for transmission that can either: Option 1) exclude those resources during resource exclusion procedure, or Option 2) avoid selecting those resources during the resource selection procedure.
  • Option 1) may be a preferable solution.
  • the RX UE may need to broadcast semi-persistently reserved resources right before each semi-persistent transmission period [00151] In the case of aperiodic transmissions, the RX UE may need to broadcast dynamically reserved resources once the new resource reservation information was signaled by the TX UE.
  • Option 2 Assignment of resource pattern for the reception.
  • a resource pattern for reception is provided to/by RX (UE-A), where transmissions from TX (UE-B) are expected.
  • Option 2A Resource pattern for reception is provided/assigned by RX (UE-A) to TX(s) (UE-B and other group members) so that TX(s) take it into account in its resource selection.
  • TX(s) may either:
  • TX may prioritize selection of candidate resources that overlap/intersect with reception pattern) if reception pattern is associated with TX;
  • Option 2B Resource pattern for reception is provided/assigned by TX(UE-B) to RX(UE-A).
  • TX (UE-B) checks if the candidate resource set has resources from a pattern for reception and prioritizes those for selection for transmission towards RX(UE-A). If there is no intersection in resources with reception pattern TX(UE-B) postpones/drops transmissions to RX(UE-A).
  • the RX avoids selecting resources that overlap with an assigned pattern for reception, i.e., prioritizes the selection of resources from candidate resource sets that do not overlap/intersect with the reception pattern.
  • the RX UE-A may decode and relay the control information of TX UE-B. For instance, in the case of unicast communication target RX UE-A can decode SCI reserving resources for transmission towards RX UE-A and announce the reserved resources over the air so that other UEs reselecting resources take into account relayed reservations of TX UE-A and exclude those from the set of potential resources for transmission.
  • UE RX-A relays part of (or the entire) content of the UE SCI transmitted by TX-B towards UE RX-A is illustrated in FIG. 13.
  • FIG. 13 illustrates a block diagram 1300 of relaying by a UE RX- A sidelink reservations made by a UE TX-B, according to some embodiments.
  • half-duplex issue means implicit ACK for the transmitter. This processing may be non-optimal since each half-duplex problem is treated by the TX UE as successful reception which is problematic behavior from a system perspective. As a solution, the predefined minimum number of initial blind retransmissions can help to cope with this issue. Another option that can be considered is an indication of detected HD issues by assisting UEs.
  • the disclosed proposal for a connection-less groupcast with NACK-only transmissions may be used.
  • the disclosed techniques may be supported by UE implementation in Rel. 16.
  • the disclosed techniques may benefit from taking possible halfduplex collisions into account during resource selection.
  • the TX can indicate the preferred pattern for transmission and perform Rel. 16 procedure to form a candidate resource set.
  • the Tx UE can prioritize for selection candidate resources (slots) that overt ap/intersect with a candidate resource set.
  • the RX can deprioritize resources (slots) indicated by TX UE for resource selection. Solutions Based on Assisting UEs (i.e.. not target TX and RX - volunteering UE)
  • multiple assisting UEs may detect collision and send assistance messages to transmitters.
  • Procedure to determine assisting UEs may be configured.
  • the following UEs can be considered as assisting UEs: target UEs (e.g., unicast RX, group member); UEs that intend to perform initial sidelink transmission within the predefined time interval from detected collision/half-duplex event; Pre-configured set of UEs (e.g. pre-configured group members); UEs within preconfigured RSRP range; UEs within preconfigured distance range; and combination of the above conditions/criteria.
  • target UEs e.g., unicast RX, group member
  • UEs that intend to perform initial sidelink transmission within the predefined time interval from detected collision/half-duplex event e.g., Pre-configured set of UEs (e.g. pre-configured group members); UEs within preconfigured RSRP range; UEs within preconfigured distance range; and combination of the above conditions/criteria.
  • conditions to trigger transmission of assistance message may include: UE serves as assisting UE and detected half-duplex or collision problem; priority level of collided transmi ssion(s) is above/below priority threshold and RSRP difference is within predefined range; Half-duplex issue (the identical Source and Destination IDs are detected in one slot in different sidelink transmissions); minimum number of collided (re)transmissions to declare half-duplex issue can be preconfigured; collision issue (RSRP levels or RSRP level difference is within a pre-configured range and partial or full overlap of resources used for transmission so that UE may not be able to decode at least one of the transmissions).
  • Content of assistance message may include: resources (slots/sub- channels indexes) with identified collision/half-duplex issues, priorities of transmissions, measured sidelink RSRP values of transmissions, source and destination IDs of colliding/half-duplex UEs.
  • Resources for transmission of assistance message may include: dedicated resources are preferred over Rel. 16 PSCCH/PSSCH resources (Alt. 1 :
  • TDM allocation as for PSFCH can be used (i.e., at the end of each k-th slot) - allocated in non-PSFCH slots; and Alt.2: FDM allocation, dedicated sub-channel or PRB can be used for that purpose).
  • Assistance messages arrive promptly (as fast as possible) to have a positive effect on aperiodic traffic.
  • a strict requirement on turnaround timing may be used (minimum resource selection window is needed for transmission of PSCCH or PSSCH with assistance data or for dedicated channel).
  • Current reservation signaling of 2 and 3 resources per SCI may not be enough to show a gain for aperiodic traffic and thus a number of reserved resources indicated by a single SCI can be increased to 4.
  • assistance messages may come in advance of the next transmission period for periodic traffic or reserved retransmission for a- periodic traffic.
  • Signaling of the assistance message may include PDCCH SCI Stage -1, SCI Stage 2, Sidelink MAC CE, and Sidelink RRC message.
  • a UE with lower transmission priority receiving the assistance message should yield transmission and may perform resource reselection.
  • a UE with equal priority receiving the assistance message - the predefined rule may be defined to determine whether the UE may yield resources. It can be based on a comparison of measured RSRP with threshold, TBS, MCS index, CRC value, RV, etc.
  • sidelink is the support of the control signaling to change sidelink transmission direction.
  • the disclosed techniques may use a change of sidelink TX direction (control of transmission direction from UE-B to UE-A or vice versa).
  • priority mechanism (arbitrage within pair of unicast UE/ or among groupcast UEs) may be considered and supported by NR sidelink communication. Transmissions from RX (UE-A) may be able to preempt transmissions to TX UE-B or other UEs of the group with lower priority (i.e., subject to sidelink transmission priority).
  • a sidelink scheduling request (SS-REQ) for change of transmission direction may be configured. For example, SS-REQ may be used to change sidelink transmission direction in unicast pair, change transmitting member of the group, or reserve resources for a member of the group. In some aspects, SS-REQ can be transmitted in dedicated resources, which allocation can be like PSFCH.
  • RX UE-A may send a sidelink scheduling request SS-REQ. Once SS-REQ is received by TX (UE-B), it can switch to reception as indicated by SS-REQ resources. Other UEs can process SS-REQ to check whether transmissions were pre-empted by SS-REQ from RX (UE-A).
  • the value of channel occupancy (CR) ratio defined per UE per priority level can be used to decide transmission direction between target TX and target RX.
  • the disclosed techniques include autonomous detection of HD and yielding UE behavior to change TX direction.
  • change of TX direction can be triggered by UE autonomously, if after at least one SCI indicating HD overlap is received. This may be a design option and may be based on a pre-emption mechanism with TDM exclusion with an additional non-priority-based condition. The advantage of this solution is that it does not require separate indications. Resource yielding and resource reselection can be done if HD is detected through SCI processing.
  • the disclosed techniques may include allocation of Rx-only resources (i.e., resources not used for TX).
  • each TX (UE-B) may keep N out of M resources to receive a potential indication for change of transmission direction, otherwise, RX(s) (UE-A or group members) may not have resources for transmission to TX (UE-B or other group member UEs).
  • Method for NR sidelink communication includes the transmission of Sidelink Scheduling Request Message (SS-REQ), the transmission of Sidelink Scheduling Response Message (SS-RSP), sidelink communication, and/or enhanced sensing and resource selection procedures.
  • SS-REQ Sidelink Scheduling Request Message
  • SS-RSP Sidelink Scheduling Response Message
  • sidelink communication and/or enhanced sensing and resource selection procedures.
  • the transmission of SS-REQ may comprise sidelink scheduling request, request to provide response/feedback with candidate resource set identified by RX, request to provide response/feedback with scheduling resources identified by RX, request to perform relaying of control information from TX including reservation of resources, parameters to perform sensing by RX UE and formation of candidate resource set or scheduled resources, QoS indication for TX packets, recommended set of resources for reception, transmission with associated, and request to change sidelink transmission direction (i.e., allocate more sidelink resources for sidelink transmission).
  • the transmission of SS-REQ may comprise one of the following formats: PDCCH SCI Stage 1, SCI Stage 2, PSSCH MAC CE, PSSCH RRC, PSFCH, and new sidelink physical channel for transmission of resource allocation requests/responses.
  • the transmission of SS-RSP may comprise: sidelink scheduling response, time-frequency resources representing candidate resource set identified by RX, time-frequency resources selected/recommended by RX for reception, time-frequency resources selected and reserved by TX and relayed by RX, an indication of half-duplex resources, and parameters used to determine time-frequency resources by RX UE.
  • the transmission of SS-RSP comes from assisting UE and comprises procedure for selection of assisting UE (target UEs (e.g. unicast RX, group member), UEs that intend to perform sidelink transmission within pre-defined time interval from detected collision/half-duplex event, pre-configured set of UEs (e.g.
  • pre-configured group members UEs within preconfigured RSRP range, UEs within preconfigured distance range where the distance range is measured from specified reference point, where the reference point could be a coordinate of the Target Transmitter or Target Receiver, and/or combination of the above conditions/criteria
  • transmission of assistance message triggered by the following conditions e.g., UE serves as assisting UE and detected half-duplex or collision problem, priority level of collided transmission(s) is above/below priority threshold and RSRP difference is within predefined range, half duplex issue where the identical Source and Destination IDs are detected in one slot in different sidelink transmissions, minimum number of collided (re)transmissions to declare half-duplex issue can be preconfigured, collision issue where RSRP levels or RSRP level difference is within a pre-configured range and partial or full overlap of resources used for transmission so that UE may not be able to decode at least one of the transmissions), content of assistance message (e.g., resources (slots/sub-channel
  • TDM allocation as for PSFCH can be used (i.e. at the end of each k-th slot) - allocated in non-PSFCH slots
  • Alt. 2 FDM allocation, dedicated sub-channel or PRB can be used for that purpose, and assistance message should come immediately (as fast as possible) to have a positive effect for aperiodic traffic), and behavior of UEs receiving the assistance message (UE with lower transmission priority receiving the assistance message should yield transmission and may perform resource reselection, and UE with equal priority receiving the assistance message - the predefined rule need to be defined to determine whether UE should yield resources. It can be based on a comparison of measured RSRP with threshold, TBS, MCS index, CRC value, RV, etc.)
  • the enhanced sensing and resource selection procedure that comprises: detection and exclusion of half-duplex resources of various types (Type 1: resources(slots) reserved by TX (UE-B) for transmissions to RX (UE-A), Type 2: resources(slots) reserved by TX (UE-B) for transmissions to other UEs (e.g., group members or for broadcast transmission), Type-2 should be excluded only if RX (UE-A) wants to communicate with TX (UE-B), Type 3: resources(slots) used for transmission by RX (UE-A) to 1) target unicast TXs (UE-B), 2) members) of the group, 3) to all UEs(broadcast)), and decoding of SL-RSP message to extract information on indicated resources and perform resource exclusion using decoded information based on either one of candidate resource set provided by assisting RX, scheduling resources provided by RX, control information from TX including reservation of resources, and recommended set of resources for a reception.
  • Type 1 resources(slots) reserved by
  • FIG. 14 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 (ST A), 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 1400 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 1400 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. In an example, the hardware of the circuitry may be immutably designed to cany 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.
  • variably connected physical components e.g., execution units, transistors, simple circuits, etc.
  • machine-readable medium e.g., magnetically, electrically, moveable placement of invariant massed particles, etc.
  • 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 1400 follow.
  • the device 1400 may operate as a standalone device or may be connected (e.g., networked) to other devices.
  • the communication device 1400 may operate in the capacity of a server communication device, a client communication device, or both in serverclient network environments.
  • the communication device 1400 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 1400 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 1400 may include a hardware processor 1402 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 1404, a static memory 1406, and a storage device 1407 (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) 1408.
  • a hardware processor 1402 e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof
  • main memory 1404 e.g., main memory 1404, a static memory 1406, and a storage device 1407 (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) 1408.
  • an interlink e.g., bus
  • the communication device 1400 may further include a display device 1410, an alphanumeric input device 1412 (e.g., a keyboard), and a user interface (UI) navigation device 1414 (e.g., a mouse).
  • UI user interface
  • the display device 1410, input device 1412, and UI navigation device 1414 may be a touchscreen display.
  • the communication device 1400 may additionally include a signal generation device 1418 (e.g., a speaker), a network interface device 1420, and one or more sensors 1421, such as a global positioning system (GPS) sensor, compass, accelerometer, or another sensor.
  • GPS global positioning system
  • the communication device 1400 may include an output controller 1428, 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.).
  • 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.).
  • USB universal serial bus
  • IR infrared
  • NFC near field communication
  • the storage device 1407 may include a communication device- readable medium 1422, on which is stored one or more sets of data structures or instructions 1424 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein.
  • registers of the processor 1402, the main memory 1404, the static memory 1406, and/or the storage device 1407 may be, or include (completely or at least partially), the device-readable medium 1422, on which is stored the one or more sets of data structures or instructions 1424, embodying or utilized by any one or more of the techniques or functions described herein.
  • one or any combination of the hardware processor 1402, the main memory 1404, the static memory 1406, or the mass storage 1416 may constitute the device-readable medium 1422.
  • the term "device-readable medium” is interchangeable with “computer-readable medium” or “machine-readable medium”. While the communication device-readable medium 1422 is illustrated as a single 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 1424.
  • 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 1424) for execution by the communication device 1400 and that causes the communication device 1400 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.
  • communication device-readable media may include nonvolatile 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; magnetooptical 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 Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)
  • flash memory devices e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)
  • flash memory devices e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory
  • Instructions 1424 may further be transmitted or received over a communications network 1426 using a transmission medium via the network interface device 1420 utilizing any one of a number of transfer protocols.
  • the network interface device 1420 may include one or more physical jacks (e.g., Ethernet, coaxial, or phonejacks) or one or more antennas to connect to the communications network 1426.
  • the network interface device 1420 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
  • MIMO multiple-input-multiple-output
  • MISO multiple- input-single-output
  • the network interface device 1420 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 1400, 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.
  • the terms include both storage devices/media and carrier waves/modulated data signals.
  • Described implementations of the subject matter can include one or more features, alone or in combination as illustrated below by way of examples.
  • Example 1 is an apparatus for a user equipment (UE) configured for operation in a Fifth Generation New Radio (5G NR) network, the apparatus comprising: processing circuitry, wherein to configure the UE as a transmitter UE (Tx UE) performing sidelink communications in the 5G NR network, the processing circuitry is to: encode a sidelink feedback request for transmission to a receiver (Rx) UE in the 5G NR network; decode sidelink scheduling feedback (S-SF) received from the Rx UE in response to the sidelink feedback request, the S-SF including sidelink resource availability information generated by the Rx UE; select sidelink resources based on the sidelink resource availability information; and encode data for a sidelink transmission to the Rx UE, the sidelink transmission using the sidelink resources; and a memory coupled to the processing circuitry and configured to store the sidelink resource availability information.
  • UE user equipment
  • 5G NR Fifth Generation New Radio
  • Example 2 the subject matter of Example 1 includes subject matter where the processing circuitry is configured to: encode the sidelink feedback request to include a request for the S-SF, and cause transmission of the sidelink feedback request using sidelink control information (SCI) transmission.
  • SCI sidelink control information
  • Example 3 the subject matter of Example 2 includes, transmission.
  • Example 4 the subject matter of Examples 1-3 includes subject matter where the processing circuitry is configured to encode the sidelink feedback request in a media access control (MAC) control element (CE) for transmission to the Rx UE using a physical sidelink shared channel (PSSCH).
  • Example 5 the subject matter of Examples 1-4 includes subject matter where the processing circuitry is configured to encode the sidelink feedback request in radio resource control (RRC) signaling for transmission to the Rx UE using a physical sidelink shared channel (PSSCH) carrying the RRC signaling.
  • RRC radio resource control
  • Example 6 the subject matter of Examples 1-5 includes subject matter where the sidelink resource availability information generated by the Rx UE includes an indication of half-duplex resources of the Rx UE.
  • Example 7 the subject matter of Example 6 includes subject matter where the half-duplex resources of the Rx UE comprise at least one of: scheduling resources reserved for transmission by the Tx UE to the Rx UE; and scheduling resources reserved for transmission by the Rx UE to at least another UE.
  • Example 8 the subject matter of Examples 1-7 includes, transceiver circuitry coupled to the processing circuitry; and one or more antennas coupled to the transceiver circuitry.
  • Example 9 is an apparatus for a user equipment (UE) configured for operation in a Fifth Generation New Radio (5G NR) network, the apparatus comprising: processing circuitry, wherein to configure the UE as a receiver UE (Rx UE) performing sidelink communications in the 5G NR network, the processing circuitry is to: decode a sidelink feedback request received from a transmitter (Tx) UE in the 5G NR network; encode sidelink scheduling feedback (S-SF) for transmission to the Tx UE in response to the sidelink feedback request, the S-SF including sidelink resource availability information generated by the Rx UE; and decode data received during a sidelink transmission by the Tx UE, the sidelink transmission using sidelink resources based on the sidelink resource availability information; and a memory coupled to the processing circuitry and configured to store the sidelink feedback request.
  • Tx transmitter
  • S-SF sidelink scheduling feedback
  • Example 10 the subject matter of Example 9 includes, transmission.
  • Example 11 the subject matter of Examples 9-10 includes subject matter where the processing circuitry is to: decode the sidelink feedback request using a media access control (MAC) control element (CE) received from the Tx UE via a physical sidelink shared channel (PSSCH).
  • MAC media access control
  • CE control element
  • Example 12 the subject matter of Examples 9-11 includes subject matter where the processing circuitry is configured to decode sidelink control information (SCI) received from the Tx UE, the SCI including an indication of sidelink resources reserved by the Tx UE for additional sidelink transmissions.
  • SCI sidelink control information
  • Example 13 the subject matter of Example 12 includes subject matter where the processing circuitry is configured to encode the indication of the sidelink resources reserved by the Tx UE for a relay transmission to at least another UE.
  • Example 14 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 as a transmitter UE (Tx UE) performing sidelink communications in a Fifth Generation New Radio (5G NR) network and to cause the UE to perform operations comprising: encoding a sidelink feedback request for transmission to a receiver (Rx) UE in the 5G NR network; decoding sidelink scheduling feedback (S-SF) received from the Rx UE in response to the sidelink feedback request, the S-SF including sidelink resource availability information generated by the Rx UE; selecting sidelink resources based on the sidelink resource availability information; and encoding data for a sidelink transmission to the Rx UE, the sidelink transmission using the sidelink resources.
  • UE user equipment
  • Tx UE transmitter UE
  • 5G NR Fifth Generation New Radio
  • Example 15 the subject matter of Example 14 includes, the operations further comprising: encoding the sidelink feedback request to include a request for the S-SF, and causing transmission of the sidelink feedback request using a sidelink control information (SCI) transmission.
  • SCI sidelink control information
  • Example 16 the subject matter of Example 15 includes, transmission.
  • Example 17 the subject matter of Examples 14-16 includes, the operations further comprising: encoding the sidelink feedback request in a media access control (MAC) control element (CE) for transmission to the Rx UE using a physical sidelink shared channel (PSSCH).
  • MAC media access control
  • CE control element
  • Example 18 the subject matter of Examples 14-17 includes, the operations further comprising: encoding the sidelink feedback request in radio resource control (RRC) signaling for transmission to the Rx UE using a physical sidelink shared channel (PSSCH) carrying the RRC signaling.
  • RRC radio resource control
  • PSSCH physical sidelink shared channel
  • Example 19 the subject matter of Examples 14-18 includes subject matter where the sidelink resource availability information generated by the Rx UE includes an indication of half-duplex resources of the Rx UE.
  • Example 20 the subject matter of Example 19 includes subject matter where the half-duplex resources of the Rx UE comprise at least one of: scheduling resources reserved for transmission by the Tx UE to the Rx UE; and scheduling resources reserved for transmission by the Rx UE to at least another UE.
  • 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 un UE en tant qu'UE émetteur (UE Tx) exécutant des communications de liaison latérale dans un réseau NR 5G, et amener l'UE à exécuter des opérations comprenant le codage d'une demande de rétroaction de liaison latérale pour une transmission à un UE récepteur (UE Rx) dans le réseau NR 5G. Une rétroaction de planification de liaison latérale (S-SF) reçue de l'UE Rx en réponse à la demande de rétroaction de liaison latérale est décodée. La S-SF comprend des informations de disponibilité de ressources de liaison latérale générées par l'UE Rx. Des ressources de liaison latérale sont sélectionnées sur la base des informations de disponibilité de ressources de liaison latérale. Des données sont codées pour une transmission de liaison latérale à l'UE Rx, la transmission de liaison latérale utilisant les ressources de liaison latérale.
PCT/US2021/056238 2020-10-22 2021-10-22 Configurations pour des communications de liaison latérale nr ultra-fiables WO2022087399A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202063104304P 2020-10-22 2020-10-22
US63/104,304 2020-10-22

Publications (1)

Publication Number Publication Date
WO2022087399A1 true WO2022087399A1 (fr) 2022-04-28

Family

ID=81290084

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2021/056238 WO2022087399A1 (fr) 2020-10-22 2021-10-22 Configurations pour des communications de liaison latérale nr ultra-fiables

Country Status (1)

Country Link
WO (1) WO2022087399A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230345424A1 (en) * 2021-06-30 2023-10-26 Qualcomm Incorporated Indication of non-preferred resources for sidelink communications
WO2024011643A1 (fr) * 2022-07-15 2024-01-18 Nec Corporation Procédés, dispositifs terminaux et support lisible par ordinateur destinés aux communications

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170127405A1 (en) * 2015-10-29 2017-05-04 Samsung Electronics Co., Ltd. Method and apparatus for sidelink communication in wireless communication system

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170127405A1 (en) * 2015-10-29 2017-05-04 Samsung Electronics Co., Ltd. Method and apparatus for sidelink communication in wireless communication system

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
FUJITSU: "Considerations on inter-UE coordination for mode 2 enhancements", 3GPP DRAFT; R1-2005546, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20200817 - 20200828, 7 August 2020 (2020-08-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051914984 *
MODERATOR (LG ELECTRONICS): "Summary for AI 8.11.2.2 Feasibility and benefits for mode 2 enhancements", 3GPP DRAFT; R1-2007412, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20200817 - 20200828, 4 September 2020 (2020-09-04), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051929919 *
OPPO: "Inter-UE coordination in mode 2 of NR sidelink", 3GPP DRAFT; R1-2006011, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20200817 - 20200828, 7 August 2020 (2020-08-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051915127 *
ZTE, SANECHIPS: "Inter-UE coordination in mode-2", 3GPP DRAFT; R1-2005961, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20200817 - 20200828, 7 August 2020 (2020-08-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051915081 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230345424A1 (en) * 2021-06-30 2023-10-26 Qualcomm Incorporated Indication of non-preferred resources for sidelink communications
WO2024011643A1 (fr) * 2022-07-15 2024-01-18 Nec Corporation Procédés, dispositifs terminaux et support lisible par ordinateur destinés aux communications

Similar Documents

Publication Publication Date Title
US12047899B2 (en) Techniques for supporting low latency NR positioning protocols
US20240196379A1 (en) Streamlining protocol layers processing, and slotless operation
KR20230161982A (ko) Redcap 사용자 장비들을 위한 bwp-기반 동작들
WO2022051738A1 (fr) Rétroaction harq pour transmissions de données de liaison descendante
US20240073930A1 (en) Sidelink transmission resources for inter-ue coordination feedback
WO2022087399A1 (fr) Configurations pour des communications de liaison latérale nr ultra-fiables
WO2022155125A1 (fr) Procédure de partage de cot pour communications à bande sans licence
WO2022087094A1 (fr) Commande de puissance d'émission pour des unités distribuées d'un réseau iab
US20230421222A1 (en) Subband reporting for full duplex operation
WO2022031541A1 (fr) Gestion de faisceau dans le cadre d'un fonctionnement multi-trp
US20240284386A1 (en) New radio (nr) positioning measurement with reduced latency
US20240155666A1 (en) Determining collisions and conflicts for sidelink communications
US20240179689A1 (en) Time domain window for joint channel estimation
US20240155603A1 (en) Dl reception and ul transmission overlap for hd-fdd operations
US20240155607A1 (en) Configuration of multiple component carrier repetition transmissions
US20240349309A1 (en) Dci enhancements for soft resource availability indication
US20240196239A1 (en) Uplink impact on pucch scell activation delay
US20230388997A1 (en) Techniques for uplink (ul) simultaneous transmission across multi-panels (stxmp)
US20240154680A1 (en) Beam management for multi-trp operation in wireless networks
WO2022032155A1 (fr) Indication de détection directionnelle par l'intermédiaire d'une infrastructure de quasi-co-localisation (qcl)
WO2023205201A1 (fr) Configuration et synchronisation à duplexage par répartition dans le temps au niveau d'un répéteur
WO2024019887A1 (fr) Attribution de ressources en mode 1 de signaux de référence de positionnement
WO2024097299A1 (fr) Comportement d'ue lorsque des ncsgs entrent en collision avec d'autres espaces
WO2024019879A1 (fr) Configuration de groupe de ressources pour positionnement de liaison latérale
WO2022155131A1 (fr) Déclenchement et réponse d'indication de dispositif dans des réseaux sans fil

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21883979

Country of ref document: EP

Kind code of ref document: A1