WO2022031358A1 - Partitionnement de ressources de canal physique d'accès aléatoire (prach) pour une transmission de petites données (sdt) - Google Patents

Partitionnement de ressources de canal physique d'accès aléatoire (prach) pour une transmission de petites données (sdt) Download PDF

Info

Publication number
WO2022031358A1
WO2022031358A1 PCT/US2021/036010 US2021036010W WO2022031358A1 WO 2022031358 A1 WO2022031358 A1 WO 2022031358A1 US 2021036010 W US2021036010 W US 2021036010W WO 2022031358 A1 WO2022031358 A1 WO 2022031358A1
Authority
WO
WIPO (PCT)
Prior art keywords
sdt
prach
allocated
preambles
access procedure
Prior art date
Application number
PCT/US2021/036010
Other languages
English (en)
Inventor
Gang Xiong
Sergey Sosnin
Original Assignee
Intel Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Intel Corporation filed Critical Intel Corporation
Priority to CN202180047937.2A priority Critical patent/CN115868241A/zh
Publication of WO2022031358A1 publication Critical patent/WO2022031358A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access

Definitions

  • Embodiments pertain to wireless communications. Some embodiments relate to wireless networks including 3 GPP (Third Generation Partnership Project) and fifth-generation (5G) networks including 5G new radio (NR) (or 5G-NR) networks. Some embodiments pertain to physical randomaccess channel (PRACH) resource partitioning. Some embodiments pertain to small data transmission (SDT).
  • 3 GPP Third Generation Partnership Project
  • 5G fifth-generation
  • NR 5G new radio
  • PRACH physical randomaccess channel
  • SDT small data transmission
  • RRC Radio Resource Control
  • FIG. 1 A illustrates an architecture of a network, in accordance with some embodiments.
  • FIG. IB and FIG. 1C illustrate a non-roaming 5G system architecture in accordance with some embodiments.
  • FIG. 2A illustrates a 4-Step RACH procedure in accordance with some embodiments.
  • FIG. 2B illustrates a 2-Step RACH procedure in accordance with some embodiments.
  • FIG. 3 illustrates PRACH resource partitioning for EDT and legacy RACH in accordance with some embodiments.
  • FIG. 4 illustrates PRACH resource partitioning for EDT and legacy RACH in accordance with some other embodiments.
  • FIG. 5 illustrates PRACH resource partitioning for EDT and legacy RACH in accordance with some other embodiments
  • FIG. 6 illustrates PRACH resource partitioning for EDT and legacy RACH in accordance with some embodiments
  • FIG. 7 is a function block diagram of a wireless communication device in accordance with some embodiments.
  • Some embodiments are directed to a user equipment (UE) configured for operation in a fifth-generation new radio (5GNR) system (5GS).
  • UE user equipment
  • 5GNR fifth-generation new radio
  • the UE may be configured to encode a physical random-access channel (PRACH) preamble for uplink transmission and decode a random-access response (RAR) from the gNB.
  • PRACH physical random-access channel
  • RAR random-access response
  • the UE may perform the random-access procedure using different PRACH preambles to differentiate a small data transmission (SDT) from a non-SDT operation.
  • FIG. 1A illustrates an architecture of a network in accordance with some embodiments.
  • the network 140A is shown to include user equipment (UE) 101 and UE 102.
  • the UEs 101 and 102 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks) but may also include any mobile or non-mobile computing device, such as Personal Data Assistants (PDAs), pagers, laptop computers, desktop computers, wireless handsets, drones, or any other computing device including a wired and/or wireless communications interface.
  • PDAs Personal Data Assistants
  • the UEs 101 and 102 can be collectively referred to herein as UE 101 , and UE 101 can be used to perform one or more of the techniques disclosed herein.
  • Any of the radio links described herein may operate according to any exemplary' radio communication technology and/or standard.
  • LTE and LTE-Advanced are standards for wireless communications of high-speed data for UE such as mobile telephones.
  • carrier aggregation is a technology according to which multiple carrier signals operating on different frequencies may be used to 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.
  • Embodiments described herein can be used m the context, of any spectrum management scheme including, for example, dedicated licensed spectrum, unlicensed spectrum, (licensed) shared spectrum (such as Incensed 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 Incensed Shared Access
  • SAS Spectrum Access System
  • Embodiments described herein can also be applied to different Single Carrier or OFDM flavors (CP-OFDM, SC-FDMA, SC-OFDM, filter bank-based multicarrier (FBMC), OFDMA, etc.) and in particular 3GPP NR (New Radio) by allocating the OFDM carrier data bit vectors to the corresponding symbol resources.
  • CP-OFDM Single Carrier or OFDM flavors
  • SC-FDMA SC-FDMA
  • SC-OFDM filter bank-based multicarrier
  • OFDMA filter bank-based multicarrier
  • 3GPP NR New Radio
  • any of the UEs 101 and 102 can comprise an Internet-of-Things (Io' T) UE or a Cellular loT (CIoT) UE, which can comprise a network access layer designed for low-power loT applications utilizing short-lived Uli connections.
  • any of the UEs 101 and 102 can include a narrowband (NB) loT UE (e.g., such as an enhanced NB- loT (eNB-IoT) LIE and Further Enhanced (FeNB-IoT) UE).
  • NB narrowband
  • eNB-IoT enhanced NB- loT
  • 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 Sendee (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., keep-alive 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, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN.
  • UMTS Evolved Universal Mobile Telecommunications System
  • E-UTRAN Evolved Universal Mobile Telecommunications System
  • 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 the connections 103 and 104.
  • These access nodes can be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), Next Generation NodeBs (gNBs), RAN 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 transmi ssion/recepti on points (TRPs).
  • the RAN 110 may include one or more RAN nodes for providing macrocells, e.g., macro RAN node 111, and one or more RAN nodes for providing femtocells or picocells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low power (LP) RAN node 112.
  • RAN nodes 111 and 1 12 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
  • another type of RAN node another type of RAN node.
  • 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 S I interface 113 is split into two parts: the Sl-U interface 114, which carries traffic data between the RAN nodes 111 and 1 12 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 Seiwing General Packet Radio Seiwice (GPRS) Support Nodes (SGSN).
  • GPRS General Packet Radio Seiwice
  • the MMEs 121 may manage mobility embodiments 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 comm uni cation sessions.
  • the CN 120 may comprise one or several HSSs 124, depending on the number of mobile subscribers, on the capacity of die 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 routes data packets between the RAN 1 10 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 a 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 Sendees (PS) domain, LTE PS data services, etc.).
  • PS UMTS Packet Sendees
  • the P-GW 123 is shown to be communicatively coupled to an application sewer 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 Protocol Connectivity Access Network
  • HPLMN Home Public Land Mobile Network
  • V-PCRF Visited PCRF
  • VPLMN Visited Public Land Mobile Network
  • the communication network 140 A can be an loT network or a 5G network, including 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
  • AMF access and mobility function
  • UPF user plane function
  • the AMF and the UPF can be communicatively coupled to the gNBs and the NG-eNBs via NG interfaces. More specifically, in some embodiments, 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, and so forth.
  • a gNB can be a master node (MN) and NG-eNB can be a secondary node (SN) in a 5G architecture.
  • MN master node
  • SN secondary node
  • FIG. IB illustrates a non-roaming 5G system architecture in accordance with some embodiments.
  • a 5G system architecture 140B in a reference point representation. More specifically, UE 102 can be in communication with RAN 110 as well as one or more other 5G core (5GC) network entities.
  • 5GC 5G core
  • the 5G system architecture 140B includes a plurality of network functions (NFs), such as access and mobilitymanagement function (AMF) 132, session management function (SMF) 136, policy control function (PCF) 148, application function (AF) 150, user plane function (UPF) 134, network slice selection function (NSSF) 142, authentication server function (AUSF) 144, and unified data management (UDM)/home subscriber server (HSS) 146.
  • the UPF 134 can provide a connection to a data network (DN) 152, which can include, for example, operator services, Internet access, or third-party services.
  • DN data network
  • the AMF 132 can be used to manage access control and mobility and can also include network slice selection functionality.
  • the SAIF 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 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). More specifically, 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. IB), or interrogating CSCF (I-CSCF) 166B.
  • the P-CSCF 162B can be configured to be the first contact point for the UE 102 within the IM subsystem (IMS) 168B.
  • the S-CSCF 164B can be configured to handle the session states in the network, and the E-CSCF can be configured to handle certain embodiments 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. I B 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), N1 1 (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
  • 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 service-based 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), Npct 158D (a service-based interface exhibited by the PCF 148), a Nudm 158E (a service-based interface exhibited by the UDM 146), Naf 158F (a service-based interface exhibited by the AF 150), Nnrf 158C (a service-based interface exhibited by the NRF 156), Nnssf 158 A (a sendee-based interface exhibited by the NSSF 142), Nausf 158G (a service-based interface exhibited by the
  • any of the UEs or base stations described in connection with FIGS. 1 A-1C can be configured to perform the functionalities described herein.
  • NR next generation wireless communication system
  • 5G next generation wireless communication system
  • NR new radio
  • 3GPP LTE-Advanced with additional potential new Radio Access Technologies (RATs) to enrich people's lives with better, simple, and seamless wireless connectivity solutions.
  • RATs Radio Access Technologies
  • Some embodiments are directed to a user equipment (UE) configured for operation in a fifth-generation new radio (5G NR) system (5GS).
  • UE user equipment
  • 5G NR fifth-generation new radio
  • the UE may be configured to encode a physical random -access channel (PRACH) preamble for uplink transmission and decode a random-access response (RAR) from the gNB.
  • PRACH physical random -access channel
  • RAR random-access response
  • the UE may perform the random-access procedure using different PRACH preambles to differentiate a small data transmission (SDT) from a non-SDT operation.
  • SDT small data transmission
  • the UE may select a PRACH preamble from a PRACH resource allocated for SDT and transmit the selected PRACH preamble for SDT within the shared PRACH occasion.
  • the UE may select a PRACH preamble from a PRACH resource allocated for non-SDT operation and transmit the selected PRACH preamble for non-SDT operation within the shared PRACH occasion.
  • the UE may transmit a PRACH comprising the selected PRACH preamble.
  • a STD may comprise a data transmission without an established RRC connection.
  • the UE may be configured to decode signalling (e.g., an system information block (SIB) from the gNB indicating whether the shared PRACH occasion is configured for the SDT and the non- SDT operation, or whether separate PRACH occasions are configured for the SDT and the non-SDT operation.
  • SIB system information block
  • the UE may be configured to decode signalling from the gNB, the signalling allocating PRACH preambles associated with synchronization signal block (SSBs) (e.g., preambles 0-23 associated with SSB#0 and preambles 24-47 associated with SSB#1 for the shared PRACH occasion).
  • SSBs synchronization signal block
  • some of the PRACH preambles may be allocated for at least one of a legacy contention based random access (CBRA) 4-step random-access procedure and a legacy CBRA 2- step random-access procedure, some of the PRACH preambles may be allocated for contention free random access (CFRA), some of the PRACH preambles may be allocated for an SDT 4-step random-access procedure and some of the preambles may be allocated for an SDT 2-step random-access procedure.
  • CBRA contention based random access
  • CFRA contention free random access
  • one of the SDT 4-step random-access procedure and the SDT 2-step random-access procedure is used for the SDT transmission
  • one of the legacy CBRA 2-step random-access procedure, the legacy CBRA 4-step random-access procedure, and the CFRA are used for the non-SDT operation.
  • a set of the allocated preambles may be allocated for the legacy CBRA 4- step random-access procedure (e.g., preambles 0-7 associated with SSB#0 and preambles 24-31 associated with SSB#1), a set of the allocated preambles maybe allocated for the legacy CBRA 2-step random-access procedure (e.g., preambles 8-15 associated with SSB#0 and preambles 32-39 associated with SSB#I), and a set of the allocated preambles may be allocated for the CFRA (e.g., preambles 16-23 associated with SSB#0 and preambles 40-47 associated with SSB#1).
  • the legacy CBRA 4- step random-access procedure e.g., preambles 0-7 associated with SSB#0 and preambles 24-31 associated with SSB#1
  • a set of the allocated preambles maybe allocated for the legacy CBRA 2-step random-access procedure (e.g., preambles 8-15 associated
  • some of the preambles that may be allocated for the CFRA may be allocated for the SDT 4-step random-access procedure (e.g., preambles 16 - 18 associated with SSB#0 and preambles 40-42 associated with SSB#1) and some of the preambles for the CFRA may be allocated for an SDT 2-step random-access procedure (e.g., preambles 19-21 associated with SSB#0 and preambles 43-45 associated with SSB#1).
  • SDT 4-step random-access procedure e.g., preambles 16 - 18 associated with SSB#0 and preambles 40-42 associated with SSB#1
  • SDT 2-step random-access procedure e.g., preambles 19-21 associated with SSB#0 and preambles 43-45 associated with SSB#1
  • a set of the allocated preambles may be allocated for the legacy CBRA 4- step random-access procedure (e.g., preambles 0-15 associated with SSB#0 and preambles 24-39 associated with SSB#1) and a set of the allocated preambles may be allocated for the CFRA (e.g., preambles 16-23 associated with SSB#0 and preambles 40-47 associated with SSB#1).
  • the legacy CBRA 4- step random-access procedure e.g., preambles 0-15 associated with SSB#0 and preambles 24-39 associated with SSB#1
  • CFRA e.g., preambles 16-23 associated with SSB#0 and preambles 40-47 associated with SSB#1
  • some of the preambles allocated for the CFRA may be allocated for an SDT 4-step random-access procedure (e.g., preambles 16-20 associated with SSB#0 and preambles 40-44 associated with SSB#1).
  • no preambles may be allocated to the SDT 2-step random-access procedure.
  • a set of the allocated preambles may be allocated for the legacy CBRA 4- step random-access procedure (e.g., preambles 0-9 associated with SSB#0 and preambles 24-33 associated with SSB#1), a set of the allocated preambles maybe allocated for the legacy CBRA 2-step random-access procedure (e.g., preambles 10-19 associated with SSB#0 and preambles 34-43 associated with SSB#1), and a set of the allocated preambles may be allocated for the CFRA (e.g., preambles 20-23 associated with SSB#0 and preambles 44-47 associated with SSB#1.
  • the legacy CBRA 4- step random-access procedure e.g., preambles 0-9 associated with SSB#0 and preambles 24-33 associated with SSB#1
  • a set of the allocated preambles maybe allocated for the legacy CBRA 2-step random-access procedure (e.g., preambles 10-19 associated
  • some of the preambles allocated for the CBRA 4-step random-access procedure may be allocated for an SDT 4-step random-access procedure (e.g., preambles 8-9 associated with SSB#0 and preambles 32-33 associated with SSB#1) and some of the preambles for the CBRA 2-step random-access procedure may be allocated for an SDT 2-step random-access procedure (e.g., preambles 18-19 associated with SSB#0 and preambles 42-43 associated with SSB#1).
  • preambles that may be allocated for other purposes may be allocated to an SDT 4-step random-access procedure (e.g., preambles 40-43 associated with SSB#0 and preambles 48-51 associated with SSB#1) and to an SDT 2-step randomaccess procedure (e.g., preambles 44-47 associated with SSB#0 and preambles 52-55 associated with SSB#1).
  • SDT 4-step random-access procedure e.g., preambles 40-43 associated with SSB#0 and preambles 48-51 associated with SSB#1
  • SDT 2-step randomaccess procedure e.g., preambles 44-47 associated with SSB#0 and preambles 52-55 associated with SSB#
  • the preambles allocated for other purposes are preambles that are not allocated for the legacy CBRA 4-step random-access procedure (e.g., preambles 0-9), preambles that are not allocated for the legacy CBRA 2-step random-access procedure, and preambles that are not allocated for the CFRA, although the scope of the embodiments is not limited in this respect.
  • the signalling from the gNB allocates preambles associated with the SSBs (i.e., preambles 0-19 associated with SSB#0 and preambles 20-39 associated with SSBkl) for the shared PRACH occasion.
  • preambles associated with the SSBs i.e., preambles 0-19 associated with SSB#0 and preambles 20-39 associated with SSBkl
  • a set of the allocated preambles may be allocated for the legacy CBRA 4-step random-access procedure (e.g., preambles 0-7 associated with SSB#0 and preambles 20-27 associated with SSB#1)
  • a set of the allocated preambles may be allocated for the legacy CBRA 2-step random-access procedure (e.g., preambles 8-15 associated with SSB#0 and preambles 28-35 associated with SSB#1)
  • a set of the allocated preambles may be allocated for CFRA (e.g., preambles 16-19 associated with SSB#0 and preambles36-39 associated with SSB#1).
  • the UE when the separate PRACH occasions are configured, the UE may be configured to perform a 4-step random-access procedure for an SDT and perform a 2-step random-access procedure for a non- SDT operation, and the SDT comprises a transmission of data from the UE without establishment of an radio-resource control (RRC) connection with the gNB.
  • RRC radio-resource control
  • Some embodiments are directed to a non-transitory computer- readable storage medium that stores instructions for execution by processing circuitry of a user equipment (UE) configured for operation in a fifth-generation new radio (5GNR) system (5GS.
  • UE user equipment
  • 5GNR fifth-generation new radio
  • the processing circuitry is to configure the UE to encode a physical random-access channel (PRACH) preamble for uplink transmission and decode a random-access response (RAR) from the gNB.
  • PRACH physical random-access channel
  • RAR random-access response
  • the processing circuitry is to configure the UE to perform the random-access procedure using different PRACH preambles to differentiate a small (or early) data transmission (SDT) from a non-SDT operation.
  • SDT small (or early) data transmission
  • Some embodiments are directed to a generation node B (gNB) configured for operation in a fifth-generation new radio (5G NR.) system (5GS).
  • the gNB may encode signalling for transmission to a user equipment (UE) to allocate physical random-access channel (PRACH) resources to configure to UE to perform a random-access procedure using different PRACH preambles to differentiate a small data transmission (SDT) from a non- SDT operation for a shared PRACH occasion.
  • PRACH physical random-access channel
  • SDT small data transmission
  • the gNB may decode a PRACH preamble for the SDT received within the shared PRACH occasion.
  • the gNB may decode a PRACH preamble for the non-SDT operation within the shared PRACH occasion.
  • the gNB may encode a system information block (SIB) for transmission to the UE indicating whether the shared PRACH occasion is configured for both the SDT and the non-SDT operation, or whether separate PRACH occasions are configured for the SDT and the non-SDT operation.
  • SIB system information block
  • the gNB may encode the signalling allocating PRACH preambles associated with synchronization signal block (SSBs) for the shared PRACH occasion.
  • the SDT may be a transmission of data from the UE without establishment of an radio-resource control (RRC) connection with the UE.
  • RRC radio-resource control
  • RACK 4-step random access
  • UE transmits physical random-access channel (PRACH) in the uplink by selecting one preamble signature.
  • PRACH physical random-access channel
  • gNB feedbacks the random-access response (RAR) which carries timing advanced (TA) command information and uplink grant for the uplink transmission.
  • RAR random-access response
  • UE transmits Msg3 physical uplink shared channel (PUSCH) which may cany' contention resolution ID.
  • PUSCH physical uplink shared channel
  • gNB sends the contention resolution message in physical downlink shared channel (PDSCH).
  • PDSCH physical downlink shared channel
  • 2-step RACH procedure was further defined, with the motivation to allow 7 fast access and low latency uplink transmission.
  • UE transmits a PRACH preamble and associated Msg A PUSCH on a configured time and frequency resource, where MsgA PUSCH may cany at least equivalent contents of Msg3 in 4-step RACH.
  • MsgB may carry equivalent contents of Msg2 and Msg4 in 4-step RACH.
  • EDT early data transmission
  • dedicated PRACH resource may need to be reserved for EDT operation, so as to allow gNB to identify whether data transmission can be enabled for Msg3 transmission.
  • certain mechanisms may need to be defined for the PRACH resource partitioning between the support of EDT operation and legacy RACH procedure. This disclosure describes PRACH resource partitioning for the support of small data transmission.
  • dedicated PRACH resource may need to be reserved for EDT operation, so as to allow gNB to identify whether data transmission can be enabled for Msg3 transmission.
  • certain mechanisms may need to be defined for the PRACH resource partitioning between the support of EDT operation and legacy RACH procedure.
  • Embodiment of PRACH resource partitioning for the support of EDT are provided as follows:
  • separate PRACH occasions can be configured for EDT with 4-step and/or 2-step RACH from legacy 4-step and/or 2-step RACH, respectively.
  • separate parameters for synchronization signal block (SSB) to RACH occasion (RO) association can be configured for EDT with 4-step RACH and/or 2-step RACH. If not configured, the configuration from legacy 4-step RACH and/or 2-step RACH can be reused.
  • SSB synchronization signal block
  • RO RACH occasion
  • the configuration from legacy 4-step RACH and/or 2-step RACH can be reused.
  • Type-3 random access procedure indicates the EDT with 4-step RACH.
  • a UE is provided a number A? of SSZPBCH block indexes associated with one PRACH occasion and a number of contention based preambles per SS/PBCH block index per valid PRACH occasion by ssb-perRACl I -OccasionAndCB- PreamblesPerSSB-edt when provided; otherwise, by ssb-perRACH- OccasionAndCB-PreamblesPerSSB .
  • shared PRACH occasions can be configured for EDT with 4- step and/or 2-step RACH from legacy 4-step and/or 2-step RACK, respectively.
  • preambles are defined for a PRACH occasion (RO). Further, total number of preambles for contention based random access (CBRA) and contention free random access (CFRA) is configured by totalNumberOfRA-Preambles, which is further divided into N sets. Each set of PRACH preambles is associated with one synchronization signal block (SSB). Within each set of PRACH preambles associated with same SSB, 4-step CBRA RACH preambles are first mapped, and followed by CBRA 2-step RACH preambles. The remaining preambles are allocated for CFRA.
  • CBRA contention based random access
  • CFRA contention free random access
  • PRACH preambles for EDT may be allocated as a part of consecutive preambles for CFRA.
  • PRACH preamble for EDT for 4-step RACH is allocated after CBRA 2-step RACH
  • PRACH preamble for EDT for 2-step RACH is allocated after EDT for 4-step RACH.
  • PRACH preamble for EDT for 2-step RACH is allocated after CBRA 2-step RACH.
  • FIG. 3 illustrates one example of PRACH resource partitioning for EDT with 4-step and/or 2-step RACH and legacy RACH procedure.
  • 2 SSBs are associated with one RO.
  • preambles with index 0-23 are associated with SSB#0
  • preambles with index 24-47 are associated with SSB#1.
  • PRACH preamble for EDT for 4-step RACH is allocated after CBRA 2-step RACH
  • PRACH preamble for EDT tor 2-step RACH is allocated after EDT for 4- step RACH.
  • EDT for 4-step RACH is supported while EDT for 2-step RACH is not supported, the same principle may be applied, e.g., EDT with 4-step RACH is mapped after CBRA for 2-step RACH in preambles associated with one SSB.
  • Type-3 random access procedure with common configuration of PRACH occasions with Type-1 and Type-2 random access procedure if one SS/PBCH block index is mapped to consecutive valid PRACH occasions and M contention based preambles with consecutive indexes associated with the SS/PBCH block index per valid PRACH occasion start from preamble index contention based preambles with consecutive indexes associated with SS/PBCH block index per valid PRACH occasion start from preamble index where is provided by totalNumberOfRA-Preambles for Type-1 random access procedure.
  • EDT with 4-step RACH is supported, and if separate PRACH occasions for CBRA 2-step RACH are configured from legacy 4-step RACH and EDT with 4-step RACH, the EDT with 4-step RACH is mapped after CBRA 4-step RACH within preambles associated with one SSB. Note that this can apply for the case when separate RO is configured for EDT with 2-step RACH or for the case when EDT with 2-step RACH is not supported.
  • FIG. 4 illustrates one example of PRACH resource partitioning for EDT with 4-step RACH and legacy CBRA RACH procedure.
  • 2 SSBs are associated with one RO.
  • preambles with index 0-23 are associated with SSB#0 and preambles with index 24-47 are associated with SSB#1.
  • PRACH preamble for EDT for 4-step RACH is allocated after CBRA 4-step RACH.
  • Type-3 random access procedure with common configuration of PRACH occasions with Type-1 random access procedure if one SS/PBCH block index is mapped to consecutive valid PRACH occasions and M contention based preambles with consecutive indexes associated with the SS/PBCH block index per valid PRACH occasion start from preamble index R. contention based preambles with consecutive indexes associated with SS/PBCH block index per valid PRACH occasion start from preamble index is provided by totalNumberOJRA-P reambles for Type-1 random access procedure.
  • PRACH preambles when shared PRACH occasions, but different PRACH preambles can be configured for EDT with 4- step and/or 2-step RACH from legacy 4-step and/or 2-step RACH, respectively.
  • EDT for 4-step and/or 2-step RACH is allocated within the preambles for legacy CBRA 4-step and/or CBRA 2-step RACH, respectively.
  • FIG. 5 illustrates one example of PRACH resource partitioning for EDT and legacy RACH.
  • 2 SSBs are associated with one RO.
  • preambles with index 0-23 are associated with SSB#0
  • preambles with index 24-47 are associated with SSB#1 for legacy 4-step RACH and 2-step RACH.
  • preambles for EDT for 4-step and 2-step RACH are allocated within preambles for CBRA 4-step RACH and 2-step RACH, respectively.
  • EDT for 4-step RACH and/or 2- step RACH may be allocated within preamble group A and/or group B for CBRA 4-step RACH and/or 2-step RACH, respectively.
  • PRACH preambles when shared PRACH occasions, but different PRACH preambles can be configured for EDT with 4- step and/or 2-step RACH from legacy 4-step and/or 2-step RACH, respectively.
  • EDT for 4-step and/or 2-step RACH is allocated within the preambles for other purpose, e.g., from totalNumberOjRA-Preambles to 63 within a RO.
  • the preambles for other purpose are partitioned into multiple sets, where each set is associated with an SSB.
  • the number of sets is determined by ssb-perRAC ⁇ i-OccasionAudC ⁇ B-PreamblesPerSSB or ssb- perRACH-OccasionAndCB-PreamblesPerSSB-msgA.
  • EDT for 2-step RACH is allocated after EDI' for 4-step RACH. If EDT for 2-step RACH is not configured or not supported, only EDT for 4-step RACH is allocated within each set.
  • FIG. 6 illustrates one example of PRACH resource partitioning for EDT and legacy RACH.
  • 2 SSBs are associated with one RO.
  • preambles with index 0-19 are associated with SSB#0
  • preambles with index 20-39 are associated with SSB#1 for legacy 4-step RACH and 2-step RACH.
  • preambles for EDT for 4-step and 2-step RACH are allocated within preambles for other purposes, e.g., from index 40-63.
  • two sets of preambles are allocated within the preambles for other purposes, where each set is associated with an SSB. Within each set, EDT for 2-step RACH is allocated after EDT for 4-step RACH.
  • preamble group A and group B when preamble group A and group B is configured for EDT with 4-step and 2-step RACH, additional PRACH resource partitioning may be applied based on the aforementioned options.
  • preamble for EDT with 4-step RACH is further divided into preamble group A and group B, where preamble group A is allocated before preamble group B for EDT with 4-step RACK.
  • the same mechanism can be applied for EDT with 2-step RACH.
  • FIG. 7 illustrates a functional block diagram of a wireless communication device in accordance with some embodiments.
  • the communication device 700 may also be suitable for use as a handheld device (e.g., a UE), a base station (e.g., a gNB), a mobile device, a cellular telephone, a smartphone, a tablet, a netbook, a wareless terminal, a laptop computer, a wearable computer device, a femtocell, a high data rate (HDR) subscriber station, an access point, an access terminal, or other personal communication system (PCS) device.
  • a handheld device e.g., a UE
  • a base station e.g., a gNB
  • a mobile device e.g., a cellular telephone
  • smartphone e.g., a smartphone
  • a tablet e.g., a netbook
  • a wareless terminal e.g., a laptop computer
  • the communication device 700 may include communications circuitry 702 and a transceiver 710 for transmitting and receiving signals to and from other communication stations using one or more antennas 701.
  • the communications circuitry' 702 may include circuitry that can operate the physical layer (PHY) communications and/or medium access control (MAC) communications for controlling access to the wireless medium, and/or any other communications layers for transmitting and receiving signals.
  • the communication device 700 may also include processing circuitry' 706 and memory' 708 arranged to perform the operations described herein.
  • the communications circuitry' 702 and the processing circuitry 706 may be configured to perform operations detailed in the above figures, diagrams, and flows.
  • the communications circuitry 702 may be arranged to contend for a wireless medium and configure frames or packets for communicating over the wireless medium.
  • the communications circuitry 702 may be arranged to transmit and receive signals.
  • the communications circuitry' 702 may also include circuitry' for modulation/demodulation, upconversion/dowmconversion, filtering, amplification, etc.
  • the processing circuitry' 706 of the communication device 700 may include one or more processors.
  • two or more antennas 701 may be coupled to the communications circuitry 702 arranged for sending and receiving signals.
  • the memory' 708 may store information for configuring the processing circuitry' 706 to perform operations for configuring and transmitting message frames and performing the various operations described herein.
  • the memory 708 may include any type of memory', including n on-transitory memory', for storing information in a form readable by a machine (e.g., a computer).
  • the memory 708 may include a computer-readable storage device, read-only memory' (ROM), randomaccess memory' (RAM), magnetic disk storage media, optical storage media, flash-memory' devices and other storage devices and media.
  • the communication device 700 may be part of a portable wireless communication device, such as a personal digital assistant (PDA), a laptop or portable computer with wireless communication capability, a w'eb tablet, a wireless telephone, a smartphone, a wireless headset, a pager, an instant messaging device, a digital camera, an access point, a television, a medical device (e.g., a heart rate monitor, a blood pressure monitor, etc.), a wearable computer device, or another device that may receive and/or transmit information wirelessly.
  • PDA personal digital assistant
  • a laptop or portable computer with wireless communication capability such as a portable personal digital assistant (PDA), a laptop or portable computer with wireless communication capability, a w'eb tablet, a wireless telephone, a smartphone, a wireless headset, a pager, an instant messaging device, a digital camera, an access point, a television, a medical device (e.g., a heart rate monitor, a blood pressure monitor, etc.), a wearable computer device, or another device that may
  • the communication device 700 may include one or more antennas 701.
  • the antennas 701 may include one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas, or other types of antennas suitable for transmission of RF signals.
  • a single antenna with multiple apertures may be used instead of two or more antennas.
  • each aperture may be considered a separate antenna.
  • MIMO multiple-input multiple-output
  • the antennas may be effectively separated for spatial diversity and the different channel characteristics that may result between each of the antennas and the antennas of a transmitting station.
  • the communication device 700 may include one or more of a keyboard, a display , a non-volatile memory' port, multiple antennas, a graphics processor, an application processor, speakers, and other mobile device elements.
  • the display may be an LCD screen including a touch screen.
  • the communication device 700 is illustrated as having several separate functional elements, tw'o or more of the functional elements may be combined ami may be implemented by combinations of software-configured elements, such as processing elements including digital signal processors (DSPs), and/or other hardware elements.
  • DSPs digital signal processors
  • some elements may include one or more microprocessors, DSPs, field-programmable gate array s (FPGAs), application specific integrated circuits (ASICs), radio-frequency integrated circuits (RFICs) and combinations of various hardware and logic circuitry' for performing at least the functions described herein.
  • the functional elements of the communication device 700 may refer to one or more processes operating on one or more processing elements.
  • Example 1 may include a method of wireless communication for a fifth generation (5G) or new radio (NR) system, the method comprising: [00971 Configuring, by gNodeB, separate physical random-access channel (PRACH) preambles for early data transmission (EDT) using 2-step random access (RACH) procedure and/or 4-step RACH procedure.
  • 5G fifth generation
  • NR new radio
  • Example 2 may include the method of example 1 or some other example herein, wherein separate PRACH occasions can be configured for EDT with 4-step and/or 2-step RACH from legacy 4-step and/or 2-step RACH, respectively;
  • Example 3 may include the method of example 1 or some other example herein, wherein shared PRACH occasions, but different PRACH preambles can be configured for EDT with 4-step and/or 2-step RACH from legacy 4-step and/or 2-step RACH, respectively.
  • Example 4 may include the method of example 3 or some other example herein, wherein when EDT is configured using 4-step RACH and/or 2- step RACH, PRACH preambles for EDT may be allocated as a part of consecutive preambles for contention free random access (CFRA)
  • CFRA contention free random access
  • Example 5 may include the method of example 3 or some other example herein, wherein within the set of preambles associated with a same synchronization signal block (SSB), PRACH preamble for EDT for 4-step RACH is allocated after contention based random access (CBRA) 2-step RACH, while PRACH preamble for EDT for 2-step RACH is allocated after EDT for 4- step RACH.
  • SSB synchronization signal block
  • Example 6 may include the method of example 3 or some other example herein, wherein if EDT with 4-step RACH is supported, and if separate PRACH occasions for CBRA 2-step RACH are configured from legacy 4-step RACH and EDT with 4-step RACH, the EDT with 4-step RACH is mapped after CBRA 4-step RACH within preambles associated with one SSB
  • Example 7 may include the method of example 3 or some other example herein, wherein EDT for 4-step and/or 2-step RACH is allocated within the preambles for legacy CBRA 4-step and/or CBRA 2-step RACH, respectively.
  • Example 8 may include the method of example 7 or some other example herein, wherein when preamble group A and group B is configured for CBRA 4-step and 2-step RACH, EDT for 4-step RACH and/or 2-step RACH may be allocated within preamble group A and/or group B for CBRA 4-step RACH and/or 2-step RACH, respectively,
  • Example 9 may include the method of example 3 or some other example herein, wherein EDT for 4-step and/or 2-step RACH is allocated within the preambles for other purpose, e.g., from total NumberOfRA-Preambles to 63 within a RO.
  • Example 10 may include the method of example 9 or some other example herein, wherein preambles for other purpose are partitioned into multiple sets, where each set is associated with an SSB.
  • Example 11 may include the method of example 9 or some other example herein, wherein within each set of preambles, EDT for 2-step RACH is allocated after EDT for 4-step RACH; wherein if EDT for 2-step RACH is not configured or not supported, only EDT for 4-step RACH is allocated within each set,
  • Example 12 may include the method of example 1 or some other example herein, wherein when preamble group A and group B is configured for EDT with 4-step and 2-step RACH, additional PRACH resource partitioning may be applied based on the aforementioned options.
  • Example 13 may include the method of example 12 or some other example herein, wherein preamble for EDT with 4-step RACH is further divided into preamble group A and group B, where preamble group A is allocated before preamble group B for EDT with 4-step RACH.
  • Example 14 may include a method comprising:
  • the PRACH preamble for transmission to a gNB as part of a random-access channel (RACH) procedure.
  • RACH random-access channel
  • Example 15 may include the method of example 14 or some other example herein, wherein the RACH procedure is a 2-step RACH procedure and/or a 4-step RACH procedure.
  • Example 16 may include the method of example 14-15 or some other example herein, wherein the PRACH preamble for EDT is different than a PRACH preamble for normal (e.g., non-EDT) communication.
  • Example 17 may include the method of example 14-16 or some other example herein, wherein the PRACH preamble for EDT is allocated as a part of consecutive preambles for contention free random access (CFRA)
  • Example 18 may include the method of example 14-16 or some other example herein, wherein within a set of PRACH preambles associated with a same synchronization signal block (SSB), the PRACH preamble for EDT for 4-step RACH is allocated after contention based random access (CBRA) 2-step RACH, while the PRACH preamble for EDT for 2-step RACH is allocated after EDT for 4-step RACH.
  • SSB synchronization signal block
  • CBRA contention based random access
  • Example 19 may include the method of example 14-16 or some other example herein, wherein if EDT with 4-step RACH is supported, and if separate PRACH occasions for CBRA 2-step RACH are configured from legacy 4-step RACH and EDT with 4-step RACH, the EDT with 4-step RACH is mapped after CBRA 4-step RACH within preambles associated with one SSB
  • Example 20 may include the method of example 14-16 or some other example herein, wherein EDT for 4-step and/or 2-step RACH is allocated within the preambles for legacy CBRA 4-step and/or CBRA 2-step RACH, respectively.
  • Example 21 may include the method of example 20 or some other example herein, wherein when preamble group A and group B is configured for CBRA 4-step and 2-step RACH, EDT for 4-step RACH and/or 2-step RACK is allocated within preamble group A and/or group B for CBRA 4-step RACH and/or 2-step RACH, respectively.
  • Example 22 may include the method of example 14-16 or some other example herein, wherein EDT for 4-step and/or 2-step RACH is allocated within one or more RACH preambles that are used for another purpose, e.g., from totalNumberOfRA-Preambles to 63 within a RACH occasion (RO).
  • EDT for 4-step and/or 2-step RACH is allocated within one or more RACH preambles that are used for another purpose, e.g., from totalNumberOfRA-Preambles to 63 within a RACH occasion (RO).
  • Example 23 may include the method of example 22 or some other example herein, wherein the one or more RACH preambles for another purpose are partitioned into multiple sets, where each set is associated with an SSB.
  • Example 24 may include the method of example 22 or some other example herein, wherein within each set of preambles, EDT for 2-step RACH is allocated after EDT for 4-step RACH; wherein if EDT for 2-step RACH is not configured or not supported, only EDT for 4-step RACH is allocated within each set.
  • Example 25 may include the method of example 14-16 or some other example herein, wherein when the configuration information includes a preamble group A and preamble group B for EDT with 4-step and 2-step RACH, respectively, and wherein additional PRACH resource partitioning is applied.
  • Example 26 may include the method of example 25 or some other example herein, wherein the preamble group A for EDT with 4-step RACH is further divided into preamble group C and preamble group D, wherein preamble group C is allocated before preamble group D for EDT with 4-step RACH.

Landscapes

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

Abstract

Un équipement utilisateur (UE) configuré pour fonctionner dans un système (5 GS) New Radio de cinquième génération (5G NR) doit effectuer une procédure d'accès aléatoire avec un nœud B de nouvelle génération (gNB). L'UE peut être configuré pour coder un préambule de canal physique d'accès aléatoire (PRACH) pour une transmission en liaison montante et décoder une réponse d'accès aléatoire (RAR) provenant du gNB. Pour une occasion de PRACH partagé (RO), l'UE peut effectuer la procédure d'accès aléatoire en utilisant différents préambules PRACH pour différencier une transmission de petites données (SDT) d'une opération non SDT.
PCT/US2021/036010 2020-08-05 2021-06-04 Partitionnement de ressources de canal physique d'accès aléatoire (prach) pour une transmission de petites données (sdt) WO2022031358A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202180047937.2A CN115868241A (zh) 2020-08-05 2021-06-04 用于小数据传输sdt的物理随机接入信道prach资源划分

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202063061699P 2020-08-05 2020-08-05
US63/061,699 2020-08-05

Publications (1)

Publication Number Publication Date
WO2022031358A1 true WO2022031358A1 (fr) 2022-02-10

Family

ID=80118381

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2021/036010 WO2022031358A1 (fr) 2020-08-05 2021-06-04 Partitionnement de ressources de canal physique d'accès aléatoire (prach) pour une transmission de petites données (sdt)

Country Status (2)

Country Link
CN (1) CN115868241A (fr)
WO (1) WO2022031358A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190364600A1 (en) * 2017-05-05 2019-11-28 Telefonaktieboiaget Lm Ericsson (Publ) Method and Device for Data Transmission
WO2020088097A1 (fr) * 2018-10-30 2020-05-07 Qualcomm Incorporated Configuration pour transmission de données de petite taille

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190364600A1 (en) * 2017-05-05 2019-11-28 Telefonaktieboiaget Lm Ericsson (Publ) Method and Device for Data Transmission
WO2020088097A1 (fr) * 2018-10-30 2020-05-07 Qualcomm Incorporated Configuration pour transmission de données de petite taille

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
HUAWEI: "Report of the Email discussion [101#57][NB-IoT/MTC R15] EDT remaining issues", 3GPP DRAFT; R2-1805078 REPORT OF E-MAIL DISCUSSION [101#57] ON EDT REMAINING ISSUES, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Sanya, China; 20180416 - 20180420, 5 April 2018 (2018-04-05), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051414947 *
INTEL CORPORATION: "Report on [106#65][R16 NB-IoT/eMTC] CP MT-EDT", 3GPP DRAFT; R2-1910386 REPORT ON EMAIL DISCUSSION MT CP-EDT, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Prague, the Czech Republic; 20190826 - 20190830, 16 August 2019 (2019-08-16), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051768165 *
NOKIA, NOKIA SHANGHAI BELL: "On 2-step RACH Procedure", 3GPP DRAFT; R1-1908342 ON 2-STEP RACH PROCEDURE, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Prague, Czech Republic; 20190826 - 20190830, 16 August 2019 (2019-08-16), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051764951 *

Also Published As

Publication number Publication date
CN115868241A (zh) 2023-03-28

Similar Documents

Publication Publication Date Title
US11457511B2 (en) Enhanced downlink semi-persistent scheduling (SPS)
US11825561B2 (en) Channel access sharing during a random access procedure for NR-unlicensed networks
US11838915B2 (en) One-shot feedback and SCell dormancy behavior in 5G NR networks
US12047950B2 (en) Aperiodic CSI-RS resource set triggering by DCI with aperiodic triggering offset
EP4201007A1 (fr) Indication de taille de faisceau de répétitions pour des transmissions de liaison montante dans un réseau nr 5g
EP4275381A1 (fr) Prise en charge de capacité d'ue pour de multiples configurations d'intervalle de mesure simultanées et indépendantes
JP2024519433A (ja) より高い搬送波周波数動作のためのサーチ空間セットにおけるマルチスロットｐｄｃｃｈモニタリング
US20240098539A1 (en) Network controlled small gap (ncsg) operations for new radio (nr)
US20210250977A1 (en) Generation node b (gnb) configured for slot-less operation at frequencies above a 52.6 ghz carrier frequency
WO2022146637A1 (fr) Capacité d'équipement utilisateur (ue) pour un nombre maximal d'instances d'intervalle d'un motif d'intervalles simultanés multiples
US20240163868A1 (en) Configured grant based small data transmission (cg-sdt) in multibeam operation
US20220095381A1 (en) Determination of rnti for performing rach procedure at carrier frequencies above 52.6 ghz
WO2023154275A1 (fr) Commande de puissance de transmission pour groupage de dmrs pour amélioration de couverture
WO2022031617A1 (fr) Indication dmrs dans des créneaux spéciaux permettant des opérations de spectre non appariées
WO2022031358A1 (fr) Partitionnement de ressources de canal physique d'accès aléatoire (prach) pour une transmission de petites données (sdt)
US20230413336A1 (en) Frequency hopping for multiple prach transmissions of a prach repetition
EP3908050A1 (fr) Aspects de strate de non-accès sur la restriction de l'utilisation d'une couverture améliorée dans des systèmes de cinquième génération
US20240014995A1 (en) Timing for non-overlapping sub-band full duplex (sbfd) operations in 5g nr
US20240172243A1 (en) Sounding reference signal (srs) transmissions triggered via downlink control information (dci) formats without scheduling information
US20240114507A1 (en) Multi-tti scheduling of pdsch and pusch by dci
WO2022031743A1 (fr) Configuration de canal prach et détermination d'identifiant rnti pour une fréquence supérieure à 52,6 ghz
WO2022087276A1 (fr) Commutation bwp basée sur le rrc pour les porteuses composantes uniques et multiples
WO2024211692A1 (fr) Coexistence de transmissions de liaison latérale nr (new radio) avec des transmissions de liaison latérale lte (évolution à long terme) dans la même porteuse
WO2023172418A1 (fr) Opération de partie de bande passante (bwp) et gestion de collision pour des communications en duplex intégral
EP4201097A1 (fr) Équipement utilisateur configurable avec plusieurs motifs d'intervalle de mesure

Legal Events

Date Code Title Description
DPE2 Request for preliminary examination filed before expiration of 19th month from priority date (pct application filed from 20040101)
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21852607

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

Country of ref document: EP

Kind code of ref document: A1