[go: up one dir, main page]

WO2020092530A1 - Attribution de ressources de prach pour nr sans licence - Google Patents

Attribution de ressources de prach pour nr sans licence Download PDF

Info

Publication number
WO2020092530A1
WO2020092530A1 PCT/US2019/058817 US2019058817W WO2020092530A1 WO 2020092530 A1 WO2020092530 A1 WO 2020092530A1 US 2019058817 W US2019058817 W US 2019058817W WO 2020092530 A1 WO2020092530 A1 WO 2020092530A1
Authority
WO
WIPO (PCT)
Prior art keywords
lbt
transmission
prach
gnb
sub
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/US2019/058817
Other languages
English (en)
Inventor
Lopamudra Kundu
Yongjun Kwak
Bishwarup Mondal
Dae Won Lee
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Intel Corp
Original Assignee
Intel Corp
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 Corp filed Critical Intel Corp
Publication of WO2020092530A1 publication Critical patent/WO2020092530A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/14—Spectrum sharing arrangements between different networks
    • 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
    • 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
    • H04W74/0838—Random access procedures, e.g. with 4-step access using contention-free random access [CFRA]

Definitions

  • Embodiments pertain to radio access networks (RANs). Some embodiments relate to cellular networks, including Third Generation Partnership Project (3GPP) Long Term Evolution (LTE), 4 th generation (4G) and 5 th generation (5G) New Radio (NR) (or next generation (NG)) networks. Some embodiments relate to unlicensed band use in such networks.
  • 3GPP Third Generation Partnership Project
  • LTE Long Term Evolution
  • 4G 4 th generation
  • 5G 5 th generation
  • NR New Radio
  • NG next generation
  • embodiments relate to allocation of physical random access channel (PRACH) resources when the unlicensed band is used.
  • PRACH physical random access channel
  • FIG. 1 illustrates combined communication system in accordance with some embodiments.
  • FIG. 2 illustrates a block diagram of a communication device in accordance with some embodiments.
  • FIG. 3 A illustrates PRACH transmission in accordance with some embodiments.
  • FIG. 3B illustrates another PRACH transmission in accordance with some embodiments.
  • FIG. 3C illustrates another PRACH transmission in accordance with some embodiments.
  • FIG. 4A illustrates PRACH transmission in accordance with some embodiments.
  • FIG. 4B illustrates another PRACH transmission in accordance with some embodiments.
  • FIG. 4C illustrates another PRACH transmission in accordance with some embodiments.
  • FIG. 5 illustrates a PRACH triggering mechanism in accordance with some embodiments.
  • FIG. 6 illustrates multiplexing of PRACH transmissions in accordance with some embodiments.
  • FIG. 1 illustrates a combined communication system in accordance with some embodiments.
  • the system 100 includes 3GPP LTE/4G and NG network functions.
  • a network function can be implemented as a discrete network element on a dedicated hardware, as a software instance running on dedicated hardware, or as a virtualized function instantiated on an appropriate platform, e.g., dedicated hardware or a cloud infrastructure.
  • the evolved packet core (EPC) of the LTE/4G network contains protocol and reference points defined for each entity.
  • These core network (CN) entities may include a mobility management entity (MME) 122, serving gateway (S-GW) 124, and paging gateway (P-GW) 126.
  • MME mobility management entity
  • S-GW serving gateway
  • P-GW paging gateway
  • the TIE 102 may be connected to either an access network or radio access network (RAN) 110 and/or may be connected to the NG-RAN 130 (gNB) or an Access and Mobility Function (AMF) 142.
  • the RAN 110 may be an eNB or a general non-3GPP access point, such as that for Wi-Fi.
  • the NG core network may contain multiple network functions besides the AMF 112.
  • the TIE 102 may generate, encode and perhaps encrypt uplink transmissions to, and decode (and decrypt) downlink transmissions from, the RAN 110 and/or gNB 130 (with the reverse being true by the RAN 1 lO/gNB 130).
  • the network functions may include a ETser Plane Function (EIPF)
  • EIPF ETser Plane Function
  • SMS Session Management Function
  • Policy Control Function Policy Control Function
  • PCF Policy and Charging Function
  • AF Application Function
  • AETSF ETser Data Management
  • ETDM ETser Data Management
  • the AMF 142 may provide ETE-based authentication, authorization, mobility management, etc.
  • the AMF 142 may be independent of the access technologies.
  • the SMF 144 may be responsible for session management and allocation of IP addresses to the UE 102.
  • the SMF 144 may also select and control the UPF 146 for data transfer.
  • the SMF 144 may be associated with a single session of the UE 102 or multiple sessions of the UE 102. This is to say that the EE 102 may have multiple 5G sessions. Different SMFs may be allocated to each session. The use of different SMFs may permit each session to be individually managed. As a consequence, the functionalities of each session may be independent of each other.
  • the EIPF 126 may be connected with a data network, with which the EE 102 may communicate, the EE 102 transmitting uplink data to or receiving downlink data from the data network.
  • the AF 148 may provide information on the packet flow to the PCF 132 responsible for policy control to support a desired QoS.
  • the PCF 132 may set mobility and session management policies for the EE 102. To this end, the PCF 132 may use the packet flow information to determine the appropriate policies for proper operation of the AMF 142 and SMF 144.
  • the AUSF 152 may store data for EE authentication.
  • the EE)M 128 may similarly store the EE subscription data.
  • the gNB l30 may be a standalone gNB or a non- standalone gNB, e.g., operating in Dual Connectivity (DC) mode as a booster controlled by the eNB 110 through an X2 or Xn interface. At least some of functionality of the EPC and the NG CN may be shared (alternatively, separate components may be used for each of the combined component shown).
  • the eNB 110 may be connected with an MME 122 of the EPC through an Sl interface and with a SGW 124 of the EPC 120 through an Sl-U interface.
  • the MME 122 may be connected with an HSS 128 through an S6a interface while the EE)M is connected to the AMF 142 through the N8 interface.
  • the SGW 124 may connected with the PGW 126 through an S5 interface (control plane PGW-C through S5-C and user plane PGW-U through S5-U).
  • the PGW 126 may serve as an IP anchor for data through the internet.
  • the NG CN may contain an AMF 142, SMF 144 and
  • the eNB 110 and gNB 130 may communicate data with the SGW 124 of the EPC 120 and the UPF 146 of the NG CN.
  • the MME 122 and the AMF 142 may be connected via the N26 interface to provide control information there between, if the N26 interface is supported by the EPC 120.
  • the gNB 130 is a standalone gNB, the 5G CN and the
  • FIG. 2 illustrates a block diagram of a communication device in accordance with some embodiments.
  • the communication device may be a UE (including an IoT device and NB-IoT device), eNB, gNB or other equipment used in the 4G/LTE or NG network environment.
  • the communication device 200 may be a specialized computer, a personal or laptop computer (PC), a tablet PC, a mobile telephone, a smart phone, a network router, switch or bridge, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine.
  • the communication device 200 may be embedded within other, non-communication-based devices such as vehicles and appliances.
  • Examples, as described herein, may include, or may operate on, logic or a number of components, modules, or mechanisms.
  • Modules and components 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 machine readable medium.
  • the software when executed by the underlying hardware of the module, causes the hardware to perform the specified operations.
  • module (and“component”) 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.
  • modules are temporarily configured, each of the modules need not be
  • the modules comprise a general-purpose hardware processor configured using software
  • the general-purpose hardware processor may be configured as respective different modules at different times.
  • 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 200 may include a hardware processor 202 (e.g., a central processing unit (CPU), a GPU, a hardware processor core, or any combination thereof), a main memory 204 and a static memory 206, some or all of which may communicate with each other via an interlink (e.g., bus) 208.
  • the main memory 204 may contain any or all of removable storage and non-removable storage, volatile memory or non-volatile memory.
  • the communication device 200 may further include a display unit 210 such as a video display, an alphanumeric input device 212 (e.g., a keyboard), and a user interface (UI) navigation device 214 (e.g., a mouse).
  • a hardware processor 202 e.g., a central processing unit (CPU), a GPU, a hardware processor core, or any combination thereof
  • main memory 204 may contain any or all of removable storage and non-removable storage, volatile memory or non-volatile memory.
  • the communication device 200 may further
  • the display unit 210, input device 212 and UI navigation device 214 may be a touch screen display.
  • the communication device 200 may additionally include a storage device (e.g., drive unit) 216, a signal generation device 218 (e.g., a speaker), a network interface device 220, and one or more sensors, such as a global positioning system (GPS) sensor, compass, accelerometer, or other sensor.
  • GPS global positioning system
  • the communication device 200 may further include an output controller, 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 216 may include a non-transitory machine readable medium 222 (hereinafter simply referred to as machine readable medium) on which is stored one or more sets of data structures or instructions 224 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein.
  • the instructions 224 may also reside, successfully or at least partially, within the main memory 204, within static memory 206, and/or within the hardware processor 202 during execution thereof by the communication device 200.
  • the machine readable medium 222 is illustrated as a single medium, the term "machine 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 224.
  • machine readable medium may include any medium that is capable of storing, encoding, or carrying instructions for execution by the communication device 200 and that cause the communication device 200 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 machine-readable medium examples may include solid-state memories, and optical and magnetic media.
  • machine-readable media may include: non-volatile memory, such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; Random Access Memory (RAM); and CD-ROM and DVD-ROM disks.
  • non-volatile memory such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flash memory devices
  • EPROM Electrically Programmable Read-Only Memory
  • EEPROM Electrically Erasable Programmable Read-Only Memory
  • flash memory devices e.g., Electrically Erasable Programmable Read-Only Memory (EEPROM)
  • EPROM Electrically Programmable Read-Only Memory
  • EEPROM Electrically Erasable Programmable Read-Only Memory
  • flash memory devices e.g
  • the instructions 224 may further be transmitted or received over a communications network using a transmission medium 226 via the network interface device 220 utilizing any one of a number of transfer protocols (e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (EIDP), hypertext transfer protocol (HTTP), etc.).
  • Example communication networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), mobile telephone networks (e.g., cellular networks), Plain Old Telephone (POTS) networks, and wireless data networks. Communications over the networks may include one or more different protocols, such as Institute of Electrical and Electronics
  • Wi-Fi Wi-Fi
  • WiMax WiMax
  • IEEE 802.15.4 family of standards
  • LTE Long Term Evolution
  • the network interface device 220 may include one or more physical jacks (e.g., Ethernet, coaxial, or phone j acks) or one or more antennas to connect to the transmission medium 226.
  • physical jacks e.g., Ethernet, coaxial, or phone j acks
  • antennas to connect to the transmission medium 226.
  • the communication device 200 may be an IoT device (also referred to as a“Machine-Type Communication device” or“MTC device”), a narrowband IoT (NB-IoT) device, or a non-IoT device (e.g., smart phone, vehicular UE), any which may communicate with the core network via the eNB or gNB shown in FIG. 1.
  • the communication device 200 may be an IoT device (also referred to as a“Machine-Type Communication device” or“MTC device”), a narrowband IoT (NB-IoT) device, or a non-IoT device (e.g., smart phone, vehicular UE), any which may communicate with the core network via the eNB or gNB shown in FIG. 1.
  • the communication device 200 may be an IoT device (also referred to as a“Machine-Type Communication device” or“MTC device”), a narrowband IoT (NB-IoT) device, or a non-Io
  • the communication device 200 is IoT device, in some embodiments, the
  • the communication device 200 may be limited in memory, size, or functionality, allowing larger numbers to be deployed for a similar cost to smaller numbers of larger devices.
  • the communication device 200 may, in some embodiments, be a virtual device, such as an application on a smart phone or other computing device.
  • UEs typically operate in the licensed spectrum.
  • NR (and LTE) systems may operate in the unlicensed spectrum (called NR-unlicensed or NR-U).
  • NR operation in unlicensed spectrum includes, but is not limited to, Carrier Aggregation (CA) based on Licensed Assisted Access (LAA)/enhanced LAA (eLAA) systems, NR operation in the unlicensed spectrum via dual connectivity (DC), and standalone NR (in which the NR networks may or may not be supported by a 4G structure) and LTE systems in the unlicensed spectrum.
  • CA Carrier Aggregation
  • LAA Licensed Assisted Access
  • eLAA enhanced LAA
  • DC dual connectivity
  • standalone NR in which the NR networks may or may not be supported by a 4G structure
  • communication devices such as base stations (gNBs) and EEs may determine channel availability via energy detection before transmitting data on the channel. For example, the gNBs and EEs may determine channel availability via energy detection before transmitting data on the channel. For example, the gNBs and EEs may determine channel availability via energy detection before transmitting data on the channel.
  • gNBs base stations
  • EEs may determine channel availability via energy detection before transmitting data on the channel.
  • the communication device may determine that the channel is occupied through a predetermined amount of energy being present in the channel or via a change in a received signal strength indication (RSSI).
  • the communication device may detect the presence of a specific sequence, such as a preamble transmitted prior to a data transmission, that indicates use of the channel.
  • the unlicensed channel may be reserved using a reservation signal to prevent WiFi signals from initiating transmission until the next frame boundary event.
  • communication devices may contend for access to the unlicensed frequency band by performing clear channel assessment (CCA) and Listen-Before-Talk (LBT) procedures, and subsequently transmitting during transmission
  • CCA clear channel assessment
  • LBT Listen-Before-Talk
  • TxOPs TxOP opportunities
  • the LBT-based channel access mechanism may thus provide a
  • CSMA/CA Collision Avoidance
  • Any node that intends to transmit in unlicensed spectrum may first perform a channel sensing operation (of, say 25ms) before initiating any transmission.
  • An additional random back-off mechanism may be adopted (in category 4 LBT) to avoid collisions when more than one node senses the channel as idle (using, e.g., average energy detection within the channel) and transmits simultaneously.
  • NR-based unlicensed access may also use LBT based channel access mechanisms. Due to LBT, the performance of uplink (UL) transmission, for example, the preamble transmission over the PRACH can be impacted when the UE operates in unlicensed spectrum. Due to the importance of PRACH transmissions, in previous unlicensed band use (LAA operation) the PRACH was always transmitted on the licensed band. When the PRACH preamble is sent on the unlicensed band, LBT is performed by the UE before the PRACH preamble can be transmitted. To increase reliability of PRACH transmission, time/frequency domain PRACH resource allocation scheme for reliability enhancements are disclosed to cope with LBT in the NR-unlicensed system.
  • the NR-U operating bandwidth may be an integer multiple of 20 MHz.
  • LBT can be performed by the UE in frequency units of 20 MHz.
  • the transmissions may take one of several different embodiments.
  • the gNB may provide the resource allocation rules for PRACH transmission to each UE as indicated below.
  • multiple frequency domain resources can be configured for the UE for PRACH preamble transmission.
  • the frequency domain resources may each correspond to a different configured uplink bandwidth part (UL BWP).
  • Each BWP may be approximately the dimension of an LBT sub-band (e.g. 20 MHz) or contained within an LBT sub-band (subject to guard PRBs) and hence subject to a single LBT.
  • the UE may dynamically select one of the configured BWPs as initial active BWP for PRACH preamble transmission as per the aggregated LBT outcome.
  • FIGS. 3A-3C illustrate a PRACH transmission in accordance with some embodiments.
  • FIGS. 3A-3C illustrate dynamic activation of initial active LIL BWP for PRACH transmission based on LBT outcome.
  • the UE may have successful LBT outcome (i.e., have sensed that the channel is clear) over one of the configured BWPs.
  • the UE may select this BWP as initial active UL BWP among the set of configured BWPs for PRACH transmission.
  • the UE may sense each BWP simultaneously or may sense the BWPs consecutively.
  • the UE may have a successful LBT outcome over more than one configured BWP (say, over M configured BWPs where, M>l).
  • the BWPs having the successful LBT outcome may, as shown in FIG. 3B, be contiguous in the frequency domain.
  • the gNB may indicate the manner of selection through a system information block (SIB) transmission, such as SIB2.
  • SIB system information block
  • the gNB may indicate that the UE is to select the BWP with the lowest index or the highest index.
  • the implementation may be left up to the UE to decide.
  • the UE may randomly select any one BWP as active among the M configured BWPs over which LBT succeeded and employ the selected BWP for PRACH transmission.
  • the gNB may, of course, sense all of the BWPs using blind decoding to determine whether the UE has transmitted the PRACH in any of the BWPs.
  • the UE may have a successful
  • the UE may, being limited to a 20MHz PRACH transmission, again randomly select a single BWP among these M non-contiguous UL BWPs over which LBT succeeded.
  • the selected BWP may then be used as an initially active UL BWP for PRACH transmission.
  • the UE may be configured with multiple BWPs and may activate multiple BWPs if LBT is successful on more than one configured BWP. In this case, as above, the UE may be limited to select a single BWP out of the multiple activated UL BWPs over which LBT succeeded and choose the corresponding PRACH frequency resource for preamble transmission.
  • the UE may choose more than one or all active UL BWPs on which LBT succeeded (which may be contiguous or non-contiguous) for PRACH transmission. Note that non-contiguous PRACH transmission may encounter difficulties due to filtering to avoid transmission of noise in the channels determined not to have a successful LBT outcome during PRACH transmission.
  • FIGS. 4A-4C illustrate PRACH transmission in accordance with some embodiments.
  • the UE may be configured with an initial active UL BWP > 20 MHz and multiple PRACH resources may be configured within that single active UL BWP.
  • Each PRACH resource may correspond to a 20 MHz LBT sub-band.
  • the UE may dynamically switch PRACH transmission bandwidth based on the aggregated LBT outcome and, as shown in FIGS. 4A-4C, select corresponding frequency domain resources for PRACH transmission.
  • the UE may have a successful LBT outcome over more than one LBT sub-band (say, M sub-bands, with M >1) within the active UL BWP.
  • the sub-bands may be contiguous in the frequency domain.
  • the UE may randomly select any one sub- band from these M sub-bands for PRACH transmission, as shown in option 1 or option 2.
  • the UE may choose all M sub-bands over which LBT succeeded for PRACH transmission, as shown in option 3 of FIG. 4A.
  • PRACH transmission over multiple sub-bands may increase the reliability of reception of the PRACH transmission by the gNB.
  • the UE may have successful LBT outcome over only one of the LBT sub-bands within the active UL BWP. In this case, the UE may select the sub-band having the successful LBT outcome for PRACH transmission. This is similar to the transmission in FIG. 3 A.
  • the UE may have a successful LBT outcome over more than one LBT sub-band (say, M sub-bands, with M >1) within the initial active UL BWP.
  • the sub- bands may be non-contiguous in the frequency domain.
  • the UE may randomly select any one sub-band from these M sub-bands for PRACH transmission, as shown in option 2 or option 3.
  • the UE may transmit the PRACH over more than one (and perhaps all) M sub-band over which LBT succeeded for PRACH transmission, as shown in option 1 of FIG. 4C, with the above caveat regarding non-consecutive PRACH transmissions.
  • multiple PRACH resources can be configured in the frequency domain for contention-based random access (CBRA) and contention- free random access (CFRA) procedures.
  • CBRA contention-based random access
  • CFRA contention-free random access
  • the above embodiments may be used for both CBRA and CFRA-based PRACH transmission.
  • the above embodiments may be used both for preamble transmission in the 4-step RACH procedure as well as Msg-l transmission for the 2-step RACH procedure.
  • the random access procedure may include the UE initially transmitting a random access preamble to the AMF using a random access channel (RACH) (Msg-l).
  • RACH may use the random access Radio Network Temporary Identifier (RA-RNTI) and a selected Preamble Index.
  • RA-RNTI Random Access Radio Network Temporary Identifier
  • the RACH may be sent at the time and frequency location determined from the RACH parameters in SIB2 of the PBCH.
  • the UE may receive a random access response (RAR) from the AMF in a physical downlink shared channel (PDSCH) (Msg-2).
  • PDSCH physical downlink shared channel
  • the RAR may include the RA-RNTI, a Cell RNTI (RA-RNTI), a timing adjustment for the UE and an uplink grant.
  • the UE may then transmit an RRC Connection Request (Msg-3) on an uplink shared channel (UL-SCH) using the resources indicated by the RAR at a timing based on the timing adjustment.
  • the UE may send an RRC Setup Request (Msg-3) using the UE identity used during contention resolution and an establishment cause.
  • the UE identity may be encrypted using the network key.
  • the AMF may then respond to the RRC Connection Request by transmitting an RRC Connection Setup message or RRC Setup message (Msg-4) on a downlink shared channel (DL-SCH).
  • the RRC Connection Setup message may include information of the Signaling Radio Bearers (SRBs), Data Radio Bearers (DRBs), and UE- specific configuration.
  • the UE may in response transmit an RRC Connection Complete message or RRC Setup Complete message on the UL-SCH.
  • the RRC Connection/Setup Complete message may acknowledge reception of the RRC Setup message.
  • PRACH opportunities in the time domain in addition to, or instead of, the frequency domain.
  • PRACH resources for CFRA in the time and frequency domains can be dynamically configured via downlink control information (DCI) rather than via a SIB.
  • the DCI may be indicated in a physical downlink control channel (PDCCH) signal.
  • the UE may perform CCA, e.g. LBT, to acquire the channel. If LBT is successful, the UE may transmit the preamble. In this case, the UE may not perform PRACH transmission in a shared channel occupancy time (COT).
  • CCA e.g. LBT
  • the gNB may share the remaining COT with the UE while triggering the PRACH transmission through dynamic resource configuration via DCI.
  • the gNB may indicate additional information via DCI related to a shared COT.
  • the additional information may include, for example, the remaining COT duration, the type of
  • a connected mode UE triggered by the gNB may be informed of the type of LBT (e.g., category 1, 2 or 4) that is to be performed for PRACH transmission within the gNB-shared COT.
  • FIG. 5 illustrates a PRACH triggering mechanism in accordance with some embodiments
  • a COT acquired by the gNB may be shared with multiple connected mode UEs; UE1 and UE2 for PRACH transmissions triggered by the gNB if the maximum DL transmission time of the gNB is less than the COT; for example, while the COT is 8ms, the gNB may have a 2ms DL transmission, leaving 6ms to be shared between UE1 and UE2 for PRACH transmission.
  • the gNB may transmit DL data, sending a DCI that indicates a particular LBT (e.g., LBT category 1) for a PRACH transmission to UE1 and UE2.
  • the LBT category may be different for UE1 and UE2.
  • the gNB may transmit dummy data during the remaining time before PRACH transmission.
  • the remaining time may include the processing time of UE1 for receiving the PRACH trigger via DCI and the time for UE1 to prepare a PRACH transmission after decoding the DCI.
  • the gNB may also multiplex DL transmissions to other UEs rather than transmitting dummy data for holding the COT (which may be a maximum of lOms).
  • the PRACH transmission for UE1 can be allowed without LBT while satisfying processing time requirements.
  • there may be no guarantee that UE1 transmits a PRACH for example, UE1 may not receive the DCI with PRACH trigger command due to being located at the cell edge. This means that there is always a possibility that the medium may become occupied and a single-shot LBT (LBT category 2; without use of the random backoff timer) may be used by UE2 (which is indicated dynamically to UE2 using the DCI).
  • LBT category 2 without use of the random backoff timer
  • FIG. 6 illustrates multiplexing of PRACH transmissions in accordance with some embodiments.
  • multiple connected mode UEs UE1 and UE2
  • PRACH resources configured via DCI may be such that these UEs are multiplexed in within the same OFDM symbols for PRACH transmission.
  • the multiplexing may be frequency division multiplexing and/or code division multiplexing. As illustrated in FIG. 6, the multiplexing may be achieved by eliminating LBT requirements for UE1 and UE2. This may be dynamically indicated with the PRACH trigger command via the DCI-configured PRACH resource for preamble transmission.
  • a connected mode UE may be triggered by the gNB.
  • a COT acquired by the gNB may be shared with connected mode UEs (UE1 and UE2).
  • the COT may be used for PRACH transmissions triggered by the gNB.
  • the gNB may not provide the LBT types for PRACH transmissions to the triggered UEs.
  • UE1 may transmit its PRACH preamble without LBT assuming that the resource being used is the first UL resource after the DL resource in the same COT and the gap is less than a fixed value.
  • UE2 may transmit its PRACH with single-shot LBT or cat-4 LBT (LBT with random backoff with variable size contention window) assuming that this is not the UL resource after the DL resource in the same COT and the gap is less than or greater than a fixed value.
  • UE2 may transmit its PRACH without LBT if
  • UE2 senses that the PRACH resources for UE1 are busy.
  • a connected mode UE may be triggered by a different gNB than the gNB to which the RACH procedure is directed. That is, the gNB may trigger the UE (e.g., via DCI) to employ the RACH procedure on another gNB.
  • the triggered RACH procedure may be used in the unlicensed band.

Landscapes

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

Abstract

L'invention concerne la transmission d'un préambule PRACH dans une bande sans licence. La transmission d'un préambule PRACH dépend de règles fournies dans un SIB ou une DCI. Si les règles sont fournies dans un SIB, le préambule PRACH est transmis sur une ou plusieurs sous-bandes, suivant qu'une opération de LBT réussit ou non sur chaque sous-bande, si les sous-bandes sont consécutives ou non et en fonction d'une largeur de bande d'un BWP par rapport à la sous-bande. Si les règles sont fournies dans une DCI, la transmission d'un préambule PRACH s'effectue pendant un COT partagé acquis par le gNB elle est dépendante du type de LBT, le cas échéant, qui est fournie dans la DCI. Le gNB transmet des données factices pour remplir le temps de repos pendant le COT avant la transmission du préambule PRACH si la LBT de catégorie 1 est utilisée.
PCT/US2019/058817 2018-11-02 2019-10-30 Attribution de ressources de prach pour nr sans licence Ceased WO2020092530A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201862755337P 2018-11-02 2018-11-02
US62/755,337 2018-11-02

Publications (1)

Publication Number Publication Date
WO2020092530A1 true WO2020092530A1 (fr) 2020-05-07

Family

ID=70462420

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2019/058817 Ceased WO2020092530A1 (fr) 2018-11-02 2019-10-30 Attribution de ressources de prach pour nr sans licence

Country Status (1)

Country Link
WO (1) WO2020092530A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115804229A (zh) * 2020-06-12 2023-03-14 高通股份有限公司 动态rach msg1/msga配置

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180027554A1 (en) * 2016-07-21 2018-01-25 Qualcomm Incorporated Techniques for communicating on an uplink in a shared radio frequency spectrum band
US20180103456A1 (en) * 2015-06-02 2018-04-12 Huawei Technologies Co., Ltd. Resource allocation method and apparatus

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180103456A1 (en) * 2015-06-02 2018-04-12 Huawei Technologies Co., Ltd. Resource allocation method and apparatus
US20180027554A1 (en) * 2016-07-21 2018-01-25 Qualcomm Incorporated Techniques for communicating on an uplink in a shared radio frequency spectrum band

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
LG ELECTRONICS: "Summary #2 on frame structure for NR-U", 3GPP DRAFT; R1-1812012 7.2.2.2 SUMMARY OF FRAME STRUCTURE FOR NR-U, vol. RAN WG1, 11 October 2018 (2018-10-11), Chengdu, China, pages 1 - 16, XP051519336 *
NOKIA ET A: "On the Frame structure and Wideband operation for NR-U", 3GPP DRAFT; R1-1810613_FRAME STRUCTURE AND WB OPERATION, vol. RAN WG1, R1-1810613_Frame structure and WB operation, 28 September 2018 (2018-09-28), Chengdu, China, pages 1 - 13, XP051518019 *
SAMSUNG: "Initial Access and Mobility Procedure for NR-U", 3GPP DRAFT; R1-1808769-INITIAL-ACCESS, vol. RAN WG1, 11 August 2018 (2018-08-11), Gothenburg, Sweden, pages 1 - 8, XP051516142 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115804229A (zh) * 2020-06-12 2023-03-14 高通股份有限公司 动态rach msg1/msga配置

Similar Documents

Publication Publication Date Title
US11147104B2 (en) PRACH resource selection
US20240397548A1 (en) Channel Occupancy Time Indication for NR Based Unlicensed Operation
US20220150802A1 (en) PBCH Content for NR Unlicensed
US12426009B2 (en) UE paging in NR unlicensed spectrum
US20210298075A1 (en) Contention Window Size Update for NR Systems Operating on Unlicensed Band
US11463938B2 (en) Managing control plane latency for integrated access and backhaul
RU2735183C1 (ru) Управление aul-передачами при сосуществовании с диспетчеризованными ue
CN106550480B (zh) 一种随机接入方法、装置及系统
US10959270B2 (en) NPRACH configuration and format for unlicensed NBIoT system
KR20180111831A (ko) 비면허 통신 채널들에서의 페이징을 위한 방법들 및 장치
CN112956255B (zh) 新无线电未许可频谱中的寻呼用户装备
US20210410199A1 (en) Random access resources based on network conditions
CN114731706A (zh) Nr-u中的基于帧的设备(fbe)
CN113424641A (zh) 无线通信网络中的随机接入
TWI620428B (zh) 處理系統資訊的裝置及方法
WO2018191916A1 (fr) Procédé d'adressage de conflits de temporisateur de canal logique et blocage de données
US11109447B2 (en) Unlicensed band IoT systems
WO2020092530A1 (fr) Attribution de ressources de prach pour nr sans licence
WO2020117593A1 (fr) Mécanismes de bande sans licence ul et de bande sous licence ul
US10980048B2 (en) Contention based signaling in a wireless communication system
WO2025166521A1 (fr) Procédé et appareil de communication sans fil, dispositif et support de stockage

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

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

Country of ref document: EP

Kind code of ref document: A1