WO2025175520A1 - Wireless communication method and communication device - Google Patents

Abstract

Provided are a wireless communication method and a communication device. The wireless communication method comprises: a first terminal device initiates a first process, wherein in the first process, the first terminal device transmits a message 3 without transmitting a message 1 and/or receiving a random access response message.

Description

Wireless communication method and communication device Technical Field

The present application relates to the field of communication technology, and more particularly, to a wireless communication method and a communication device.

Background Art

In a communication system, a terminal device often needs to perform a random access process to perform uplink synchronization and/or data transmission with a network device. The traditional random access process has the problem of high signaling overhead.

Summary of the Invention

The present application provides a wireless communication method and a communication device. The following introduces various aspects involved in the present application.

In a first aspect, a wireless communication method is provided, including: a first terminal device initiating a first process; wherein, in the first process, the first terminal device transmits message 3 without transmitting message 1 and/or receiving a random access response message.

According to a second aspect, a wireless communication method is provided, including: a network device receives a message 3 sent by a first terminal device through a first process; wherein, in the first process, the first terminal device transmits message 3 without transmitting message 1 and/or receiving a random access response message.

According to a third aspect, a communication device is provided, which is a first terminal device, and includes: a processing unit for initiating a first process; wherein, in the first process, the first terminal device transmits message 3 without transmitting message 1 and/or receiving a random access response message.

In a fourth aspect, a communication device is provided, which is a network device, and the communication device includes: a receiving unit for receiving a message 3 sent by a first terminal device through a first process; wherein, in the first process, the first terminal device transmits message 3 without transmitting message 1 and/or receiving a random access response message.

In a fifth aspect, a communication device is provided, comprising a transceiver, a memory, and a processor, wherein the memory is used to store programs, and the processor is used to call the programs in the memory and control the transceiver to receive or send signals so that the communication device executes the method described in the first aspect or the second aspect.

In a sixth aspect, a device is provided, comprising a processor for calling a program from a memory so that the device executes the method as described in the first aspect or the second aspect.

In a seventh aspect, a chip is provided, comprising a processor for calling a program from a memory so that a device equipped with the chip executes the method as described in the first aspect or the second aspect.

In an eighth aspect, a computer-readable storage medium is provided, on which a program is stored, wherein the program enables a computer to execute the method as described in the first aspect or the second aspect.

In a ninth aspect, a computer program product is provided, comprising a program, wherein the program enables a computer to execute the method as described in the first aspect or the second aspect.

In a tenth aspect, a computer program is provided, which enables a computer to execute the method as described in the first aspect or the second aspect.

The embodiment of the present application directly transmits message 3 without transmitting message 1 and message 2, which can reduce the signaling overhead of the random access process.

BRIEF DESCRIPTION OF THE DRAWINGS

1A-1C are system architecture diagrams of communication systems to which embodiments of the present application may be applied.

FIG. 2A-FIG . 2B are schematic diagrams of a random access process applicable to an embodiment of the present application.

FIG3 is a schematic diagram of a data transmission flow of EDT according to an embodiment of the present application.

FIG4 is a flow chart of a wireless communication method according to an embodiment of the present application.

FIG5 is a schematic flow chart of a wireless communication method according to another embodiment of the present application.

FIG6 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application.

FIG7 is a schematic structural diagram of a communication device according to another embodiment of the present application.

FIG8 is a schematic diagram of the structure of the device provided in an embodiment of the present application.

DETAILED DESCRIPTION

The technical solution in this application will be described below with reference to the accompanying drawings.

Communication system architecture

The technical solutions of the embodiments of the present 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 (WCDMA) system, general packet radio service (GPRS), long term evolution (LTE) system, advanced long term evolution (LTE-A) system, new radio (NR) system, NR system evolution system, LT on unlicensed spectrum. LTE-based access to unlicensed spectrum (LTE-U) system, NR-based access to unlicensed spectrum (NR-U) system on unlicensed spectrum, non-terrestrial network (NTN) system, universal mobile telecommunication system (UMTS), wireless local area networks (WLAN), wireless fidelity (WiFi), fifth-generation (5G) system or other communication systems, such as future communication systems, such as sixth-generation mobile communication systems, and satellite communication systems.

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 (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), vehicle-to-vehicle (V2V) communication, or vehicle-to-everything (V2X) communication, etc. The embodiments of the present application can also be applied to these communication systems.

The communication system in the embodiments of the present application can be applied to carrier aggregation (CA) scenarios, dual connectivity (DC) scenarios, and standalone (SA) networking scenarios.

The communication system in the embodiment of the present application can be applied to an unlicensed spectrum, where the unlicensed spectrum can also be considered as a shared spectrum; or, the communication system in the embodiment of the present application can also be applied to an authorized spectrum, where the authorized spectrum can also be considered as a dedicated spectrum.

The embodiments of the present application can be applied to NTN systems as well as terrestrial networks (TN) systems. By way of example and not limitation, NTN systems include NR-based NTN systems and IoT-based NTN systems.

The embodiments of the present application describe various embodiments in conjunction with network equipment and terminal equipment, wherein the terminal equipment may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent or user device, etc.

In an embodiment of the present application, the terminal device may be a station (STATION, ST) in a WLAN, a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA) device, a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a next-generation communication system such as an NR network, or a terminal device in a future-evolved public land mobile network (PLMN) network, etc.

In the embodiments of the present application, a terminal device may be a device that provides voice and/or data connectivity to a user and can be used to connect people, objects, and machines, such as a handheld device or vehicle-mounted device with wireless connection capabilities. The terminal device in the embodiments of the present application may be a mobile phone, a tablet computer, a laptop computer, a PDA, a mobile internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in smart grids, a wireless terminal in transportation safety, a wireless terminal in smart cities, a wireless terminal in smart homes, etc. Optionally, the terminal device may be used to act as a base station. For example, a terminal device can act as a dispatching entity, providing sidelink signals between terminal devices in V2X or D2D. For example, a cell phone and a car can communicate with each other using sidelink signals. A cell phone and a smart home device can also communicate with each other without relaying the communication signal through a base station.

In an embodiment of the present application, the terminal device can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; it can also be deployed on the water surface (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons and satellites, etc.).

In the embodiments of the present application, the terminal device may be a mobile phone, a tablet computer, a computer with wireless transceiver functions, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical care, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, or a wireless terminal device in a smart home. The terminal device involved in the embodiments of the present application may also be referred to as a terminal, user equipment (UE), access terminal device, vehicle-mounted terminal, industrial control terminal, UE unit, UE station, mobile station, mobile station, remote station, remote terminal device, mobile device, UE, wireless communication device, UE agent, or UE device. The terminal device may also be fixed or mobile.

As an example but not a limitation, in the embodiment of the present application, the terminal device may also be a wearable device. Wearable devices can also be called wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses. Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not just hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. In a broad sense, wearable smart devices include those that are full-featured, large in size, and can achieve full or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those that focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

The network device in the embodiments of the present application may be a device for communicating with a terminal device. The network device may also be referred to as an access network device or a radio access network device. For example, the network device may be a base station. The network device in the embodiments of the present application may refer to a radio access network (RAN) node (or device) that connects a terminal device to a wireless network. The term “base station” can broadly cover the following various names or be replaced with the following names, such as: NodeB, evolved NodeB (eNB), next generation NodeB (gNB), relay station, access point, transmitting and receiving point (TRP), transmitting point (TP), master station MeNB, secondary station SeNB, multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. The base station can be a macro base station, a micro base station, a relay node, a donor node or the like, or a combination thereof. The base station can also refer to a communication module, a modem or a chip for being provided in the aforementioned device or apparatus. The base station can also be a mobile switching center and a device to device D2D, vehicle-to-everything (V2X), a device that performs the base station function in machine-to-machine (M2M) communications, a network side device in a 6G network, a device that performs the base station function in a future communication system, and the like. The base station can support networks with the same or different access technologies. The embodiments of the present application do not limit the specific technology and specific device form adopted by the network equipment.

Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move based on the location of the mobile base station. In other examples, a helicopter or drone can be configured to act as a device that communicates with another base station.

In some deployments, the network device in the embodiments of the present application may refer to a CU or a DU, or the network device may include a CU and a DU. The gNB may also include an AAU.

The network equipment and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; they can also be deployed in the air on aircraft, balloons, and satellites. The embodiments of this application do not limit the scenarios in which the network equipment and terminal devices are located.

As an example and not a limitation, in an embodiment of the present application, a network device may have a mobile feature, for example, the network device may be a mobile device. In some embodiments of the present application, the network device may be a satellite or a balloon station. For example, the satellite may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. In some embodiments of the present application, the network device may also be a base station set up in a location such as land or water.

In an embodiment of the present application, a network device may provide services for a cell, and a terminal device may communicate with the network device through the transmission resources used by the cell (e.g., frequency domain resources, or spectrum resources). The cell may be a cell corresponding to a network device (e.g., a base station). The cell may belong to a macro base station or a base station corresponding to a small cell. The small cells here may include: metro cells, micro cells, pico cells, femto cells, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

For example, Figure 1A is a schematic diagram of the architecture of a communication system provided in an embodiment of the present application. As shown in Figure 1A, the communication system 100 may include a network device 110, which may be a device that communicates with a terminal device 120 (or also referred to as 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 within the coverage area.

Figure 1A exemplarily shows a network device and two terminal devices. In some embodiments of the present application, the communication system 100 may include multiple network devices and each network device may include other number of terminal devices within its coverage area, which is not limited in the embodiments of the present application.

For example, FIG1B is a schematic diagram of the architecture of another communication system provided in an embodiment of the present application. Referring to FIG1B , a terminal device 1101 and a satellite 1102 are included, and wireless communication can be performed between the terminal device 1101 and the satellite 1102. The network formed between the terminal device 1101 and the satellite 1102 can also be referred to as an NTN. In the architecture of the communication system shown in FIG1B , the satellite 1102 can have the function of a base station, and the terminal device 1101 and the satellite 1102 can communicate directly. In the system architecture, the satellite 1102 can be referred to as a network device. In some embodiments of the present application, the communication system may include multiple network devices 1102, and each network device 1102 may include other numbers of terminal devices within its coverage area, which is not limited in the embodiments of the present application.

For example, FIG1C is a schematic diagram of the architecture of another communication system provided by an embodiment of the present application. Referring to FIG1C, the system includes a terminal device 1201, a satellite 1202, and a base station 1203. The terminal device 1201 and the satellite 1202 can communicate wirelessly. The satellite 1202 and the base station 1203 can communicate wirelessly. Stations 1203 can communicate with each other. The network formed between the terminal device 1201, the satellite 1202 and the base station 1203 can also be referred to as an NTN. In the architecture of the communication system shown in Figure 1C, the satellite 1202 may not have the function of a base station, and the communication between the terminal device 1201 and the base station 1203 needs to be relayed by the satellite 1202. In this system architecture, the base station 1203 can be referred to as a network device. In some embodiments of the present application, the communication system may include multiple network devices 1203, and each network device 1203 may include other number of terminal devices within its coverage area, which is not limited in the embodiments of the present application.

It should be noted that Figures 1A-1C are only examples of the system to which this application is applicable. Of course, the method shown in the embodiment of this application can also be applied to other systems, such as 5G communication systems, LTE communication systems, etc., and the embodiment of this application does not make specific limitations on this.

In some embodiments of the present application, the wireless communication system shown in Figures 1A-1C may also include other network entities such as a mobility management entity (MME) and an access and mobility management function (AMF), but the embodiments of the present application are not limited to this.

It should be understood that in the embodiments of the present application, a device having a communication function in a network/system may be referred to as a communication device. Taking the communication system 100 shown in FIG1A as an example, the communication device may include a network device 110 and a terminal device 120 having a communication function. The network device 110 and the terminal device 120 may be the specific devices described above and will not be described in detail here. The communication device may also include other devices in the communication system 100, such as a network controller, a mobility management entity, and other network entities, which are not limited in the embodiments of the present application.

It should be understood that the "indication" mentioned in the embodiments of this application can be a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association between A and B.

In the description of the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and being indicated, configuration and being configured, etc.

The "configuration" in the embodiments of the present application may include configuration through at least one of system messages, radio resource control (RRC) signaling and media access control element (MAC CE).

In some embodiments of the present application, "predefined" or "preset" may be implemented by pre-storing corresponding codes, tables, or other methods that can be used to indicate relevant information in a device (e.g., a terminal device or a network device). This application does not limit the specific implementation method. For example, predefined may refer to information defined in a protocol.

In some embodiments of the present application, the "protocol" may refer to a standard protocol in the field of communications, for example, it may include an LTE protocol, an NR protocol, and related protocols used in future communication systems, and this application does not limit this.

Random access (RA) process

The random access process is essential for a terminal device to initially access a network. Random access can be categorized into two types: contention-based random access (CBRA) and contention-free random access (CFRA). The following describes the random access process in detail, using the LTE network as an example.

In LTE, the random access process is mainly triggered by one or more of the following events: establishing a wireless connection when the terminal device initially accesses, such as when the terminal device changes from the RRC_IDLE state to the RRC_CONNECTED state; RRC connection reestablishment process: so that the terminal device can reestablish the wireless connection after the radio link fails; cell handover: the terminal device needs to establish uplink synchronization with the new cell;

In the RRC_CONNECTED state, DL (downlink) data arrives while the UL (uplink) is out of sync. In the RRC_CONNECTED state, UL data arrives while the UL is out of sync or there are no PUCCH resources available to send a scheduling request (SR). SR failure. Synchronization reconfiguration request from RRC.

As shown in FIG2A , the contention-based random access process may include the following steps:

Step S201: The terminal device sends message 1 (message1, Msg1) to the network device.

The terminal device can send Msg1 on the physical random access channel (PRACH), and Msg1 includes a random access preamble (random access preamble).

For example, the terminal device selects a preamble from the preset 64 preambles and determines a random access resource for sending the preamble. The terminal device sends Msg1 including the preamble to the base station on the determined random access resource.

Based on the preamble, the network device can estimate the uplink timing and the grant size required for the terminal device to transmit Msg3.

Step S202: The network device sends message 2 (message2, Msg2) to the terminal device. Msg2 can be called a random access response (RAR).

After the terminal device sends Msg1, it opens a random access response time window (ra-ResponseWindow) and monitors the PDCCH scrambled with the random access radio access network temporary identifier (RA-RNTI) within this window. In LTE, the RA-RNTI is calculated as follows:

RA-RNTI = 1 + t_id + 10 * f_id

Among them, t_id is the first subframe index of PRACH transmission (0≤t_id<10), and f_id is the corresponding subframe of PRACH on this subframe. Frequency domain index (0≤f_id<6), where PRACH resources are numbered in ascending order in the frequency domain.

For enhanced machine-type communication (eMTC), the RA-RNTI is calculated as follows:

RA-RNTI＝1+t_id+10*f_id+60*(SFN_id mod(Wmax/10))

Where t_id is the first subframe index of the PRACH transmission (0 ≤ t_id < 10), f_id is the frequency domain index corresponding to the PRACH in that subframe (0 ≤ f_id < 6), and PRACH resources are numbered sequentially in the frequency domain from low to high. SFN_id is the first SFN index of the PRACH transmission, and Wmax is the maximum PRACH window length supported by eMTC, which is 400 subframes.

For narrowband internet of things (NB-IoT) UEs, the RA-RNTI is calculated as follows:

RA-RNTI＝1+floor(SFN_id/4)+256*carrier_id

Where SFN_id is the first SFN index of the PRACH transmission, and carrier_id is the UL carrier index corresponding to the PRACH transmission. The carrier_id corresponding to the anchor carrier is 0.

For NB-IoT UEs in time division duplexing (TDD) mode, the RA-RNTI is calculated as follows:

RA-RNTI＝1+floor(SFN_id/4)+256*(H-SFN mod 2)

Among them, SFN_id is the first SFN index transmitted by PRACH, and H-SFN is the first H-SFN transmitted by PRACH.

From the above RA-RNTI calculation formula, it can be seen that RA-RNTI is related to the PRACH time-frequency resources used by the UE to send Msg1.

After a terminal successfully receives the RA-RNTI-scrambled physical downlink control channel (PDCCH), it can obtain the physical downlink shared channel (PDSCH) scheduled by the PDCCH, which contains the random access response (RAR). The RAR can contain multiple pieces of information. For example, the subheader of RAR may include a backoff indicator (BI), which can be used to indicate the backoff time for retransmitting MSG1; the random access preamble identification (RAPID) in RAR indicates the preamble index to which the network device responds; the payload in RAR may include a timing advance group (TAG), which can be used to adjust the uplink timing; RAR may also include an uplink grant (UL grant), which is used to indicate the uplink resources for scheduling MSG3; RAR may also include a cell-radio network temporary identifier (C-RNTI). For a terminal device that initially accesses, the terminal device can use the temporary C-RNTI to decode the PDCCH of MSG4.

If the terminal receives a PDCCH scrambled with RA-RNTI and the RAR contains the preamble index sent by itself, the terminal considers that the random access response has been successfully received.

Step S203: The terminal device sends message 3 (message3, Msg3) to the network device. Msg3 can also be called scheduled transmission.

Msg3 is primarily used to inform the network of the event that triggered the PRACH process. For example, if it is an initial access randomization process, the Msg3 will carry the terminal device identifier (UE ID) and the trigger establishment cause; if it is an RRC reestablishment process, it will carry the connected terminal device identifier and the trigger establishment cause.

Step S204: The network device sends message 4 (Msg4) to the terminal device. The Msg4 can be called a contention resolution message.

Msg4 has two functions: one is for contention resolution, and the second is for the network to transmit RRC configuration messages to the terminal. There are two ways to resolve contention conflicts: one is that if the UE carries the C-RNTI in Msg3, Msg4 is scheduled using the PDCCH scrambled with the C-RNTI. The other is that if the UE does not carry the C-RNTI in Msg3, such as for initial access, Msg4 is scheduled using the PDCCH scrambled with the temporary cell-radio network temporary identifier (C-RNTI). The conflict is resolved by the UE receiving the PDSCH in Msg4 and matching the CCCH SDU in the PDSCH.

As shown in FIG2B , the process of non-contention-based random access may include the following steps:

Step S211: The network device sends random access preamble assignment information (RA preamble assignment) to the terminal device.

Step S212: The terminal device sends a random access preamble to the network device. This corresponds to step S201 in FIG2A , and will not be described in detail here.

It should be noted that, for non-contention-based random access, PRACH resources and preamble may be specified by the network device.

Step S213: The network device sends a random access response to the terminal device, which corresponds to step S202 in FIG. 2A and will not be described in detail here.

For non-contention-based random access, the random access process ends after the terminal successfully receives Msg2. For contention-based random access, after the terminal successfully receives Msg2, it needs to continue to transmit Msg3 and receive Msg4.

As can be seen from the random access process described above, the primary purpose of random access is to achieve uplink synchronization between the terminal device and the cell. During random access, the network device determines the time when the terminal device transmits the preamble based on the PRACH time-frequency resources used to receive the preamble from the terminal device. Based on the preamble's transmission and reception times, the network device determines the terminal's initial timing advance (TA) and notifies the terminal device via the RAR.

Early data transmission (EDT)

In traditional LTE systems, if a terminal device in the RRC IDLE state has uplink data to transmit, it must first initiate an RRC connection through a random access process. Only after establishing an RRC connection with the network can it transmit data to the network. To reduce the signaling interaction between the terminal device and the network caused by data transmission and save terminal power consumption, 3GPP introduced the EDT mechanism in R15 for Narrow-Band Internet of Things (NB-IoT) and enhanced Machine-Type Communication (eMTC). This feature allows terminal devices in the RRC IDLE state to transmit uplink data through Msg3 during the random access process. After receiving a successful reception response from the base station, the random access process terminates, and the terminal device continues to remain in the RRC IDLE state without entering the RRC connected state. The base station configures a separate NPRACH (narrowband physical random access channel) resource for EDT. When the amount of uplink data to be transmitted by the terminal device does not exceed the upper limit of the data volume configured by the network, the terminal device can send Msg1 on the separate NPRACH resource of EDT, thereby requesting Msg3grant for EDT from the base station.

Taking the user plane transmission solution as an example, the EDT data transmission process is shown in Figure 3 and includes the following steps:

S301, the terminal device (UE) sends a random access preamble to the base station (eNB);

S302, eNB sends a random access response (Random Access Response) to the UE.

S303, UE sends an RRC connection resumption request (RRC contention resume request) to the eNB.

The RRC Connection resume request carries the resume ID, resume case, authentication token (shortResumeMAC-I) and uplink data (Uplink Data).

S304, eNB sends a UE context resume request (Context resume request) to the Mobility Management Entity (MME).

S305, modify the bearer between MME and serving gateway (S-GW).

S306, MME sends a context resume response (Context resume response) to the UE.

S307: The UE sends uplink data to the S-GW.

S308, the S-GW sends downlink data to the base station.

S309: The eNB and the MME perform a suspension process, and the bearer is modified between the MME and the S-GW.

S310, eNB sends an RRC connection release notification (RRC contention release) to UE.

RRC Connection Release carries the release case, resume ID, next-hop chaining count (NCC) and downlink data.

Preconfigured uplink resources (PUR)

In order to further reduce signaling overhead and terminal power consumption based on EDT, 3GPP introduced the PUR feature for NB-IoT and eMTC in R16. This feature allows the base station to configure PUR resources for the UE while releasing the UE to the RRC IDLE state, so that the UE can use the PUR resources for uplink transmission in the RRC IDLE state without initiating a random access process. In other words, the uplink resources used to send the uplink data can be configured in advance by the network device. For example, after the terminal device enters the idle state, it can determine whether the timing advance TA is valid. If valid, it can use PUR to send data. For example, when TA is invalid, or based on the radio resource control (RRC) signaling sent by the network device, it is decided whether to end the PUR mode.

It should be understood that before executing PUR transmission, the terminal device needs to verify the validity of the TA. The judgment of the validity of the TA is based on one or more of the following conditions: whether the serving cell changes; whether the timing advance timer (TAT) times out; and changes in the reference signal receiving power (RSRP) of the terminal device.

In some implementations, when the network configures the PUR for a terminal device, it may also configure a cyclic shift of the demodulation reference signal (DMRS). This allows up to two UEs to share the same PUSCH resources (using the DMRS to distinguish between different UEs). By skipping the random access procedure, uplink transmission efficiency can be further improved and terminal device energy consumption can be further reduced.

To reduce the uplink and downlink signaling overhead of the random access process (or EDT process), it is possible to skip the transmission of Message 1 and Message 2 (RAR) and directly transmit Message 3. In this case, how the network device should provide the configuration information related to Message 3/Message 4, how the terminal device should trigger this transmission process, and how the terminal device should determine the transmission resources during this transmission process are issues that need to be considered.

In response to one or more of the above problems, the embodiments of the present application are introduced below.

Referring to Figure 4, in step S410, the first terminal device initiates the first process. In the first process, the first terminal device transmits message 3 without transmitting message 1 and/or receiving a random access response message, thereby helping to reduce signaling overhead. It should be noted that the first process may refer to an EDT-related process. Unlike traditional EDT, the first process mentioned in the embodiment of the present application may not transmit message 1 and a random access response message. Therefore, the first process may be called PRACH-less EDT. Alternatively, the first process may refer to a PUR-related process. Unlike traditional PUR, the preconfigured uplink resources used to transmit message 3 in the first process provided in the embodiment of the present application are contention-based (see the description below for details). Therefore, the first process may also be called contention-based preconfigured uplink resources (CB-PUR).

In some implementations, before the first terminal device initiates the first process, the process further includes: the first terminal device receives configuration information sent by the network device, the configuration information can be used to transmit message 3 and/or receive message 4, the configuration information includes public configuration information and/or first Exclusive configuration information of the terminal device.

In an embodiment of the present application, public configuration information is sent to the first terminal device through a network device, so that the first terminal device and other terminal devices can share the public configuration information to transmit message 3 and/or receive message 4, thereby helping to improve the utilization rate of Msg3 uplink resources and/or Msg4 downlink resources, and further helping to improve system capacity.

The embodiments of the present application do not specifically limit the content of the public configuration information and the exclusive configuration information of the first terminal device, and may include any type of information that helps the terminal device transmit message 3 and/or receive message 4. The contents of the public configuration information and the exclusive configuration information are described in detail below with examples.

Public configuration information

In an embodiment of the present application, the public configuration information may include one or more of the following information: first information, used to transmit message 3; second information, used to receive message 4; third information, used by the terminal device to determine the validity of the TA in the RRC non-connected state.

First Information

In some implementations, the first information may include one or more of the following: one or more first resource pools used to transmit message 3; a power control parameter of message 3.

The first resource pool (or each resource pool used to transmit Message 3) may include one or more of the following resources: time domain resources, frequency domain resources, and code domain resources. For example, the first resource pool may include time domain resources and frequency domain resources, and thus the first resource pool may also be referred to as the Msg3 time-frequency resource pool. For another example, the first resource pool may include time domain resources, frequency domain resources, and code domain resources, and thus the first resource pool may also be referred to as the Msg3 time-frequency-code resource pool.

In some implementations, the first resource pool (or each resource pool used to transmit message 3) can correspond to a semi-persistent scheduling (SPS) configuration.

In some implementations, the first resource pool (or each resource pool used to transmit Message 3) is configured for one or more of: enhanced coverage level (CE level); carrier; subcarrier space; transmission block size of Message 3; and number of subcarriers (tone number) used for transmission of Message 3.

For example, the first resource pool (or each resource pool used to transmit message 3) may be configured based on an enhanced coverage level.

For another example, the first resource pool (or each resource pool used to transmit message 3) may be configured based on a carrier. The carrier-based configuration of the first resource pool (or each resource pool used to transmit message 3) may include one or more of the following: configuring the first resource pool for an anchor carrier; or configuring the first resource pool for a non-anchor carrier.

As an example, a Msg3 time-frequency resource pool or a Msg3 time-frequency code resource pool can be configured on the anchor carrier and/or non-anchor carrier, that is, each Msg3 time-frequency resource pool or Msg3 time-frequency code resource pool corresponds to an anchor carrier or a non-anchor carrier.

For another example, the first resource pool (or each resource pool used to transmit Message 3) can be configured based on the subcarrier spacing. As an example, a Msg3 time-frequency resource pool or a Msg3 time-frequency code resource pool can be configured for different subcarrier spacings (such as 15 kHz subcarrier spacing and 3.75 kHz subcarrier spacing), that is, each Msg3 time-frequency resource pool or Msg3 time-frequency code resource pool corresponds to one subcarrier spacing.

For another example, the first resource pool (or each resource pool used to transmit message 3) can be configured based on the transport block size (TBS) of message 3. The configuration based on the transport block size of message 3 may include one of the following: the first resource pool (or each resource pool used to transmit message 3) corresponds to a transport block size of message 3; the first resource pool (or each resource pool used to transmit message 3) corresponds to a maximum value of the transport block size of message 3.

As an example, each Msg3 time-frequency resource pool or Msg3 time-frequency code resource pool corresponds to one Msg3TBS (i.e., the resource size or number is fixed, and the modulation and coding scheme (MCS) is fixed), and different Msg3 time-frequency resource pools or Msg3 time-frequency code resource pools can correspond to different Msg3TBSs.

As another example, each Msg3 time-frequency resource pool or Msg3 time-frequency code resource pool corresponds to a maximum Msg3TBS (i.e., the resource size or number is fixed, and corresponds to a maximum MCS). The first terminal device can adjust the actual Msg3TBS according to the number of bits to be transmitted, but the resource size or number remains unchanged, and the actual MCS is lower than the maximum MCS.

For another example, the first resource pool (or each resource pool used to transmit message 3) can be configured based on the number of subcarriers (single-tone or multi-tone) used for transmitting message 3.

As an example, for a 15 kHz subcarrier spacing, a first resource pool (such as an Msg3 time-frequency resource pool or an Msg3 time-frequency code resource pool) is configured for single-tone and multi-tone, respectively. That is, each Msg3 time-frequency resource pool or Msg3 time-frequency code resource pool corresponding to a subcarrier spacing of 15 kHz corresponds to single-tone or multi-tone. It should be understood that if the Msg3 time-frequency resource pool or the Msg3 time-frequency code resource pool corresponds to multi-tone, then the Msg3 time-frequency resource pool or the Msg3 time-frequency code resource pool corresponds to one tone in multi-tone.

As can be seen from the foregoing description, by introducing a common resource pool, different terminal devices can share the same resources for transmitting message 3 (such as Msg3PUSCH), thereby improving resource utilization and further improving system capacity.

Second information

In some implementations, the second information includes one or more of the following: PDCCH configuration information, PDCCH used for scheduling Receipt of message 4; length of contention resolution timer.

In some implementations, the PDCCH configuration information can be configured for enhanced coverage levels. That is, each PDCCH configuration information corresponds to a CE level.

In some implementations, the duration of the contention resolution timer can be configured for the enhanced coverage level. That is, the duration of each contention resolution timer corresponds to a CE level.

It should be noted that the configuration information of the PDCCH may include the PDCCH search space, the maximum number of PDCCH repetitions, etc., and this application does not impose any specific restrictions on this.

Third Information

The third information includes one or more of the following: the duration of the time alignment timer; the RSRP change threshold.

For example, the duration of the time alignment timer may be used to evaluate the validity of the TA when the terminal device is in the RRC non-connected state.

For example, the RSRP change threshold can also be used to evaluate the effectiveness of the TA when the terminal device is in the RRC non-connected state.

Exclusive configuration information

In some implementations, the exclusive configuration information received by the first terminal device may be carried in the exclusive signaling of the first terminal device, which may be, for example, an RRC message (such as an RRC connection release message, an RRC early data completion message), MAC CE, PDCCH, etc.

The above-mentioned exclusive configuration information includes one or more of the following: fourth information, used to indicate whether the first terminal device is allowed to initiate the first process in the RRC non-connected state; fifth information, used for the first terminal device to determine the validity of the TA in the RRC non-connected state; sixth information, used to indicate the corresponding carrier for the transmission of message 3 and/or the reception of message 4; seventh information, used to indicate the subcarrier spacing corresponding to the transmission of message 3; eighth information, used to indicate the number of subcarriers corresponding to the transmission of message 3; ninth information, used to indicate the power control parameters of message 3.

For example, the fourth information may indicate explicitly or implicitly whether the first terminal device is allowed to initiate the first process in the RRC non-connected state. As an example, the fourth information may include a first field (such as 1 bit) indicating whether the first terminal device is allowed to initiate the first process in the RRC non-connected state, such as 1 for allowing and 0 for not allowing.

As another example, the fourth information may include terminal device-specific configuration information related to the first process, implicitly indicating whether the first terminal device is allowed to initiate the first process in the RRC non-connected state.

In some implementations, the fourth information may be RACH-less EDT or CB-PUR enable/disable indication information.

For another example, the fifth information may include the duration of the time alignment timer, which may be used by the first terminal device to determine the validity of the TA in the RRC non-connected state. It should be understood that the duration of the time alignment timer and the duration of the time alignment timer used for the PUR may be the same configuration parameter or independent configuration parameters.

In some implementations, if the network device configures the duration of the time alignment timer for the first terminal device through terminal device-specific signaling, the first terminal device uses the duration of the time alignment timer configured by the terminal device-specific signaling; otherwise, the first terminal device may use the duration of the time alignment timer configured by public signaling.

For another example, the fifth information may include an RSRP change threshold, which can be used by the first terminal device to determine the validity of the TA in the RRC non-connected state. It should be understood that the RSRP change threshold and the RSRP change threshold for the PUR can be the same configuration parameter or independent configuration parameters. Of course, the RSRP change threshold can also be obtained through the above-mentioned public configuration information.

For example, the sixth information can be used to indicate the carrier used by the first terminal device for transmission and/or reception after the first terminal device initiates the first process, that is, the carrier corresponding to the transmission of message 3 and/or the reception of message 4.

For example, the seventh information may be used to indicate the subcarrier spacing corresponding to the Msg3 transmission after the first terminal device initiates the first process.

For another example, the eighth information may be used to indicate the number of subcarriers (number of tones) corresponding to the Msg3 transmission after the first terminal device initiates the first process.

The above describes in detail the configuration information related to Message 3/Message 4. Next, how the first terminal device determines the transmission resources of Message 3 is described in detail.

In some implementations, the transmission resources of message 3 are determined based on one or more of: configuration information of the network device; the capabilities of the first terminal device; the channel quality of the service cell of the first terminal device; the amount of data to be transmitted by the first terminal device; the coverage enhancement level of the first terminal device; the carrier corresponding to the transmission of message 3; the subcarrier spacing corresponding to the transmission of message 3; the number of subcarriers corresponding to the transmission of message 3; the transmission block size of message 3; and the maximum value of the transmission block size of message 3.

In some implementations, the coverage enhancement level of the first terminal device can be determined based on one or more of the following: the coverage enhancement level of the first terminal device when it last received an RRC connection release message or an RRC early data complete message; and the measurement result of the RSRP of the first terminal device on the serving cell.

As an example, when the first terminal device receives the RRC connection release message or the RRC early data completion message for the last time, the first terminal device is at the first CE level, and the first terminal device uses the first CE level as the current (initial) CE level.

As another example, the first terminal device determines the (initial) CE level based on the RSRP measurement result of the current serving cell, where the RSRP threshold corresponding to each CE level is configured by the network. Of course, the method for determining the CE level during the random access process in the related art can also be reused.

In some implementations, the carrier corresponding to the transmission of message 3 is determined based on a network device configuration, or based on a selection probability factor corresponding to one or more carriers.

For example, the carrier corresponding to the transmission of message 3 can be configured to the first terminal device by the network device through terminal device dedicated signaling (such as RRC connection release message, RRC early data completion).

For another example, the first terminal device may randomly select a carrier from multiple carriers based on a selection probability factor corresponding to one or more carriers.

In some implementations, one or more carriers have respective corresponding selection probability factors; or an anchor carrier among the one or more carriers corresponds to a first selection probability factor, and each non-anchor carrier among the one or more carriers corresponds to a second selection probability factor, and the first selection probability factor is different from the second selection probability factor.

As an example, for each carrier i in the Msg3 transmission resource pool configured with the first procedure (RACH-less EDT or CB-PUR), the network device configures a selection probability factor alpha_i, and the first terminal device randomly selects a carrier from multiple carriers in the Msg3 transmission resource pool configured with the first procedure based on the selection probability factor. Here, i is a positive integer.

As another example, the network device may configure a selection probability factor alpha_anchor for the anchor carrier. The probability of the first terminal device selecting the anchor carrier is alpha_anchor. For non-anchor carriers other than the anchor carrier among the multiple carriers, the probability of the first terminal device selecting each non-anchor carrier is the same, which is (1-alpha_anchor)/N, where N is the number of non-anchor carriers in the Msg3 transmission resource pool configured for the first process (such as RACH-less EDT or CB-PUR) for the CE level, and N is a positive integer. It should be understood that alpha_anchor can reuse the selection probability factor used by the terminal device to select the carrier during the random access process in the related art, or it can be a selection probability factor introduced separately for RACH-less EDT or CB-PUR.

In some implementations, the subcarrier spacing corresponding to the transmission of message 3 is determined based on the network device configuration or based on the capabilities of the first terminal device.

For example, the subcarrier spacing corresponding to the transmission of message 3 can be configured to the first terminal device by the network device through terminal device-specific signaling (such as RRC connection release message, RRC early data completion).

For another example, the first terminal device may also select and determine the subcarrier spacing corresponding to the transmission of message 3 according to its own capabilities.

In some implementations, the number of subcarriers corresponding to the transmission of message 3 is determined based on the network device configuration or based on the capabilities of the first terminal device.

For example, the number of subcarriers corresponding to the transmission of message 3 can be configured to the first terminal device by the network device through terminal device-specific signaling (such as RRC connection release message, RRC early data completion).

For another example, the first terminal device may also select and determine the number of subcarriers corresponding to the transmission of message 3 according to its own capabilities.

In some implementations, the transport block size or the maximum transport block size of Message 3 is based on a network device configuration.

For example, the transport block size of message 3 or the maximum transport block size may be configured by the network device to the first terminal device through terminal device-specific signaling (such as RRC connection release message, RRC early data completion).

In some implementations, the transmission block size or the maximum value of the transmission block size of message 3 is determined by the amount of data to be transmitted by the first terminal device.

For example, the first terminal device may select a (maximum) TBS that is not less than the current amount of data to be transmitted by the terminal device as the (maximum) Msg3TBS according to the current amount of data to be transmitted.

The first process mentioned above can be triggered by the terminal device actively or under certain conditions. The following is a detailed description of possible triggering conditions of the first process.

In some implementations, the first process is triggered based on a first condition, and the first condition includes one or more of the following: the first terminal device receives an RRC connection establishment or RRC connection recovery request; the TA of the first terminal device is valid; the RSRP of the current cell of the first terminal device is greater than or equal to the first threshold; the current cell of the first terminal device belongs to the target cell that allows the first process.

For example, the first terminal device currently has a valid TA, including whether the time alignment timer is running and/or whether the RSRP change of the first terminal device on the serving cell exceeds the threshold value configured by the network device.

For another example, the RSRP of the first terminal device in the current serving cell is greater than or equal to a first RSRP threshold. The first RSRP threshold is configured by the network device, and the network device configures the first RSRP threshold for different CE levels. The first RSRP threshold is different from the RSRP threshold used by the UE to determine the (initial) CE level. It should be understood that, for each CE level, the first RSRP threshold is greater than or equal to the RSRP threshold corresponding to the (initial) CE level.

In some implementations, the target cell satisfies one of the following: the target cell is the cell where the first terminal device is located when receiving the exclusive configuration information; the target cell is a cell that supports the first process; the target cell is the cell indicated when the network device sends the exclusive configuration information to the first terminal device; wherein the exclusive configuration information is used to configure the first process.

That is to say, when the first terminal device initiates the first process (PRACH-less EDT or CB-PUR), there is a cell restriction. The first process can only be initiated (also called using the first process) on a target cell that meets the requirements.

For example, the first terminal device can only use PRACH-less EDT or CB-PUR on the target cell of the terminal device-specific configuration related to the most recent reception of the first process (such as PRACH-less EDT or CB-PUR).

For another example, the first terminal device may use PRACH-less EDT or CB-PUR on any target cell that supports the first process (such as PRACH-less EDT or CB-PUR).

For another example, when providing a first terminal device with a terminal-specific configuration related to PRACH-less EDT or CB-PUR, the network device also indicates whether the first terminal device is permitted to use PRACH-less EDT or CB-PUR in cells other than the current cell. It should be understood that, if permitted, the network device may also provide a list of cells permitted to use PRACH-less EDT or CB-PUR.

It should be noted that, for the first terminal device in the RRC non-connected state (such as the RRC IDLE state), if the first terminal device initiates the first process (such as PRACH-less EDT or CB-PUR), the first terminal device can confirm the transmission resources of Msg3 based on one or more confirmation methods of the Msg3 transmission resources mentioned above.

The following describes in more detail the process of the first terminal device sending the first process with reference to specific examples. It should be noted that the example of FIG5 is merely intended to help those skilled in the art understand the embodiments of the present application, and is not intended to limit the embodiments of the present application to the specific numerical values or specific scenarios illustrated. Based on the example of FIG5 given, those skilled in the art can obviously make various equivalent modifications or changes, and such modifications or changes also fall within the scope of the embodiments of the present application.

Referring to FIG. 5 , in step S510 , a first terminal device receives public configuration information related to a first process (PRACH-free EDT or CB-PUR) broadcast from a network device. This public configuration information corresponds to the public configuration information described above and is not further described here.

In step S520, the first terminal device performs a capability report. The capability report includes reporting to the network device whether the UE has PRACH-free EDT or CB-PUR capabilities (this step is optional).

In step S530, for the first terminal device with PRACH-free EDT or CB-PUR capability, the network device configures UE-specific configuration information related to PRACH-free EDT or CB-PUR to the first terminal device through terminal device-specific signaling.

In step S540, the first terminal device evaluates whether the PRACH-free EDT or CB-PUR triggering criteria are met in the RRC non-connected state (such as the RRC IDLE state).

In step S550, the first terminal device selects the Msg3 resource and sends the Msg3 to the network device;

In step S560, the first terminal device receives a confirmation/contention resolution response from the network device. It should be understood that the first terminal device may return to the RRC IDLE state or enter the RRC CONNECTED state according to the instructions of the network device.

It should be noted that step S520 and step S530 in FIG5 are optional.

The method embodiment of the present application is described in detail above in conjunction with Figures 1 to 5 , and the device embodiment of the present application is described in detail below in conjunction with Figures 6 to 8 . It should be understood that the description of the method embodiment corresponds to the description of the device embodiment, and therefore, for portions not described in detail, reference can be made to the above method embodiment.

FIG6 is a schematic diagram of the structure of a communication device according to an embodiment of the present application. The communication device shown in FIG6 is a first terminal device, and the communication device 600 includes a processing unit 610. The processing unit 610 is configured to initiate a first process; wherein, in the first process, the first terminal device transmits a message 3 without transmitting a message 1 and/or receiving a random access response message.

In some implementations, the communication device further includes: a receiving unit for receiving configuration information sent by a network device before the first terminal device initiates the first process, the configuration information being used to transmit message 3 and/or receive message 4, the configuration information including public configuration information and/or exclusive configuration information of the first terminal device.

In some implementations, the public configuration information includes one or more of the following information: first information, used to transmit message 3; second information, used to receive message 4; and third information, used by the terminal device to determine the validity of the timing advance TA in the non-connected state of the radio resource control RRC.

In some implementations, the first information includes one or more of the following: one or more first resource pools for transmitting message 3; and a power control parameter of message 3.

In some implementations, the first resource pool is configured for one or more of: enhanced coverage level; carrier; subcarrier spacing; transport block size of message 3; and number of subcarriers used for message 3 transmission.

In some implementations, the first resource pool is configured for a carrier, including one or more of the following: the first resource pool is configured for an anchor carrier; the first resource pool is configured for a non-anchor carrier.

In some implementations, the first resource pool is configured for the transmission block size of message 3, including one of the following: the first resource pool corresponds to a transmission block size of message 3; the first resource pool corresponds to a maximum value of the transmission block size of message 3.

In some implementations, the second information includes one or more of the following: configuration information of a physical downlink control channel PDCCH, where the PDCCH is used to schedule reception of message 4; and a duration of a contention resolution timer.

In some implementations, the configuration information of the PDCCH is configured for the enhanced coverage level; and/or the duration of the contention resolution timer is configured for the enhanced coverage level.

In some implementations, the third information includes one or more of the following: a duration of a time alignment timer; and a change threshold of a reference signal received power RSRP.

In some implementations, the exclusive configuration information includes one or more of the following: fourth information, used to indicate whether the first terminal device is allowed to initiate the first process in the RRC non-connected state; fifth information, used for the first terminal device to determine the validity of the TA in the RRC non-connected state; sixth information, used to indicate the corresponding carrier for the transmission of message 3 and/or the reception of message 4; seventh information, used to indicate the subcarrier spacing corresponding to the transmission of message 3; eighth information, used to indicate the number of subcarriers corresponding to the transmission of message 3; and ninth information, used to indicate the power control parameters of message 3.

In some implementations, the fifth information includes one or more of the following: a duration of a time alignment timer; and a RSRP change threshold.

In some implementations, the transmission resources of the message 3 are determined based on one or more of the following: configuration information of the network device; the capabilities of the first terminal device; the channel quality of the service cell of the first terminal device; the amount of data to be transmitted by the first terminal device; the coverage enhancement level of the first terminal device; the carrier corresponding to the transmission of the message 3; the subcarrier spacing corresponding to the transmission of the message 3; the number of subcarriers corresponding to the transmission of the message 3; the transmission block size of the message 3; and the maximum value of the transmission block size of the message 3.

In some implementations, the coverage enhancement level of the first terminal device is determined based on one or more of the following: the coverage enhancement level of the first terminal device when it last received an RRC connection release message or an RRC early data completion message; and the measurement result of the RSRP of the first terminal device on the serving cell.

In some implementations, the carrier corresponding to the transmission of the message 3 is determined based on a network device configuration, or based on a selection probability factor corresponding to one or more carriers.

In some implementations, the one or more carriers have respective corresponding selection probability factors; or an anchor carrier among the one or more carriers corresponds to a first selection probability factor, and each non-anchor carrier among the one or more carriers corresponds to a second selection probability factor, and the first selection probability factor is different from the second selection probability factor.

In some implementations, the subcarrier spacing corresponding to the transmission of the message 3 is determined based on the network device configuration or based on the capabilities of the first terminal device.

In some implementations, the transmission block size or the maximum transmission block size of the message 3 is based on the network device configuration; or, the transmission block size or the maximum transmission block size of the message 3 is determined by the amount of data to be transmitted by the first terminal device.

In some implementations, the first process is triggered based on a first condition, and the first condition includes one or more of the following: the first terminal device receives an RRC connection establishment or RRC connection recovery request; the TA of the first terminal device is valid; the RSRP of the current cell of the first terminal device is greater than or equal to a first threshold; the current cell of the first terminal device belongs to the target cell that allows the first process.

In some implementations, the target cell satisfies one of the following: the target cell is the cell where the first terminal device is located when receiving the exclusive configuration information; the target cell is a cell that supports the first process; the target cell is the cell indicated when the network device sends the exclusive configuration information to the first terminal device; wherein the exclusive configuration information is used to configure the first process.

FIG7 is a schematic diagram of the structure of a communication device according to an embodiment of the present application. The communication device shown in FIG7 is a network device, and the communication device 700 includes a receiving unit 710. The receiving unit 710 is configured to receive a message 3 sent by a first terminal device through a first process; wherein, in the first process, the first terminal device transmits the message 3 without transmitting the message 1 and/or receiving the random access response message.

In some implementations, the communication device further includes: a sending unit for sending configuration information to the first terminal device before the network device receives a message 3 sent by the first terminal device through a first process, the configuration information being used to transmit message 3 and/or receive message 4, the configuration information including public configuration information and/or exclusive configuration information of the first terminal device.

In some implementations, the public configuration information includes one or more of the following information: first information, used to transmit message 3; second information, used to receive message 4; and third information, used by the terminal device to determine the validity of the timing advance TA in the non-connected state of the radio resource control RRC.

In some implementations, the first information includes one or more of the following: one or more first resource pools for transmitting message 3; and a power control parameter of message 3.

In some implementations, the first resource pool is configured for one or more of: enhanced coverage level; carrier; subcarrier spacing; transport block size of message 3; and number of subcarriers used for message 3 transmission.

In some implementations, the first resource pool is configured for a carrier, including one or more of the following: the first resource pool is configured for an anchor carrier; the first resource pool is configured for a non-anchor carrier.

In some implementations, the first resource pool is configured for the transmission block size of message 3, including one of the following: the first resource pool corresponds to a transmission block size of message 3; the first resource pool corresponds to a maximum value of the transmission block size of message 3.

In some implementations, the second information includes one or more of the following: configuration information of a physical downlink control channel PDCCH, where the PDCCH is used to schedule reception of message 4; and a duration of a contention resolution timer.

In some implementations, the configuration information of the PDCCH is configured for the enhanced coverage level; and/or the duration of the contention resolution timer is configured for the enhanced coverage level.

In some implementations, the third information includes one or more of the following: a duration of a time alignment timer; and a change threshold of a reference signal received power RSRP.

In some implementations, the exclusive configuration information includes one or more of the following: fourth information, used to indicate whether the first terminal device is allowed to initiate the first process in the RRC non-connected state; fifth information, used for the first terminal device to determine the validity of the TA in the RRC non-connected state; sixth information, used to indicate the corresponding carrier for the transmission of message 3 and/or the reception of message 4; seventh information, used to indicate the subcarrier spacing corresponding to the transmission of message 3; eighth information, used to indicate the number of subcarriers corresponding to the transmission of message 3; and ninth information, used to indicate the power control parameters of message 3.

In some implementations, the fifth information includes one or more of the following: a duration of a time alignment timer; and a RSRP change threshold.

In some implementations, the transmission resources of the message 3 are determined based on one or more of the following: configuration information of the network device; the capabilities of the first terminal device; the channel quality of the service cell of the first terminal device; the amount of data to be transmitted by the first terminal device; the coverage enhancement level of the first terminal device; the carrier corresponding to the transmission of the message 3; the subcarrier spacing corresponding to the transmission of the message 3; the number of subcarriers corresponding to the transmission of the message 3; the transmission block size of the message 3; and the maximum value of the transmission block size of the message 3.

In some implementations, the coverage enhancement level of the first terminal device is determined based on one or more of the following: the coverage enhancement level of the first terminal device when it last received an RRC connection release message or an RRC early data completion message; and the measurement result of the RSRP of the first terminal device on the serving cell.

In some implementations, the carrier corresponding to the transmission of the message 3 is determined based on a network device configuration, or based on a selection probability factor corresponding to one or more carriers.

In some implementations, the one or more carriers have respective corresponding selection probability factors; or an anchor carrier among the one or more carriers corresponds to a first selection probability factor, and each non-anchor carrier among the one or more carriers corresponds to a second selection probability factor, and the first selection probability factor is different from the second selection probability factor.

In some implementations, the subcarrier spacing corresponding to the transmission of the message 3 is determined based on the network device configuration or based on the capabilities of the first terminal device.

In some implementations, the transmission block size or the maximum transmission block size of the message 3 is based on the network device configuration; or, the transmission block size or the maximum transmission block size of the message 3 is determined by the amount of data to be transmitted by the first terminal device.

In some implementations, the first process is triggered based on a first condition, and the first condition includes one or more of the following: the first terminal device receives an RRC connection establishment or RRC connection recovery request; the TA of the first terminal device is valid; the RSRP of the current cell of the first terminal device is greater than or equal to a first threshold; the current cell of the first terminal device belongs to the target cell that allows the first process.

In some implementations, the target cell satisfies one of the following: the target cell is the cell where the first terminal device is located when receiving the exclusive configuration information; the target cell is a cell that supports the first process; the target cell is the cell indicated when the network device sends the exclusive configuration information to the first terminal device; wherein the exclusive configuration information is used to configure the first process.

FIG8 is a schematic block diagram of a communication device to which embodiments of the present application may be applied. The dashed lines in FIG8 indicate that the unit or module is optional. The device 800 may be used to implement the method described in the above method embodiment. The device 800 may be a chip or a communication device.

The device 800 may include one or more processors 810. The processor 810 may support the device 800 to implement the method described in the above method embodiment. The processor 810 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be another general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc. The general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.

The apparatus 800 may further include one or more memories 820. The memories 820 store programs that can be executed by the processor 810, causing the processor 810 to perform the methods described in the above method embodiments. The memories 820 may be independent of the processor 810 or integrated into the processor 810.

The apparatus 800 may further include a transceiver 830. The processor 810 may communicate with other devices or chips via the transceiver 830. For example, the processor 810 may transmit and receive data with other devices or chips via the transceiver 830.

The present application also provides a computer-readable storage medium for storing a program. The computer-readable storage medium can be applied to a terminal device or network device provided in the present application, and the program enables a computer to execute the method performed by the terminal device or network device in each embodiment of the present application.

The present application also provides a computer program product. The computer program product includes a program. The computer program product can be applied In the terminal device or network device provided in the embodiments of the present application, the program enables the computer to execute the methods performed by the terminal device or network device in each embodiment of the present application.

The present application also provides a computer program that can be applied to a terminal device or network device provided in the present application, and enables a computer to execute the method performed by the terminal device or network device in each embodiment of the present application.

It should be understood that the terms "system" and "network" in this application can be used interchangeably. In addition, the terms used in this application are only used to explain the specific embodiments of this application and are not intended to limit this application. The terms "first", "second", "third", and "fourth" in the specification and claims of this application and the accompanying drawings are used to distinguish different objects rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions.

In the embodiments of this application, the term "indication" may refer to a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" may refer to a direct indication of B, e.g., B can obtain information through A; it may refer to an indirect indication of B, e.g., A indicates C, e.g., B can obtain information through C; or it may refer to an association between A and B.

In the embodiment of the present application, "B corresponding to A" means that B is associated with A and B can be determined based on A. However, it should be understood that determining B based on A does not mean determining B based solely on A, but B can also be determined based on A and/or other information.

In the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and indication, configuration and configuration, etc.

In the embodiments of the present application, "pre-definition" or "pre-configuration" may be implemented by pre-storing corresponding codes, tables, or other methods that can be used to indicate relevant information in a device (e.g., a terminal device and a network device). The present application does not limit the specific implementation method. For example, pre-definition may refer to information defined in a protocol.

In the embodiments of the present application, the “protocol” may refer to a standard protocol in the communications field, for example, it may include an LTE protocol, an NR protocol, and related protocols used in future communication systems, and the present application does not limit this.

In the embodiments of this application, the term "and/or" is simply a description of the association relationship between related objects, indicating that three relationships can exist. For example, A and/or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character "/" in this document generally indicates that the related objects are in an "or" relationship.

In various embodiments of the present application, the size of the serial numbers of the above-mentioned 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 constitute any limitation on the implementation process of the embodiments of the present application.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

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

In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that can be read by a computer or a data storage device such as a server or data center that includes one or more available media integrated. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a digital versatile disc (DVD)), or a semiconductor medium (e.g., a solid state disk (SSD)), etc.

The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims (86)

A wireless communication method, comprising: The first terminal device initiates a first process; In the first process, the first terminal device transmits message 3 without transmitting message 1 and/or receiving a random access response message. The method according to claim 1, characterized in that before the first terminal device initiates the first process, the method further comprises: The first terminal device receives configuration information sent by the network device, where the configuration information is used to transmit message 3 and/or receive message 4, and the configuration information includes public configuration information and/or exclusive configuration information of the first terminal device. The method according to claim 2, wherein the public configuration information includes one or more of the following information: First information, used to transmit message 3; Second information, used to receive message 4; The third information is used by the terminal device to determine the validity of the timing advance TA in the non-connected state of the radio resource control RRC. The method according to claim 3, wherein the first information includes one or more of the following: One or more first resource pools, used for transmitting message 3; Power control parameters for message 3. The method according to claim 4, wherein the first resource pool is configured for one or more of the following: Enhanced coverage levels; carrier wave; subcarrier spacing; The transport block size of message 3; The number of subcarriers used for Message 3 transmission. The method according to claim 5, wherein the first resource pool is configured for a carrier, including one or more of the following: The first resource pool is configured for an anchor carrier; The first resource pool is configured for a non-anchor carrier. The method according to claim 5 or 6, wherein the first resource pool is configured for the transmission block size of message 3, including one of the following: The first resource pool corresponds to a transmission block size of message 3; The first resource pool corresponds to a maximum value of the transmission block size of message 3. The method according to any one of claims 3 to 7, wherein the second information includes one or more of the following: Configuration information of a physical downlink control channel (PDCCH), where the PDCCH is used to schedule reception of message 4; The duration of the contention resolution timer. The method according to claim 8, characterized in that: The PDCCH configuration information is configured for an enhanced coverage level; and/or, The duration of the contention resolution timer is configured according to the enhanced coverage level. The method according to any one of claims 3 to 9, wherein the third information includes one or more of the following: The duration of the time alignment timer; Reference signal received power (RSRP) change threshold. The method according to any one of claims 2 to 10, wherein the dedicated configuration information includes one or more of the following: Fourth information, used to indicate whether the first terminal device is allowed to initiate the first process in the RRC non-connected state; Fifth information is used by the first terminal device to determine the validity of the TA in the RRC non-connected state; Sixth information, used to indicate the carrier corresponding to the transmission of message 3 and/or the reception of message 4; The seventh information is used to indicate the subcarrier spacing corresponding to the transmission of message 3; The eighth information is used to indicate the number of subcarriers corresponding to the transmission of message 3; The ninth information is used to indicate the power control parameters of message 3. The method according to claim 11, wherein the fifth information includes one or more of the following: The duration of the time alignment timer; RSRP change threshold. The method according to any one of claims 1 to 12, wherein the transmission resource of the message 3 is determined based on one or more of the following: Configuration information of network devices; capabilities of the first terminal device; channel quality of a serving cell of the first terminal device; the amount of data to be transmitted by the first terminal device; the coverage enhancement level of the first terminal device; The carrier corresponding to the transmission of the message 3; The subcarrier spacing corresponding to the transmission of the message 3; The number of subcarriers corresponding to the transmission of message 3; The transport block size of message 3; The maximum value of the transport block size of message 3. The method according to claim 13, wherein the coverage enhancement level of the first terminal device is determined based on one or more of the following: The coverage enhancement level at which the first terminal device was located when the first terminal device last received an RRC connection release message or an RRC early data completion message; The RSRP measurement result of the first terminal device on the serving cell. The method according to claim 13 or 14 is characterized in that the carrier corresponding to the transmission of message 3 is determined based on the network device configuration, or based on the selection probability factors corresponding to one or more carriers. The method according to claim 15, characterized in that: The one or more carriers have respective corresponding selection probability factors; or An anchor carrier among the one or more carriers corresponds to a first selection probability factor, and each non-anchor carrier among the one or more carriers corresponds to a second selection probability factor, where the first selection probability factor is different from the second selection probability factor. The method according to any one of claims 13 to 16 is characterized in that the subcarrier spacing corresponding to the transmission of the message 3 is determined based on the network device configuration or based on the capability of the first terminal device. The method according to any one of claims 13 to 17, characterized in that: The transport block size or the maximum transport block size of the message 3 is based on the network device configuration; or, The transmission block size of the message 3 or the maximum value of the transmission block size is determined by the amount of data to be transmitted by the first terminal device. The method according to any one of claims 1 to 18, wherein the first process is triggered based on a first condition, and the first condition includes one or more of the following: The first terminal device receives an RRC connection establishment or RRC connection recovery request; The TA of the first terminal device is valid; The RSRP of the current cell of the first terminal device is greater than or equal to a first threshold; The current cell of the first terminal device belongs to the target cell that allows the first process to be performed. The method according to claim 19, wherein the target cell satisfies one of the following: The target cell is the cell where the first terminal device is located when receiving the exclusive configuration information; The target cell is a cell that supports the first process; The target cell is the cell indicated by the network device when sending the exclusive configuration information to the first terminal device; The exclusive configuration information is used to configure the first process. A wireless communication method, comprising: The network device receives a message 3 sent by the first terminal device through the first process; In the first process, the first terminal device transmits message 3 without transmitting message 1 and/or receiving a random access response message. The method according to claim 21, characterized in that before the network device receives the message 3 sent by the first terminal device through the first process, the method further comprises: The network device sends configuration information to the first terminal device, where the configuration information is used to transmit message 3 and/or receive message 4, and the configuration information includes public configuration information and/or exclusive configuration information of the first terminal device. The method according to claim 22, wherein the public configuration information includes one or more of the following information: First information, used to transmit message 3; Second information, for receiving message 4; The third information is used by the terminal device to determine the validity of the timing advance TA in the non-connected state of the radio resource control RRC. The method according to claim 23, wherein the first information includes one or more of the following: One or more first resource pools, used for transmitting message 3; Power control parameters for message 3. The method according to claim 24, wherein the first resource pool is configured for one or more of the following: Enhanced coverage levels; carrier wave; subcarrier spacing; The transport block size of message 3; The number of subcarriers used for Message 3 transmission. The method according to claim 25, wherein the first resource pool is configured for a carrier, including one or more of the following: The first resource pool is configured for an anchor carrier; The first resource pool is configured for a non-anchor carrier. The method according to claim 25 or 26, wherein the first resource pool is configured for the transmission block size of message 3, including one of the following: The first resource pool corresponds to a transmission block size of message 3; The first resource pool corresponds to a maximum value of the transmission block size of message 3. The method according to any one of claims 23 to 27, wherein the second information includes one or more of the following: Configuration information of a physical downlink control channel (PDCCH), where the PDCCH is used to schedule reception of message 4; The length of the contention resolution timer. The method according to claim 28, characterized in that: The PDCCH configuration information is configured for an enhanced coverage level; and/or, The duration of the contention resolution timer is configured according to the enhanced coverage level. The method according to any one of claims 23 to 29, wherein the third information includes one or more of the following: The duration of the time alignment timer; Reference signal received power (RSRP) change threshold. The method according to any one of claims 22 to 30, wherein the dedicated configuration information includes one or more of the following: Fourth information, used to indicate whether the first terminal device is allowed to initiate the first process in the RRC non-connected state; Fifth information is used by the first terminal device to determine the validity of the TA in the RRC non-connected state; Sixth information, used to indicate the carrier corresponding to the transmission of message 3 and/or the reception of message 4; The seventh information is used to indicate the subcarrier spacing corresponding to the transmission of message 3; The eighth information is used to indicate the number of subcarriers corresponding to the transmission of message 3; The ninth information is used to indicate the power control parameters of message 3. The method according to claim 31, wherein the fifth information includes one or more of the following: The duration of the time alignment timer; RSRP change threshold. The method according to any one of claims 21 to 32, wherein the transmission resource of the message 3 is determined based on one or more of the following: Configuration information of network devices; capabilities of the first terminal device; channel quality of a serving cell of the first terminal device; the amount of data to be transmitted by the first terminal device; the coverage enhancement level of the first terminal device; The carrier corresponding to the transmission of the message 3; The subcarrier spacing corresponding to the transmission of the message 3; The number of subcarriers corresponding to the transmission of message 3; The transport block size of message 3; The maximum value of the transport block size of message 3. The method according to claim 33, wherein the coverage enhancement level of the first terminal device is based on the following Determine one or more of: The coverage enhancement level at which the first terminal device was located when the first terminal device last received an RRC connection release message or an RRC early data completion message; The RSRP measurement result of the first terminal device on the serving cell. The method according to claim 33 or 34 is characterized in that the carrier corresponding to the transmission of message 3 is determined based on the network equipment configuration, or based on the selection probability factor corresponding to one or more carriers. The method according to claim 35, characterized in that: The one or more carriers have respective corresponding selection probability factors; or An anchor carrier among the one or more carriers corresponds to a first selection probability factor, and each non-anchor carrier among the one or more carriers corresponds to a second selection probability factor, where the first selection probability factor is different from the second selection probability factor. The method according to any one of claims 33 to 36 is characterized in that the subcarrier spacing corresponding to the transmission of the message 3 is determined based on the network device configuration or based on the capability of the first terminal device. The method according to any one of claims 33 to 37, characterized in that: The transport block size or the maximum transport block size of the message 3 is based on the network device configuration; or, The transmission block size of the message 3 or the maximum value of the transmission block size is determined by the amount of data to be transmitted by the first terminal device. The method according to any one of claims 21 to 38, wherein the first process is triggered based on a first condition, and the first condition includes one or more of the following: The first terminal device receives an RRC connection establishment or RRC connection recovery request; The TA of the first terminal device is valid; The RSRP of the current cell of the first terminal device is greater than or equal to a first threshold; The current cell of the first terminal device belongs to the target cell that allows the first process to be performed. The method according to claim 39, wherein the target cell satisfies one of the following: The target cell is the cell where the first terminal device is located when receiving the exclusive configuration information; The target cell is a cell that supports the first process; The target cell is the cell indicated by the network device when sending the exclusive configuration information to the first terminal device; The exclusive configuration information is used to configure the first process. A communication device, characterized in that the communication device is a first terminal device, and the communication device includes: a processing unit, configured to initiate a first process; In the first process, the first terminal device transmits message 3 without transmitting message 1 and/or receiving a random access response message. The communication device according to claim 41, characterized in that the communication device further comprises: A receiving unit is used to receive configuration information sent by a network device before the first terminal device initiates the first process, wherein the configuration information is used to transmit message 3 and/or receive message 4, and the configuration information includes public configuration information and/or exclusive configuration information of the first terminal device. The communication device according to claim 42, wherein the public configuration information includes one or more of the following information: First information, used to transmit message 3; Second information, for receiving message 4; The third information is used by the terminal device to determine the validity of the timing advance TA in the non-connected state of the radio resource control RRC. The communication device according to claim 43, wherein the first information includes one or more of the following: One or more first resource pools, used for transmitting message 3; Power control parameters for message 3. The communication device according to claim 44, wherein the first resource pool is configured for one or more of the following: Enhanced coverage levels; carrier wave; subcarrier spacing; The transport block size of message 3; The number of subcarriers used for Message 3 transmission. The communication device according to claim 45, wherein the first resource pool is configured for a carrier, including one or more of the following: The first resource pool is configured for an anchor carrier; The first resource pool is configured for a non-anchor carrier. The communication device according to claim 45 or 46, wherein the first resource pool is configured for the transport block size of message 3, including one of the following: The first resource pool corresponds to a transmission block size of message 3; The first resource pool corresponds to a maximum value of the transmission block size of message 3. The communication device according to any one of claims 43 to 47, wherein the second information includes one or more of the following: Configuration information of a physical downlink control channel (PDCCH), where the PDCCH is used to schedule reception of message 4; The length of the contention resolution timer. The communication device according to claim 48, characterized in that: The PDCCH configuration information is configured for an enhanced coverage level; and/or, The duration of the contention resolution timer is configured according to the enhanced coverage level. The communication device according to any one of claims 43 to 49, wherein the third information includes one or more of the following: The duration of the time alignment timer; Reference signal received power (RSRP) change threshold. The communication device according to any one of claims 42 to 50, wherein the dedicated configuration information includes one or more of the following: Fourth information, used to indicate whether the first terminal device is allowed to initiate the first process in the RRC non-connected state; Fifth information is used by the first terminal device to determine the validity of the TA in the RRC non-connected state; Sixth information, used to indicate the carrier corresponding to the transmission of message 3 and/or the reception of message 4; The seventh information is used to indicate the subcarrier spacing corresponding to the transmission of message 3; The eighth information is used to indicate the number of subcarriers corresponding to the transmission of message 3; The ninth information is used to indicate the power control parameters of message 3. The communication device according to claim 51, wherein the fifth information includes one or more of the following: The duration of the time alignment timer; RSRP change threshold. The communication device according to any one of claims 41 to 52, wherein the transmission resource of the message 3 is determined based on one or more of the following: Configuration information of network devices; capabilities of the first terminal device; channel quality of a serving cell of the first terminal device; the amount of data to be transmitted by the first terminal device; the coverage enhancement level of the first terminal device; The carrier corresponding to the transmission of the message 3; The subcarrier spacing corresponding to the transmission of the message 3; The number of subcarriers corresponding to the transmission of message 3; The transport block size of message 3; The maximum value of the transport block size of message 3. The communication device according to claim 53, wherein the coverage enhancement level of the first terminal device is determined based on one or more of the following: The coverage enhancement level at which the first terminal device was located when the first terminal device last received an RRC connection release message or an RRC early data completion message; The RSRP measurement result of the first terminal device on the serving cell. The communication device according to claim 53 or 54 is characterized in that the carrier corresponding to the transmission of message 3 is determined based on the network device configuration, or based on the selection probability factor corresponding to one or more carriers. The communication device according to claim 55, characterized in that: The one or more carriers have respective corresponding selection probability factors; or An anchor carrier among the one or more carriers corresponds to a first selection probability factor, and each non-anchor carrier among the one or more carriers corresponds to a second selection probability factor, where the first selection probability factor is different from the second selection probability factor. The communication device according to any one of claims 53 to 56 is characterized in that the subcarrier spacing corresponding to the transmission of the message 3 is determined based on the network device configuration or based on the capability of the first terminal device. The communication device according to any one of claims 53 to 57, characterized in that: The transport block size or the maximum transport block size of the message 3 is based on the network device configuration; or, The transmission block size of the message 3 or the maximum value of the transmission block size is determined by the amount of data to be transmitted by the first terminal device. The communication device according to any one of claims 41 to 58, wherein the first process is triggered based on a first condition, and the first condition includes one or more of the following: The first terminal device receives an RRC connection establishment or RRC connection recovery request; The TA of the first terminal device is valid; The RSRP of the current cell of the first terminal device is greater than or equal to a first threshold; The current cell of the first terminal device belongs to the target cell that allows the first process to be performed. The communication device according to claim 59, wherein the target cell satisfies one of the following: The target cell is the cell where the first terminal device is located when receiving the exclusive configuration information; The target cell is a cell that supports the first process; The target cell is the cell indicated by the network device when sending the exclusive configuration information to the first terminal device; The exclusive configuration information is used to configure the first process. A communication device, characterized in that the communication device is a network device, and the communication device includes: A receiving unit, configured to receive a message 3 sent by the first terminal device through the first process; In the first process, the first terminal device transmits message 3 without transmitting message 1 and/or receiving a random access response message. The communication device according to claim 61, characterized in that the communication device further comprises: A sending unit is used to send configuration information to the first terminal device before the network device receives the message 3 sent by the first terminal device through the first process, and the configuration information is used to transmit message 3 and/or receive message 4. The configuration information includes public configuration information and/or exclusive configuration information of the first terminal device. The communication device according to claim 62, wherein the public configuration information includes one or more of the following information: First information, used to transmit message 3; Second information, used to receive message 4; The third information is used by the terminal device to determine the validity of the timing advance TA in the non-connected state of the radio resource control RRC. The communication device according to claim 63, wherein the first information includes one or more of the following: One or more first resource pools, used for transmitting message 3; Power control parameters for message 3. The communication device according to claim 64, wherein the first resource pool is configured for one or more of the following: Enhanced coverage levels; carrier wave; subcarrier spacing; The transport block size of message 3; The number of subcarriers used for Message 3 transmission. The communication device according to claim 65, wherein the first resource pool is configured for a carrier, including one or more of the following: The first resource pool is configured for an anchor carrier; The first resource pool is configured for a non-anchor carrier. The communication device according to claim 65 or 66, wherein the first resource pool is configured for a transport block size of message 3, including one of the following: The first resource pool corresponds to a transmission block size of message 3; The first resource pool corresponds to a maximum value of the transmission block size of message 3. The communication device according to any one of claims 63 to 67, wherein the second information includes one or more of the following: Configuration information of a physical downlink control channel (PDCCH), where the PDCCH is used to schedule reception of message 4; The duration of the contention resolution timer. The communication device according to claim 68, characterized in that: The PDCCH configuration information is configured for an enhanced coverage level; and/or, The duration of the contention resolution timer is configured according to the enhanced coverage level. The communication device according to any one of claims 63 to 69, wherein the third information includes one or more of the following: The duration of the time alignment timer; Reference signal received power (RSRP) change threshold. The communication device according to any one of claims 62 to 70, wherein the dedicated configuration information includes one or more of the following: Fourth information, used to indicate whether the first terminal device is allowed to initiate the first process in the RRC non-connected state; Fifth information is used by the first terminal device to determine the validity of the TA in the RRC non-connected state; Sixth information, used to indicate the carrier corresponding to the transmission of message 3 and/or the reception of message 4; The seventh information is used to indicate the subcarrier spacing corresponding to the transmission of message 3; The eighth information is used to indicate the number of subcarriers corresponding to the transmission of message 3; The ninth information is used to indicate the power control parameters of message 3. The communication device according to claim 71, wherein the fifth information includes one or more of the following: The duration of the time alignment timer; RSRP change threshold. The communication device according to any one of claims 61 to 72, wherein the transmission resource of the message 3 is determined based on one or more of the following: Configuration information of network devices; capabilities of the first terminal device; channel quality of a serving cell of the first terminal device; the amount of data to be transmitted by the first terminal device; the coverage enhancement level of the first terminal device; The carrier corresponding to the transmission of the message 3; The subcarrier spacing corresponding to the transmission of the message 3; The number of subcarriers corresponding to the transmission of message 3; The transport block size of message 3; The maximum value of the transport block size of message 3. The communication device according to claim 73, wherein the coverage enhancement level of the first terminal device is determined based on one or more of the following: The coverage enhancement level at which the first terminal device was located when the first terminal device last received an RRC connection release message or an RRC early data completion message; The RSRP measurement result of the first terminal device on the serving cell. The communication device according to claim 73 or 74 is characterized in that the carrier corresponding to the transmission of message 3 is determined based on the network device configuration, or based on the selection probability factor corresponding to one or more carriers. The communication device according to claim 75, characterized in that: The one or more carriers have respective corresponding selection probability factors; or An anchor carrier among the one or more carriers corresponds to a first selection probability factor, and each non-anchor carrier among the one or more carriers corresponds to a second selection probability factor, where the first selection probability factor is different from the second selection probability factor. The communication device according to any one of claims 73 to 76 is characterized in that the subcarrier spacing corresponding to the transmission of the message 3 is determined based on the network device configuration or based on the capability of the first terminal device. The communication device according to any one of claims 73 to 77, characterized in that: The transport block size or the maximum transport block size of the message 3 is based on the network device configuration; or, The transmission block size of the message 3 or the maximum value of the transmission block size is determined by the amount of data to be transmitted by the first terminal device. The communication device according to any one of claims 61 to 78, wherein the first process is triggered based on a first condition, and the first condition includes one or more of the following: The first terminal device receives an RRC connection establishment or RRC connection recovery request; The TA of the first terminal device is valid; The RSRP of the current cell of the first terminal device is greater than or equal to a first threshold; The current cell of the first terminal device belongs to the target cell that allows the first process to be performed. The communication device according to claim 79, wherein the target cell satisfies one of the following: The target cell is the cell where the first terminal device is located when receiving the exclusive configuration information; The target cell is a cell that supports the first process; The target cell is the cell indicated by the network device when sending the exclusive configuration information to the first terminal device; The exclusive configuration information is used to configure the first process. A communication device, characterized by comprising a processor, configured to call a program from a memory to execute the method according to any one of claims 1-20 or 21-40. A device, characterized in that it comprises a processor, configured to call a program from a memory to execute the method according to any one of claims 1-20 or 21-40. A chip, characterized in that it includes a processor for calling a program from a memory so that a device equipped with the chip executes the method according to any one of claims 1-20 or 21-40. A computer-readable storage medium, characterized in that a program is stored thereon, wherein the program enables a computer to execute the method according to any one of claims 1 to 20 or 21 to 40. A computer program product, characterized in that it comprises a program, wherein the program enables a computer to execute the method according to any one of claims 1 to 20 or 21 to 40. A computer program, characterized in that the computer program enables a computer to execute the method according to any one of claims 1 to 20 or 21 to 40.