Wireless communication method, device, and storage medium

Abstract

The present application provides a wireless communication method, a device, and a storage medium. The method comprises: a first device determines a first identifier, the first identifier being allocated by a second device or determined on the basis of a first identifier range, and the first identifier being used for communication between the first device and the second device.

Description

A wireless communication method and device, and a storage medium Technical Field

[0001] This application relates to the field of mobile communication technology, specifically to a wireless communication method and device, and a storage medium. Background Technology

[0002] Ambient Internet of Things (A-IoT) communication employs energy harvesting and backscatter communication technologies. A-IoT devices are IoT devices powered by various environmental energy sources, such as radio frequency energy, light energy, solar energy, thermal energy, and mechanical energy. These devices may have no energy storage capacity or very limited energy storage capacity (e.g., using capacitors with a capacitance of tens of microfarads (µF)).

[0003] A-IoT supports many industrial applications, such as automated warehousing, smart homes, smart agriculture, and finding personal items.

[0004] Summary of the Invention

[0005] This application provides a wireless communication method, device, and storage medium.

[0006] The first device determines a first identifier, which is assigned by the second device or determined based on a range of first identifiers, and the first identifier is used for communication between the first device and the second device.

[0007] The wireless communication method provided in this application includes:

[0008] The second device communicates with the first device based on a first identifier, which is assigned by the second device or determined based on a range of the first identifier.

[0009] The first device provided in this application embodiment includes:

[0010] The determining unit is configured to determine a first identifier, which is assigned by the second device or determined based on a range of first identifiers, and the first identifier is used for communication between the first device and the second device.

[0011] The second device provided in this application embodiment includes:

[0012] The first communication unit is configured to communicate with the first device based on a first identifier, wherein the first identifier is assigned by the second device or determined based on a range of the first identifier.

[0013] The communication device provided in this application embodiment can be either the first device or the second device in the above-described scheme. The communication device includes a processor and a memory. The memory stores a computer program, and the processor calls and runs the computer program stored in the memory to execute the aforementioned wireless communication method.

[0014] The chip provided in this application embodiment is used to implement the above-described wireless communication method.

[0015] Specifically, the chip includes a processor for calling and running a computer program from a memory, causing a device equipped with the chip to perform the aforementioned wireless communication method.

[0016] The computer-readable storage medium provided in this application embodiment is used to store a computer program that causes a computer to execute the above-described wireless communication method.

[0017] The computer program product provided in this application includes computer program instructions that cause a computer to execute the above-described wireless communication method.

[0018] The computer program provided in this application embodiment, when run on a computer, causes the computer to execute the above-described wireless communication method.

[0019] Through the above technical solution, the first identifier for communication between the first device and the second device is assigned to the second device or determined based on the range of the first identifier, so that the first device and the second device can communicate based on the determined first identifier, and the problem of communication failure caused by different first devices using the same identifier to communicate with the second device, i.e., identifier conflict, is avoided as much as possible. Attached Figure Description

[0020] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0021] Figure 1 is a schematic diagram of an application scenario of an embodiment of this application;

[0022] Figure 2 is a schematic diagram of an optional structure of the A-IoT communication system provided in an embodiment of this application;

[0023] Figure 3 is a schematic diagram of an optional location for radio frequency energy harvesting provided in an embodiment of this application;

[0024] Figure 4 is a schematic diagram of an optional backscatter communication provided in an embodiment of this application;

[0025] Figure 5 is a schematic diagram of an optional grounding circuit for resistive load modulation provided in an embodiment of this application;

[0026] Figure 6 is a schematic diagram of an optional single-tag access process provided in an embodiment of this application;

[0027] Figure 7 is an optional flowchart of the wireless communication method provided in an embodiment of this application;

[0028] Figure 8 is an optional flowchart of the wireless communication method provided in an embodiment of this application;

[0029] Figure 9 is an optional flowchart of the wireless communication method provided in an embodiment of this application;

[0030] Figure 10 is an optional flowchart of the wireless communication method provided in an embodiment of this application;

[0031] Figure 11 is an optional flowchart of the wireless communication method provided in an embodiment of this application;

[0032] Figure 12 is an optional flowchart of the wireless communication method provided in an embodiment of this application;

[0033] Figure 13 is a schematic diagram of the optional structure of the first device provided in an embodiment of this application;

[0034] Figure 14 is a schematic diagram of the optional structure of the second device provided in an embodiment of this application;

[0035] Figure 15 is a schematic structural diagram of a communication device provided in an embodiment of this application;

[0036] Figure 16 is a schematic structural diagram of a chip according to an embodiment of this application;

[0037] Figure 17 is a schematic block diagram of a communication system provided in an embodiment of this application. Detailed Implementation

[0038] The technical solutions of the embodiments of this application will now be described with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application.

[0039] Communication system scenarios include Terrestrial Networks (TN) and NTN. NTN typically uses satellite communication to provide communication services to terrestrial users. Current NTN systems include NR-NTN and IoT-NTN systems, and other NTN systems may be included in the future.

[0040] Figure 1 is a schematic diagram of the architecture of a communication system provided in an embodiment of this application. As shown in Figure 1, the communication system 100 may include a terminal device 110 and a network device 120. The network device 120 can communicate with the terminal device 110 via an air interface. Multi-service transmission is supported between the terminal device 110 and the network device 120.

[0041] It should be understood that the embodiments of this application are only illustrated by way of example with communication system 100, but the embodiments of this application are not limited thereto. That is to say, the technical solutions of the embodiments of this application can be applied to various communication systems, such as: Long Term Evolution (LTE) system, LTE Time Division Duplex (TDD), Universal Mobile Telecommunication System (UMTS), Internet of Things (IoT) system, Narrow Band Internet of Things (NB-IoT) system, enhanced Machine-Type Communications (eMTC) system, 5G communication system (also known as New Radio (NR) communication system), or future communication systems, etc.

[0042] In the communication system 100 shown in Figure 1, network device 120 may be an access network device that communicates with terminal device 110. The access network device can provide communication coverage for a specific geographical area and can communicate with terminal device 110 (e.g., UE) located within that coverage area.

[0043] Network device 120 may be an evolved Node B (eNB or eNodeB) in a Long Term Evolution (LTE) system, a Next Generation Radio Access Network (NG RAN) device, a base station (gNB) in an NR system, a radio controller in a Cloud Radio Access Network (CRAN), or a relay station, access point, vehicle-mounted device, wearable device, hub, switch, bridge, router, or network device in a future evolved Public Land Mobile Network (PLMN), etc.

[0044] Terminal device 110 can be any terminal device, including but not limited to terminal devices that are connected to network device 120 or other terminal devices via wired or wireless connections.

[0045] For example, the terminal device 110 can refer to an access terminal, user equipment (UE), user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device. The access terminal can be a cellular phone, cordless phone, Session Initiation Protocol (SIP) phone, IoT device, satellite handheld terminal, Wireless Local Loop (WLL) station, Personal Digital Assistant (PDA), handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, in-vehicle device, wearable device, terminal device in a 5G network, or terminal device in a future evolved network, etc.

[0046] Terminal device 110 can be used for device-to-device (D2D) communication.

[0047] The wireless communication system 100 may further include a core network device 130 that communicates with the base station. This core network device 130 may be a 5G core network (5G Core, 5GC) device, such as an Access and Mobility Management Function (AMF), an Authentication Server Function (AUSF), a User Plane Function (UPF), or a Session Management Function (SMF). Optionally, the core network device 130 may also be an Evolved Packet Core (EPC) device for an LTE network, such as a Session Management Function + Core Packet Gateway (SMF+PGW-C) device. It should be understood that SMF+PGW-C can simultaneously implement the functions of both SMF and PGW-C. During network evolution, the aforementioned core network device may also be called by other names, or new network entities may be formed by dividing the core network functions; this embodiment does not limit this.

[0048] The various functional units in the communication system 100 can also establish connections and communicate with each other through the next generation (NG) interface.

[0049] For example, terminal devices establish an air interface connection with access network devices through the Uu interface for transmitting user plane data and control plane signaling; terminal devices can establish a control plane signaling connection with the AMF through NG interface 1 (N1); access network devices, such as next-generation radio access base stations (gNB), can establish a user plane data connection with the UPF through NG interface 3 (N3); access network devices can establish a control plane signaling connection with the AMF through NG interface 2 (N2); the UPF can establish a control plane signaling connection with the SMF through NG interface 4 (N4); the UPF can interact with the data network for user plane data through NG interface 6 (N6); the AMF can establish a control plane signaling connection with the SMF through NG interface 11 (N11); and the SMF can establish a control plane signaling connection with the PCF through NG interface 7 (N7).

[0050] Figure 1 exemplarily illustrates a base station, a core network device, and two terminal devices. Optionally, the wireless communication system 100 may include multiple base station devices, and each base station may include other numbers of terminal devices within its coverage area. This application embodiment does not limit this.

[0051] It should be noted that Figure 1 is merely an example illustrating the system to which this application applies. Of course, the method shown in the embodiments of this application can also be applied to other systems. Furthermore, the terms "system" and "network" are often used interchangeably in this document. The term "and / or" in this document merely describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship. It should also be understood that "instruction" mentioned in the embodiments of this application can be a direct instruction, an indirect instruction, or an indication of a related relationship. For example, A instructing B can mean that A directly instructs B, for example, B can be obtained through A; it can also mean that A indirectly instructs B, for example, A instructs C, B can be obtained through C; or it can mean that there is a related relationship between A and B. It should also be understood that "correspondence" mentioned in the embodiments of this application can indicate a direct or indirect correspondence between two things, or an related relationship between two things, or a relationship of instruction and being instructed, configuration and being configured, etc. It should also be understood that the "predefined" or "predefined rules" mentioned in the embodiments of this application can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including terminal devices and network devices), and this application does not limit the specific implementation method. For example, predefined can refer to those defined in a protocol. It should also be understood that in the embodiments of this application, the "protocol" can refer to standard protocols in the field of communication, such as the LTE protocol, the NR protocol, and related protocols applied to future communication systems, and this application does not limit this.

[0052] To facilitate understanding of the technical solutions of the embodiments of this application, the relevant technologies of the embodiments of this application are described below. The following relevant technologies are optional solutions and can be combined with the technical solutions of the embodiments of this application in any way, and they all fall within the protection scope of the embodiments of this application.

[0053] A-IoT communication technology principle

[0054] A-IoT communication can employ energy harvesting and backscatter communication technologies. As shown in Figure 2, the A-IoT communication network consists of a network device 201 and an A-IoT terminal 202. The network device 201 sends wireless power signals and downlink communication signals 203 to the A-IoT terminal 202 and receives backscatter signals 204 from the A-IoT terminal. A basic A-IoT terminal 201 includes an energy harvesting module 2011, a backscatter communication module 2022, and a low-power computing module 2023. Furthermore, the A-IoT terminal 202 may also have a memory or sensor 2024 for storing basic information (such as object identification) or acquiring sensor data such as ambient temperature and humidity.

[0055] Key technologies for A-IoT communication include radio frequency energy harvesting and backscatter communication.

[0056] Radio Frequency Power Harvesting

[0057] As shown in Figure 3, the radio frequency (RF) energy harvesting module harvests electromagnetic wave energy from space based on the principle of electromagnetic induction, thereby obtaining the energy required to drive the A-IoT terminal, such as driving low-power demodulation and modulation modules, sensors, and memory reading. Therefore, the A-IoT terminal does not require a traditional battery. The structure of the energy harvesting module, as shown in Figure 3, includes a diode 301, a capacitor 302, and a resistor 303, thereby harvesting radio frequency (RF) energy from space. Optionally, the end of capacitor 302 connected to diode 301 is the positive terminal.

[0058] Backscattering communication

[0059] The working principle of backscatter communication is shown in Figure 4. The zero-power terminal 401, also known as the A-IOT terminal, receives the carrier wave 403 transmitted by the backscatter reader 402. Energy is harvested through the RF energy harvesting module 4011, which then powers the low-power computing module 4012 (also called the logic module). The received carrier wave 403 is modulated to load the information to be transmitted, and the modulated signal is radiated from the antenna as a backscatter signal 404. This information transmission process is called backscatter communication. The transmitter (TX) and amplifier (AMP) of the backscatter reader 402 are connected, and the receiver (RX) of the backscatter reader 402 is connected to a low-noise amplifier (LNA).

[0060] Backscattering and load modulation are inseparable. Load modulation adjusts and controls the circuit parameters of the A-IoT terminal's oscillation circuit according to the data flow rhythm, thereby changing parameters such as the electronic tag's impedance, thus completing the modulation process.

[0061] Load modulation techniques include two methods: resistive load modulation and capacitive load modulation. In resistive load modulation, as shown in Figure 5, the load R... L A resistor R3 is connected in parallel. R3 can be called the load modulation resistor. This resistor R3 is switched on or off based on the control of the binary data stream, as shown in Figure 5. The zero-power terminal also includes: resistor R2, inductor L1, inductor L2, and capacitor C2. Switching resistor R3 on and off causes a change in the circuit voltage, thus achieving amplitude shift keying (ASK) modulation. This means that the signal is modulated and transmitted by adjusting the amplitude of the backscattered signal from the A-IoT terminal. Similarly, in capacitive load modulation, switching the capacitor on and off changes the circuit's resonant frequency, achieving frequency shift keying (FSK) modulation. This means that the signal is modulated and transmitted by adjusting the operating frequency of the backscattered signal from the A-IoT terminal.

[0062] As can be seen, A-IoT terminals utilize load modulation to modulate the incoming signal, thereby achieving backscatter communication. Therefore, A-IoT terminals have significant advantages:

[0063] 1) A-IoT terminals do not actively transmit signals, therefore they do not require complex radio frequency links, such as power amplifiers (PAs) and radio frequency filters;

[0064] 2) A-IoT terminals do not need to actively generate high-frequency signals, therefore they do not need high-frequency crystal oscillators;

[0065] 3) With the help of backscatter communication, the signal transmission of A-IoT terminals does not require A-IoT to consume the terminal's own energy.

[0066] Classification of A-IoT terminals

[0067] Based on the current discussions within 3GPP, A-IoT terminals can be categorized into two types based on their energy storage capacity and their ability to generate RF signals for signal transmission.

[0068] Device type 1: Transmitting power is about 1uW, with energy storage function, but it does not have independent signal generation and uplink / downlink signal amplification functions. Signal transmission can only rely on backscatter.

[0069] Device type 2 (Device type 3): Transmitting power of several hundred uW, with energy storage function, uplink and downlink signal amplification function, and can generate signals independently or transmit signals using backscattering.

[0070] In standardization discussions, zero-power IoT can also be referred to as A-IoT or passive IoT. A-IoT devices (Ambient IoT devices) refer to IoT devices that use various environmental energy sources, such as radio frequency energy, light energy, solar energy, thermal energy, and mechanical energy, to power themselves. These devices may have no energy storage capacity or very limited energy storage capacity (e.g., using capacitors with a capacitance of tens of microseconds). Compared to existing IoT devices, A-IoT devices have many advantages, including no need for conventional batteries, no maintenance, small size, low complexity and low cost, and long lifespan.

[0071] A-IoT supports many industrial applications, such as automated warehousing, smart homes, smart agriculture, and finding personal items.

[0072] Automated warehousing: Automated warehouse inventory scenarios involve multiple stages, including verification and unloading, receiving, inventory counting, outbound, and inspection. As goods are transferred, stored, and stocked, a large amount of warehousing information is generated. This information is typically characterized by frequent data read operations and large data volumes. Environmental IoT devices are connected to items of different value and uses, such as pallets, containers, and individual products, and related communication devices are deployed. Through information exchange between communication devices and tags, efficient management of accurate and rapid inventory and storage information can be achieved at each stage.

[0073] For automated warehousing, 3GPP defines an inventory use case, the purpose of which is to discover what goods (e.g., boxes, drawers, packages, tools, etc.) are present in a specific area. Upon receiving a request from the network within that specific area, A-IoT devices attached to these goods report the identifier associated with the goods to the network device, and may also attach other information such as status information, measurement results, and location information. In terms of business model, this falls under the device-originated–device-terminated triggered (DO-DTT) mode.

[0074] Random access in RFID technology

[0075] When the interrogator needs to read or write a tag, as shown in Figure 6, it first sends a query command to all tags. This command includes a parameter Q (Q is an integer between 0 and 15). Tags within the interrogator's radio frequency field will generate a value between 0 and 2 upon receiving this command. Q A random number between the specified intervals is used as the tag's response time slot, and this random number is loaded into the time slot counter. Only tags with a time slot of 0 in the time slot counter will send a 16-bit random number (RN16) to the reader as a response. When the reader receives the RN16 sent by the tag, it sends an acknowledgment (ACK(RN16)) instruction with the same RN16 bit parameters. If the tag receives a valid ACK instruction, i.e., an ACK instruction carrying RN16, it immediately switches to the acknowledged state and backscatters its Protocol Control (PC), Electronic Product Code (EPC), and 16-bit Cyclic Redundancy Check-16 (CRC-16) code. When the tag is in the confirmed state, it waits for the reader to send it a random number request (REQ_RN) with the correct RN16. Upon receiving the REQ_RN (RN16) sent by the reader, the tag executes the REQ_RN (RN16) instruction sent by the reader, sends a new RN16, i.e., a handle, and transitions to another state (open state or protected state). In the open state or protected state, the reader can perform read and write operations on this tag independently.

[0076] As shown in Figure 6, if the tag sends a valid EPC, the reader sends a REQ_RN; if the tag sends an invalid EPC, the reader sends a negative acknowledgment (NAK).

[0077] In related technologies, tags and readers are identified using RN16 or handles during communication. In Ambient IoT, if both contention-based random access (CBRA) and contention-free access need to be supported simultaneously, the question of how the terminal obtains the handle needs to be addressed.

[0078] To facilitate understanding of the technical solutions of the embodiments of this application, the technical solutions of this application are described in detail below through specific embodiments. The above-mentioned related technologies are optional solutions and can be arbitrarily combined with the technical solutions of the embodiments of this application, all of which fall within the protection scope of the embodiments of this application. The embodiments of this application include at least some of the following contents.

[0079] This application provides a wireless communication method applied to a first device, as shown in FIG7, including:

[0080] S701. The first device determines a first identifier, which is assigned by the second device or determined based on a range of first identifiers, and the first identifier is used for communication between the first device and the second device.

[0081] In some embodiments, the first device is a terminal device or an Internet of Things (IoT) terminal.

[0082] In some embodiments, the first device may be understood as a tag or a terminal having a tag.

[0083] In some embodiments, the second device is an intermediate device, a relay device, or a network device.

[0084] In some embodiments, the second device can be understood as a reader or interrogator, an intermediate UE with a reader, a relay terminal, or a network device. The first device can be connected to the network device via an intermediate device or relay terminal.

[0085] The first device determines a first identifier, which can be understood as the handle of the first device, used to identify the first device, enabling the first device and the second device to communicate based on the identifier of the first device. In the case of multiple first devices interacting with the second device, the identifiers of the different first devices are different, allowing the second device to distinguish between different first devices and thus communicate with them.

[0086] The first identifier of the first device may be assigned to the second device, or it may be determined by the first device based on a range of first identifiers. The range of first identifiers can be understood as a range for selecting the first identifier, or a set of multiple identifiers, or a group of identifiers.

[0087] In this embodiment, the first identifier for communication between the first device and the second device is assigned to the second device or determined based on the range of the first identifier, so that the first device and the second device can communicate based on the determined first identifier, thereby avoiding the problem of communication failure caused by different first devices using the same identifier to communicate with the second device, i.e., identifier conflict.

[0088] In some embodiments, the first identifier is a binary number.

[0089] In some embodiments, the first device determines a first identifier during the access process of the second device, wherein the first device accesses the second device in the following ways: contention-free access and CBRA.

[0090] In some embodiments, in the absence of contention for access, the first identifier of the first device is assigned by the second device.

[0091] In some embodiments, under CBRA conditions, the first identifier of the first device is determined based on a first identifier range.

[0092] In some embodiments, when the first identifier is assigned by the second device, the first device determines the first identifier by:

[0093] The first device receives the first identifier sent by the second device.

[0094] Accordingly, the first device receives the first identifier assigned to the first device by the second device.

[0095] In some embodiments, the first device receives the first identifier sent by the second device, including:

[0096] The first device receives a first downlink message sent by the second device, the first downlink message containing the first identifier.

[0097] In some embodiments, the first downlink message includes one or more of the following:

[0098] Paging message, initial downlink message, query command, selection command.

[0099] In this embodiment of the application, the first downlink message can be understood as a downlink message sent by the second device to the first device to indicate the first identifier or the range of the first identifier, and it can also be other messages or be replaced with other names.

[0100] In some embodiments, the first downlink message includes one or more identifiers, and the one or more identifiers include the first identifier.

[0101] In the case where the first downlink message carries an identifier, the first downlink message carries a first identifier, which is an identifier assigned by the second device to the current first device.

[0102] In the case where the first downlink message carries multiple identifiers, the different identifiers among the multiple identifiers carried in the first downlink message are identifiers assigned by the second device to different first devices, wherein the multiple identifiers include the first identifier assigned to the current first device.

[0103] In some embodiments, for each of one or more identifiers, the first downlink message carries the device ID of the first device corresponding to each identifier, thereby distinguishing which identifier is assigned to which first device.

[0104] In some embodiments, the first downlink message further includes multiple resource indication messages, with different resource indication messages used to allocate dedicated transmission resources to different first devices.

[0105] In this embodiment of the application, when the first downlink message includes multiple identifiers, the first downlink message also includes resource indication information corresponding to each identifier, which is used to indicate the dedicated transmission resources allocated to each first device.

[0106] In some embodiments, the transmission resources indicated by the resources in the first downlink message are used for sending the first uplink message, wherein the first uplink message is used in response to the first downlink message.

[0107] In this embodiment of the application, multiple resource indication information carried in the first downlink message are used to allocate dedicated transmission resources for the access process to different first devices, so that different first devices send the first uplink message based on different transmission resources, thereby avoiding the situation where different first devices use the same transmission resources to send the first uplink message and causing conflicts or competition.

[0108] In some embodiments, the dedicated transmission resources include one or more of the following:

[0109] Dedicated time-domain resources, dedicated frequency-domain resources, and dedicated code-domain resources.

[0110] In this embodiment, the transmission resources of different first devices are distinguished by one or more dimensions of the time domain, frequency domain, and code domain, thereby isolating different transmission resources and improving resource utilization.

[0111] In some embodiments, when the first identifier is determined based on a first identifier range, the first device determines the first identifier by including:

[0112] The first device determines the first identifier based on the first identifier range.

[0113] The first device may randomly select an identifier from the first identifier range as the first identifier, or it may select an identifier from the first identifier range as the first identifier based on predefined rules.

[0114] In some embodiments, the identifier assigned by the second device to the first device belongs to the assigned identifier range. Here, the assigned identifier range can be understood as the identifier range, identifier set, or group of identifiers used by the second device to generate the assigned identifier. The assigned identifier range does not overlap with the first identifier range.

[0115] In this embodiment of the application, by ensuring that the allocation of the identifier range does not overlap with the first identifier range, the handle used by CBRA and the handle used by non-contention access are separated, which can avoid the conflict between the handle used by CBRA and the handle used by non-contention access, thereby avoiding the failure of non-contention access or receiving messages that do not belong to oneself.

[0116] In some embodiments, the first identifier range is predefined or configured by the second device.

[0117] The first identifier's scope is predefined, and can also be understood as being stipulated or agreed upon by the agreement.

[0118] In some embodiments, where the first identifier ranges from the second device configuration, the method further includes:

[0119] The first device receives a first downlink message sent by the second device. The first downlink message includes: first information or second information, wherein the first information is used to indicate a first set of identifiers, and the first identifier is an identifier in the first set of identifiers; and the second information is used to indicate a first mask, wherein the first mask is an N-bit mask out of M bits, and the first identifier is M bits.

[0120] In this application embodiment, the first downlink message is configured with a first identifier range in one or more of the following two configuration methods:

[0121] The first downlink message contains first information indicating the first set of identifiers;

[0122] The first downlink message contains second information indicating the first mask.

[0123] When the first information indicates a first set of identifiers, the first information may indicate multiple identifiers included in the first set of identifiers, or it may indicate the minimum identifier and the maximum identifier in the first set of identifiers, so that the first device determines the first set of identifiers based on the minimum identifier and the maximum identifier.

[0124] In one example, the first information indicates all IDs between ID1 and ID2.

[0125] In one example, the first information indicates ID1 and ID2, which are used by the first device to determine all IDs between ID1 and ID2.

[0126] When the second information indicates the first mask, the first device determines the first identifier based on the first mask, wherein the first identifier is M bits, the MN bits in M ​​are determined or fixed, and are all 0s or weighted 1s, and the value of the N bits is uncertain or fixed.

[0127] In some embodiments, when the first device determines the first identifier based on the first mask, the N bits can be randomly generated while the values ​​of the MN bits remain unchanged, thereby obtaining the M-bit first identifier.

[0128] In some embodiments, the N bits in the first mask may be the consecutive lowest N bits, consecutive highest N bits, or other consecutive or non-consecutive N bits from the M bits.

[0129] In some embodiments, the method further includes:

[0130] The first device sends a first uplink message, which contains the first identifier.

[0131] The first device sends the first identifier to the second device through the first uplink message, thereby reporting the determined first identifier to the second device, so that the second device knows the first identifier of the first device.

[0132] In some embodiments, when the first downlink message contains resource indication information, the first device sends the first uplink message on the transmission resources dedicated to the first device. In this case, the first uplink message can be understood as a response message to the first downlink message.

[0133] In some embodiments, the first uplink message and / or the first downlink message can be understood as a message in a CBRA procedure or a contention-free access procedure, and the transmission of the first uplink message is used to indicate the completion of the CBRA procedure or the contention-free access procedure.

[0134] In some embodiments, the first uplink message includes or carries higher-layer data and / or the device ID of the first device.

[0135] In some embodiments, the method further includes: the first device receiving a second downlink message, the second downlink message being used to obtain the first identifier or to update the first identifier.

[0136] The second device sends a second downlink message to the first device to query the first identifier or update the first identifier.

[0137] In some embodiments, the second downlink message may be a Req RN instruction.

[0138] After receiving the second downlink message sent by the second device, the first device sends a response message to the second device in response to the second downlink message, wherein the response message contains a first identifier or an updated first identifier.

[0139] When the second downlink message is used to query the first identifier, the response message includes the first identifier. When the second downlink message is used to update the first identifier, the response message includes the updated first identifier.

[0140] In some embodiments, the updated first identifier is an identifier generated based on a first identifier range, and the updated first identifier is different from the first identifier.

[0141] In some embodiments, the second downlink message may carry update indication information. The value of the update indication information or the existence of the update indication information is used to indicate that the second downlink message is used to query the first identifier or to update the first identifier.

[0142] In some embodiments, where the second downlink message is used to update the first identifier, the method further includes:

[0143] The first device determines the second identifier based on the second identifier range, and the second identifier is the updated first identifier;

[0144] The first device sends the second identifier.

[0145] The updated first identifier, i.e., the second identifier, is an identifier generated based on the range of the second identifier. The range of the second identifier can be understood as the range used to select the first identifier, or a set of multiple identifiers, or a group of identifiers, and the range of the first identifier is different from the range of the second identifier. The difference between the range of the first identifier and the range of the second identifier makes the updated first identifier different from the first identifier.

[0146] The first device can randomly select an identifier from the second identifier range as the second identifier, or it can select an identifier from the second identifier range based on predefined rules as the second identifier.

[0147] In some embodiments, the second identifier range does not overlap with the assigned identifier range.

[0148] Understandably, the first device sends a response message to the second device in response to the second downlink message, and the response message contains a second identifier.

[0149] In some embodiments, the second identifier range is predefined or configured by the second device.

[0150] In some embodiments, when the second identifier range is configured as the second device, the second downlink message includes: third information or fourth information, wherein the third information is used to indicate a second identifier set, and the second identifier is an identifier in the second identifier set; the fourth information is used to indicate a second mask, wherein the second mask is an N-bit mask of M bits, the first identifier is M bits, and the second mask is different from the first mask.

[0151] In this application embodiment, the method of configuring the second identifier range for the second downlink message includes, but is not limited to, one or more of the following two configuration methods:

[0152] The second downlink message contains third information indicating the second set of identifiers;

[0153] The second downlink message contains fourth information indicating the second mask.

[0154] When the third information indicates the second set of identifiers, the second information may indicate multiple identifiers included in the second set of identifiers, or it may indicate the minimum identifier and the maximum identifier in the second set of identifiers, so that the first device determines the second set of identifiers based on the minimum identifier and the maximum identifier.

[0155] In one example, the third piece of information indicates all IDs between ID3 and ID4.

[0156] In one example, the third information indicates ID3 and ID4, which the first device uses to determine all IDs between ID3 and ID4.

[0157] When the fourth information indicates the second mask, the first device determines the second identifier based on the second mask. The second identifier is M bits, where the MN bits in M ​​are determined or fixed, and are either all 0s or weighted 1s. The value of the N bits is uncertain or fixed.

[0158] In some embodiments, when the first device determines the second identifier based on the second mask, the N bits can be randomly generated while the values ​​of the MN bits remain unchanged, thereby obtaining the M-bit second identifier.

[0159] In some embodiments, the N bits in the second mask may be the consecutive lowest N bits, consecutive highest N bits, or other consecutive or non-consecutive N bits from the M bits.

[0160] It is understandable that the positions of the N bits in the first mask and the second mask are different, or the positions of the N bits are the same but the values ​​of the N bits are different.

[0161] In some embodiments, the method further includes: the first device processing the third downlink message based on the first identifier.

[0162] In some embodiments, a third downlink message can be understood as a downlink message sent by a second device received by a first device after the first device has completed a CBRA procedure or a contention-free access procedure.

[0163] In some embodiments, the first device receives a third downlink message based on the first identifier, including:

[0164] If the third downlink message contains the first identifier, the first device performs the operation corresponding to the third downlink message; and / or

[0165] If the third downlink message does not contain the first identifier, the first device ignores the third downlink message.

[0166] If the third downlink message contains a first identifier, indicating that the third downlink message is a downlink message sent to the current first device, then the first device executes the operation or command corresponding to the third downlink message.

[0167] If the third downlink message does not contain the first identifier, indicating that the third downlink message is not a downlink message sent to the current first device, then the first device ignores the third downlink message.

[0168] In some embodiments, the method further includes:

[0169] The first device sends a second uplink message, which contains the first identifier.

[0170] In some embodiments, the second downlink message can be understood as an uplink message sent by the first device to the second device after completing the CBRA procedure or a contention-free access procedure.

[0171] The second uplink message sent by the first device includes a first identifier to indicate that the second uplink message was sent by the first device.

[0172] This application provides a wireless communication method applied to a second device, as shown in FIG8, including:

[0173] S801, the second device communicates with the first device based on the first identifier, wherein the first identifier is assigned by the second device or determined based on the range of the first identifier.

[0174] In some embodiments, the first device is a terminal device or an Internet of Things (IoT) terminal.

[0175] In some embodiments, the first device may be understood as a tag or a terminal having a tag.

[0176] In some embodiments, the second device is an intermediate device, a relay device, or a network device.

[0177] In some embodiments, the second device can be understood as a reader or interrogator, an intermediate UE with a reader, a relay terminal, or a network device. The first device can be connected to the network device via an intermediate device or relay terminal.

[0178] The first identifier can be understood as the handle of the first device, used to identify the first device, enabling the first device and the second device to communicate based on the first device's identifier. Specifically, when multiple first devices interact with the second device, each first device has a different identifier, allowing the second device to distinguish between different first devices and thus communicate with them.

[0179] The first identifier of the first device may be assigned to the second device, or it may be determined by the first device based on a range of first identifiers. The range of first identifiers can be understood as a range for selecting the first identifier, or a set of multiple identifiers, or a group of identifiers.

[0180] In this embodiment, the first identifier for communication between the first device and the second device is assigned to the second device or determined based on the range of the first identifier, so that the first device and the second device can communicate based on the determined first identifier, thereby avoiding the problem of communication failure caused by different first devices using the same identifier to communicate with the second device, i.e., identifier conflict.

[0181] In some embodiments, the first identifier is a binary number.

[0182] In some embodiments, the first device determines a first identifier during the access process of the second device, wherein the first device accesses the second device in the following ways: contention-free access and CBRA.

[0183] In some embodiments, in the absence of contention for access, the first identifier of the first device is assigned by the second device.

[0184] In some embodiments, under CBRA conditions, the first identifier of the first device is determined based on a first identifier range.

[0185] In some embodiments, where the first identifier is assigned to the second device, the method further includes:

[0186] The second device sends the first identifier to the first device.

[0187] Accordingly, the second device assigns a first identifier to the first device and sends the first identifier assigned to the first device to the first device.

[0188] In some embodiments, the second device sends the first identifier to the first device, including:

[0189] The second device sends a first downlink message to the first device, the first downlink message containing the first identifier.

[0190] In some embodiments, the first downlink message includes one or more of the following:

[0191] Paging message, initial downlink message, query command, selection command.

[0192] In this embodiment of the application, the first downlink message can be understood as a downlink message sent by the second device to the first device to indicate the first identifier or the range of the first identifier, and it can also be other messages or be replaced with other names.

[0193] In some embodiments, the first downlink message includes one or more identifiers, and the one or more identifiers include the first identifier.

[0194] In the case where the first downlink message carries an identifier, the first downlink message carries a first identifier, which is an identifier assigned by the second device to the current first device.

[0195] In the case where the first downlink message carries multiple identifiers, the different identifiers among the multiple identifiers carried in the first downlink message are identifiers assigned by the second device to different first devices, wherein the multiple identifiers include the first identifier assigned to the current first device.

[0196] In some embodiments, for each of one or more identifiers, the first downlink message carries the device ID of the first device corresponding to each identifier, thereby distinguishing which identifier is assigned to which first device.

[0197] In some embodiments, where the first downlink message contains multiple identifiers, different identifiers are assigned to different first devices.

[0198] In this embodiment of the application, when the first downlink message includes multiple identifiers, the first downlink message also includes resource indication information corresponding to each identifier, which is used to indicate the dedicated transmission resources allocated to each first device.

[0199] In some embodiments, the first downlink message further includes multiple resource indication messages, with different resource indication messages used to allocate dedicated transmission resources to different first devices.

[0200] In some embodiments, the transmission resources indicated by the resources in the first downlink message are used for sending the first uplink message, wherein the first uplink message is used in response to the first downlink message.

[0201] In this embodiment of the application, multiple resource indication information carried in the first downlink message are used to allocate dedicated transmission resources for the access process to different first devices, so that different first devices send the first uplink message based on different transmission resources, thereby avoiding the situation where different first devices use the same transmission resources to send the first uplink message.

[0202] In some embodiments, the dedicated transmission resources include one or more of the following: dedicated time-domain resources, dedicated frequency-domain resources, and dedicated code-domain resources.

[0203] In this embodiment, the transmission resources of different first devices are distinguished by one or more dimensions of the time domain, frequency domain, and code domain, thereby isolating different transmission resources and improving resource utilization.

[0204] In some embodiments, the first identifier range is predefined or configured by the second device.

[0205] In some embodiments, the first identifier range is used for the first device to randomly select the first identifier, or to select the first identifier based on predefined rules.

[0206] In some embodiments, the identifier assigned by the second device to the first device belongs to the assigned identifier range. The assigned identifier range can be understood as a range of identifiers, a set of identifiers, or a group of identifiers used by the second device to generate the assigned identifier. The assigned identifier range does not overlap with the first identifier range.

[0207] In this embodiment of the application, by ensuring that the allocation of the identifier range does not overlap with the first identifier range, the handle used by CBRA and the handle used by non-contention access are separated, which can avoid the conflict between the handle used by CBRA and the handle used by non-contention access, thereby avoiding the failure of non-contention access or receiving messages that do not belong to oneself.

[0208] In some embodiments, where the first identifier ranges from the second device configuration, the method further includes:

[0209] The second device sends a first downlink message to the first device. The first downlink message includes: first information or second information, the first information being used to indicate a first set of identifiers, the first identifier being an identifier in the first set of identifiers; the second information being used to indicate a first mask, the first mask being an N-bit mask out of M bits, the first identifier being M bits.

[0210] The first downlink message can be configured with one or more of the following two configuration methods:

[0211] The first downlink message contains first information indicating the first set of identifiers;

[0212] The first downlink message contains second information indicating the first mask.

[0213] When the first information indicates a first set of identifiers, the first information may indicate multiple identifiers included in the first set of identifiers, or it may indicate the minimum identifier and the maximum identifier in the first set of identifiers, so that the first device determines the first set of identifiers based on the minimum identifier and the maximum identifier.

[0214] In one example, the first information indicates all IDs between ID1 and ID2.

[0215] In one example, the first information indicates ID1 and ID2, which are used by the first device to determine all IDs between ID1 and ID2, i.e., the first identification range.

[0216] When the second information indicates the first mask, the first mask is used by the first device to determine the first identifier, wherein the first identifier is M bits, the MN bits in M ​​are determined or fixed, and are all 0s or weighted 1s, and the value of the N bits is uncertain or fixed.

[0217] In some embodiments, when the first mask is used to determine the first identifier, the N bits can be randomly generated while the values ​​of the MN bits remain unchanged, thereby obtaining the M-bit first identifier.

[0218] In some embodiments, the N bits in the first mask may be the consecutive lowest N bits, consecutive highest N bits, or other consecutive or non-consecutive N bits from the M bits.

[0219] In some embodiments, the method further includes: the second device receiving a first uplink message, the first uplink message containing the first identifier.

[0220] The second device receives the first identifier sent by the first device through the first uplink message, so that the second device knows the first identifier of the first device.

[0221] In some embodiments, when the first downlink message contains resource indication information, the second device receives the first uplink message on the transmission resources dedicated to the first device. In this case, the first uplink message can be understood as a response message to the first downlink message.

[0222] In some embodiments, the first uplink message and / or the first downlink message can be understood as a message in a CBRA procedure or a contention-free access procedure, and the transmission of the first uplink message is used to indicate the completion of the CBRA procedure or the contention-free access procedure.

[0223] In some embodiments, the first uplink message includes or carries higher-layer data and / or the device ID of the first device.

[0224] In some embodiments, the method further includes: the second device sending a second downlink message, the second downlink message being used to obtain the first identifier or to update the first identifier.

[0225] The second device sends a second downlink message to the first device to query the first identifier or update the first identifier.

[0226] In some embodiments, the second downlink message may be a Req RN instruction.

[0227] After receiving the second downlink message sent by the second device, the first device sends a response message to the second device in response to the second downlink message, wherein the response message contains a first identifier or an updated first identifier.

[0228] When the second downlink message is used to query the first identifier, the response message includes the first identifier. When the second downlink message is used to update the first identifier, the response message includes the updated first identifier.

[0229] In some embodiments, the updated first identifier is an identifier generated based on a first identifier range, and the updated first identifier is different from the first identifier.

[0230] In some embodiments, the second downlink message may carry update indication information. The value of the update indication information or the existence of the update indication information is used to indicate that the second downlink message is used to query the first identifier or to update the first identifier.

[0231] In some embodiments, where the second downlink message is used to update the first identifier, the method further includes:

[0232] The second device receives a second identifier sent by the first device. The second identifier is determined based on a second identifier range and is an updated version of the first identifier.

[0233] The updated first identifier, i.e., the second identifier, is an identifier generated based on the range of the second identifier. The range of the second identifier can be understood as the range used to select the first identifier, or a set of multiple identifiers, or a group of identifiers, and the range of the first identifier is different from the range of the second identifier. The difference between the range of the first identifier and the range of the second identifier makes the updated first identifier different from the first identifier.

[0234] The first device can randomly select an identifier from the second identifier range as the second identifier, or it can select an identifier from the second identifier range based on predefined rules as the second identifier.

[0235] In some embodiments, the second identifier range does not overlap with the assigned identifier range.

[0236] Understandably, the second device receives a response message sent by the first device in response to a second downlink message, and the response message contains a second identifier.

[0237] In some embodiments, the second identifier range is predefined or configured by the second device.

[0238] In some embodiments, when the second identifier range is configured as the second device, the second downlink message includes: third information or fourth information, the third information being used to indicate a second identifier set, the second identifier being an identifier in the second identifier set; the fourth information being used to indicate a second mask, the second mask being an N-bit mask out of M bits, the first identifier being M bits, and the second mask being different from the first mask.

[0239] In this application embodiment, the method of configuring the second identifier range for the second downlink message includes, but is not limited to, one or more of the following two configuration methods:

[0240] The second downlink message contains third information indicating the second set of identifiers;

[0241] The second downlink message contains fourth information indicating the second mask.

[0242] When the third information indicates the second set of identifiers, the second information may indicate multiple identifiers included in the second set of identifiers, or it may indicate the minimum identifier and the maximum identifier in the second set of identifiers, so that the first device determines the second set of identifiers based on the minimum identifier and the maximum identifier.

[0243] In one example, the third piece of information indicates all IDs between ID3 and ID4.

[0244] In one example, the third information indicates ID3 and ID4, which the first device uses to determine all IDs between ID3 and ID4.

[0245] When the fourth information indicates the second mask, the first device determines the second identifier based on the second mask. The second identifier is M bits, where the MN bits in M ​​are determined or fixed, and are either all 0s or weighted 1s. The value of the N bits is uncertain or fixed.

[0246] In some embodiments, when the first device determines the second identifier based on the second mask, the N bits can be randomly generated while the values ​​of the MN bits remain unchanged, thereby obtaining the M-bit second identifier.

[0247] In some embodiments, the N bits in the second mask may be the consecutive lowest N bits, consecutive highest N bits, or other consecutive or non-consecutive N bits from the M bits.

[0248] It is understandable that the positions of the N bits in the first mask and the second mask are different, or the positions of the N bits are the same but the values ​​of the N bits are different.

[0249] In some embodiments, the second device communicates with the first device based on a first identifier, including:

[0250] The second device sends a third downlink message containing the first identifier to the first device. The third downlink message containing the first identifier is used to instruct the first device to perform the operation corresponding to the third downlink message.

[0251] In some embodiments, a third downlink message can be understood as a downlink message sent by a second device received by a first device after the first device has completed a CBRA procedure or a contention-free access procedure.

[0252] If the third downlink message sent by the second device contains the first identifier, it indicates that the third downlink message is a downlink message sent to the current first device, and is used by the first device to execute the operation or command corresponding to the third downlink message.

[0253] If the third downlink message does not contain the first identifier, it indicates that the third downlink message is not a downlink message sent to the current first device, and the first device can ignore the third downlink message.

[0254] In some embodiments, the second device communicates with the first device based on a first identifier, including:

[0255] The second device receives a second uplink message, which includes the first identifier.

[0256] The second uplink message received by the second device includes a first identifier to indicate that the second uplink message was sent by the first device.

[0257] This application provides a wireless communication method applied to a wireless communication system including a first device and a second device, as shown in FIG9, including:

[0258] S901, The first device determines a first identifier, which is assigned by the second device or determined based on a range of first identifiers, and the first identifier is used for communication between the first device and the second device.

[0259] S902, the second device communicates with the first device based on the first identifier.

[0260] In the wireless communication method shown in Figure 9, the description of the first device can be found in the description of the first device in the wireless communication method shown in Figure 7, and the description of the second device can be found in the description of the second device in the wireless communication method shown in Figure 8.

[0261] The wireless communication method provided in this application will now be described through several embodiments.

[0262] The wireless communication method provided in this application can be implemented as including, but not limited to, the following embodiments one to three.

[0263] Example 1: For contention-free access, the Reader provides identification information when access is triggered.

[0264] The wireless communication method provided in Embodiment 1 is shown in Figure 10, and includes:

[0265] S1001 When the reader sends a downlink message to the A-IoT terminal, it indicates the first identifier to the A-IoT terminal.

[0266] The downlink message in S1001, i.e. the first downlink message, can be an AIOT paging message, an initial downlink message, a query command, or a select command. It can also be other names, such as inventory request, paging, inventory, etc.

[0267] In S1001, the Reader can assign a first identifier to a single A-IoT terminal, for example, by identifying the A-IoT terminal through its device ID. The first identifier assigned by the reader is an M-bit binary number, for example, M can be 16 or 8 or other values.

[0268] In S1001, the Reader can assign a first identifier to multiple A-IoT terminals, for example, by identifying these A-IoT terminals using their device IDs. The Reader assigns a different M-bit binary number as the first identifier to each A-IoT terminal. Furthermore, the Reader allocates dedicated transmission resources (e.g., dedicated time-domain / frequency-domain / code-domain resources) to each A-IoT terminal for them to send their respective responses, i.e., the first uplink message.

[0269] S1002, the A-IoT terminal sends a response to the reader.

[0270] After receiving a downlink message, the A-IoT terminal sends a response on the uplink resources indicated by the downlink message. The response message may contain the A-IoT terminal's device ID and / or higher-layer data.

[0271] S1003, the reader sends a downlink message to the A-IoT terminal, which carries (a first identifier and a command).

[0272] The A-IoT terminal uses the first identifier information obtained by S1001 to listen to the downlink message of the reader, namely the third downlink message. If the downlink message contains the first identifier, the A-IoT terminal processes the command in the downlink message; if the downlink message does not contain the first identifier, the A-IoT terminal ignores the downlink message.

[0273] In this embodiment, since contention-free access does not require random access, the A-IoT terminal does not need to generate a random ID like CBRA. However, a handle is required during communication between the A-IoT terminal and the reader. This is to enable communication between a specific A-IoT terminal and a specific reader in scenarios with multiple readers and multiple A-IoT terminals. Therefore, when the communication handle under contention-free access is assigned to the A-IoT terminal by the reader, a handle is available for subsequent one-to-one communication.

[0274] Example 2: For CBRA, the reader instructs the device to generate a random ID from a specific set of IDs and access the reader.

[0275] The wireless communication method provided in Embodiment 2 is shown in Figure 11, and includes:

[0276] S1101. When the reader sends a downlink message to the A-IoT terminal, it indicates the first identifier group to the A-IoT terminal.

[0277] The downlink message in S1101, i.e. the first downlink message, can be an AIOT paging message, an initial downlink message, a query command, or a select command. It can also be other names, such as inventory request, paging, inventory, etc.

[0278] The identifier is an M-bit binary number, for example, M can be 16 or 8 or other values.

[0279] The first group of identifiers can be an identifier range, such as all IDs from ID 1 to ID 2.

[0280] The first identifier group can be an ID group composed of N bit masks in an M-bit binary number. That is, these N bits in the M bits can be randomly generated, and the other M-N bits are all 0s or all 1s. The N bit mask can be the highest N bits, the lowest N bits, or other specific N bits in the M-bit binary number.

[0281] S1102, the A-IoT terminal sends the first identifier to the reader.

[0282] After receiving the downlink message, the A-IoT terminal randomly generates an M-bit number, i.e., the first identifier, from the first identifier group, and sends the determined M-bit number to the reader. It can also send other higher-layer data and / or the device ID of the A-IoT terminal at the same time.

[0283] S1103, the reader sends the Req RN command to the A-IoT terminal.

[0284] The Req RN command sent by the reader (instructing the reader to retrieve or update the handle).

[0285] S1104, the A-IoT terminal sends a handle to the reader.

[0286] When the Req RN instruction tells the reader to obtain the handle, the A-IoT terminal reports the first identifier to the reader.

[0287] When the Req RN instruction tells the reader to update the handle, the A-IoT terminal generates a random number (as the handle) from the first identifier group or the second identifier group and reports it to the reader. The second identifier group can be carried by the require RN instruction.

[0288] Example 3: For CBRA, the protocol stipulates that the device generates a random ID from a specific set of IDs to access the reader.

[0289] The wireless communication method provided in Embodiment 3 is shown in Figure 12, and includes:

[0290] S1201, the reader sends downlink messages to the A-IoT terminal.

[0291] The downlink message in S1201, i.e. the first downlink message, can be an AIOT paging message, an initial downlink message, a query command, or a select command. It can also be named in other ways, such as inventory request, paging, inventory, etc.

[0292] The downlink messages here do not carry identifier groups.

[0293] S1202, the A-IoT terminal sends the first identifier to the reader.

[0294] After receiving the downlink message, the A-IoT terminal randomly generates an M-bit number from the first identifier group as the first identifier and sends it to the reader (it can also send other higher-layer data and / or device ID at the same time). The first identifier group is defined by the protocol.

[0295] S1203, the reader sends the Req RN command to the A-IoT terminal.

[0296] The Req RN command sent by the reader (instructing the reader to retrieve or update the handle).

[0297] S1204, the A-IoT terminal sends a handle to the reader.

[0298] When the Req RN instruction tells the reader to obtain the handle, the A-IoT terminal reports the first identifier to the reader.

[0299] When the Req RN instruction tells the reader to update the handle, the A-IoT terminal generates a random number (as the handle) from the first identifier group or the second identifier group and reports it to the reader. The second identifier group can be carried by the require RN instruction.

[0300] If the CBRA randomly generates IDs from the entire M-bit binary space, it can easily cause conflicts with the handles assigned to A-IoT terminals by the reader in contention-free access. This can easily lead to contention-free access failures or receiving instructions that do not belong to the device. In this embodiment, separating the CBRA's random ID pool, i.e., the first identifier group, from the handles used for contention-free access can avoid conflicts between them.

[0301] If the CBRA randomly generates IDs from the entire M-bit binary space, it can easily cause conflicts with the handles assigned to A-IoT terminals by the reader in contention-free access. This can easily lead to contention-free access failures or receiving instructions that do not belong to the device. In embodiments two and three of this application, separating the random ID pool of the CBRA, i.e., the first identifier group, from the handles used for contention-free access can avoid conflicts between them.

[0302] It should be noted that in Embodiments 2 and 3, after S1102 or S1202, the reader communicates with the A-IoT terminal based on the determined first identifier used as the handle.

[0303] In the above embodiments one to three, the reader can be a base station or an intermediate UE.

[0304] The preferred embodiments of this application have been described in detail above with reference to the accompanying drawings. However, this application is not limited to the specific details of the above embodiments. Within the scope of the technical concept of this application, various simple modifications can be made to the technical solutions of this application, and these simple modifications all fall within the protection scope of this application. For example, the various specific technical features described in the above specific embodiments can be combined in any suitable manner without contradiction. To avoid unnecessary repetition, this application will not describe the various possible combinations separately. Furthermore, various different embodiments of this application can also be arbitrarily combined, as long as they do not violate the spirit of this application, they should also be considered as the content disclosed in this application. Moreover, without conflict, the various embodiments and / or the technical features in the various embodiments described in this application can be arbitrarily combined with the prior art, and the resulting technical solutions should also fall within the protection scope of this application.

[0305] It should also be understood that in the various method embodiments of this application, the sequence number of each process does not imply 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 this application. Furthermore, in the embodiments of this application, the terms "downlink," "uplink," and "sidelink" are used to indicate the transmission direction of signals or data. "Downlink" indicates that the transmission direction of signals or data is a first direction from the site to the user equipment in the cell; "uplink" indicates that the transmission direction of signals or data is a second direction from the user equipment in the cell to the site; and "sidelink" indicates that the transmission direction of signals or data is a third direction from user equipment 1 to user equipment 2. For example, "downlink signal" indicates that the transmission direction of the signal is the first direction. Additionally, in the embodiments of this application, the term "and / or" is merely a description of the association relationship between related objects, indicating that three relationships can exist. Specifically, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Furthermore, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0306] Figure 13 is a schematic diagram of the structure of the first device provided in an embodiment of this application. As shown in Figure 13, the first device 1300 includes:

[0307] The determining unit 1301 is configured to determine a first identifier, which is assigned by the second device or determined based on a range of first identifiers, and the first identifier is used for communication between the first device and the second device.

[0308] In some embodiments, the first device 1300 further includes a second communication unit configured to receive the first identifier sent by the second device when the first identifier is assigned to the second device.

[0309] In some embodiments, the second communication unit is further configured to receive a first downlink message sent by the second device, the first downlink message including the first identifier.

[0310] In some embodiments, the first downlink message includes one or more identifiers, and the one or more identifiers include the first identifier.

[0311] In some embodiments, where the first downlink message contains multiple identifiers, different identifiers are assigned to different first devices.

[0312] In some embodiments, the first downlink message further includes multiple resource indication messages, with different resource indication messages used to allocate dedicated transmission resources to different first devices.

[0313] In some embodiments, the dedicated transmission resources include one or more of the following:

[0314] Dedicated time-domain resources, dedicated frequency-domain resources, and dedicated code-domain resources.

[0315] In some embodiments, the determining unit is further configured to determine the first identifier based on the first identifier range if the first identifier is determined based on the first identifier range.

[0316] In some embodiments, the first identifier range is predefined or configured by the second device.

[0317] In some embodiments, the second communication unit is further configured to receive a first downlink message sent by the second device when the first identifier range is configured for the second device. The first downlink message includes: first information or second information, wherein the first information is used to indicate a first identifier set, and the first identifier is an identifier in the first identifier set; and the second information is used to indicate a first mask, wherein the first mask is an N-bit mask out of M bits, and the first identifier is M bits.

[0318] In some embodiments, the second communication unit is further configured to send a first uplink message, the first uplink message including the first identifier.

[0319] In some embodiments, the second communication unit is further configured to receive a second downlink message, the second downlink message being used to obtain the first identifier or to update the first identifier.

[0320] In some embodiments,

[0321] The determining unit 1301 is further configured to determine the second identifier based on the range of the second identifier when the second downlink message is used to update the first identifier, wherein the second identifier is the updated first identifier;

[0322] The second communication unit is also configured to transmit the second identifier.

[0323] In some embodiments, the second identifier range is predefined or configured by the second device.

[0324] In some embodiments, when the second identifier range is configured as the second device, the second downlink message includes: third information or fourth information, the third information being used to indicate a second identifier set, the second identifier being an identifier in the second identifier set; the fourth information being used to indicate a second mask, the second mask being an N-bit mask out of M bits, the first identifier being M bits, and the second mask being different from the first mask.

[0325] In some embodiments, the first downlink message includes one or more of the following:

[0326] Paging message, initial downlink message, query command, selection command.

[0327] In some embodiments, the determining unit 1301 is further configured to process the third downlink message based on the first identifier.

[0328] In some embodiments, the determining unit 1301 is further configured to

[0329] If the third downlink message contains the first identifier, perform the operation corresponding to the third downlink message; and / or

[0330] If the third downlink message does not contain the first identifier, the third downlink message is ignored.

[0331] In some embodiments, the second communication unit is further configured to send a second uplink message, the second uplink message including the first identifier.

[0332] In some embodiments, the first device is a terminal device or an Internet of Things (IoT) terminal.

[0333] In some embodiments, the second device is an intermediate device, a relay device, or a network device.

[0334] The second communication unit in the first device can be implemented by the transceiver in the first device. The determination unit in the first device can be implemented by the processor in the first device.

[0335] Figure 14 is a schematic diagram of the structure of the second device provided in an embodiment of this application. As shown in Figure 14, the second device 1400 includes:

[0336] The first communication unit 1401 is configured to communicate with the first device based on a first identifier, wherein the first identifier is assigned by the second device or determined based on a range of the first identifier.

[0337] In some embodiments, the first communication unit 1401 is further configured to send the first identifier to the first device when the first identifier is assigned to the second device.

[0338] In some embodiments, the first communication unit 1401 is further configured to send a first downlink message to the first device, the first downlink message including the first identifier.

[0339] In some embodiments, the first downlink message includes one or more identifiers, and the one or more identifiers include the first identifier.

[0340] In some embodiments, where the first downlink message contains multiple identifiers, different identifiers are assigned to different first devices.

[0341] In some embodiments, the first downlink message further includes multiple resource indication messages, with different resource indication messages used to allocate dedicated transmission resources to different first devices.

[0342] In some embodiments, the dedicated transmission resources include one or more of the following:

[0343] Dedicated time-domain resources, dedicated frequency-domain resources, and dedicated code-domain resources.

[0344] In some embodiments, the first identifier range is predefined or configured by the second device.

[0345] In some embodiments, the first communication unit 1401 is further configured to send a first downlink message to the first device when the first identifier range is configured as the second device. The first downlink message includes: first information or second information, the first information being used to indicate a first identifier set, the first identifier being an identifier in the first identifier set; the second information being used to indicate a first mask, the first mask being an N-bit mask out of M bits, the first identifier being M bits.

[0346] In some embodiments, the first communication unit 1401 is further configured to receive a first uplink message, the first uplink message including the first identifier.

[0347] In some embodiments, the first communication unit 1401 is further configured to send a second downlink message, the second downlink message being used to obtain the first identifier or to update the first identifier.

[0348] In some embodiments, the first communication unit 1401 is further configured to receive a second identifier sent by the first device when the second downlink message is used to update the first identifier, wherein the second identifier is determined based on a second identifier range and the second identifier is the updated first identifier.

[0349] In some embodiments, the second identifier range is predefined or configured by the second device.

[0350] In some embodiments, when the second identifier range is configured as the second device, the second downlink message includes: third information or fourth information, the third information being used to indicate a second identifier set, the second identifier being an identifier in the second identifier set; the fourth information being used to indicate a second mask, the second mask being an N-bit mask out of M bits, the first identifier being M bits, and the second mask being different from the first mask.

[0351] In some embodiments, the first downlink message includes one or more of the following:

[0352] Paging message, initial downlink message, query command, selection command.

[0353] In some embodiments, the first communication unit 1401 is further configured to send a third downlink message containing the first identifier to the first device, wherein the third downlink message containing the first identifier is used to instruct the first device to perform an operation corresponding to the third downlink message.

[0354] In some embodiments, the first communication unit 1401 is further configured to receive a second uplink message, the second uplink message including the first identifier.

[0355] In some embodiments, the first device is a terminal device or an Internet of Things (IoT) terminal.

[0356] In some embodiments, the second device is an intermediate device, a relay device, or a network device.

[0357] The first communication unit in the second device can be implemented by the transceiver in the first device.

[0358] Those skilled in the art should understand that the descriptions of the first or second device in the embodiments of this application can be understood with reference to the descriptions of the wireless communication methods in the embodiments of this application.

[0359] Figure 15 is a schematic structural diagram of a communication device 1500 provided in an embodiment of this application. This communication device can be a first device or a second device. The communication device 1500 shown in Figure 15 includes a processor 1510, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0360] Optionally, as shown in FIG15, the communication device 1500 may further include a memory 1520. The processor 1510 may retrieve and run computer programs from the memory 1520 to implement the methods described in the embodiments of this application.

[0361] The memory 1520 can be a separate device independent of the processor 1510, or it can be integrated into the processor 1510.

[0362] Optionally, as shown in FIG15, the communication device 1500 may further include a transceiver 1530, and the processor 1510 may control the transceiver 1530 to communicate with other devices. Specifically, it may send information or data to other devices or receive information or data sent by other devices.

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

[0364] Optionally, the communication device 1500 may specifically be the second device in the embodiments of this application, and the communication device 1500 may implement the corresponding processes implemented by the second device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0365] Optionally, the communication device 1500 may specifically be the first device in the embodiments of this application, and the communication device 1500 may implement the corresponding processes implemented by the first device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0366] Figure 16 is a schematic structural diagram of a chip according to an embodiment of this application. The chip 1600 shown in Figure 16 includes a processor 1610, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0367] Optionally, as shown in FIG16, chip 1600 may further include memory 1620. Processor 1610 can call and run computer programs from memory 1620 to implement the methods in the embodiments of this application.

[0368] The memory 1620 can be a separate device independent of the processor 1610, or it can be integrated into the processor 1610.

[0369] Optionally, the chip 1600 may also include an input interface 1630. The processor 1610 can control the input interface 1630 to communicate with other devices or chips; specifically, it can acquire information or data sent by other devices or chips.

[0370] Optionally, the chip 1600 may also include an output interface 1640. The processor 1610 can control the output interface 1640 to communicate with other devices or chips, specifically, to output information or data to other devices or chips.

[0371] Optionally, the chip can be applied to the second device in the embodiments of this application, and the chip can implement the corresponding processes implemented by the second device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0372] Optionally, the chip can be applied to the first device in the embodiments of this application, and the chip can implement the corresponding processes implemented by the first device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0373] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0374] Figure 17 is a schematic block diagram of a communication system 1700 provided in an embodiment of this application. As shown in Figure 17, the communication system 1700 includes a first device 1710 and a second device 1720.

[0375] The first device 1710 can be used to implement the corresponding functions implemented by the first device in the above method, and the second device 1720 can be used to implement the corresponding functions implemented by the second device in the above method. For the sake of brevity, these will not be described in detail here.

[0376] It should be understood that the processor in the embodiments of this application may be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the above method embodiments can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor described above can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.

[0377] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0378] It should be understood that the above-described memory is exemplary and not a limiting description. For example, the memory in the embodiments of this application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DR RAM), etc. That is to say, the memory in the embodiments of this application is intended to include, but is not limited to, these and any other suitable types of memory.

[0379] This application also provides a computer-readable storage medium for storing computer programs.

[0380] Optionally, the computer-readable storage medium can be applied to the second device in the embodiments of this application, and the computer program causes the computer to execute the corresponding processes implemented by the second device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0381] Optionally, the computer-readable storage medium can be applied to the first device in the embodiments of this application, and the computer program causes the computer to execute the corresponding processes implemented by the first device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0382] This application also provides a computer program product, including computer program instructions.

[0383] Optionally, the computer program product can be applied to the second device in the embodiments of this application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the second device in the various methods of the embodiments of this application. For the sake of brevity, they will not be described in detail here.

[0384] Optionally, the computer program product can be applied to the first device in the embodiments of this application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the first device in the various methods of the embodiments of this application. For the sake of brevity, they will not be described in detail here.

[0385] This application also provides a computer program.

[0386] Optionally, the computer program can be applied to the second device in the embodiments of this application. When the computer program is run on a computer, it causes the computer to execute the corresponding processes implemented by the second device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0387] Optionally, the computer program can be applied to the first device in the embodiments of this application. When the computer program is run on a computer, it causes the computer to execute the corresponding processes implemented by the first device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0388] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0389] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0390] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0391] The units described as separate components may or may not be physically separate. 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 the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0392] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0393] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0394] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A wireless communication method, the method comprising: The first device determines a first identifier, which is assigned by the second device or determined based on a range of first identifiers, and the first identifier is used for communication between the first device and the second device.

2. The method according to claim 1, wherein, When the first identifier is assigned by the second device, the first device determines the first identifier by: The first device receives the first identifier sent by the second device.

3. The method according to claim 2, wherein, The first device receives the first identifier sent by the second device, including: The first device receives a first downlink message sent by the second device, the first downlink message containing the first identifier.

4. The method according to claim 3, wherein, The first downlink message contains one or more identifiers, and the one or more identifiers include the first identifier.

5. The method according to claim 4, wherein, In the case where the first downlink message contains multiple identifiers, different identifiers are assigned to different first devices.

6. The method according to claim 5, wherein, The first downlink message also includes multiple resource indication information, with different resource indication information used to allocate dedicated transmission resources to different first devices.

7. The method according to claim 6, wherein, The dedicated transmission resources include one or more of the following: Dedicated time-domain resources, dedicated frequency-domain resources, and dedicated code-domain resources.

8. The method according to any one of claims 1 to 7, wherein, When the first identifier is determined based on a first identifier range, the first device determines the first identifier, including: The first device determines the first identifier based on the first identifier range.

9. The method according to claim 8, wherein, The first identifier range is either predefined or configured by the second device.

10. The method according to claim 9, wherein, When the first identifier range is configured with the second device, the method further includes: The first device receives a first downlink message sent by the second device. The first downlink message includes: first information or second information, wherein the first information is used to indicate a first set of identifiers, and the first identifier is an identifier in the first set of identifiers; and the second information is used to indicate a first mask, wherein the first mask is an N-bit mask out of M bits, and the first identifier is M bits.

11. The method according to any one of claims 8 to 10, wherein, The method further includes: The first device sends a first uplink message, which contains the first identifier.

12. The method according to any one of claims 8 to 11, wherein, The method further includes: The first device receives a second downlink message, which is used to obtain the first identifier or to update the first identifier.

13. The method according to claim 12, wherein, When the second downlink message is used to update the first identifier, the method further includes: The first device determines the second identifier based on the second identifier range, and the second identifier is the updated first identifier; The first device sends the second identifier.

14. The method according to claim 13, wherein, The second identifier range is either predefined or configured by the second device.

15. The method according to claim 14, wherein, When the second identifier range is configured as the second device, the second downlink message includes: third information or fourth information, wherein the third information is used to indicate a second identifier set, and the second identifier is an identifier in the second identifier set; the fourth information is used to indicate a second mask, wherein the second mask is an N-bit mask out of M bits, the first identifier is M bits, and the second mask is different from the first mask.

16. The method according to any one of claims 3 to 7, 10, wherein, The first downlink message includes one or more of the following: Paging message, initial downlink message, query command, selection command.

17. The method according to any one of claims 1 to 16, wherein, The method further includes: The first device processes the third downlink message based on the first identifier.

18. The method according to claim 17, wherein, The first device processes a third downlink message based on the first identifier, including: If the third downlink message contains the first identifier, the first device performs the operation corresponding to the third downlink message; and / or If the third downlink message does not contain the first identifier, the first device ignores the third downlink message.

19. The method according to any one of claims 1 to 18, wherein, The method further includes: The first device sends a second uplink message, which contains the first identifier.

20. The method according to any one of claims 1 to 19, wherein, The first device is a terminal device or an Internet of Things (IoT) terminal.

21. The method according to any one of claims 1 to 20, wherein, The second device is an intermediate device, a relay device, or a network device.

22. A wireless communication method, the method comprising: The second device communicates with the first device based on a first identifier, which is assigned by the second device or determined based on a range of the first identifier.

23. The method according to claim 22, wherein, When the first identifier is assigned to the second device, the method further includes: The second device sends the first identifier to the first device.

24. The method according to claim 23, wherein, The second device sends the first identifier to the first device, including: The second device sends a first downlink message to the first device, the first downlink message containing the first identifier.

25. The method according to claim 24, wherein, The first downlink message contains one or more identifiers, and the one or more identifiers include the first identifier.

26. The method of claim 25, wherein, In the case where the first downlink message contains multiple identifiers, different identifiers are assigned to different first devices.

27. The method according to claim 26, wherein, The first downlink message also includes multiple resource indication information, with different resource indication information used to allocate dedicated transmission resources to different first devices.

28. The method according to claim 27, wherein, The dedicated transmission resources include one or more of the following: Dedicated time-domain resources, dedicated frequency-domain resources, and dedicated code-domain resources.

29. The method according to any one of claims 22 to 28, wherein, The first identifier range is either predefined or configured by the second device.

30. The method according to claim 29, wherein, When the first identifier range is configured with the second device, the method further includes: The second device sends a first downlink message to the first device. The first downlink message includes: first information or second information, the first information being used to indicate a first set of identifiers, the first identifier being an identifier in the first set of identifiers; the second information being used to indicate a first mask, the first mask being an N-bit mask out of M bits, the first identifier being M bits.

31. The method according to claim 29 or 30, wherein, The method further includes: The second device receives a first uplink message, which contains the first identifier.

32. The method according to any one of claims 29 to 31, wherein, The method further includes: The second device sends a second downlink message, which is used to obtain the first identifier or to update the first identifier.

33. The method according to claim 32, wherein, When the second downlink message is used to update the first identifier, the method further includes: The second device receives a second identifier sent by the first device. The second identifier is determined based on a second identifier range and is an updated version of the first identifier.

34. The method according to claim 33, wherein, The second identifier range is either predefined or configured by the second device.

35. The method according to claim 34, wherein, When the second identifier range is configured as the second device, the second downlink message includes: third information or fourth information, wherein the third information is used to indicate a second identifier set, and the second identifier is an identifier in the second identifier set; the fourth information is used to indicate a second mask, wherein the second mask is an N-bit mask out of M bits, the first identifier is M bits, and the second mask is different from the first mask.

36. The method according to any one of claims 24 to 28, 30, wherein, The first downlink message includes one or more of the following: Paging message, initial downlink message, query command, selection command.

37. The method according to any one of claims 22 to 36, wherein, The second device communicates with the first device based on the first identifier, including: The second device sends a third downlink message containing the first identifier to the first device. The third downlink message containing the first identifier is used to instruct the first device to perform the operation corresponding to the third downlink message.

38. The method according to any one of claims 22 to 37, wherein, The second device communicates with the first device based on the first identifier, including: The second device receives a second uplink message, which includes the first identifier.

39. The method according to any one of claims 22 to 38, wherein, The first device is a terminal device or an Internet of Things (IoT) terminal.

40. The method according to any one of claims 22 to 39, wherein, The second device is an intermediate device, a relay device, or a network device.

41. A first device, comprising: The determining unit is configured to determine a first identifier, which is assigned by the second device or determined based on a range of first identifiers, and the first identifier is used for communication between the first device and the second device.

42. A second device, comprising: The first communication unit is configured to communicate with the first device based on a first identifier, wherein the first identifier is assigned by the second device or determined based on a range of the first identifier.

43. A first device, comprising: A processor and a memory for storing a computer program, the processor for calling and running the computer program stored in the memory to perform the method as described in any one of claims 1 to 21.

44. A second device, comprising: A processor and a memory for storing a computer program, the processor for calling and running the computer program stored in the memory to perform the method as described in any one of claims 22 to 40.

45. A chip, comprising: A processor for retrieving and running a computer program from memory, causing a device having the chip mounted to perform the method as claimed in any one of claims 1 to 21, or the method as claimed in any one of claims 22 to 40.

46. ​​A computer-readable storage medium for storing a computer program, the execution of which causes the computer to perform the method as claimed in any one of claims 1 to 21, or the method as claimed in any one of claims 22 to 40.

47. A computer program product comprising computer program instructions, the execution of which causes a computer to perform the method as claimed in any one of claims 1 to 21, or to perform the method as claimed in any one of claims 22 to 40.

48. A computer program, the execution of which causes a computer to perform the method as claimed in any one of claims 1 to 21, or the method as claimed in any one of claims 22 to 40.

Images