Method of wireless communication and communication device

Abstract

Provided are a wireless communication method and a communication device. The method comprises: a first terminal device sending a first terminal device identifier to a target device; and the first terminal device receiving first information sent by the target device, the first information comprising a terminal device identifier received by the target device, wherein the target device comprises a network device and / or a second terminal device. In the embodiments of the present application, the first terminal device can perform a random access process based on the first terminal device identifier, which helps to reduce the power consumption of the terminal device in the random access process compared with a conventional random access process.

Description

Wireless communication method and communication device Technical Field

[0001] The present application relates to the field of communication technology, and more specifically, to a wireless communication method and communication device. Background Art

[0002] The traditional random access process is overly complex and may result in high power consumption by terminal devices. In some scenarios, low-capability terminal devices (for example, the electronic tags mentioned above) are introduced to reduce terminal device power consumption. Compared to traditional terminal devices, these terminal devices may support simpler communication methods. In this case, if these terminal devices still use the traditional random access method to access the network device, the power consumption of the terminal device may increase.

[0003] Summary of the Invention

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

[0005] In a first aspect, a method for wireless communication is provided, comprising: a first terminal device sends a first terminal device identifier to a 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.

[0006] In a second aspect, a method for wireless communication is provided, including: a target device receives a first terminal device identifier sent by a first terminal device; the target device sends first information, the first information including the terminal device identifier received by the target device, wherein the target device includes the network device and / or the second terminal device.

[0007] In a third aspect, a terminal device is provided, which is a first terminal device and includes: a sending unit for sending a first terminal device identifier to a target device; a receiving unit for receiving 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.

[0008] In a fourth aspect, a communication device is provided, which is a target device and includes: a receiving unit for receiving a first terminal device identifier sent by a first terminal device; a sending unit for sending first information, 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.

[0009] 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 program in the memory so that the terminal device executes part or all of the steps in the method of the first aspect.

[0010] In the 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 program in the memory so that the communication device executes part or all of the steps in the method of the second aspect.

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

[0012] 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 target device) to execute part or all of the steps in the methods of the above aspects.

[0013] In a ninth aspect, embodiments of the present application provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program, wherein the computer program is operable to cause a communication device (e.g., a terminal device or a target device) to perform some or all of the steps of the methods described in each of the above aspects. In some implementations, the computer program product can be a software installation package.

[0014] 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.

[0015] In an embodiment of the present application, the first terminal device can perform a random access process based on the first terminal device identifier, which helps to reduce the power consumption of the terminal device during the random access process compared to the traditional random access process. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] FIG1 is a wireless communication system 100 used in an embodiment of the present application.

[0017] FIG2A is a schematic diagram of a conventional four-step random access process.

[0018] FIG2B is a flowchart of a non-contention-based random access process.

[0019] FIG2C is a schematic diagram of a conventional two-step random access process.

[0020] FIG2D is a flow chart of another conventional two-step random access process.

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

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

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

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

[0025] FIG7 shows a schematic flow chart of an initial access process of radio frequency identification (RFID).

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

[0027] FIG9 is a schematic diagram of a method for indicating a first time domain resource in an embodiment of the present application.

[0028] FIG10 is a schematic flowchart of a random access method according to an embodiment of the present application.

[0029] FIG11 is a schematic flowchart of a random access method according to another embodiment of the present application.

[0030] FIG12 is a schematic flowchart of a random access method according to another embodiment of the present application.

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

[0032] FIG14 is a schematic diagram of a terminal device according to an embodiment of the present application.

[0033] FIG15 is a schematic diagram of a communication device according to an embodiment of the present application.

[0034] FIG16 is a schematic structural diagram of a communication device according to an embodiment of the present application. DETAILED DESCRIPTION

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

[0036] Figure 1 illustrates 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 geographic area and may communicate with the terminal device 120 within the coverage area.

[0037] 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 numbers of terminal devices within its coverage area, which is not limited in the embodiments of the present application.

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

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

[0040] The terminal device in the embodiments 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 embodiments of the present application may refer to 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 embodiments of the present application can be a mobile phone, a tablet computer, a laptop computer, a PDA, a mobile internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a 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 smart home devices communicate without relaying the communication signal through the base station.

[0041] The network device in the embodiments of the present application may be a device for communicating with a terminal device, and may also be referred to as an access network device or a radio access network device. For example, the network device may be a base station. The network device in the embodiments of the present application may refer to a radio access network (RAN) node (or device) that connects a terminal device to a wireless network. 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 and receiving point (TRP), transmitting point (TP), master station MeNB, secondary station SeNB, multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmitting node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. 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. A base station can also refer to a communication module, modem or chip used to be set in the aforementioned device or apparatus. The base station can also be a mobile switching center and a device that performs base station functions in device-to-device D2D, vehicle-to-everything (V2X), and machine-to-machine (M2M) communications, a network-side device in a 6G network, or a device that performs base station functions in future communication systems. The base station can support networks with the same or different access technologies. The embodiments of this application do not limit the specific technology and specific device form used by the network equipment.

[0042] 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.

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

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

[0045] It should be understood that all or part of the functions of the communication device in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (such as a cloud platform).

[0046] Random access process

[0047] 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 was introduced in the LTE system and is also used in the NR system. The traditional 4-step random access process is introduced below 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.

[0048] 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.

[0049] Typically, after sending a preamble, a reception window is set to wait for message 2 (Msg2) from the network device. The start and end times of the reception window are set based on configuration parameters. From the perspective of the network device, it is capable of distinguishing 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 in the same time-frequency domain, resulting in an access conflict.

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

[0051] Typically, Message 2 may be a group message, that is, Message 2 may include a random access response (RAR) message to multiple terminal devices. The addressing information of 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. The carrier type information is used to indicate whether the carrier of the preamble is a SUL carrier or a NUL carrier.

[0052] 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 a temporary identifier (temporary cell-radio network temporary identifier, T_C_RNTI) configured by the network device for the terminal device, a timing advance (for uplink synchronization), an uplink grant (UL-GRANT) for sending message 3 (message3, Msg3), and an index of the preamble received by the network device.

[0053] In some implementations, Message 2 may also include a backoff parameter to mitigate conflicts between preambles. If the terminal device decides to resend the preamble, it generates a random time based on the backoff parameter, such that the resent preamble is sent at least later than the generated random time.

[0054] 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 to the network device based on UL-GRANT, also known as "scheduled transmission". Message 3 includes the terminal device identification (also known as terminal device ID).

[0055] Typically, a terminal device can determine whether the network device has received the preamble it sent based on the RA-RNTI and the preamble index in the RAR. If the terminal device confirms that the network device has received the preamble it sent, it sends message 3 based on the UL-GRANT, which includes at least the terminal's identifier (terminal device ID). Message 3 can be addressed using the T_C_RNTI at the physical layer.

[0056] Afterwards, the terminal device may start a timer and, during the timer running, 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 included in the MAC CE of message 3 are different.

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

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

[0059] 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 may not be able to decode it (for example, when the interference levels between the messages 3 sent by multiple terminal devices are comparable). 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 it sent, 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 identifier. Afterwards, if message 4 contains its own terminal device identifier, the terminal device can confirm that the random access process is complete 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.

[0060] The random access process described above in conjunction with Figure 2A can also be called a contention-based random access process (CBRA). Some protocols also introduce a non-contention or contention-free random access process (CFRA). Figure 2B shows a flowchart of the non-contention random access process. In the non-contention random access process, the network device can allocate specific random access resources to the terminal device. Accordingly, the network device can identify the specific terminal device through the random access preamble.

[0061] As shown in Figure 2B , the network device sends RA preamble assignment information to the terminal device. Subsequently, in response to the RA preamble assignment information, the terminal device may send a preamble to the network device. Accordingly, the MAC processing 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. Accordingly, the processing in the terminal device is the same as the contention-based random access process.

[0062] 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 Messages 1 and 3 of the 4-step random access procedure into Message A, and combines the contents of Messages 2 and 4 of the 4-step random access procedure into Message B. FIG2C and FIG2D illustrate a conventional 2-step random access procedure.

[0063] As shown in Figure 2C, the terminal device sends Message A to the network device. Message A includes a preamble and a physical uplink shared channel (PUSCH), which contains the terminal device's terminal device identifier. The network device then sends Message B (also known as a "collision resolution message") to the terminal device. There are two ways to address the terminal device in Message B: Method 1 and Method 2.

[0064] 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 procedure has been successful, that is, the conflict has been resolved.

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

[0066] In mode 2, if the terminal device identifier in message A is an identifier other than the C-RNTI, then the RA-RNTI is convolved on the PDCCH carrying message B. Accordingly, if the terminal device identifier contained in the Success RAR (SuccessRAR) in message B matches the terminal device's own terminal device identifier, the terminal device considers the random access process successful and the conflict resolved. Otherwise, the terminal device can choose to resend message A or fall back to the 4-step random access process.

[0067] Generally, method 2 is applicable to scenarios other than method 1.

[0068] As shown in Figure 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 preamble and PUSCH. The terminal device then sends message A to the network device based on the allocation information, where message A includes the preamble and PUSCH, where the PUSCH includes the terminal device identifier of the terminal device. The network device then sends message B (also known as "random access response") to the terminal device.

[0069] Internet of Things (IoT) technology

[0070] The rise of IoT technology has posed new challenges to communication systems. IoT terminal devices can be used in a variety of scenarios, including logistics, warehousing, factory automation, and animal husbandry. IoT terminal devices and network equipment can perform intermittent, simple communications or perform rough location tracking. Even the simplest IoT terminal devices, such as NB-IoT devices used for coal and electricity metering, require batteries for power. However, despite their low energy consumption, the batteries within these devices only last for a few years before eventually becoming depleted. Therefore, batteries in IoT terminal devices require regular replacement, which is labor-intensive. Furthermore, some industrial scenarios present certain risks and are not suitable for manual operation. Consequently, battery-free IoT terminal devices have emerged.

[0071] Battery-free IoT terminal devices are numerous and inexpensive, and generally require no manual maintenance after installation. Radio frequency identification (RFID) terminal devices can, to some extent, meet people's demand for battery-free IoT terminal devices. However, the operation of RFID systems still requires human participation, such as the need for manual handheld readers in some RFID systems. 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 manual participation. For example, using an RFID system to take inventory of goods in a large supermarket requires a lot of manpower, material resources, and time.

[0072] Ambient IoT (A-IoT) communication system

[0073] Transplanting systems like RFID into cellular networks can effectively address the issue of limited coverage. This is because cellular networks (such as fourth-generation (4G) and 5G) systems have achieved nationwide coverage, or at least coverage of major cities, in some countries and regions (such as China, Europe, and the United States). With this wider network coverage, the communication and positioning process between IoT terminal devices and network devices can be performed without human intervention. Therefore, IoT terminal devices can operate continuously and efficiently. Furthermore, IoT terminal devices can even operate efficiently in environments unsuitable for human intervention (such as wilderness, mines, and factories). Therefore, when using IoT terminal devices, apart from the initial need to associate the IoT terminal device with a specific object, subsequent data reading, writing, and operation and maintenance can be performed through an app on a smartphone, which is very convenient and efficient. This type of communication system can be called an ambient IoT communication system or a zero-power communication system.

[0074] As shown in Figure 3, the A-IoT communication system can be composed of a network device 310 and a terminal device 320. The network device 310 can be, for example, a reader. The terminal device 320 is also called an A-IoT device, and can be, for example, a tag, also known as an electronic tag. Generally, 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 to the terminal device 320, and receive backscattered signals from the terminal device 320.

[0075] Continuing with FIG3 , terminal device 320 may include an energy harvesting module 321, a backscatter communication module 322, and a low-power computing module 323. In other scenarios, terminal device 320 may also include a memory module (not shown) for storing basic information (such as item identification). In other scenarios, terminal device 320 may also include a sensor module 324 for acquiring sensor data such as ambient temperature and humidity.

[0076] Some protocols discuss the use cases of A-IoT communication systems as being categorized into four main categories: inventory, sensors, tracking, and commands. Inventory refers to checking for missing items and replenishing missing items as they enter and exit the warehouse. Common sensors include temperature, pressure, and humidity. These sensors can be used in industrial, agricultural, and smart city applications. The information collected by these sensors can be uploaded to a third-party 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 their smartphones to track the real-time location of their parcels. Commands involve operating certain servos through the A-IoT system. These servos can be connected to A-IoT end devices. For example, while working or relaxing in the office, people can water their backyard plants using a mobile app. The watering servo can be connected to an A-IoT end device.

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

[0078] As shown in Figure 4B, network devices and A-IoT devices can communicate through an intermediate node. 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 this 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.

[0079] As shown in Figure 4C, network devices and A-IoT devices can communicate through auxiliary nodes. The data or information transmitted between the auxiliary node and the terminal device is also called A-IoT data or signals, and the data or information transmitted between the terminal device and the network device is also called A-IoT data or signals. The auxiliary node can be another network device. In this case, the auxiliary node can only receive data or signals sent by the network device via the Uu interface. In this case, the auxiliary node cannot send data or signals to the network device.

[0080] As shown in FIG4D , 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.

[0081] Some protocols categorize A-IoT devices into three types: Type A, Type B, and Type C. Type A and Type B devices can only communicate by reflecting and modulating received radio waves, a communication method known as backscattering. This means they cannot actively transmit radio signals, and their power ranges from 1 to 10 microwatts (μW). Type A devices have the lowest transmit power and hardware complexity, approaching the level of RFID devices. Type B devices have slightly more complex hardware and may include signal amplifiers and certain energy storage devices. Therefore, the communication distance between Type B devices and network devices is greater than that between Type A devices. Type C devices typically have the ability to actively transmit radio waves, with a transmit power of approximately 1 to 10 milliwatts (mW), and are capable of storing a certain amount of energy. All three types of devices can harvest energy from the environment and can operate continuously for several years or even more than 10 years. In addition, to save energy, Type A and Type B terminal devices are essentially dormant until a network device triggers a communication process with them. They only begin to work after being activated by a wireless signal from a network device.

[0082] Currently, A-IoT device receivers can be divided into two major types: Type 1 and Type 2. Type 1 receivers are wideband receivers, also known as RF receivers. RF receivers use RF bandpass filters to obtain signals within the intended bandwidth, then perform envelope detection and subsequent baseband processing. RF receivers have the simplest structure, with power consumption as low as a few uW or even lower. However, due to the poor precision of RF bandpass filters, even when the target signal occupies a narrow bandwidth, RF receivers often receive signals within a wider bandwidth. As a result, the RF receiver's reception process introduces significant noise and interference, resulting in poor reception performance, or in other words, poor reception sensitivity. The typical RF receiver reception process is shown in Figure 5.

[0083] Receiver type 2 is a narrowband receiver, which can include an intermediate frequency (IF) receiver or a zero-IF receiver. In addition to using an RF bandpass filter to obtain signals within the intended reception bandwidth, narrowband receivers can also downconvert the RF signal and further filter the baseband signal using a low-pass filter to eliminate noise and interference. Therefore, narrowband receivers have a narrow reception bandwidth and good reception performance, or high reception sensitivity. However, narrowband receivers require a local oscillator (LO). LO power consumption is high; even the recommended LO consumes 100uW or more. Therefore, narrowband receivers have high relative power consumption, but their absolute power consumption is very low, making them suitable for use in zero-power devices. The typical reception process of an IF receiver can be shown in Figure 6.

[0084] 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.

[0085] RFID initial access process

[0086] In some protocols, an initial access process adjusted for IoT systems is introduced. Figure 7 shows a schematic flow chart of the initial access process of RFID. The interrogator can be the network device described above. As shown in Figure 7, 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 (denoted by "RN16") to the interrogator. During this process, if another tag also sends a random number through the same channel at substantially the same time, the first collision will occur during the interrogator's reception process. If the interrogator responds with an ACK to the correctly decoded random number. For the tag, a tag that successfully conflicts will receive the same random number as it sent, while a tag that fails to conflict will receive a different random number than it sent.

[0087] A tag that successfully resolves a collision can send its EPC or related information to the interrogator. In response, the interrogator repeatedly feeds the same random number (the correctly decoded one) back to the tag via a random number request (Req_RN). The tag then returns a handle to the interrogator, which serves as the tag's identifier for subsequent processes. This handle is also a 16-bit random number. The interrogator can then send a command to the tag, including the tag's identifier.

[0088] During the initial RFID access process, the tag generates the identifier (handle) used in subsequent processes. This approach is suitable for RFID because the interrogator's coverage area is typically small, and the identifier is long enough to distinguish different RFIDs. However, this initial access process is not suitable for scenarios with larger network device coverage areas. The identifier (handle) may not be long enough for the network device to distinguish different terminal devices. Traditional random access processes are overly complex and may result in high power consumption in terminal devices. This limits the extent to which low-capability terminal devices (such as the electronic tags described above) can be introduced to reduce power consumption.

[0089] 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 described 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.

[0090] In some implementations, the target device shown in Figure 8 can be a second terminal device, in which case the first terminal device can access the network through the second terminal device. In other words, the second terminal device can serve as an auxiliary node or intermediate node for communication between the first terminal device and the network device to help the first terminal device access the network device. In other implementations, the target device can be a network device other than the network device that the terminal device is ready to access, that is, the network device serving as the target device can 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) to help the first terminal device access the network device. Of course, in an embodiment of the present application, the target device can be the network device that the terminal device attempts to access, in which case the first terminal device can communicate directly with the network device to attempt to access the network device.

[0091] 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.

[0092] In the embodiments of this application, there are no limitations on the first terminal device and the second terminal device. In some implementations, the second terminal device may have higher capabilities than the first terminal device. For example, the second terminal device may be a smart terminal device, and the first terminal device may be the electronic tag described above. In other implementations, the second terminal device may have similar capabilities to the first terminal device.

[0093] Figure 8 is a schematic flow chart of a wireless communication method according to an embodiment of the present application. The method shown in Figure 8 includes steps S810 to S820.

[0094] In step S810, the first terminal device sends a first terminal device identifier to the target device.

[0095] 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. Compared to the terminal device identifier configured by the network device for the terminal device during a traditional random access process, the first terminal device identifier is shorter, which helps to reduce the power consumption required by the first terminal device to transmit the first terminal device identifier. For example, the first terminal device identifier may be 16 bits long.

[0096] In some implementations, the transmission of the first terminal device identifier may be the first piece of information in the random access process. Therefore, the information containing the first terminal device identifier may be referred to as message A (Msg A), for example, MsgA in a two-step random access process.

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

[0098] In step S820, the target device sends first information to the first terminal device, where the first information includes a terminal device identifier received by the target device.

[0099] 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 the target device is successfully accessed to resolve the conflict.

[0100] 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 is successful and access to the target device is successful. 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.

[0101] In some implementations, the first information may further 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 for 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, i.e., use the first RNTI as the identifier of the first terminal device.

[0102] In an embodiment of the present application, the first RNTI can be carried only in the first information. At this time, the transmission of other messages in the random access process can be performed not based on RNTI. Compared with the traditional RNTI-based random access process, it 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.

[0103] 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 for random access.

[0104] 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.

[0105] 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 network device serves a large number of terminal devices, the length of the first RNTI may be longer to facilitate distinguishing between multiple terminal devices. Conversely, if the network device serves a small number of terminal devices, the length of the first RNTI may be shorter to reduce the complexity of communication by the first terminal device based on the first RNTI.

[0106] Assuming the network device is located outdoors, the number of terminal devices served by the network device may be in the tens of thousands. In this case, the length of the first RNTI may need to be 4 bytes. Assuming the network device is located indoors, the number of terminal devices served by the network device may be only a few hundred. In this case, the length of the first RNTI may only need to be 2 bytes.

[0107] In the embodiments of the present application, there is no limitation on 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 embodiments of the present application, if the length of the first RNTI can be changed by truncation, that is, an original RNTI of uniform length can be generated, and then truncation can be used to truncate the original RNTI to obtain the first RNTI.

[0108] As described above, the length of the first RNTI is variable. Therefore, to reduce the complexity for the first terminal device to obtain 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 via configuration information. In other words, the target device may send 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.

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

[0110] For example, the first time period starts at the time when the first terminal device identifier is sent. That is, after the first terminal device sends the first terminal device identifier, the first terminal device immediately enters the first time period to prepare for receiving the first information, which helps the first terminal device receive energy from other communication devices (e.g., a reader) during the first time period for subsequent communication via backscattered radio waves.

[0111] For another example, the start position of the first time period is separated from the time when the first terminal device identifier is sent by a first time interval. Alternatively, the start position of the first time period is obtained by starting at the time when the first terminal device identifier is sent and offset by the first time interval in the direction of time elapses. In other words, after the first terminal device sends the first terminal device identifier, it will wait for the first time interval before entering the first time period to prepare for receiving the first information, which helps the first terminal device save power consumption.

[0112] 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 represented by a timer.

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

[0114] Typically, 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 within a channel to save power consumption of the first terminal device when receiving the first information.

[0115] In some implementations, the first information includes one or more of the following: information for instructing the first terminal device to access the network based on the backoff mechanism; and parameters for the first terminal device to access the network based on the backoff mechanism.

[0116] Take the example where the first information includes information for indicating that the first terminal device accesses the network based on the backoff mechanism, or in other words, the first information is used to indicate that the first terminal device supports the backoff mechanism during access to the network.

[0117] Taking the first information including the above-mentioned parameter as an example, in some implementations, the parameter is used to indicate the maximum number of times the first terminal device attempts to access the network. In some implementations, if 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 less than the maximum number, the first terminal device may re-monitor the second information.

[0118] In other implementations, 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, the first terminal device may confirm that access to the target device has failed.

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

[0120] 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.

[0121] In other implementations, the above parameter is also used to indicate the backoff time information for the first terminal device to attempt to access the target device again, or in other words, the above parameter is used to indicate the time the first terminal device needs to wait before attempting to access the target device again, that is, the time interval between the time when the first terminal device next initiates a random access process 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 for the second information at a first moment, and the first moment is a moment after the time indicated by the backoff time information, starting from the time when the first terminal device confirms that the conflict resolution has failed.

[0122] In the embodiment of the present application, the above parameter may be a 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.

[0123] 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.

[0124] Therefore, to address the above-mentioned issues, an embodiment of the present application provides a wireless communication method, in which a target device can send second information to a first terminal device to trigger the first terminal device to perform a random access process. In other words, the second information is used to trigger the first terminal device to send the first terminal device identifier, wherein the second information can be transmitted aperiodically. Of course, if the above-mentioned issues are not considered, the second information can be transmitted periodically.

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

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

[0127] In some implementations, the time domain resource for sending the second information (also referred to as the "reference time domain resource") can be used to determine the time domain resource for sending the first terminal device identifier (also referred to as the "first time domain resource"). In other words, the first time domain resource is determined based on the reference time domain resource.

[0128] 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.

[0129] 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.

[0130] 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.

[0131] 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.

[0132] In the embodiments of the present application, the implementation of the 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.

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

[0134] 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, 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 the 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.

[0135] 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 9. As shown in Figure 9, 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 t1 for indicating the reference time domain resource and the first time domain resource, a duration t2 corresponding to each time domain resource in the multiple time domain resources, and a time interval 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 first time domain resource is time domain resource 0 based on the above-mentioned parameters in the resource configuration parameters.

[0136] 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.

[0137] 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, the transmission power used by the first terminal device may be increased during the process of the first terminal device attempting to access the target device multiple times. For example, during the process of the first terminal device attempting 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 of the first terminal device attempting 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 P. N , then P N It can be determined by the following formula: N =P+N×ΔP.

[0138] In some implementations, the initial transmit power may be the transmit power used by the first terminal device when attempting to access the target device for the first time, in which case N is a positive integer greater than or equal to 0. Of course, in the embodiment of the present application, the transmit power used by the first terminal device when attempting to access the target device for the first time may be the sum of the initial transmit power and the power step size, in which case N is a positive integer greater than or equal to 1.

[0139] 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 first terminal device identifier during the process of the first terminal device attempting to access the target device.

[0140] 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 embodiments of the present application, the parameters for power adjustment (e.g., initial transmit power and / or power step) may be predefined or preconfigured.

[0141] In some implementations, before step S810, the method further includes: the first terminal device sending a preamble to the target device, where the preamble is used for the target device to perform uplink time synchronization and / or uplink frequency synchronization.

[0142] In the embodiment of the present application, in order to simplify the process of generating the preamble and reduce the power consumption required by the first terminal device to generate the preamble, the preamble can be fixed. Of course, if the above problem is not considered, the preamble can be generated in a traditional manner.

[0143] In some implementations, during the process of the first terminal device attempting to access the target device, the information (e.g., the second information and / or 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 first terminal device identifier) ​​sent by the first terminal device to the network device may be transmitted within a certain channel.

[0144] In some implementations, the timing at which the first terminal device sends information (e.g., the first terminal device identifier) ​​is associated with the terminal type of the first terminal device. For example, for terminal devices 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 devices of type A and / or type B start sending messages. For another example, for terminal devices 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.

[0145] In some cases, the target device may not be able to demodulate the terminal device identifiers sent by multiple terminal devices (if the terminal device identifiers sent by multiple terminal devices use similar transmission power). At this time, multiple terminal devices fail to access the target device.

[0146] In other cases, it is possible that one of the terminal device identifiers sent by multiple terminal devices is successfully demodulated, while the terminal device identifiers sent by the remaining terminal devices cannot be demodulated. If the terminal device identifiers sent by multiple terminal devices use different transmission powers, for the network device, the terminal device identifier 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 that was successfully demodulated. The terminal devices corresponding to the other terminal device identifiers that were not successfully demodulated will fail to access because they cannot wait for the first information.

[0147] For ease of understanding, the random access method of an embodiment of the present application is introduced below in conjunction with Figures 10 to 13. 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 the identification of the first terminal device, and Msg2 can be used as an example of the first information.

[0148] Figure 10 is a schematic flow chart of a random access method according to an embodiment of the present application. The method shown in Figure 10 includes steps S1010 to S1030.

[0149] In step S1010 , the network device sends Msg0 .

[0150] 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, where the multiple terminal devices include the first terminal device.

[0151] In step S1020 , in response to the first terminal device receiving Msg0 , the first terminal device sends Msg1 to the network device.

[0152] In some implementations, Msg1 includes the first terminal device identifier, where the terminal device identifier is a random number generated by the first terminal device.

[0153] In step S1030, the network device sends Msg2 to the first terminal device.

[0154] In some implementations, Msg2 includes the terminal device identifier received by the network device and a first RNTI corresponding to the terminal device identifier.

[0155] In some implementations, if the terminal device identifier carried in Msg2 includes the first terminal device identifier, the first terminal device may consider that the conflict resolution is successful. Thereafter, 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 Msg2 does not include the first terminal device identifier, the first terminal device may consider that the conflict resolution has failed.

[0156] Figure 11 is a schematic flow chart of a random access method according to another embodiment of the present application. The method shown in Figure 11 includes steps S1110 to S1130.

[0157] In step S1110 , the network device sends Msg0 .

[0158] 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, where the multiple terminal devices include the first terminal device.

[0159] In some implementations, Msg0 may include resource configuration parameters for determining a first time domain resource, wherein the first time domain resource may be used to send the first terminal device identifier. It should be understood that the method for determining the first time domain resource can be referred to as shown in FIG9 , and for the sake of brevity, it will not be repeated here.

[0160] In step S1120 , in response to the first terminal device receiving Msg0 , the first terminal device sends Msg1 to the network device on the first time domain resource.

[0161] In some implementations, Msg1 includes the first terminal device identifier, where the terminal device identifier is a random number generated by the first terminal device.

[0162] In step S1130, the network device sends Msg2 to the first terminal device.

[0163] In some implementations, Msg2 includes the terminal device identifier received by the network device and a first RNTI corresponding to the terminal device identifier.

[0164] In some implementations, if the terminal device identifier carried in Msg2 includes the first terminal device identifier, the first terminal device may consider that the conflict resolution is successful. Thereafter, 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 Msg2 does not include the first terminal device identifier, the first terminal device may consider that the conflict resolution has failed.

[0165] Figure 12 is a schematic flowchart of a random access method according to another embodiment of the present application. Assume that the first terminal device is a Type C terminal device described above. This type of terminal device can autonomously select a channel to transmit information. In some scenarios, this type of first terminal device can operate in an FDD frequency band. The method shown in Figure 12 includes steps S1210 to S1240.

[0166] In step S1210, the first terminal device sends a wake-up signal to the network device to wake up the network device.

[0167] 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 the time when the first terminal device initiates the random access process, the network device usually triggers the first terminal device to perform random access by periodically broadcasting Msg0. However, the periodic broadcast of Msg0 will result in consumption of 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 Msg0 is not found, the first terminal device can send a wake-up signal to the network device to trigger the network device to send Msg0.

[0168] In step S1220 , in response to the wake-up signal, the network device sends Msg0 .

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

[0170] In step S1230 , in response to the first terminal device receiving Msg0 , the first terminal device sends Msg1 to the network device.

[0171] In some implementations, the first terminal device may randomly select a time domain resource for sending Msg1.

[0172] In some implementations, Msg1 includes the first terminal device identifier, where the terminal device identifier is a random number generated by the first terminal device.

[0173] In step S1240, the network device sends Msg2 to the first terminal device.

[0174] In some implementations, Msg2 includes the terminal device identifier received by the network device and a first RNTI corresponding to the terminal device identifier.

[0175] In some implementations, if the terminal device identifier carried in Msg2 includes the first terminal device identifier, the first terminal device may consider that the conflict resolution is successful. Thereafter, 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 Msg2 does not include the first terminal device identifier, the first terminal device may consider that the conflict resolution has failed.

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

[0177] In step S1310 , the network device sends Msg0 .

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

[0179] 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 transmit Msg1. It should be understood that the method for determining the first time domain resource can be seen in FIG9 , and for the sake of brevity, it is not further described here. Of course, in the embodiment of the present application, Msg0 may also include frequency domain resources for transmitting Msg1.

[0180] In step S1320, in response to the first terminal device receiving Msg0, the first terminal device sends Msg1 to the network device.

[0181] In some implementations, the time domain resources for the first terminal device to send Msg1 can be determined based on the time domain resources of Msg0, or in other words, the first terminal device sends Msg1 on the transmission resources (time domain resources and / or frequency domain resources) indicated by Msg0.

[0182] In some implementations, Msg1 includes the first terminal device identifier, where the first terminal device identifier is a random number generated by the first terminal device.

[0183] In some implementations, Msg1 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 (for example, the maximum number of times the first terminal device attempts to access the target device).

[0184] In step S1330 , in response to the network device receiving the terminal device identification, the network device sends Msg2 .

[0185] In some implementations, Msg2 includes the terminal device identifier received by the network device and a first RNTI corresponding to the terminal device identifier.

[0186] In some implementations, if the terminal device identifier carried in Msg2 includes the first terminal device identifier, the first terminal device may consider that the conflict resolution is successful. Thereafter, 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 Msg2 does not include the first terminal device identifier, the first terminal device may consider that the conflict resolution has failed (i.e., see step S1340).

[0187] In step S1350, if the number of times the first terminal device currently 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, ie, re-execute steps S1310 to S1340.

[0188] In some implementations, if steps S1310 to S1340 are executed again, the time domain resource for the first terminal device to transmit the first terminal device identifier can be independently selected by the first terminal device.

[0189] In some implementations, if steps S1310 to S1340 are re-executed for the first terminal device to attempt to access the target device for the Nth time, and Msg1 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 P N , then P N It can be determined by the following formula: N =P+N×ΔP.

[0190] It should be noted that the transmission power P N It can be used to transmit Msg1 when the first terminal device attempts to access the target device for the Nth time.

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

[0192] 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.

[0193] The method embodiment of the present application is described in detail above in conjunction with Figures 1 to 13. The device embodiment of the present application is described in detail below in conjunction with Figures 14 to 16. It should be understood that the description of the method embodiment corresponds to the description of the device embodiment. Therefore, for parts not described in detail, reference can be made to the above method embodiment.

[0194] FIG14 is a schematic diagram of a terminal device according to an embodiment of the present application. The terminal device 1400 shown in FIG14 is a first terminal device, and the first terminal device includes: a sending unit 1410 and a receiving unit 1420 .

[0195] The sending unit 1410 is configured to send a first terminal device identifier to a target device;

[0196] The receiving unit 1420 is configured 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.

[0197] In some implementations, the terminal device further includes: a first processing unit for confirming that the conflict resolution is successful if the terminal device identifier in the first information is the same as the first terminal device identifier; and / or a second processing unit for confirming that the conflict resolution fails if the terminal device identifier in the first information is not the same as the first terminal device identifier.

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

[0199] In some implementations, the receiving unit is used to receive second information sent by the target device, where the second information is used to trigger the first terminal device to send the first terminal device identifier, and the second information is information that is sent non-periodically, or the second information is information that is sent periodically.

[0200] In some implementations, the first time domain resource where the first terminal device identifier is sent is determined based on a reference time domain resource, and the reference time domain resource is used to receive the second information.

[0201] 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: the time domain offset between the reference time domain resource and the first time domain resource; the 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; the 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.

[0202] In some implementations, the resource configuration parameters are carried in the second information.

[0203] 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 first terminal device identifier.

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

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

[0206] In some implementations, the terminal device further includes: a third processing unit configured to retain the first RNTI when the first terminal device confirms that the conflict resolution is successful.

[0207] 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.

[0208] In some implementations, the first information further includes: information for instructing the first terminal device to access a network based on a backoff mechanism; and / or parameters for the first terminal device to execute the backoff mechanism.

[0209] In some implementations, if the first 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.

[0210] In some implementations, if the parameter is used to indicate the maximum number of times, if 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, the receiving unit is used to re-listen for the second information.

[0211] In some implementations, if the parameter is used to indicate the maximum number of times, the terminal device also includes: if 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, the fourth processing unit is used to confirm that access to the target device has failed.

[0212] 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 the moment starting from the moment when the first terminal device confirms that the conflict resolution has failed, and the moment after the backoff time indicated by the backoff time information.

[0213] In some implementations, the first information carries multiple terminal device identifiers and an RNTI associated with each of the multiple terminal device identifiers, and the multiple first terminal device identifiers include the first terminal device identifier.

[0214] In some implementations, the first information is carried on a broadcast channel.

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

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

[0217] In some implementations, the terminal device further includes: if the first information is not received within the first time period, a fifth processing unit is configured to confirm that the conflict resolution has failed.

[0218] In some implementations, before the first terminal device sends the first terminal device identifier to the target device, the sending unit is further used to: send a preamble code to the target device, where the preamble code is used by the target device to perform uplink time synchronization and / or uplink frequency synchronization.

[0219] FIG15 is a schematic diagram of a communication device according to an embodiment of the present application. The communication device 1500 shown in FIG15 is a target device, and the communication device 1500 includes a receiving unit 1510 and a sending unit 1520 .

[0220] The receiving unit 1510 is configured to receive a first terminal device identifier sent by a first terminal device;

[0221] The sending unit 1520 is configured to send first information, where the first information includes a terminal device identifier received by a target device, wherein the target device includes a network device and / or a second terminal device.

[0222] In some implementations, if the terminal device identifier included in the first information is the same as the first terminal device identifier, the first terminal device conflict resolution is successful; and / or if the terminal device identifier included in the first information is different from the first terminal device identifier, the first terminal device conflict resolution fails.

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

[0224] In some implementations, the sending unit is used to send second information to the first terminal device, where the second information is used to trigger the first terminal device to send the first terminal device identification, and the second information is information that is sent non-periodically, or the second information is information that is sent periodically.

[0225] In some implementations, the first time domain resource where the first terminal device identifier is received is determined based on a reference time domain resource, and the reference time domain resource is used to send the second information.

[0226] 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: the time domain offset between the reference time domain resource and the first time domain resource; the 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; the 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.

[0227] In some implementations, the resource configuration parameters are carried in the second information.

[0228] 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 first terminal device identifier.

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

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

[0231] In some implementations, the sending unit is further used to send 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.

[0232] In some implementations, the first information further includes: information for instructing the first terminal device to access a network based on a backoff mechanism; and / or parameters for the first terminal device to execute the backoff mechanism.

[0233] In some implementations, if the first 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.

[0234] In some implementations, when the parameter is used to indicate the maximum number of times, if 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.

[0235] In some implementations, if the parameter is used to indicate the backoff time information, the first terminal device re-listens to the second information at a first moment, and the first moment is a moment starting from the moment when the first terminal device fails to resolve the conflict and after the backoff time indicated by the backoff time information.

[0236] In some implementations, the first information carries multiple terminal device identifiers and an RNTI associated with each of the multiple terminal device identifiers, and the multiple first terminal device identifiers include the first terminal device identifier.

[0237] In some implementations, the first information is carried on a broadcast channel.

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

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

[0240] In some implementations, if the first information is not received within the first time period, conflict resolution for the first terminal device fails.

[0241] In some implementations, before the target device receives the first terminal device identifier sent by the first terminal device, the receiving unit is further used to: receive a preamble code sent by the first terminal device, and the preamble code is used by the target device to perform uplink time synchronization and / or uplink frequency synchronization.

[0242] In an optional embodiment, the sending unit 1410 and the receiving unit 1420 may be a transceiver 1630. The terminal device 1400 may further include a processor 1610 and a memory 1620, as specifically shown in FIG16 .

[0243] In an optional embodiment, the sending unit 1510 and the receiving unit 1520 may be a transceiver 1630. The communication device 1500 may further include a processor 1610 and a memory 1620, as specifically shown in FIG16 .

[0244] Figure 16 is a schematic block diagram of a communication device according to an embodiment of the present application. The dashed lines in Figure 16 indicate that the unit or module is optional. Device 1600 may be used to implement the method described in the above method embodiment. Device 1600 may be a chip, a terminal device, or a network device.

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

[0246] The apparatus 1600 may further include one or more memories 1620. The memories 1620 store programs that can be executed by the processor 1610, causing the processor 1610 to perform the methods described in the above method embodiments. The memories 1620 may be independent of the processor 1610 or integrated into the processor 1610.

[0247] The apparatus 1600 may further include a transceiver 1630. The processor 1610 may communicate with other devices or chips via the transceiver 1630. For example, the processor 1610 may transmit and receive data with other devices or chips via the transceiver 1630.

[0248] 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.

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

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

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

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

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

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

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

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

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

[0258] 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.

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

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

[0261] 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.

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

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

Claims

1. A method for wireless communication, characterized in that, it includes: A first terminal device sends a first terminal device identifier to a target device; The first terminal device receives first information sent by the target device, where 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.

2. The method according to claim 1, characterized in that, the method further includes: If the terminal device identifier in the first information is the same as the first terminal device identifier, the first terminal device confirms that the conflict resolution is successful; and / or If the terminal device identifier in the first information is different from the first terminal device identifier, the first terminal device confirms that the conflict resolution fails.

3. The method according to claim 1 or 2, characterized in that, the first terminal device identifier is generated by the first terminal device.

4. The method according to any one of claims 1-3, characterized in that, the method further includes: The first terminal device receives second information sent by the target device, where the second information is used to trigger the first terminal device to send the first terminal device identifier, and the second information is information sent non-periodically, or the second information is information sent periodically.

5. The method according to claim 4, characterized in that, The first time domain resource where the first terminal device identifier is sent is determined based on a reference time domain resource, and the reference time domain resource is used to receive the second information.

6. The method according to claim 5, characterized in that, the first time domain resource is determined based on the reference time domain resource and resource configuration parameters, and the resource configuration parameters are used to indicate one or more of the following: The time domain offset between the reference time domain resource and the first time domain resource; The duration corresponding to each time domain resource in a plurality of time domain resources, where the plurality of time domain resources includes the first time domain resource; The time interval between two adjacent time domain resources in the time domain among the plurality of time domain resources; The number of time domain resources of the plurality of time domain resources.

7. The method according to claim 6, characterized in that, the resource configuration parameters are carried in the second information.

8. The method according to any one of claims 4-7, 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 first terminal device identifier.

9. The method according to any one of claims 1-4, characterized in that, The time domain resource for sending the first terminal device identifier is randomly selected by the first terminal device.

10. The method according to any one of claims 1-9, characterized in that, the first information further includes a first radio network temporary identifier RNTI associated with the terminal device identifier.

11. The method according to claim 10, characterized in that, the method further includes: When the first terminal device confirms that the conflict resolution is successful, the first terminal device retains the first RNTI.

12. The method according to claim 10 or 11, characterized in that, the method further includes: The first terminal device receives the 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.

13. The method according to any one of claims 1-12, characterized in that the first information further includes: information for instructing the first terminal device to access the network based on a backoff mechanism; and / or parameters for the first terminal device to execute the backoff mechanism.

14. The method according to claim 13, characterized in that if the first information includes the parameters, the parameters are used to indicate the maximum number of times the first terminal device attempts to access the target device; and / or the backoff time information for the first terminal device to attempt to access the target device again.

15. The method according to claim 14, characterized in that if the parameter is used to indicate the maximum number of times, the method further includes: 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 of times, the first terminal device re-monitors the second information.

16. 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 includes: 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 of times, the first terminal device confirms that the access to the target device fails.

17. The method according to claim 14, characterized in that if the parameter is used to indicate the backoff time information, the method further includes: the first terminal device re-monitors the second information at a first moment, where the first moment is a moment after the moment when the first terminal device confirms that the conflict resolution fails and after the backoff time indicated by the backoff time information.

18. The method according to any one of claims 1-17, characterized in that the first information carries multiple terminal device identifiers and the RNTIs associated with each of the multiple terminal device identifiers, and the multiple first terminal device identifiers include the first terminal device identifier.

19. The method according to any one of claims 1-18, characterized in that the first information is carried on a broadcast channel.

20. The method according to any one of claims 1-19, characterized in that the first terminal device receives the first information within a first time period, and the starting position of the first time period is determined based on the sending time of the first terminal device identifier.

21. The method according to claim 20, characterized in that the starting position of the first time period is the sending time of the first terminal device identifier, or there is a first time interval between the starting position of the first time period and the sending time of the first terminal device identifier.

22. The method according to claim 20 or 21, characterized in that the method further includes: if the first information is not received within the first time period, the first terminal device confirms that the conflict resolution fails.

23. The method according to any one of claims 1-22, characterized in that, before the first terminal device sends the first terminal device identifier to the target device, the method further comprises: the first terminal device sends a preamble to the target device, and the preamble is used for the target device to perform uplink time synchronization and / or uplink frequency synchronization.

24. A method for wireless communication, characterized in that, comprising: the target device receives the first terminal device identifier sent by the first terminal device; the target device sends first information, and 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.

25. The method according to claim 24, characterized in that, if the terminal device identifier included in the first information is the same as the first terminal device identifier, the conflict resolution of the first terminal device is successful; and / or if the terminal device identifier included in the first information is different from the first terminal device identifier, the conflict resolution of the first terminal device fails.

26. The method according to claim 24 or 25, characterized in that, the first terminal device identifier is generated by the first terminal device.

27. The method according to any one of claims 24-26, characterized in that, the method further comprises: the target device sends second information to the first terminal device, and the second information is used to trigger the first terminal device to send the first terminal device identifier, and the second information is a non-periodically sent information, or the second information is a periodically sent information.

28. The method according to claim 27, characterized in that, the first time domain resource for receiving the first terminal device identifier is determined based on a reference time domain resource, and the reference time domain resource is used to send the second information.

29. The method according to claim 28, characterized in that, the first time domain resource is determined based on the reference time domain resource and resource configuration parameters, and the resource configuration parameters are used to indicate one or more of the following: the time domain offset between the reference time domain resource and the first time domain resource; the duration corresponding to each time domain resource in a plurality of time domain resources, and the plurality of time domain resources include the first time domain resource; the time interval between two adjacent time domain resources in the time domain among the plurality of time domain resources; the number of time domain resources of the plurality of time domain resources.

30. The method according to claim 29, characterized in that, the resource configuration parameters are carried in the second information.

31. The method according to any one of claims 27-30, 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 first terminal device identifier.

32. The method according to any one of claims 24-27, characterized in that, the time domain resource for sending the first terminal device identifier is randomly selected by the first terminal device.

33. The method according to any one of claims 24-32, characterized in that, The first information further includes a first Radio Network Temporary Identity (RNTI) associated with the terminal device identifier.

34. The method according to claim 32 or 33, wherein, the method further includes: the target device sends 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.

35. The method according to any one of claims 24 - 34, wherein, the first information further includes: information for instructing the first terminal device to access the network based on a backoff mechanism; and / or parameters for the first terminal device to execute the backoff mechanism.

36. The method according to claim 35, wherein, if the first information includes the parameters, the parameters are used to indicate the maximum number of times for the first terminal device to attempt to access the target device; and / or backoff time information for the first terminal device to retry accessing the target device.

37. The method according to claim 36, wherein, in the case where the parameters are used to indicate the maximum number of times, if 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.

38. The method according to claim 36, wherein, if the parameters are used to indicate the backoff time information, at a first moment the first terminal device re - listens for the second information, and the first moment is a moment after a backoff time indicated by the backoff time information starting from the moment when the first terminal device fails to resolve the conflict.

39. The method according to any one of claims 24 - 38, wherein, the first information carries multiple terminal device identifiers, and RNTIs associated with each of the multiple terminal device identifiers, and the multiple first terminal device identifiers include the first terminal device identifier.

40. The method according to any one of claims 24 - 39, wherein, the first information is carried on a broadcast channel.

41. The method according to any one of claims 24 - 40, wherein, the first terminal device receives the first information within a first time period, and a starting position of the first time period is determined based on a transmission time of the first terminal device identifier.

42. The method according to claim 41, wherein, the starting position of the first time period is the transmission time of the first terminal device identifier, or there is a first time interval between the starting position of the first time period and the transmission time of the first terminal device identifier.

43. The method according to claim 41 or 42, wherein, if the first information is not received within the first time period, the first terminal device fails to resolve the conflict.

44. The method according to any one of claims 24 - 43, wherein, before the target device receives the first terminal device identifier sent by the first terminal device, the method further includes: The target device receives the preamble sent by the first terminal device, where the preamble is used for the target device to perform uplink time synchronization and / or uplink frequency synchronization.

45. A terminal device, characterized in that, the terminal device is the first terminal device, and includes: a sending unit, configured to send a first terminal device identifier to a target device; a receiving unit, configured to receive first information sent by the target device, where the first information includes the terminal device identifier received by the target device, where the target device includes a network device and / or a second terminal device.

46. The terminal device according to claim 45, characterized in that, the terminal device further includes: if the terminal device identifier in the first information is the same as the first terminal device identifier, a first processing unit, configured to confirm that the conflict resolution is successful; and / or if the terminal device identifier in the first information is different from the first terminal device identifier, a second processing unit, configured to confirm that the conflict resolution fails.

47. The terminal device according to claim 45 or 46, characterized in that, the first terminal device identifier is generated by the first terminal device.

48. The terminal device according to any one of claims 45-47, characterized in that, the receiving unit is configured to receive second information sent by the target device, where the second information is used to trigger the first terminal device to send the first terminal device identifier, and the second information is information sent non-periodically, or the second information is information sent periodically.

49. The terminal device according to claim 48, characterized in that, the first time domain resource where the first terminal device identifier is sent is determined based on a reference time domain resource, and the reference time domain resource is used to receive the second information.

50. The terminal device according to claim 49, characterized in that, the first time domain resource is determined based on the reference time domain resource and a resource configuration parameter, where 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; the duration corresponding to each time domain resource in a plurality of time domain resources, where the plurality of time domain resources includes the first time domain resource; a time interval between two adjacent time domain resources in the time domain among the plurality of time domain resources; the number of time domain resources of the plurality of time domain resources.

51. The terminal device according to claim 50, characterized in that, the resource configuration parameter is carried in the second information.

52. The terminal device according to any one of claims 48-51, 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 first terminal device identifier.

53. The terminal device according to any one of claims 45-48, characterized in that, the time domain resource for sending the first terminal device identifier is randomly selected by the first terminal device.

54. The terminal device according to any one of claims 45-53, characterized in that, the first information further includes a first radio network temporary identifier RNTI associated with the terminal device identifier.

55. The terminal device according to claim 54, characterized in that, the terminal device further comprises: a third processing unit, configured to retain the first RNTI when the first terminal device confirms successful conflict resolution.

56. The terminal device according to claim 54 or 55, characterized in that, the receiving unit is further configured 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.

57. The terminal device according to any one of claims 45-56, characterized in that, the first information further comprises: information for instructing the first terminal device to access the network based on a backoff mechanism; and / or parameters for the first terminal device to execute the backoff mechanism.

58. The terminal device according to claim 57, characterized in that, if the first information includes the parameters, the parameters are 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 retry accessing the target device.

59. The terminal device according to claim 58, characterized in that, if the parameters are used to indicate the maximum number of times, when the first terminal device confirms failed conflict resolution and the number of times the first terminal device attempts to access the target device is less than the maximum number of times, the receiving unit is configured to re-monitor the second information.

60. The terminal device according to claim 58 or 59, characterized in that, if the parameters are used to indicate the maximum number of times, the terminal device further comprises: when the first terminal device confirms failed conflict resolution 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, a fourth processing unit, configured to confirm failed access to the target device.

61. The terminal device according to claim 58, characterized in that, if the parameters are used to indicate the backoff time information, the receiving unit is configured to re-monitor the second information at a first moment, where the first moment is a moment after a backoff time indicated by the backoff time information starting from the moment when the first terminal device confirms failed conflict resolution.

62. The terminal device according to any one of claims 45-61, characterized in that, the first information carries multiple terminal device identifiers and RNTIs associated with each of the multiple terminal device identifiers, and the multiple first terminal device identifiers include the first terminal device identifier.

63. The terminal device according to any one of claims 45-62, characterized in that, the first information is carried on a broadcast channel.

64. The terminal device according to any one of claims 45-63, characterized in that, the first terminal device receives the first information within a first time period, and a starting position of the first time period is determined based on a sending time of the first terminal device identifier.

65. The terminal device according to claim 64, characterized in that, the starting position of the first time period is the sending time of the first terminal device identifier, or There is a first time interval between the starting position of the first time period and the sending time of the first terminal device identifier.

66. The terminal device according to claim 64 or 65, wherein, the terminal device further includes: a fifth processing unit that, when the first information is not received within the first time period, is configured to confirm that the conflict resolution fails.

67. The terminal device according to any one of claims 45-66, wherein, before the first terminal device sends the first terminal device identifier to the target device, the sending unit is further configured to: send a preamble to the target device, where the preamble is used by the target device for uplink time synchronization and / or uplink frequency synchronization.

68. A communication device, wherein, the communication device is a target device, and includes: a receiving unit configured to receive a first terminal device identifier sent by a first terminal device; a sending unit configured to send first information, where 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.

69. The communication device according to claim 68, wherein, if the terminal device identifier included in the first information is the same as the first terminal device identifier, then the conflict resolution of the first terminal device is successful; and / or if the terminal device identifier included in the first information is different from the first terminal device identifier, then the conflict resolution of the first terminal device fails.

70. The communication device according to claim 68 or 69, wherein, the first terminal device identifier is generated by the first terminal device.

71. The communication device according to any one of claims 68-70, wherein, the sending unit is configured to send second information to the first terminal device, where the second information is used to trigger the first terminal device to send the first terminal device identifier, and the second information is a non-periodically sent information, or the second information is a periodically sent information.

72. The communication device according to claim 71, wherein, the first time domain resource where the first terminal device identifier is received is determined based on a reference time domain resource, and the reference time domain resource is used to send the second information.

73. The communication device according to claim 72, wherein, the first time domain resource is determined based on the reference time domain resource and resource configuration parameters, and the resource configuration parameters are used to indicate one or more of the following: the time domain offset between the reference time domain resource and the first time domain resource; the duration corresponding to each time domain resource among multiple time domain resources, where the multiple time domain resources include the first time domain resource; the time interval between two adjacent time domain resources in the time domain among the multiple time domain resources; the number of time domain resources of the multiple time domain resources.

74. The communication device according to claim 73, wherein, the resource configuration parameters are carried in the second information.

75. The communication device according to any one of claims 71-74, wherein, The second information includes a power adjustment parameter, which is used to adjust the transmission power of the first terminal device identifier.

76. The communication device according to any one of claims 68-71, characterized in that the time domain resource for sending the first terminal device identifier is randomly selected by the first terminal device.

77. The communication device according to any one of claims 68-76, characterized in that the first information further includes a first radio network temporary identifier (RNTI) associated with the terminal device identifier.

78. The communication device according to claim 76 or 77, characterized in that the sending unit is further configured to send 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.

79. The communication device according to any one of claims 68-78, characterized in that the first information further includes: information for instructing the first terminal device to access the network based on a backoff mechanism; and / or parameters for the first terminal device to execute the backoff mechanism.

80. The communication device according to claim 79, characterized in that if the first information includes the parameter, the parameter is used to indicate the maximum number of times for the first terminal device to attempt to access the target device; and / or the backoff time information for the first terminal device to re-attempt to access the target device.

81. The communication device according to claim 80, characterized in that in the case where the parameter is used to indicate the maximum number of times, if 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.

82. The communication device according to claim 80, characterized in that if the parameter is used to indicate the backoff time information, at a first moment, the first terminal device re-monitors the second information, and the first moment is a moment after a backoff time indicated by the backoff time information starting from the moment when the first terminal device fails to resolve the conflict.

83. The communication device according to any one of claims 68-82, characterized in that the first information carries a plurality of terminal device identifiers and RNTIs associated with each of the plurality of terminal device identifiers, and the plurality of first terminal device identifiers include the first terminal device identifier.

84. The communication device according to any one of claims 68-83, characterized in that the first information is carried on a broadcast channel.

85. The communication device according to any one of claims 68-84, characterized in that the first terminal device receives the first information within a first time period, and a starting position of the first time period is determined based on a sending time of the first terminal device identifier.

86. The communication device according to claim 85, characterized in that the starting position of the first time period is the sending time of the first terminal device identifier, or There is a first time interval between the starting position of the first time period and the transmission time of the first terminal device identifier.

87. The communication device according to claim 85 or 86, wherein, if the first information is not received within the first time period, the first terminal device fails to resolve the conflict.

88. The communication device according to any one of claims 68 - 87, wherein, before the target device receives the first terminal device identifier sent by the first terminal device, the receiving unit is further configured to: receive a preamble sent by the first terminal device, where the preamble is used by the target device for uplink time synchronization and / or uplink frequency synchronization.

89. A terminal device, wherein, the terminal device is a first terminal device, and includes a transceiver, a memory, and a processor. The memory is used to store a program, and the processor is used to call the program in the memory and control the transceiver to receive or send signals, so that the terminal device executes the method according to any one of claims 1 - 23.

90. A communication device, wherein, the communication device is a target device, and includes a transceiver, a memory, and a processor. The memory is used to store a program, and the processor is used to call the program in the memory and control the transceiver to receive or send signals, so that the network device executes the method according to any one of claims 24 - 44.

91. A device, wherein, it includes a processor configured to call a program from a memory, so that the device executes the method according to any one of claims 1 - 44.

92. A chip, wherein, it includes a processor configured to call a program from a memory, such that a device installed with the chip executes the method according to any one of claims 1 - 44.

93. A computer-readable storage medium, wherein, a program is stored thereon, and the program causes a computer to execute the method according to any one of claims 1 - 44.

94. A computer program product, wherein, it includes a program, and the program causes a computer to execute the method according to any one of claims 1 - 44.

95. A computer program, wherein, the computer program causes a computer to execute the method according to any one of claims 1 - 4.

Images