WO2020186468A1

WO2020186468A1 - Random access method and device

Info

Publication number: WO2020186468A1
Application number: PCT/CN2019/078788
Authority: WO
Inventors: 石聪
Original assignee: Oppo广东移动通信有限公司
Priority date: 2019-03-19
Filing date: 2019-03-19
Publication date: 2020-09-24

Abstract

The embodiments of the present application relate to a random access method and device, the method comprising: a terminal device sends a first message to a network device, the first message comprising a random access preamble and an uplink message, and the uplink message comprising a first identifier; on the basis of the first identifier, the terminal device determines a first target radio network temporary identifier RNTI used for blind detection of a first physical downlink control channel PDCCH; on the basis of the first target RNTI, the terminal device blind detects the first PDCCH; on the basis of the result of the blind detection of the first PDCCH, the terminal device determines whether to blind detect a second PDCCH; if the terminal device determines to blind detect the second PDCCH, the terminal device blind detects the second PDCCH; and, on the basis of the result of the blind detection of the second PDCCH, the terminal device determines whether contention conflict in the random access procedure has already been resolved. The random access method and device in the embodiments of the present application can resolve contention conflict in a two-step random access procedure.

Description

Random access method and equipment

Technical field

This application relates to the field of communications, in particular to a method and equipment for random access.

Background technique

In the New Radio (NR) system (or 5G system, 5G network), a two-step random access process can be used. In the two-step random access process, message 1 (Msg 1) and message 3 (Msg 3) in the four-step random access process can be sent as the first message (Msg A) in the two-step random access process , And send message 2 (Msg 2) and message 2 (Msg 4) in the four-step random access process as the second message (Msg B) in the two-step random access process.

Since the first message can be shared by multiple terminal devices, conflicts may arise. Therefore, how to solve the contention conflict in the two-step random access process is an urgent problem to be solved.

Summary of the invention

The embodiments of the present application provide a random access method and device, which can resolve contention conflicts in a two-step random access process.

In a first aspect, a random access method is provided. The method includes: a terminal device sends a first message to a network device, the first message includes a random access preamble and an uplink message, and the uplink message includes a first message. An identifier; the terminal device determines the first target radio network temporary identifier RNTI for blind detection of the first physical downlink control channel PDCCH according to the first identifier; the terminal device blindly detects the first target RNTI according to the first target RNTI Detecting the first PDCCH; the terminal device determines whether to blindly detect the second PDCCH according to the result of blindly detecting the first PDCCH; if the terminal device determines to blindly detect the second PDCCH, the terminal device blindly detects The second PDCCH; the terminal device determines whether the contention conflict in the random access process has been resolved according to the result of the blind detection of the second PDCCH.

In a second aspect, a random access method is provided. The method includes: a network device receives a first message sent by a terminal device, where the first message includes a preamble identifier ID for random access and an uplink message, and The uplink message includes a first identifier; the network device decodes the first message; the network device determines a response message to be sent to the terminal device according to the decoding situation of the first message.

In a third aspect, a terminal device is provided, which is used to execute the method in the foregoing first aspect or each of its implementation manners.

Specifically, the terminal device includes a functional module for executing the method in the foregoing first aspect or each implementation manner thereof.

In a fourth aspect, a network device is provided, which is configured to execute the method in the second aspect or its implementation manners.

Specifically, the network device includes a functional module for executing the method in the foregoing second aspect or each implementation manner thereof.

In a fifth aspect, a terminal device is provided, including a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method in the above-mentioned first aspect or each of its implementation modes.

In a sixth aspect, a network device is provided, including a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method in the above-mentioned second aspect or each of its implementation modes.

In a seventh aspect, a chip is provided for implementing any one of the above-mentioned first aspect to the second aspect or the method in each implementation manner thereof.

Specifically, the chip includes: a processor, configured to call and run a computer program from the memory, so that the device installed with the chip executes any one of the above-mentioned first aspect to the second aspect or any of the implementations thereof method.

In an eighth aspect, a computer-readable storage medium is provided for storing a computer program that enables a computer to execute any one of the first aspect to the second aspect or the method in each implementation manner thereof.

In a ninth aspect, a computer program product is provided, including computer program instructions, which cause a computer to execute any one of the above-mentioned first aspect to the second aspect or the method in each implementation manner thereof.

In a tenth aspect, a computer program is provided, which when running on a computer, causes the computer to execute any one of the above-mentioned first aspect to the second aspect or the method in each implementation manner thereof.

In the above technical solution, in the two-step random access process, the network device can send the first PDCCH and the second PDCCH to the terminal device, and the terminal device can determine whether to blindly detect the second PDCCH according to the result of the blind detection of the first PDCCH. If the device determines to blindly detect the second PDCCH, it can determine whether the contention conflict in the random access process has been resolved according to the result of the blind detection of the second PDCCH, so that the contention conflict in the two-step random access process can be resolved.

Description of the drawings

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

Fig. 2 is a schematic flowchart of a four-step random access method according to an embodiment of the present application.

Fig. 3 is a schematic flowchart of another two-step random access method according to an embodiment of the present application.

Fig. 4 is a schematic diagram of a MAC PDU including RAR according to an embodiment of the present application.

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

Fig. 6 is a schematic block diagram of a RAPID prefix according to an embodiment of the present application.

Fig. 7 is a schematic block diagram of a MAC RAR according to an embodiment of the present application.

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

Fig. 9 is a schematic flowchart of a random access method according to an embodiment of the present application.

Fig. 10 is a schematic diagram of a random access method according to an embodiment of the present application.

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

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

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

Fig. 14 is a schematic block diagram of a chip according to an embodiment of the present application.

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

detailed description

The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are a part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative work shall fall within the protection scope of this application.

The embodiments of this application can be applied to various communication systems, such as: Global System of Mobile Communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (Wideband Code) Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, New Wireless (New Radio, NR) system, evolution system of NR system, LTE (LTE-based access to unlicensed spectrum, LTE-U) system on unlicensed spectrum, NR (NR-based access to unlicensed spectrum, on unlicensed spectrum, NR-U) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (WiFi), next-generation communication systems or other communication systems, etc.

Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communication, but also support, for example, Device to Device (Device to Device, D2D) communication, machine to machine (Machine to Machine, M2M) communication, machine type communication (MTC), and vehicle to vehicle (V2V) communication, etc. The embodiments of this application can also be applied to these communications system.

Optionally, the communication system in the embodiments of the present application can be applied to a carrier aggregation (Carrier Aggregation, CA) scenario, can also be applied to a dual connectivity (DC) scenario, and can also be applied to a standalone (SA) deployment. Network scene.

Exemplarily, the communication system 100 applied in the embodiment of the present application 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 called a communication terminal or terminal). The network device 110 may provide communication coverage for a specific geographic area, and may communicate with terminal devices located in the coverage area. Optionally, the network device 110 may be a base station (Base Transceiver Station, BTS) in a GSM system or a CDMA system, a base station (NodeB, NB) in a WCDMA system, or an evolved base station in an LTE system (Evolutional Node B, eNB or eNodeB), or the wireless controller in the Cloud Radio Access Network (CRAN), or the network equipment can be a mobile switching center, a relay station, an access point, a vehicle-mounted device, Wearable devices, hubs, switches, bridges, routers, network-side devices in 5G networks, or network devices in the future evolution of the Public Land Mobile Network (PLMN), etc.

The communication system 100 also includes at least one terminal device 120 located within the coverage area of the network device 110. The "terminal equipment" used here includes but is not limited to connection via wired lines, such as via public switched telephone networks (PSTN), digital subscriber lines (Digital Subscriber Line, DSL), digital cables, and direct cable connections ; And/or another data connection/network; and/or via a wireless interface, such as for cellular networks, wireless local area networks (WLAN), digital TV networks such as DVB-H networks, satellite networks, AM- FM broadcast transmitter; and/or another terminal device that is set to receive/send communication signals; and/or Internet of Things (IoT) equipment. A terminal device set to communicate through a wireless interface may be referred to as a "wireless communication terminal", a "wireless terminal" or a "mobile terminal". Examples of mobile terminals include, but are not limited to, satellites or cellular phones; Personal Communications System (PCS) terminals that can combine cellular radio phones with data processing, fax, and data communication capabilities; can include radio phones, pagers, Internet/intranet PDA with internet access, web browser, memo pad, calendar, and/or Global Positioning System (GPS) receiver; and conventional laptop and/or palmtop receivers or others including radio phone transceivers Electronic device. Terminal equipment can refer to access terminals, user equipment (UE), user units, user stations, mobile stations, mobile stations, remote stations, remote terminals, mobile equipment, user terminals, terminals, wireless communication equipment, user agents, or User device. The access terminal can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital processing (Personal Digital Assistant, PDA), with wireless communication Functional handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in 5G networks, or terminal devices in the future evolution of PLMN, etc.

The network device 110 may provide services for a cell, and the terminal device 120 communicates with the network device 110 through transmission resources (for example, frequency domain resources, or spectrum resources) used by the cell. The cell may be the network device 110 (for example, a base station) The corresponding cell, the cell can belong to a macro base station or a base station corresponding to a small cell (Small cell). The small cell here can include, for example, a metro cell, a micro cell, and a pico cell. Femto cells, etc. These small cells have the characteristics of small coverage and low transmit power, and are suitable for providing high-rate data transmission services.

Figure 1 exemplarily shows one network device and two terminal devices. Optionally, the communication system 100 may include multiple network devices and the coverage of each network device may include other numbers of terminal devices. The embodiment does not limit this.

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

It should be understood that the devices with communication functions in the network/system in the embodiments of the present application may be referred to as communication devices. 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, and the network device 110 and the terminal device 120 may be the specific devices described above, which will not be repeated here. The communication device may also include other devices in the communication system 100, such as other network entities such as a network controller and a mobility management entity, which are not limited in this embodiment of the application.

It should be understood that the terms "system" and "network" in this article are often used interchangeably in this article. The term "and/or" in this article is only an association relationship describing associated objects, which means that there can be three relationships, for example, A and/or B, which can mean: A alone exists, A and B exist at the same time, exist alone B these three situations. In addition, the character "/" in this text generally indicates that the associated objects before and after are in an "or" relationship.

After the cell search process, the terminal device has achieved downlink synchronization with the cell, so the terminal device can receive downlink data. However, the terminal equipment can only perform uplink transmission if it has achieved uplink synchronization with the cell. The terminal equipment can establish a connection with the cell and obtain uplink synchronization through a random access procedure (Random Access Procedure). In order to facilitate the understanding of the solution of the embodiment of the present application, the random access process will be briefly introduced below in conjunction with FIG. 2 and FIG. 3.

The random access process can usually be triggered by the following events:

(1) Initial Access (Initial Access).

The terminal device can enter the RRC connected state (RRC_CONNECTED) from the radio resource control (Radio Resource Control, RRC) idle state (RRC_IDLE state).

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

(3) Handover.

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

(4) In the RRC connection state, when downlink data or uplink data arrives, the uplink is in a "non-synchronised" state (DL or UL data arrival during RRC_CONNECTED when UL synchronisation status is "non-synchronised").

(5) In the RRC connected state, when uplink data arrives, there is no available physical uplink control channel (PUCCH) resource 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) RRC request during synchronous configuration (Request by RRC upon synchronous reconfiguration).

(8) The terminal device transitions from the RRC inactive state (Transition from RRC_INACTIVE).

(9) Establish time alignment (To establish time alignment at SCell addition) when SCell is added.

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

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

In the NR system, two random access methods can be supported: a contention-based random access method as shown in FIG. 2 and a non-contention-based random access method as shown in FIG. The following briefly describes the four-step random access process based on contention:

Step 1. The terminal device sends a random access preamble (Preamble, that is, message1, Msg1) to the network device.

Among them, the random access preamble may also be referred to as a preamble, a random access preamble sequence, a preamble sequence, and so on.

Specifically, the terminal device may select physical random access channel (Physical Random Access Channel, PRACH) resources, and the PRACH resources may include time domain resources, frequency domain resources, and code domain resources. Next, the terminal device can send the selected Preamble on the selected PRACH resource. The network device can estimate the transmission delay between it and the terminal device based on the Preamble and use this to calibrate the uplink timing, and can roughly determine the size of the resource required for the terminal device to transmit message 3 (Msg3).

Step 2: The network device sends a random access response (Random Access Response, RAR, that is, message2, Msg2) to the terminal device

After the terminal device sends the Preamble to the network device, it can open a RAR window, in which RAR window detects the corresponding physical downlink control channel (Physical Downlink) according to the Random Access Radio Network Temporary Identifier (RA-RNTI) Control Channel, PDCCH). 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 the RAR corresponding to the Preamble.

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

Optionally, in this embodiment of the present application, the RA-RNTI may calculate the value of the RA-RNTI by using the time-frequency position of the Preamble that is clear to both the transmitting and receiving parties. For example, RA-RNTI associated with Preamble can be calculated by formula (1):

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

Among them, s_id is the index of the first Orthogonal Frequency Division Multiplexing (OFDM) symbol of the PRACH resource (0≤s_id<14), and t_id is the index of the first time slot of the PRACH resource in a system frame. Index (0≤t_id<80), f_id is the index of the PRACH resource in the frequency domain (0≤f_id<8), and ul_carrier_id is the uplink carrier used to transmit the Preamble (0 represents the NUL carrier, 1 represents the SUL carrier). For FDD, there is only one PRACH resource per subframe, so f_id is fixed to 0.

In other words, since the time-frequency position of the Preamble sent by the terminal device is determined, the network device also obtains the time-frequency position of the Preamble when decoding the Preamble, and can then know the RA-RNTI that needs to be used in the RAR. When the terminal device successfully receives a RAR (using a certain RA-RNTI to decode), and the random access sequence identifier (Random Access Preamble Identifier, RAPID) in the RAR is the same as the preamble index sent by the terminal device, it can It is considered that the RAR is successfully received, and the terminal device can stop detecting the PDCCH scrambled by the RA-RNTI at this time.

The RAR can be carried in the Media Access Control (MAC) protocol data unit (Protocol Data Unit, PDU). The information carried by the RAR will be introduced from the perspective of the configuration of the MAC PDU including the RAR with reference to FIG. 4.

It can be seen from Figure 4 that a MAC PDU may include one or more MAC subPDUs (subPDU) and possibly padding bits, and a MAC subPDU may only have a Backoff Indicator (BI), or There are only random access sequence identifiers (Random Access Preamble Identifier, RAPID), or RAPID and MAC RAR.

It can be seen from the structure of MAC PDU that if a network device detects random access requests from multiple terminal devices on the same PRACH resource, it can use one MAC PDU to respond to these access requests. Each random access The response to the request (corresponding to a preamble index) corresponds to a RAR. In other words, if multiple terminal devices send Preamble on the same PRACH resource (the same time and frequency position, using the same RA-RNTI), the corresponding RARs are multiplexed in the same MAC PDU.

That is, all terminal devices that use the same PRACH resource to send the Preamble (the Preamble is not necessarily the same) detect the same RA-RNTI scrambled PDCCH and receive the same MAC PDU, but different RAPIDs correspond to different RARs.

Since the MAC PDU can only be scrambled with one RA-RNTI, this also means that the RAR corresponding to the Preamble sent using different PRACH resources (different time and frequency positions) cannot be multiplexed into the same MAC PDU.

FIG. 5 is a schematic block diagram of a BI subheader in an embodiment of the present application. As shown in FIG. 5, the BI sub-header may include an extension field (E), a type field (T), two reserved fields (R), and a BI value.

Regarding the BI sub-header, the BI sub-header appears only once and is located at the first head of the MAC header (header). If the terminal device receives a BI subheader, it will save a backoff value, which is equal to the value corresponding to the BI in the header; otherwise, the terminal device can set the Backoff value to 0. The value corresponding to BI specifies the time range that the terminal device needs to wait before resending the Preamble. If the terminal device does not receive the RAR within the RAR window, or if none of the received RARs matches the preamble index selected by the terminal device, it can be considered that the RAR reception fails. At this time, the terminal device needs to wait for a period of time before initiating random access. The waiting time can be any random value within the waiting time interval specified by the value corresponding to 0 to BI.

Fig. 6 is a schematic block diagram of a RAPID subheader in an embodiment of the present application.

As shown in Figure 6, the RAPID subheader can include an E, a T, and RAPID values. Among them, RAPID is the Preamble index received by the network device in response. If the terminal device finds that the value is the same as the index used when it sends the Preamble, it can be considered that the corresponding RAR has been successfully received.

FIG. 7 is a schematic block diagram of a MAC RAR according to an embodiment of the present application. As shown in Figure 7, MAC RAR may include: reserved bit R (for example, 1 bit), time alignment command (Timing Advance Command, TAC), uplink grant (UL grant), and temporary cell radio network temporary identification ( Temporary Cell Radio Network Temporary Identifier, TC-RNTI).

Among them, TAC can be used to specify the amount of time adjustment required for the uplink synchronization of the terminal equipment, and can occupy 12 bits. UL grant can be used to schedule Msg3 uplink resource indication. TC-RNTI can be used to scramble the Msg4 PDCCH (initial access).

Step 3. The terminal device sends Msg3.

After receiving the RAR message, the terminal device determines whether the RAR is its own RAR message. For example, the terminal device can use the preamble index to check. After determining that it is its own RAR message, it can generate Msg3 in the RRC layer and send it to The network device sends Msg3, which needs to carry the identification information of the terminal device, etc.

Among them, Msg3 is mainly used to notify the network equipment of the random access trigger event. For different random access trigger events, the Msg3 sent by the terminal device in step 3 may include different content.

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

For another example, for an RRC connection re-establishment scenario, Msg3 may include an RRC connection re-establishment request message (RRC Reestabilshment Request) generated by the RRC layer. In addition, Msg3 may also carry, for example, a Cell Radio Network Temporary Identifier (C-RNTI).

For another example, for a handover scenario, Msg3 may include an RRC handover confirmation message (RRC Handover Confirm) generated by the RRC layer, which carries the C-RNTI of the terminal device. In addition, Msg3 may also carry information such as Buffer Status Report (BSR). For other trigger events such as uplink/downlink data arrival scenarios, Msg3 may at least include the C-RNTI of the terminal device.

Step 4. The network device sends a contention resolution message (Msg4) to the terminal device.

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

Since the terminal device in step 3 can carry its own unique identifier in Msg3, the network device will carry the unique identifier of the terminal device in Msg4 in the contention resolution mechanism to specify the terminal device that wins the competition. Other terminal devices that did not win in the contention resolution will re-initiate random access.

It should be understood that, in the embodiment of the present application, there are two ways to resolve the contention conflict:

Manner 1: If the terminal equipment carries the C-RNTI in Msg3, Msg4 can be scheduled with the PDCCH scrambled by the C-RNTI.

Manner 2: If the terminal device does not carry the C-RNTI in the Msg3, such as initial access, the Msg4 can be scheduled with the PDCCH scrambled by the TC-RNTI. At this time, the resolution of the contention conflict can be through the terminal device receiving the PDSCH of Msg4 to obtain the conflict resolution ID, and by matching the conflict resolution ID with the common control channel (CCCH) service data unit in msg3 , SDU) to determine whether to resolve the conflict.

The delay of four-step random access is relatively large, which is not suitable for the low-latency and high-reliability scenarios in 5G. Considering the characteristics of low-latency and high-reliability related services, a two-step random access process scheme is proposed. As shown in Figure 8, in the two-step random access process, in simple terms, it is equivalent to combining the first and third steps of the four-step random access process into the first step in the two-step random access process. The second and fourth steps of the four-step random access process are combined into the second step of the two-step random access process.

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

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

The first message may be composed of a preamble and a payload (payload). The Preamble is a four-step random access Preamble. The preamble is transmitted on the PRACH resource. The payload mainly carries information in Msg3 in the four-step random access. For example, it may include CCCH SDU, such as corresponding to random access in RRC idle state, and may also include C-RNTI MAC control element (CE), such as mainly corresponding to random access in RRC connected state. The payload may be carried on an uplink channel, and the channel may be, for example, a 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 Msg3 in the four-step random access process.

Step 2: 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, it can send the second message to the terminal device. The second message may include part or all of the information carried in Msg2 and Msg4 in the four-step random access process. The names of the first message and the second message are not limited, that is, they can also be expressed as other names. For example, the first message may also be called Msg A, random access request message or new Msg1, and the second message may also be called Msg B or new Msg2.

It should also be understood that FIG. 8 is only a specific implementation of the two-step random access process, and should not limit the protection scope of this application.

However, in the two-step random access process, since the first message can be shared by multiple terminal devices, it is necessary to consider the issue of contention conflict and how to resolve the contention conflict. In order to solve the above problem, the embodiment of the present application proposes a random access method, which can enable the terminal device to effectively resolve the contention conflict in the two-step random access process.

FIG. 9 is a schematic flowchart of a random access method 300 according to an embodiment of the present application. The method described in FIG. 9 may be executed by a terminal device and a network device. The terminal device may be, for example, the terminal device 120 shown in FIG. 1, and the network device may be, for example, the network device 110 shown in FIG. As shown in FIG. 9, the method 300 may include at least part of the following content.

In 310, the terminal device sends a first message to the network device. The first message includes a random access preamble (ie, Preamble) and an uplink message, and the uplink message includes a first identifier.

In 320, after receiving the first message, the network device decodes the first message, and determines the response message to be sent to the terminal device according to the decoding situation of the first message.

In 330, the network device sends a response message to the terminal device.

In 340, if the response message sent by the network device includes the first PDCCH, the terminal device determines the first target RNTI used for blind detection of the first PDCCH according to the first identifier.

In 350, the terminal device blindly detects the first PDCCH according to the first target RNTI, and determines whether to blindly detect the second PDCCH according to the result of blindly detecting the first PDCCH.

In 360, if the terminal device determines to blindly detect the second PDCCH, the terminal device blindly detects the second PDCCH, and determines whether the contention conflict in the random access process has been resolved according to the result of the blind detection of the second PDCCH.

It should be understood that the first message in the method 300 may correspond to the first message in FIG. 8.

In the embodiment of the present application, the first message including the Preamble and the uplink message can be understood as: between the terminal device sending the Preamble and the uplink message to the network device, there is no other message between the network device and the terminal device, and/or the network device The second message may be sent to the terminal device simultaneously for the Preamble and the uplink message.

Specifically, the terminal device may first select the resource of the first message, including the PRACH resource and the corresponding PUSCH resource, and then use the selected resource to transmit the first message. Among them, the terminal device can use the PRACH resource to transmit the Preamble and the PUSCH resource to transmit the payload.

The terminal device can be in a connected state, an inactive state or an idle state. When the terminal device is in a different RRC state, the first identifier included in the first message may be different. The first identifier can basically be expressed as two types, one is that the payload contains C-RNTI MAC CE, and the other is that the payload does not contain C-RNTI MAC CE, that is, it contains CCCH SDU.

The terminal device can determine the first identifier carried in the payload according to its current RRC state. When the terminal device is in the connected state, the first identifier may be but is not limited to the C-RNTI, and the C-RNTI may be included in the C-RNTI MAC CE. Alternatively, when the terminal device is in an idle state or in an inactive state, the first identifier may include, but is not limited to, a random number, 5G-S-TMSI (or a part of 5G-S-TMSI), and identifying RNTI (Identify-RNTI, I- RNTI), Short I-RNTI (Short I-RNTI). Among them, the number of bits of the random number is fixed, and the I-RNTI can be used to identify the content of the terminal equipment in the RRC inactive state. At this time, the CCCH SDU may include the identification of the terminal device.

The SDU may include the RRC message transmitted in the Signaling Radio Bearer (Signaling Radio Bearer, SRB) 0, such as:

The message in the above content may generally include the first identifier. For example, if the terminal device transmits an RRCSetupRequest to the network device, the first identifier may be a random number or a part of 5G-S-TMSI.

The terminal device sends the first message to the network device, and correspondingly, the network device can receive the first message sent by the terminal device and decode the first message. When the network device decodes the first message, there can be multiple situations:

Case 1: The network device successfully decodes one or more Preambles, but fails to decode the Payload in the PUSCH.

Case 2: The network device successfully decodes one or more Preambles and one or more Payloads.

Case 3: The network device successfully decoded the payload but failed to decode the preamble. It should be noted that, since the network device needs the Preamble as the uplink timing estimation, the possibility of case 3 is small, and case 3 is not considered in this embodiment of the application.

Case 1 and Case 2 are described in detail below.

Because multiple terminal devices can use the same PRACH resource to transmit the Preamble. Therefore, in case 1, if the network device only decodes the preamble, the network device may not be able to distinguish the terminal device at this time. In this case, the network device can respond to the Preamble, that is, send the RAR in the four-step random access to the terminal device to respond to the Preamble. In this way, for a terminal device with two-step random access, it can fall back to a four-step random access; for a terminal device with four-step random access, it is a normal process. Or it does not respond to the Preamble, that is, the network device may send the second indication information to the terminal device, and the second indication information may be used to instruct the terminal device to retransmit the first message.

It should be understood that the first message retransmitted by the terminal device may be the same as or different from the first message previously transmitted, and the resource for retransmitting the first message may be the same as or different from the resource previously transmitted for the first message.

Further, if the network device can distinguish between a terminal device that performs four-step random access and a terminal device that performs two-step random access, the network device may send third instruction information to the terminal device, and the third instruction information may be used to indicate The terminal device stops blindly checking the first PDCCH, so that the terminal device can retransmit the first message as soon as possible. Among them, the first PDCCH is used for scheduling RAR.

Optionally, the PRACH resources of the terminal device performing the two-step random access and the terminal device performing the four-step random access may be different. In this case, the network device can distinguish the terminal performing the four-step random access according to the PRACH resource that receives the Preamble Equipment and terminal equipment for two-step random access.

Wherein, the PRACH resource may be configured by the network device, or may be preset on the terminal device.

In case 2, the network device can distinguish the terminal device corresponding to the identifier in the payload. At this time, the network device may have different response modes according to the first identifier.

Optionally, there is a certain association relationship between the PRACH resource carrying the Preamble and the PUSCH carrying the payload. If the network device responds to the payload, it can respond to the payload based on the above association relationship. For example, if the Preamble is successfully decoded but the Payload corresponding to the Preamble is not successfully decoded, the network device may respond to the Preamble or not. If the Preamble is successfully decoded and the Payload corresponding to the Preamble is also successfully decoded, the network device can respond to the Payload. Further, since multiple terminal devices may use the successfully decoded Preamble at the same time, the network device may further respond to the successfully decoded Preamble.

In the embodiment of the present application, if the network device responds to the RAR, the network device may send the first PDCCH to the terminal device.

In a possible embodiment, the terminal device may determine the first target RNTI according to the first identifier, and then blindly detect the first PDCCH according to the first target RNTI.

If the first identifier is C-RNTI, the terminal device determines that the first target RNTI may be C-RNTI; if the first identifier is an identifier other than C-RNTI, the terminal device may determine that the first target RNTI may be RA- RNTI. Exemplarily, the identifiers other than C-RNTI may be random numbers, 5G-S-TMSI, I-RNTI, Short I-RNTI, and so on.

Optionally, the RA-RNTI may have a corresponding relationship with the PRACH resource for transmitting the Preamble in the first message, and/or the PUSCH resource for transmitting the payload. That is, the terminal device or the network device may determine the RA-RNTI according to the PRACH resource of the Preamble transmitted in the first message, and/or the PUSCH resource of the payload transmitted.

Exemplarily, the correspondence between the RA-RNTI and the PRACH resource for transmitting the Preamble in the first message may be: RA-RNTI may be calculated from the position of the PRACH time-frequency resource for transmitting the Preamble. A possible calculation method is as follows: (2):

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

Among them, s_id is the index of the first OFDM symbol of the PRACH resource for transmitting the Preamble in the first message (0≤s_id<14), and t_id is the first one of the PRACH resource for transmitting the Preamble in the first message in a system frame The index of the time slot (0≤t_id<80), f_id is the index of the PRACH resource for transmitting the Preamble in the first message in the frequency domain (0≤f_id<8), and ul_carrier_id is the uplink used to transmit the Preamble in the first message Carrier (0 means NUL carrier, 1 means SUL carrier).

After the terminal device determines the first target RNTI, the terminal device may blindly detect the first PDCCH according to the first target RNTI.

In an implementation manner, the blind detection of the first PDCCH by the terminal device may include: after the terminal device sends the first message to the network device, the terminal device starts a first timer or opens a first window, and the first timer or Within the duration of the window, blindly check the first PDCCH.

Optionally, the duration of the first timer or the first window may be preset on the terminal device based on a protocol, or may be pre-configured by the network device to the terminal device, for example, it may be configured through RRC signaling.

It should be understood that the first timer or the first window may be started after the random access preamble is sent, or after the uplink message is sent, which is not specifically limited in the embodiment of the present application.

The following describes the next behavior of the terminal device from two cases where the first target RNTI is C-RNTI or RA-RNTI.

Case 1: The first target RNTI is C-RNTI.

In this case, if the terminal device does not blindly detect the second PDCCH, the terminal device can determine whether the contention conflict in the random access process has been resolved according to the result of blindly detecting the first PDCCH.

Specifically, if the terminal device blindly detects the first PDCCH scrambled by the C-RNTI, and the C-RNTI matches the first identifier in the first message successfully, the terminal device can determine the contention conflict in the random access process solved. If the terminal device blindly detects the first PDCCH scrambled by the C-RNTI, but the C-RNTI does not match the first identifier in the first message successfully, the terminal device may determine that the contention conflict in the random access process is not resolved.

Or, if the terminal device does not blindly detect the first PDCCH scrambled by the C-RNTI, the terminal device may determine that the contention conflict in the random access process is not resolved, and the terminal device may resend the first message to the network device.

Case 2: The first target RNTI is RA-RNTI.

In this case, if the terminal device does not blindly detect the first PDCCH, the terminal device may resend the first message to the network device.

If the terminal device blindly detects the first PDCCH and successfully decodes the first indication information, and the first indication information includes a MAC subPDU, the RAPID included in the header of the MAC subPDU corresponds to the Preamble index in the first message, then The terminal device may determine that the first indication information has been successfully decoded, and the terminal device may determine whether to blindly detect the second PDCCH and determine the second target RNTI for blindly detecting the second PDCCH according to the first indication information. The information scheduled by the first PDCCH may include the first indication information, or the physical downlink shared channel (Physical Downlink Shared Channel, PDSCH) scheduled by the first PDCCH may include the first indication information.

In the embodiments of this application, the first PDCCH or the second PDCCH may also be an enhanced physical downlink control channel (EPDCCH), a machine type communication physical downlink control channel (Machine Type Communication Physical Downlink Control Channel, MPDCCH) ), Narrowband Physical Downlink Control Channel (NPDCCH), which is not limited in this application.

As an example, if the value of at least one bit in the first indication information is the first value, the first indication may be used to instruct the terminal device to blindly detect the second PDCCH.

Or, if the value of at least one bit in the first indication information is the second value, the first indication may be used to instruct the terminal device not to blindly detect the second PDCCH.

Preferably, the first indication information is one bit. In this case, the first value can be "0" or "1", and the second value can also be "0" or "1". When the first value is "0", the second value is "1"; when the first value is "1", the second value is "0".

As another example, if the number of bits of the first indication information is multiple, and when the multiple bits are the same, the first indication information can be used to instruct the terminal device to detect the second PDCCH; if there are at least two of the multiple bits The bits are different, and the first indication information may be used to instruct the terminal device not to detect the second PDCCH. For example, the 3 bits in the first indication information are used to indicate whether the terminal device detects the second PDCCH, "000" indicates that the terminal device detects the second PDCCH, and "010" indicates that the terminal device does not detect the second PDCCH.

It should be understood that the specific examples in the embodiments of the present application are only used to help those skilled in the art to better understand the embodiments of the present invention, rather than limiting the scope of the embodiments of the present application. For example, when multiple bits are the same, the first indication information may be used to instruct the terminal device not to detect the second PDCCH.

As another example, the first indication information may indicate whether the terminal device detects the second PDCCH through the first parameter. Exemplarily, if the first indication information includes the first parameter, the terminal device is instructed to detect the second PDCCH; if the first indication information does not include the first parameter, the terminal device is instructed not to detect the second PDCCH.

It should be noted that the embodiment of the present application does not specifically limit the first parameter, and any parameter that can indicate whether the terminal device detects the second PDCCH is included in the protection scope of the present application.

Optionally, the first indication information may be RAR. The format of the RAR may be the same as or different from the format of the RAR in FIG. 7, which is not specifically limited in the embodiment of the present application.

Optionally, the bit position of the at least one bit may be equal to the bit position of the reserved bit in the four-step random access. Exemplarily, as shown in FIG. 7, at this time, the number of the at least one bit is one. For example, the RAR may use bit "1" to instruct the terminal device to detect the second PDCCH, and use bit "0" to instruct the terminal device not to detect the second PDCCH.

It should be noted that the embodiment of the present application does not limit the name of the at least one bit.

Optionally, the first indication information may also be downlink control information (Downlink Control Information, DCI) carried by the first PDCCH, or other information carried by the first PDCCH.

For the terminal device, if the first indication information is used to instruct the terminal device not to detect the second PDCCH, in one case, the terminal device can fall back to the four-step random access, and the behavior is consistent with the four-step random access, namely: a. Process TAC; b. Process UL grant; c. Set TC-RNTI value; d. If there is no MAC PDU in the Msg3 buffer, the terminal device can generate Msg3MAC PDU; e. The terminal device stops blindly checking the second message window or Timer. After that, the terminal device can send Msg3 to the network device, and the network device sends Msg4 to the terminal device after receiving the Msg3. In another case, the terminal device may retransmit the first message to the network device.

If the first indication information is used to instruct the terminal device to blindly detect the second PDCCH, the terminal device blindly detects the second PDCCH.

Optionally, the terminal device may blindly detect the second PDCCH according to the second target RNTI.

In an implementation manner, the second target RNTI may be TC-RNTI or C-RNTI.

At this time, the terminal device may set a TC-RNTI or C-RNTI value, and the TC-RNTI or C-RNTI value is used for the terminal device to blindly detect possible second PDCCH scheduling in the second message.

As an example, if the terminal device blindly detects the second PDCCH by using the TC-RNTI, and the first identifier matches the second identifier successfully, the terminal device may determine that the random access contention conflict has been resolved. The second identifier may be an identifier carried by the second PDCCH or an identifier in the PDSCH scheduled by the second PDCCH.

Specifically, if the terminal device blindly detects the first PDCCH scrambled by TC-RNTI, and the terminal device successfully decodes the MAC PDU contained in the scheduling data, and the conflict resolution ID contained in the MAC PDU matches the first message If the CCCH and SDU included in the Payload, the terminal device can determine that the contention conflict of the two-step random access has been resolved. Among them, the second identifier is the contention conflict resolution ID MAC CE.

In another implementation manner, the second PDCCH may be scrambled by the third identifier. Exemplarily, the third identifier may be a random number, 5G-S-TMSI, I-RNTI, Short I-RNTI, etc.

In this implementation mode, if the terminal device blindly detects the first PDCCH scrambled by the third identifier, the terminal device can match the third identifier with the first identifier. If the matching is successful, the terminal device can determine the two-step random access Incoming competition conflict has been resolved. For example, if the second PDCCH is scrambled by a fixed-size random number, the terminal device can match the fixed-size random number with the first identifier. If the matching is successful, the terminal device can determine the two-step random access The competition conflict has been resolved.

The first identifier mentioned in the above content matches the second identifier (or third identifier) successfully, which can be understood as: the first identifier and the second identifier (or third identifier) are the same; or, the first identifier and the second identifier ( Or the third identifier) is different but belongs to the same terminal device; or, the first identifier and the second identifier (or third identifier) have a corresponding relationship.

Further, if the terminal device blindly detects the second PDCCH, the terminal device can also process the RAR scheduled by the first PDCCH, such as processing TAC, uplink authorization, and so on.

FIG. 10 is a diagram of a specific implementation example of an embodiment of the present application. In Figure 10, an arrow indicates one data transmission, and there are 3 data transmissions in total. The first identifier is an identifier other than C-RNTI, and the second target RNTI is TC-RNTI or C-RNTI.

It can be seen that the terminal device sends the first message to the network device. After that, the terminal device starts the first timer or opens the first window, and blindly detects the second message within the duration of the first timer or the first window. After receiving the first message, the network device sends a second message to the terminal device. The second message includes the RAR and Msg B1. The network device uses the first PDCCH scrambled by RA-RNTI to schedule the RAR. After successfully decoding the first PDCCH, the terminal device can determine whether to blindly detect the second PDCCH according to the indication of the RAR. If the RAR indicates blind detection of the second PDCCH, the terminal device blindly detects the second PDCCH; if the RAR indicates not blind detection of the second PDCCH, the terminal device does not blindly detect the second PDCCH. Among them, the network equipment uses the second PDCCH scrambled by TC-RNTI or C-RNTI to schedule Msg B1.

After the terminal device resolves the contention conflict, the fourth indication information in the second PDCCH may be used for data transmission.

Optionally, the fourth indication information may be used to indicate whether the terminal device uses the parameters in the RAR for data transmission. For example, whether to use the uplink authorization in RAR for data transmission. If the fourth indication information indicates that the parameters in the RAR of the terminal device perform data transmission, the terminal device can use the parameters in the RAR to perform data transmission.

Optionally, the fourth indication information may include parameters required by the terminal device for uplink transmission. For example, TAC and so on. In this way, the terminal device does not need to process RAR.

It should be understood that in the embodiments of the present application, "first", "second", "third", and "fourth" are only used to distinguish different objects, but do not limit the scope of the embodiments of the present application.

In the embodiment of this application, in the two-step random access process, the network device may send the first PDCCH and the second PDCCH to the terminal device, and the terminal device may determine whether to blindly check the second PDCCH according to the result of blindly checking the first PDCCH. If the terminal device determines to blindly detect the second PDCCH, it can determine whether the contention conflict in the random access process has been resolved according to the result of the blind detection of the second PDCCH, so that the contention conflict in the two-step random access process can be resolved.

The preferred embodiments of the present application are described in detail above with reference to the accompanying drawings. However, the present application is not limited to the specific details in the above-mentioned embodiments. Within the scope of the technical concept of the present application, various simple modifications can be made to the technical solutions of the present application. These simple variants all belong to the protection scope of this application.

For example, the specific technical features described in the above specific embodiments can be combined in any suitable manner without contradiction. In order to avoid unnecessary repetition, this application no longer discusses various possible combinations. Explain separately.

For another example, various different implementations of this application can also be combined arbitrarily, as long as they do not violate the idea of this application, they should also be regarded as the content disclosed in this application.

It should be understood that, in the various method embodiments of the present application, the size of the sequence number of the foregoing processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not be implemented in this application. The implementation process of the example constitutes any limitation.

The communication method according to the embodiment of the present application is described in detail above. The communication device according to the embodiment of the present application will be described below with reference to FIG. 11 to FIG. 13. The technical features described in the method embodiment are applicable to the following device embodiments.

FIG. 11 shows a schematic block diagram of a terminal device 400 according to an embodiment of the present application. As shown in FIG. 11, the terminal device 400 includes:

The communication unit 410 is configured to send a first message to a network device, the first message including a preamble for random access and an uplink message, the uplink message including a first identifier.

The processing unit 420 is configured to determine, according to the first identifier, a first target radio network temporary identifier RNTI used for blind detection of the first physical downlink control channel PDCCH.

The processing unit 420 is further configured to blindly detect the first PDCCH according to the first target RNTI.

The processing unit 420 is further configured to determine whether to blindly detect the second PDCCH according to the result of the blind detection of the first PDCCH.

The processing unit 420 is further configured to, if it is determined to blindly detect the second PDCCH, blindly detect the second PDCCH.

The processing unit 420 is further configured to determine whether the contention conflict in the random access process has been resolved according to the result of the blind detection of the second PDCCH.

Optionally, in the embodiment of the present application, the processing unit 420 is further configured to: after the communication unit 410 sends the first message to the network device, start a first timer or open a first window; The processing unit 420 is specifically configured to: blindly detect the first PDCCH according to the first target RNTI within the duration range of the first timer or the first window.

Optionally, in this embodiment of the present application, the first identifier is a cell-radio network temporary identifier C-RNTI, and the first target RNTI is a C-RNTI.

Optionally, in the embodiment of the present application, if the terminal device 400 does not blindly check the second PDCCH, the processing unit 420 is further configured to: determine whether it has been resolved according to the result of the blind check of the first PDCCH Contention conflict during random access.

Optionally, in the embodiment of the present application, the processing unit 420 is specifically configured to: if the processing unit 420 blindly detects the first PDCCH, determine that the contention conflict in the random access process has been resolved; The processing unit 420 does not blindly detect the first PDCCH, and determines that the contention conflict in the random access process is not resolved.

Optionally, in this embodiment of the present application, the first identifier is an identifier other than the C-RNTI, and the first target RNTI is an RA-RNTI.

Optionally, in the embodiment of the present application, the RA-RNTI is based on the physical random access channel PRACH resource for transmitting the random access preamble, and/or the physical uplink shared channel PUSCH for transmitting the uplink message The location of the resource is determined.

Optionally, in the embodiment of the present application, the processing unit 420 is specifically configured to: if the processing unit 420 blindly detects the first PDCCH, determine whether to blindly detect the second PDCCH according to the first indication information, and The second target RNTI is determined, where the first PDCCH includes the first indication information, or the PDSCH scheduled by the first PDCCH includes the first indication information.

Optionally, in this embodiment of the application, if the value of at least one bit in the first indication information is a first value, the first indication information is used to instruct the terminal device to blindly detect the second PDCCH .

Optionally, in this embodiment of the present application, if the value of at least one bit in the first indication information is the second value, the first indication information is used to instruct the terminal device not to blindly check the second value. PDCCH.

Optionally, in the embodiment of the present application, the processing unit 420 is specifically configured to: if the first indication information is used to instruct the terminal device 400 to blindly detect the second PDCCH, determine to blindly detect the second PDCCH PDCCH; if the first indication information is used to instruct the terminal device 400 not to blindly detect the second PDCCH, determine not to blindly detect the second PDCCH.

Optionally, in this embodiment of the present application, the first indication information is included in a random access response RAR.

Optionally, in this embodiment of the application, the bit position of at least one bit in the RAR is equal to the bit position of a reserved bit in the four-step random access.

Optionally, in this embodiment of the application, if the terminal device does not blindly detect the second PDCCH, the communication unit 410 is further configured to: send a message 3 in four-step random access to the network device; Receive the message 4 sent by the network device for the message 3;

The processing unit 420 is further configured to: according to the message 4, determine whether the contention conflict in the random access process has been resolved.

Optionally, in this embodiment of the present application, if the terminal device 400 does not blindly detect the second PDCCH, the communication unit 410 is further configured to: retransmit the first message to the network device.

Optionally, in this embodiment of the present application, if the terminal device determines to blindly detect the second PDCCH, the processing unit 420 is specifically configured to: use the second target RNTI to blindly detect the second PDCCH.

Optionally, in the embodiment of the present application, the processing unit 420 is specifically configured to: if the terminal device 400 blindly detects the second PDCCH, and the first identifier matches the second identifier successfully, then determine that the resolution has been resolved In a contention conflict in a random access process, the second identifier is a conflict resolution identifier carried in the second PDCCH, or the second identifier is a conflict resolution identifier carried in a PDSCH scheduled by the second PDCCH.

Optionally, in this embodiment of the present application, the second target RNTI is a cell-radio network temporary identifier C-RNTI or a temporary cell-radio network temporary identifier TC-RNTI.

Optionally, in the embodiment of the present application, the first identifier includes at least one of the following: a random number, a 5G-S-temporary mobile user identifier TMSI, I-RNTI, and Short I-RNTI.

Optionally, in this embodiment of the present application, the second PDCCH is used to indicate parameters used by the terminal device 400 for data transmission after the terminal device 400 resolves the contention conflict.

Optionally, in this embodiment of the present application, the parameters used by the terminal device 400 for data transmission include parameters in the RAR sent by the network device for the first message.

It should be understood that the terminal device 400 may correspond to the terminal device in the method 300, and can implement the corresponding operations of the terminal device in the method 300. For brevity, details are not described herein again.

FIG. 12 shows a schematic block diagram of a network device 500 according to an embodiment of the present application. As shown in FIG. 12, the network device 500 includes:

The communication unit 510 is configured to receive a first message sent by a terminal device, the first message including a random access preamble and an uplink message, the uplink message including a first identifier.

The processing unit 520 is configured to decode the first message.

The processing unit 520 is further configured to determine a response message sent to the terminal device according to the decoding situation of the first message.

Optionally, in this embodiment of the present application, the communication unit 510 is further configured to: if the random access preamble is successfully decoded and the first identifier is successfully decoded, send the first target wireless signal to the terminal device. The first physical downlink control channel PDCCH scrambled by the network temporary identifier RNTI.

Optionally, in the embodiment of the present application, the communication unit 510 is specifically configured to send the first PDCCH and the second PDCCH scrambled by the second target RNTI to the terminal device.

Optionally, in this embodiment of the application, the first indication information is used to indicate whether the terminal device blindly detects the second PDCCH, wherein the first PDCCH scheduling information includes the first indication information, or The PDSCH scheduled by the first PDCCH includes the first indication information.

Optionally, in this embodiment of the present application, if the value of at least one bit in the first indication information is a first value, the first indication is used to instruct the terminal device to blindly detect the second PDCCH.

Optionally, in this embodiment of the present application, the first indication information is a random access response RAR.

Optionally, in this embodiment of the present application, the bit position of at least one bit in the RAR is equal to the bit position of a reserved bit in the four-step random access.

Optionally, in the embodiment of the present application, if the first indication information is used to instruct the terminal device not to detect the second PDCCH, the communication unit 510 is further configured to: receive the fourth PDCCH sent by the terminal device. Step: Message 3 in random access; For the message 3, message 4 is sent to the terminal device.

Optionally, in this embodiment of the present application, if the first indication information is used to instruct the terminal device not to detect the second PDCCH, the communication unit 510 is further configured to: receive the retransmission of the terminal device The first message.

Optionally, in the embodiment of the present application, the second PDCCH is used to indicate the parameters used by the terminal device for data transmission when the terminal device determines that the contention conflict in the random access process has been resolved.

Optionally, in this embodiment of the present application, the parameters used by the terminal device for data transmission include parameters in the information scheduled by the first PDCCH.

Optionally, in this embodiment of the application, the RA-RNTI is based on the physical random access channel PRACH resource for receiving the random access preamble, and/or the physical uplink shared channel PUSCH for receiving the uplink message The location of the resource is determined.

Optionally, in the embodiment of the present application, the communication unit 510 is further configured to: if the random access preamble is successfully decoded and the first identifier fails to be decoded, send a four-step random access to the terminal device. Incoming message 2; or sending second indication information to the terminal device, where the second indication information is used to instruct the terminal device to retransmit the first message.

It should be understood that the network device 500 may correspond to the network device in the method 300, and can implement the corresponding operations of the network device in the method 300. For brevity, details are not described herein again.

FIG. 13 is a schematic structural diagram of a communication device 600 provided by an embodiment of the present application. The communication device 600 shown in FIG. 13 includes a processor 610, and the processor 610 can call and run a computer program from a memory to implement the method in the embodiment of the present application.

Optionally, as shown in FIG. 13, the communication device 600 may further include a memory 620. The processor 610 may call and run a computer program from the memory 620 to implement the method in the embodiment of the present application.

The memory 620 may be a separate device independent of the processor 610, or may be integrated in the processor 610.

Optionally, as shown in FIG. 13, the communication device 600 may further include a transceiver 630, and the processor 6710 may control the transceiver 630 to communicate with other devices. Specifically, it may send information or data to other devices, or receive other devices. Information or data sent by the device.

The transceiver 630 may include a transmitter and a receiver. The transceiver 630 may further include an antenna, and the number of antennas may be one or more.

Optionally, the communication device 600 may specifically be a network device in an embodiment of the present application, and the communication device 600 may implement the corresponding process implemented by the network device in each method of the embodiment of the present application. For brevity, details are not repeated here. .

Optionally, the communication device 600 may specifically be a terminal device in an embodiment of this application, and the communication device 600 may implement the corresponding procedures implemented by the terminal device in each method of the embodiment of the application. .

FIG. 14 is a schematic structural diagram of a chip of an embodiment of the present application. The chip 700 shown in FIG. 14 includes a processor 710, and the processor 710 can call and run a computer program from the memory to implement the method in the embodiment of the present application.

Optionally, as shown in FIG. 14, the chip 700 may further include a memory 720. Wherein, the processor 710 may call and run a computer program from the memory 720 to implement the method in the embodiment of the present application.

The memory 720 may be a separate device independent of the processor 710, or may be integrated in the processor 710.

Optionally, the chip 700 may further include an input interface 730. The processor 710 may control the input interface 730 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

Optionally, the chip 700 may further include an output interface 740. The processor 710 can control the output interface 740 to communicate with other devices or chips, and specifically, can output information or data to other devices or chips.

Optionally, the chip can be applied to the terminal device in the embodiment of the present application, and the chip can implement the corresponding process implemented by the terminal device in the various methods of the embodiment of the present application. For brevity, details are not repeated here.

Optionally, the chip can be applied to the network device in the embodiment of the present application, and the chip can implement the corresponding process implemented by the network device in the various methods of the embodiment of the present application. For brevity, details are not described herein again.

It should be understood that the chip mentioned in the embodiment of the present application may also be referred to as a system-level chip, a system-on-chip, a system-on-chip, or a system-on-chip.

It should be understood that the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capability. In the implementation process, the steps of the foregoing method embodiments can be completed by hardware integrated logic circuits in the processor or instructions in the form of software. The aforementioned processor may be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (ASIC), a ready-made programmable gate array (Field Programmable Gate Array, FPGA) or other Programming logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like. The steps of the method disclosed in the embodiments of the present application may be directly embodied as being executed and completed by a hardware decoding processor, or executed and completed by a combination of hardware and software modules in the decoding processor. The software module can be located in a mature storage medium in the field such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

It can be understood that the memory in the embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory. Among them, the non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), and electrically available Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory. The volatile memory may be a random access memory (Random Access Memory, RAM), which is used as an external cache. By way of exemplary but not restrictive description, many forms of RAM are available, such as static random access memory (Static RAM, SRAM), dynamic random access memory (Dynamic RAM, DRAM), synchronous dynamic random access memory (Synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory (Synchlink DRAM, SLDRAM) ) And Direct Rambus RAM (DR RAM). It should be noted that the memories of the systems and methods described herein are intended to include, but are not limited to, these and any other suitable types of memories.

It should be understood that the foregoing memory is exemplary but not restrictive. For example, the memory in the embodiment of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc. That is to say, the memory in the embodiment of the present application is intended to include but not limited to these and any other suitable types of memory.

FIG. 15 is a schematic block diagram of a communication system 800 according to an embodiment of the present application. As shown in FIG. 15, the communication system 800 includes a terminal device 810 and a network device 820.

Wherein, the terminal device 810 can be used to implement the corresponding function implemented by the terminal device in the above method, and the network device 820 can be used to implement the corresponding function implemented by the network device in the above method. For brevity, it will not be repeated here. .

The embodiment of the present application also provides a computer-readable storage medium for storing computer programs.

Optionally, the computer-readable storage medium can be applied to the terminal device in the embodiment of the present application, and the computer program causes the computer to execute the corresponding process implemented by the terminal device in each method of the embodiment of the present application. For brevity, here No longer.

Optionally, the computer-readable storage medium may be applied to the network device in the embodiment of the present application, and the computer program causes the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application. For brevity, here No longer.

The embodiments of the present application also provide a computer program product, including computer program instructions.

Optionally, the computer program product can be applied to the terminal device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the terminal device in each method of the embodiment of the present application. For the sake of brevity, it is not here. Repeat it again.

Optionally, the computer program product can be applied to the network device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application. For the sake of brevity, it is not here. Repeat it again.

The embodiment of the present application also provides a computer program.

Optionally, the computer program can be applied to the terminal device in the embodiment of the present application. When the computer program runs on the computer, it causes the computer to execute the corresponding process implemented by the terminal device in each method of the embodiment of the present application. For the sake of brevity , I won’t repeat it here.

Optionally, the computer program can be applied to the network device in the embodiment of the present application. When the computer program runs on the computer, the computer is caused to execute the corresponding process implemented by the network device in each method of the embodiment of the present application. For the sake of brevity , I won’t repeat it here.

A person of ordinary skill in the art may be aware that the units and algorithm steps of the examples described in combination with the embodiments disclosed herein can be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether these functions are executed by hardware or software depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that, for the convenience and conciseness of description, the specific working process of the above-described system, device, and unit can refer to the corresponding process in the foregoing method embodiment, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, device, and method may be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components can be combined or It can be integrated into another system, or some features can be ignored or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.

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

If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium. Based on this understanding, the technical solution of this application essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory,) ROM, random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program code .

The above are only specific implementations of this application, but the protection scope of this application is not limited to this. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed in this application. Should be covered within the scope of protection of this application. Therefore, the protection scope of this application shall be subject to the protection scope of the claims.

Claims

A random access method, characterized in that the method includes:

The terminal device sends a first message to the network device, where the first message includes a random access preamble and an uplink message, and the uplink message includes a first identifier;

The terminal device determines, according to the first identifier, a first target radio network temporary identifier RNTI used for blind detection of the first physical downlink control channel PDCCH;

The terminal device blindly detects the first PDCCH according to the first target RNTI;

The terminal device determines whether to blindly detect the second PDCCH according to the result of blindly detecting the first PDCCH;

If the terminal device determines to blindly detect the second PDCCH, the terminal device blindly detects the second PDCCH;

The terminal device determines whether the contention conflict in the random access process has been resolved according to the result of the blind detection of the second PDCCH.
The method of claim 1, wherein the method further comprises:

After the terminal device sends the first message to the network device, the terminal device starts a first timer or opens a first window;

The blind detection of the first PDCCH by the terminal device according to the first target RNTI includes:

The terminal device blindly detects the first PDCCH according to the first target RNTI within the duration range of the first timer or the first window.
The method according to claim 1 or 2, wherein the first identifier is a cell-radio network temporary identifier C-RNTI, and the first target RNTI is a C-RNTI.
The method according to claim 3, wherein if the terminal device does not blindly detect the second PDCCH, the method further comprises:

The terminal device determines whether the contention conflict in the random access process has been resolved according to the result of the blind detection of the first PDCCH.
The method according to claim 4, wherein the terminal device determines whether the contention conflict in the random access process has been resolved according to the result of the blind detection of the first PDCCH, comprising:

If the terminal device blindly detects the first PDCCH, the terminal device determines that the contention conflict in the random access process has been resolved;

If the terminal device does not blindly detect the first PDCCH, the terminal device determines that the contention conflict in the random access process is not resolved.
The method according to claim 1 or 2, wherein the first identifier is an identifier other than the C-RNTI, and the first target RNTI is an RA-RNTI.
The method according to claim 6, wherein the RA-RNTI is based on the physical random access channel PRACH resource for transmitting the random access preamble, and/or the physical uplink sharing for transmitting the uplink message The location of the channel PUSCH resource is determined.
The method according to claim 6 or 7, wherein the terminal device determines whether to blindly detect the second PDCCH according to the result of blindly detecting the first PDCCH, comprising:

If the terminal device blindly detects the first PDCCH, the terminal device determines whether to blindly detect the second PDCCH according to the first indication information, where the first PDCCH includes the first indication information, or The PDSCH scheduled by the first PDCCH includes the first indication information.
The method according to claim 8, wherein if the value of at least one bit in the first indication information is a first value, the first indication information is used to instruct the terminal device to blindly detect the first value. Two PDCCH.
The method according to claim 8, wherein if the value of at least one bit in the first indication information is the second value, the first indication information is used to instruct the terminal device not to blindly check the The second PDCCH.
The method according to any one of claims 8 to 10, wherein the terminal device determining whether to blindly check the second PDCCH according to the first indication information comprises:

If the first indication information is used to instruct the terminal device to blindly detect the second PDCCH, the terminal device determines to blindly detect the second PDCCH;

If the first indication information is used to indicate that the terminal device does not blindly detect the second PDCCH, the terminal device determines not to blindly detect the second PDCCH.
The method according to any one of claims 8 to 11, wherein the first indication information is included in a random access response RAR.
The method according to claim 12, wherein the bit position of at least one bit in the RAR is equal to the bit position of a reserved bit in the four-step random access.
The method according to any one of claims 6 to 13, wherein if the terminal device does not blindly detect the second PDCCH, the method further comprises:

The terminal device sends a message 3 in four-step random access to the network device;

The terminal device receives the message 4 sent by the network device for the message 3;

According to the message 4, the terminal device determines whether the contention conflict in the random access process has been resolved.
The method according to any one of claims 6 to 13, wherein if the terminal device does not blindly detect the second PDCCH, the method further comprises:

The terminal device retransmits the first message to the network device.
The method according to any one of claims 6 to 13, wherein if the terminal device determines to blindly detect the second PDCCH, the terminal device blindly detects the second PDCCH, comprising:

The terminal device uses the second target RNTI to blindly detect the second PDCCH.
The method according to claim 16, wherein the terminal device determines whether the contention conflict in the random access process has been resolved according to the result of the blind detection of the second PDCCH, comprising:

If the terminal device blindly detects the second PDCCH, and the first identifier matches the second identifier successfully, the terminal device determines that the contention conflict in the random access process has been resolved, where the second identifier is The conflict resolution identifier carried by the second PDCCH, or the second identifier is the conflict resolution identifier carried in the PDSCH scheduled by the second PDCCH.
The method according to claim 16 or 17, wherein the second target RNTI is a cell-radio network temporary identification C-RNTI or a temporary cell-radio network temporary identification TC-RNTI.
The method according to any one of claims 6 to 18, wherein the first identifier includes at least one of the following: a random number, a 5G-serving temporary mobile user identifier 5G-S-TMSI, and a wireless network identifier Temporary identifier I-RNTI, short identifier wireless network temporary identifier Short I-RNTI.
The method according to any one of claims 1 to 19, wherein the second PDCCH is used to indicate a parameter used by the terminal device for data transmission after the terminal device resolves a contention conflict.
The method according to claim 20, wherein the parameters used by the terminal device for data transmission include parameters in the RAR sent by the network device for the first message.
A random access method, characterized in that the method includes:

The network device receives a first message sent by the terminal device, where the first message includes a random access preamble and an uplink message, and the uplink message includes a first identifier;

The network device decodes the first message;

The network device determines the response message to be sent to the terminal device according to the decoding situation of the first message.
The method according to claim 22, wherein the network device determining the response message sent to the terminal device according to the decoding situation of the first message comprises:

If the random access preamble is successfully decoded and the first identifier is successfully decoded, the network device sends the first physical downlink control channel PDCCH scrambled by the first target radio network temporary identifier RNTI to the terminal device.
The method according to claim 23, wherein the first identifier is a cell-radio network temporary identifier C-RNTI, and the first target RNTI is a C-RNTI.
The method according to claim 23, wherein the first identifier is an identifier other than the C-RNTI, and the first target RNTI is an RA-RNTI.
The method according to claim 25, wherein the sending, by the network device to the terminal device, the first physical downlink control channel PDCCH scrambled by the first target radio network temporary identifier RNTI comprises:

The network device sends the first PDCCH and the second PDCCH scrambled by the second target RNTI to the terminal device.
The method according to claim 26, wherein the first indication information is used to indicate whether the terminal device blindly detects the second PDCCH, wherein the first PDCCH scheduling information includes the first indication information Or the PDSCH scheduled by the first PDCCH includes the first indication information.
The method according to claim 27, wherein if the value of at least one bit in the first indication information is a first value, the first indication is used to instruct the terminal device to blindly check the second PDCCH.
The method according to claim 27, wherein if the value of at least one bit in the first indication information is the second value, the first indication information is used to instruct the terminal device not to blindly check the The second PDCCH.
The method according to any one of claims 27 to 29, wherein the first indication information is a random access response RAR.
The method according to claim 30, wherein the bit position of at least one bit in the RAR is equal to the bit position of a reserved bit in the four-step random access.
The method according to any one of claims 27 to 31, wherein if the first indication information is used to indicate that the terminal device does not detect the second PDCCH, the method further comprises:

The network device receives the message 3 in the four-step random access sent by the terminal device;

For the message 3, the network device sends a message 4 to the terminal device.
The method according to any one of claims 27 to 31, wherein if the first indication information is used to indicate that the terminal device does not detect the second PDCCH, the method further comprises:

The network device receives the first message retransmitted by the terminal device.
The method according to any one of claims 26 to 33, wherein the second PDCCH is used to indicate that when the terminal device determines that the contention conflict in the random access process has been resolved, the terminal device performs Parameters used for data transmission.
The method according to claim 34, wherein the parameters used by the terminal device for data transmission include parameters in the information scheduled by the first PDCCH.
The method according to any one of claims 26 to 35, wherein the second target RNTI is a cell-radio network temporary identification C-RNTI or a temporary cell-radio network temporary identification TC-RNTI.
The method according to any one of claims 25 to 36, wherein the RA-RNTI is based on the physical random access channel PRACH resource that receives the random access preamble, and/or receives the The location of the physical uplink shared channel PUSCH resource of the uplink message is determined.
The method according to any one of claims 25 to 37, wherein the first identifier comprises at least one of the following: a random number, a 5G-serving temporary mobile user identifier 5G-S-TMSI, and a wireless network identifier Temporary identifier I-RNTI, short identifier wireless network temporary identifier Short I-RNTI.
The method according to claim 22, wherein the network device determining the response message sent to the terminal device according to the decoding situation of the first message comprises:

If the random access preamble is successfully decoded and the first identifier fails to be decoded, the network device sends a four-step random access message 2 to the terminal device; or

The network device sends second indication information to the terminal device, where the second indication information is used to instruct the terminal device to retransmit the first message.
A terminal device, characterized by comprising:

A communication unit, configured to send a first message to a network device, where the first message includes a random access preamble and an uplink message, and the uplink message includes a first identifier;

A processing unit, configured to determine, according to the first identifier, a first target radio network temporary identifier RNTI used for blind detection of the first physical downlink control channel PDCCH;

The processing unit is further configured to blindly detect the first PDCCH according to the first target RNTI;

The processing unit is further configured to determine whether to blindly detect the second PDCCH according to the result of the blind detection of the first PDCCH;

The processing unit is further configured to, if it is determined to blindly detect the second PDCCH, blindly detect the second PDCCH;

The processing unit is further configured to determine whether the contention conflict in the random access process has been resolved according to the result of the blind detection of the second PDCCH.
The terminal device according to claim 40, wherein the processing unit is further configured to:

After the communication unit sends the first message to the network device, start a first timer or open a first window;

The processing unit is specifically used for:

Blindly detect the first PDCCH according to the first target RNTI within the duration range of the first timer or the first window.
The terminal device according to claim 40 or 41, wherein the first identifier is a cell-radio network temporary identifier C-RNTI, and the first target RNTI is a C-RNTI.
The terminal device according to claim 42, wherein if the terminal device does not blindly detect the second PDCCH, the processing unit is further configured to:

According to the result of blind detection of the first PDCCH, it is determined whether the contention conflict in the random access process has been resolved.
The terminal device according to claim 43, wherein the processing unit is specifically configured to:

If the processing unit blindly detects the first PDCCH, determining that the contention conflict in the random access process has been resolved;

If the processing unit does not blindly detect the first PDCCH, it is determined that the contention conflict in the random access process is not resolved.
The terminal device according to claim 40 or 41, wherein the first identifier is an identifier other than the C-RNTI, and the first target RNTI is an RA-RNTI.
The terminal device according to claim 45, wherein the RA-RNTI is based on a physical random access channel PRACH resource for transmitting the random access preamble, and/or a physical uplink for transmitting the uplink message The location of the shared channel PUSCH resource is determined.
The terminal device according to claim 45 or 46, wherein the processing unit is specifically configured to:

If the processing unit blindly detects the first PDCCH, it determines whether to blindly detect the second PDCCH and determines the second target RNTI according to the first indication information, where the first PDCCH includes the first indication Information, or the PDSCH scheduled by the first PDCCH includes the first indication information.
The terminal device according to claim 47, wherein if the value of at least one bit in the first indication information is a first value, the first indication information is used to instruct the terminal device to blindly check the The second PDCCH.
The terminal device according to claim 47, wherein if the value of at least one bit in the first indication information is the second value, the first indication information is used to indicate that the terminal device does not blindly detect The second PDCCH.
The terminal device according to any one of claims 47 to 49, wherein the processing unit is specifically configured to:

If the first indication information is used to instruct the terminal device to blindly detect the second PDCCH, determine to blindly detect the second PDCCH;

If the first indication information is used to indicate that the terminal device does not blindly detect the second PDCCH, determine not to blindly detect the second PDCCH.
The terminal device according to any one of claims 47 to 50, wherein the first indication information is included in a random access response RAR.
The terminal device according to claim 51, wherein the bit position of at least one bit in the RAR is equal to the bit position of a reserved bit in the four-step random access.
The terminal device according to any one of claims 45 to 52, wherein if the terminal device does not blindly detect the second PDCCH, the communication unit is further configured to:

Sending a message 3 in four-step random access to the network device;

Receive the message 4 sent by the network device for the message 3;

The processing unit is also used for:

According to the message 4, it is determined whether the contention conflict in the random access process has been resolved.
The terminal device according to any one of claims 45 to 52, wherein if the terminal device does not blindly detect the second PDCCH, the communication unit is further configured to:

Retransmit the first message to the network device.
The terminal device according to any one of claims 45 to 52, wherein if the terminal device determines to blindly detect the second PDCCH, the processing unit is specifically configured to:

Using the second target RNTI, blindly check the second PDCCH.
The terminal device according to claim 55, wherein the processing unit is specifically configured to:

If the terminal device blindly detects the second PDCCH, and the first identifier matches the second identifier successfully, it is determined that the contention conflict in the random access process has been resolved, where the second identifier is the second The conflict resolution identifier carried by the PDCCH, or the second identifier is the conflict resolution identifier carried in the PDSCH scheduled by the second PDCCH.
The method according to claim 55 or 56, wherein the second target RNTI is a cell-radio network temporary identification C-RNTI or a temporary cell-radio network temporary identification TC-RNTI.
The terminal device according to any one of claims 45 to 57, wherein the first identifier includes at least one of the following: a random number, a G-service temporary mobile user identifier 5G-S-TMSI, and a wireless identifier. The network temporary identifier I-RNTI, the short identifier wireless network temporary identifier Short I-RNTI.
The terminal device according to any one of claims 40 to 58, wherein the second PDCCH is used to indicate a parameter used by the terminal device for data transmission after the terminal device resolves a contention conflict.
The terminal device according to claim 59, wherein the parameters used by the terminal device for data transmission include parameters in the RAR sent by the network device for the first message.
A network device, characterized by comprising:

A communication unit, configured to receive a first message sent by a terminal device, where the first message includes a random access preamble and an uplink message, and the uplink message includes a first identifier;

A processing unit, configured to decode the first message;

The processing unit is further configured to determine a response message to be sent to the terminal device according to the decoding situation of the first message.
The network device according to claim 61, wherein the communication unit is further configured to:

If the random access preamble is successfully decoded and the first identifier is successfully decoded, the first physical downlink control channel PDCCH scrambled by the first target radio network temporary identifier RNTI is sent to the terminal device.
The network device according to claim 62, wherein the first identifier is a cell-radio network temporary identifier C-RNTI, and the first target RNTI is a C-RNTI.
The network device according to claim 62, wherein the first identifier is an identifier other than the C-RNTI, and the first target RNTI is an RA-RNTI.
The network device according to claim 64, wherein the communication unit is specifically configured to:

Sending the first PDCCH and the second PDCCH scrambled by the second target RNTI to the terminal device.
The network device according to claim 65, wherein the first indication information is used to indicate whether the terminal device blindly detects the second PDCCH, wherein the first PDCCH scheduling information includes the first indication Information, or the PDSCH scheduled by the first PDCCH includes the first indication information.
The network device according to claim 66, wherein if the value of at least one bit in the first indication information is a first value, the first indication is used to instruct the terminal device to blindly check the first value. Two PDCCH.
The network device according to claim 66, wherein if the value of at least one bit in the first indication information is the second value, the first indication information is used to indicate that the terminal device does not blindly detect The second PDCCH.
The network device according to any one of claims 66 to 68, wherein the first indication information is a random access response RAR.
The network device according to claim 69, wherein the bit position of at least one bit in the RAR is equal to the bit position of a reserved bit in four-step random access.
The network device according to any one of claims 66 to 70, wherein if the first indication information is used to indicate that the terminal device does not detect the second PDCCH, the communication unit is further configured to:

Receiving message 3 in the four-step random access sent by the terminal device;

For the message 3, the message 4 is sent to the terminal device.
The network device according to any one of claims 66 to 70, wherein if the first indication information is used to indicate that the terminal device does not detect the second PDCCH, the communication unit is further configured to:

Receiving the first message retransmitted by the terminal device.
The network device according to any one of claims 65 to 72, wherein the second PDCCH is used to indicate that when the terminal device determines that the contention conflict in the random access process has been resolved, the terminal device Parameters used for data transmission.
The network device according to claim 73, wherein the parameters used by the terminal device for data transmission include parameters in the information scheduled by the first PDCCH.
The network device according to any one of claims 65 to 74, wherein the second target RNTI is a cell-wireless network temporary identity C-RNTI or a temporary cell-wireless network temporary identity TC-RNTI.
The network device according to any one of claims 64 to 75, wherein the RA-RNTI is based on a physical random access channel PRACH resource receiving the random access preamble, and/or receiving The position of the physical uplink shared channel PUSCH resource of the uplink message is determined.
The network device according to any one of claims 64 to 76, wherein the first identifier comprises at least one of the following: a random number, a 5G-serving temporary mobile user identifier 5G-S-TMSI, and a wireless identifier The network temporary identifier I-RNTI, the short identifier wireless network temporary identifier Short I-RNTI.
The network device according to claim 77, wherein the communication unit is further configured to:

If the random access preamble is successfully decoded and the first identifier fails to be decoded, send a four-step random access message 2 to the terminal device; or

Sending second indication information to the terminal device, where the second indication information is used to instruct the terminal device to retransmit the first message.
A terminal device, characterized by comprising: a processor and a memory, the memory is used to store a computer program, the processor is used to call and run the computer program stored in the memory, and execute as claimed in claims 1 to 21 Any of the methods described.
A network device, characterized by comprising: a processor and a memory, the memory is used to store a computer program, the processor is used to call and run the computer program stored in the memory, and execute the Any of the methods described.
A chip, characterized by comprising: a processor, configured to call and run a computer program from a memory, so that a device installed with the chip executes the method according to any one of claims 1 to 21.
A chip, characterized by comprising: a processor, configured to call and run a computer program from a memory, so that a device installed with the chip executes the method according to any one of claims 22 to 39.
A computer-readable storage medium, characterized in that it is used to store a computer program that enables a computer to execute the method according to any one of claims 1 to 21.
A computer-readable storage medium, characterized in that it is used to store a computer program that enables a computer to execute the method according to any one of claims 22 to 39.
A computer program product, characterized by comprising computer program instructions, which cause a computer to execute the method according to any one of claims 1 to 21.
A computer program product, characterized by comprising computer program instructions, which cause a computer to execute the method according to any one of claims 22 to 39.
A computer program, wherein the computer program causes a computer to execute the method according to any one of claims 1 to 21.
A computer program, wherein the computer program causes a computer to execute the method according to any one of claims 22 to 39.