WO2025118135A1 - Wireless communication method and communication device - Google Patents

Abstract

Provided are a wireless communication method and a communication device. The method comprises: a first terminal device sends a preamble to a target device; the first terminal device receives a first index sent by the target device, the first index being used for indicating the preamble received by the target device; in response to the first index being identical to an index of the preamble, the first terminal device sends a first terminal device identifier to the target device; and the first terminal device receives first information sent by the target device, the first information comprising the terminal device identifier received by the target device, and the target device comprising a network device and/or a second terminal device. In embodiments of the present application, the first terminal device can perform a random access procedure on the basis of the first terminal device identifier. Compared with a conventional random access procedure, a reduction of power consumption of the terminal device in the random access procedure is facilitated.

Description

Wireless communication method and communication device Technical Field

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

Background Art

The traditional random access process is too complicated and may cause the terminal device to consume more power. In some scenarios, in order to reduce the power consumption of the terminal device, low-capability terminal devices (for example, the electronic tags mentioned above) are introduced. Compared with traditional terminal devices, the communication methods supported by this type of terminal device may be simpler. At this time, if this type of terminal device still uses the traditional random access method to access the network device, the power consumption of the terminal device may increase.

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 method for wireless communication is provided, comprising: a first terminal device sends a preamble code to a target device; the first terminal device receives a first index sent by the target device, the first index being used to indicate the preamble code received by the target device; in response to the first index being the same as the index of the preamble code, the first terminal device sends a first terminal device identifier to the target device; the first terminal device receives first information sent by the target device, the first information including the terminal device identifier received by the target device; wherein the target device includes a network device and/or a second terminal device.

In a second aspect, a random access method is provided, comprising: a target device receives a preamble code sent by a first terminal device; the target device sends a first index to the first terminal device, the first index being used to indicate the preamble code received by a network device; the target device receives a terminal device identification sent by the terminal device; the target device sends first information to the terminal device, the first information including the terminal device identification received by the target device; wherein the target device includes a network device and/or a second terminal device.

According to a third aspect, a terminal device is provided, which is a first terminal device, comprising: a sending unit, configured to send a preamble code to a target device; a receiving unit, configured to receive a first index sent by the target device, wherein the first index is used to indicate the preamble code received by the target device; the sending unit, configured to send a first terminal device identifier to the target device in response to the first index being the same as the index of the preamble code; the receiving unit, configured to receive first information sent by the target device, wherein the first information includes the terminal device identifier received by the target device; wherein the target device includes a network device and/or a second terminal device.

In a fourth aspect, a communication device is provided, which is a target device, comprising: a receiving unit, used to receive a preamble code sent by a first terminal device; a sending unit, used to send a first index to the first terminal device, the first index being used to indicate the preamble code received by a network device; the receiving unit, used to receive a terminal device identifier sent by the terminal device; the sending unit, used to send first information to the terminal device, the first information including the terminal device identifier received by the target device; wherein the target device includes a network device and/or a second terminal device.

In a fifth aspect, a terminal device is provided, comprising a processor, a memory and a communication interface, wherein the memory is used to store one or more computer programs, and the processor is used to call the computer programs in the memory so that the terminal device executes part or all of the steps in the method of the first aspect.

In a sixth aspect, a communication device is provided, comprising a processor, a memory, and a transceiver, wherein the memory is used to store one or more computer programs, and the processor is used to call the computer programs in the memory so that the communication device executes part or all of the steps in the method of the second aspect.

In a seventh aspect, an embodiment of the present application provides a communication system, which includes the above-mentioned terminal device and/or communication device. In another possible design, the system may also include other devices that interact with the terminal device or network device in the solution provided by the embodiment of the present application.

In an eighth aspect, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program, and the computer program enables a communication device (for example, a terminal device or a communication device) to perform some or all of the steps in the methods of the above aspects.

In a ninth aspect, an embodiment of the present application provides a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program, and the computer program is operable to enable a communication device (e.g., a terminal device or a communication device) to perform some or all of the steps in the above-mentioned various aspects of the method. In some implementations, the computer program product can be a software installation package.

In the tenth aspect, an embodiment of the present application provides a chip, which includes a memory and a processor. The processor can call and run a computer program from the memory to implement some or all of the steps described in the methods of the above aspects.

In the embodiment of the present application, the first terminal device can perform a random access process based on the first terminal device identifier. For the random access process, it helps to reduce the power consumption of terminal devices during random access.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a wireless communication system 100 to which an embodiment of the present application is applied.

FIG. 2A is a schematic diagram of a conventional four-step random access process.

FIG. 2B is a flow chart of a non-contention random access process.

FIG. 2C is a schematic diagram of a conventional two-step random access process.

FIG. 2D is a flow chart of another conventional two-step random access process.

FIG3 is a schematic diagram of an A-IoT communication system applicable to an embodiment of the present application.

4A to 4D are schematic diagrams of four topological network structures of an A-IoT communication system applicable to embodiments of the present application.

FIG5 is a schematic diagram of a receiving process of an RF receiver to which an embodiment of the present application is applicable.

FIG6 is a schematic diagram of a receiving process of an intermediate frequency receiver applicable to an embodiment of the present application.

Figure 7 shows a schematic flow chart of the initial access process of radio frequency identification (RFID).

FIG8 is a schematic flowchart of a wireless communication method according to an embodiment of the present application.

FIG. 9 is a schematic diagram of a method for indicating a second time domain resource in an embodiment of the present application.

FIG10 is a schematic diagram of time domain resources for sending a preamble code and time domain resources for sending a terminal device identifier in an embodiment of the present application.

FIG. 11 is a schematic diagram illustrating a method for indicating a first time domain resource in an embodiment of the present application.

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

FIG13 is a schematic flowchart of a random access method according to another embodiment of the present application.

FIG14 is a schematic flowchart of a random access method according to another embodiment of the present application.

FIG15 is a schematic flowchart of a random access method according to another embodiment of the present application.

FIG. 16 is a schematic diagram of a terminal device according to an embodiment of the present application.

FIG. 17 is a schematic diagram of a communication device according to an embodiment of the present application.

FIG. 18 is a schematic structural diagram of a communication device according to an embodiment of the present application.

DETAILED DESCRIPTION

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

FIG1 is a wireless communication system 100 used in an embodiment of the present application. The wireless communication system 100 may include a network device 110 and a terminal device 120. The network device 110 may be a device that communicates with the terminal device 120. The network device 110 may provide communication coverage for a specific geographical area, and may communicate with the terminal device 120 located in the coverage area.

FIG1 exemplarily shows a network device and two terminals. Optionally, the wireless 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.

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

It should be understood that the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: the fifth generation (5th generation, 5G) system or new radio (new radio, NR), long term evolution (long term evolution, LTE) system, LTE frequency division duplex (frequency division duplex, FDD) system, LTE time division duplex (time division duplex, TDD), etc. The technical solutions provided by the present application can also be applied to future communication systems, such as the sixth generation mobile communication system, satellite communication system, etc.

The terminal device in the embodiment of the present application 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 device, user agent or user device. The terminal device in the embodiment of the present application 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 with wireless connection function, a vehicle-mounted device, etc. The terminal device in the embodiment of the present application can be a mobile phone, a tablet computer, a laptop, 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 grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, etc. Optionally, the UE can be used to act as a base station. For example, the UE can act as a scheduling entity that provides sidelink signals between UEs in V2X or D2D, etc. For example, a cellular phone and a car communicate with each other using sidelink signals. The cellular phone and the smart home device communicate with each other without relaying the communication signal through the base station.

The network device in the embodiment of the present application may be a device for communicating with a terminal device, and the network device may also be referred to as an access network device or a wireless access network device. For example, the network device may be a base station. The network device in the embodiment of the present application may refer to a device that connects a terminal device to a wireless access network. A radio access network (RAN) node (or device) of a wireless network. A base station can broadly cover various names as follows, or be replaced with the following names, such as: NodeB, evolved NodeB (eNB), next generation NodeB (gNB), relay station, access point, transmitting 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), transmitting node, transceiver node, base band unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A 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 may also refer to a communication module, modem or chip used to be set in the aforementioned device or apparatus. The base station may also be a mobile switching center and a device to device D2D, vehicle-to-everything (V2X), machine-to-machine (M2M) communication device that performs the base station function, a network side device in a 6G network, and a device that performs the base station function in a future communication system. The base station may 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 includes a CU and a DU. The gNB may also include an AAU.

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

It should be understood that all or part of the functions of the communication device in the present application may also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (eg, a cloud platform).

Random access process

In some protocols, two random access procedures are specified: 2-step random access channel (2-step RACH) and 4-step random access channel (4-step RACH). Among them, the 4-step RACH process is introduced in the LTE system and is also used in the NR system. The following introduces the traditional 4-step random access process in conjunction with Figure 2A. Usually, before initiating the RACH process, the terminal device can first obtain the PRACH resource configuration from the system message or dedicated signaling. Afterwards, steps S210 to S240 can be executed.

In step S210, the terminal device sends a preamble to the network device. The preamble may be referred to as message 1 (Msg1) in the MAC layer protocol.

Usually, after sending the preamble, you can wait for message 2 (Msg2) fed back by the network device in the reception window. The start time and end time of the reception window are set according to the configuration parameters. From the perspective of the network device, the network device has the ability to distinguish preambles received in different time-frequency domains, or different preambles in the same time-frequency domain. However, the network device cannot distinguish the same preamble sent by multiple terminal devices received in the same time-frequency domain, in which case an access conflict will occur.

In step S220, the network device sends message 2 to the terminal device.

Typically, the message 2 may be a group message, that is, the message 2 may include a random access response (RAR) message to multiple terminal devices. The addressing information of the message 2 is contained in a group identifier called a random access network temporary identifier (RA-RNTI), which is used to identify the time domain resource information, frequency domain resource information and carrier type information of the received preamble code, wherein the carrier type information is used to indicate whether the carrier of the preamble code is a SUL carrier or a NUL carrier.

That is, a message 2 may include the RAR corresponding to the preamble received from the same carrier and the same time-frequency point. The RAR IE sent to each terminal device may include the temporary identifier (temporary cell-radio network temporary identifier, T_C_RNTI) configured by the network device for the terminal device, the time advance (for uplink synchronization), the uplink grant (UL-GRANT) for sending message 3 (message3, Msg3), and the index of the preamble received by the network device.

In some implementations, message 2 may also include a backoff parameter to mitigate conflicts between preambles. At this time, if the terminal device decides to send the preamble again, a random time will be generated based on the backoff parameter, so that the sending time of the preamble sent again is at least later than the generated random time.

In step S230, if the terminal device confirms that the network device has received the preamble code sent by itself, the terminal device sends message 3, also known as "scheduled transmission", to the network device based on UL-GRANT. Message 3 includes the terminal device identification (also known as the terminal device ID).

Usually, the terminal device can determine whether the network device has received the preamble code it sent based on the RA-RNTI and the preamble code index in the RAR. If the terminal device confirms that the network device has received the preamble code it sent, the terminal device sends message 3 based on UL-GRANT. At least the terminal identifier (terminal device ID) is included. Message 3 can be addressed using T_C_RNTI on the physical layer.

Afterwards, the terminal device may start a timer and, during the timer operation, detect the downlink control channel PDCCH carrying message 4. If multiple terminal devices collide in step S210, then the conflict will continue to be sent in step S230, because multiple terminal devices will send message 3 based on the same UL-GRANT, but the terminal identifiers contained in the MAC CE of message 3 are different.

In step S240, if the network device correctly decodes message 3, the network device may send message 4 (message 4, Msg4) to the terminal device. This message is also called "contention resolution".

Typically, this message 4 is addressed using the T_C_RNTI received in message 3, and the MAC CE therein includes the terminal device identifier included in message 3 and a newly allocated C-RNTI.

If multiple terminal devices send message 3 on the same UL GRANT, the network device may be able to correctly decode one of them or not (for example, when the interference level between the messages 3 sent by multiple terminal devices is similar). Therefore, when the terminal device receives message 4, if it finds that the T_C_RNTI convolved on the physical downlink control channel (PDCCH) matches the message 3 sent by itself, it will further check whether the medium access control control element (MAC CE) in the message 4 sent by the network device contains its own terminal device identification. After that, if message 4 contains its own terminal device identification, the terminal device can confirm that the random access process is completed and use the newly allocated C-RNTI as its own identity. This identity is used for addressing information of subsequent physical layer, MAC and radio resource control (RRC) layer protocols.

The random access process described above in conjunction with FIG2A can also be called a competitive random access process (contention based random access, CBRA). In some protocols, a non-competitive random access process (non-contention or contention free random access, CFRA) is also introduced. FIG2B shows a flow chart of a non-competitive random access process. In the non-competitive random access process, the network device can allocate a specific random access resource to the terminal device, and accordingly, the network device can identify a specific terminal device through a random access preamble.

As shown in FIG. 2B , the network device sends RA preamble assignment information to the terminal device. Afterwards, in response to the RA preamble assignment information, the terminal device may send a preamble to the network device, and accordingly, the MAC processing process in the network device is the same as the contention-based random access process. After receiving the preamble, the network device may send a random access response (RAR) to the terminal device, and accordingly, the processing process of the terminal device is the same as the contention-based random access process.

The difference between the 2-step random access procedure and the 4-step random access procedure is that the 2-step random access procedure combines the contents of message 1 and message 3 of the 4-step random access procedure in message A, and combines the contents of message 2 and message 4 of the 4-step random access procedure in message B. FIG2C and FIG2D show the conventional 2-step random access procedure.

As shown in FIG. 2C , the terminal device sends a message A to the network device, wherein the message A includes a preamble and a physical uplink shared channel (PUSCH), wherein the PUSCH includes a terminal device identifier of the terminal device. Afterwards, the network device sends a message B (also called a “conflict resolution message”) to the terminal device. There are two ways to address the terminal device in message B: way 1 and way 2.

In mode 1, if the terminal device identifier in message A is a cell-radio network temporary identifier (C-RNTI), then the C-RNTI is also convolved on the PDCCH carried in message B. In this case, if the terminal device can confirm that the C-RNTI convolved on the PDCCH of message B (also known as conflict resolution) matches its own C-RNTI, the random access process has been successful, that is, the conflict has been resolved.

Generally, method 1 is applicable to a terminal device in the RRC_CONNECTED state, that is, the terminal device has completed initial access and established an RRC connection with the network device.

In mode 2, if the terminal device identifier in message A is an identifier other than C-RNTI, then the RA-RNTI is convolved on the PDCCH carrying message B. Correspondingly, if the terminal device identifier contained in the Success RAR (SuccessRAR) in message B matches the terminal device identifier of the terminal device itself, then the terminal device considers that the random access process is successful and the conflict is resolved. Otherwise, the terminal device can choose to resend message A, or the terminal device falls back to the 4-step random access process.

Generally, method 2 is applicable to other scenarios besides method 1.

As shown in FIG. 2D , the network device sends allocation information (also known as RA preamble and PUSCH allocation information) to the terminal device to allocate transmission resources for the transmission preamble and PUSCH. Afterwards, the terminal device sends message A to the network device based on the allocation information, wherein message A includes the preamble and PUSCH, wherein the PUSCH includes the terminal device identifier of the terminal device. Afterwards, the network device sends message B (also known as "random access response") to the terminal device.

Internet of Things (IoT) Technology

The rise of IoT technology has brought new challenges to communication systems. The use scenarios of IoT terminal devices can include logistics, warehousing, factory automation, and animal husbandry. IoT terminal devices and network devices can communicate intermittently or perform rough positioning and tracking. Even the simplest IoT terminal devices, such as NB-IoT terminal devices used for coal and electricity metering, require batteries to provide energy. Although IoT terminal devices have low energy consumption, their internal batteries can only last for a few years at most, but will eventually be exhausted. Therefore, the batteries of IoT terminal devices need to be replaced regularly, which consumes a lot of manpower. In addition, some industrial scenarios are dangerous and not suitable for manual operation. Therefore, battery-free IoT terminal devices came into being.

Battery-free IoT terminal devices are huge in number and low in cost. Generally, they do not require manual maintenance after installation. Radio frequency identification (RFID) terminal devices can meet people's demand for battery-free IoT terminal devices to some extent. However, the operation of RFID systems still requires human participation. For example, some RFID systems require manual handheld readers. Moreover, the wireless coverage range of a single RFID reader is limited (within 10 meters), so RFID systems deployed over a large area require more human participation. For example, when using an RFID system to take inventory of goods in a large supermarket, it takes a lot of manpower, material resources and time.

Ambient IoT (A-IoT) communication systems

Transplanting systems like RFID into cellular networks can effectively solve the problem of limited coverage, because cellular networks (such as the fourth generation (4G) system and 5G system) have achieved full coverage or at least coverage of major cities in some countries or regions (such as China and Europe and the United States). Based on the wider network coverage, the communication or positioning process between IoT terminal devices and network devices can be done without human intervention. Therefore, IoT terminal devices can work uninterruptedly and efficiently. In addition, IoT terminal devices can even work efficiently in environments that are not suitable for human intervention (such as wilderness, mines, and factories). Therefore, when applying IoT terminal devices, in addition to the initial need to associate the IoT terminal device with a specific object, subsequent data reading, writing, and operation and maintenance can be operated through apps such as on smartphones, which is very convenient and efficient. Such a communication system can be called an ambient IoT communication system or a zero-power communication system.

As shown in FIG3 , the A-IoT communication system may be composed of a network device 310 and a terminal device 320. The network device 310 may be, for example, a reader. The terminal device 320 is also called an A-IoT device, for example, a tag, also known as an electronic tag. Usually, the energy source of an A-IoT device comes from the surrounding environment, such as radio frequency (RF), solar energy, thermal energy, mechanical vibration, wind energy, etc. Accordingly, the A-IoT communication system adopts energy harvesting and backscattering communication technology, and the network device 310 can send wireless power supply signals, downlink communication signals, and receive backscattering signals from the terminal device 320 to the terminal device 320.

Continuing to refer to FIG. 3 , the terminal device 320 may include an energy collection module 321, a backscatter communication module 322, and a low-power computing module 323. In other scenarios, the terminal device 320 may also include a memory module (not shown) for storing some basic information (such as item identification, etc.). In other scenarios, the terminal device 320 may also include a sensor module 324 for acquiring sensor data such as ambient temperature and ambient humidity.

In some protocols, the use cases of A-IoT communication systems can be divided into four categories: inventory, sensor, tracking, and command. Inventory refers to checking for missing goods when goods enter and leave the warehouse. Common sensors can include temperature, pressure, humidity and other sensors. Sensors can be used in industry, agriculture, smart cities and other occasions. The information collected by the sensors can be uploaded to a third-party application (application, App) through the A-IoT system for monitoring and management. Tracking generally refers to obtaining the approximate location of an object at irregular intervals. For example, users can use smartphones to understand the location of their express delivery in real time. Command refers to the operation of a certain servo mechanism through the A-IoT system, which can be connected to an A-IoT terminal device. For example, people can water the flowers and plants in the backyard through a mobile phone app while working or taking a break in the office, and the watering servo mechanism can be connected to an A-IoT terminal device.

In some protocols, the A-IoT communication system is divided into four topological network structures as shown in Figures 4A to 4D. As shown in Figure 4A, data or signals (also called A-IoT data or signals) can be directly transmitted between network devices and A-IoT devices.

As shown in FIG4B , the network device and the A-IoT device can communicate through an intermediate node, wherein the data or information transmitted between the intermediate node and the terminal device is also called A-IoT data or signal. The intermediate node can be another network device, in which case the intermediate node and the network device can communicate through the Uu interface, for example, the intermediate node can send data or signals to the network device through the Uu interface, and the intermediate node can receive data or signals sent by the network device through the Uu interface.

As shown in FIG4C , the network device and the A-IoT device can communicate through the auxiliary point node, wherein the data or information transmitted between the auxiliary node and the terminal device is also called A-IoT data or signal, and the data or information transmitted between the terminal device and the network device is also called A-IoT data or signal. The auxiliary node can be another network device. In this case, the auxiliary node can only receive the data or signal sent by the network device through the Uu interface. In this case, the auxiliary node cannot send data or signals to the network device.

As shown in FIG. 4D , data or signals (also referred to as A-IoT data or signals) can be directly transmitted between the terminal device and the A-IoT device.

In some protocols, A-IoT devices can be divided into three types: Type A, Type B, and Type C. For terminal devices of type A and type B, such devices can only communicate by reflecting and modulating received radio waves. This communication method is called back-scattering. In other words, such devices cannot actively send radio signals, and their power is within the range of 1 to 10 microwatts (uW). Among them, the terminal devices of type A have the lowest transmission power and the lowest hardware complexity, which is basically close to the level of RFID terminal devices. The hardware of type B terminal devices is slightly more complicated, which may include signal amplification devices and certain energy storage devices. Therefore, the communication distance between the terminal devices of type B and the network devices is compared with the communication distance between the terminal devices of type A and the network devices. Further. Type C terminal devices usually have the ability to actively send radio waves, with a transmission power of about 1 to 10 milliwatts (mW), and can store a certain amount of energy. All three types of terminal devices can obtain energy from the environment and can continue to work for several years or more than 10 years. In addition, in order to save energy, type A and type B terminal devices are basically in a dormant state before the network device triggers the communication process with them. Only after being activated by the wireless signal of the network device, the type A and type B terminal devices will start working.

At present, the receivers of A-IoT devices can include two major types: receiver type 1 and receiver type 2. Receiver type 1 is a broadband receiver, which is also called an RF receiver. The RF receiver can obtain the signal within the bandwidth to be received based on the RF bandpass filter, and then perform envelope detection and subsequent baseband processing. The structure of the RF receiver is the simplest, and its power consumption can be as low as several uW or even lower. However, due to the poor accuracy of the RF bandpass filter, even when the target signal occupies a narrow bandwidth, the RF receiver often receives signals within a wider bandwidth. Therefore, more noise and interference will be introduced in the receiving process of the RF receiver, and its receiving performance is poor, or the receiving sensitivity is poor. The receiving process of a typical RF receiver can be shown in Figure 5.

Receiver type 2 is a narrowband receiver, which may include an intermediate frequency receiver or a zero intermediate frequency receiver. In signal reception, in addition to using an RF bandpass filter to obtain a signal within the bandwidth to be received, a narrowband receiver can also down-convert the RF signal and further filter the baseband signal using a low-pass filter to eliminate noise and interference. Therefore, the narrowband receiver has a narrow receiving bandwidth and good receiving performance, or a high receiving sensitivity. However, a narrowband receiver requires the use of a local oscillator (LO). The power consumption of LO is high, and even the recommended LO consumes 100uW or even more power. Therefore, the relative power consumption of a narrowband receiver is high, but because its absolute power consumption is very low, it is still suitable for use in zero-power devices. The receiving process of a typical intermediate frequency receiver can be shown in Figure 6.

In some scenarios, the above-mentioned type A terminal device usually adopts a broadband receiver, the type C communication device usually adopts a narrowband receiver, and the type B terminal device may adopt one or both types of receivers.

RFID initial access process

In some protocols, an initial access process adjusted for the IoT system is introduced. FIG7 shows a schematic flow chart of the initial access process of RFID. Among them, the interrogator can be the network device introduced above. As shown in FIG7, the interrogator can initiate a query to the tag to trigger the tag to initiate the initial access process. After that, the tag sends a 16-bit random number (indicated by "RN16") to the interrogator. In this process, if another tag also sends a random number through the same channel at substantially the same time, the first conflict will occur during the interrogator's reception process. If the interrogator responds to the correctly decoded random number through an ACK. For the tag, the tag that successfully conflicts will receive the same random number as it sent, while the tag that failed the conflict will receive a different random number from the one it sent.

For tags that successfully collide, they can send their EPC or related information to the interrogator. Correspondingly, the interrogator will repeatedly feed back the same random number (the one that is correctly decoded) to the tag through a random number request (Req_RN). Then the tag will feed back an identifier (handle) to the interrogator, which will be used as the identifier of the tag in the subsequent process. The identifier is also a 16-bit random number. After that, the interrogator can send a command to the tag, in which the tag identifier is written.

In the above-mentioned RFID initial access process, the identifier (handle) used by the tag in the subsequent process is actually generated by the tag. This method is more suitable for RFID because the coverage of the interrogator is usually small, and the length of the identifier is sufficient to distinguish different RFIDs. However, this initial access process is not suitable for scenarios where the network equipment has a large coverage range. The above-mentioned identifier (handle) may not be long enough for the network equipment to distinguish different terminal devices. The traditional random access process is too complicated and may cause the terminal equipment to consume more power. At this time, the degree to which power consumption can be reduced by introducing low-capability terminal devices (for example, the electronic tags introduced above) will be limited.

Therefore, in response to the above problems, an embodiment of the present application provides a wireless communication method to reduce the power consumption of a terminal device (also referred to as a "first terminal device") during a random access process. The wireless communication method of an embodiment of the present application is described below in conjunction with Figure 8. In some implementations, the first terminal device may be a low-power device. In some implementations, the first terminal device is the A-IoT device introduced above, for example, it may be a terminal device of type A. For another example, it may be a terminal device of type B. For another example, it may be a terminal device of type C. Of course, in an embodiment of the present application, the terminal device may also be a terminal device in an IoT system.

In some implementations, the target device shown in FIG8 may be a second terminal device, in which case the first terminal device may access the network through the second terminal device. In other words, the second terminal device may serve as an auxiliary node or intermediate node for communication between the first terminal device and the network device, so as to help the first terminal device access the network device. In other implementations, the target device may be a network device other than the network device that the terminal device is ready to access, in other words, the network device as the target device may serve as an auxiliary node or intermediate node for communication between the first terminal device and the network device (the network device that the terminal device attempts to access), so as to help the first terminal device access the network device. Of course, in an embodiment of the present application, the target device may be a network device that the terminal device attempts to access, in which case the first terminal device may communicate directly with the network device to attempt to access the network device.

In the embodiment of the present application, the network device may be a general term for network nodes including a reader. Of course, the network device may also only include a node that provides backscattered radio waves to the first terminal device alone.

In the embodiments of the present application, the first terminal device and the second terminal device are not limited. In some implementations, the second terminal device The capability of the second terminal device may be higher than that of the first terminal device. For example, the second terminal device may be an intelligent terminal device, and the first terminal device may be the electronic tag described above. In other implementations, the second terminal device may be a terminal device with similar capabilities to the first terminal device.

Fig. 8 is a schematic flow chart of a wireless communication method according to an embodiment of the present application. The method shown in Fig. 8 includes steps S810 to S840.

In step S810, the first terminal device sends a preamble code to the target device.

In some implementations, the preamble may be generated based on a sequence. For example, the preamble may be generated based on multiple fixed sequences, which helps to simplify the generation method of the preamble compared to the traditional preamble that is generated based on a derivative sequence of a root sequence, thereby saving the power consumption required for the first terminal device to generate the preamble.

In some implementations, the number of the plurality of sequences may be limited, for example, the number of the plurality of sequences may be 2 ⁴ = 16. In the embodiment of the present application, the preamble may be generated based on a limited number of sequences, which helps to simplify the complexity of generating the preamble.

In the embodiments of the present application, the generation process of the preamble code can also be simplified by other methods. In some implementations, the sequence used in the embodiments of the present application can adopt a relatively simple orthogonal method, for example, the minimum mean square error sequence can be used. In some implementations, the sequence used in the embodiments of the present application can adopt a relatively simple modulation method, for example, binary on-off keying (OOK) can be used for modulation. In some implementations, the length of the preamble code used in the embodiments of the present application can be shorter than the length of the preamble code used in the traditional random access process.

In some implementations, preamble codes generated based on different sequences may correspond to different indexes for easy identification by a network device.

In some implementations, the transmission of the preamble code described above may be used as the first piece of information in the random access process, and therefore, the preamble code may be referred to as message 1 (Msg 1).

In step S820, the target device sends a first index to the first terminal device.

In some implementations, the first index is used to indicate a preamble code received by the target device, and therefore, the first index may also be referred to as a “preamble code index”.

In some implementations, if the target device successfully receives and demodulates the preamble, the target device will send the first index corresponding to the preamble. Therefore, the target device sending the first index to the terminal device can be understood as the target device successfully receiving and demodulating the preamble indicated by the first index.

In some implementations, the transmission of the first index can be used as the second information in the random access process. Therefore, the information where the first index is located (i.e., the third information below) can be called message 2 (Msg 2).

In step S830, in response to the first index being the same as the index of the preamble code, the first terminal device sends the first terminal device identifier to the target device.

In some implementations, if the first index is the same as the index of the preamble code, it can be indicated that the preamble code successfully received and demodulated by the network device is the preamble code sent by the first terminal device. At this time, the first terminal device can send the first terminal device identifier to the target device.

In some implementations, if the first index is different from the index of the preamble code, it may indicate that the preamble code successfully received and demodulated by the network device is not the preamble code sent by the first terminal device. At this time, the first terminal device may consider that the conflict resolution has failed.

In some implementations, the first terminal device identifier may be generated by the first terminal device, for example, the first terminal device identifier may be a random number generated by the first terminal device, which is shorter than the terminal device identifier configured by the network device for the terminal device in the traditional random access process, and helps to simplify the power consumption required by the first terminal device to transmit the first terminal device identifier. For example, the length of the first terminal device identifier may be 16 bits.

In some implementations, the transmission of the first terminal device identifier may be used as the third piece of information in the random access process. Therefore, the information containing the terminal device identifier (i.e., the fourth information below) may be referred to as message 3 (Msg 3).

In some implementations, the time domain resource for sending the first terminal device identifier may be randomly selected by the first terminal device.

Correspondingly, in the above step S830, from the perspective of the target device, the target device receives the terminal device identification sent by the terminal device, wherein the terminal device may be the first terminal device, or the terminal device may include other terminal devices and the first terminal device.

In some implementations, the terminal device may be the terminal device that sends the preamble in step S810. For example, the terminal device that sends the preamble may be multiple terminal devices, and the multiple terminal devices include the first terminal device. In this case, the terminal device in step S830 may be the multiple terminal devices in step S810. For another example, the terminal device that sends the preamble may be the first terminal device. In this case, the terminal device in step S830 may be the first terminal device in step S810.

In step S840, the first terminal device receives first information sent by the target device, where the first information includes a terminal device identifier received by the target device.

Correspondingly, in the above step S840, from the perspective of the target device, the target device sends the first information to the terminal device, wherein the terminal device may be the first terminal device, or the terminal device may include other terminal devices and the first terminal device.

In some implementations, the terminal device in step S840 may be the terminal device in step S830, or the terminal device in step S840 is one of the terminal devices in step S830. In some scenarios, assuming that the preambles sent by multiple terminal devices are the same, in this case, in step S830, the multiple terminal devices will also send terminal device identifiers to the target device, and accordingly, the target device may only successfully receive the terminal device identifier of one of the terminal devices.

For ease of understanding, the following description is made by taking the first terminal device as an example, wherein the terminal device identifier of the first terminal device is the first terminal device identifier (or referred to as the identifier of the first terminal device). The access process of other terminal devices may be similar.

In some implementations, the first terminal device may compare the terminal device identifier carried in the first information with the first terminal device identifier to determine whether to successfully access the target device to resolve the conflict.

For example, if the terminal device identifier in the first information is the same as the first terminal device identifier, the first terminal device conflict resolution successfully accesses the target device. For another example, if the terminal device identifier in the first information is different from the first terminal device identifier, the first terminal device conflict resolution fails.

In some implementations, the first information may also include a first radio network temporary identifier (RNTI) associated with the terminal device identifier received by the target device. Accordingly, if the terminal device identifier in the first information is the same as the first terminal device identifier (or, if the conflict resolution of the first terminal device is successful), the first terminal device may retain the first RNTI. In some scenarios, the first terminal device may communicate with the target device based on the first RNTI, that is, use the first RNTI as the identifier of the first terminal device.

In the embodiment of the present application, the first RNTI may be carried only in the first information, and at this time, the transmission of other messages in the random access process may not be performed based on the RNTI. For example, the third information may not contain the RNTI, and for another example, the fourth information may not be processed using the RNTI. Compared with the traditional random access process, the RNTI is carried in the message 2, and the RNTI is used for processing in the transmission message 3, which helps to simplify the complexity of the first terminal device accessing the target device and reduce the power consumption of the first terminal device accessing the target device.

In addition, in an embodiment of the present application, the first terminal device can first perform random access with the network device based on the first terminal device identifier, and then indicate the first RNTI in the first information. Since the length of the first terminal device identifier is shorter than the first RNTI, it helps to simplify the power consumption of the first terminal device performing random access.

In some scenarios, the first terminal device may access the target device because there is information to be transmitted (for example, the ambient temperature collected by the first terminal device). If the information to be transmitted has been transmitted to the network device during the process of the first terminal device accessing the target device, the network device may no longer carry the first RNTI in the first information to reduce the overhead of transmitting the first information.

In some implementations, the length of the first RNTI is adjustable, or in other words, the first RNTI is variable in length. For example, the length of the first RNTI may be associated with the number of terminal devices served by the network device, that is, if the number of terminal devices served by the network device is large, the length of the first RNTI may be long to facilitate distinguishing multiple terminal devices. On the contrary, if the number of terminal devices served by the network device is small, the length of the first RNTI may be short to reduce the complexity of the first terminal device communicating based on the first RNTI.

Assuming that the network device is located in an outdoor scenario, the number of terminal devices served by the network device may be tens of thousands, and the length of the first RNTI may require 4 bytes. Assuming that the network device is located in an indoor scenario, the number of terminal devices served by the network device may be only a few hundred, and the length of the first RNTI may only require 2 bytes.

In the embodiment of the present application, there is no limitation on the change of the length of the first RNTI. For example, the length of the first RNTI can be adjusted by using different encoding methods, or the network device can use different encoding methods to generate first RNTIs of different lengths. Of course, in the embodiment of the present application, if the length change of the first RNTI can be achieved by truncation, that is, an original RNTI of uniform length can be generated, and then the original RNTI can be truncated by truncation to obtain the first RNTI.

As described above, the length of the first RNTI is variable. Therefore, in order to reduce the complexity of the first terminal device acquiring the first RNTI, the network device may indicate the length of the first RNTI to the first terminal device. In some implementations, the target device may configure the length of the first RNTI for the first terminal device through configuration information, that is, the target device may send configuration information to the first terminal device, and the configuration information is used to configure the length of the first RNTI for the first terminal device.

In some implementations, the first terminal device may receive the first information within the second time period to increase the probability of successfully receiving the first information, wherein the starting position of the second time period may be determined based on the sending time of the first terminal device identifier (or the sending time of the fourth information).

For example, the starting position of the second time period is the sending time of the first terminal device identifier. That is to say, after the first terminal device sends the first terminal device identifier, the first terminal device immediately enters the second time period to prepare to receive the first information, which helps the first terminal device to receive energy from other communication devices (e.g., readers) in the second time period for subsequent communication through backscattered radio waves.

For another example, the second time period is separated from the sending time of the first terminal device identifier by a second time interval, or the second time period is obtained by starting from the sending time of the first terminal device identifier and offsetting by the second time interval in the direction of time elapse. That is to say, after the first terminal device sends the first terminal device identifier, it will enter the second time period again after a second time interval to prepare to receive the first information, which helps the first terminal device save power consumption.

In the embodiment of the present application, the implementation method of the second time period is not limited. For example, the second time period can be represented by a time window. Of course, the second time period can also be represented by a timer.

In some implementations, when the first information is not received within the second time period, conflict resolution of the first terminal device fails.

Generally, the first terminal device may support receiving messages within a bandwidth range, or support receiving messages within a channel. For the first terminal device that supports receiving messages within a channel, the first information may be a narrowband message transmitted in a channel to save the first terminal device. The power consumption of the device when receiving the first information.

The above introduces the first information in the embodiment of the present application, and the following introduces the third information used to carry the first index in the embodiment of the present application.

In some implementations, the third information includes one or more of the following: information used to instruct the first terminal device to access the network based on the backoff mechanism; parameters used for the first terminal device to access the network based on the backoff mechanism; information used to instruct the terminal device to send a second time domain resource identifying the terminal device.

Take the example that the third information includes information for indicating that the first terminal device accesses the network based on the backoff mechanism, or in other words, the third information is used to indicate that the backoff mechanism is supported during the process of the first terminal device accessing the network.

Taking the third information including the above parameters as an example, in some implementations, the parameters are used to indicate the maximum number of times the first terminal device attempts to access the network. In some implementations, when the first terminal device confirms that the conflict resolution fails and the number of times the first terminal device attempts to access the target device is less than the maximum number, the first terminal device can re-listen to the second information.

In some other implementations, when the first terminal device confirms that the conflict resolution fails and the number of times the first terminal device attempts to access the target device is greater than or equal to the maximum number, the first terminal device may confirm that access to the target device has failed.

In the embodiment of the present application, if the first terminal device confirms that the access to the target device fails, the first terminal device may no longer monitor the second information. Alternatively, the first terminal device may monitor the second information again after a long interval, which is not limited in the embodiment of the present application.

In some implementations, the first terminal device may set a counter to record the maximum number of times the first terminal device attempts to access the network. Accordingly, the counter increases by 1 each time the first terminal device attempts to access the network.

In other implementations, the above parameters are also used to indicate the backoff time information for the first terminal device to try to access the target device again, or in other words, the above parameters are used to indicate the waiting time for the first terminal device to try to access the target device again, that is, the time interval between the time when the first terminal device initiates the random access process next time and the time when the random access process is initiated this time is greater than or equal to the backoff time indicated by the parameter. In other words, the first terminal device re-listens to the second information at the first moment, and the first moment is the moment after the time indicated by the backoff time information, starting from the moment when the first terminal device confirms that the conflict resolution fails.

In the embodiment of the present application, the above parameter may be the backoff time. Of course, in the embodiment of the present application, the above parameter may be indication information for indicating the backoff time, for example, the above parameter may be an index for indicating the backoff time, which helps to reduce the bits occupied by indicating the backoff time.

Taking the third information including information for indicating the second time domain resource as an example, in some implementations, the terminal device may send the terminal device identification on the second time domain resource. In other words, the information for indicating the second time domain resource (or the third information) may include one or more of the following: a time domain offset between the reception time of the third information and the second time domain resource; a duration corresponding to each time domain resource in a plurality of time domain resources; a time interval between two time domain resources that are adjacent in time domain in a plurality of time domain resources.

In some implementations, the time domain offset between the time domain resource corresponding to the reception time of the third information and the second time domain resource can be replaced by the time offset between the reception time of the third information and the time corresponding to the second time domain resource.

In an embodiment of the present application, the above-mentioned time domain offset may include one of the following: a time domain offset between a starting position of a time domain resource corresponding to a receiving time of the above-mentioned third information and a starting position of a second time domain resource, a time domain offset between an ending position of a time domain resource corresponding to a receiving time of the above-mentioned third information and an ending position of the second time domain resource, a time domain offset between a starting position of a time domain resource corresponding to a receiving time of the above-mentioned third information and an ending position of the second time domain resource, and a time domain offset between an ending position of a time domain resource corresponding to a receiving time of the above-mentioned third information and a starting position of the second time domain resource.

In an embodiment of the present application, the above-mentioned time offset may include one of the following: the time domain offset between the reception time of the above-mentioned third information and the start time of the second time domain resource, and the time domain offset between the reception time of the above-mentioned third information and the end time of the second time domain resource.

In the embodiment of the present application, the implementation method of the above-mentioned time domain offset and/or time offset is not limited. For example, the time domain offset and/or time offset can be represented by a period of time. For another example, the time domain offset and/or time offset can be represented by the number of time domain resources.

In some implementations, the multiple time domain resources may be multiple time domain resources that can be used to transmit the terminal device identifier, or in other words, the multiple time domain resources are candidate time domain resources for transmitting the terminal device identifier, wherein the multiple time domain resources include the second time domain resource.

In some implementations, the time interval between two time domain resources that are adjacent in the time domain among multiple time domain resources can be indicated by parameter t3, and the parameter t3 can be the duration between the starting time domain position of a time domain resource among the multiple time domain resources and the starting time domain position of the next time domain resource. At this time, the first terminal device can determine the above time interval based on the duration corresponding to a time domain resource and parameter t3. Of course, in an embodiment of the present application, the above time interval can also be the duration between the ending time domain position of a time domain resource and the starting time domain position of the next time domain resource.

For ease of understanding, the following describes a method for indicating the second time domain resource in an embodiment of the present application in conjunction with Figure 9. As shown in Figure 9, multiple time domain resources include time domain resources 0 to N, and the time when the first terminal device receives the third information is t. The information carried in the above third information for indicating the second time domain resource includes: a time domain offset t1 between the reception time of the third information and the second time domain resource, a duration t2 corresponding to each time domain resource in the multiple time domain resources, and a duration t3 between the starting position of time domain resource 0 and the starting position of time domain resource 1. Accordingly, the first terminal device can determine that the second time domain resource is time domain resource 0 based on the above parameters in the third information.

In some scenarios, the network device may successfully receive and demodulate multiple preamble codes. In this case, the third information may carry multiple indexes. To indicate multiple preamble codes received by the network device.

In some implementations, the third information is further used to indicate: information about time domain resources where multiple preamble codes corresponding to multiple indexes are located; and/or information about channels where preamble codes corresponding to each of the multiple indexes are located, which helps the first terminal device distinguish the preamble codes corresponding to the multiple indexes. The multiple indexes include the first index.

In some implementations, the information of the channels where the multiple preambles are located may be used to identify the information of the channel where each of the multiple preambles is located. For example, the information may be an index of the channel where each of the multiple preambles is located.

In some implementations, the information of the time domain resources where the multiple preambles are located can be used to identify the time domain resource where each of the multiple preambles is located. For example, the information can be an index of the time domain resource where each of the multiple preambles is located.

In some implementations, the indexes of the time domain resources where the multiple preamble codes are located may increase in order from early to late in the time domain. For example, the indexes of the time domain resources where the multiple preamble codes are located may increase in order from early to late in the time domain.

Usually, if the third information includes multiple indexes, it means that the target device receives preambles sent by multiple terminal devices. At this time, after determining that the preambles indicated by the multiple indexes include the preambles sent by themselves, the multiple terminal devices will send their respective terminal device identifiers to the target device. In other words, the network device will receive the terminal device identifiers of multiple terminal devices. In order to facilitate the network device to determine the correspondence between the received terminal device identifier and the received preamble, the index of the time domain resources where the multiple preambles are located can be set to correspond one by one with the time domain resources carrying the multiple terminal device identifiers. At this time, the network device can determine which preamble is sent by the terminal device indicated by the terminal device identifier based on the correspondence and the time domain resource where the terminal device identifier is located.

In some implementations, the above correspondence may include multiple terminal device identifiers being carried on multiple time domain resources in a first order, and the first order is the order of the indexes of the time domain resources where the multiple preamble codes corresponding to the multiple terminal device identifiers are located from small to large. In other words, for the terminal device that sends the preamble code first, its corresponding terminal device identifier is preferentially sent on the time domain resources where the multiple terminal device identifiers are located. In other words, the order in which the preamble codes (i.e., the multiple preamble codes in the previous text) are transmitted on multiple time domain resources among multiple terminal devices is the same as the order in which the terminal device identifiers (i.e., the multiple terminal device identifiers in the previous text) are transmitted on multiple time domain resources by multiple terminal devices.

As shown in FIG. 10 , it is assumed that terminal device 1 to terminal device 3 send preambles 1 to 3 to the network device respectively, wherein terminal device 1 sends preamble 1 on time domain resource 1, terminal device 2 sends preamble 2 on time domain resource 2, and terminal device 3 sends preamble 3 on time domain resource 3, and the arrangement order of the above three time domain resources from early to late in the time domain is time domain resource 1, time domain resource 2, and time domain resource 3. Accordingly, the network device successfully receives preambles 1 to 3 and sends the indexes corresponding to preambles 1 to 3. At this time, terminal device 1 can transmit the terminal device identification of terminal device 1 on time domain resource n+1, terminal device 2 can transmit the terminal device identification of terminal device 2 on time domain resource n+2, and terminal device 3 can transmit the terminal device identification of terminal device 3 on time domain resource n+3. Among them, the arrangement order of time domain resources n+1 to time domain resources n+3 from early to late in the time domain is time domain resource n+1, time domain resource n+2, and time domain resource n+3.

In some implementations, the third information may be transmitted in a broadcast manner, that is, the channel for sending the third information may be a broadcast channel. For example, the network device may send the third information in a broadcast manner within a bandwidth range, wherein the third information may include one or more indexes to indicate multiple preamble codes received by the target device.

In some implementations, the channel for sending the third information may be the same as the channel for sending the preamble code by the first terminal device, or in other words, the channel for sending the third information may be the same as the channel for sending the first terminal device identifier, which helps to simplify the complexity of the first terminal device receiving the third information.

It should be noted that if the channel for sending the third information can be the same as the channel for sending the preamble by the first terminal device, and the first terminal device selects the time domain resource for sending the preamble, then the time domain resource for sending the preamble indicated in the third information is selected by the first terminal device. At this time, the third information may not indicate the channel information for transmitting the preamble to save power consumption for transmitting the third information. Of course, in the embodiment of the present application, if the above problem is not considered, the third information may also indicate the channel information for transmitting the preamble.

In some implementations, the first terminal device may receive the third information within a first time period to increase the probability of successfully receiving the third information, wherein the starting position of the first time period may be determined based on the transmission time of the preamble code.

For example, the starting position of the first time period is the sending time of the preamble code. In the embodiment of the present application, the starting position of the first time period is set to the sending time of the preamble code, that is, after the first terminal device sends the preamble code, the first terminal device immediately enters the first time period to prepare to receive the third information, which helps the first terminal device to receive energy from other communication devices (for example, readers) in the first time period for subsequent communication through backscattered radio waves.

For another example, the starting position of the first time period is separated from the sending time of the preamble by a first time interval, or the starting position of the first time period is obtained by starting from the sending time of the preamble and shifting by the first time interval in the direction of time lapse. That is to say, after the first terminal device sends the preamble, it will continue to wait for the first time interval before entering the first time period to prepare for receiving the third information, which helps the first terminal device save power consumption.

In the embodiment of the present application, the implementation method of the first time period is not limited. For example, the first time period can be represented by a time window. Of course, the first time period can also be identified by a timer.

In some implementations, when the third information is not received within the first time period, conflict resolution of the first terminal device fails.

In the traditional random access process, the network device usually sends trigger information in a periodic form to trigger the first terminal device to perform a random access process. However, this method of periodically triggering the random access process is unnecessary and may result in reduced utilization of transmission resources. For example, for the terminal device of type A or type B introduced above, its working principle is based on backscattering, so before initiating any process, the reader usually sends one or more messages to the terminal device so that the terminal device can perform backscattering based on one or more messages sent by the reader. At this time, one or more messages can realize the function of triggering the random access process mentioned above. At this time, sending the trigger information in a periodic manner is obviously more consuming of system resources.

Therefore, in response to the above problem, an embodiment of the present application provides a wireless communication method, in which the target device can send second information to the first terminal device to trigger the first terminal device to perform a random access process, or in other words, the second information is used to trigger the first terminal device to send a preamble, wherein the second information can be transmitted aperiodically. Of course, if the above problem is not considered, the second information can be transmitted periodically.

For example, in a logistics transmission scenario, if the network device needs to take inventory of items in a warehouse, the network device can send the second information to the electronic tag on the item (as an example of the first terminal device). At this time, it can be understood that the second information is triggered based on the need to take inventory of items in the warehouse.

In some implementations, the second information may be information broadcast within a bandwidth range so that multiple terminal devices can receive it.

In some implementations, the time domain resource for sending the second information (also called "reference time domain resource") can be used to determine the time domain resource for sending the preamble (also called "first time domain resource"). In other words, the first time domain resource is determined based on the reference time domain resource.

In some implementations, the first time domain resource is determined based on a reference time domain resource and a resource configuration parameter, wherein the resource configuration parameter is used to indicate one or more of the following: a time domain offset between the reference time domain resource and the first time domain resource; a duration corresponding to each time domain resource in a plurality of time domain resources; a time interval between two time domain resources that are adjacent in time domain in a plurality of time domain resources; and the number of time domain resources in a plurality of time domain resources.

In some implementations, the time domain offset between the reference time domain resource and the first time domain resource may be replaced by a time offset between a time corresponding to the reference time domain resource and a time corresponding to the first time domain resource.

In an embodiment of the present application, the above-mentioned time domain offset may include one of the following: a time domain offset between the starting position of the above-mentioned reference time domain resource and the starting position of the first time domain resource, a time domain offset between the ending position of the above-mentioned reference time domain resource and the ending position of the first time domain resource, a time domain offset between the starting position of the above-mentioned reference time domain resource and the ending position of the first time domain resource, and a time domain offset between the ending position of the above-mentioned reference time domain resource and the starting position of the first time domain resource.

In an embodiment of the present application, the above-mentioned time offset may include one of the following: a time domain offset between the start time of the above-mentioned reference time domain resource and the start time of the first time domain resource, a time domain offset between the end time of the above-mentioned reference time domain resource and the end time of the first time domain resource, a time domain offset between the start time of the above-mentioned reference time domain resource and the end time of the first time domain resource, and a time domain offset between the end time of the above-mentioned reference time domain resource and the start time of the first time domain resource.

In the embodiment of the present application, the implementation method of the above-mentioned time domain offset and/or time offset is not limited. For example, the time domain offset and/or time offset can be represented by a period of time. For another example, the time domain offset and/or time offset can be represented by the number of time domain resources.

In some implementations, the multiple time domain resources may be multiple time domain resources that can be used to transmit the preamble, or in other words, the multiple time domain resources are candidate time domain resources for transmitting the preamble, wherein the multiple time domain resources include the first time domain resource.

In some implementations, the time interval between two time domain resources that are adjacent in the time domain among multiple time domain resources can be indicated by parameter t6, which can be the duration between the starting time domain position of a time domain resource among the multiple time domain resources and the starting time domain position of the next time domain resource. At this time, the first terminal device can determine the above time interval based on the duration corresponding to a time domain resource and parameter t6. Of course, in an embodiment of the present application, the above time interval can also be the duration between the ending time domain position of a time domain resource and the starting time domain position of the next time domain resource.

For ease of understanding, the following describes the indication method of the first time domain resource in an embodiment of the present application in conjunction with Figure 11. As shown in Figure 11, the multiple time domain resources include time domain resources 0 to N, and the reference time domain resource is time domain resource t. The above-mentioned resource configuration parameters include: a time domain offset t4 used to indicate the reference time domain resource and the first time domain resource, a duration t5 corresponding to each time domain resource in the multiple time domain resources, and a time interval t6 between the starting position of time domain resource 0 and the starting position of time domain resource 1. Accordingly, the first terminal device can determine that the first time domain resource is time domain resource 0 based on the above-mentioned parameters in the resource configuration parameters.

In some implementations, the resource configuration parameters are carried in the second information. Of course, in the embodiment of the present application, the resource configuration parameters may be predefined or preconfigured.

In some scenarios, in order to improve the success rate of the first terminal device accessing the target device, the first terminal device may use a different transmission power each time it attempts to access the network. In some implementations, during the process in which the first terminal device attempts to access the target device multiple times, the transmission power used by the first terminal device may be increased. For example, during the process in which the first terminal device attempts to access the target device multiple times, the transmission power used by the first terminal device may be adjusted based on a power step. For another example, during the process in which the first terminal device attempts to access the target device multiple times, the transmission power used by the first terminal device may be obtained by adjusting the power step based on the initial transmission power. For example, if the power step is ΔP and the initial transmission power is P, then the transmission power used by the first terminal device when attempting to access the target device for the Nth time may be Assume that _PN , then _PN can be determined by the following formula: _PN = P + N × ΔP.

In some implementations, the initial transmission power may be used by the first terminal device when it attempts to access the target device for the first time, and N is a positive integer greater than or equal to 0. Of course, in the embodiment of the present application, the transmission power used by the first terminal device when it attempts to access the target device for the first time may be the sum of the initial transmission power and the power step, and N is a positive integer greater than or equal to 1.

In an embodiment of the present application, the transmission power used by the first terminal device to attempt to access the target device may refer to the transmission power used to transmit the preamble code and/or the fourth information (or the terminal device identifier) during the process of the first terminal device attempting to access the target device.

In some implementations, the parameters for power adjustment (e.g., initial transmit power and/or power step) may be configured by the network device through the second information. Of course, in the embodiment of the present application, the parameters for power adjustment (e.g., initial transmit power and/or power step) may be predefined or preconfigured.

In some implementations, during the process of the first terminal device attempting to access the target device, the information (e.g., one or more of the second information, the third information, and the first information) sent by the network device to the first terminal device may be transmitted within a bandwidth range or within a certain channel. Accordingly, the information (e.g., the preamble and/or the fourth information) sent by the first terminal device to the network device may be transmitted within a certain channel.

In some implementations, the timing at which the first terminal device sends information (e.g., a preamble and/or the fourth information) is associated with the terminal type of the first terminal device. For example, for a terminal device of type A and/or type B, the time to start sending information can be determined based on internal preparations and whether external radio waves for backscattering exist. When both are ready, the terminal device of type A and/or type B starts sending messages. For another example, for a terminal device of type C, the time to start sending information can be determined based on internal preparations, that is, if the internal preparations have been completed, the terminal device of type C can send information.

It should be noted that when the terminal devices on the same channel select the same preamble code, a conflict will occur. In this case, different terminal devices will send the fourth information on the same channel at substantially the same time. In some cases, the network device may not be able to demodulate the fourth information sent by multiple terminal devices (if the transmission power used by the fourth information sent by multiple terminal devices is similar, the network device may not be able to demodulate the fourth information sent by multiple terminal devices). At this time, multiple terminal devices fail to access the target device.

In other cases, some of the fourth information sent by multiple terminal devices may be successfully demodulated, while the fourth information sent by the remaining terminal devices cannot be demodulated. (If the fourth information sent by multiple terminal devices uses different transmission powers, for the network device, the fourth information sent with the maximum transmission power may be successfully demodulated.) In this case, the terminal device identifier fed back by the network device in the first information is the terminal device identifier in the successfully demodulated fourth information. The terminal devices corresponding to the other fourth information that has not been successfully demodulated will fail to access because they cannot wait for the first information.

For ease of understanding, the random access method of an embodiment of the present application is introduced below in conjunction with Figures 12 to 15. In the random access process introduced below, Msg0 can be used as an example of the second information, Msg1 can be used as an example of information carrying a preamble code, Msg2 can be used as an example of the third information, Msg3 can be used as an example of the fourth information, and Msg4 can be used as an example of the first information.

Fig. 12 is a schematic flow chart of a random access method according to an embodiment of the present application. The method shown in Fig. 12 includes steps S1210 to S1250.

In step S1210, the network device sends Msg0.

In some implementations, for inventory purposes, the network device may broadcast Msg0 on a certain frequency band to trigger multiple terminal devices to perform random access, wherein the multiple terminal devices include the first terminal device.

In step S1220, in response to the first terminal device receiving Msg0, the first terminal device sends a preamble code 1 (also referred to as Msg1) to the network device.

In some implementations, a sequence may be modulated in preamble 1, and the sequence may be one of 16 preset sequences.

In some implementations, each of the 16 sequences may correspond to an index so that the network device can demodulate preambles carrying different sequences. If the network device receives preambles modulated with the same sequence from different terminal devices, the network device cannot identify that the multiple preambles come from different terminal devices. At this time, the network device may demodulate the multiple preambles sent by the multiple terminal devices as a preamble sent by one terminal device.

In step S1230, the network device sends Msg2 to the first terminal device.

In some implementations, Msg2 may include the index of the preamble that the network device received and correctly demodulated.

In step S1240, if the index of the preamble code carried in Msg2 includes the index of preamble code 1, the first terminal device sends Msg3 to the network device.

In some implementations, Msg3 includes a terminal device identifier of the first terminal device, wherein the terminal device identifier is a random number generated by the first terminal device.

In some implementations, after receiving Msg2, the first terminal device determines whether the index of the preamble code carried in Msg2 includes the index of preamble code 1. If the index of the preamble code carried in Msg2 includes the index of preamble code 1, it means that the preamble code 1 sent by the first terminal device is received and correctly demodulated by the network device, and the first terminal device sends Msg3 to the network device.

If the index of the preamble code carried in Msg2 does not include the index of the preamble code 1, it means that the preamble code 1 sent by the first terminal device is not received and correctly demodulated by the network device, then the first terminal device may consider that the random access has failed.

In step S1250, in response to the network device receiving the terminal device identification, the network device sends Msg4 to the first terminal device.

In some implementations, Msg4 includes a terminal device identifier received by the network device and a first RNTI corresponding to the terminal device identifier.

In some implementations, if the terminal device identifier carried in Msg4 includes the terminal device identifier of the first terminal device, the first terminal device may consider that the random access is successful, and then the first terminal device may use the first RNTI as its own identifier and communicate with the network device based on the first RNTI. If the terminal device identifier carried in Msg4 does not include the terminal device identifier of the first terminal device, the first terminal device may consider that the random access has failed.

Fig. 13 is a schematic flow chart of a random access method according to another embodiment of the present application. The method shown in Fig. 13 includes steps S1310 to S1350.

In step S1310, the network device sends Msg0.

In some implementations, for inventory purposes, the network device may broadcast Msg0 on a certain frequency band to trigger multiple terminal devices to perform random access, wherein the multiple terminal devices include the first terminal device.

In some implementations, Msg0 may include resource configuration parameters for determining a first time domain resource, where the first time domain resource may be used to send preamble 1. It should be understood that the determination method of the first time domain resource may refer to FIG. 11 , and for the sake of brevity, it will not be repeated here.

In step S1320, in response to the first terminal device receiving Msg0, the first terminal device sends a preamble code 1 (also referred to as Msg1) to the network device on the first time domain resource.

In some implementations, a sequence may be modulated in preamble 1, and the sequence may be one of 16 preset sequences.

In some implementations, each of the 16 sequences may correspond to an index so that the network device can demodulate preambles carrying different sequences. If the network device receives preambles modulated with the same sequence from different terminal devices, the network device cannot identify that the multiple preambles come from different terminal devices. At this time, the network device may demodulate the multiple preambles sent by the multiple terminal devices as a preamble sent by one terminal device.

In step S1330, the network device sends Msg2 to the first terminal device.

In some implementations, Msg2 may include the index of the preamble code received and correctly demodulated by the network device, and the index of the time domain resource where the preamble code was sent.

In some implementations, if Msg2 is sent via a broadcast message, Msg2 also needs to carry the index of the channel on which the preamble code is sent.

In some implementations, Msg2 may include resource configuration parameters for determining a second time domain resource, wherein the second time domain resource may be used to send Msg3. It should be understood that the determination method of the second time domain resource may refer to FIG9 , and for the sake of brevity, it will not be described here.

In step S1340, if the index of the preamble code carried in Msg2 includes the index of the preamble code 1, the first terminal device sends Msg3 to the network device on the second time domain resources.

In some implementations, Msg3 includes a terminal device identifier of the first terminal device, wherein the terminal device identifier is a random number generated by the first terminal device.

In some implementations, after receiving Msg2, the first terminal device determines whether the index of the preamble code carried in Msg2 includes the index of preamble code 1. If the index of the preamble code carried in Msg2 includes the index of preamble code 1, it means that the preamble code 1 sent by the first terminal device is received and correctly demodulated by the network device, and the first terminal device sends Msg3 to the network device.

If the index of the preamble code carried in Msg2 does not include the index of the preamble code 1, it means that the preamble code 1 sent by the first terminal device is not received and correctly demodulated by the network device, then the first terminal device may consider that the random access has failed.

In step S1350, in response to the network device receiving the terminal device identification, the network device sends Msg4 to the first terminal device.

In some implementations, Msg4 includes a terminal device identifier received by the network device and a first RNTI corresponding to the terminal device identifier.

In some implementations, if the terminal device identifier carried in Msg4 includes the terminal device identifier of the first terminal device, the first terminal device may consider that the random access is successful, and then the first terminal device may use the first RNTI as its own identifier and communicate with the network device based on the first RNTI. If the terminal device identifier carried in Msg4 does not include the terminal device identifier of the first terminal device, the first terminal device may consider that the random access has failed.

FIG14 is a schematic flow chart of a random access method according to another embodiment of the present application. Assume that the first terminal device is a terminal device of type C described above, and the terminal device of this type can autonomously select a channel to send information. In some scenarios, the first terminal device of this type can operate in an FDD frequency band. The method shown in FIG14 includes steps S1410 to S1460.

In step S1410, the first terminal device sends a wake-up signal to the network device to wake up the network device.

In some implementations, if the network device requires the first terminal device to actively send information (if the first terminal device is a sensor for detecting temperature, the information actively sent by the first terminal device includes temperature information), then, since the network device does not know whether the first terminal device sends The time to start the random access process, therefore, the network device usually triggers the first terminal device to perform random access by periodically broadcasting Msg0. However, the periodic broadcasting of Msg0 will consume system energy and bandwidth. In this case, if no terminal device needs to initiate a random access process, the network device can stop broadcasting Msg0. If a terminal device needs to initiate a random access process, but does not find Msg0, the first terminal device can send a wake-up signal to the network device to trigger the network device to send Msg0.

In step S1420, in response to the wake-up signal, the network device sends Msg0.

In some implementations, the network device may broadcast Msg0 on a certain frequency band to trigger multiple terminal devices to perform random access, wherein the multiple terminal devices include the first terminal device.

In step S1430, in response to the first terminal device receiving Msg0, the first terminal device sends a preamble code 1 (also referred to as Msg1) to the network device.

In some implementations, the transmission resource for the first terminal device to send the preamble 1 may be independently selected by the first terminal device. The transmission resource may include one or more of the following time domain resources, frequency domain resources, and spatial domain resources.

In some implementations, a sequence may be modulated in preamble 1, and the sequence may be one of 16 preset sequences.

In some implementations, each of the 16 sequences may correspond to an index so that the network device can demodulate preambles carrying different sequences. If the network device receives preambles modulated with the same sequence from different terminal devices, the network device cannot identify that the multiple preambles come from different terminal devices. At this time, the network device may demodulate the multiple preambles sent by the multiple terminal devices as a preamble sent by one terminal device.

In step S1440, the network device sends Msg2 to the first terminal device.

In some implementations, Msg2 may include one or more of the following: an index of a preamble code received and correctly demodulated by the network device, an index of a time domain resource for sending the preamble code, an index of a channel for sending the preamble code, and a timing advance (TA) value for uplink synchronization.

In some implementations, since the coverage range of the network device may be large (for example, the coverage range exceeds 500 meters), Msg2 may include a TA value to facilitate time synchronization between the network device and the terminal device.

In some implementations, Msg2 may include resource configuration parameters for determining a second time domain resource, wherein the second time domain resource may be used to send Msg3. It should be understood that the determination method of the second time domain resource can be shown in FIG9, and for the sake of brevity, it is not repeated here. Of course, in the embodiment of the present application, Msg2 may also include a frequency domain resource for transmitting Msg3.

In some scenarios, the network device may successfully receive and demodulate multiple preamble codes. In this case, Msg2 includes the indexes of multiple preamble codes. At this time, the indexes of multiple preamble codes can correspond to a set of the above parameters: the index of the preamble code received and correctly demodulated by the network device, as well as the index of the time domain resource for sending the preamble code, the index of the channel for sending the preamble code, the TA value used for uplink synchronization; the resource configuration parameters for determining the second time domain resources; and the frequency domain resources for transmitting Msg3.

In step S1450, if the index of the preamble code carried in Msg2 includes the index of preamble code 1, the first terminal device sends Msg3 to the network device.

In some implementations, the transmission resources for sending Msg3 by the first terminal device may be determined based on Msg2, or in other words, the first terminal device sends Msg3 on the transmission resources indicated by Msg2.

In some implementations, Msg3 includes a terminal device identifier of the first terminal device, wherein the terminal device identifier is a random number generated by the first terminal device.

In some implementations, after receiving Msg2, the first terminal device determines whether the index of the preamble code carried in Msg2 includes the index of preamble code 1. If the index of the preamble code carried in Msg2 includes the index of preamble code 1, it means that the preamble code 1 sent by the first terminal device is received and correctly demodulated by the network device, and the first terminal device sends Msg3 to the network device.

If the index of the preamble code carried in Msg2 does not include the index of the preamble code 1, it means that the preamble code 1 sent by the first terminal device is not received and correctly demodulated by the network device, then the first terminal device may consider that the random access has failed.

In step S1460, in response to the network device receiving the terminal device identification, the network device sends Msg4 to the first terminal device.

In some implementations, Msg4 includes a terminal device identifier received by the network device and a first RNTI corresponding to the terminal device identifier.

In some implementations, if the terminal device identifier carried in Msg4 includes the terminal device identifier of the first terminal device, the first terminal device may consider that the random access is successful, and then the first terminal device may use the first RNTI as its own identifier and communicate with the network device based on the first RNTI. If the terminal device identifier carried in Msg4 does not include the terminal device identifier of the first terminal device, the first terminal device may consider that the random access has failed.

Fig. 15 is a schematic flow chart of a random access method according to another embodiment of the present application. The method shown in Fig. 15 includes steps S1510 to S1570.

In step S1510, the network device sends Msg0.

In some implementations, the network device may broadcast Msg0 on a certain frequency band to trigger multiple terminal devices to perform random access, wherein the multiple terminal devices include the first terminal device.

In step S1520, in response to the first terminal device receiving Msg0, the first terminal device sends a preamble code 1 (also referred to as Msg1) to the network device.

In some implementations, the transmission resource for the first terminal device to send the preamble 1 may be independently selected by the first terminal device. The transmission resource may include one or more of the following time domain resources, frequency domain resources, and spatial domain resources.

In some implementations, a sequence may be modulated in preamble 1, and the sequence may be one of 16 preset sequences.

In some implementations, each of the 16 sequences may correspond to an index so that the network device can demodulate preambles carrying different sequences. If the network device receives preambles modulated with the same sequence from different terminal devices, the network device cannot identify that the multiple preambles come from different terminal devices. At this time, the network device may demodulate the multiple preambles sent by the multiple terminal devices as a preamble sent by one terminal device.

In step S1530, the network device sends Msg2 to the first terminal device.

In some implementations, Msg2 may include one or more of the following: an index of a preamble code received and correctly demodulated by the network device, an index of a time domain resource for sending the preamble code, an index of a channel for sending the preamble code, and a timing advance (TA) value for uplink synchronization.

In some implementations, since the coverage range of the network device may be large (for example, the coverage range exceeds 500 meters), Msg2 may include a TA value to facilitate time synchronization between the network device and the terminal device.

In some implementations, Msg2 may include resource configuration parameters for determining a second time domain resource, wherein the second time domain resource may be used to send Msg3. It should be understood that the determination method of the second time domain resource can be shown in FIG9, and for the sake of brevity, it is not repeated here. Of course, in the embodiment of the present application, Msg2 may also include a frequency domain resource for transmitting Msg3.

In some implementations, Msg2 may include information for instructing the first terminal device to access the network based on the backoff mechanism; parameters for the first terminal device to access the network based on the backoff mechanism (e.g., the maximum number of times the first terminal device attempts to access the target device).

In some scenarios, the network device may successfully receive and demodulate multiple preamble codes. In this case, Msg2 includes indexes of multiple preamble codes. In this case, the indexes of multiple preamble codes can correspond to a set of the above parameters: the index of the preamble code received and correctly demodulated by the network device, as well as the index of the time domain resource for sending the preamble code, the index of the channel for sending the preamble code, and the TA value for uplink synchronization; resource configuration parameters for determining the second time domain resources; frequency domain resources for transmitting Msg3; information for indicating that the first terminal device accesses the network based on the backoff mechanism; and parameters for the first terminal device to access the network based on the backoff mechanism.

In step S1540, if the index of the preamble code carried in Msg2 includes the index of preamble code 1, the first terminal device sends Msg3 to the network device.

In some implementations, the transmission resources for sending Msg3 by the first terminal device may be determined based on Msg2, or in other words, the first terminal device sends Msg3 on the transmission resources indicated by Msg2.

In some implementations, Msg3 includes a terminal device identifier of the first terminal device, wherein the terminal device identifier is a random number generated by the first terminal device.

In some implementations, after receiving Msg2, the first terminal device determines whether the index of the preamble code carried in Msg2 includes the index of preamble code 1. If the index of the preamble code carried in Msg2 includes the index of preamble code 1, it means that the preamble code 1 sent by the first terminal device is received and correctly demodulated by the network device, and the first terminal device sends Msg3 to the network device.

If the index of the preamble code carried in Msg2 does not include the index of the preamble code 1, it means that the preamble code 1 sent by the first terminal device is not received and correctly demodulated by the network device, then the first terminal device may consider that the random access has failed.

In step S1550, in response to the network device receiving the terminal device identification, the network device sends Msg4.

In some implementations, Msg4 includes a terminal device identifier received by the network device and a first RNTI corresponding to the terminal device identifier.

In some implementations, if the terminal device identifier carried in Msg4 includes the terminal device identifier of the first terminal device, the first terminal device may consider that the random access is successful, and then the first terminal device may use the first RNTI as its own identifier and communicate with the network device based on the first RNTI. If the terminal device identifier carried in Msg4 does not include the terminal device identifier of the first terminal device, the first terminal device may consider that the random access has failed.

In step S1560, if the terminal device identifier carried in Msg4 does not include the terminal device identifier of the first terminal device, the first terminal device considers that the random access has failed.

In step S1570, if the number of times the current first terminal device attempts to access the target device has not reached the maximum number, the first terminal device may continue to attempt to access the target device, that is, re-execute steps S1510 to S1550.

In some implementations, if steps S1510 to S1550 are re-executed, the transmission resources for the first terminal device to transmit the preamble code and the fourth information can be independently selected by the first terminal device.

In some implementations, if re-execution of steps S1510 to S1550 is the Nth attempt of the first terminal device to access the target device, and Msg0 carries parameters for adjusting the transmit power, for example, the power step ΔP and the initial transmit power P, then the transmit power used by the first terminal device when attempting to access the target device for the Nth time may be _PN , and _PN may be determined by the following formula: _PN = P+ N×ΔP.

It should be noted that the transmission power _PN can be used to transmit the preamble code and/or Msg3 during the Nth attempt of the first terminal device to access the target device.

It should be noted that the above text takes the case where the terminal device identifier carried in Msg4 does not include the terminal device identifier of the first terminal device as an example to introduce a solution in which the first terminal device retries to access the target device. In some scenarios, if the index of the preamble code carried in Msg2 does not include the index of preamble code 1 in step 1540, the first terminal device will also retry to access the target device after failing to access the target device. At this time, the way in which the first terminal device retries to access the target device is similar to the solution introduced in step S1570. For details, please refer to the above introduction, which will not be repeated for the sake of brevity.

In the embodiment of the present application, the time domain resources are not limited. For example, the time domain resources may be time slots, subframes, mini-subframes, symbols, etc. Of course, in the embodiment of the present application, the time domain resources may also be other time domain resources newly introduced in future communication systems.

In addition, in the embodiments of the present application, terms such as "access network", "access network device", "access target device" and "random access" can be used interchangeably.

The method embodiment of the present application is described in detail above in conjunction with Figures 1 to 15, and the device embodiment of the present application is described in detail below in conjunction with Figures 16 to 18. It should be understood that the description of the method embodiment corresponds to the description of the device embodiment, so the part not described in detail can refer to the previous method embodiment.

Fig. 16 is a schematic diagram of a terminal device according to an embodiment of the present application. The terminal device 1600 shown in Fig. 16 is a first terminal device, including: a sending unit 1610 and a receiving unit 1620.

The sending unit 1610 is used to send a preamble code to a target device;

The receiving unit 1620 is configured to receive a first index sent by the target device, where the first index is used to indicate a preamble received by the target device;

The sending unit 1610 is configured to send a first terminal device identifier to the target device in response to the first index being the same as the index of the preamble;

The receiving unit 1620 is used to receive first information sent by the target device, where the first information includes a terminal device identifier received by the target device; wherein the target device includes a network device and/or a second terminal device.

In some implementations, the terminal device includes: a first processing unit, used to confirm that the conflict resolution is successful when the terminal device identifier in the first information matches the first terminal device identifier; and/or a second processing unit, used to confirm that the conflict resolution fails when the terminal device identifier in the first information does not match the first terminal device identifier.

In some implementations, the first information also includes a first radio network temporary identifier RNTI associated with the terminal device identifier.

In some implementations, the receiving unit is further used to receive configuration information sent by the target device, where the configuration information is used to configure the length of the first RNTI for the first terminal device.

In some implementations, the terminal device further includes:

The third processing unit is used to retain the first RNTI associated with the first terminal device identifier when the first terminal device confirms that the conflict is successfully resolved.

In some implementations, the first terminal device identifier is generated by the first terminal device.

In some implementations, the receiving unit is further used to receive second information sent by the target device, where the second information is used to instruct the first terminal device to send the preamble code, and the second information is information that is sent non-periodically, or the second information is information that is sent periodically.

In some implementations, the first time domain resource for sending the preamble is determined based on a reference time domain resource, and the reference time domain resource is used to receive the second information.

In some implementations, the first time domain resource is determined based on the reference time domain resource and a resource configuration parameter, and the resource configuration parameter is used to indicate one or more of the following: a time domain offset between the reference time domain resource and the first time domain resource; a duration corresponding to each time domain resource in a plurality of time domain resources, the plurality of time domain resources including the first time domain resource; a time interval between two time domain resources that are adjacent in time domain in the plurality of time domain resources; and the number of time domain resources in the plurality of time domain resources.

In some implementations, the resource configuration parameter is carried in the second information.

In some implementations, the second information includes a power adjustment parameter, and the power adjustment parameter is used to adjust the transmission power of the preamble code and/or the transmission power of the first terminal device identifier.

In some implementations, the time domain resource for sending the first terminal device identifier is randomly selected by the first terminal device.

In some implementations, the first index is carried in third information, and the third information includes one or more of the following: information used to indicate that the first terminal device accesses the network based on the backoff mechanism; parameters used for the first terminal device to access the network based on the backoff mechanism; information used to indicate a second time domain resource for sending the first terminal device identifier.

In some implementations, if the third information includes the parameter, the parameter is used to indicate the maximum number of times the first terminal device attempts to access the target device; and/or backoff time information for the first terminal device to attempt to access the target device again.

In some implementations, if the parameter is used to indicate the maximum number of times, the receiving unit is further used to re-listen to the second information when the first terminal device confirms that the conflict resolution has failed and the number of times the first terminal device attempts to access the target device is less than the maximum number of times.

In some implementations, if the parameter is used to indicate the maximum number of times, the terminal device also includes: a fourth processing unit, which is also used to confirm that access to the target device has failed when the first terminal device confirms that the conflict resolution has failed and the number of times the first terminal device attempts to access the target device is greater than or equal to the maximum number of times.

In some implementations, if the parameter is used to indicate the backoff time information, the receiving unit is used to re-listen to the second information at a first moment, where the first moment is a moment starting from the moment when the first terminal device confirms that the conflict resolution has failed and after the duration indicated by the backoff time information has passed.

In some implementations, if the third information is used to indicate a second time domain resource for sending the terminal device identifier, the third information includes one or more of the following: a time domain offset between a time domain resource corresponding to a reception time of the third information and the second time domain resource; a duration corresponding to each time domain resource in a plurality of time domain resources, the plurality of time domain resources including the second time domain resource; and a time interval between two time domain resources that are adjacent in time domain in the plurality of time domain resources.

In some implementations, if the third information carries multiple indexes, the multiple indexes are used to indicate multiple preamble codes received by the target device, the multiple indexes include the first index, and the third information is used to indicate information about time domain resources where the multiple preamble codes corresponding to the multiple indexes are located; and/or information about channels where the multiple preamble codes corresponding to the multiple indexes are located.

In some implementations, the information of the time domain resources where the multiple preamble codes are located includes indexes of the time domain resources where the multiple preamble codes are located, and the indexes of the time domain resources where the multiple preamble codes are located increase in order from early to late in the time domain.

In some implementations, the multiple preamble codes are sent by multiple terminal devices, and the time domain resources where the multiple preamble codes are located correspond one-to-one to the time domain resources where the multiple terminal devices send multiple terminal device identifiers.

In some implementations, the order in which the multiple terminal devices send preamble codes on the multiple time domain resources is the same as the order in which the multiple terminal devices send terminal device identifications on the multiple time domain resources.

In some implementations, the third information channel is a broadcast channel.

In some implementations, the first terminal device receives the third information within a first time period, and a starting position of the first time period is determined based on a sending time of the preamble code.

In some implementations, the starting position of the first time period is the sending time of the preamble code, or the starting position of the first time period is separated from the sending time of the preamble code by a first time interval.

In some implementations, the terminal device further includes: if the third information is not received within the first time period, the fifth processing unit is used to confirm that the conflict resolution fails.

In some implementations, the first terminal device receives the first information within a second time period, and a starting position of the second time period is determined based on a sending time of the first terminal device identifier.

In some implementations, the starting position of the second time period is the sending time of the first terminal device identifier, or the starting position of the second time period is separated from the sending time of the first terminal device identifier by a second time interval.

In some implementations, the terminal device further includes: if the first information is not received within the second time period, a sixth processing unit is used to confirm that the conflict resolution fails.

In some implementations, the channel for sending the preamble code is the same as the channel for sending the first terminal device identifier.

Fig. 17 is a schematic diagram of a communication device according to an embodiment of the present application. The communication device 1700 shown in Fig. 17 is a target device, and the communication device 1700 includes: a receiving unit 1710 and a sending unit 1720.

The receiving unit 1710 is configured to receive a preamble sent by a first terminal device;

A sending unit 1720 is configured to send a first index to the first terminal device, where the first index is used to indicate a preamble received by a target device;

The receiving unit 1710 is configured to receive a terminal device identification sent by the terminal device;

The sending unit 1720 is used to send first information to the terminal device, where the first information includes a terminal device identifier received by the target device; wherein the target device includes a network device and/or a second terminal device.

In some implementations, the terminal device includes the first terminal device, and the first terminal device corresponds to a first terminal device identifier. If the terminal device identifier in the first information matches the first terminal device identifier, the conflict resolution of the first terminal device is successful; and/or if the terminal device identifier in the first information does not match the first terminal device identifier, the conflict resolution of the first terminal device fails.

In some implementations, the first information also includes a first radio network temporary identifier RNTI associated with the terminal device identifier.

In some implementations, when the conflict of the first terminal device is successfully resolved, the target device communicates with the first terminal device based on the first RNTI.

In some implementations, the sending unit is used to send configuration information to the first terminal device, and the configuration information is used to The first terminal device configures the length of the first RNTI.

In some implementations, the first terminal device corresponds to a first terminal device identifier, and the first terminal device identifier is generated by the first terminal device.

In some implementations, the sending unit is used to send second information to the first terminal device, where the second information is used to instruct the first terminal device to send the preamble code, and the second information is information that is sent non-periodically, or the second information is information that is sent periodically.

In some implementations, the first time domain resource for sending the preamble is determined based on a reference time domain resource, and the reference time domain resource is used to receive the second information.

In some implementations, the first time domain resource is determined based on the reference time domain resource and a resource configuration parameter, and the resource configuration parameter is used to indicate one or more of the following: a time domain offset between the reference time domain resource and the first time domain resource; a duration corresponding to each time domain resource in a plurality of time domain resources, the plurality of time domain resources including the first time domain resource; a time interval between two time domain resources that are adjacent in time domain in the plurality of time domain resources; and the number of time domain resources in the plurality of time domain resources.

In some implementations, the resource configuration parameter is carried in the second information.

In some implementations, the second information includes a power adjustment parameter, and the power adjustment parameter is used to adjust the transmission power of the preamble code and/or the transmission power of the terminal device identifier, and the terminal device corresponding to the terminal device identifier includes the first terminal device.

In some implementations, the time domain resource for sending the first terminal device identifier is randomly selected by the first terminal device.

In some implementations, the first index is carried in third information, and the third information includes one or more of the following: information used to instruct the terminal device to access the target device based on a backoff mechanism; parameters used for the terminal device to access the target device based on the backoff mechanism; and information used to instruct the terminal device to send a second time domain resource corresponding to the terminal device identifier.

In some implementations, if the third information includes the parameter, the parameter is used to indicate the maximum number of times the terminal device attempts to access the target device; and/or backoff time information for the terminal device to attempt to access the target device again.

In some implementations, if the parameter is used to indicate the maximum number of times, then when the first terminal device fails to resolve the conflict and the number of times the first terminal device attempts to access the target device is greater than or equal to the maximum number of times, the first terminal device fails to access the target device.

In some implementations, if the parameter is used to indicate the backoff time information, the first moment is the moment when the first terminal device listens to the second information again, and the first moment is the moment after the time indicated by the backoff time information, starting from the moment when the conflict resolution of the first terminal device fails.

In some implementations, if the third information is used to indicate a second time domain resource for sending the terminal device identifier, the third information includes one or more of the following: a time domain offset between a time domain resource corresponding to a reception time of the third information and the second time domain resource; a duration corresponding to each time domain resource in a plurality of time domain resources, the plurality of time domain resources including the second time domain resource; and a time interval between two time domain resources that are adjacent in time domain in the plurality of time domain resources.

In some implementations, if the third information carries multiple indexes, the multiple indexes are used to indicate multiple preamble codes received by the target device, the multiple indexes include the first index, and the third information is used to indicate information about time domain resources where the multiple preamble codes corresponding to the multiple indexes are located; and/or information about channels where the multiple preamble codes corresponding to the multiple indexes are located.

In some implementations, the information of the time domain resources where the multiple preamble codes are located includes indexes of the time domain resources where the multiple preamble codes are located, and the indexes of the time domain resources where the multiple preamble codes are located increase in order from early to late in the time domain.

In some implementations, the multiple preamble codes are sent by multiple terminal devices, and the time domain resources where the multiple preamble codes are located correspond one-to-one to the time domain resources where the multiple terminal devices send multiple terminal device identifiers.

In some implementations, the order in which the multiple terminal devices send preamble codes on the multiple time domain resources is the same as the order in which the multiple terminal devices send terminal device identifications on the multiple time domain resources.

In some implementations, the third information channel is a broadcast channel.

In some implementations, the first terminal device receives the third information within a first time period, and a starting position of the first time period is determined based on a sending time of the preamble code.

In some implementations, the starting position of the first time period is the sending time of the preamble code, or the starting position of the first time period is separated from the sending time of the preamble code by a first time interval.

In some implementations, when the third information is not received within the first time period, conflict resolution of the first terminal device fails.

In some implementations, the terminal device is the first terminal device, the first terminal device corresponds to a first terminal device identifier, the first terminal device receives the first information within a second time period, and the starting position of the second time period is determined based on the sending time of the first terminal device identifier.

In some implementations, the starting position of the second time period is the sending time of the first terminal device identifier, or the second The start position of the time period is separated from the sending time of the first terminal device identifier by a second time interval.

In some implementations, if the first information is not received within the second time period, conflict resolution of the first terminal device fails.

In some implementations, the terminal device is the first terminal device, the first terminal device corresponds to a first terminal device identifier, and a channel for sending the preamble code is the same as a channel for sending the first terminal device identifier.

In an optional embodiment, the sending unit 1610 and the receiving unit 1620 may be a transceiver 1830. The terminal device 1600 may further include a processor 1810 and a memory 1820, as specifically shown in FIG. 18 .

In an optional embodiment, the sending unit 1710 and the receiving unit 1720 may be a transceiver 1830. The communication device 1700 may further include a processor 1810 and a memory 1820, as specifically shown in FIG. 18 .

FIG18 is a schematic structural diagram of a communication device according to an embodiment of the present application. The dotted lines in FIG18 indicate that the unit or module is optional. The device 1800 may be used to implement the method described in the above method embodiment. The device 1800 may be a chip, a terminal device, or a network device.

The device 1800 may include one or more processors 1810. The processor 1810 may support the device 1800 to implement the method described in the above method embodiment. The processor 1810 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 also be other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

The apparatus 1800 may further include one or more memories 1820. The memory 1820 stores a program, which can be executed by the processor 1810, so that the processor 1810 executes the method described in the above method embodiment. The memory 1820 may be independent of the processor 1810 or integrated in the processor 1810.

The apparatus 1800 may further include a transceiver 1830. The processor 1810 may communicate with other devices or chips through the transceiver 1830. For example, the processor 1810 may transmit and receive data with other devices or chips through the transceiver 1830.

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 or network device provided in the present application, and the program enables a computer to execute the method performed by the terminal or network device in each embodiment of the present application.

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

The embodiment of the present application also provides a computer program. The computer program can be applied to the terminal or network device provided in the embodiment of the present application, and the computer program enables a computer to execute the method executed by the terminal 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 the present application, and are not intended to limit the present 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 of their variations are intended to cover non-exclusive inclusions.

In the embodiments of the present application, the "indication" mentioned can be a direct indication, an indirect indication, or an indication of an association relationship. For example, A indicates B, which 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 relationship 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 according to A. However, it should be understood that determining B according to A does not mean determining B only according to A, and B can also be determined according to A and/or other information.

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

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

In the embodiments of the present application, the “protocol” may refer to a standard protocol in the communication 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 the present application, the term "and/or" is only a description of the association relationship of the associated objects, indicating that there can be three relationships. 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 article generally indicates that the associated objects before and after 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. Implementation. For example, the device embodiments described above are only schematic, for example, the division of the units is only a logical function division, and there may be other division methods in actual implementation, 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 separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated 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 by software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium may 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 video disc (DVD)), or a semiconductor medium (e.g., a solid state disk (SSD)), etc.

The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims (125)

A wireless communication method, comprising: The first terminal device sends a preamble code to the target device; The first terminal device receives a first index sent by the target device, where the first index is used to indicate a preamble received by the target device; In response to the first index being the same as the index of the preamble code, the first terminal device sends a first terminal device identifier to the target device; The first terminal device receives first information sent by the target device, where the first information includes a terminal device identifier received by the target device; Wherein, the target device includes a network device and/or a second terminal device. The method according to claim 1, characterized in that the method further comprises: If the terminal device identifier in the first information matches the first terminal device identifier, the first terminal device confirms that the conflict is resolved successfully; and/or If the terminal device identifier in the first information does not match the first terminal device identifier, the first terminal device confirms that the conflict resolution has failed. The method according to claim 1 or 2 is characterized in that the first information also includes a first wireless network temporary identifier RNTI associated with the terminal device identifier. The method according to claim 3, characterized in that the method further comprises: When the first terminal device confirms that the conflict is resolved successfully, the first terminal device retains the first wireless network temporary identifier RNTI associated with the first terminal device identifier. The method according to claim 3 or 4, characterized in that the method further comprises: The first terminal device receives configuration information sent by the target device, where the configuration information is used to configure the length of the first RNTI for the first terminal device. The method according to any one of claims 1 to 5, characterized in that the first terminal device identifier is generated by the first terminal device. The method according to any one of claims 1 to 6, characterized in that the method further comprises: The first terminal device receives second information sent by the target device, where the second information is used to instruct the first terminal device to send the preamble code, and the second information is information that is sent non-periodically, or the second information is information that is sent periodically. The method as claimed in claim 7 is characterized in that the first time domain resource for sending the preamble code is determined based on a reference time domain resource, and the reference time domain resource is used to receive the second information. The method according to claim 8, wherein the first time domain resource is determined based on the reference time domain resource and a resource configuration parameter, and the resource configuration parameter is used to indicate one or more of the following: A time domain offset between the reference time domain resource and the first time domain resource; a duration corresponding to each time domain resource of a plurality of time domain resources, the plurality of time domain resources including the first time domain resource; A time interval between two time domain resources that are adjacent in the time domain among the multiple time domain resources; The number of time domain resources of the multiple time domain resources. The method according to claim 9, characterized in that the resource configuration parameters are carried in the second information. The method as described in any one of claims 7-10 is characterized in that the second information includes a power adjustment parameter, and the power adjustment parameter is used to adjust the transmission power of the preamble code and/or the transmission power of the first terminal device identifier. The method according to any one of claims 1-7 is characterized in that the time domain resource for sending the first terminal device identifier is randomly selected by the first terminal device. The method according to any one of claims 1 to 12, wherein the first index is carried in third information, and the third information includes one or more of the following: Information used to instruct the first terminal device to access the network based on the backoff mechanism; Parameters used by the first terminal device to access the network based on the backoff mechanism; Information used to indicate a second time domain resource for sending the first terminal device identifier. The method according to claim 13, characterized in that, if the third information includes the parameter, the parameter is used to indicate the maximum number of times the first terminal device attempts to access the target device; and/or The first terminal device attempts to access the target device again. The method according to claim 14, characterized in that if the parameter is used to indicate the maximum number of times, the method further comprises: If the first terminal device confirms that the conflict resolution fails and the number of times the first terminal device attempts to access the target device is less than the maximum number, the first terminal device listens to the second information again. The method according to claim 14 or 15, characterized in that if the parameter is used to indicate the maximum number of times, the method further comprises: If the first terminal device confirms that the conflict resolution fails, and the number of times the first terminal device attempts to access the target device is greater than or equal to the maximum number, the first terminal device confirms that the access to the target device has failed. The method according to claim 14, characterized in that if the parameter is used to indicate the backoff time information, the method further comprises: The first terminal device re-listens to the second information at a first moment, where the first moment is a moment starting from a moment when the first terminal device fails to resolve the conflict and after a time duration indicated by the backoff time information has elapsed. The method according to any one of claims 13 to 17, wherein if the third information is used to indicate the second time domain resource for sending the first terminal device identifier, the third information includes one or more of the following: Used to indicate a time domain offset between a time domain resource corresponding to a reception time of the third information and the second time domain resource; a duration corresponding to each time domain resource of a plurality of time domain resources, the plurality of time domain resources including the second time domain resource; The time interval between two time domain resources that are adjacent in the time domain among the multiple time domain resources. The method as described in any one of claims 13-18 is characterized in that if the third information carries multiple indexes, the multiple indexes are used to indicate multiple preamble codes received by the target device, the multiple indexes include the first index, and the third information is used to indicate information about time domain resources where the multiple preamble codes corresponding to the multiple indexes are located; and/or information about channels where the multiple preamble codes corresponding to the multiple indexes are located. The method as claimed in claim 19 is characterized in that the information of the time domain resources where the multiple preamble codes are located includes the index of the time domain resources where the multiple preamble codes are located, and the index of the time domain resources where the multiple preamble codes are located increases in order from early to late in the time domain. The method as claimed in claim 20 is characterized in that the multiple preamble codes are sent by multiple terminal devices, and the time domain resources where the multiple preamble codes are located correspond one-to-one to the time domain resources where the multiple terminal devices send multiple terminal device identifiers. The method as claimed in claim 21 is characterized in that the order in which the multiple terminal devices send preamble codes on multiple time domain resources is the same as the order in which the multiple terminal devices send terminal device identifiers on multiple time domain resources. The method according to any one of claims 13 to 22, characterized in that the third information channel for sending is a broadcast channel. The method as described in any one of claims 13-23 is characterized in that the first terminal device receives the third information within a first time period, and the starting position of the first time period is determined based on the sending time of the preamble code. The method according to claim 24, characterized in that the starting position of the first time period is the sending time of the preamble code, or A first time interval is between the start position of the first time period and the sending time of the preamble code. The method according to claim 24 or 25, characterized in that the method further comprises: If the third information is not received within the first time period, the first terminal device confirms that the conflict resolution has failed. The method according to any one of claims 1-26 is characterized in that the first terminal device receives the first information within a second time period, and the starting position of the second time period is determined based on the sending time of the first terminal device identifier. The method according to claim 27, wherein the starting position of the second time period is the sending time of the first terminal device identifier, or A second time interval exists between the start position of the second time period and the sending time of the first terminal device identifier. The method according to claim 27 or 28, characterized in that the method further comprises: If the first information is not received within the second time period, the first terminal device confirms that the conflict resolution has failed. The method according to any one of claims 1-29 is characterized in that the channel for sending the preamble code is the same as the channel for sending the first terminal device identifier. A random access method, characterized by comprising: The target device receives the preamble sent by the first terminal device; The target device sends a first index to the first terminal device, where the first index is used to indicate a preamble received by the target device; The target device receives the terminal device identification sent by the terminal device; The target device sends first information to the terminal device, where the first information includes a terminal device identifier received by the target device; Wherein, the target device includes a network device and/or a second terminal device. The method according to claim 31, wherein the terminal device includes the first terminal device, and the first terminal device corresponds to a first terminal device identifier, If the terminal device identifier in the first information matches the first terminal device identifier, the conflict of the first terminal device is resolved successfully; and/or If the terminal device identifier in the first information does not match the first terminal device identifier, conflict resolution of the first terminal device fails. The method as claimed in claim 31 or 32 is characterized in that the first information also includes a first wireless network temporary identifier RNTI associated with the terminal device identifier. The method as claimed in claim 33 is characterized in that, when the conflict of the first terminal device is successfully resolved, the target device communicates with the first terminal device based on the first RNTI. The method according to claim 33 or 34, characterized in that the method further comprises: The target device sends configuration information to the first terminal device, where the configuration information is used to configure the length of the first RNTI for the first terminal device. The method as described in any one of claims 31-35 is characterized in that the first terminal device corresponds to a first terminal device identifier, and the first terminal device identifier is generated by the first terminal device. The method according to any one of claims 31 to 36, characterized in that the method further comprises: The target device sends second information to the first terminal device, where the second information is used to instruct the first terminal device to send the preamble code, and the second information is information that is sent non-periodically. The method as claimed in claim 37 is characterized in that the first time domain resource for sending the preamble code is determined based on a reference time domain resource, and the reference time domain resource is used to receive the second information. The method of claim 38, wherein the first time domain resource is determined based on the reference time domain resource and a resource configuration parameter, and the resource configuration parameter is used to indicate one or more of the following: A time domain offset between the reference time domain resource and the first time domain resource; a duration corresponding to each time domain resource of a plurality of time domain resources, the plurality of time domain resources including the first time domain resource; A time interval between two time domain resources that are adjacent in the time domain among the multiple time domain resources; The number of time domain resources of the multiple time domain resources. The method as claimed in claim 39 is characterized in that the resource configuration parameters are carried in the second information. The method as described in any one of claims 37-40 is characterized in that the second information includes a power adjustment parameter, and the power adjustment parameter is used to adjust the transmission power of the preamble code and/or the transmission power of the terminal device identifier. The method as described in any one of claims 31-37 is characterized in that the time domain resources for receiving the terminal device identifier are randomly selected by the terminal device corresponding to the terminal device identifier, and the terminal device corresponding to the terminal device identifier includes the first terminal device. The method according to any one of claims 31 to 42, wherein the first index is carried in third information, and the third information includes one or more of the following: Information used to instruct the terminal device to access the target device based on a backoff mechanism; Parameters for the terminal device to access the target device based on the backoff mechanism; Used to instruct the terminal device to send information of a second time domain resource corresponding to the terminal device identifier of the terminal device. The method of claim 43, wherein if the third information includes the parameter, the parameter is used to indicate the maximum number of times the terminal device attempts to access the target device; and/or The terminal device attempts to access the target device again. The method as claimed in claim 44 is characterized in that if the parameter is used to indicate the maximum number of times, then when the conflict resolution of the first terminal device fails and the number of times the first terminal device attempts to access the target device is greater than or equal to the maximum number of times, the first terminal device fails to access the target device. The method as claimed in claim 44 is characterized in that if the parameter is used to indicate the backoff time information, the first moment is the moment when the first terminal device re-listens to the second information, and the first moment is the moment after the time indicated by the backoff time information, starting from the moment when the conflict resolution of the first terminal device fails. The method according to any one of claims 43 to 46, wherein if the third information is used to indicate a second time domain resource for receiving the terminal device identifier, the third information includes one or more of the following: Used to indicate a time domain offset between a time domain resource corresponding to a reception time of the third information and the second time domain resource; a duration corresponding to each time domain resource of a plurality of time domain resources, the plurality of time domain resources including the second time domain resource; The time interval between two time domain resources that are adjacent in the time domain among the multiple time domain resources. The method as described in any one of claims 43-47 is characterized in that if the third information carries multiple indexes, the multiple indexes are used to indicate multiple preamble codes received by the target device, the multiple indexes include the first index, and the third information is used to indicate the time domain resources where the multiple preamble codes corresponding to the multiple indexes are located; and/or the time domain resources where the multiple preamble codes corresponding to the multiple indexes are located. Information on the channel. The method as claimed in claim 48 is characterized in that the information of the time domain resources where the multiple preamble codes are located includes the indexes of the time domain resources where the multiple preamble codes are located, and the indexes of the time domain resources where the multiple preamble codes are located increase in order from early to late in the time domain. The method as claimed in claim 49 is characterized in that the multiple preamble codes are sent by multiple terminal devices, and the time domain resources where the multiple preamble codes are located correspond one-to-one to the time domain resources where the multiple terminal devices send multiple terminal device identifiers. The method as claimed in claim 50 is characterized in that the order in which the multiple terminal devices send preamble codes on multiple time domain resources is the same as the order in which the multiple terminal devices send terminal device identifiers on multiple time domain resources. The method according to any one of claims 43 to 51, characterized in that the third information channel for sending is a broadcast channel. The method as described in any one of claims 43-52 is characterized in that the first terminal device receives the third information within a first time period, and the starting position of the first time period is determined based on the sending time of the preamble code. The method of claim 53, wherein the starting position of the first time period is the sending time of the preamble code, or A first time interval is between the start position of the first time period and the sending time of the preamble code. The method as claimed in claim 53 or 54 is characterized in that, when the third information is not received within the first time period, the conflict resolution of the first terminal device fails. The method as described in any one of claims 31-55 is characterized in that the terminal device is the first terminal device, the first terminal device corresponds to a first terminal device identifier, the first terminal device receives the first information within a second time period, and the starting position of the second time period is determined based on the sending time of the first terminal device identifier. The method of claim 56, wherein the starting position of the second time period is the sending time of the first terminal device identifier, or A second time interval exists between the start position of the second time period and the sending time of the first terminal device identifier. The method as claimed in claim 56 or 57 is characterized in that if the first information is not received within the second time period, the conflict resolution of the first terminal device fails. The method as described in any one of claims 31-58 is characterized in that the terminal device is the first terminal device, the first terminal device corresponds to a first terminal device identifier, and the channel for sending the preamble code is the same as the channel for sending the first terminal device identifier. A terminal device, characterized in that the terminal device is a first terminal device, comprising: A sending unit, used for sending a preamble code to a target device; A receiving unit, configured to receive a first index sent by the target device, where the first index is used to indicate a preamble received by the target device; The sending unit is configured to send a first terminal device identifier to the target device in response to the first index being the same as the index of the preamble; The receiving unit is configured to receive first information sent by the target device, wherein the first information includes a terminal device identifier received by the target device; Wherein, the target device includes a network device and/or a second terminal device. The terminal device according to claim 60, characterized in that the terminal device comprises: A first processing unit is configured to confirm that the conflict is successfully resolved when the terminal device identifier in the first information matches the first terminal device identifier; and/or The second processing unit is configured to confirm that the conflict resolution fails when the terminal device identifier in the first information does not match the first terminal device identifier. The terminal device as described in claim 60 or 61 is characterized in that the first information also includes a first wireless network temporary identifier RNTI associated with the terminal device identifier. The terminal device as described in claim 62 is characterized in that the receiving unit is also used to receive configuration information sent by the target device, and the configuration information is used to configure the length of the first RNTI for the first terminal device. The terminal device according to claim 62 or 63, characterized in that the terminal device further comprises: The third processing unit is used to retain the first RNTI associated with the first terminal device identifier when the first terminal device confirms that the conflict is successfully resolved. The terminal device as described in any one of claims 60-64 is characterized in that the first terminal device identifier is generated by the first terminal device. The terminal device as described in any one of claims 60-65 is characterized in that the receiving unit is also used to receive second information sent by the target device, the second information is used to instruct the first terminal device to send the preamble code, the second information is information sent non-periodically, or the second information is information sent periodically. The terminal device according to claim 66, characterized in that the first time domain resource for sending the preamble is based on a reference time domain resource. The reference time domain resource is determined by a time domain resource, and the reference time domain resource is used to receive the second information. The terminal device according to claim 67, wherein the first time domain resource is determined based on the reference time domain resource and a resource configuration parameter, and the resource configuration parameter is used to indicate one or more of the following: A time domain offset between the reference time domain resource and the first time domain resource; a duration corresponding to each time domain resource of a plurality of time domain resources, the plurality of time domain resources including the first time domain resource; A time interval between two time domain resources that are adjacent in the time domain among the multiple time domain resources; The number of time domain resources of the multiple time domain resources. The terminal device as described in claim 68 is characterized in that the resource configuration parameters are carried in the second information. The terminal device as described in any one of claims 66-69 is characterized in that the second information includes a power adjustment parameter, and the power adjustment parameter is used to adjust the transmission power of the preamble code and/or the transmission power of the first terminal device identifier. The terminal device as described in any one of claims 60-66 is characterized in that the time domain resource for sending the first terminal device identifier is randomly selected by the first terminal device. The terminal device according to any one of claims 60 to 71, wherein the first index is carried in third information, and the third information includes one or more of the following: Information used to instruct the first terminal device to access the network based on the backoff mechanism; Parameters used by the first terminal device to access the network based on the backoff mechanism; Information used to indicate a second time domain resource for sending the first terminal device identifier. The terminal device as described in claim 72 is characterized in that if the third information includes the parameter, the parameter is used to indicate the maximum number of times the first terminal device attempts to access the target device; and/or The first terminal device attempts to access the target device again. The terminal device as claimed in claim 73, characterized in that if the parameter is used to indicate the maximum number of times, The receiving unit is further configured to re-monitor the second information when the first terminal device confirms that the conflict resolution fails and the number of times the first terminal device attempts to access the target device is less than the maximum number. The terminal device according to claim 73 or 74, characterized in that if the parameter is used to indicate the maximum number of times, the terminal device further includes: The fourth processing unit is further used to confirm that access to the target device has failed when the first terminal device confirms that conflict resolution has failed and the number of times the first terminal device attempts to access the target device is greater than or equal to the maximum number. The terminal device as claimed in claim 73, characterized in that if the parameter is used to indicate the backoff time information, The receiving unit is used to re-listen to the second information at a first moment, where the first moment is a moment starting from the moment when the first terminal device confirms that the conflict resolution has failed and after a time period indicated by the backoff time information has passed. The terminal device according to any one of claims 72 to 76, characterized in that if the third information is used to indicate the second time domain resource for sending the first terminal device identifier, the third information includes one or more of the following: Used to indicate a time domain offset between a time domain resource corresponding to a reception time of the third information and the second time domain resource; a duration corresponding to each time domain resource of a plurality of time domain resources, the plurality of time domain resources including the second time domain resource; The time interval between two time domain resources that are adjacent in the time domain among the multiple time domain resources. The terminal device as described in any one of claims 72-77 is characterized in that if the third information carries multiple indexes, the multiple indexes are used to indicate multiple preamble codes received by the target device, the multiple indexes include the first index, and the third information is used to indicate information about time domain resources where the multiple preamble codes corresponding to the multiple indexes are located; and/or information about channels where the multiple preamble codes corresponding to the multiple indexes are located. The terminal device as described in claim 78 is characterized in that the information of the time domain resources where the multiple preamble codes are located includes the indexes of the time domain resources where the multiple preamble codes are located, and the indexes of the time domain resources where the multiple preamble codes are located increase in order from early to late in the time domain. The terminal device as described in claim 79 is characterized in that the multiple preamble codes are sent by multiple terminal devices, and the time domain resources where the multiple preamble codes are located correspond one-to-one to the time domain resources where the multiple terminal devices send multiple terminal device identifiers. The terminal device as described in claim 80 is characterized in that the order in which the multiple terminal devices send preamble codes on multiple time domain resources is the same as the order in which the multiple terminal devices send terminal device identifiers on multiple time domain resources. The terminal device as described in any one of claims 72-81 is characterized in that the third information channel for sending is a broadcast channel. The terminal device as described in any one of claims 72-82 is characterized in that the first terminal device receives the third information within a first time period, and the starting position of the first time period is determined based on the sending time of the preamble code. The terminal device as described in claim 83 is characterized in that the starting position of the first time period is the sending time of the preamble code, or the starting position of the first time period is separated from the sending time of the preamble code by a first time interval. The terminal device according to claim 83 or 84, characterized in that the terminal device further comprises: If the third information is not received within the first time period, the fifth processing unit is configured to confirm that the conflict resolution fails. The terminal device as described in any one of claims 60-85 is characterized in that the first terminal device receives the first information within a second time period, and the starting position of the second time period is determined based on the sending time of the first terminal device identifier. The terminal device according to claim 86, characterized in that the starting position of the second time period is the sending time of the first terminal device identification, or A second time interval exists between the start position of the second time period and the sending time of the first terminal device identifier. The terminal device according to claim 86 or 87, characterized in that the terminal device further comprises: If the first information is not received within the second time period, the sixth processing unit is configured to confirm that the conflict resolution fails. The terminal device as described in any one of claims 60-88 is characterized in that the channel for sending the preamble code is the same as the channel for sending the first terminal device identifier. A communication device, characterized in that the communication device is a target device, comprising: A receiving unit, configured to receive a preamble sent by a first terminal device; A sending unit, configured to send a first index to the first terminal device, where the first index is used to indicate a preamble code received by a target device; The receiving unit is used to receive the terminal device identification sent by the terminal device; The sending unit is used to send first information to the terminal device, where the first information includes a terminal device identifier received by the target device; Wherein, the target device includes a network device and/or a second terminal device. The communication device according to claim 90, characterized in that the terminal device includes the first terminal device, and the first terminal device corresponds to a first terminal device identifier, If the terminal device identifier in the first information matches the first terminal device identifier, the conflict of the first terminal device is resolved successfully; and/or If the terminal device identifier in the first information does not match the first terminal device identifier, conflict resolution of the first terminal device fails. The communication device as described in claim 90 or 91 is characterized in that the first information also includes a first wireless network temporary identifier RNTI associated with the terminal device identifier. The communication device as described in claim 91 is characterized in that, when the conflict of the first terminal device is successfully resolved, the target device communicates with the first terminal device based on the first RNTI. The communication device as described in claim 92 is characterized in that the sending unit is used to send configuration information to the first terminal device, and the configuration information is used to configure the length of the first RNTI for the first terminal device. The communication device as described in any one of claims 90-94 is characterized in that the first terminal device corresponds to a first terminal device identifier, and the first terminal device identifier is generated by the first terminal device. The communication device as described in any one of claims 90-95 is characterized in that the sending unit is used to send second information to the first terminal device, the second information is used to instruct the first terminal device to send the preamble code, the second information is information that is sent non-periodically, or the second information is information that is sent periodically. The communication device as described in claim 96 is characterized in that the first time domain resource for sending the preamble code is determined based on a reference time domain resource, and the reference time domain resource is used to receive the second information. The communication device according to claim 97, characterized in that the first time domain resource is determined based on the reference time domain resource and a resource configuration parameter, and the resource configuration parameter is used to indicate one or more of the following: A time domain offset between the reference time domain resource and the first time domain resource; a duration corresponding to each time domain resource of a plurality of time domain resources, the plurality of time domain resources including the first time domain resource; A time interval between two time domain resources that are adjacent in the time domain among the multiple time domain resources; The number of time domain resources of the multiple time domain resources. The communication device as described in claim 98 is characterized in that the resource configuration parameter is carried in the second information. The communication device as described in any one of claims 95-99 is characterized in that the second information includes a power adjustment parameter, and the power adjustment parameter is used to adjust the transmission power of the preamble code and/or the transmission power of the terminal device identifier. The communication device as described in any one of claims 90-96 is characterized in that the time domain resources for receiving the terminal device identifier are randomly selected by the terminal device corresponding to the terminal device identifier, and the terminal device corresponding to the terminal device identifier includes the first terminal device. The communication device according to any one of claims 90 to 101, wherein the first index is carried in third information, and the third information includes one or more of the following: Information used to instruct the terminal device to access the target device based on a backoff mechanism; Parameters for the terminal device to access the target device based on the backoff mechanism; Used to instruct the terminal device to send information of a second time domain resource corresponding to the terminal device identifier of the terminal device. The communication device as described in claim 102, characterized in that if the third information includes the parameter, the parameter is used to indicate the maximum number of times the terminal device attempts to access the target device; and/or The terminal device attempts to access the target device again. The communication device as described in claim 103 is characterized in that if the parameter is used to indicate the maximum number of times, then when the first terminal device fails to resolve the conflict and the number of times the first terminal device attempts to access the target device is greater than or equal to the maximum number of times, the first terminal device fails to access the target device. The communication device as described in claim 103 or 104 is characterized in that if the parameter is used to indicate the backoff time information, the first moment is the moment when the first terminal device re-listens to the second information, and the first moment is the moment after the time indicated by the backoff time information, starting from the moment when the first terminal device fails to resolve the conflict. The communication device according to any one of claims 102 to 105, characterized in that if the third information is used to indicate the second time domain resource for receiving the terminal device identifier, the third information includes one or more of the following: Used to indicate a time domain offset between a time domain resource corresponding to a reception time of the third information and the second time domain resource; a duration corresponding to each time domain resource of a plurality of time domain resources, the plurality of time domain resources including the second time domain resource; The time interval between two time domain resources that are adjacent in the time domain among the multiple time domain resources. The communication device as described in any one of claims 101-106 is characterized in that if the third information carries multiple indexes, the multiple indexes are used to indicate multiple preamble codes received by the target device, the multiple indexes include the first index, and the third information is used to indicate information about time domain resources where the multiple preamble codes corresponding to the multiple indexes are located; and/or information about channels where the multiple preamble codes corresponding to the multiple indexes are located. The communication device as described in claim 107 is characterized in that the information of the time domain resources where the multiple preamble codes are located includes the indexes of the time domain resources where the multiple preamble codes are located, and the indexes of the time domain resources where the multiple preamble codes are located increase in order from early to late in the time domain. The communication device as described in claim 108 is characterized in that the multiple preamble codes are sent by multiple terminal devices, and the time domain resources where the multiple preamble codes are located correspond one-to-one to the time domain resources where the multiple terminal devices send multiple terminal device identifiers. The communication device as described in claim 109 is characterized in that the order in which the multiple terminal devices send preamble codes on multiple time domain resources is the same as the order in which the multiple terminal devices send terminal device identifiers on multiple time domain resources. The communication device as described in any one of claims 102-110 is characterized in that the third information channel for sending is a broadcast channel. The communication device as described in any one of claims 102-111 is characterized in that the first terminal device receives the third information within a first time period, and the starting position of the first time period is determined based on the sending time of the preamble code. The communication device as described in claim 112 is characterized in that the starting position of the first time period is the sending time of the preamble code, or the starting position of the first time period is separated from the sending time of the preamble code by a first time interval. The communication device as described in claim 112 or 113 is characterized in that when the third information is not received within the first time period, the conflict resolution of the first terminal device fails. The communication device as described in any one of claims 90-114 is characterized in that the terminal device is the first terminal device, the first terminal device corresponds to a first terminal device identifier, the first terminal device receives the first information within a second time period, and the starting position of the second time period is determined based on the sending time of the first terminal device identifier. The communication device according to claim 115, characterized in that the starting position of the second time period is the sending time of the first terminal device identifier, or A second time interval exists between the start position of the second time period and the sending time of the first terminal device identifier. The communication device as described in claim 115 or 116 is characterized in that if the first information is not received within the second time period, the conflict resolution of the first terminal device fails. The communication device as described in any one of claims 90-117 is characterized in that the terminal device is the first terminal device, the first terminal device corresponds to a first terminal device identifier, and the channel for sending the preamble code is the same as the channel for sending the first terminal device identifier. A terminal device, characterized in that the terminal device is a first terminal device, comprising a transceiver, a memory and a processor, the memory being used to store programs, the processor being used to call the programs in the memory and control the transceiver to receive or send signals so that the terminal device executes the method as described in any one of claims 1 to 30. A communication device, characterized in that the communication device is a target device, including a transceiver, a memory and a processor, the memory is used to store programs, the processor is used to call the programs in the memory and control the transceiver to receive or send signals so that the network device executes the method described in any one of claims 31-59. A device, characterized in that it includes a processor for calling a program from a memory so that the device executes the method of claim The method of any one of claims 1-59. 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 a method as described in any one of claims 1 to 59. A computer-readable storage medium, characterized in that a program is stored thereon, wherein the program enables a computer to execute the method as described in any one of claims 1-59. 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 59. A computer program, characterized in that the computer program enables a computer to execute the method according to any one of claims 1 to 59.