CN112806088B

CN112806088B - Random access method, terminal equipment and network equipment

Info

Publication number: CN112806088B
Application number: CN201980064762.9A
Authority: CN
Inventors: 石聪
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2019-03-27
Filing date: 2019-03-27
Publication date: 2023-06-02
Anticipated expiration: 2039-03-27
Also published as: CN112806088A; WO2020191679A1

Abstract

The embodiment of the application provides a random access method, terminal equipment and network equipment, wherein in two-step random access, the terminal equipment in an idle state or a deactivated state can blindly detect Msg B based on a first RNTI after the Msg A is sent. The random access method comprises the following steps: the terminal equipment sends first information in a two-step random access process; the terminal device monitors a PDCCH scrambled by the first RNTI, the PDCCH being used for scheduling a PDSCH carrying second information in a two-step random access procedure.

Description

Random access method, terminal equipment and network equipment

Technical Field

Embodiments of the present application relate to the field of communications, and more particularly, to a random access method, a terminal device, and a network device.

Background

Two-step random access can be supported in a New air interface (NR) system, in which Message 1 (Message 1, msg 1) and Message 3 (Msg 3) in a four-step random access process can be transmitted as a first Message (Message a, msgA) in the two-step random access process, and Message 2 (Msg 2) and Message 2 (Msg 4) in the four-step random access process can be transmitted as a second Message (Message B, msgB) in the two-step random access process. However, since the terminal device in the idle state or the deactivated state has no cell radio network temporary identifier (Cell Radio Network Temporary Identity, C-RNTI) information in the two-step random access procedure, how to blindly check the MsgB after the terminal device has sent the MsgA is a problem to be solved.

Disclosure of Invention

The embodiment of the application provides a random access method, terminal equipment and network equipment, wherein in two-step random access, the terminal equipment in an idle state or a deactivated state can blindly detect MsgB based on a first RNTI after the MsgA is sent.

In a first aspect, a random access method is provided, the method including:

the terminal equipment sends first information in a two-step random access process;

the terminal device listens to a physical downlink control channel (Physical Downlink Control Channel, PDCCH) scrambled by a first RNTI, the PDCCH being used for scheduling a PDSCH carrying second information in a two-step random access procedure.

It should be noted that, after the terminal device monitors the PDCCH scrambled by the first radio network temporary identifier (Radio Network Temporary Identity, RNTI), the terminal device may determine, according to the first RNTI, that the PDCCH is scheduled to be sent to its own physical downlink shared channel (Physical Downlink Shared Channel, PDSCH), and the PDSCH carries the second information in the two-step random access procedure.

Optionally, the terminal device is in a deactivated state or an idle state.

It should be appreciated that the first RNTI is a newly defined RNTI, unlike other existing RNTIs, so that collisions with existing RNTIs such as Random Access RNTIs (RA-RNTIs) may be avoided.

In a second aspect, a random access method is provided, the method comprising:

the network equipment receives first information in a two-step random access process;

the network device transmits a PDCCH scrambled by the first RNTI, the PDCCH being used for scheduling a PDSCH carrying second information in a two-step random access procedure.

In a third aspect, a terminal device is provided for performing the method in the first aspect or each implementation manner thereof.

Specifically, the terminal device comprises functional modules for performing the method of the first aspect or its implementation manner.

In a fourth aspect, a network device is provided for performing the method of the second aspect or implementations thereof.

In particular, the network device comprises functional modules for performing the method of the second aspect or implementations thereof described above.

In a fifth aspect, a terminal device is provided comprising a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory and executing the method in the first aspect or various implementation manners thereof.

In a sixth aspect, a network device is provided that includes a processor and a memory. The memory is for storing a computer program and the processor is for calling and running the computer program stored in the memory for performing the method of the second aspect or implementations thereof described above.

A seventh aspect provides an apparatus for implementing the method of any one of the first to second aspects or each implementation thereof.

Specifically, the device comprises: a processor for calling and running a computer program from a memory, causing a device in which the apparatus is installed to perform the method as in any one of the first to second aspects or implementations thereof described above.

In an eighth aspect, a computer-readable storage medium is provided for storing a computer program that causes a computer to perform the method of any one of the above-described first to second aspects or implementations thereof.

A ninth aspect provides a computer program product comprising computer program instructions for causing a computer to perform the method of any one of the first to second aspects or implementations thereof.

In a tenth aspect, there is provided a computer program which, when run on a computer, causes the computer to perform the method of any one of the first to second aspects or implementations thereof.

Through the technical scheme, in the two-step random access, after the terminal equipment in the idle state or the deactivated state transmits the Msg A, the terminal equipment can blindly detect the Msg B based on the first RNTI.

Drawings

Fig. 1 is a schematic diagram of a communication system architecture provided in an embodiment of the present application.

Fig. 2 is a schematic diagram of a four-step random access provided in an embodiment of the present application.

Fig. 3 is a schematic diagram of a four-step random access to a two-step random access according to an embodiment of the present application.

Fig. 4 is a schematic flow chart of a random access method according to an embodiment of the present application.

Fig. 5 is a schematic block diagram of a terminal device according to an embodiment of the present application.

Fig. 6 is a schematic block diagram of a network device provided according to an embodiment of the present application.

Fig. 7 is a schematic block diagram of a communication device provided according to an embodiment of the present application.

Fig. 8 is a schematic block diagram of an apparatus provided in accordance with an embodiment of the present application.

Fig. 9 is a schematic block diagram of a communication system provided according to an embodiment of the present application.

Detailed Description

The following description of the technical solutions in the embodiments of the present application will be made with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art without undue burden for the embodiments herein, are intended to be within the scope of the present application.

The embodiments of the present application may be applied to various communication systems, for example: global system for mobile communications (Global System of Mobile communication, GSM), code division multiple access (Code Division Multiple Access, CDMA) system, wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA) system, general packet Radio service (General Packet Radio Service, GPRS), long term evolution (Long Term Evolution, LTE) system, long term evolution advanced (Advanced long term evolution, LTE-a) system, new Radio (NR) system, evolution system of NR system, LTE-based access to unlicensed spectrum, LTE-U) system over unlicensed spectrum, NR (NR-based access to unlicensed spectrum, NR-U) system over unlicensed spectrum, universal mobile communication system (Universal Mobile Telecommunication System, UMTS), wireless local area network (Wireless Local Area Networks, WLAN), wireless fidelity (Wireless Fidelity, wiFi), next generation communication system or other communication system, etc.

Generally, the number of connections supported by the conventional communication system is limited and easy to implement, however, with the development of communication technology, the mobile communication system will support not only conventional communication but also, for example, device-to-Device (D2D) communication, machine-to-machine (Machine to Machine, M2M) communication, machine type communication (Machine Type Communication, MTC), inter-vehicle (Vehicle to Vehicle, V2V) communication, and the like, to which the embodiments of the present application can also be applied.

Optionally, the communication system in the embodiment of the present application may be applied to a carrier aggregation (Carrier Aggregation, CA) scenario, a dual connectivity (Dual Connectivity, DC) scenario, and a Stand Alone (SA) fabric scenario.

The frequency spectrum of the application in the embodiments of the present application is not limited. For example, embodiments of the present application may be applied to licensed spectrum as well as unlicensed spectrum.

Exemplary, a communication system 100 to which embodiments of the present application apply is shown in fig. 1. The communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal device 120 (or referred to as a communication terminal, terminal). Network device 110 may provide communication coverage for a particular geographic area and may communicate with terminal devices located within the coverage area.

Fig. 1 illustrates one network device and two terminal devices by way of example, and alternatively, the communication system 100 may include a plurality of network devices and may include other numbers of terminal devices within the coverage area of each network device, which is not limited in this embodiment of the present application.

Optionally, the communication system 100 may further include a network controller, a mobility management entity, and other network entities, which are not limited in this embodiment of the present application.

It should be understood that a device having a communication function in a network/system in an embodiment of the present application may be referred to as a communication device. Taking the communication system 100 shown in fig. 1 as an example, the communication device may include a network device 110 and a terminal device 120 with communication functions, where the network device 110 and the terminal device 120 may be specific devices described above, and are not described herein again; the communication device may also include other devices in the communication system 100, such as a network controller, a mobility management entity, and other network entities, which are not limited in this embodiment of the present application.

It should be understood that the terms "system" and "network" are used interchangeably herein. The term "and/or" is herein merely an association relationship describing an associated object, meaning that there may be three relationships, e.g., a and/or B, may represent: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.

Embodiments of the present application describe various embodiments in connection with a terminal device and a network device, wherein: a terminal device may also be called a User Equipment (UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a User terminal, a wireless communication device, a User agent, a User device, or the like. The terminal device may be a Station (ST) in a WLAN, may be a cellular telephone, a cordless telephone, a session initiation protocol (Session Initiation Protocol, SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital assistant (Personal Digital Assistant, PDA) device, a handheld device with wireless communication functionality, a computing device or other processing device connected to a wireless modem, a vehicle mounted device, a wearable device, and a next generation communication system, such as a terminal device in an NR network or a terminal device in a future evolved public land mobile network (Public Land Mobile Network, PLMN) network, etc.

By way of example, and not limitation, in embodiments of the present application, the terminal device may also be a wearable device. The wearable device can also be called as a wearable intelligent device, and is a generic name for intelligently designing daily wear by applying wearable technology and developing wearable devices, such as glasses, gloves, watches, clothes, shoes and the like. The wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user. The wearable device is not only a hardware device, but also can realize a powerful function through software support, data interaction and cloud interaction. The generalized wearable intelligent device includes full functionality, large size, and may not rely on the smart phone to implement complete or partial functionality, such as: smart watches or smart glasses, etc., and focus on only certain types of application functions, and need to be used in combination with other devices, such as smart phones, for example, various smart bracelets, smart jewelry, etc. for physical sign monitoring.

The network device may be a device for communicating with the mobile device, the network device may be an Access Point (AP) in WLAN, a base station (Base Transceiver Station, BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (Evolutional Node B, eNB or eNodeB) in LTE, or a relay station or an Access Point, or a vehicle device, a wearable device, and a network device (gNB) in NR network, or a network device in future evolved PLMN network, etc.

In the embodiment of the present application, the network device provides services for a cell, and the terminal device communicates with the network device through a transmission resource (for example, a frequency domain resource, or a spectrum resource) used by the cell, where the cell may be a cell corresponding to the network device (for example, a base station), and the cell may belong to a macro base station, or may belong to a base station corresponding to a Small cell (Small cell), where the Small cell may include: urban cells (Metro cells), micro cells (Micro cells), pico cells (Pico cells), femto cells (Femto cells) and the like, and the small cells have the characteristics of small coverage area and low transmitting power and are suitable for providing high-rate data transmission services.

After the cell search procedure, the terminal device has acquired downlink synchronization with the cell, and thus the terminal device can receive downlink data. But the terminal equipment can only perform uplink transmission if uplink synchronization is obtained with the cell. The terminal device can establish a connection with the cell and acquire uplink synchronization through a random access procedure (Random Access Procedure). In order to facilitate understanding of the scheme of the embodiment of the present application, the random access procedure will be briefly described below with reference to fig. 2.

The random access procedure may be triggered by the following events in general:

(1) Initial Access (Initial Access).

The terminal device may enter an RRC CONNECTED state (rrc_connected) from a radio resource control (Radio Resource Control, RRC) IDLE state (rrc_idle state).

(2) RRC connection reestablishment procedure (RRC Connection Re-establishment procedure).

(3) Handover (Handover).

At this time, the terminal device is in a connected state, and needs to establish uplink synchronization with a new cell.

(4) In the RRC connected state, when downlink data or uplink data arrives, the uplink is in an "unsynchronized" state (DL or UL data arrival during RRC _ CONNECTED when UL synchronisation status is "non-synchronized").

(5) In the RRC connected state, when uplink data arrives, no physical uplink control channel (Physical Uplink Control Channel, PUCCH) resources are available for scheduling request (Scheduling Request, SR) transmission (UL data arrival during RRC _ CONNECTED when there are no PUCCH resources for SR available).

(6) SR failure (SR failure).

(7) Request for RRC in synchronous configuration (Request by RRC upon synchronous reconfiguration).

(8) The terminal device transitions from the RRC INACTIVE state (Transition from RRC _inactive).

(9) Time alignment is established upon SCell addition (To establish time alignment at SCell addition).

(10) The terminal device requests other system information (Other System Information, OSI).

(11) The terminal device needs to perform recovery (Beam failure recovery) of Beam (Beam) failure.

In an NR system, two random access modes can be supported: a contention-based random access scheme and a non-contention-based random access scheme. The following briefly describes a contention-based four-step random access procedure, as shown in fig. 2, which includes:

step 1, a terminal device sends a random access Preamble (Preamble, i.e. message1, msg 1) to a network device.

The random access preamble may also be referred to as a preamble, a random access preamble sequence, a preamble sequence, or the like.

In particular, the terminal device may select physical random access channel (Physical Random Access Channel, PRACH) resources, which may include time domain resources, frequency domain resources, and code domain resources. Next, the terminal device may send the selected Preamble on the selected PRACH resource. The network device may estimate its transmission delay with the terminal device based on the Preamble and calibrate the uplink timing (timing) accordingly, and may generally determine the size of resources required by the terminal device to transmit message 3 (Msg 3).

Step 2, the network device sends a random access response (Random Access Response, RAR, i.e. message2, msg 2) to the terminal device

After the terminal device sends the Preamble to the network device, a RAR window may be opened, and a corresponding physical downlink control channel (Physical Downlink Control Channel, PDCCH) may be detected in the RAR window according to the random access radio network temporary identifier (Random Access Radio Network Temporary Identifier, RA-RNTI). If the terminal device detects the PDCCH scrambled by the RA-RNTI, it can obtain the physical downlink shared channel (Physical Downlink Shared Channel, PDSCH) scheduled by the PDCCH. Wherein, the PDSCH includes a RAR corresponding to the Preamble.

If the RAR returned by the network device is not received within the RAR window, the terminal device may consider that the random access procedure fails. It should be appreciated that both the terminal device and the network device need to uniquely determine the value of the RA-RNTI, otherwise the terminal device cannot decode the RAR.

Alternatively, in the embodiment of the present application, the RA-RNTI may be calculated by receiving and transmitting the time-frequency location of the Preamble that is clear to both parties. For example, the RA-RNTI associated with the Preamble may be calculated by equation 1:

RA-rnti=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_c_id equation 1

Where s_id is an index (0.ltoreq.s_id < 14) of a first orthogonal frequency division multiplexing (Orthogonal Frequency Division Multiplexing, OFDM) symbol of the PRACH resource, t_id is an index (0.ltoreq.t_id < 80) of a first slot of the PRACH resource in one system frame, f_id is an index (0.ltoreq.f_id < 8) of the PRACH resource in the frequency domain, ul_c_id is an Uplink carrier (0 represents Normal Uplink (NUL) carrier) for transmitting the Preamble, and 1 represents a supplementary Uplink (Supplementary Uplink, SUL) carrier. For frequency division multiplexing (Frequency Division Duplexing, FDD), there is only one PRACH resource per subframe, so the f_id is fixed to 0.

In other words, since the Preamble time-frequency position sent by the terminal device is determined, the network device obtains the time-frequency position of the Preamble when decoding the Preamble, so that the RA-RNTI needed to be used in the RAR can be known. When the terminal device successfully receives an RAR (decoded using the determined RA-RNTI) and the random access sequence identifier (Random Access Preamble Identifier, RAPID) in the RAR is the same as the Preamble index transmitted by the terminal device, the terminal device may consider that the RAR was successfully received, and may stop detecting the PDCCH scrambled by the RA-RNTI.

And 3, the terminal equipment sends Msg 3.

After receiving the RAR message, the terminal device determines whether the RAR is an RAR message belonging to itself, for example, the terminal device may check by using the preamble index, and after determining that the RAR message is an RAR message belonging to itself, may generate Msg3 in the RRC layer and send the Msg3 to the network device, where the terminal device needs to carry identification information of the terminal device, and so on.

Wherein Msg3 is mainly used for informing the network device of the trigger event of the random access. The Msg3 sent by the terminal device in step 3 may comprise different content for different random access trigger events.

For example, for the initial access scenario, msg3 may include an RRC connection request message generated by the RRC layer (RRC Setup Request). In addition, the Msg3 may also carry, for example, a 5G-service temporary mobile subscriber identity (Serving-Temporary Mobile Subscriber Identity, S-TMSI) or a random number of the terminal device, etc.

For another example, for an RRC connection reestablishment scenario, msg3 may include an RRC connection reestablishment request message generated by the RRC layer (RRC Reestabilshment Request). In addition, the Msg3 may also carry, for example, a cell radio network temporary identity (Cell Radio Network Temporary Identifier, C-RNTI) or the like.

For another example, for a handover scenario, msg 3 may include an RRC layer generated RRC handover confirm message (RRC Handover Confirm) that carries the C-RNTI of the terminal device. In addition, msg 3 may also carry information such as buffer status reports (Buffer Status Report, BSR). For other trigger events, such as the scenario of up/down data arrival, msg 3 may include at least the C-RNTI of the terminal device.

Step 4, the network device sends a conflict resolution message (contention resolution), i.e. Msg4, to the terminal device.

The network device sends Msg4 to the terminal device, and the terminal device receives Msg4 correctly to complete contention resolution (Contention Resolution). For example, during RRC connection establishment, an RRC connection establishment message may be carried in Msg4.

Since the terminal device in step 3 can carry its own unique identifier in Msg 3, the network device will carry the unique identifier of the terminal device in Msg4 in the contention resolution mechanism to designate the terminal device that wins the contention. While other terminal devices that are not winning in contention resolution will re-initiate random access.

It should be appreciated that in the embodiments of the present application, contention conflict resolution may be in two ways:

in one approach, if the terminal device carries a C-RNTI at Msg 3, msg4 may schedule a PDCCH scrambled with the C-RNTI.

In the second mode, if the terminal device does not carry the C-RNTI in the Msg 3, such as initial access, the Msg 4 may schedule with the TC-RNTI scrambled PDCCH. At this time, the resolving of the contention conflict may be to receive PDSCH of Msg 4 through the terminal device, obtain a conflict resolution ID, and determine whether to resolve the conflict by matching the conflict resolution ID with a common control channel (Common control channel, CCCH) service data unit (Service Data Unit, SDU) in Msg 3.

The time delay of the four-step random access is relatively large, and the method is unsuitable for a low-time delay high-reliability scene in 5G. The scheme of the two-step random access process is provided by considering the characteristics of the low-delay high-reliability related service. As shown in fig. 3, in the two-step random access procedure, simply speaking, the first step and the third step of the four-step random access procedure are combined to be the first step in the two-step random access procedure, and the second step and the fourth step of the four-step random access procedure are combined to be the second step in the two-step random access procedure.

More specifically, the two-step random access procedure may include:

the first step: the terminal device sends a first message to the network device.

The first message may consist of a Preamble and a Payload (Payload), where the Preamble is a Preamble of four-step random access, and the Preamble is transmitted on a PRACH resource, and the Payload mainly carries information in Msg 3 in the four-step random access. For example, CCCH SDUs may be included, such as corresponding to random access in RRC idle state, or C-RNTI MAC Control Element (CE) may be included, such as mainly corresponding to random access in RRC connected state. Payload may be carried on an uplink channel, which may be, for example, a physical uplink shared channel (Physical Uplink Shared Channel, PUSCH).

It should be understood that the first message may carry part or all of the information carried in the Preamble and Msg 3 in the four-step random access procedure.

And a second step of: the network device sends a second message to the terminal device.

If the network device successfully receives the first message sent by the terminal device, the network device may send a second message to the terminal device. The second message may include part or all of the information carried in Msg 2 and Msg 4 in the four-step random access procedure. The names of the first message and the second message are not limited, that is, they may be expressed as other names. For example, the first message may also be referred to as Msg a, random access request message, or new Msg 1, and the second message may also be referred to as Msg B, random access response information, or new Msg 2.

It should be understood that fig. 3 is only a specific implementation of the two-step random access procedure, and should not limit the scope of protection of the present application.

However, in the two-step random access procedure, the terminal device in the idle state or the deactivated state has no C-RNTI information in the two-step random access procedure, so how to blindly check Msg B after Msg a is transmitted is a problem. In a four-step random access, the terminal device decodes the RA-RNTI scrambled PDCCH, i.e. in a four-step random access, the network device uses the RA-RNTI to schedule Msg 4. If the network device still uses the RA-RNTI to schedule the msb, for the terminal device of the four-step random access, when the terminal device detects the PDCCH scrambled by the RA-RNTI, it can distinguish whether to issue the RAR of the terminal device or not only after decoding the PDSCH (i.e., payload) scheduled by the PDCCH, thereby increasing the overhead caused by the terminal device of the four-step random access to decode the PDCCH.

The two-step random access scheme devised by the present application in view of the above technical problems is described in detail below.

Fig. 4 is a schematic flow chart of a random access method 200 according to an embodiment of the present application, as shown in fig. 4, the method 200 may include the following:

s210, a terminal device sends first information in a two-step random access process to a network device;

s220, the network equipment receives the first information;

s230, the network equipment transmits a PDCCH scrambled by a first RNTI, wherein the PDCCH is used for scheduling a PDSCH carrying second information in a two-step random access process;

s240, the terminal equipment monitors the PDCCH scrambled by the first RNTI.

It should be appreciated that the first information may correspond to the first message (Msg a) in fig. 3 and the second information may correspond to the second message (Msg B) in fig. 3.

It should be noted that, after the terminal device monitors the PDCCH scrambled by the first RNTI, the terminal device may determine that the PDCCH is scheduled by the PDSCH and the PDSCH carries the second information in the two-step random access procedure according to the first RNTI.

Optionally, the terminal device is in a deactivated state or an idle state.

It will be appreciated that the first RNTI is a newly defined RNTI, unlike existing other RNTIs, so that collisions with existing, e.g., RA-RNTIs, etc., can be avoided.

Optionally, the first information comprises a random access preamble and/or a first terminal identity. The random access preamble is transmitted on PRACH resources, the first terminal identity may be carried in a payload, and the payload is transmitted by a first PUSCH.

Optionally, in this embodiment of the present application, the first RNTI is an RA-RNTI determined at least according to resource information of a first PUSCH, where the first information includes a random access preamble, and the resource information of the first PUSCH is associated with PRACH resources that transmit the random access preamble.

Specifically, the association relationship between PUSCH resources and PRACH resources may be one-to-one, or many-to-one, or one-to-many, which is not limited in the embodiment of the present application.

Alternatively, the association between the PUSCH resource and the PRACH resource may be configured by the network device, for example, the network device configures the association through a broadcast message. The association relationship between the PUSCH resource and the PRACH resource may also be preconfigured or agreed by a protocol.

Optionally, as example 1, the first RNTI is an RA-RNTI determined at least from time domain resources of the first PUSCH.

Specifically, in example 1, the first RNTI is determined according to the following equation 2:

First rnti=1+s_id+14×t_id+14×80×f_id+14×80× 8×ul_c_id+n1×pusch_s_id+n2×pusch_t_id, equation 2

Wherein s_id is the index of the first OFDM symbol in the PRACH resource, and s_id is more than or equal to 0 and less than or equal to 14; t_id is the index of the first time slot in the PRACH resource on a system frame, and t_id is more than or equal to 0 and less than or equal to 80; f_id is the index of the PRACH resource in the frequency domain, and f_id is more than or equal to 0 and less than or equal to 8; ul_c_id is the uplink UL carrier for the random access preamble transmission; pusch_s_id is the index of the first OFDM symbol in the time domain resource of the first PUSCH; pusch_t_id is the index of the first slot in the time domain resource of the first PUSCH in the system frame; n1 and N2 are one value that is preconfigured.

Alternatively, as example 2, the first RNTI is an RA-RNTI determined at least from frequency domain resources of the first PUSCH.

Specifically, in example 2, the first RNTI is determined according to the following equation 3:

first rnti=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_c_id+n3×pusch_f_id, formula 3

Wherein s_id is the index of the first OFDM symbol in the PRACH resource, and s_id is more than or equal to 0 and less than or equal to 14; t_id is the index of the first time slot in the PRACH resource on a system frame, and t_id is more than or equal to 0 and less than or equal to 80; f_id is the index of the PRACH resource in the frequency domain, and f_id is more than or equal to 0 and less than or equal to 8; ul_c_id is the uplink UL carrier for the random access preamble transmission; pusch_f_id is an index of the frequency domain resource of the first PUSCH in the frequency domain; pusch_t_id is the index of the first slot in the time domain resource of the first PUSCH in the system frame; n3 is a pre-configured value.

Optionally, as example 3, the first RNTI is an RA-RNTI determined at least from a resource location of the first PUSCH.

Specifically, in example 3, the first RNTI is determined according to the following equation 4:

first rnti=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_c_id+n4×pusch_p_id, equation 4

Wherein s_id is the index of the first OFDM symbol in the PRACH resource, and s_id is more than or equal to 0 and less than or equal to 14; t_id is the index of the first time slot in the PRACH resource on a system frame, and t_id is more than or equal to 0 and less than or equal to 80; f_id is the index of the PRACH resource in the frequency domain, and f_id is more than or equal to 0 and less than or equal to 8; ul_c_id is the uplink UL carrier for the random access preamble transmission; pusch_f_id is an index of the frequency domain resource of the first PUSCH in the frequency domain; pusch_p_id is an index of the resource location of the first PUSCH relative to the resource location of the PRACH resource; n4 is a pre-configured value.

In formulas 2 to 4, ul_c_id is an uplink carrier for transmitting a Preamble (0 represents a NUL carrier, 1 represents a SUL carrier.

Optionally, in an embodiment of the present application, the first RNTI is determined according to a first terminal identifier and an RNTI interval, where the first information includes the first terminal identifier.

Specifically, the first RNTI is determined according to the following equation 5:

first rnti=rnti_l+first terminal identity mod (rnti_h-rnti_l), equation 5

Wherein, RNTI_L is the minimum value in the RNTI zone, RNTI_H is the maximum value in the RNTI zone, and mod is modulo operation.

Optionally, the RNTI interval is configured for a network device. The network device may consider whether or not it may collide with other RNTIs, for example, whether or not it may collide with RNTIs such as RA-RNTIs, C-RNTIs, etc., when configuring the RNTI range, so as to avoid collision with other RNTIs as much as possible.

Optionally, in an embodiment of the present application, the network device may configure the RNTI interval after receiving the first information. Of course, the RNTI region may be preconfigured on the network side.

Optionally, the network device sends a system broadcast message, where the system broadcast message includes the RNTI interval, so that the terminal device obtains the RNTI interval by receiving the system broadcast message.

Specifically, the network device may broadcast only the minimum value rnti_l and the maximum value rnti_h in the RNTI interval to the terminal device through a system broadcast message.

Optionally, in an embodiment of the present application, the first RNTI is determined according to a first terminal identifier, where the first information includes the first terminal identifier.

Specifically, the first RNTI is M-bit information in the first terminal identifier, where the first terminal identifier includes N-bit information, M and N are positive integers, and M is smaller than N.

For example, the first RNTI is the first M-bit information in the first terminal identifier, or the first RNTI is the second M-bit information in the first terminal identifier, or the first RNTI is the M-bit information in the middle position in the first terminal identifier.

For example, m=16. That is, the first RNTI is the first 16-bit information in the first terminal identifier, or the first RNTI is the last 16-bit information in the first terminal identifier, or the first RNTI is the 16-bit information in the middle position in the first terminal identifier.

Optionally, in an embodiment of the present application, the first terminal identifier includes, but is not limited to, at least one of the following:

a random number or 5G-service temporary mobile subscriber identity (5G-Serving-Temporary Mobile Subscriber Identity, 5G-S-TMSI) used by the terminal device during the initial access in the idle state,

a recovery identity or a message authentication code (Message Authentication Code Integrity, MAC-I) for recovering integrity, which is used by the terminal device during the recovery of the deactivated state connection,

The terminal device reestablishes the terminal identity in part used in the RRC connection reestablishment procedure.

Optionally, the recovery identity is an Inactive radio network temporary identity (I-RNTI) or a short I-RNTI (short I-RNTI).

Optionally, the reestablishing terminal identity includes at least one of:

C-RNTI, short MAC-I of the terminal equipment under the source cell, physical cell identification (Physical Cell Identifier, PCI) of the source cell.

Optionally, in this embodiment of the present application, the first RNTI is determined according to a second RNTI and the RNTI interval, the second RNTI is an RA-RNTI determined at least according to resource information of a first PUSCH, the first information includes a random access preamble, and the resource information of the first PUSCH is associated with PRACH resources that transmit the random access preamble.

Specifically, the first RNTI is determined according to the following equation 6:

first rnti=rnti_l+second RNTI mod (rnti_h-rnti_l), equation 6

Optionally, the second RNTI is an RA-RNTI determined at least from time domain resources of the first PUSCH.

Specifically, the second RNTI is determined according to the following equation 7:

Second rnti=1+s_id+14×t_id+14×80×f_id+14×80× 8×ul_c_id+n1×pusch_s_id+n2×pusch_t_id, equation 7

Optionally, the second RNTI is an RA-RNTI determined at least from frequency domain resources of the first PUSCH.

Specifically, the second RNTI is determined according to the following equation 8:

second rnti=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_c_id+n3×pusch_f_id, formula 8

Optionally, the second RNTI is an RA-RNTI determined at least from a resource location of the first PUSCH.

Specifically, the second RNTI is determined according to the following equation 9:

second rnti=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_c_id+n4×pusch_p_id, equation 9

In formulas 7 to 9, ul_c_id is an uplink carrier for transmitting a Preamble (0 represents a NUL carrier, 1 represents a SUL carrier.

Optionally, in an embodiment of the present application, the first RNTI is determined according to a third RNTI and the RNTI interval, where the third RNTI is RA-RNTI.

Specifically, the first RNTI is determined according to the following equation 10:

first rnti=rnti_l+third RNTI mod (rnti_h-rnti_l), equation 10

Optionally, the third RNTI is determined according to the following equation 11:

third rnti=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_c_id, equation 11

Wherein s_id is an index of a first OFDM symbol in the PRACH resource, and s_id is more than or equal to 0 and less than or equal to 14; t_id is the index of the first time slot in the PRACH resource on a system frame, and t_id is more than or equal to 0 and less than or equal to 80; f_id is an index of the PRACH resource in a frequency domain, and f_id is more than or equal to 0 and less than or equal to 8; ul_c_id is the uplink UL carrier for the random access preamble transmission.

In equation 11, ul_c_id is an uplink carrier for transmitting a Preamble (0 indicates a NUL carrier, 1 indicates a SUL carrier, and for FDD, there is only one PRACH resource per subframe, and thus, f_id is fixed to 0.

It should be noted that, in the four-step random access, the terminal device decodes the PDCCH scrambled by the RA-RNTI, and the third RNTI may be the RA-RNTI in the four-step random access, that is, the third RNTI may also be calculated by the above formula 1.

Therefore, in the embodiment of the present application, in the two-step random access, after the terminal device in the idle state or the deactivated state has sent the MsgA, the msb may be blind-detected based on the first RNTI. In addition, because the first RNTI is a newly defined RNTI, the conflict between the first RNTI and the RA-RNTI can be reduced to a certain extent, and the expenditure of detecting the PDSCH by the terminal equipment in the four-step random access process is reduced.

Fig. 5 shows a schematic block diagram of a terminal device 300 according to an embodiment of the present application. As shown in fig. 5, the terminal device 300 includes:

a communication unit 310, configured to send first information in a two-step random access procedure;

the communication unit 310 is further configured to monitor a PDCCH scrambled by the first RNTI, the PDCCH being used to schedule a PDSCH carrying the second information in the two-step random access procedure.

Optionally, the first RNTI is an RA-RNTI determined at least according to resource information of a first PUSCH, wherein the first information includes a random access preamble, and the resource information of the first PUSCH is associated with PRACH resources transmitting the random access preamble.

Optionally, the first RNTI is an RA-RNTI determined at least from time domain resources of the first PUSCH.

Optionally, the first RNTI is determined according to the following formula:

First rnti=1+s_id+14×t_id+14×80×f_id+14×80× 8×ul_c_id+n1×pusch_s_id+n2×pusch_t_id,

Optionally, the first RNTI is an RA-RNTI determined at least from frequency domain resources of the first PUSCH.

Optionally, the first RNTI is determined according to the following formula:

the first rnti=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_c_id+n3×pusch_f_id,

Optionally, the first RNTI is an RA-RNTI determined at least from a resource location of the first PUSCH.

Optionally, the first RNTI is determined according to the following formula:

the first rnti=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_c_id+n4×pusch_p_id,

Optionally, the first RNTI is determined according to a first terminal identifier and an RNTI interval, where the first information includes the first terminal identifier.

Optionally, the first RNTI is determined according to the following formula:

first rnti=rnti_l+first terminal identity mod (rnti_h-rnti_l),

Optionally, the first RNTI is determined according to a first terminal identity, wherein the first information includes the first terminal identity.

Optionally, the first RNTI is M-bit information in the first terminal identifier, where the first terminal identifier includes N-bit information, M and N are positive integers, and M is smaller than N.

Optionally, the first RNTI is the first M-bit information in the first terminal identifier, or the first RNTI is the second M-bit information in the first terminal identifier, or the first RNTI is the M-bit information in the middle position in the first terminal identifier.

Alternatively, m=16.

Optionally, the first terminal identification includes at least one of:

a random number or 5G-S-TMSI used by the terminal device during the initial access in the idle state,

the recovery identity or recovery MAC-I used by the terminal device in the process of deactivating the connection recovery,

Optionally, the recovery identity is either an I-RNTI or a short I-RNTI.

Optionally, the reestablishing terminal identity includes at least one of:

C-RNTI, short MAC-I of the terminal equipment under the source cell and PCI of the source cell.

Optionally, the first RNTI is determined according to a second RNTI and an RNTI interval, the second RNTI is an RA-RNTI determined at least according to resource information of a first PUSCH, the first information includes a random access preamble, and the resource information of the first PUSCH is associated with PRACH resources transmitting the random access preamble.

Optionally, the first RNTI is determined according to the following formula:

first rnti=rnti_l+second RNTI mod (rnti_h-rnti_l),

Optionally, the second RNTI is determined according to the following formula:

second rnti=1+s_id+14×t_id+14×80×f_id+14×80× 8×ul_c_id+n1×pusch_s_id+n2×pusch_t_id,

Optionally, the second RNTI is determined according to the following formula:

the second rnti=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_c_id+n3×pusch_f_id,

Optionally, the second RNTI is determined according to the following formula:

the second rnti=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_c_id+n4×pusch_p_id,

Optionally, the first RNTI is determined according to a third RNTI and an RNTI range, wherein the third RNTI is RA-RNTI.

Optionally, the first RNTI is determined according to the following formula:

first rnti=rnti_l+third RNTI mod (rnti_h-rnti_l),

Optionally, the third RNTI is determined according to the following formula:

the third rnti=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_c_id,

wherein s_id is the index of the first OFDM symbol in the PRACH resource, and s_id is more than or equal to 0 and less than or equal to 14; t_id is the index of the first time slot in the PRACH resource on a system frame, and t_id is more than or equal to 0 and less than or equal to 80; f_id is the index of the PRACH resource in the frequency domain, and f_id is more than or equal to 0 and less than or equal to 8; ul_c_id is the uplink UL carrier for the random access preamble transmission.

Optionally, the communication unit 310 is further configured to receive a system broadcast message, where the system broadcast message includes the RNTI interval.

Optionally, the terminal device 300 is in an idle state or a deactivated state.

It should be understood that the terminal device 300 according to the embodiment of the present application may correspond to the terminal device in the embodiment of the method of the present application, and the foregoing and other operations and/or functions of each unit in the terminal device 300 are respectively for implementing the corresponding flow of the terminal device in the method 200 shown in fig. 4, which is not described herein for brevity.

Fig. 6 shows a schematic block diagram of a network device 400 according to an embodiment of the present application. As shown in fig. 6, the network device 400 includes:

a communication unit 410, configured to receive first information in a two-step random access procedure;

the communication unit 410 is further configured to send a PDCCH scrambled by the first RNTI, the PDCCH being used for scheduling a PDSCH carrying the second information in the two-step random access procedure.

Optionally, the first RNTI is determined according to the following formula:

the first rnti=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_c_id+n3×pusch_f_id,

Optionally, the first RNTI is determined according to the following formula:

the first rnti=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_c_id+n4×pusch_p_id,

Optionally, the first RNTI is determined according to the following formula:

first rnti=rnti_l+first terminal identity mod (rnti_h-rnti_l),

Alternatively, m=16.

Optionally, the first terminal identification includes at least one of:

a random number or 5G-S-TMSI used by the peer device during the initial access in the idle state,

the recovery identity or recovery MAC-I used by the peer device in the process of deactivating the connection recovery,

The opposite terminal equipment reestablishes the terminal identification partially in the process of RRC connection reestablishment.

Optionally, the recovery identity is either an I-RNTI or a short I-RNTI.

Optionally, the reestablishing terminal identity includes at least one of:

C-RNTI, short MAC-I of opposite terminal equipment under a source cell and PCI of the source cell.

Optionally, the first RNTI is determined according to the following formula:

first rnti=rnti_l+second RNTI mod (rnti_h-rnti_l),

Optionally, the second RNTI is determined according to the following formula:

the second rnti=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_c_id+n3×pusch_f_id,

Optionally, the second RNTI is determined according to the following formula:

the second rnti=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_c_id+n4×pusch_p_id,

Optionally, the first RNTI is determined according to the following formula:

first rnti=rnti_l+third RNTI mod (rnti_h-rnti_l),

Optionally, the third RNTI is determined according to the following formula:

the third rnti=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_c_id,

Optionally, the communication unit 410 is further configured to send a system broadcast message, where the system broadcast message includes the RNTI interval.

Optionally, the peer device is in an idle state or a deactivated state.

It should be understood that the network device 400 according to the embodiment of the present application may correspond to the network device in the embodiment of the method of the present application, and the foregoing and other operations and/or functions of each unit in the network device 400 are respectively for implementing the corresponding flow of the network device in the method 200 shown in fig. 4, and are not further described herein for brevity.

Fig. 7 is a schematic structural diagram of a communication device 500 provided in an embodiment of the present application. The communication device 500 shown in fig. 7 comprises a processor 510, from which the processor 510 may call and run a computer program to implement the method in the embodiments of the present application.

Optionally, as shown in fig. 7, the communication device 500 may further comprise a memory 520. Wherein the processor 510 may call and run a computer program from the memory 520 to implement the methods in embodiments of the present application.

Wherein the memory 520 may be a separate device from the processor 510 or may be integrated into the processor 510.

Optionally, as shown in fig. 7, the communication device 500 may further include a transceiver 530, and the processor 510 may control the transceiver 530 to communicate with other devices, and in particular, may send information or data to other devices, or receive information or data sent by other devices.

Wherein the transceiver 530 may include a transmitter and a receiver. The transceiver 530 may further include antennas, the number of which may be one or more.

Optionally, the communication device 500 may be specifically a network device in the embodiment of the present application, and the communication device 500 may implement a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the communication device 500 may be specifically a mobile terminal/terminal device in the embodiment of the present application, and the communication device 500 may implement a corresponding flow implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein for brevity.

Fig. 8 is a schematic structural view of an apparatus of an embodiment of the present application. The apparatus 600 shown in fig. 8 includes a processor 610, and the processor 610 may call and run a computer program from a memory to implement the methods in the embodiments of the present application.

Optionally, as shown in fig. 8, the apparatus 600 may further comprise a memory 620. Wherein the processor 610 may call and run a computer program from the memory 620 to implement the methods in embodiments of the present application.

The memory 620 may be a separate device from the processor 610 or may be integrated into the processor 610.

Optionally, the apparatus 600 may further comprise an input interface 630. The processor 610 may control the input interface 630 to communicate with other devices or chips, and in particular, may acquire information or data sent by the other devices or chips.

Optionally, the apparatus 600 may further comprise an output interface 640. Wherein the processor 610 may control the output interface 640 to communicate with other devices or chips, and in particular, may output information or data to other devices or chips.

Optionally, the apparatus may be applied to a network device in the embodiments of the present application, and the apparatus may implement a corresponding flow implemented by the network device in each method in the embodiments of the present application, which is not described herein for brevity.

Optionally, the apparatus may be applied to a mobile terminal/terminal device in the embodiment of the present application, and the apparatus may implement a corresponding flow implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein for brevity.

Alternatively, the device mentioned in the embodiments of the present application may also be a chip. For example, a system-on-chip or a system-on-chip, etc.

Fig. 9 is a schematic block diagram of a communication system 700 provided in an embodiment of the present application. As shown in fig. 9, the communication system 700 includes a terminal device 710 and a network device 720.

The terminal device 710 may be configured to implement the corresponding functions implemented by the terminal device in the above method, and the network device 720 may be configured to implement the corresponding functions implemented by the network device in the above method, which are not described herein for brevity.

It should be appreciated that the processor of an embodiment of the present application may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be implemented by integrated logic circuits of hardware in a processor or instructions in software form. The processor may be a general purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. The disclosed methods, steps, and logic blocks in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present application may be embodied directly in hardware, in a decoded processor, or in a combination of hardware and software modules in a decoded processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.

It will be appreciated that the memory in embodiments of the present application may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM) which acts as an external cache. By way of example, and not limitation, many forms of RAM are available, such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (Double Data Rate SDRAM), enhanced SDRAM (ESDRAM), synchronous DRAM (SLDRAM), and Direct RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

It should be understood that the above memory is exemplary but not limiting, and for example, the memory in the embodiments of the present application may be Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), direct RAM (DR RAM), and the like. That is, the memory in embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.

Embodiments of the present application also provide a computer-readable storage medium for storing a computer program.

Optionally, the computer readable storage medium may be applied to a network device in the embodiments of the present application, and the computer program causes a computer to execute a corresponding flow implemented by the network device in each method in the embodiments of the present application, which is not described herein for brevity.

Optionally, the computer readable storage medium may be applied to a mobile terminal/terminal device in the embodiments of the present application, and the computer program causes a computer to execute a corresponding procedure implemented by the mobile terminal/terminal device in each method of the embodiments of the present application, which is not described herein for brevity.

Embodiments of the present application also provide a computer program product comprising computer program instructions.

Optionally, the computer program product may be applied to a network device in the embodiments of the present application, and the computer program instructions cause the computer to execute corresponding flows implemented by the network device in the methods in the embodiments of the present application, which are not described herein for brevity.

Optionally, the computer program product may be applied to a mobile terminal/terminal device in the embodiments of the present application, and the computer program instructions cause a computer to execute corresponding processes implemented by the mobile terminal/terminal device in the methods in the embodiments of the present application, which are not described herein for brevity.

The embodiment of the application also provides a computer program.

Optionally, the computer program may be applied to a network device in the embodiments of the present application, and when the computer program runs on a computer, the computer is caused to execute a corresponding flow implemented by the network device in each method in the embodiments of the present application, which is not described herein for brevity.

Optionally, the computer program may be applied to a mobile terminal/terminal device in the embodiments of the present application, where the computer program when run on a computer causes the computer to execute corresponding processes implemented by the mobile terminal/terminal device in the methods in the embodiments of the present application, and for brevity, will not be described herein.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. For such understanding, the technical solutions of the present application may be embodied in essence or in a part contributing to the prior art or in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

The foregoing is merely specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the present application, and the changes and substitutions are intended to be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A random access method, comprising:

the terminal equipment monitors a Physical Downlink Control Channel (PDCCH) scrambled by a first Radio Network Temporary Identifier (RNTI), the PDCCH is used for scheduling a Physical Downlink Shared Channel (PDSCH) carrying second information in a two-step random access process,

the first RNTI is a random access-radio network temporary identifier RA-RNTI determined at least according to resource information of a first physical uplink shared channel PUSCH, wherein the first information includes a random access preamble, and the resource information of the first PUSCH is associated with a physical random access channel PRACH resource that transmits the random access preamble.

2. The method of claim 1, wherein the first RNTI is a RA-RNTI determined from at least time domain resources of the first PUSCH.

3. The method of claim 2, wherein the first RNTI is determined according to the following equation:

wherein s_id is an index of a first Orthogonal Frequency Division Multiplexing (OFDM) symbol in the PRACH resource, and s_id is more than or equal to 0 and less than or equal to 14; t_id is the index of the first time slot in the PRACH resource on a system frame, and t_id is more than or equal to 0 and less than or equal to 80; f_id is an index of the PRACH resource in a frequency domain, and f_id is more than or equal to 0 and less than or equal to 8; ul_c_id is an uplink UL carrier for the random access preamble transmission; pusch_s_id is the index of the first OFDM symbol in the time domain resource of the first PUSCH; pusch_t_id is the index of the first slot in the time domain resource of the first PUSCH in a system frame; n1 and N2 are one value that is preconfigured.

4. The method of claim 1, wherein the first RNTI is a RA-RNTI determined from at least frequency domain resources of the first PUSCH.

5. The method of claim 4, wherein the first RNTI is determined according to the following equation:

the first rnti=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_c_id+n3×pusch_f_id,

Wherein s_id is an index of a first OFDM symbol in the PRACH resource, and s_id is more than or equal to 0 and less than or equal to 14; t_id is the index of the first time slot in the PRACH resource on a system frame, and t_id is more than or equal to 0 and less than or equal to 80; f_id is an index of the PRACH resource in a frequency domain, and f_id is more than or equal to 0 and less than or equal to 8; ul_c_id is an uplink UL carrier for the random access preamble transmission; pusch_f_id is an index of the frequency domain resource of the first PUSCH in the frequency domain; pusch_t_id is the index of the first slot in the time domain resource of the first PUSCH in a system frame; n3 is a pre-configured value.

6. The method of claim 1, wherein the first RNTI is a RA-RNTI determined based at least on a resource location of the first PUSCH.

7. The method of claim 6, wherein the first RNTI is determined according to the following equation:

the first rnti=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_c_id+n4×pusch_p_id,

wherein s_id is an index of a first OFDM symbol in the PRACH resource, and s_id is more than or equal to 0 and less than or equal to 14; t_id is the index of the first time slot in the PRACH resource on a system frame, and t_id is more than or equal to 0 and less than or equal to 80; f_id is an index of the PRACH resource in a frequency domain, and f_id is more than or equal to 0 and less than or equal to 8; ul_c_id is an uplink UL carrier for the random access preamble transmission; pusch_f_id is an index of the frequency domain resource of the first PUSCH in the frequency domain; pusch_p_id is an index of the resource location of the first PUSCH relative to the resource location of the PRACH resource; n4 is a pre-configured value.

8. The method of claim 1, wherein the first RNTI is further determined based on a second RNTI and an RNTI interval, the second RNTI being an RA-RNTI determined based at least on resource information of a first PUSCH including a random access preamble, the resource information of the first PUSCH being associated with PRACH resources from which the random access preamble was transmitted.

9. The method of claim 8, wherein the first RNTI is determined according to the following equation:

first rnti=rnti_l+second RNTI mod (rnti_h-rnti_l),

10. The method according to claim 8 or 9, wherein the second RNTI is a RA-RNTI determined at least from time domain resources of the first PUSCH.

11. The method of claim 10, wherein the second RNTI is determined according to the following equation:

wherein s_id is an index of a first OFDM symbol in the PRACH resource, and s_id is more than or equal to 0 and less than or equal to 14; t_id is the index of the first time slot in the PRACH resource on a system frame, and t_id is more than or equal to 0 and less than or equal to 80; f_id is an index of the PRACH resource in a frequency domain, and f_id is more than or equal to 0 and less than or equal to 8; ul_c_id is an uplink UL carrier for the random access preamble transmission; pusch_s_id is the index of the first OFDM symbol in the time domain resource of the first PUSCH; pusch_t_id is the index of the first slot in the time domain resource of the first PUSCH in a system frame; n1 and N2 are one value that is preconfigured.

12. The method according to claim 8 or 9, wherein the second RNTI is a RA-RNTI determined at least from frequency domain resources of the first PUSCH.

13. The method of claim 12, wherein the second RNTI is determined according to the following equation:

the second rnti=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_c_id+n3×pusch_f_id,

14. The method according to claim 8 or 9, wherein the second RNTI is a RA-RNTI determined at least from a resource location of the first PUSCH.

15. The method of claim 14, wherein the second RNTI is determined according to the following equation:

The second rnti=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_c_id+n4×pusch_p_id,

16. A random access method, comprising:

the network device sends a Physical Downlink Control Channel (PDCCH) scrambled by a first Radio Network Temporary Identity (RNTI), the PDCCH is used for scheduling a Physical Downlink Shared Channel (PDSCH) carrying second information in a two-step random access process,

17. The method of claim 16, wherein the first RNTI is a RA-RNTI determined from at least time domain resources of the first PUSCH.

18. The method of claim 17, wherein the first RNTI is determined according to the following equation:

19. The method of claim 16, wherein the first RNTI is a RA-RNTI determined from at least frequency domain resources of the first PUSCH.

20. The method of claim 19, wherein the first RNTI is determined according to the following equation:

The first rnti=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_c_id+n3×pusch_f_id,

21. The method of claim 16, wherein the first RNTI is a RA-RNTI determined based at least on a resource location of the first PUSCH.

22. The method of claim 21, wherein the first RNTI is determined according to the following equation:

the first rnti=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_c_id+n4×pusch_p_id,

23. The method of claim 16, wherein the first RNTI is further determined based on a second RNTI and an RNTI interval, the second RNTI being an RA-RNTI determined based at least on resource information of a first PUSCH including a random access preamble, the resource information of the first PUSCH being associated with PRACH resources from which the random access preamble was transmitted.

24. The method of claim 23, wherein the first RNTI is determined according to the following equation:

first rnti=rnti_l+second RNTI mod (rnti_h-rnti_l),

25. The method according to claim 23 or 24, wherein the second RNTI is a RA-RNTI determined at least from time domain resources of the first PUSCH.

26. The method of claim 25, wherein the second RNTI is determined according to the following equation:

27. The method according to claim 23 or 24, wherein the second RNTI is a RA-RNTI determined at least from frequency domain resources of the first PUSCH.

28. The method of claim 27, wherein the second RNTI is determined according to the following equation:

the second rnti=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_c_id+n3×pusch_f_id,

29. The method according to claim 23 or 24, wherein the second RNTI is a RA-RNTI determined at least from a resource location of the first PUSCH.

30. The method of claim 29, wherein the second RNTI is determined according to the following equation:

The second rnti=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_c_id+n4×pusch_p_id,

31. A terminal device, comprising:

the communication unit is used for sending first information in the two-step random access process;

the communication unit is further configured to monitor a physical downlink control channel PDCCH scrambled by a first radio network temporary identity RNTI, the PDCCH being used for scheduling a physical downlink shared channel PDSCH carrying second information in a two-step random access procedure,

32. The terminal device of claim 31, wherein the first RNTI is a RA-RNTI determined from at least time domain resources of the first PUSCH.

33. The terminal device of claim 32, wherein the first RNTI is determined according to the following formula:

34. The terminal device of claim 31, wherein the first RNTI is a RA-RNTI determined from at least frequency domain resources of the first PUSCH.

35. The terminal device of claim 34, wherein the first RNTI is determined according to the following formula:

the first rnti=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_c_id+n3×pusch_f_id,

36. The terminal device of claim 31, wherein the first RNTI is a RA-RNTI determined based at least on a resource location of the first PUSCH.

37. The terminal device of claim 36, wherein the first RNTI is determined according to the following formula:

the first rnti=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_c_id+n4×pusch_p_id,

38. The terminal device of claim 31, wherein the first RNTI is further determined based on a second RNTI and an RNTI interval, the second RNTI being an RA-RNTI determined based at least on resource information of a first PUSCH including a random access preamble, the resource information of the first PUSCH being associated with PRACH resources from which the random access preamble was transmitted.

39. The terminal device of claim 38, wherein the first RNTI is determined according to the following formula:

first rnti=rnti_l+second RNTI mod (rnti_h-rnti_l),

40. The terminal device of claim 38 or 39, wherein the second RNTI is a RA-RNTI determined at least from time domain resources of the first PUSCH.

41. The terminal device of claim 40, wherein the second RNTI is determined according to the following formula:

42. The terminal device of claim 38 or 39, wherein the second RNTI is a RA-RNTI determined at least from frequency domain resources of the first PUSCH.

43. The terminal device of claim 42, wherein the second RNTI is determined according to the following equation:

the second rnti=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_c_id+n3×pusch_f_id,

44. The terminal device of claim 38 or 39, wherein the second RNTI is a RA-RNTI determined at least from a resource location of the first PUSCH.

45. The terminal device of claim 44, wherein the second RNTI is determined according to the following equation:

the second rnti=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_c_id+n4×pusch_p_id,

46. A network device, comprising:

the communication unit is used for receiving the first information in the two-step random access process;

the communication unit is further configured to send a physical downlink control channel, PDCCH, scrambled by a first radio network temporary identity, RNTI, the PDCCH being used for scheduling a physical downlink shared channel, PDSCH, carrying second information in a two-step random access procedure,

47. The network device of claim 46, wherein the first RNTI is a RA-RNTI determined based at least on time domain resources of the first PUSCH.

48. The network device of claim 47, wherein the first RNTI is determined according to the following equation:

49. The network device of claim 46, wherein the first RNTI is a RA-RNTI determined based at least on frequency domain resources of the first PUSCH.

50. The network device of claim 49, wherein the first RNTI is determined according to the following equation:

the first rnti=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_c_id+n3×pusch_f_id,

51. The network device of claim 46, wherein the first RNTI is a RA-RNTI determined based at least on a resource location of the first PUSCH.

52. The network device of claim 51, wherein the first RNTI is determined according to the following equation:

the first rnti=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_c_id+n4×pusch_p_id,

Wherein s_id is an index of a first Orthogonal Frequency Division Multiplexing (OFDM) symbol in the PRACH resource, and s_id is more than or equal to 0 and less than or equal to 14; t_id is the index of the first time slot in the PRACH resource on a system frame, and t_id is more than or equal to 0 and less than or equal to 80; f_id is an index of the PRACH resource in a frequency domain, and f_id is more than or equal to 0 and less than or equal to 8; ul_c_id is an uplink UL carrier for the random access preamble transmission; pusch_f_id is an index of the frequency domain resource of the first PUSCH in the frequency domain; pusch_p_id is an index of the resource location of the first PUSCH relative to the resource location of the PRACH resource; n4 is a pre-configured value.

53. The network device of claim 46, wherein the first RNTI is further determined based on a second RNTI and an RNTI interval, the second RNTI being an RA-RNTI determined based at least on resource information of a first PUSCH including a random access preamble, the resource information of the first PUSCH being associated with PRACH resources from which the random access preamble was transmitted.

54. The network device of claim 53, wherein the first RNTI is determined according to the following equation:

first rnti=rnti_l+second RNTI mod (rnti_h-rnti_l),

55. The network device of claim 53 or 54, wherein the second RNTI is a RA-RNTI determined from at least time domain resources of the first PUSCH.

56. The network device of claim 55, wherein the second RNTI is determined according to the following equation:

57. The network device of claim 53 or 54, wherein the second RNTI is a RA-RNTI determined from at least frequency domain resources of the first PUSCH.

58. The network device of claim 57, wherein the second RNTI is determined according to the following equation:

the second rnti=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_c_id+n3×pusch_f_id,

59. The network device of claim 53 or 54, wherein the second RNTI is a RA-RNTI determined based at least on a resource location of the first PUSCH.

60. The network device of claim 59, wherein the second RNTI is determined according to the following equation:

the second rnti=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_c_id+n4×pusch_p_id,

61. A terminal device, comprising: a processor and a memory for storing a computer program, the processor being adapted to invoke and run the computer program stored in the memory, to perform the method of any of claims 1 to 15.

62. A network device, comprising: a processor and a memory for storing a computer program, the processor being for invoking and running the computer program stored in the memory, performing the method of any of claims 16 to 30.

63. An apparatus, comprising: a processor for calling and running a computer program from a memory, causing a device in which the apparatus is installed to perform the method of any one of claims 1 to 15.

64. An apparatus, comprising: a processor for calling and running a computer program from a memory, causing a device in which the apparatus is installed to perform the method of any of claims 16 to 30.

65. A computer readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 1 to 15.

66. A computer readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 16 to 30.