WO2020151754A1 - 一种ra-rnti处理方法和装置 - Google Patents

一种ra-rnti处理方法和装置 Download PDF

Info

Publication number
WO2020151754A1
WO2020151754A1 PCT/CN2020/073886 CN2020073886W WO2020151754A1 WO 2020151754 A1 WO2020151754 A1 WO 2020151754A1 CN 2020073886 W CN2020073886 W CN 2020073886W WO 2020151754 A1 WO2020151754 A1 WO 2020151754A1
Authority
WO
WIPO (PCT)
Prior art keywords
rnti
preamble
indicates
rar
value range
Prior art date
Application number
PCT/CN2020/073886
Other languages
English (en)
French (fr)
Inventor
吴霁
张佳胤
贾琼
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP20746036.1A priority Critical patent/EP3917232A4/en
Priority to KR1020217026858A priority patent/KR20210116636A/ko
Priority to CA3127703A priority patent/CA3127703A1/en
Priority to JP2021543174A priority patent/JP7282182B2/ja
Priority to BR112021014571-0A priority patent/BR112021014571A2/pt
Publication of WO2020151754A1 publication Critical patent/WO2020151754A1/zh
Priority to US17/385,570 priority patent/US20210360697A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0808—Non-scheduled access, e.g. ALOHA using carrier sensing, e.g. carrier sense multiple access [CSMA]
    • H04W74/0816—Non-scheduled access, e.g. ALOHA using carrier sensing, e.g. carrier sense multiple access [CSMA] with collision avoidance
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0048—Allocation of pilot signals, i.e. of signals known to the receiver
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path
    • H04L5/0094—Indication of how sub-channels of the path are allocated
    • 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
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0446—Resources in time domain, e.g. slots or frames
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0453—Resources in frequency domain, e.g. a carrier in FDMA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0466—Wireless resource allocation based on the type of the allocated resource the resource being a scrambling code
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H04W72/231—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal the control data signalling from the layers above the physical layer, e.g. RRC or MAC-CE signalling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H04W72/232—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal the control data signalling from the physical layer, e.g. DCI signalling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/002—Transmission of channel access control information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/002—Transmission of channel access control information
    • H04W74/004—Transmission of channel access control information in the uplink, i.e. towards network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/002—Transmission of channel access control information
    • H04W74/006—Transmission of channel access control information in the downlink, i.e. towards the terminal
    • 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/0841—Random access procedures, e.g. with 4-step access with collision treatment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0808—Non-scheduled access, e.g. ALOHA using carrier sensing, e.g. carrier sense multiple access [CSMA]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • 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

  • This application relates to the field of wireless communication technology, and in particular to a RA-RNTI processing method and device.
  • the UE After the cell search process, the UE has achieved downlink synchronization with the cell, so the UE can receive downlink data. However, the UE can only perform uplink transmission if it has achieved uplink synchronization with the cell.
  • the UE establishes a connection with the cell and obtains uplink synchronization through a random access procedure (Random Access Procedure).
  • the main purpose of random access is: (1) Obtain uplink synchronization; (2) Assign a unique identifier C-RNTI in the cell to the UE.
  • RA-RNTI Random Access Network Identifier
  • the calculation of RA-RNTI is related to the time-frequency resources of the UE sending the preamble sequence, and the generation formula is as follows:
  • RA-RNTI 1+t_id+10*f_id (1)
  • t_id indicates that the sending preamble occupies the first subframe number, and its value range is 0 ⁇ t_id ⁇ 10.
  • f_id indicates the number of the preamble transmission resource in the frequency domain, and its value range is 0 ⁇ t_id ⁇ 6.
  • the value of RA-RNTI will not repeat within a 10ms window (that is, within 10 subframes).
  • the RA-RNTI calculation formula is as follows:
  • RA-RNTI 1+s_id+14 ⁇ t_id+14 ⁇ 80 ⁇ f_id+14 ⁇ 80 ⁇ 8 ⁇ ul_carrier_id(2)
  • s_id indicates that the sending preamble occupies the start symbol number of the first subframe, and its value range is 0 ⁇ s_id ⁇ 14.
  • t_id indicates that the preamble transmission resource occupies the first subframe number, and its value range is 0 ⁇ t_id ⁇ 80.
  • f_id indicates the number of the preamble transmission resource in the frequency domain, and its value range is 0 ⁇ f_id ⁇ 8.
  • ul_carrier_id indicates the uplink carrier used for preamble transmission, ‘0’ indicates the normal uplink carrier, and ‘1’ indicates the auxiliary uplink carrier.
  • the reason for the different value from LTE is that NR PRACH transmission time-frequency resources can theoretically start on each symbol in each slot in each system frame of each uplink carrier, and PRACH transmission supports a maximum of 120kHz subcarrier spacing .
  • the technical problem to be solved by this application is to reduce the repetition of RA-RNTI on the unlicensed spectrum in the NR system.
  • An RA-RNTI processing method After the NR-U UE succeeds in LBT, it randomly selects a preamble, selects an available random access time-frequency resource RO; sends the preamble on the selected RO; based on the RO generates RA-RNTI.
  • a first indication sent by a network device may be received, and the first indication is used to indicate time information or location information of the RAR; the NR-U UE is only in the time window (RAR) indicated by the first indication
  • the PDCCH is detected internally, and the PDCCH is scrambled by the gNB using the same RA-RNTI.
  • the first indication is carried in DCI.
  • the first indication is carried in the RAR MAC CE.
  • RA-RNTI is generated according to one of the following formulas:
  • RA-RNTI 1+s_id+14 ⁇ t_id+14 ⁇ K ⁇ f_id+14 ⁇ K ⁇ 8 ⁇ ul_carrier_id(3)
  • the s_id in the above formula indicates that the sending preamble occupies the start symbol number of the first subframe, and its value range is 0 ⁇ s_id ⁇ 14.
  • t_id indicates that the preamble transmission resource occupies the first subframe number, and its value range is 0 ⁇ t_id ⁇ 80.
  • f_id indicates the number of the preamble transmission resource in the frequency domain, and its value range is 0 ⁇ f_id ⁇ 8.
  • ul_carrier_id indicates the uplink carrier used for preamble transmission, ‘0’ indicates a normal uplink carrier, and ‘1’ indicates an auxiliary uplink carrier; the K is a parameter corresponding to the maximum value of the RAR window;
  • RA-RNTI 1+s_id+14 ⁇ t_id+14 ⁇ 80 ⁇ f_id+14 ⁇ 80 ⁇ 8 ⁇ ul_carrier_id(2a)
  • s_id is used to indicate that the sending preamble occupies the first subframe start symbol number, and its value range It is 0 ⁇ s_id ⁇ 14.
  • t_id is used to indicate that the preamble transmission resource occupies the first subframe number, and its value range is 0 ⁇ t_id ⁇ 80.
  • f_id indicates the number of the preamble transmission resource in the frequency domain, and its value range is 0 ⁇ f_id ⁇ 8.
  • the ul_carrier_id indication information in the NR RA-RNTI calculation formula (2a) is used to indicate the position information of the Preamble received by the gNB in the RAR window.
  • it can also be the formula (2), formula (3a) or (3b) mentioned in the embodiment, which will not be repeated here.
  • the selection of the available random access time-frequency resource RO specifically includes: selecting a subframe in multiple subframes in a system frame configured for the NRU UE, and selecting The preamble is sent in the subframes of, and the number of the multiple subframes is less than 10.
  • the present application also provides a device, a computer-readable storage medium, and the like that can execute the foregoing methods.
  • the implementation of the embodiments of this application can improve the flexibility of uplink resource scheduling on the basis of meeting the OCB requirements of ESTI for the use of unlicensed frequency bands. Furthermore, resource utilization can be improved.
  • Figure 1 is a schematic diagram of an existing resource allocation method involved in this application
  • FIG. 2 is a schematic diagram of the architecture of a wireless communication system related to this application.
  • FIG. 3 is a schematic diagram of the hardware architecture of a terminal provided by an embodiment of the present application.
  • FIG. 4 is a schematic diagram of the hardware architecture of a base station provided by an embodiment of the present application.
  • FIG. 5 is a schematic flowchart of the NR-U UE random access process provided by an embodiment of the present application
  • Fig. 6 is a simple schematic diagram of NRU RAR MAC provided by an embodiment of the present application.
  • FIG. 7 is a schematic diagram of an NRU SF indication subframe header provided by an embodiment of the present application.
  • FIG. 8 is a schematic diagram of NRU RA-RNTI detection provided by an embodiment of the present application.
  • FIG. 2 shows a wireless communication system 200 related to the present application.
  • the wireless communication system 200 may work in a licensed frequency band or an unlicensed frequency band. It can be understood that the use of unlicensed frequency bands can increase the system capacity of the wireless communication system 200.
  • the wireless communication system 200 includes: one or more network devices 201, such as base stations, NodeB, eNodeB or WLAN access points, wireless relay nodes, wireless backhaul nodes, and one or more terminals (Terminal) 203, and the core network 215. among them:
  • the network device 201 can be used to communicate with the terminal 203 under the control of a base station controller (not shown).
  • the base station controller may be part of the core network 230 or integrated into the base station 201.
  • the network device 201 may be used to transmit control information (control information) or user data (user data) to the core network 215 through a backhaul interface (such as an S1 interface) 213.
  • control information control information
  • user data user data
  • the network device 201 may perform wireless communication with the terminal 203 through one or more base station antennas. Each base station 201 can provide communication coverage for its corresponding coverage area 207.
  • the coverage area 207 corresponding to the access point may be divided into multiple sectors (sector), where one sector corresponds to a part of the coverage area (not shown).
  • the network device 201 and the base station 201 may also communicate with each other directly or indirectly through a backhaul link 211.
  • the backhaul link 211 may be a wired communication connection or a wireless communication connection.
  • the network device 201 may also be a wireless controller in a cloud radio access network (cloud radio access network, CRAN) scenario.
  • the network device 201 may also be a network device in a 5G network or a network device in a future evolution network; it may also be a wearable device or a vehicle-mounted device.
  • the network device 201 may also be a small station, a transmission reference point (TRP), etc.
  • TRP transmission reference point
  • the network device 201 may include: a base transceiver station (Base Transceiver Station), a wireless transceiver, a basic service set (Basic Service Set, BSS), and an extended service set (Extended Service Set, ESS). ), NodeB, eNodeB, etc.
  • the wireless communication system 200 may include several different types of base stations 201, such as a macro base station (macro base station), a micro base station (micro base station), and so on.
  • the base station 201 may apply different wireless technologies, such as cell wireless access technology or WLAN wireless access technology.
  • the terminal 203 may be distributed in the entire wireless communication system 200, and may be stationary or mobile. It can be deployed on land, including indoor or outdoor, handheld, wearable or vehicle-mounted; it can also be deployed on the water (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons, and satellites, etc.).
  • the terminal device may be a mobile phone (mobile phone), a tablet computer (Pad), a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (Augmented Reality, AR) terminal device, an industrial control ( Wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical, wireless terminals in smart grid, and transportation safety (transportation safety) Wireless terminal, wireless terminal in smart city, wireless terminal in smart home, etc.
  • Terminal equipment can sometimes be called user equipment (UE), access terminal equipment, UE unit, UE station, mobile station, mobile station, remote station, remote terminal equipment, mobile equipment, UE terminal equipment, terminal equipment, Wireless communication equipment, UE agent or UE device, etc.
  • the terminal 203 may include: a mobile device, a mobile station, a mobile unit, a wireless unit, a remote unit, a user agent, a mobile client, and so on.
  • the wireless communication system 200 may be an LTE communication system capable of working in an unlicensed frequency band, such as LTE-U, or may be a 5G and future new air interface capable of working in an unlicensed frequency band, such as NR-U. system.
  • the wireless communication system 200 may adopt a licensed assisted access (LAA) scheme to process terminal access on an unlicensed frequency band.
  • LAA licensed assisted access
  • the primary cell Primary Cell
  • the secondary cell (Secondary Cell) works in an unlicensed frequency band to improve data plane performance.
  • the wireless communication system 200 may support multi-carrier (waveform signals of different frequencies) operation.
  • Multi-carrier transmitters can simultaneously transmit modulated signals on multiple carriers.
  • each communication connection 205 can carry multi-carrier signals modulated by different wireless technologies.
  • Each modulated signal can be sent on a different carrier, and can also carry control information (for example, reference signals, control channels, etc.), overhead information (Overhead Information), data, and so on.
  • the wireless communication system 200 may also include a WiFi network.
  • the wireless communication system 200 may adopt a listen before talk (LBT) mechanism.
  • LBT listen before talk
  • some terminals 203 can connect to the WiFi access point 209 through the WiFi communication connection 217 to use unlicensed spectrum resources, and some terminals 203 can also connect to the base station 201 through the mobile communication connection 205 to use unlicensed spectrum resources.
  • any device When using an unlicensed frequency band, any device must first monitor to see if the frequency band is occupied. If the frequency band is not busy, it can occupy and transmit data.
  • FIG. 3 shows a terminal 300 provided by some embodiments of the present application.
  • the terminal 300 may include: an input and output module (including an audio input and output module 318, a key input module 316, a display 320, etc.), a user interface 302, one or more terminal processors 304, a transmitter 306, a receiver 308, coupler 310, antenna 314, and memory 312. These components can be connected via a bus or in other ways.
  • Fig. 3 uses a bus connection as an example. among them:
  • the communication interface 301 can be used for the terminal 300 to communicate with other communication devices, such as a base station.
  • the other communication device may be the base station 400 shown in FIG. 4.
  • the communication interface 301 may include: Global System for Mobile Communication (GSM) (2G) communication interface, Wideband Code Division Multiple Access (WCDMA) (3G) communication interface, and long-term One or more of the evolution (Long Term Evolution, LTE) (4G) communication interfaces, etc., may also be 4.5G, 5G, or future new air interface communication interfaces.
  • GSM Global System for Mobile Communication
  • WCDMA Wideband Code Division Multiple Access
  • LTE Long Term Evolution
  • 4G Long Term Evolution
  • the terminal 300 may also be configured with a wired communication interface 301, such as a local access network (Local Access Network, LAN) interface.
  • a wired communication interface 301 such as a local access network (Local Access Network, LAN) interface.
  • the antenna 314 can be used to convert electromagnetic energy in a transmission line into electromagnetic waves in a free space, or convert electromagnetic waves in a free space into electromagnetic energy in a transmission line.
  • the coupler 310 is used to divide the mobile communication signal received by the antenna 314 into multiple channels and distribute them to multiple receivers 308.
  • the transmitter 306 may be used to transmit and process the signal output by the terminal processor 304, such as modulating the signal in a licensed frequency band or modulating a signal in an unlicensed frequency band.
  • the transmitter 206 may include an unlicensed spectrum transmitter 3061 and a licensed spectrum transmitter 3063.
  • the unlicensed spectrum transmitter 3061 can support the terminal 300 to transmit signals on one or more unlicensed spectrums
  • the licensed spectrum transmitter 3063 can support the terminal 300 to transmit signals on one or more licensed spectrums.
  • the receiver 308 can be used to receive and process the mobile communication signal received by the antenna 314.
  • the receiver 308 may demodulate the received signal modulated on the unlicensed frequency band, or may demodulate the received signal modulated on the licensed frequency band.
  • the receiver 308 may include an unlicensed spectrum receiver 3081 and a licensed spectrum receiver 3083.
  • the unlicensed spectrum receiver 3081 can support the terminal 300 to receive signals modulated on the unlicensed spectrum
  • the licensed spectrum receiver 3083 can support the terminal 300 to receive signals modulated on the licensed spectrum.
  • the transmitter 306 and the receiver 308 can be regarded as one wireless modem.
  • the number of the transmitter 306 and the receiver 308 may each be one or more.
  • the terminal 300 may also include other communication components, such as a GPS module, a Bluetooth (Bluetooth) module, and a wireless high-fidelity (Wireless Fidelity, Wi-Fi) module. Not limited to the above-mentioned wireless communication signals, the terminal 300 may also support other wireless communication signals, such as satellite signals, shortwave signals, and so on. Not limited to wireless communication, the terminal 300 may also be configured with a wired network interface (such as a LAN interface) to support wired communication.
  • a wired network interface such as a LAN interface
  • the input and output module may be used to implement interaction between the terminal 300 and the user or the external environment, and may mainly include an audio input and output module 318, a key input module 316, and a display 320. Specifically, the input and output module may also include a camera, a touch screen, a sensor, and so on. Wherein, the input and output modules all communicate with the terminal processor 304 through the user interface 302.
  • the memory 312 is coupled with the terminal processor 304, and is used to store various software programs and or multiple sets of instructions.
  • the memory 312 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state storage devices.
  • the memory 312 may store an operating system (hereinafter referred to as system), such as an embedded operating system such as ANDROID, IOS, WINDOWS, or LINUX.
  • system such as an embedded operating system such as ANDROID, IOS, WINDOWS, or LINUX.
  • the memory 312 may also store a network communication program, which may be used to communicate with one or more additional devices, one or more terminal devices, and one or more network devices.
  • the memory 312 can also store a user interface program, which can vividly display the content of the application program through a graphical operation interface, and receive user control operations on the application program through input controls such as menus, dialog boxes,
  • the memory 312 may be used to store an implementation program on the terminal 300 side of the resource allocation method provided by one or more embodiments of the present application.
  • the implementation of the resource allocation method provided by one or more embodiments of this application please refer to the subsequent embodiments.
  • the terminal processor 304 can be used to read and execute computer-readable instructions. Specifically, the terminal processor 304 may be used to call a program stored in the memory 312, such as a program for implementing the resource allocation method provided by one or more embodiments of the present application on the terminal 300 side, and execute the instructions contained in the program.
  • a program stored in the memory 312 such as a program for implementing the resource allocation method provided by one or more embodiments of the present application on the terminal 300 side, and execute the instructions contained in the program.
  • the terminal 300 may be the terminal 203 in the wireless communication system 200 shown in FIG. 2, and may be implemented as a mobile device, a mobile station, a mobile unit, a wireless unit, a remote unit, and a user agent. , Mobile client and so on.
  • the terminal 300 shown in FIG. 3 is only an implementation manner of the embodiment of the present application. In actual applications, the terminal 300 may also include more or fewer components, which is not limited here.
  • FIG. 4 shows a base station 400 provided by some embodiments of the present application.
  • the base station 400 may include: a communication interface 403, one or more base station processors 401, a transmitter 407, a receiver 409, a coupler 411, an antenna 413, and a memory 405. These components can be connected via a bus or in other ways.
  • Fig. 4 uses a bus connection as an example. among them:
  • the communication interface 403 can be used for the base station 400 to communicate with other communication devices, such as terminal devices or other base stations.
  • the terminal device may be the terminal 300 shown in FIG. 3.
  • the communication interface 403 may include: a global system for mobile communication (GSM) (2G) communication interface, a wideband code division multiple access (WCDMA) (3G) communication interface, and a long-term evolution (LTE) (4G) communication interface, etc.
  • GSM global system for mobile communication
  • WCDMA wideband code division multiple access
  • LTE long-term evolution
  • the base station 400 may also be configured with a wired communication interface 403 to support wired communication.
  • the backhaul link between one base station 400 and other base stations 400 may be a wired communication connection.
  • the antenna 413 can be used to convert electromagnetic energy in a transmission line into electromagnetic waves in a free space, or convert electromagnetic waves in a free space into electromagnetic energy in a transmission line.
  • the coupler 411 can be used to divide the mobile communication signal into multiple channels and distribute them to multiple receivers 409.
  • the transmitter 407 may be used to transmit and process the signal output by the base station processor 401, for example, modulate the signal in a licensed frequency band or modulate a signal in an unlicensed frequency band.
  • the transmitter 407 may include an unlicensed spectrum transmitter 4071 and a licensed spectrum transmitter 4073.
  • the unlicensed spectrum transmitter 4071 can support the base station 400 to transmit signals on one or more unlicensed spectrums
  • the licensed spectrum transmitter 4073 can support the base station 400 to transmit signals on one or more licensed spectrums.
  • the receiver 409 can be used to receive and process the mobile communication signal received by the antenna 413.
  • the receiver 409 may demodulate the received signal modulated on the unlicensed frequency band, and may also demodulate the received signal modulated on the licensed frequency band.
  • the receiver 409 may include an unlicensed spectrum receiver 4091 and a licensed spectrum receiver 4093.
  • the unlicensed spectrum receiver 4091 can support the base station 400 to receive signals modulated on the unlicensed spectrum
  • the licensed spectrum receiver 4093 can support the base station 400 to receive signals modulated on the licensed spectrum.
  • the transmitter 407 and the receiver 409 can be regarded as a wireless modem.
  • the number of transmitters 407 and receivers 409 may each be one or more.
  • the memory 405 is coupled with the base station processor 401, and is used to store various software programs and or multiple sets of instructions.
  • the memory 405 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state storage devices.
  • the memory 405 may store an operating system (hereinafter referred to as system), such as embedded operating systems such as uCOS, VxWorks, RTLinux, and so on.
  • system such as embedded operating systems such as uCOS, VxWorks, RTLinux, and so on.
  • the memory 405 may also store a network communication program, which may be used to communicate with one or more additional devices, one or more terminal devices, and one or more network devices.
  • the base station processor 401 can be used to perform wireless channel management, implement call and communication link establishment and teardown, and control the handover of user equipment in the control area.
  • the base station processor 401 may include: an administration or communication module (Administration Module or Communication Module, AM or CM) (a center for voice channel exchange and information exchange), a basic module (Basic Module, BM) (for completing Call processing, signaling processing, wireless resource management, wireless link management and circuit maintenance functions), transcoder and submultiplexer (TCSM) (used to complete multiplexing, demultiplexing and code conversion functions) and many more.
  • an administration or communication module (Administration Module or Communication Module, AM or CM) (a center for voice channel exchange and information exchange), a basic module (Basic Module, BM) (for completing Call processing, signaling processing, wireless resource management, wireless link management and circuit maintenance functions), transcoder and submultiplexer (TCSM) (used to complete multiplexing, demultiplexing and code conversion functions) and many more.
  • AM or CM administration
  • the base station processor 401 may be used to read and execute computer-readable instructions. Specifically, the base station processor 401 may be used to call a program stored in the memory 405, such as a program for implementing the resource allocation method provided by one or more embodiments of the present application on the base station 400 side, and execute the instructions contained in the program.
  • a program stored in the memory 405 such as a program for implementing the resource allocation method provided by one or more embodiments of the present application on the base station 400 side, and execute the instructions contained in the program.
  • the base station 400 may be the base station 201 in the wireless communication system 200 shown in FIG. 2, and may be implemented as a base transceiver station, a wireless transceiver, a basic service set (BSS), an extended service set (ESS), and NodeB , ENodeB, etc.
  • the base station 400 may be implemented as several different types of base stations, such as macro base stations, micro base stations, and so on.
  • the base station 400 may apply different wireless technologies, such as cell wireless access technology or WLAN wireless access technology.
  • the base station 400 shown in FIG. 4 is only an implementation manner of the embodiment of the present application. In practical applications, the base station 400 may also include more or fewer components, which is not limited here.
  • the terminal 300 or the base station 400 may also be configured as a general-purpose processing system, for example, a general-purpose processing system called a chip.
  • the general-purpose processing system includes: one or more microprocessors that provide processor functions; and an external device that provides at least a part of a storage medium. Memory, all of which are connected with other support circuits through an external bus architecture.
  • the terminal 300 or the base station 400 can be implemented using the following: an ASIC (application specific integrated circuit) with a processor, a bus interface, or a user interface; and at least a part of a storage medium integrated in a single chip, or the terminal 300 or base station 400 can be implemented using the following: one or more FPGAs (field programmable gate arrays), PLDs (programmable logic devices), controllers, state machines, gate logic, discrete hardware components, any other suitable circuits Or any combination of circuits capable of performing the various functions described throughout the present invention.
  • the processor is responsible for managing the bus and general processing (including executing software stored on the storage medium).
  • the processor may be implemented using one or more general-purpose processors and/or special-purpose processors.
  • processors include microprocessors, microcontrollers, DSP processors, and other circuits capable of executing software.
  • Software should be interpreted broadly to mean instructions, data, or any combination thereof, regardless of whether it is called software, firmware, middleware, microcode, hardware description language, or other.
  • This specific embodiment mainly involves a competitive random access process, and only takes NR-U UE and gNB as examples of terminals and network devices. The process is shown in FIG. 5.
  • Step 101 After the NR-U UE succeeds in LBT, it randomly selects a Preamble according to the system configuration information, and selects an available random access time slot, and sends the Preamble in the available random access time slot.
  • the UE can obtain its own RA-RNTI (Random Access Network Identity) according to the time and frequency domain position of the selected random access slot.
  • RA-RNTI Random Access Network Identity
  • the time-frequency resource for the UE to send the Preamble is called RACH occasion, or RO for short.
  • the gNB receives the Preamble sent by the aforementioned NR-U UE.
  • system configuration information includes preamble setting information, RO configuration information, the corresponding relationship between SSB and RO, the value of t_id, the maximum duration of RAR window, and so on.
  • the available random access time slots may be all available random access time slots, or under special circumstances, they may also be specific partial random access time slots, such as the sixth embodiment.
  • Step 102 Specifically, the gNB obtains the same RA-RNTI by using the same method in step 101 (according to the time-frequency resource of the received Preamble), and sends the PDCCH scrambled by the RA-RNTI after the LBT is successful.
  • the NR-U UE detects or tries to receive the PDCCH scrambled with the same RA-RNTI obtained in step 101 and sent by the gNB within the detection time range configured for the NR-U UE.
  • the PDCCH channel mainly carries PUSCH and PDSCH channel control information (DCI), and the PDCCH information of different UEs are distinguished by their corresponding RA-RNTI information, that is, the CRC of their DCI is scrambled by the RA-RNTI.
  • DCI PDSCH channel control information
  • the transmission of the above-mentioned PDCCH by the gNB is affected by LBT, that is, there is a situation where the gNB is ready for the above-mentioned PDCCH but cannot be transmitted because the channel is busy.
  • LBT Low-power Bluetooth
  • the maximum value of the RAR window is extended to greater than 10 ms in NR-U, so that gNB has more opportunities to send PDCCH.
  • the calculation method of NR RA-RNTI can only ensure that it is only unique within 10ms, so this better implementation can be used to solve how the UE correctly judges that the gNB transmission is scrambled by RA-RNTI in the RAR window greater than 10ms Whether the PDCCH (including DCI, etc.) is for yourself.
  • the above-mentioned detection time range configured for NR-U UE includes many situations, and you can refer to the descriptions in each of the following embodiments 1 to 6; among them, if there is no special description, the detection time range refers to all RAR time windows . That is, the UE detects within the RAR time window until it detects its own PDCCH.
  • the NR-U UE attempts to descramble one or more received PDCCHs by using its own RA-RNTI, and the PDCCH that can be successfully descrambled is the PDCCH of the NR-U UE.
  • each embodiment further includes the following steps 103-105, but since the relevant steps no longer involve RA-RNTI, they will not be described in detail herein.
  • Step 103 If the PDCCH is successfully received, the UE decodes the information carried in the PDSCH (Physical downlink shared channel); if the PDCCH is not detected within the detection time range, the NR-U UE adjusts its own transmit power Step 101 is performed again in the random access time slot configured in the next system.
  • PDSCH Physical downlink shared channel
  • Step 104 The above PDSCH includes the time-frequency resource information of the NR-U UE to send Msg3 and the temporary network identification (TC-RNTI: Temporary Cell Radio Network Temporary Identification) allocated to the NR-U UE, and the UE sends it in the corresponding time-frequency resource Msg3, and carries the NR-U UE's unique network identifier in the entire network for random success confirmation in step 104.
  • TC-RNTI Temporary Cell Radio Network Temporary Identification
  • Step 105 The NR-U UE will detect the PDCCH scrambled with the NR-U UE temporary network identity in step 103. If successful, it will decode the information carried in the PDSCH. If the information carries the network-wide unique identifier sent by itself in step 103, the random access is successful, and the NR-U UE sends an acknowledgement (ACK) to the gNB. If it is not its own identity, the random access fails, and step 101 is repeated.
  • ACK acknowledgement
  • the gNB indicates the time information or location information of the RAR to avoid misdetection that may be caused by the RA-RNTI not being unique.
  • the gNB sends a first indication, which is used to indicate the time information or location information of the RAR, that is, to indicate which RAR corresponding to the NR-U UE belongs to within 10ms of the RAR window or within which system frame .
  • the NR-U UE receives and obtains the first indication. Generally, one system frame lasts for 10ms.
  • the above method also includes:
  • the gNB receives the Preamble sent by the NR-U UE. Specifically, the gNB detects the Preamble sent by the NR-U UE, and after detecting the Preamble, it determines the RA-RNTI of the NR-U UE according to the time-frequency resource RO of the detected Preamble.
  • the NR-U UE can also calculate the RA-RNTI based on the same RO information.
  • s_id is used to indicate that the sending preamble occupies the start symbol number of the first subframe, and its value range is 0 ⁇ s_id ⁇ 14.
  • t_id is used to indicate that the preamble transmission resource occupies the first subframe number, and its value range is 0 ⁇ t_id ⁇ 80.
  • f_id indicates the number of the preamble transmission resource in the frequency domain, and its value range is 0 ⁇ f_id ⁇ 8.
  • ul_carrier_id is used to indicate the uplink carrier used for preamble transmission, ‘0’ means normal uplink carrier, and ‘1’ means auxiliary uplink carrier.
  • gNB generates the same RA-RNTI in the same way.
  • the NR-U UE Detect the RAR, and determine whether to continue parsing the PDCCH carried by the RAR according to the first instruction. Specifically, the NR-U UE first determines whether the time window for the first indication of a detected RAR is the same as the time window for sending the preamble, for example, within the same 10ms, and if so, continues to analyze the RAR To obtain information such as the PDSCH carried in the PDCCH. If not, give up analyzing the RAR, thereby greatly reducing detection and analysis resources.
  • the PDCCH is the PDCCH of the NR-U UE, and the NR-U UE stops continuing to detect the RAR.
  • the first indication is carried in DCI.
  • the gNB may add extra bits to the DCI scrambled by the RA-RNTI to indicate which 10 ms of the RAR window the RAR corresponding to the UE belongs to, and use extra indication information to indicate in which system frame the gNB receives the preamble.
  • the gNB or NR-U UE can use the above formula (2) to generate the RA-RNTI, and still remain unique within 10ms.
  • '0' means that the time between the two is less than 10ms
  • '1' means that the time between the two is greater than 10ms and less than 20ms.
  • bits can be used in the DCI to indicate the RAR window time information, and the method is similar to the above, and will not be repeated here.
  • 2 bits can indicate the RA-RNTI reception condition within a 40ms RAR window at most
  • 3 bits can indicate the RA-RNTI reception condition within an 80ms RAR window at most.
  • one or more bits of the DCI may be multiplexed, and part of the value is used to indicate the above-mentioned RAR window information.
  • Using this method can save some overhead on the basis of indicating the above information.
  • the existing RA-RNTI scrambled DCI1_0 has 16 reserved bits (reserved bits), and one or more of the reserved bits can be used for the above indication according to the maximum supported RAR window duration, for example, 2, 3. , 4 bits.
  • the first indication is carried in the RAR MAC CE.
  • the NRU RAR MAC frame structure is shown in Figure 6 and Figure 7 below.
  • the RAR MAC CE (control element: control element) includes an SF indication subframe header, which is used to indicate which system the RA-RNTI scrambled PDCCH corresponding to a certain preamble received by the gNB is located.
  • the SF indication subframe header is used to indicate the system frame sequence number where the PDCCH or RAR of the UE is located.
  • the SF indication subframe header may be located after the BI subframe header and the RAPID subframe header.
  • the first three bits of the SF indication subframe header can be set to '101', and the remaining 5 bits can be used to indicate the system frame number of the RA-RNTI.
  • 5 bits can indicate a maximum of 32 system frames, that is, the maximum length of the RAR window is 320 ms.
  • the NRU UE receives it, and the NRU UE can determine whether the subsequent MAC RAR is its own after detecting the SF indication subframe header. Further, the preamble received by the gNB indicated in the RAR MAC PDU can be sorted according to the frame or subframe sequence number. When the UE detects that the system frame or subframe indicated by the SFI field (the system frame or subframe corresponding to the MAC RAR) is greater than the system frame number or subframe number of the preamble sent by the UE, it will not try to detect the MAC PDU (physical data unit: Physical data unit) remaining sub PDUs to achieve the purpose of saving UE energy.
  • the MAC PDU physical data unit: Physical data unit
  • UE 1 sends a Preamble in system frame 5, and receives its corresponding RA-RNTI scrambled RAR (PDCCH) in system frame 10.
  • the SF indication subframe header indicates that the subsequent MAC RAR corresponds to the RA-RNTI received by the gNB in system frames 6 and 8 (RA-RNTI calculated based on the time-frequency resource of the received preamble), and the UE will not continue to analyze at this time The subsequent MAC information, and considers that the gNB has not received the preamble sent by it.
  • the NR UE blindly checks all subPDUs of the MAC PDU indicated by the DCI scrambled by the RA-RNTI to ensure that the RAR information sent by the gNB to itself is not omitted.
  • the value range of RA-RNTI is 0001-FFEF (65519)
  • the value range of RA-RNTI in a 10ms window is 1-17920 (1+13+14*13+14*80*7+14*80*8*1), which can guarantee a maximum window of 36ms
  • the inner RA-RNTI is not repeated.
  • RA-RNTI 1+s_id+14 ⁇ t_id+14 ⁇ 80 ⁇ f_id+14 ⁇ 80 ⁇ 8 ⁇ ul_carrier_id
  • the value of t_id can be directly expanded from the current 80 to 320. If the RAR window size is extended to 40msec, the value range of t_id becomes 0 ⁇ t_id ⁇ 320 and the maximum RA-RNTI value becomes (71680-1) which is larger than the 16-bit RNTI can provide.
  • the calculation formula (3) of NR RA-RNTI and the corresponding parameter K is used to make it more suitable for scenarios when the RAR window length is greater than 10 ms
  • RA-RNTI 1+s_id+14 ⁇ t_id+14 ⁇ K ⁇ f_id+14 ⁇ K ⁇ 8 ⁇ ul_carrier_id(3)
  • the s_id in the above formula indicates that the sending preamble occupies the start symbol number of the first subframe, and its value range is 0 ⁇ s_id ⁇ 14.
  • t_id indicates that the preamble transmission resource occupies the first subframe number, and its value range is 0 ⁇ t_id ⁇ 80.
  • f_id indicates the number of the preamble transmission resource in the frequency domain, and its value range is 0 ⁇ f_id ⁇ 8.
  • ul_carrier_id indicates the uplink carrier used for preamble transmission, ‘0’ indicates the normal uplink carrier, and ‘1’ indicates the auxiliary uplink carrier.
  • NR PRACH transmission time-frequency resources can theoretically start on each symbol in each slot in each system frame of each uplink carrier, and PRACH transmission supports a maximum of 120 kHz. Carrier spacing.
  • the value of K can be different according to the maximum value of the RAR window, refer to Table 1.
  • the relevant standard may specify that the maximum value of the RAR window is any one or more of those in Table 1, and the value of K above is the corresponding value in Table 1.
  • Table 1 also gives the value range of RNTI calculated by the formula (3) under the corresponding scheme.
  • the gNB can statically/semi-statically configure the RA-RNTI generation parameter K in a cell in RMSI or other public messages, and the UE in the cell performs the above formula (3) according to the received K. Calculation.
  • cell related parameters for example, K
  • it can take into account the available RA-RNTI, Temporary C-RNTI, C-RNTI, etc., and can also refer to factors such as the cell's LBT passing probability.
  • gNB For example, it takes an average of 22ms for gNB to send RA-RNTI scrambled DCI several times (such as 100 times), then gNB updates K to 200 and sends it in a broadcast message; for example, it takes 28ms on average for gNB to send RA-RNTI scrambled DCI. Then gNB updates K to 240 and sends it in a broadcast message.
  • the method includes:
  • the gNB sends a second indication, where the second indication is used to indicate the value of K or indicate the maximum value of the RAR window.
  • the NR-U UE receives the second indication to obtain the value of K, or obtain the value of K corresponding to the maximum value of the RAR window.
  • the sending process of step 301 is not required.
  • the above method also includes:
  • the NRU RA-RNTI can be generated in combination with other embodiments.
  • the value of t_id will be greater than 80, and it is necessary to further define how the UE obtains the t_id parameter corresponding to the RO:
  • Method 1 Provide a fixed mapping relationship directly in the standard.
  • the value of t_id has a mapping relationship with the frame number of the system where the RO is located, or the value of t_id includes multiple t_id segments, and each t_id segment corresponds to a system where the RO is located. Frame number.
  • Example 1 RAR window length is 20ms, the value of t_id for odd system frames is 0-79, and the value of t_id for even system frames
  • Method 2 The gNB semi-statically configures the t_id parameter according to the availability of RA-RNTI in the cell.
  • the availability of RA-RNTI mainly refers to which RNTIs in the cell are still idle and can be set as RA-RNTI.
  • the above static configuration may be that the UE's size of x may be notified through broadcast signaling such as RMSI/OSI or RRC dedicated signaling. Calculate t_id according to x by the following formula:
  • the length of the RAR window is 30ms
  • the UE can use the following formula when calculating its RA-RNTI:
  • the situation of sending the preamble in system frame 3 is similar to that in system frame 0, and will not be repeated here.
  • the situation of sending the preamble in system frame 3 is similar to that in system frame 0, and will not be repeated here.
  • the NRU is still adopted.
  • the search space/time-frequency resources of the UE are limited in this embodiment. Specifically, including:
  • the UE After the UE succeeds in the LBT, the UE will randomly select a Preamble and available random access time slots for sending the Preamble according to the system configuration information.
  • the gNB calculates the same RA-RNTI using the same method described above, and uses the RA-RNTI to scramble the PDCCH.
  • the UE only detects and tries to receive the PDCCH scrambled with the aforementioned RA-RNTI sent by the gNB within a relatively limited time window (RAR).
  • RAR time window
  • all system frames can be recorded as N groups according to the law of average dispersion.
  • the UE sends Preamble in a certain system frame group.
  • the UE only performs RAR detection in the RAR corresponding to one group of system frames, and does not need to be RAR detection is performed within the system frame of the group.
  • N is an integer greater than or equal to 2.
  • the system frames can be grouped according to mod (index, N) or mod (index-offset, N) (offset is a fixed subframe/system frame offset).
  • the UE uses its RA-RNTI only in the even system frame or only in the odd system frame Come blindly check the corresponding RAR.
  • the preamble is sent in an even-numbered system frame, and the PDCCH is only blindly detected in each subsequent even-numbered system frame; and the preamble is sent in an odd-numbered system frame, and the PDCCH is only blindly detected in each subsequent odd-numbered system frame .
  • the maximum RAR window length that can be supported becomes 20 ms without changing the RA-RNTI calculation method.
  • the UE sends a Preamble in a system frame with a frame number of 4 for initial access, and then the UE will only perform RAR detection in a system frame with an even number.
  • the gNB can also configure the UE to perform RAR detection in an odd numbered system frame. In this method, all system frames are equally divided into two groups (odd-numbered system frames and even-numbered system frames), and the UE sends Preamble in different system frames, and RAR detection is only performed in one group of system frames.
  • all system frames can be grouped into four groups.
  • the system frame number is index
  • the UE sends the Preamble in group 0 (in the system frame with frame number 4) for initial access, and then the UE only performs the preamble in group 0 (with the sequence number 8, 12...system frame) RAR detection.
  • the gNB can also configure PDCCH search spaces corresponding to different system frames/subframes. After sending the preamble, the UE will only detect its corresponding RAR in the specific search space configured by the gNB to ensure that the RAR corresponding to other UEs will not be detected by mistake .
  • the length of the NRU RAR window is greater than 10 ms and less than 20 ms.
  • the NRU UE does not need to perform PRACH on the secondary uplink carrier.
  • formula (2a) may be used to generate NR RA-RNTI.
  • RA-RNTI 1+s_id+14 ⁇ t_id+14 ⁇ 80 ⁇ f_id+14 ⁇ 80 ⁇ 8 ⁇ ul_carrier_id(2a)
  • s_id is used to indicate that the sending preamble occupies the first subframe start symbol number, and its value range It is 0 ⁇ s_id ⁇ 14.
  • t_id is used to indicate that the preamble transmission resource occupies the first subframe number, and its value range is 0 ⁇ t_id ⁇ 80.
  • f_id indicates the number of the preamble transmission resource in the frequency domain, and its value range is 0 ⁇ f_id ⁇ 8.
  • the ul_carrier_id indication information in the NR RA-RNTI calculation formula (2a) is used to indicate which 10ms time period (in the system frame) of the RAR window the Preamble received by the gNB is located, that is, the position of the Preamble in the RAR window information.
  • Using the above formula (2a) can ensure that the RA-RNTI does not repeat in the 20ms RAR window.
  • ul_carrier_id when the UE sends a Preamble in an even-numbered system frame, the value of ul_carrier_id is 0, and when the Preamble is sent in an odd-numbered system frame, the value of ul_carrier_id is 1; or vice versa;
  • the gNB may also inform the UE of the value of ul_carrier_id in the odd/even system frame in the system information (RMSI/OSI) or RRC signaling, and the UE calculates its own RA-RNTI according to the gNB indication information.
  • RMSI/OSI system information
  • RRC Radio Resource Control
  • NR supports PRACH transmission with a maximum subcarrier spacing of 120kHz, while in this embodiment, NR-U PRACH transmission only supports a maximum subcarrier spacing of 60kHz.
  • formula (3a) or (3b) can be used to generate NR-U RA-RNTI:
  • RA-RNTI 1+s_id+14 ⁇ t_id+14 ⁇ 40 ⁇ f_id+14 ⁇ 40 ⁇ 8 ⁇ ul_carrier_id(3a)
  • s_id is used to indicate that the sending preamble occupies the first subframe start symbol number, and its value range is 0 ⁇ s_id ⁇ 14.
  • t_id is used to indicate that the preamble transmission resource occupies the first subframe number, and its value range is 0 ⁇ t_id ⁇ 80.
  • f_id indicates the number of the preamble transmission resource in the frequency domain, and its value range is 0 ⁇ f_id ⁇ 8.
  • ul_carrier_id is used to indicate the uplink carrier used for preamble transmission, ‘0’ means normal uplink carrier, and ‘1’ means auxiliary uplink carrier. Therefore, without repeating it, the NR-U RA-RNTI calculated by the above formula (3a) can be guaranteed not to be repeated within the 20ms RAR window.
  • RA-RNTI 1+s_id+14 ⁇ t_id+14 ⁇ 40 ⁇ f_id+14 ⁇ 40 ⁇ 8 ⁇ ul_carrier_id(3b)
  • the resource used for PRACH transmission can be the start of any symbol of any subframe in any system frame.
  • the NRU PRACH transmission resource location is restricted, and this embodiment includes:
  • Step 601 After the LBT succeeds, the NRU UE randomly selects a preamble according to the system configuration information.
  • the NRU UE only allows preamble transmission (PRACH transmission) in some subframes (that is, less than 10 subframes) in each system frame. . Or, only the NRU UE is allowed to perform PRACH transmission in a subframe at a specific position in each system frame.
  • the UE can obtain its own RA-RNTI (Random Access Network Identity) according to the time and frequency domain position of the selected random access slot.
  • RA-RNTI Random Access Network Identity
  • the method for generating RA-RNTI can adopt the existing technology, namely formula (2), or alternatively, one of the methods mentioned in the foregoing embodiments 1 to 5 can also be adopted.
  • the first column in Table 2 is the RACH configuration index number configured by the gNB for the UE; the second column is the Preamble type; the 3-4 columns are the periodic parameters of the RACH resource, where "1 0" means the system frame number divided by System frames with more than 1 0 are configured with RACH resources, that is, RACH resources are configured in each system frame.
  • the fifth column in Table 1 is used to indicate which subframes of each system frame are configured with RCACH resources.
  • NRU UE is configured with the RACH index number 105, only some NRU UEs are allowed to perform PRACH in each subframe with an even number of system frame numbers, such as (0, 2, 4, 6, 8). send.
  • PRACH transmission may be performed only in subframes with an odd sequence number of each system frame, such as (1, 3, 5, 7, 9). In this case, the same number of available t_id indications can be used for different situations.
  • the produced RA-RNTI is guaranteed to be unique at least within a 20ms window under the condition that other parameters remain unchanged.
  • the first column is the different values of t_id
  • the second column is the system frame and subframe information corresponding to the t_id value when the PRACH transmission position is not limited
  • the third column is when the PRACH transmission position is limited to an even number, different systems The value of t_id corresponding to the PRACH resource in the frame and subframe.
  • Steps 602-605 are similar to the aforementioned steps 102-105, and will not be repeated here.
  • steps 602-605 one or more of the foregoing various embodiments can be combined to effectively extend the duration of the NRU RAR window to ensure that the RA-RNTI calculation is not repeated in the extended RAR window. It prevents the UE from misdetecting RAR information, causing subsequent random access collisions, and reducing access delay and access efficiency.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center integrated with one or more available media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)).

Landscapes

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

Abstract

一种RA-RNTI处理方法，NR-U UE在LBT成功后，随机选择一个前导码Preamble，选择可用的随机接入时频资源RO；在所述选择的RO上发送所述Preamble；基于所述RO生成RA-RNTI。具体的，可以接收网络装置发送的第一指示，所述第一指示用于指示RAR的时间信息或者位置信息；所述NR-U UE仅在所述第一指示指示的时间窗(RAR)内检测PDCCH，所述PDCCH由所述gNB采用相同的RA-RNTI进行加扰。

Description

一种RA-RNTI处理方法和装置
本申请要求于2019年1月24日提交中国专利局、申请号为201910069184.X、发明名称为“一种RA-RNTI处理方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及无线通信技术领域，尤其涉及一种RA-RNTI处理方法和装置。
背景技术
在小区搜索过程之后，UE已经与小区取得了下行同步，因此UE能够接收下行数据。但UE只有与小区取得上行同步，才能进行上行传输。UE通过随机接入过程(Random Access Procedure)与小区建立连接并取得上行同步。
随机接入的主要目的：(1)获得上行同步；(2)为UE分配一个在小区内的唯一标识C-RNTI。
随机接入过程有2种不同的方式：基于竞争(Contention based)和基于非竞争(Non-Contention based,Contention-Free based)的随机接入过程。对于竞争随机接入，整个流程包含4个步骤，对于非竞争随机接入，整个流程包含2个步骤。RA-RNTI(随机接入网络标识)是在竞争随机接入过程中使用的UE的唯一标识。
LTE系统中，RA-RNTI的计算与UE发送前导序列的时频资源相关，生成公式如下：
RA-RNTI＝1+t_id+10*f_id  (1)
其中t_id指示发送前导码占用第一个子帧编号，其取值范围为0≤t_id<10。f_id指示前导码传输资源在频域的编号，其取值范围为0≤t_id<6。综上可知，RA-RNTI的取值在10ms窗内(即10个子帧内)不会重复。
类似的，在NR系统中，RA-RNTI的计算公式如下：
RA-RNTI＝1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id(2)
其中s_id指示发送前导码占用第一个子帧起始符号编号，其取值范围为0≤s_id<14。t_id指示前导码传输资源占用第一个子帧编号，其取值范围为0≤t_id<80。f_id指示前导码传输资源在频域编号，其取值范围为0≤f_id<8。ul_carrier_id指示前导码传输所使用的上行载波，‘0’表示普通上行载波，‘1’表示辅助上行载波。与LTE取值不同的原因在于NR PRACH传输时频资源理论上可以在每个上行载波的每个系统帧内的每个slot内的每个符号上起始，且PRACH传输支持最大120kHz子载波间隔。
综上可知，以上述公式计算NR RA-RNTI的取值，仅能保证在10ms窗内(即10个子帧内)不会重复。
发明内容
本申请所要解决的技术问题在于减少NR系统中非授权频谱上的RA-RNTI的重复。
一种RA-RNTI处理方法，NR-U UE在LBT成功后，随机选择一个前导码Preamble，选择可用的随机接入时频资源RO；在所述选择的RO上发送所述Preamble；基于所述RO生成RA-RNTI。
较优的，可以接收网络装置发送的第一指示，所述第一指示用于指示RAR的时间信息或者位置信息；所述NR-U UE仅在所述第一指示指示的时间窗(RAR)内检测PDCCH，所述PDCCH由所述gNB采用相同的RA-RNTI进行加扰。其中，所述第一指示承载于DCI中。或者，所述 第一指示承载于RAR MAC CE中。所述基于所述RO生成RA-RNTI可以采用各种方法，例如，根据下述公式之一生成RA-RNTI：
RA-RNTI＝1+s_id+14×t_id+14×K×f_id+14×K×8×ul_carrier_id(3)
上述公式中的s_id指示发送前导码占用第一个子帧起始符号编号，其取值范围为0≤s_id<14。t_id指示前导码传输资源占用第一个子帧编号，其取值范围为0≤t_id<80。f_id指示前导码传输资源在频域编号，其取值范围为0≤f_id<8。ul_carrier_id指示前导码传输所使用的上行载波，‘0’表示普通上行载波，‘1’表示辅助上行载波；所述K为与所述RAR窗口的最大值对应的参数；
或者，
RA-RNTI＝1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id(2a)
NR RA-RNTI计算公式(2a)中的s_id，t_id，f_id等参数的功能与公式(2)中相同；s_id用于指示发送前导码占用第一个子帧起始符号编号，其取值范围为0≤s_id<14。t_id用于指示前导码传输资源占用第一个子帧编号，其取值范围为0≤t_id<80。f_id指示前导码传输资源在频域编号，其取值范围为0≤f_id<8。但是，NR RA-RNTI计算公式(2a)中的ul_carrier_id指示信息，用于指示gNB收到的Preamble在RAR窗口内的位置信息。当然，还可以是实施方式中提到的公式(2)，公式(3a)或者(3b)等等，此处不赘述。
在其他的例子中，也可以把所有系统帧按照平均分散的规律记为N组，仅在其中一组系统帧对应的RAR内进行RAR检测,不需要在其他组的系统帧内进行RAR检测；N为大于等于2的整数。或者，在另一些例子中，所述选择可用的随机接入时频资源RO具体为：在为所述NRU UE的配置的一个系统帧内的多个子帧内选择一个子帧，在所述选择的子帧进行所述preamble的发送；所述多个子帧少于10个。
在另一方面，提供了网络侧装置上的RA-RNTI处理方法，此处不赘述
在其他方面，本申请还提供可以执行前述各个方法的装置，计算机可读存储介质等等。
实施本申请实施例，针对非授权频段的使用，可实现在满足ESTI的OCB要求的基础上，提高上行资源调度的灵活性。进一步的，还可以提高资源利用率。
附图说明
为了更清楚地说明本申请实施例或背景技术中的技术方案，下面将对本申请实施例或背景技术中所需要使用的附图进行说明。
图1是本申请涉及的一种现有资源分配方式的示意图；
图2是本申请涉及的一种无线通信系统的架构示意图；
图3是本申请的一个实施例提供的终端的硬件架构示意图；
图4是本申请的一个实施例提供的基站的硬件架构示意图；
图5是本申请的一个实施例提供的NR-U UE随机接入过程的流程示意图；
图6是本申请一个实施例提供的NRU RAR MAC简单示意图；
图7是本申请的一个实施例提供的NRU SF indication子帧头示意图；
图8本申请的一个实施例提供的一种NRU RA-RNTI检测示意图。
具体实施方式
本申请的实施方式部分使用的术语仅用于对本申请的具体实施例进行解释，而非旨在限定本申请。
为了方便后续描述，本文缩略语和关键术语可以参考下表：
Figure PCTCN2020073886-appb-000001
为了便于了解本申请实施，首先介绍本申请实施例涉及的无线通信系统。
参考图2，图2示出了本申请涉及的无线通信系统200。无线通信系统200可以工作在授权频段，也可以工作在非授权频段。可以理解的，非授权频段的使用可以提高无线通信系统200的系统容量。如图2所示，无线通信系统200包括：一个或多个网络设备201，例如基站，NodeB、eNodeB或者WLAN接入点、无线中继节点、无线回传节点，一个或多个终端(Terminal)203，以及核心网215。其中：
网络设备201可用于在基站控制器(未示出)的控制下与终端203通信。在一些实施例中，所述基站控制器可以是核心网230的一部分，也可以集成到基站201中。
网络设备201可用于通过回程(backhaul)接口(如S1接口)213向核心网215传输控制信息(control information)或者用户数据(user data)。
网络设备201可以通过一个或多个基站天线来和终端203进行无线通信。各个基站201均可以为各自对应的覆盖范围207提供通信覆盖。接入点对应的覆盖范围207可以被划分为多个扇区(sector)，其中，一个扇区对应一部分覆盖范围(未示出)。
网络设备201与基站201之间也可以通过回程(backhaul)链接211，直接地或者间接地，相互通信。这里，所述回程链接211可以是有线通信连接，也可以是无线通信连接。
网络设备201，还可以是云无线接入网络(cloud radio access network，CRAN)场景下的无线控制器。网络设备201还可以是5G网络中的网络设备或未来演进网络中的网络设备；还可以是可穿戴设备或车载设备等。网络设备201还可以是小站，传输节点(transmission reference point，TRP)等。当然不申请不限于此。
在本申请的一些实施例中，网络设备201可以包括：基站收发台(Base Transceiver Station)，无线收发器，一个基本服务集(Basic Service Set，BSS)，一个扩展服务集(Extended Service Set，ESS)，NodeB，eNodeB等等。无线通信系统200可以包括几种不同类型的基站201，例如宏基站(macro base station)、微基站(micro base station)等。基站201可以应用不同的无线技术，例如小区无线接入技术，或者WLAN无线接入技术。
终端203可以分布在整个无线通信系统200中，可以是静止的，也可以是移动的。可以部署在陆地上，包括室内或室外、手持、穿戴或车载；也可以部署在水面上(如轮船等)；还可以部署在空中(例如飞机、气球和卫星上等)。所述终端设备可以是手机(mobile phone)、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(Virtual Reality，VR)终端设备、增强现实(Augmented Reality，AR)终端设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等等。本申请的实施例对应用场景不做限定。终端设备有时也可以称为用户设备(user equipment，UE)、接入终端设备、UE单元、UE站、移动站、移动台、远方站、远程终端设备、移动设备、UE终端设备、终端设备、无线通信设备、UE代理或UE装置等。在本申请的一些实施例中，终端203可以包括：移动设备，移动台(mobile station)，移动单元(mobile unit)，无线单元，远程单元，用户代理，移动客户端等等。
本申请实施例中，无线通信系统200可以是能够工作在非授权频段的LTE通信系统，例如LTE-U，也可以是能够工作在非授权频段的5G以及未来新空口，例如NR-U等通信系统。无线通信系统200可以采用授权辅助接入(LAA)方案来处理终端在非授权频段上的接入。在LAA方案中，主小区(Primary Cell)工作在授权频段，传送关键的消息和需要服务质量保证的业务；辅小区(Secondary Cell)工作在非授权频段，用于实现数据平面性能的提升。
本申请实施例中，无线通信系统200可以支持多载波(multi-carrier)(不同频率的波形信号)操作。多载波发射器可以在多个载波上同时发射调制信号。例如，每一个通信连接205都可以承载利用不同无线技术调制的多载波信号。每一个调制信号均可以在不同的载波上发送，也可以承载控制信息(例如参考信号、控制信道等)，开销信息(Overhead Information)，数据等等。
另外，无线通信系统200还可以包括WiFi网络。为了实现运营商网络和WiFi网络(工作在非授权频谱)之间的和谐共存，无线通信系统200可采用先听后说(Listen before Talk，LBT)机制。例如，在无线通信系统200中，一些终端203可以通过WiFi通信连接217连接WiFi接入点209来使用非授权频谱资源，一些终端203也可以通过移动通信连接205连接基站201来使用非授权频谱资源。在使用非授权频段时，任何设备必须先监听，看看该频段是否被占用，如果该频段不忙，才可以占用并传输数据。
参考图3，图3示出了本申请的一些实施例提供的终端300。如图3所示，终端300可包括：输入输出模块(包括音频输入输出模块318、按键输入模块316以及显示器320等)、用户接口302、一个或多个终端处理器304、发射器306、接收器308、耦合器310、天线314以及存储器312。这些部件可通过总线或者其它方式连接，图3以通过总线连接为例。其中：
通信接口301可用于终端300与其他通信设备，例如基站，进行通信。具体的，所述其他通信设备可以是图4所示的基站400。具体的，通信接口301可包括：全球移动通信系统(Global System for Mobile Communication，GSM)(2G)通信接口、宽带码分多址(Wideband Code Division Multiple Access，WCDMA)(3G)通信接口，以及长期演进(Long Term Evolution，LTE)(4G)通信接口等等中的一种或几种，也可以是4.5G、5G或者未来新空口的通信接口。不限于无线通信接口，终端300还可以配置有有线的通信接口301，例如局域接入网(Local Access Network，LAN)接口。
天线314可用于将传输线中的电磁能转换成自由空间中的电磁波，或者将自由空间中的电磁波转换成传输线中的电磁能。耦合器310用于将天线314接收到的移动通信信号分成多路，分配给多个的接收器308。
发射器306可用于对终端处理器304输出的信号进行发射处理，例如将该信号调制在授权频段的信号，或者调制在非授权频段的信号。在本申请的一些实施例中，发射器206可包括非授权频谱发射器3061和授权频谱发射器3063。其中，非授权频谱发射器3061可以支持终端300在一个或多个非授权频谱上发射信号，授权频谱发射器3063可以支持终端300在一个或多个授权频谱上发射信号。
接收器308可用于对天线314接收的移动通信信号进行接收处理。例如，接收器308可以解调已被调制在非授权频段上的接收信号，也可以解调调制在授权频段上的接收信号。在本申请的一些实施例中，接收器308可包括非授权频谱接收器3081和授权频谱接收器3083。其中，非授权频谱接收器3081可以支持终端300接收调制在非授权频谱上的信号，授权频谱 接收器3083可以支持终端300接收调制在授权频谱上的信号。
在本申请的一些实施例中，发射器306和接收器308可看作一个无线调制解调器。在终端300中，发射器306和接收器308的数量均可以是一个或者多个。
除了图3所示的发射器306和接收器308，终端300还可包括其他通信部件，例如GPS模块、蓝牙(Bluetooth)模块、无线高保真(Wireless Fidelity，Wi-Fi)模块等。不限于上述表述的无线通信信号，终端300还可以支持其他无线通信信号，例如卫星信号、短波信号等等。不限于无线通信，终端300还可以配置有有线网络接口(如LAN接口)来支持有线通信。
所述输入输出模块可用于实现终端300和用户或者外部环境之间的交互，可主要包括音频输入输出模块318、按键输入模块316以及显示器320等。具体的，所述输入输出模块还可包括：摄像头、触摸屏以及传感器等等。其中，所述输入输出模块均通过用户接口302与终端处理器304进行通信。
存储器312与终端处理器304耦合，用于存储各种软件程序和或者或多组指令。具体的，存储器312可包括高速随机存取的存储器，并且也可包括非易失性存储器，例如一个或多个磁盘存储设备、闪存设备或其他非易失性固态存储设备。存储器312可以存储操作系统(下述简称系统)，例如ANDROID，IOS，WINDOWS，或者LINUX等嵌入式操作系统。存储器312还可以存储网络通信程序，该网络通信程序可用于与一个或多个附加设备，一个或多个终端设备，一个或多个网络设备进行通信。存储器312还可以存储用户接口程序，该用户接口程序可以通过图形化的操作界面将应用程序的内容形象逼真的显示出来，并通过菜单、对话框以及按键等输入控件接收用户对应用程序的控制操作。
在本申请的一些实施例中，存储器312可用于存储本申请的一个或多个实施例提供的资源分配方法在终端300侧的实现程序。关于本申请的一个或多个实施例提供的资源分配方法的实现，请参考后续实施例。
终端处理器304可用于读取和执行计算机可读指令。具体的，终端处理器304可用于调用存储于存储器312中的程序，例如本申请的一个或多个实施例提供的资源分配方法在终端300侧的实现程序，并执行该程序包含的指令。
可以理解的，终端300可以是图2示出的无线通信系统200中的终端203，可实施为移动设备，移动台(mobile station)，移动单元(mobile unit)，无线单元，远程单元，用户代理，移动客户端等等。
需要说明的，图3所示的终端300仅仅是本申请实施例的一种实现方式，实际应用中，终端300还可以包括更多或更少的部件，这里不作限制。
参考图4，图4示出了本申请的一些实施例提供的基站400。如图4所示，基站400可包括：通信接口403、一个或多个基站处理器401、发射器407、接收器409、耦合器411、天线413和存储器405。这些部件可通过总线或者其它方式连接，图4以通过总线连接为例。其中：
通信接口403可用于基站400与其他通信设备，例如终端设备或其他基站，进行通信。具体的，所述终端设备可以是图3所示的终端300。具体的，通信接口403可包括：全球移动通信系统(GSM)(2G)通信接口、宽带码分多址(WCDMA)(3G)通信接口，以及长期演进(LTE)(4G)通信接口等等中的一种或几种，也可以是4.5G、5G或者未来新空口的通信接口。 不限于无线通信接口，基站400还可以配置有有线的通信接口403来支持有线通信，例如一个基站400与其他基站400之间的回程链接可以是有线通信连接。
天线413可用于将传输线中的电磁能转换成自由空间中的电磁波，或者将自由空间中的电磁波转换成传输线中的电磁能。耦合器411可用于将移动通信号分成多路，分配给多个的接收器409。
发射器407可用于对基站处理器401输出的信号进行发射处理，例如将该信号调制在授权频段的信号，或者调制在非授权频段的信号。在本申请的一些实施例中，发射器407可包括非授权频谱发射器4071和授权频谱发射器4073。其中，非授权频谱发射器4071可以支持基站400在一个或多个非授权频谱上发射信号，授权频谱发射器4073可以支持基站400在一个或多个授权频谱上发射信号。
接收器409可用于对天线413接收的移动通信信号进行接收处理。例如，接收器409可以解调已被调制在非授权频段上的接收信号，也可以解调调制在授权频段上的接收信号。在本申请的一些实施例中，接收器409可包括非授权频谱接收器4091和授权频谱接收器4093。其中，非授权频谱接收器4091可以支持基站400接收调制在非授权频谱上的信号，授权频谱接收器4093可以支持基站400接收调制在授权频谱上的信号。
在本申请的一些实施例中，发射器407和接收器409可看作一个无线调制解调器。在基站400中，发射器407和接收器409的数量均可以是一个或者多个。
存储器405与基站处理器401耦合，用于存储各种软件程序和或者或多组指令。具体的，存储器405可包括高速随机存取的存储器，并且也可包括非易失性存储器，例如一个或多个磁盘存储设备、闪存设备或其他非易失性固态存储设备。存储器405可以存储操作系统(下述简称系统)，例如uCOS、VxWorks、RTLinux等嵌入式操作系统。存储器405还可以存储网络通信程序，该网络通信程序可用于与一个或多个附加设备，一个或多个终端设备，一个或多个网络设备进行通信。
基站处理器401可用于进行无线信道管理、实施呼叫和通信链路的建立和拆除，并为本控制区内用户设备的过区切换进行控制等。具体的，基站处理器401可包括：管理或者通信模块(Administration Module或者Communication Module，AM或者CM)(用于话路交换和信息交换的中心)、基本模块(Basic Module，BM)(用于完成呼叫处理、信令处理、无线资源管理、无线链路的管理和电路维护功能)、码变换及子复用单元(Transcoder and SubMultiplexer，TCSM)(用于完成复用解复用及码变换功能)等等。
本申请实施例中，基站处理器401可用于读取和执行计算机可读指令。具体的，基站处理器401可用于调用存储于存储器405中的程序，例如本申请的一个或多个实施例提供的资源分配方法在基站400侧的实现程序，并执行该程序包含的指令。
可以理解的，基站400可以是图2示出的无线通信系统200中的基站201，可实施为基站收发台，无线收发器，一个基本服务集(BSS)，一个扩展服务集(ESS)，NodeB，eNodeB等等。基站400可以实施为几种不同类型的基站，例如宏基站、微基站等。基站400可以应用不同的无线技术，例如小区无线接入技术，或者WLAN无线接入技术。
需要说明的，图4所示的基站400仅仅是本申请实施例的一种实现方式，实际应用中，基站400还可以包括更多或更少的部件，这里不作限制。
可以替换的，终端300或者基站400也可配置成通用处理系统，例如通称为芯片，该通 用处理系统包括:提供处理器功能的一个或多个微处理器；以及提供存储介质的至少一部分的外部存储器，所有这些都通过外部总线体系结构与其它支持电路连接在一起。
可替换的，终端300或者基站400可以使用下述来实现:具有处理器、总线接口、或者用户接口的ASIC(专用集成电路)；以及集成在单个芯片中的存储介质的至少一部分，或者，终端300或者基站400可以使用下述来实现:一个或多个FPGA(现场可编程门阵列)、PLD(可编程逻辑器件)、控制器、状态机、门逻辑、分立硬件部件、任何其它适合的电路、或者能够执行本发明通篇所描述的各种功能的电路的任意组合。其中，处理器负责管理总线和一般处理(包括执行存储在存储介质上的软件)。处理器可以使用一个或多个通用处理器和/或专用处理器来实现。处理器的例子包括微处理器、微控制器、DSP处理器和能够执行软件的其它电路。应当将软件广义地解释为表示指令、数据或其任意组合，而不论是将其称作为软件、固件、中间件、微代码、硬件描述语言还是其它。
本具体实施方式主要涉及竞争随机接入流程，仅以NR-U UE和gNB为终端和网络装置的举例，其流程如图5所示。
步骤101：NR-U UE在LBT成功后，根据系统配置信息随机选择一个Preamble，以及，选择可用随机接入时隙，在该可用随机接入时隙发送Preamble。UE可以根据选择的随机接入时隙的时间和频域位置获取自己的RA-RNTI(随机接入网络标识)。其中，UE发送Preamble的时频资源称为RACH occasion，简称RO。相应的，gNB接收前述NR-U UE发送的Preamble。
具体的，较优的生成RA-RNTI的方式可以采用后续各个实施例中提到的方法中的一种。一般的，系统配置信息包括Preamble的设置信息，配置RO的信息，SSB和RO对应关系，t_id取值，RAR window最大持续时间，等等。一般的方案中，可用的随机接入时隙，可能是全部可用的随机接入时隙，特殊的情况下，也可能是特定的部分随机接入时隙，例如后续的实施例六。
步骤102：具体的，gNB采用步骤101中相同的方法(根据接收到Preamble的时频资源)得到相同的RA-RNTI，并在LBT成功后发送采用该RA-RNTI加扰的PDCCH。NR-U UE在为该NR-U UE配置的检测时间范围内检测或者尝试接收gNB发送的用与步骤101中得到的相同的RA-RNTI加扰的PDCCH。具体的，PDCCH信道主要承载着PUSCH和PDSCH信道控制信息(DCI)，不同UE的PDCCH信息通过其对应的RA-RNTI信息区分，即其DCI的CRC由RA-RNTI加扰。
在unlicensed中，gNB发送上述PDCCH受到LBT影响，即存在gNB准备好上述PDCCH但由于信道忙而无法发送的情况。为了降低LBT对PDCCH发送/接收的影响，在NR-U中把RAR窗口最大值延长到大于10ms，以使gNB有更多的机会发送PDCCH。但NR RA-RNTI的计算方式只能保证其在10ms内仅有唯一性，因此本较优的实施方式可以用于解决UE在大于10ms的RAR窗口内如何正确判断gNB发送由RA-RNTI加扰的PDCCH(包含DCI等)是否是给自己的。具体的，上述为NR-U UE配置的检测时间范围包括多种情况，可以参考后续各个实施方式一至六中的说明；其中，如果无特殊的说明，该检测时间范围是指全部的RAR时间窗。即UE在RAR时间窗内检测，直到检测到自己的PDCCH。具体而言，NR-U UE通过采用自己的RA-RNTI尝试解扰接收到的一个或者多个PDCCH，能成功解扰的PDCCH即该NR-U UE的PDCCH。
可选的，各个实施方式中还包括如下步骤103-105，但由于相关步骤不再涉及RA-RNTI，因而本文将不详细赘述。
步骤103：如果成功接收PDCCH，则UE解码PDSCH(Physical downlink shared channel:下行物理共享信道)携带的信息；如果在检测时间范围内没有检测到上述PDCCH，则该NR-U UE 调整自己的发射功率在下个系统配置的随机接入时隙重新进行步骤101。
步骤104：上述PDSCH中包含NR-U UE发送Msg3的时频资源信息和分配给NR-U UE的临时网络标识(TC-RNTI:Temporary Cell Radio Network temporary identification)，UE在对应的时频资源发送Msg3，并携带NR-U UE全网唯一的网络标识用于步骤104中进行随机成功确认。
步骤105：NR-U UE会检测用步骤103中NR-U UE临时网络标识加扰的PDCCH。如果成功，它会解码PDSCH中携带的信息。如果该信息携带了自己在步骤103中发送的全网唯一标识，则随机接入成功，NR-U UE向gNB发送确认(ACK)。如果不是自己的标识，则随机接入失败，重复步骤101。
实施方式一
在本实施方式中，gNB通过指示RAR的时间信息或者位置信息，避免可能因RA-RNTI不唯一导致的误检测。
201.gNB发送第一指示，所述第一指示用于指示RAR的时间信息或者位置信息，也就是说，指示NR-U UE对应的RAR属于RAR窗口的哪一个10ms内或者哪一个系统帧内。NR-U UE接收并获取该第一指示。一般的，1个系统帧持续10ms。
相应的，上述方法还包括:
202.NR-U UE在LBT成功后，UE会根据系统配置信息随机选择一个Preamble以及可用随机接入时隙用于发送Preamble。相应的，gNB接收NR-U UE发送的Preamble。具体的，gNB检测NR-U UE发送的Preamble，当检测到Preamble后会根据检测到该Preamble的时频资源RO确定所述NR-U UE的RA-RNTI。
相应的，NR-U UE也可以根据根据相同的RO信息计算得到RA-RNTI。例如，gNB或者NR-UUE采用RA-RNTI＝1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id(2)生成RA-RNTI。
其中s_id用于指示发送前导码占用第一个子帧起始符号编号，其取值范围为0≤s_id<14。t_id用于指示前导码传输资源占用第一个子帧编号，其取值范围为0≤t_id<80。f_id指示前导码传输资源在频域编号，其取值范围为0≤f_id<8。ul_carrier_id用于指示前导码传输所使用的上行载波，‘0’表示普通上行载波，‘1’表示辅助上行载波。相应的，gNB采用相同的方式生成相同的RA-RNTI。
203.检测RAR，根据第一指示确定是否继续解析该RAR携带的PDCCH。具体的，NR-U UE先确定检测到的某个RAR的第一指示所述指示的时间窗是否与自己发送preamble的时间窗相同，例如位于同一个10ms内，如果是，则继续解析该RAR中携带的PDCCH，以获得PDCCH中承载的PDSCH等信息。如果不是，则放弃解析该RAR，从而很大的程度上减少检测解析资源。
如果NR-U UE继续解析RAR，并能用自己的RA-RNTI成功的解扰某个PDCCH，则该PDCCH为该NR-U UE的PDCCH，则该NR-U UE停止继续检测RAR。
通过上述方法，可以减少UE其他时间内不必要的检测或者不必要的解析，也可以避免在不同的时间窗可能发生的，因不同窗口生成的RA-RNTI重复导致的误检测。在该方法中，生成的RA-RNTI的过程不需要被复杂化。
后续的步骤可以参考前述104-105，此处不再赘述。
在一个例子中，所述第一指示承载于DCI中。
具体的，gNB可以在RA-RNTI加扰的DCI中增加额外比特来指示UE对应的RAR是属于 RAR窗口的哪个10ms内，利用额外指示信息来指示gNB在哪个系统帧内接收到该Preamble。另一方面，gNB或者NR-U UE进行RA-RNTI的生成过程可以采用上述公式(2)，仍保持10ms内唯一。
例如，当RAR窗口最长是20ms时，只需要在DCI中增加1bit来指示gNB是在奇数系统帧还是偶数系统帧接收到该Preamble。也可以通过指示该发送DCI和gNB收到该Preamble的相对时间差，如‘0’表示两者相隔小于10ms，‘1’表示两者相隔时间大于10ms小于20ms。
当RAR窗口大于20ms时，DCI中可采用更多的比特来指示RAR窗时间信息，方法与上述类似，在此不再赘述。例如，2比特最多可以指示40msRAR窗内RA-RNTI的接收情况，3比特最多可以指示80msRAR窗内RA-RNTI的接收情况。
在其他的例子中，可以复用DCI的一个或者多个比特，其中部分值用于指示上述RAR窗口的信息。采用该方式能在指示上述信息的基础上节省一些开销。例如，现有RA-RNTI加扰的DCI1_0中有16个预留比特(reserved bit)，可以根据最大支持RAR窗口时长使用其中的一个或多个预留比特用于上述指示，例如，2,3,4比特。
另一个具体的例子中，所述第一指示承载于RAR MAC CE中。
NRU RAR MAC帧结构如下图6和图7所示。具体的，RAR MAC CE(control element:控制元素)中包括SF indication子帧头，所述SF indication子帧头用于指示gNB收到的某个Preamble对应的RA-RNTI加扰的PDCCH位于哪个系统帧内，或者，哪一个10ms内；或者，简单的来说，所述SF indication子帧头用于指示UE的PDCCH或者RAR所在的系统帧序号。
SF indication子帧头可以位于BI子帧头和RAPID子帧头之后。为了区别于现有的BI子帧头和RAPID子帧头，SF indication子帧头的前三位bit可以设置为‘101’，剩余5比特bits可用于指示RA-RNTI所处的系统帧序号。5比特可指示最多32个系统帧，即RAR窗最大长度为320ms。
在接收侧，NRU UE接收，NRU UE在检测SF indication子帧头后即可判断后续MAC RAR是否是自己的。进一步的，gNB在RAR MAC PDU指示收到的Preamble可以按照所在帧或者子帧序号进行排序。当UE检测到SFI字段指示的系统帧或者子帧(MAC RAR对应的系统帧或者子帧)大于自己发送Preamble的系统帧号或者子帧号时，不会尝试检测该MAC PDU(physical data unit:物理数据单元)剩余sub PDU，以达到节省UE能量的目的。例如，UE 1在系统帧5发送了Preamble，并在系统帧10收到了其对应RA-RNTI加扰的RAR(PDCCH)。但SF indication子帧头指示后续的MAC RAR对应gNB在系统帧6和8收到的RA-RNTI(根据收到preamble的时频资源计算得到的RA-RNTI)，则此时UE不会继续解析后续的MAC信息，并认为gNB没收到它发送的preamble。现有技术中，NR UE会盲检对应RA-RNTI加扰的DCI指示的MAC PDU的所有subPDU，以确保gNB发给自己的RAR信息没有被遗漏。
实施方式二
具体而言，根据标准3GPP 38.321的文本，gNB/UE生成RA-RNTI时，RA-RNTI的取值范围为0001-FFEF(65519)
Figure PCTCN2020073886-appb-000002
Figure PCTCN2020073886-appb-000003
由下述公式可知，10ms窗内RA-RNTI取值范围为1-17920(1+13+14*13+14*80*7+14*80*8*1),即可保证最大36ms的窗口内RA-RNTI不重复。
RA-RNTI＝1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id
一种较差的实施方式中，当RAR window持续时间大于10ms时，可以直接把t_id的取值由现在的80拓展到320。If the RAR window size is extended to 40msec,the value rangeof t_id becomes 0≤t_id<320 and the maximum RA-RNTI value becomes(71680-1)which is larger than the 16-bit RNTI can provide。
但是直接把t_id拓展到320用于指示40ms内的RO起始subframe idx时存在如下问题：当t_id＝240，f_id＝0时，用上述公式计算出来的RA-RNTI与t_id＝160,f_id＝1以及t_id＝80,f_id＝2t_id＝0,f_id＝3时的RA-RNTI一样(假设其他参数取值相同)。这样会导致在不同10ms窗内上述RO成功发送Preamble的多个UE认为用上述RA-RNTI加扰RAR是发给自己的，并在RAR指示资源上发送Msg3，增大其碰撞概率，降低系统接入效率。
在较优的实施方式中，使用NR RA-RNTI的计算公式(3)及相应的参数K，使其更加适用于RAR窗口长大于10ms时的场景
RA-RNTI＝1+s_id+14×t_id+14×K×f_id+14×K×8×ul_carrier_id(3)
上述公式中的s_id指示发送前导码占用第一个子帧起始符号编号，其取值范围为0≤s_id<14。t_id指示前导码传输资源占用第一个子帧编号，其取值范围为0≤t_id<80。f_id指示前导码传输资源在频域编号，其取值范围为0≤f_id<8。ul_carrier_id指示前导码传输所使用的上行载波，‘0’表示普通上行载波，‘1’表示辅助上行载波。上述公式与LTE取值不同的原因在于NR PRACH传输时频资源理论上可以在每个上行载波的每个系统帧内的每个slot内的每个符号上起始，且PRACH传输支持最大120kHz子载波间隔。其中，K的取值可以根据RAR窗口的最大值的不同而不同，参考表1。
具体的，一个例子中，相关标准中可以规定RAR窗口最大值为表1中的任意一个或者多个，上述K的取值则为表1中对应的取值。表1中还给出了相应的方案下该公式(3)算出的RNTI的取值范围。
表1
Figure PCTCN2020073886-appb-000004
Figure PCTCN2020073886-appb-000005
较优的另一例子中，gNB可以在RMSI或其他公共消息中静态/半静态配置一个小区中的的RA-RNTI生成参数K，小区中的UE根据接收到的K进行上述公式(3)的计算。这样，gNB在配置cell的相关参数时(例如K)，可以同时兼顾可用RA-RNTI，Temporary C-RNTI,C-RNTI等,还可以参考小区的LBT通过概率等因素。例如，gNB发送若干次(如100次)RA-RNTI加扰的DCI平均需要22ms，则gNB更新K为200，并在广播消息中发送；如gNB发送RA-RNTI加扰的DCI平均需要28ms，则gNB更新K为240，并在广播消息中发送。
该方法包括：
301.可选的，gNB发送第二指示，所述第二指示用于指示K的取值或者指示RAR窗口最大值。NR-U UE接收该第二指示，以获取K的取值，或者，获取RAR窗口最大值对应的K的值。当然，如果标准规定一种RAR窗口最大值或者K的取值，则不需要上述步骤301的发送过程。
相应的，上述方法还包括:
302.gNB或者NR-U UE在LBT成功后，采用RA-RNTI＝1+s_id+14×t_id+14×K×f_id+14×K×8×ul_carrier_id(3)以及，接收到的所述K的取值，或者RAR窗口最大值对应的K的取值，生成RA-RNTI。
后续的步骤可以参考前述103-105，此处不再赘述。
另一个例子中，当gNB需要配置的RAR window持续时间大于35ms或通信系统可使用的RNTI数小于上述表格中的所需值时，可结合其他实施例来生成NRU RA-RNTI。
例如，当RAR window大于10ms时，t_id取值会大于80，则需要进一步定义UE如何获取RO对应的t_id参数：
方法一，在标准中直接给出固定映射关系，例如t_id取值与RO所在系统帧号具有映射关系，或者，t_id的取值包括多个t_id分段，各个t_id分段分别对应一个RO所在系统帧号。
例子1，RAR window长度为20ms，奇数系统帧t_id取值为0-79，偶数系统帧t_id取值
为80-159；或者反之。
例子2，RAR window长度为30ms，mod(SFN,3)＝0,t_id取值为0-79；mod(SFN,3)＝1,t_id取值为80-159；mod(SFN,3)＝2,t_id取值为160-239。
方法二，gNB根据本cell中RA-RNTI可用情况来半静态配置t_id参数。RA-RNTI可用情况重要指本cell中哪些RNTI仍然空闲，可以被设为RA-RNTI。上述静态配置可以是，可以通过RMSI/OSI等广播信令或是RRC专属信令告知UE x的大小。通过如下公式根据x算得t_id：
例如RAR window长度为30ms，
mod(SFN-x,3)＝0,t_id取值为0-79；
mod(SFN-x,3)＝1,t_id取值为80-159；
mod(SFN-x,3)＝2,t_id取值为160-239。上述公式中x为整数。
简单的概述为，当RAR window长度为10*y ms，
UE在计算其RA-RNTI时可采用如下公式，
mod(SFN-x,y)＝t,t取值为0,1,..y。t与t_id相关联，如t＝0，t_id取值为0-79；t＝1，t_id取值为80-159；以此类推。
当RAR window为30ms，x取值为0，则UE在系统帧0发送Preamble，t＝mod(0,3)＝0,t_id取值为0-79；当UE在系统帧1发送Preamble，t＝mod(1,3)＝1,t_id取值为80-159；当UE在系统帧2发送Preamble，t＝mod(2,3)＝2,t_id取值为160-239。在系统帧3发送preamble情况与在系统帧0类似，在此不再赘述。
当RAR window为30ms，x取值为1，则UE在系统帧0发送Preamble，t＝mod(0-1,3)＝2,t_id取值为160-239；当UE在系统帧1发送Preamble，t＝mod(1-1,3)＝0,t_id取值为0-79；当UE在系统帧2发送Preamble，t＝mod(2-1,3)＝1,t_id取值为80-159。在系统帧3发送preamble情况与在系统帧0类似，在此不再赘述。
实施方式三
本实施方式中，NRU仍采用，为了让不同的UE检测自己对应的RAR不发生混淆，在本实施例中UE的搜索空间/时频资源做了限定。具体的，包括：
401.UE在LBT成功后，UE会根据系统配置信息随机选择一个Preamble以及可用随机接入时隙用于发送Preamble。UE可以根据选择的随机接入时隙的时间和频域位置，采用RA-RNTI＝1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id(2)生成RA-RNTI。
401.gNB采用上述相同的方法计算得到相同的RA-RNTI，并以该RA-RNTI对PDCCH进行加扰。
402.UE仅在相对有限的时间窗(RAR)内，检测\尝试接收gNB发送的用上述的RA-RNTI加扰的PDCCH。具体的，可以把所有系统帧按照平均分散的规律记为N组，UE在某一个系统帧组内发送Preamble，该UE仅在其中一组系统帧对应的RAR内进行RAR检测,不需要在其他组的系统帧内进行RAR检测。N为大于等于2的整数。具体的，可以按照mod(index,N)或是mod(index-offset,N)(offset为固定子帧/系统帧偏移)的方式对系统帧进行分组。
例如，当UE在序号为偶数或者奇数的系统帧内的某个子帧对应的PRACH传输时频资源发送preamble后，该UE只在偶数系统帧内或者只在奇数系统帧内使用自己的RA-RNTI来盲检对应的RAR。具体的可以是，在某个偶数系统帧发送preamble，只在后续的各个偶数系统帧内盲检PDCCH；以及，在某个奇数系统帧发送preamble，只在后续的各个奇数系统帧内盲检PDCCH。或者，在某个偶数系统帧发送preamble，只在后续的各个奇数系统帧内盲检PDCCH；以及，在某个奇数系统帧发送preamble，只在后续的各个偶数系统帧内盲检PDCCH。
上述实施方式中，在不改变RA-RNTI计算方式时可以支持最大的RAR窗长变为20ms。如图8上半部分所示，UE在帧号为4的系统帧内发送Preamble用于初始接入，随后UE只会在序号为偶数的系统帧内进行RAR检测。当然，gNB也可以配置该UE在序号为奇数的系统帧内进行RAR检测。该方法中，把所有系统帧平均分成两组(奇数系统帧和偶数系统帧)，UE在不同的系统帧内发送Preamble，只会在其中一组系统帧内进行RAR检测。
另一个例子中，当所需RAR窗口长最大为40ms时，可以把所有系统帧分组为四组。当系统帧号为index时，通过下述公式依次把系统帧分为4组：mod(index,4)＝0,1,2or3，分别记为组0,1,2or3。如图8下半部分所示，UE在组0内(帧号为4的系统帧内)发送Preamble用于初始接入，随后UE仅在组0(序号为8,12…系统帧)内进行RAR检测。当然，gNB也可以配置该UE在序号为(mod(index,4)＝1或2或3的系统帧内进行RAR检测。
此外，gNB还可配置不同系统帧/子帧对应的PDCCH搜索空间，UE在发送preamble后只会在gNB配置的特定搜索空间内检测其对应的RAR，以保证不会误检其它UE对应的RAR。
实施例四
在本实施方式中，NRU RAR窗口长度大于10ms且小于20ms，另外，NRU UE不需要在辅上行载波上进行PRACH。
前述步骤101-102中，可以采用公式(2a)生成NR RA-RNTI。
RA-RNTI＝1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id(2a)
NR RA-RNTI计算公式(2a)中的s_id，t_id，f_id等参数的功能与公式(2)中相同；s_id用于指示发送前导码占用第一个子帧起始符号编号，其取值范围为0≤s_id<14。t_id用于指示前导码传输资源占用第一个子帧编号，其取值范围为0≤t_id<80。f_id指示前导码传输资源在频域编号，其取值范围为0≤f_id<8。但是，NR RA-RNTI计算公式(2a)中的ul_carrier_id指示信息，用于指示gNB收到的Preamble是位于RAR窗口内的哪个10ms时间段内(系统帧内)，即Preamble在RAR窗口内的位置信息。使用上述公式(2a)可以保证20ms的RAR窗口内RA-RNTI不重复。
较优选的，可以在标准中规定在UE在偶数系统帧发送Preamble，则ul_carrier_id取值为0，在奇数系统帧发送Preamble，则ul_carrier_id取值为1；或者反之；
可选的，gNB也可以在系统信息(RMSI/OSI)或RRC信令中告知UE在奇数/偶数系统帧的ul_carrier_id取值，UE根据gNB指示信息来计算自己的RA-RNTI。
实施例五
具体的，NR支持最大120kHz子载波间隔的PRACH传输，而本实施方式中，NR-U PRACH传输只支持最大60kHz子载波间隔，
前述步骤101-102中，可以采用公式(3a)或者(3b)生成NR-U RA-RNTI:
RA-RNTI＝1+s_id+14×t_id+14×40×f_id+14×40×8×ul_carrier_id(3a)
公式(3a)中的s_id，t_id，f_id以及ul_carrier_id与公式(2)中相同，s_id用于指示发送前导码占用第一个子帧起始符号编号，其取值范围为0≤s_id<14。t_id用于指示前导码传输资源占用第一个子帧编号，其取值范围为0≤t_id<80。f_id指示前导码传输资源在频域编号，其取值范围为0≤f_id<8。ul_carrier_id用于指示前导码传输所使用的上行载波，‘0’表示普通上行载波，‘1’表示辅助上行载波。因而不赘述，则通过上述公式(3a)计算的NR-U RA-RNTI可以保证在20ms RAR窗内不重复。
RA-RNTI＝1+s_id+14×t_id+14×40×f_id+14×40×8×ul_carrier_id(3b)
公式(3a)中的s_id，t_id，f_id以及ul_carrier_id与公式(2a)中相同，因而不赘述，在这个公式(3a)的实施方式中，即当ul_carrier_id指示信息也用于指示RAR窗时，可以保证RA-RNTI在40ms窗内不重复。
实施例六
一般的，用于PRACH传输的资源可以是任意系统帧内任意子帧的任意符号开始。但是，在本实施方式中，对NRU PRACH传输资源位置进行了限制，该实施方式包括：
步骤601、NRU UE在LBT成功后，根据系统配置信息随机选择一个Preamble，NRU UE只允许在每个系统帧内的部分子帧(即少于10个子帧)内进行preamble发送(PRACH的发送)。或者，只允许NRU UE在每个系统帧内的特定位置的子帧内进行PRACH发送。UE可以根据选择的随机接入时隙的时间和频域位置获取自己的RA-RNTI(随机接入网络标识)。具体的，生成RA-RNTI的方式可以采用现有技术，即公式(2)，或者，也可以采用前述各个实施例一至五中提到的方法中的一种。
例如，表2中的第1列为gNB配置给UE的RACH配置索引号；第2列为Preamble类型；第3-4列为RACH资源的周期性参数，其中“1 0”表示系统帧号除1余0的系统帧配置有RACH资源，即每个系统帧内都配置了RACH资源。表1中的第5列用于指示每个系统帧的哪些子帧内配置有RCACH资源。
如表2所述，假如NRU UE被配置了索引号为105的RACH,只允许部分NRU UE在每个系统帧序号为偶数例如(0,2,4,6,8)的子帧内进行PRACH发送。对于另一部分NRU UE，可能只在每个系统帧序号为奇数例如(1,3,5,7,9)的子帧内进行PRACH发送。这种情况下，则相同可用t_id指示数量可以针对不同的情况，例如PRACH资源只出现在偶数子帧的情况和奇数子帧的情况下，指示2个系统帧内的PRACH资源所在子帧序号(如表3所示)，在其它参数不变的情况下使得生产的RA-RNTI至少在20ms窗内保证唯一。表3中第1列为t_id的不同取值，第2列为不限定PRACH发送位置时该t_id的值对应的系统帧及子帧信息，第3列为限定PRACH发送位置为偶数时，不同系统帧及子帧中PRACH资源对应的t_id取值。
步骤602-605，与前述步骤102-105类似，此处不赘述。
具体而言，步骤602-605中，可以结合前述各个实施方式中的一种或多种可以有效的延长支持NRU RAR窗的持续时间，保证在延长的RAR窗口内RA-RNTI的计算不重复，避免UE误检RAR信息，造成后续随机接入的碰撞，降低接入时延和接入效率。
表2
Figure PCTCN2020073886-appb-000006
表3
Figure PCTCN2020073886-appb-000007
以上所示例的具体实施方式，对本申请的目的和技术方案进行了进一步详细说明，所应理解的是，以上所述仅为本申请的具体实施方式而已，并不用于限定本申请的保护范围。凡 在本申请的技术方案的基础之上，所做的任何修改、等同替换、改进等，均应包括在本申请的保护范围之内。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本发明实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘Solid State Disk(SSD))等。

Claims (24)

  1. 一种RA-RNTI处理方法，其特征在于，
    NR-U UE在LBT成功后，随机选择一个前导码Preamble，选择可用的随机接入时频资源RO；
    在所述选择的RO上发送所述Preamble；
    基于所述RO生成RA-RNTI。
  2. 根据权利要求1所述的方法，
    接收网络装置发送的第一指示，所述第一指示用于指示RAR的时间信息或者位置信息；
    所述NR-U UE仅在所述第一指示指示的时间窗(RAR)内检测PDCCH，所述PDCCH由所述gNB采用相同的RA-RNTI进行加扰。
  3. 根据权利要求2所述的方法，
    所述第一指示承载于DCI中。
  4. 根据权利要求2所述的方法，
    所述第一指示承载于RAR MAC CE中。
  5. 根据权利要求1-4任一所述的方法，所述基于所述RO生成RA-RNTI包括：根据下述公式之一生成RA-RNTI：
    RA-RNTI＝1+s_id+14×t_id+14×K×f_id+14×K×8×ul_carrier_id  (3)
    上述公式中的s_id指示发送前导码占用第一个子帧起始符号编号，其取值范围为0≤s_id<14。t_id指示前导码传输资源占用第一个子帧编号，其取值范围为0≤t_id<80。f_id指示前导码传输资源在频域编号，其取值范围为0≤f_id<8。ul_carrier_id指示前导码传输所使用的上行载波，‘0’表示普通上行载波，‘1’表示辅助上行载波；所述K为与所述RAR窗口的最大值对应的参数；
    或者，
    RA-RNTI＝1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id  (2a)
    NR RA-RNTI计算公式(2a)中的s_id，t_id，f_id等参数的功能与公式(2)中相同；s_id用于指示发送前导码占用第一个子帧起始符号编号，其取值范围为0≤s_id<14。t_id用于指示前导码传输资源占用第一个子帧编号，其取值范围为0≤t_id<80。f_id指示前导码传输资源在频域编号，其取值范围为0≤f_id<8。但是，NR RA-RNTI计算公式(2a)中的ul_carrier_id指示信息，用于指示gNB收到的Preamble在RAR窗口内的位置信息。
  6. 根据权利要求1或者5所述的方法，其特征在于，
    把所有系统帧按照平均分散的规律记为N组，仅在其中一组系统帧对应的RAR内进行RAR检测,不需要在其他组的系统帧内进行RAR检测；N为大于等于2的整数。
  7. 根据权利要求1或者5所述的方法，
    所述选择可用的随机接入时频资源RO具体为：在为所述NRU UE的配置的一个系统帧内的多个子帧内选择一个子帧，在所述选择的子帧进行所述preamble的发送；所述多个子帧少于10个。
  8. 一种RA-RNTI处理方法，其特征在于，
    网络装置接收NR-U UE发送的前导Preamble；
    基于接收的所述Preamble随机接入时频资源RO生成RA-RNTI；
    采用所述RA-RNTI加扰PDCCH；
    在LBT成功后发送所述加扰后的PDCCH。
  9. 根据权利要求8所述的方法，所述方法还包括
    网络装置发送第一指示，所述第一指示用于指示RAR的时间信息或者位置信息；
  10. 根据权利要求9所述的方法，
    所述第一指示承载于DCI中。
  11. 根据权利要求9所述的方法，
    所述第一指示承载于RAR MAC CE中。
  12. 根据权利要求8-11任一所述的方法，所述基于接收的所述Preamble随机接入时频资源RO生成RA-RNTI，包括采用下述公式之一计算RA-RNTI：
    RA-RNTI＝1+s_id+14×t_id+14×K×f_id+14×K×8×ul_carrier_id  (3)
    上述公式中的s_id指示发送前导码占用第一个子帧起始符号编号，其取值范围为0≤s_id<14。t_id指示前导码传输资源占用第一个子帧编号，其取值范围为0≤t_id<80。f_id指示前导码传输资源在频域编号，其取值范围为0≤f_id<8。ul_carrier_id指示前导码传输所使用的上行载波，‘0’表示普通上行载波，‘1’表示辅助上行载波；所述K为与所述RAR窗口的最大值对应的参数；
    或者，
    RA-RNTI＝1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id  (2a)
    NR RA-RNTI计算公式(2a)中的s_id，t_id，f_id等参数的功能与公式(2)中相同；s_id用于指示发送前导码占用第一个子帧起始符号编号，其取值范围为0≤s_id<14。t_id用于指示前导码传输资源占用第一个子帧编号，其取值范围为0≤t_id<80。f_id指示前导码传输资源在频域编号，其取值范围为0≤f_id<8。但是，NR RA-RNTI计算公式(2a)中的ul_carrier_id指示信息，用于指示gNB收到的Preamble在RAR窗口内的位置信息。
  13. 一种RA-RNTI处理装置，其特征在于，
    第一模块，用于在NR-U UE进行LBT成功后，随机选择一个前导码Preamble，选择可用的随机接入时频资源RO；
    第二模块，用于在所述选择的RO上发送所述Preamble；
    第三模块，用于基于所述RO生成RA-RNTI。
  14. 根据权利要求13所述的装置，
    第四模块，用于接收网络装置发送的第一指示，所述第一指示用于指示RAR的时间信息或者位置信息；
    第五模块，用于所述NR-U UE仅在所述第一指示指示的时间窗(RAR)内检测PDCCH，所述PDCCH由所述gNB采用相同的RA-RNTI进行加扰。
  15. 根据权利要求14所述的装置，
    所述第一指示承载于DCI中。
  16. 根据权利要求14所述的装置，
    所述第一指示承载于RAR MAC CE中。
  17. 根据权利要求13-16任一所述的装置，
    所述第三模块中，RA-RNTI＝1+s_id+14×t_id+14×K×f_id+14×K×8×ul_carrier_id   (3)
    上述公式中的s_id指示发送前导码占用第一个子帧起始符号编号，其取值范围为0≤s_id<14。t_id指示前导码传输资源占用第一个子帧编号，其取值范围为0≤t_id<80。f_id指示前导码传输资源在频域编号，其取值范围为0≤f_id<8。ul_carrier_id指示前导码传输所使用的上行载波，‘0’表示普通上行载波，‘1’表示辅助上行载波；所述K为与所述RAR窗口的最大值对应的参数；
    或者，
    RA-RNTI＝1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id   (2a)
    NR RA-RNTI计算公式(2a)中的s_id，t_id，f_id等参数的功能与公式(2)中相同；s_id用于指示发送前导码占用第一个子帧起始符号编号，其取值范围为0≤s_id<14。t_id用于指示前导码传输资源占用第一个子帧编号，其取值范围为0≤t_id<80。f_id指示前导码传输资源在频域编号，其取值范围为0≤f_id<8。但是，NR RA-RNTI计算公式(2a)中的ul_carrier_id指示信息，用于指示gNB收到的Preamble在RAR窗口内的位置信息。
  18. 根据权利要求13或者17任一所述的装置，包括
    第五模块，用于把所有系统帧按照平均分散的规律记为N组，仅在其中一组系统帧对应的RAR内进行RAR检测,不需要在其他组的系统帧内进行RAR检测；N为大于等于2的整数。
  19. 根据权利要求13或者17任一所述的装置，
    所述第一模块，具体用于：进行LBT成功后，在为所述NRU UE的配置的一个系统帧内的多个子帧内选择一个子帧，在所述选择的子帧进行所述preamble的发送；所述多个子帧少于10个。
  20. 一种RA-RNTI处理装置，其特征在于，
    第一模块，用于接收NR-U UE发送的前导Preamble；
    第二模块，用于基于接收的所述Preamble随机接入时频资源RO生成RA-RNTI；
    第三模块，用于采用所述RA-RNTI加扰PDCCH；
    在LBT成功后发送所述加扰后的PDCCH。
  21. 根据权利要求20所述的装置，所述装置还包括
    第四模块，用于发送第一指示，所述第一指示用于指示RAR的时间信息或者位置信息；
  22. 根据权利要求21所述的装置，
    所述第一指示承载于DCI中。
  23. 根据权利要求21所述的装置，
    所述第一指示承载于RAR MAC CE中。
  24. 根据权利要求20-23任一所述的装置，所述第二模块用于根据下述公式生成所述RA-RNTI：
    RA-RNTI＝1+s_id+14×t_id+14×K×f_id+14×K×8×ul_carrier_id   (3)
    上述公式中的s_id指示发送前导码占用第一个子帧起始符号编号，其取值范围为0≤s_id<14。t_id指示前导码传输资源占用第一个子帧编号，其取值范围为0≤t_id<80。f_id指示前导码传输资源在频域编号，其取值范围为0≤f_id<8。ul_carrier_id指示前导码传输所使用的上行载波，‘0’表示普通上行载波，‘1’表示辅助上行载波；所述K为与所述RAR窗口的最大值对应的参数；
    或者，
    RA-RNTI＝1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id  (2a)
    NR RA-RNTI计算公式(2a)中的s_id，t_id，f_id等参数的功能与公式(2)中相同；s_id用于指示发送前导码占用第一个子帧起始符号编号，其取值范围为0≤s_id<14。t_id用于指示前导码传输资源占用第一个子帧编号，其取值范围为0≤t_id<80。f_id指示前导码传输资源在频域编号，其取值范围为0≤f_id<8。但是，NR RA-RNTI计算公式(2a)中的ul_carrier_id指示信息，用于指示gNB收到的Preamble在RAR窗口内的位置信息。
PCT/CN2020/073886 2019-01-24 2020-01-22 一种ra-rnti处理方法和装置 WO2020151754A1 (zh)

Priority Applications (6)

Application Number Priority Date Filing Date Title
EP20746036.1A EP3917232A4 (en) 2019-01-24 2020-01-22 METHOD AND APPARATUS FOR RA-RNTI PROCESSING
KR1020217026858A KR20210116636A (ko) 2019-01-24 2020-01-22 Ra-rnti 처리 방법 및 장치
CA3127703A CA3127703A1 (en) 2019-01-24 2020-01-22 Ra-rnti processing method and apparatus
JP2021543174A JP7282182B2 (ja) 2019-01-24 2020-01-22 Ｒａ－ｒｎｔｉ処理方法及び装置
BR112021014571-0A BR112021014571A2 (pt) 2019-01-24 2020-01-22 Método e aparelho de processamento de ra-rnti
US17/385,570 US20210360697A1 (en) 2019-01-24 2021-07-26 Ra-rnti processing method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910069184.X 2019-01-24
CN201910069184.XA CN111478757A (zh) 2019-01-24 2019-01-24 一种ra-rnti处理方法和装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/385,570 Continuation US20210360697A1 (en) 2019-01-24 2021-07-26 Ra-rnti processing method and apparatus

Publications (1)

Publication Number Publication Date
WO2020151754A1 true WO2020151754A1 (zh) 2020-07-30

Family

ID=71735558

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/073886 WO2020151754A1 (zh) 2019-01-24 2020-01-22 一种ra-rnti处理方法和装置

Country Status (8)

Country Link
US (1) US20210360697A1 (zh)
EP (1) EP3917232A4 (zh)
JP (1) JP7282182B2 (zh)
KR (1) KR20210116636A (zh)
CN (2) CN112713983B (zh)
BR (1) BR112021014571A2 (zh)
CA (1) CA3127703A1 (zh)
WO (1) WO2020151754A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2022520610A (ja) * 2019-02-14 2022-03-31 ペキン シャオミ モバイル ソフトウェア カンパニー， リミテッド ランダムアクセスの処理方法及び装置
US20230156804A1 (en) * 2020-08-05 2023-05-18 Apple Inc. Rach procedures for non-terrestrial networks for user equipment
JP2023524842A (ja) * 2020-08-06 2023-06-13 エルジー エレクトロニクス インコーポレイティド 無線通信システムにおいて無線信号の送受信方法及び装置

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US12063691B2 (en) 2019-04-15 2024-08-13 Beijing Xiaomi Mobile Software Co., Ltd. Random access method and apparatus
CN114698087A (zh) * 2020-12-31 2022-07-01 维沃移动通信有限公司 Ra-rnti的处理方法、装置、终端及可读存储介质
CN115150967A (zh) * 2021-03-31 2022-10-04 华为技术有限公司 一种随机接入方法及装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101674661A (zh) * 2009-10-14 2010-03-17 普天信息技术研究院有限公司 长期演进系统中的随机接入方法
US20150023194A1 (en) * 2012-01-11 2015-01-22 Lg Electronics Inc. Method for transceiving channel state information in wireless access system and apparatus for the method
CN108012329A (zh) * 2017-09-27 2018-05-08 华为技术有限公司 一种寻呼的方法、通信定时的方法和装置
CN108289329A (zh) * 2017-01-09 2018-07-17 北京三星通信技术研究有限公司 随机接入的方法及基站设备、用户设备
CN108668361A (zh) * 2017-04-01 2018-10-16 北京三星通信技术研究有限公司 一种信息生成方法和设备

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10631330B2 (en) 2015-04-03 2020-04-21 Qualcomm Incorporated Random access procedures under coverage limitations
ES2732479T3 (es) * 2015-04-22 2019-11-22 Intel Ip Corp Solicitud de planificación basada en la contención de baja latencia
WO2017131430A1 (en) * 2016-01-26 2017-08-03 Lg Electronics Inc. Method for performing a random access procedure in wireless communication system and a device therefor
EP3457803A1 (en) 2016-05-12 2019-03-20 NTT DoCoMo, Inc. User terminal and wireless communication method
CN106102182B (zh) * 2016-06-07 2019-02-19 北京交通大学 非正交随机接入方法
CN116390265A (zh) 2016-07-15 2023-07-04 株式会社Ntt都科摩 终端、无线通信方法、基站以及无线通信系统
CN108289339B (zh) * 2017-01-09 2021-12-24 北京三星通信技术研究有限公司 随机接入响应发送和检测的方法及基站、用户设备
CN108737039B (zh) * 2017-04-14 2023-11-10 华为技术有限公司 随机接入及响应方法、终端设备、网络设备
US11272532B2 (en) * 2018-11-01 2022-03-08 Comcast Cable Communications, Llc Random access response reception

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101674661A (zh) * 2009-10-14 2010-03-17 普天信息技术研究院有限公司 长期演进系统中的随机接入方法
US20150023194A1 (en) * 2012-01-11 2015-01-22 Lg Electronics Inc. Method for transceiving channel state information in wireless access system and apparatus for the method
CN108289329A (zh) * 2017-01-09 2018-07-17 北京三星通信技术研究有限公司 随机接入的方法及基站设备、用户设备
CN108668361A (zh) * 2017-04-01 2018-10-16 北京三星通信技术研究有限公司 一种信息生成方法和设备
CN108012329A (zh) * 2017-09-27 2018-05-08 华为技术有限公司 一种寻呼的方法、通信定时的方法和装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3917232A4

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2022520610A (ja) * 2019-02-14 2022-03-31 ペキン シャオミ モバイル ソフトウェア カンパニー， リミテッド ランダムアクセスの処理方法及び装置
JP7258166B2 (ja) 2019-02-14 2023-04-14 ペキン シャオミ モバイル ソフトウェア カンパニー， リミテッド ランダムアクセスの処理方法及び装置
US20230156804A1 (en) * 2020-08-05 2023-05-18 Apple Inc. Rach procedures for non-terrestrial networks for user equipment
JP2023524842A (ja) * 2020-08-06 2023-06-13 エルジー エレクトロニクス インコーポレイティド 無線通信システムにおいて無線信号の送受信方法及び装置
JP7385773B2 (ja) 2020-08-06 2023-11-22 エルジー エレクトロニクス インコーポレイティド 無線通信システムにおいて無線信号の送受信方法及び装置
US12096480B2 (en) 2020-08-06 2024-09-17 Lg Electronics Inc. Method and apparatus for transmitting and receiving wireless signal in wireless communication system

Also Published As

Publication number Publication date
CN111478757A (zh) 2020-07-31
BR112021014571A2 (pt) 2021-10-05
JP2022518780A (ja) 2022-03-16
US20210360697A1 (en) 2021-11-18
CA3127703A1 (en) 2020-07-30
JP7282182B2 (ja) 2023-05-26
EP3917232A4 (en) 2022-03-30
EP3917232A1 (en) 2021-12-01
CN112713983B (zh) 2022-04-12
KR20210116636A (ko) 2021-09-27
CN112713983A (zh) 2021-04-27

Similar Documents

Publication Publication Date Title
WO2020151754A1 (zh) 一种ra-rnti处理方法和装置
US11877259B2 (en) Paging method, terminal device, and network device
RU2687033C1 (ru) Передача ответного сообщения произвольного доступа
RU2730967C1 (ru) Устройство и способ конфигурирования направления передачи частотно-временного ресурса
US20210068154A1 (en) Channel sensing method, related device, and system
EP3437285A1 (en) Method performed by user equipment, method performed by evolved node b, user equipment, and evolved node b
JP2017508361A (ja) マシンタイプ通信についてのランダムアクセスのためのユーザ機器及び進化型ノードｂ及び方法
US10419185B2 (en) System and method for listen before talk-based random access with partial subframes
US11284442B2 (en) Random access method, user equipment, base station, and random access system
US11570731B2 (en) Method for sending synchronization signal in unlicensed frequency band, network device, and terminal device
US12010721B2 (en) Initial signal detection method and apparatus
WO2020063482A1 (zh) 传输随机接入信号的方法和装置
US20230354415A1 (en) Channel access method and device
EP3886496B1 (en) Resource reservation method and related device
WO2020029070A1 (en) Method, apparatus and computer readable media for resource allocation
KR20130125075A (ko) 반 이중 단말 및 반 이중 단말의 랜덤 억세스 방법
KR20230005135A (ko) 랜덤 액세스 대역폭에 기초한 통신 구성
EP3846572A1 (en) Random access method, data receiving method and device thereof, and communication system
US20240163777A1 (en) Network slicing-based random access method and apparatus, and storage medium
EP4432587A1 (en) Communication method and apparatus
WO2023020542A1 (zh) 随机接入的方法和装置
WO2024031587A1 (zh) 通信方法、终端设备和网络设备
CN107396446A (zh) 一种信息处理的方法及装置
WO2024131702A1 (zh) 确定下行频域资源的方法以及用户设备
US20240313882A1 (en) Wireless communication method, terminal device, and network device

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 3127703

Country of ref document: CA

ENP Entry into the national phase

Ref document number: 2021543174

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112021014571

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 20217026858

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2020746036

Country of ref document: EP

Effective date: 20210824

ENP Entry into the national phase

Ref document number: 112021014571

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20210723