RA-RNTI processing method and device

Abstract

The invention relates to an RA-RNTI (Random Access-Radio Network Temporary Identity) processing method, which comprises the following steps: NR-U UE randomly selects a preamble and selects an available random access time-frequency resource RO after LBT succeeds; the Preamble is sent on the selected RO (Reverse Osmosis); and generating the RA-RNTI based on the RO. Specifically, a first indication sent by a network device can be received, and the first indication is used for indicating time information or position information of the RAR; and the NR-U UE only detects the PDCCH in a time window (RAR) indicated by the first indication, and the PDCCH is scrambled by the gNB by adopting the same RA-RNTI (Random Access-Radio Network Temporary Identity).

Description

[0001] This application is a divisional application. The application number of the original application is 201910069184.X, and the original application date is January 24, 2019. The entire contents of the original application are incorporated into this application by reference. Technical Field

[0002] The present application relates to the field of wireless communication technology, and in particular to a RA-RNTI processing method and device. Background Art

[0003] 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 after it has achieved uplink synchronization with the cell. The UE establishes a connection with the cell and achieves uplink synchronization through the Random Access Procedure.

[0004] The main purposes of random access are: (1) to obtain uplink synchronization; (2) to allocate a unique identifier C-RNTI within the cell to the UE.

[0005] There are two different ways of random access process: contention based and non-contention based (Non-Contention based, Contention-Free based) random access process. For contention random access, the whole process includes 4 steps, and for non-contention random access, the whole process includes 2 steps. RA-RNTI (Random Access Network Identifier) ​​is the unique identifier of the UE used in the contention random access process.

[0006] In the LTE system, the calculation of RA-RNTI is related to the time-frequency resources used by the UE to send the preamble sequence. The generation formula is as follows:

[0007] RA-RNTI = 1 + t_id + 10 * f_id (1)

[0008] Where t_id indicates the number of the first subframe occupied by the preamble code, and its value range is 0≤t_id<10. f_id indicates the number of the preamble code transmission resource in the frequency domain, and its value range is 0≤f_id<6. In summary, the value of RA-RNTI will not be repeated within a 10ms window (i.e., within 10 subframes).

[0009] Similarly, in the NR system, the calculation formula of RA-RNTI is as follows:

[0010] RA-RNTI= 1 + s_id + 14 × t_id + 14 × 80 × f_id + 14 × 80 × 8 ×ul_carrier_id (2)

[0011] Among them, s_id indicates the starting symbol number of the first subframe occupied by the sent preamble, and its value range is 0≤s_id<14. t_id indicates the first subframe number occupied by the preamble transmission resource, and its value range is 0≤t_id<80. f_id indicates the frequency domain number of the preamble transmission resource, 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 reason for the difference in value from LTE is that the NR PRACH transmission time-frequency resources can theoretically start at each symbol in each slot in each system frame of each uplink carrier, and PRACH transmission supports a maximum subcarrier spacing of 120kHz.

[0012] In summary, the value of NR RA-RNTI calculated using the above formula can only ensure that it will not be repeated within a 10ms window (i.e., within 10 subframes). Summary of the invention

[0013] The technical problem to be solved by the present application is to reduce the repetition of RA-RNTI on the unlicensed spectrum in the NR system.

[0014] A RA-RNTI processing method, after LBT is successful, the NR-U UE randomly selects a preamble code Preamble, selects an available random access time-frequency resource RO; sends the Preamble on the selected RO; and generates RA-RNTI based on the RO.

[0015] Preferably, a first indication sent by a network device can be received, wherein the first indication is used to indicate the time information or location information of the RAR; the NR-U UE detects the PDCCH only within the time window (RAR) indicated by the first indication, and the PDCCH is scrambled by the gNB using the same RA-RNTI. The first indication is carried in the DCI. Alternatively, the first indication is carried in the RAR MAC CE. Various methods can be used to generate the RA-RNTI based on the RO, for example, generating the RA-RNTI according to one of the following formulas:

[0016] RA-RNTI=1+s_id+14×t_id+14×K×f_id+14×K×8×ul_carrier_id(3)

[0017] In the above formula, s_id indicates the number of the first subframe starting symbol occupied by the transmitted preamble, and its value range is 0≤s_id<14. t_id indicates the number of the first subframe occupied by the preamble transmission resource, 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 the preamble transmission, '0' indicates a normal uplink carrier, and '1' indicates an auxiliary uplink carrier; K is a parameter corresponding to the maximum value of the RAR window;

[0018] or,

[0019] RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id(2a)

[0020] The functions of parameters such as s_id, t_id, f_id in the NR RA-RNTI calculation formula (2a) are the same as those in formula (2); s_id is used to indicate that the sending preamble occupies the first subframe starting 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 frequency domain number of the preamble transmission resource, and its value range is 0≤f_id<8. However, 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. Of course, it can also be the formula (2), formula (3a) or (3b) mentioned in the implementation method, etc., which will not be repeated here.

[0021] In other examples, all system frames may be recorded as N groups according to the rule of average dispersion, and RAR detection is performed only in the RAR corresponding to one group of system frames, and RAR detection is not required in the system frames of other groups; N is an integer greater than or equal to 2. Alternatively, in other examples, the selection of available random access time-frequency resources RO is specifically: selecting a subframe from multiple subframes in a system frame configured for the NRU UE, and sending the preamble in the selected subframe; the multiple subframes are less than 10.

[0022] On the other hand, a RA-RNTI processing method on a network side device is provided, which will not be described in detail here.

[0023] In other aspects, the present application also provides devices, computer-readable storage media, etc. that can execute the aforementioned methods.

[0024] By implementing the embodiments of the present application, for the use of unlicensed frequency bands, the flexibility of uplink resource scheduling can be improved while meeting the Occupancy Channel Bandwidth (OCB) requirements of the European Telecommunications Standards Institute (ETSI). Furthermore, resource utilization can be improved. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the background technology, the drawings required for use in the embodiments of the present application or the background technology will be described below.

[0026] Figure 1 It is a schematic diagram of an existing resource allocation method involved in this application;

[0027] Figure 2 It is a schematic diagram of the architecture of a wireless communication system involved in the present application;

[0028] Figure 3 is a schematic diagram of the hardware architecture of a terminal provided by an embodiment of the present application;

[0029] Figure 4 is a schematic diagram of the hardware architecture of a base station provided by an embodiment of the present application;

[0030] Figure 5 It is a flowchart of a NR-U UE random access process provided by an embodiment of the present application;

[0031] Figure 6 This is a simple schematic diagram of NRU RAR MAC provided by an embodiment of the present application;

[0032] Figure 7 is a schematic diagram of an NRU SF indication subframe header provided by an embodiment of the present application;

[0033] Figure 8 An embodiment of the present application provides a schematic diagram of NRU RA-RNTI detection. DETAILED DESCRIPTION

[0034] The terms used in the implementation section of this application are only used to explain the specific embodiments of this application and are not intended to limit this application.

[0035] For the convenience of subsequent description, the abbreviations and key terms in this article can be referred to in the following table:

[0036]

[0037]

[0038] Figure 1 It is a schematic diagram of an existing resource allocation method involved in this application;

[0039] In order to facilitate understanding of the implementation of the present application, the wireless communication system involved in the embodiments of the present application is first introduced.

[0040] refer to Figure 2 , Figure 2 2 shows a wireless communication system 200 involved in the present application. The wireless communication system 200 can operate in a licensed frequency band or an unlicensed frequency band. It can be understood that the use of the unlicensed frequency band can improve the system capacity of the wireless communication system 200. Figure 2 As shown, the wireless communication system 200 includes: one or more network devices 201, such as base stations, NodeBs, eNodeBs or WLAN access points, wireless relay nodes, wireless backhaul nodes, one or more terminals 203, and a core network 215. Among them:

[0041] The network device 201 may be used to communicate with the terminal 203 under the control of a base station controller (not shown). In some embodiments, the base station controller may be a part of the core network 230 or may be integrated into the base station 201.

[0042] The network device 201 may be used to transmit control information or user data to a core network 215 via a backhaul interface (eg, S1 interface) 213 .

[0043] The network device 201 can wirelessly communicate 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 can be divided into multiple sectors, where one sector corresponds to a part of the coverage area (not shown).

[0044] The network device 201 and the base station 201 may also communicate with each other directly or indirectly via a backhaul link 211. Here, the backhaul link 211 may be a wired communication connection or a wireless communication connection.

[0045] The network device 201 may also be a wireless controller in a 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 an in-vehicle device, etc. The network device 201 may also be a small station, a transmission reference point (TRP), etc. Of course, the application is not limited to this.

[0046] In some embodiments of the present application, the network device 201 may include: a base transceiver station, a wireless transceiver, a basic service set (BSS), an 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, a micro base station, etc. The base station 201 may apply different wireless technologies, such as a cell wireless access technology or a WLAN wireless access technology.

[0047] The terminal 203 can be distributed throughout the wireless communication system 200, and can be stationary or mobile. It can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; it can also be deployed on the water surface (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons and satellites, etc.). The terminal device can be a mobile phone, a tablet computer (Pad), a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, etc. The embodiments of the present application do not limit the application scenarios. The terminal device may also be sometimes referred to as user equipment (UE), access terminal equipment, UE unit, UE station, mobile station, mobile station, remote station, remote terminal equipment, mobile device, UE terminal equipment, terminal equipment, wireless communication equipment, UE agent or UE device, etc. In some embodiments of the present application, 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, etc.

[0048] In an embodiment of the present application, the wireless communication system 200 may be an LTE communication system capable of operating in an unlicensed frequency band, such as LTE-U, or may be a 5G communication system capable of operating in an unlicensed frequency band and future new air interfaces, such as NR-U and other communication systems. The wireless communication system 200 may adopt a licensed assisted access (LAA) scheme to handle terminal access in an unlicensed frequency band. In the LAA scheme, the primary cell (Primary Cell) operates in an authorized frequency band to transmit critical messages and services that require quality of service assurance; the secondary cell (Secondary Cell) operates in an unlicensed frequency band to achieve improved data plane performance.

[0049] In the embodiment of the present application, the wireless communication system 200 can support multi-carrier (waveform signals of different frequencies) operation. A multi-carrier transmitter can transmit modulated signals on multiple carriers simultaneously. For example, each communication connection 205 can carry multi-carrier signals modulated using different wireless technologies. Each modulated signal can be sent on a different carrier and can also carry control information (such as reference signals, control channels, etc.), overhead information, data, etc.

[0050] In addition, the wireless communication system 200 may also include a WiFi network. In order to achieve harmonious coexistence between the operator network and the WiFi network (operating in the unlicensed spectrum), the wireless communication system 200 may adopt a Listen before Talk (LBT) mechanism. For example, in the wireless communication system 200, some terminals 203 may use unlicensed spectrum resources by connecting to the WiFi access point 209 via the WiFi communication connection 217, and some terminals 203 may also use unlicensed spectrum resources by connecting to the base station 201 via the mobile communication connection 205. When using an unlicensed frequency band, any device must first listen to see if the frequency band is occupied. If the frequency band is not busy, it can occupy and transmit data.

[0051] refer to Figure 3 , Figure 3 FIG. 3 shows a terminal 300 provided in some embodiments of the present application. Figure 3 As shown, the terminal 300 may include: an input and output module (including an audio input and output module 318, a key input module 316, and a display 320, etc.), a user interface 302, one or more terminal processors 304, a transmitter 306, a receiver 308, a coupler 310, an antenna 314, and a memory 312. These components may be connected via a bus or other means. Figure 3 Take bus connection as an example.

[0052] The communication interface 301 can be used for the terminal 300 to communicate with other communication devices, such as a base station. Specifically, the other communication device can be Figure 4The base station 400 shown. Specifically, the communication interface 301 may include: a global system for mobile communication (Global System for Mobile Communication, GSM) (2G) communication interface, a wideband code division multiple access (WCDMA) (3G) communication interface, and a long-term evolution (LongTerm Evolution, LTE) (4G) communication interface, etc. One or more of the above, can also be a communication interface of 4.5G, 5G or future new air interfaces. Not limited to wireless communication interfaces, the terminal 300 can also be configured with a wired communication interface 301, such as a local access network (LAN) interface.

[0053] The antenna 314 can be used to convert electromagnetic energy in the transmission line into electromagnetic waves in free space, or convert electromagnetic waves in free space into electromagnetic energy in the transmission line. The coupler 310 is used to divide the mobile communication signal received by the antenna 314 into multiple paths and distribute them to multiple receivers 308.

[0054] The transmitter 306 may be used to perform transmission processing on the signal output by the terminal processor 304, for example, modulating the signal into a signal in an authorized frequency band, or modulating the signal into a signal in an unauthorized frequency band. In some embodiments of the present application, the transmitter 206 may include an unauthorized spectrum transmitter 3061 and an authorized spectrum transmitter 3063. The unauthorized spectrum transmitter 3061 may support the terminal 300 to transmit signals on one or more unauthorized spectrums, and the authorized spectrum transmitter 3063 may support the terminal 300 to transmit signals on one or more authorized spectrums.

[0055] The receiver 308 may be used to receive and process the mobile communication signal received by the antenna 314. For example, the receiver 308 may demodulate the received signal modulated on the unlicensed frequency band, and may also demodulate the received signal modulated on the licensed frequency band. In some embodiments of the present application, the receiver 308 may include an unlicensed spectrum receiver 3081 and an authorized spectrum receiver 3083. The unlicensed spectrum receiver 3081 may support the terminal 300 to receive the signal modulated on the unlicensed spectrum, and the authorized spectrum receiver 3083 may support the terminal 300 to receive the signal modulated on the authorized spectrum.

[0056] In some embodiments of the present application, the transmitter 306 and the receiver 308 can be regarded as a wireless modem. In the terminal 300, the number of the transmitter 306 and the number of the receiver 308 can be one or more.

[0057] Apart from Figure 3In addition to the transmitter 306 and the receiver 308 shown, the terminal 300 may also include other communication components, such as a GPS module, a Bluetooth module, a wireless high-fidelity (Wireless Fidelity, Wi-Fi) module, etc. Not limited to the wireless communication signals described above, the terminal 300 may also support other wireless communication signals, such as satellite signals, shortwave signals, etc. 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.

[0058] The input and output modules can be used to realize the interaction between the terminal 300 and the user or the external environment, and can mainly include an audio input and output module 318, a key input module 316, and a display 320. Specifically, the input and output modules can also include: a camera, a touch screen, and a sensor. Among them, the input and output modules communicate with the terminal processor 304 through the user interface 302.

[0059] The memory 312 is coupled to the terminal processor 304 and is used to store various software programs and or multiple groups of instructions. Specifically, the memory 312 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more disk storage devices, flash memory devices or other non-volatile solid-state storage devices. The memory 312 can store an operating system (hereinafter referred to as the system), such as an embedded operating system such as ANDROID, IOS, WINDOWS, or LINUX. The memory 312 can also store a network communication program, which can 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 display the content of the application program vividly through a graphical operation interface, and receive user control operations on the application program through input controls such as menus, dialog boxes, and buttons.

[0060] In some embodiments of the present application, the memory 312 may be used to store an implementation program of the resource allocation method provided by one or more embodiments of the present application on the terminal 300 side. For the implementation of the resource allocation method provided by one or more embodiments of the present application, please refer to the subsequent embodiments.

[0061] The terminal processor 304 can be used to read and execute computer-readable instructions. Specifically, the terminal processor 304 can be used to call a program stored in the memory 312, such as an implementation program of the resource allocation method provided in one or more embodiments of the present application on the terminal 300 side, and execute the instructions contained in the program.

[0062] It is understandable that the terminal 300 may be Figure 2The terminal 203 in the wireless communication system 200 shown may be implemented as a mobile device, a mobile station, a mobile unit, a wireless unit, a remote unit, a user agent, a mobile client, and the like.

[0063] Need to explain, Figure 3 The terminal 300 shown is only one implementation 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.

[0064] refer to Figure 4 , Figure 4 4 shows a base station 400 provided in some embodiments of the present application. Figure 4 As shown, 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 may be connected via a bus or other means. Figure 4 Take bus connection as an example.

[0065] 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. Specifically, the terminal device can be Figure 3 The terminal 300 shown. Specifically, the communication interface 403 may include: one or more of the global system for mobile communications (GSM) (2G) communication interface, wideband code division multiple access (WCDMA) (3G) communication interface, and long-term evolution (LTE) (4G) communication interface, etc., and may also be a communication interface of 4.5G, 5G or future new air interfaces. Not limited to wireless communication interfaces, the base station 400 may also be configured with a wired communication interface 403 to support wired communication, for example, the backhaul link between a base station 400 and other base stations 400 may be a wired communication connection.

[0066] The antenna 413 can be used to convert electromagnetic energy in the transmission line into electromagnetic waves in free space, or convert electromagnetic waves in free space into electromagnetic energy in the transmission line. The coupler 411 can be used to divide the mobile communication signal into multiple paths and distribute them to multiple receivers 409.

[0067] The transmitter 407 may be used to perform transmission processing on the signal output by the base station processor 401, for example, modulating the signal into a signal in an authorized frequency band, or modulating the signal into a signal in an unauthorized frequency band. In some embodiments of the present application, the transmitter 407 may include an unauthorized spectrum transmitter 4071 and an authorized spectrum transmitter 4073. The unauthorized spectrum transmitter 4071 may support the base station 400 to transmit signals on one or more unauthorized spectrums, and the authorized spectrum transmitter 4073 may support the base station 400 to transmit signals on one or more authorized spectrums.

[0068] The receiver 409 may be used to receive and process the mobile communication signal received by the antenna 413. For example, 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. In some embodiments of the present application, the receiver 409 may include an unlicensed spectrum receiver 4091 and an authorized spectrum receiver 4093. The unlicensed spectrum receiver 4091 may support the base station 400 to receive the signal modulated on the unlicensed spectrum, and the authorized spectrum receiver 4093 may support the base station 400 to receive the signal modulated on the authorized spectrum.

[0069] In some embodiments of the present application, the transmitter 407 and the receiver 409 can be regarded as a wireless modem. In the base station 400, the number of the transmitter 407 and the number of the receiver 409 can be one or more.

[0070] The memory 405 is coupled to the base station processor 401 and is used to store various software programs and or multiple groups of instructions. Specifically, the memory 405 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more disk storage devices, flash memory devices or other non-volatile solid-state storage devices. The memory 405 can store an operating system (hereinafter referred to as system), such as uCOS, VxWorks, RTLinux and other embedded operating systems. The memory 405 can also store a network communication program, which can be used to communicate with one or more additional devices, one or more terminal devices, and one or more network devices.

[0071] The base station processor 401 can be used to manage wireless channels, establish and remove calls and communication links, and control the handover of user equipment in the control area. Specifically, the base station processor 401 may include: an administration module or a communication module (AM or CM) (a center for voice exchange and information exchange), a basic module (BM) (for completing call processing, signaling processing, wireless resource management, wireless link management and circuit maintenance functions), a transcoder and submultiplexer (TCSM) (for completing multiplexing, demultiplexing and code conversion functions), and the like.

[0072] In the embodiment of the present application, the base station processor 401 can be used to read and execute computer-readable instructions. Specifically, the base station processor 401 can be used to call a program stored in the memory 405, such as an implementation program of the resource allocation method provided in one or more embodiments of the present application on the base station 400 side, and execute the instructions contained in the program.

[0073] It is understandable that the base station 400 may be Figure 2 The base station 201 in the wireless communication system 200 shown can be implemented as a base transceiver station, a wireless transceiver, a basic service set (BSS), an extended service set (ESS), NodeB, eNodeB, etc. The base station 400 can be implemented as several different types of base stations, such as a macro base station, a micro base station, etc. The base station 400 can apply different wireless technologies, such as a cell wireless access technology, or a WLAN wireless access technology.

[0074] Need to explain, Figure 4 The base station 400 shown is only one implementation of the embodiment of the present application. In actual applications, the base station 400 may also include more or fewer components, which is not limited here.

[0075] Alternatively, the terminal 300 or the base station 400 may also be configured as a general-purpose processing system, such as commonly referred to as a chip, which includes: one or more microprocessors that provide processor functions; and an external memory that provides at least a portion of the storage medium, all of which are connected to other supporting circuits through an external bus architecture.

[0076] Alternatively, the terminal 300 or the base station 400 can be implemented using: an ASIC (application specific integrated circuit) having a processor, a bus interface, or a user interface; and at least a portion of a storage medium integrated in a single chip, or the terminal 300 or the base station 400 can be implemented using: 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. Among them, the processor is responsible for managing the bus and general processing (including executing software stored on the storage medium). The processor can be implemented using one or more general-purpose processors and / or special-purpose processors. Examples of processors include microprocessors, microcontrollers, DSP processors, and other circuits capable of executing software. Software should be broadly interpreted as representing instructions, data, or any combination thereof, regardless of whether it is referred to as software, firmware, middleware, microcode, hardware description language, or other.

[0077] This specific implementation mainly involves the contention random access process, and only takes NR-U UE and gNB as an example of the terminal and network device. The process is as follows Figure 5 shown.

[0078] Step 101: After LBT is successful, the NR-U UE 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 Identifier) ​​according to the time and frequency domain position of the selected random access time slot. Among them, the time and frequency resource for the UE to send the Preamble is called RACH occasion, referred to as RO. Correspondingly, the gNB receives the Preamble sent by the aforementioned NR-U UE.

[0079] Specifically, a preferred method for generating RA-RNTI may adopt one of the methods mentioned in the subsequent embodiments. Generally, the system configuration information includes the setting information of the Preamble, the information for configuring the RO, the correspondence between the SSB and the RO, the t_id value, the maximum duration of the RAR window, etc. In a general solution, the available random access time slots may be all the available random access time slots, and in special cases, may also be specific partial random access time slots, such as the subsequent embodiment 6.

[0080] Step 102: Specifically, the gNB obtains the same RA-RNTI using the same method as in step 101 (based on the time-frequency resources of the received Preamble), and sends the PDCCH scrambled with the RA-RNTI after the LBT is successful. The NR-U UE detects or attempts to receive the PDCCH sent by the gNB scrambled with the same RA-RNTI obtained in step 101 within the detection time range configured for the NR-U UE. Specifically, the PDCCH channel mainly carries PUSCH and PDSCH channel control information (DCI), and the PDCCH information of different UEs is distinguished by their corresponding RA-RNTI information, that is, the CRC of their DCI is scrambled by the RA-RNTI.

[0081] In unlicensed, the gNB's sending of the above PDCCH is affected by LBT, that is, there is a situation where the gNB prepares the above PDCCH but cannot send it because the channel is busy. In order to reduce the impact of LBT on PDCCH transmission / reception, the maximum value of the RAR window is extended to more than 10ms in NR-U to give gNB more opportunities to send PDCCH. However, the calculation method of NR RA-RNTI can only ensure its uniqueness within 10ms. Therefore, this preferred implementation method can be used to solve the problem of how UE can correctly judge whether the PDCCH (including DCI, etc.) encrypted by RA-RNTI sent by gNB is for itself within the RAR window greater than 10ms. Specifically, the detection time range configured for NR-U UE includes multiple situations, and the descriptions in the subsequent implementations one to six can be referred to; among them, if there is no special description, the detection time range refers to the entire RAR time window. That is, the UE detects within the RAR time window until it detects its own PDCCH. Specifically, 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.

[0082] Optionally, each implementation 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.

[0083] Step 103: If the PDCCH is successfully received, the UE decodes the information carried by the PDSCH (Physical downlink shared channel); if the above PDCCH is not detected within the detection time range, the NR-U UE adjusts its transmission power and repeats step 101 in the next random access time slot configured by the system.

[0084] Step 104: The above PDSCH contains the time-frequency resource information for the NR-U UE to send Msg3 and the temporary network identifier (TC-RNTI: Temporary Cell Radio Network temporary identification) allocated to the NR-U UE. The UE sends Msg3 in the corresponding time-frequency resources and carries the NR-U UE's unique network identifier for the entire network for random success confirmation in step 104.

[0085] Step 105: The NR-U UE detects the PDCCH scrambled with the NR-U UE temporary network identity in step 103. If successful, it decodes the information carried in the PDSCH. If the information carries its own network-wide unique identity sent in step 103, the random access is successful and the NR-U UE sends an ACK to the gNB. If it is not its own identity, the random access fails and step 101 is repeated.

[0086] Implementation Method 1

[0087] In this embodiment, the gNB avoids misdetection that may be caused by non-unique RA-RNTI by indicating the time information or location information of the RAR.

[0088] 201. The gNB sends a first indication, where the first indication is used to indicate the time information or location information of the RAR, that is, to indicate which 10 ms or system frame of the RAR window the RAR corresponding to the NR-U UE belongs to. The NR-U UE receives and obtains the first indication. Generally, one system frame lasts for 10 ms.

[0089] Accordingly, the above method also includes:

[0090] 202. After the NR-U UE succeeds in LBT, the UE will randomly select a Preamble and an available random access time slot for sending the Preamble according to the system configuration information. Correspondingly, the gNB receives the Preamble sent by the NR-U UE. Specifically, the gNB detects the Preamble sent by the NR-U UE, and when the Preamble is detected, the gNB determines the RA-RNTI of the NR-U UE according to the time-frequency resource RO of the detected Preamble.

[0091] Correspondingly, the NR-U UE can also calculate the RA-RNTI based on the same RO information. For example, the gNB or NR-U UE generates the RA-RNTI using RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id(2).

[0092] Among them, s_id is used to indicate the number of the first subframe starting symbol occupied by the transmitted preamble, and its value range is 0≤s_id<14. t_id is used to indicate the number of the first subframe occupied by the preamble transmission resource, 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' indicates a normal uplink carrier, and '1' indicates an auxiliary uplink carrier. Accordingly, the gNB generates the same RA-RNTI in the same way.

[0093] 203. Detect the RAR, and determine whether to continue parsing the PDCCH carried by the RAR according to the first indication. Specifically, the NR-UUE first determines whether the time window of the first indication of a detected RAR is the same as the time window of the preamble sent by itself, for example, within the same 10ms. If so, continue to parse the PDCCH carried in the RAR to obtain information such as the PDSCH carried in the PDCCH. If not, give up parsing the RAR, thereby greatly reducing detection and parsing resources.

[0094] If the NR-U UE continues to parse the RAR and can successfully descramble a PDCCH with its own RA-RNTI, then the PDCCH is the PDCCH of the NR-U UE, and the NR-U UE stops detecting the RAR.

[0095] By using the above method, unnecessary detection or unnecessary analysis of the UE at other times can be reduced, and false detection caused by repeated RA-RNTIs generated in different windows that may occur in different time windows can be avoided. In this method, the process of generating RA-RNTI does not need to be complicated.

[0096] The subsequent steps can refer to the aforementioned 104-105 and will not be repeated here.

[0097] In one example, the first indication is carried in DCI.

[0098] Specifically, the gNB can add an additional bit to the RA-RNTI scrambled DCI to indicate which 10ms of the RAR window the RAR corresponding to the UE belongs to, and use the additional indication information to indicate in which system frame the gNB receives the Preamble. On the other hand, the gNB or NR-U UE can use the above formula (2) to generate the RA-RNTI, and still keep it unique within 10ms.

[0099] For example, when the maximum RAR window is 20ms, only 1 bit needs to be added to the DCI to indicate whether the gNB receives the Preamble in an odd system frame or an even system frame. It is also possible to indicate the relative time difference between sending the DCI and receiving the Preamble by the gNB, such as '0' means the time difference between the two is less than 10ms, and '1' means the time difference between the two is greater than 10ms and less than 20ms.

[0100] When the RAR window is greater than 20ms, more bits may be used in the DCI to indicate the RAR window time information, and the method is similar to that described above and will not be repeated here. For example, 2 bits may indicate the reception of RA-RNTI within a 40ms RAR window at most, and 3 bits may indicate the reception of RA-RNTI within an 80ms RAR window at most.

[0101] In other examples, one or more bits of DCI may be reused, and some values ​​are used to indicate the information of the RAR window. This method can save some overhead on the basis of indicating the above information. For example, there are 16 reserved bits in the existing RA-RNTI scrambled DCI1_0, and one or more of the reserved bits may be used for the above indication according to the maximum supported RAR window duration, for example, 2, 3, or 4 bits.

[0102] In another specific example, the first indication is carried in the RAR MAC CE.

[0103] The NRU RAR MAC frame structure is as follows Figure 6 and Figure 7 Specifically, the RAR MAC CE (control element) includes an SF indication subframe header, which is used to indicate in which system frame or 10ms the RA-RNTI-scrambled PDCCH corresponding to a certain Preamble received by the gNB is located; or, in simple terms, the SF indication subframe header is used to indicate the system frame number where the UE's PDCCH or RAR is located.

[0104] The SF indication subframe header can be located after the BI subframe header and the RAPID subframe header. In order to distinguish it from the existing 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 where the RA-RNTI is located. The 5 bits can indicate a maximum of 32 system frames, that is, the maximum length of the RAR window is 320ms.

[0105] On the receiving side, the NRU UE receives and can determine whether the subsequent MAC RAR is its own after detecting the SF indication subframe header. Furthermore, the gNB can sort the received Preambles indicated in the RAR MAC PDU according to the frame or subframe 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 it sends, it will not try to detect the remaining sub PDUs of the MAC PDU (physical data unit) to save UE energy. For example, UE 1 sends the Preamble in system frame 5 and receives the RAR (PDCCH) scrambled with its corresponding RA-RNTI in system frame 10. However, the SFindication subframe header indicates that the subsequent MAC RAR corresponds to the RA-RNTI received by the gNB in ​​system frames 6 and 8 (the RA-RNTI calculated based on the time-frequency resources of the received preamble). At this time, the UE will not continue to parse the subsequent MAC information and assume that the gNB has not received the preamble it sent. In the prior art, the NR UE will blindly detect all subPDUs of the MAC PDU indicated by the DCI corresponding to the RA-RNTI scramble to ensure that the RAR information sent to it by the gNB is not missed.

[0106] Implementation Method 2

[0107] Specifically, according to the text of standard 3GPP 38.321, when gNB / UE generates RA-RNTI, the value range of RA-RNTI is 0001-FFEF(65519)

[0108]

[0109] It can be seen from the following formula that the value range of RA-RNTI in the 10ms window is 1-17920 (1+13+14*13+14*80*7+14*80*8*1), which can ensure that RA-RNTI is not repeated in the maximum window of 36ms.

[0110] RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id

[0111] In a less favorable implementation, when the RAR window duration is greater than 10 ms, the value of t_id can be directly extended from the current 80 to 320. If the RAR window size is extended to 40 msec, 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.

[0112] However, when t_id is directly extended to 320 to indicate the RO start subframe idx within 40ms, the following problem occurs: when t_id = 240, f_id = 0, the RA-RNTI calculated by the above formula is the same as the RA-RNTI when t_id = 160, f_id = 1 and t_id = 80, f_id = 2t_id = 0, f_id = 3 (assuming that other parameters are the same). This will cause multiple UEs that successfully send Preambles with the above RO in different 10ms windows to believe that the RAR encrypted with the above RA-RNTI is sent to themselves, and send Msg3 on the RAR indication resource, increasing their collision probability and reducing system access efficiency.

[0113] In a preferred implementation, the calculation formula (3) of NR RA-RNTI and the corresponding parameter K are used to make it more suitable for scenarios where the RAR window length is greater than 10ms.

[0114] RA-RNTI=1+s_id+14×t_id+14×K×f_id+14×K×8×ul_carrier_id(3)

[0115] The s_id in the above formula indicates the starting symbol number of the first subframe occupied by the sent preamble, and its value range is 0≤s_id<14. t_id indicates the first subframe number occupied by the preamble transmission resource, and its value range is 0≤t_id<80. f_id indicates the frequency domain number of the preamble transmission resource, and its value range is 0≤f_id<8. ul_carrier_id indicates the uplink carrier used for the preamble transmission, '0' represents a normal uplink carrier, and '1' represents an auxiliary uplink carrier. The reason why the above formula is different from the LTE value is that the NR PRACH transmission time-frequency resource can theoretically start at each symbol in each slot in each system frame of each uplink carrier, and PRACH transmission supports a maximum subcarrier spacing of 120kHz. Among them, the value of K can vary according to the maximum value of the RAR window, refer to Table 1.

[0116] Specifically, in an example, the relevant standard may specify that the maximum value of the RAR window is any one or more of the values ​​in Table 1, and the value of K is the corresponding value in Table 1. Table 1 also gives the value range of RNTI calculated by formula (3) under the corresponding solution.

[0117] Table 1

[0118]

[0119] In another preferred example, the gNB can statically / semi-statically configure the RA-RNTI generation parameter K in a cell in the RMSI or other public messages, and the UE in the cell performs the calculation of the above formula (3) based on the received K. In this way, when configuring the relevant parameters of the cell (such as K), the gNB can take into account the available RA-RNTI, Temporary C-RNTI, C-RNTI, etc., and can also refer to factors such as the LBT passing probability of the cell. For example, if it takes an average of 22ms for the gNB to send DCI encrypted with RA-RNTI several times (such as 100 times), the gNB updates K to 200 and sends it in the broadcast message; if it takes an average of 28ms for the gNB to send DCI encrypted with RA-RNTI, the gNB updates K to 240 and sends it in the broadcast message.

[0120] The method includes:

[0121] 301. Optionally, the gNB sends a second indication, where the second indication is used to indicate a value of K or a maximum value of the RAR window. The NR-UUE receives the second indication to obtain the value of K, or obtains the value of K corresponding to the maximum value of the RAR window. Of course, if the standard specifies a maximum value of the RAR window or a value of K, the sending process of step 301 is not required.

[0122] Accordingly, the above method also includes:

[0123] 302. After LBT succeeds, the gNB or NR-U UE uses RA-RNTI=1+s_id+14×t_id+14×K×f_id+14×K×8×ul_carrier_id(3) and the received value of K, or the value of K corresponding to the maximum value of the RAR window, to generate RA-RNTI.

[0124] The subsequent steps can refer to the aforementioned 103-105 and will not be repeated here.

[0125] In another example, when the RAR window duration that the gNB needs to configure is greater than 35 ms or the number of RNTIs available in the communication system is less than the required value in the above table, other embodiments can be combined to generate NRU RA-RNTI.

[0126] For example, when the RAR window is greater than 10ms, the t_id value will be greater than 80, and it is necessary to further define how the UE obtains the t_id parameter corresponding to the RO:

[0127] Method 1: A fixed mapping relationship is directly given in the standard, for example, a t_id value has a mapping relationship with the system frame number where the RO is located, or the t_id value includes multiple t_id segments, each t_id segment corresponds to a system frame number where the RO is located.

[0128] Example 1: The RAR window length is 20ms, the odd system frame t_id value is 0-79, and the even system frame t_id value is 80-159;

[0129] Or vice versa.

[0130] Example 2, the RAR window length is 30ms, mod(SFN,3)=0, t_id value is 0-79; mod(SFN,3)=1, t_id value is 80-159; mod(SFN,3)=2, t_id value is 160-239.

[0131] Method 2: gNB semi-statically configures the t_id parameter based on the availability of RA-RNTI in the cell. The availability of RA-RNTI refers to which RNTIs in the cell are still idle and can be set as RA-RNTI. The above static configuration can be to inform the UE of the size of x through broadcast signaling such as RMSI / OSI or RRC dedicated signaling. Calculate t_id based on x using the following formula:

[0132] For example, the RAR window length is 30ms.

[0133] mod(SFN-x,3)=0, t_id value is 0-79;

[0134] mod(SFN-x,3)=1, t_id value is 80-159;

[0135] mod(SFN-x,3)=2, t_id takes a value of 160-239. In the above formula, x is an integer.

[0136] A simple summary is that when the RAR window length is 10*y ms,

[0137] The UE can use the following formula to calculate its RA-RNTI:

[0138] mod(SFN-x,y)=t, t takes values ​​of 0, 1, ...y. t is associated with t_id, for example, t=0, t_id takes values ​​of 0-79; t=1, t_id takes values ​​of 80-159, and so on.

[0139] When the RAR window is 30ms and the value of x is 0, the UE sends the Preamble in system frame 0, t=mod(0,3)=0, and the value of t_id is 0-79; when the UE sends the Preamble in system frame 1, t=mod(1,3)=1, and the value of t_id is 80-159; when the UE sends the Preamble in system frame 2, t=mod(2,3)=2, and the value of t_id is 160-239. The situation of sending the preamble in system frame 3 is similar to that in system frame 0, which will not be repeated here.

[0140] When the RAR window is 30ms, and the value of x is 1, the UE sends the Preamble in system frame 0, t=mod(0-1,3)=2, and the value of t_id is 160-239; when the UE sends the Preamble in system frame 1, t=mod(1-1,3)=0, and the value of t_id is 0-79; when the UE sends the Preamble in system frame 2, t=mod(2-1,3)=1, and the value of t_id is 80-159. The situation of sending the preamble in system frame 3 is similar to that in system frame 0, and will not be repeated here.

[0141] Implementation Method 3

[0142] In this implementation, NRU is still used. In order to prevent confusion between different UEs in detecting their corresponding RARs, the search space / time-frequency resources of the UE are limited in this implementation. Specifically, they include:

[0143] 401. After the LBT is successful, the UE randomly selects a Preamble and an available random access time slot according to the system configuration information for sending the Preamble. The UE can generate the RA-RNTI using RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id(2) according to the time and frequency domain position of the selected random access time slot.

[0144] 401.gNB calculates the same RA-RNTI using the same method as above, and scrambles the PDCCH with the RA-RNTI.

[0145] 402. The UE detects and attempts to receive the PDCCH scrambled with the above RA-RNTI sent by the gNB only within a relatively limited time window (RAR). Specifically, all system frames can be recorded as N groups according to the law of average dispersion. The UE sends the 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 perform RAR detection in system frames of other groups. N is an integer greater than or equal to 2. Specifically, the system frames can be grouped according to mod(index,N) or mod(index-offset,N) (offset is a fixed subframe / system frame offset).

[0146] For example, after the UE sends a preamble in the PRACH transmission time-frequency resource corresponding to a subframe in a system frame with an even or odd sequence number, the UE uses its own RA-RNTI to blindly detect the corresponding RAR only in the even system frame or only in the odd system frame. Specifically, it can be that the preamble is sent in a certain even system frame, and the PDCCH is blindly detected only in each subsequent even system frame; and, the preamble is sent in a certain odd system frame, and the PDCCH is blindly detected only in each subsequent odd system frame. Alternatively, the preamble is sent in a certain even system frame, and the PDCCH is blindly detected only in each subsequent odd system frame; and, the preamble is sent in a certain odd system frame, and the PDCCH is blindly detected only in each subsequent even system frame.

[0147] In the above implementation, the maximum RAR window length can be changed to 20ms without changing the RA-RNTI calculation method. Figure 8As shown in the upper part, the UE sends the Preamble in the system frame numbered 4 for initial access, and then the UE will only perform RAR detection in the system frames with even numbers. Of course, the gNB can also configure the UE to perform RAR detection in the system frames with odd numbers. In this method, all system frames are evenly divided into two groups (odd system frames and even system frames). The UE sends Preambles in different system frames and only performs RAR detection in one group of system frames.

[0148] In another example, when the maximum required RAR window length is 40ms, all system frames can be grouped into four groups. When the system frame number is index, the system frames are divided into four groups in turn by the following formula: mod(index,4)=0,1,2or3, respectively recorded as group 0,1,2or3. Figure 8 As shown in the lower part, the UE sends the Preamble in group 0 (within the system frame number 4) for initial access, and then the UE performs RAR detection only in group 0 (within the system frames numbered 8, 12, etc.). Of course, the gNB can also configure the UE to perform RAR detection in the system frames with the sequence numbers (mod(index,4)=1 or 2 or 3).

[0149] In addition, 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 misdetected.

[0150] Embodiment 4

[0151] In this embodiment, the NRU RAR window length is greater than 10 ms and less than 20 ms. In addition, the NRU UE does not need to perform PRACH on the secondary uplink carrier.

[0152] In the aforementioned steps 101-102, formula (2a) may be used to generate the NR RA-RNTI.

[0153] RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id(2a)

[0154] The functions of the parameters such as s_id, t_id, f_id in the NR RA-RNTI calculation formula (2a) are the same as those in formula (2); s_id is used to indicate the number of the first subframe starting symbol occupied by the transmitted preamble, and its value range is 0≤s_id<14. t_id is used to indicate the number of the first subframe occupied by the preamble transmission resource, 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. However, the ul_carrier_id indication information in the NR RA-RNTI calculation formula (2a) is used to indicate which 10ms time period (system frame) the Preamble received by the gNB is located in within the RAR window, that is, the location information of the Preamble within the RAR window. Using the above formula (2a) can ensure that the RA-RNTI within the 20ms RAR window is not repeated.

[0155] Preferably, it may be specified in the standard that when the UE sends the Preamble in an even system frame, the ul_carrier_id value is 0, and when the UE sends the Preamble in an odd system frame, the ul_carrier_id value is 1; or vice versa;

[0156] Optionally, the gNB may also inform the UE of the ul_carrier_id value in the odd / even system frames in the system information (RMSI / OSI) or RRC signaling, and the UE calculates its own RA-RNTI based on the gNB indication information.

[0157] Embodiment 5

[0158] Specifically, NR supports PRACH transmission with a maximum subcarrier spacing of 120kHz, while in this implementation, NR-UPRACH transmission only supports a maximum subcarrier spacing of 60kHz.

[0159] In the aforementioned steps 101-102, the NR-U RA-RNTI may be generated using formula (3a) or (3b):

[0160] RA-RNTI=1+s_id+14×t_id+14×40×f_id+14×40×8×ul_carrier_id

[0161] (3a)

[0162] The s_id, t_id, f_id and ul_carrier_id in formula (3a) are the same as those in formula (2). s_id is used to indicate the number of the first subframe starting symbol occupied by the transmitted preamble, and its value range is 0≤s_id<14. t_id is used to indicate the number of the first subframe occupied by the preamble transmission resource, 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 the preamble transmission, '0' indicates a normal uplink carrier, and '1' indicates an auxiliary uplink carrier. Therefore, it is not repeated here. The NR-U RA-RNTI calculated by the above formula (3a) can be guaranteed not to be repeated within the 20ms RAR window.

[0163] RA-RNTI=1+s_id+14×t_id+14×40×f_id+14×40×8×ul_carrier_id

[0164] (3b)

[0165] The s_id, t_id, f_id and ul_carrier_id in formula (3a) are the same as those in formula (2a), and thus are not described in detail. In the implementation of this formula (3a), that is, when the ul_carrier_id indication information is also used to indicate the RAR window, it can be ensured that the RA-RNTI is not repeated within the 40ms window.

[0166] Embodiment 6

[0167] Generally, the resource used for PRACH transmission may start from any symbol of any subframe in any system frame. However, in this embodiment, the NRU PRACH transmission resource position is restricted, and the embodiment includes:

[0168] Step 601, after the LBT is successful, the NRU UE randomly selects a Preamble according to the system configuration information. The NRU UE is only allowed to send the preamble (send the PRACH) in some subframes (i.e., less than 10 subframes) in each system frame. Alternatively, the NRU UE is only allowed to send the PRACH in subframes at specific positions in each system frame. The UE can obtain its own RA-RNTI (random access network identifier) ​​according to the time and frequency domain position of the selected random access time slot. Specifically, the method for generating the RA-RNTI can adopt the existing technology, i.e., formula (2), or one of the methods mentioned in the aforementioned embodiments one to five can be adopted.

[0169] For example, the first column in Table 2 is the RACH configuration index number configured by the gNB to the UE; the second column is the Preamble type; the third and fourth columns are the periodic parameters of the RACH resources, where "1 0" indicates that the system frame with a system frame number equal to 0 divided by 1 is 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.

[0170] As described in Table 2, if the NRU UE is configured with a RACH with an index number of 105, only some NRU UEs are allowed to send PRACH in subframes with even system frame numbers, such as (0, 2, 4, 6, 8). For another part of the NRU UEs, PRACH may only be sent in subframes with odd system frame numbers, such as (1, 3, 5, 7, 9). In this case, the same number of available t_id indications can be used for different situations, such as when PRACH resources only appear in even subframes and when they appear in odd subframes, to indicate the subframe numbers of the PRACH resources in two system frames (as shown in Table 3), so that the generated RA-RNTI is guaranteed to be unique within a 20ms window at least when other parameters remain unchanged. The first column in Table 3 shows the different values ​​of t_id, the second column shows the system frame and subframe information corresponding to the t_id value when the PRACH transmission position is not limited, and the third column shows the t_id values ​​corresponding to the PRACH resources in different system frames and subframes when the PRACH transmission position is limited to an even number.

[0171] Steps 602-605 are similar to the aforementioned steps 102-105 and are not described in detail here.

[0172] Specifically, in steps 602-605, one or more of the aforementioned implementations can be combined to effectively extend the duration of the NRU RAR window, ensure that the calculation of RA-RNTI is not repeated within the extended RAR window, avoid UE misdetecting RAR information, cause subsequent random access collisions, and reduce access delay and access efficiency.

[0173] Table 2

[0174]

[0175] Table 3

[0176]

[0177] The specific implementation methods illustrated above further explain the purpose and technical solutions of this application in detail. It should be understood that the above description is only the specific implementation methods of this application and is not intended to limit the scope of protection of this application. Any modification, equivalent replacement, improvement, etc. made on the basis of the technical solution of this application shall be included in the scope of protection of this application.

[0178] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented by software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present invention is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can 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 can be transmitted from a website site, computer, server or data center to another website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state hard disk Solid State Disk (SSD)), etc.

Claims

1. A method for processing a random access network identifier RA-RNTI, characterized in that: include: After the listen-before-talk LBT is successful, a preamble and an available random access time-frequency resource RO are selected; sending the selected preamble on the selected RO; generating a RA-RNTI, the RA-RNTI being associated with the selected RO; Receiving information of a system frame where the selected preamble code is located; A physical downlink control channel PDCCH is detected in a random access response RAR window according to the RA-RNTI and information of the system frame where the selected preamble code is located.

2. The method according to claim 1, characterized in that The information of the system frame where the selected preamble code is located is carried in the downlink control information DCI.

3. The method according to claim 1 or 2, characterized in that: The RA-RNTI satisfies RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id, wherein s_id is used to indicate the starting symbol number of the first subframe occupied by the selected RO, 0≤s_id<14; t_id is used to indicate the first subframe number occupied by the selected RO, 0≤t_id<80, f_id indicates the number of the selected RO in the frequency domain, 0≤f_id<8; ul_carrier_id is used to indicate the position information of the selected preamble code in the RAR window.

4. The method according to any one of claims 1 to 3, characterized in that: The information of the system frame where the selected preamble code is located includes 1 bit, and the 1 bit is used to indicate whether the system frame where the selected preamble code is located is an odd system frame or an even system frame; or The information of the system frame where the selected preamble code is located includes 2 bits; The information of the system frame where the selected preamble code is located includes 3 bits.

5. The method according to any one of claims 2 to 4, characterized in that: The information of the system frame where the selected preamble code is located multiplexes one or more bits of the DCI.

6. The method according to claim 2, 3 or 5, characterized in that: The DCI is DCI_0, and the information of the system frame where the selected preamble code is located is carried in the reserved bits of the DCI_0.

7. The method according to claim 6, characterized in that The information of the system frame where the selected preamble code is located is carried in 2 bits, 3 bits or 4 bits of the reserved bits of the DCI_0.

8. The method according to any one of claims 1 to 7, characterized in that: The available RO includes: a subframe within a plurality of subframes within a configured system frame; the plurality of subframes is less than 10.

9. The method according to any one of claims 1 to 8, characterized in that: The selecting a preamble code includes: randomly selecting a preamble code according to system configuration information.

10. The method according to claim 1, characterized in that The information of the system frame where the preamble code is located is carried in the random access response media access control element RAR MAC CE.

11. The method according to claim 10, characterized in that The RAR MAC CE includes a SF indication subframe header, and the SF indication subframe header is used to indicate in which system frame the RA-RNTI-scrambled PDCCH corresponding to the preamble code is located.

12. The method according to claim 10, characterized in that The RAR MAC CE includes a SF indication subframe header, and the SF indication subframe header is used to indicate the system frame number where the preamble code is located.

13. The method according to claim 11 or 12, characterized in that: The SF indication subframe header is located after the BI subframe header and the RAPID subframe header.

14. The method according to any one of claims 11 to 13, characterized in that: The first three bits of the SF indication subframe header are 101, and the remaining 5 bits are used to indicate the system frame number where the RA-RNTI is located.

15. A method for processing a random access network identifier RA-RNTI, characterized in that: include: Receiving a preamble sent on a first random access time-frequency resource RO; generating a RA-RNTI, wherein the RA-RNTI is related to the RO; The information of the system frame in which the preamble code is located is sent.

16. The method according to claim 15, characterized in that The information of the system frame where the preamble code is located is carried in the downlink control information DCI.

17. The method according to claim 15 or 16, characterized in that The RA-RNTI satisfies RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id, wherein s_id is used to indicate the starting symbol number of the first subframe occupied by the RO, 0≤s_id<14; t_id is used to indicate the first subframe number occupied by the RO, 0≤t_id<80, f_id indicates the number of the RO in the frequency domain, 0≤f_id<8; ul_carrier_id is used to indicate the position information of the preamble code in the random access response RAR window.

18. The method according to any one of claims 15 to 17, characterized in that: The information of the system frame where the preamble code is located includes 1 bit, and the 1 bit is used to indicate whether the system frame where the preamble code is located is an odd system frame or an even system frame; or The information of the system frame where the preamble code is located includes 2 bits; The information of the system frame where the preamble code is located includes 3 bits.

19. The method according to any one of claims 16 to 18, characterized in that: The information of the system frame where the preamble code is located multiplexes one or more bits of the DCI.

20. The method according to any one of claims 16 to 19, characterized in that: The DCI is DCI_0, and the information of the system frame where the preamble code is located is carried in the reserved bits of the DCI_0.

21. The method according to claim 20, characterized in that The information of the system frame where the preamble code is located is carried in 2 bits, 3 bits or 4 bits of the reserved bits of the DCI_0.

22. A processing system, characterized in that: The method comprises a processor configured to implement the method according to any one of claims 1 to 21.

23. The processing system according to claim 22, characterized in that The processing system is a terminal side device or a network side device.

24. The processing system according to claim 22 or 23, characterized in that The processing system is a chip.

25. A computer-readable storage medium, characterized in that: The invention comprises a computer program which, when executed, causes a computer to execute the method according to any one of claims 1 to 21.

26. A computer program product, characterized in that The invention comprises a computer program which, when executed, causes a computer to execute the method according to any one of claims 1 to 21.

Images