Communication method and apparatus

Abstract

The present application provides a communication method and apparatus. The method comprises: a first device sends first information, and receives attribute information of a second device on a resource corresponding to the second device, wherein the first information comprises a mapping relationship, and the mapping relationship is a mapping relationship between identification information of the second device and the resource corresponding to the second device. The first device carries, in the first information, the mapping relationship between the identification information of the second device and the resource corresponding to the second device, so that the second device that receives the first information can accurately determine, in a timely manner on the basis of the mapping relationship, the resource corresponding to the second device, and the second device can further exchange information with the first device on the basis of the resource corresponding to the second device, thereby effectively reducing the probability of resource collisions when multiple second devices respectively exchange information with the first device, enabling the multiple second devices to simultaneously respond to the first device without causing conflicts, and thus effectively improving tag inventory efficiency.

Description

A communication method and apparatus

[0001] Cross-references to related applications

[0002] This application claims priority to Chinese Patent Application No. 202411456956.2, filed on October 17, 2024, entitled "A Communication Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application relates to the field of communication technology, and in particular to a communication method and apparatus. Background Technology

[0004] Passive Internet of Things (AIoT) is an important technology in the Internet of Things (IoT) field. Its core feature is that terminal node devices do not require external power cords or built-in batteries. Instead, they collect energy from the environment, such as radio wave energy, heat energy, vibration energy, and mechanical energy, and convert this energy into electrical energy that can drive the device's circuitry, thereby enabling functions such as data acquisition, transmission, and distributed computing.

[0005] Radio Frequency Identification (RFID) technology, as a passive Internet of Things (IoT) technology, has been widely applied in various fields, such as logistics management, inventory management, item tracking, security authentication, asset management, intelligent transportation, and industrial automation. RFID technology is a non-contact automatic identification technology that uses radio frequency (RF) for non-contact, two-way data communication to identify targets (such as tags or RFID cards). Specifically, RFID technology uses RF to read and write to tags (or RFID cards) to identify them and exchange information and data with them.

[0006] Currently, existing RFID systems typically employ time-division multiple access (TDMA) based inventory methods, such as the Aloha protocol (Additive Link On-line Hawaii, ALOHA), to perform tag inventory (also known as tag counting or tag identification) processes. This involves using the ALOHA protocol to individually count a large number of tags to obtain their information. However, when inventorying a large number of tags, using the ALOHA protocol to count each tag individually requires a considerable amount of time, resulting in relatively low inventory efficiency. Summary of the Invention

[0007] This application provides a communication method and apparatus to effectively improve the efficiency of tag inventory.

[0008] Firstly, this application provides a communication method, which can be executed by a first device or a module in the first device (such as a processor, processing unit, chip system, circuit, or chip). Optionally, the method can also be implemented by a logical node, logical module, or software capable of implementing all or part of the functions of the first device. For example, the following describes the execution of the communication method by the first device. The method may include the following steps: the first device sends first information, and then the first device can receive attribute information of the second device on the resources corresponding to the second device. The first information may include a mapping relationship, which can describe the mapping relationship between the identification information of the second device and the resources corresponding to the second device.

[0009] In this method, the first device, by carrying the mapping relationship between the identification information of the second device and the resources corresponding to the second device in the first information, can facilitate the second device, which receives (or monitors) the first information, to determine the resources corresponding to the second device (which can be understood as the exclusive resources corresponding to the second device) in a timely and accurate manner according to the mapping relationship. Furthermore, the second device can interact with the first device based on the resources corresponding to the second device. This can effectively reduce the probability of resource collisions when multiple second devices interact with the first device separately, and help reduce resource conflicts. Thus, multiple second devices can respond to the first device simultaneously without causing conflicts, effectively avoiding the waiting time of the time-division multiplexing-based inventory method in the existing solution. In turn, it can effectively improve the inventory efficiency (also known as inventory speed) and accuracy of the second device (such as the tag).

[0010] Secondly, this application provides a communication method, which can be executed by a second device or a module in the second device (such as a processor, processing unit, chip system, circuit, or chip). Optionally, the method can also be implemented by a logical node, logical module, or software capable of implementing all or part of the functions of the second device. For example, the following describes the execution of the communication method by a second device. The method may include the following steps: the second device receives first information; subsequently, if the second device is connected to the first device, it can send attribute information of the second device on the resources corresponding to the second device. The first information may include a mapping relationship, which can describe the mapping relationship between the identification information of the second device and the resources corresponding to the second device.

[0011] The technical effects achievable in the second aspect are similar to those achievable in the first aspect, and will not be elaborated upon here.

[0012] Based on the first or second aspect, in one possible implementation, the resources corresponding to the second device may include at least one of the following: time domain resources, frequency domain resources, and code domain resources.

[0013] For example, one scenario is that different second devices have different time-domain resources, but at least one of the frequency-domain or code-domain resources is the same. Another scenario is that different second devices have different frequency-domain resources, but at least one of the time-domain or code-domain resources is the same. Yet another scenario is that different second devices have different code-domain resources, but at least one of the time-domain or code-domain resources is the same. Through this configuration, efficient resource utilization can be achieved, and it is convenient for different second devices to interact with the reader on different resources. This effectively reduces resource conflicts when multiple second devices interact with the first device, thereby significantly improving the second-device identification efficiency of the RFID system.

[0014] Based on the first or second aspect, in one possible implementation, the mapping relationship describing the mapping relationship between the identification information of the second device and the resources corresponding to the second device includes:

[0015] The mapping relationship can describe the mapping relationship between the identification information of the second device and the information of the time-domain resources corresponding to the second device;

[0016] The mapping relationship can describe the mapping relationship between the identification information of the second device and the information of the frequency domain resources corresponding to the second device;

[0017] The mapping relationship can describe the mapping relationship between the identification information of the second device and the information of the corresponding code field resources of the second device; or,

[0018] The mapping relationship can describe the mapping relationship between the identification information of the second device and the information of the time and frequency resources corresponding to the second device.

[0019] The above implementation method can achieve flexible configuration of mapping relationships, which helps to provide different resource allocation methods, thereby improving resource utilization efficiency and effectively avoiding resource waste.

[0020] Based on the first or second aspect, in one possible implementation, the information of the time-domain resource corresponding to the second device may include the start position and length of the time-domain resource; or,

[0021] The information about the time-domain resources corresponding to the second device may include the time-domain resource number.

[0022] The above implementation method enables flexible configuration of time-domain resources corresponding to the second device, facilitating refined management of these resources. For example, by flexibly configuring or allocating the starting position and length of corresponding time-domain resources for different second devices, efficient utilization of these resources can be achieved. Furthermore, it facilitates information interaction between different second devices and the first device on their respective time-domain resources, effectively reducing resource conflicts when multiple second devices interact with the first device, thereby significantly improving the identification efficiency of the second device in the RFID system. In addition, since the starting position and length of the time-domain resources corresponding to different second devices can be flexibly allocated according to actual needs, the configuration of these resources for different second devices is highly flexible.

[0023] Based on the first or second aspect, in one possible implementation, the first information may further include the starting position of the time-domain resource set, the length of the time-domain resources, and the interval between two adjacent time-domain resources in the time-domain resource set, wherein the time-domain resource set may include multiple time-domain resources.

[0024] In the above implementation, by configuring or allocating the starting position of a shared time-domain resource set, the length of the time-domain resources included in the time-domain resource set, and the interval between two adjacent time-domain resources in the time-domain resource set for different second devices, it is possible for different second devices to promptly and accurately determine multiple time-domain resources based on the starting position of the time-domain resource set, the length of the time-domain resources included in the time-domain resource set, and the interval between two adjacent time-domain resources in the time-domain resource set. Furthermore, based on the number of their respective time-domain resources, they can determine their respective time-domain resources from among the multiple time-domain resources. This further enables different second devices to interact with the first device on their respective time-domain resources, which helps to effectively reduce resource conflicts when multiple second devices interact with the first device, thereby effectively improving the identification efficiency of the second device in the RFID system.

[0025] Based on the first or second aspect, in one possible implementation, the first information may further include the system frame number and time slot number required for the first device to synchronize with the second device.

[0026] The above implementation method can facilitate timely and accurate synchronization between at least one second device and the first device.

[0027] Based on the second aspect, in one possible implementation, the method further includes:

[0028] The second device can determine the first time slot based on the system frame number and time slot number. Then, the second device can determine the time domain resources corresponding to the second device in the first time slot based on the start position and length of the time domain resources corresponding to the second device.

[0029] The above implementation method enables the second device to determine the time domain resources corresponding to the second device in a timely and accurate manner based on the start position and length of the time domain resources corresponding to the second device.

[0030] Based on the second aspect, in one possible implementation, the method further includes:

[0031] The second device can determine the second time slot based on the system frame number and time slot number. Then, the second device can determine multiple time-domain resources in the second time slot based on the starting position of the time-domain resource set, the length of the time-domain resources, and the interval between two adjacent time-domain resources in the time-domain resource set. Then, the second device can determine the time-domain resource corresponding to the second device from among the multiple time-domain resources based on the number of the time-domain resource corresponding to the second device.

[0032] The above implementation method enables the second device to determine the time domain resource corresponding to the second device in a timely and accurate manner based on the starting position of the time domain resource set, the length of the time domain resource, the interval between two adjacent time domain resources in the time domain resource set, and the number of the time domain resource corresponding to the second device.

[0033] Based on the first or second aspect, in one possible implementation, the information of the frequency domain resources corresponding to the second device may include the starting position and frequency domain width of the frequency domain resources; or,

[0034] The information about the frequency domain resources corresponding to the second device may include the number of the frequency domain resources.

[0035] The above implementation allows for flexible configuration of frequency domain resources for the second device, facilitating refined management of these resources. For example, by flexibly configuring or allocating the starting position and bandwidth of corresponding frequency domain resources for different tags, efficient utilization of these resources can be achieved. This also facilitates information exchange between different tags and the reader on their respective frequency domain resources, effectively reducing resource conflicts when multiple second devices interact with the first device, thereby significantly improving the identification efficiency of the second device in the RFID system. Furthermore, since the starting position and bandwidth of the frequency domain resources for different second devices can be flexibly allocated according to actual needs, the configuration of frequency domain resources for different second devices is highly flexible.

[0036] Based on the first or second aspect, in one possible implementation, the first information may further include the starting position of the frequency domain resource set, the frequency domain width of the frequency domain resources, and the interval between two adjacent frequency domain resources in the frequency domain resource set, wherein the frequency domain resource set may include multiple frequency domain resources.

[0037] In the above implementation, by configuring or allocating the starting position of a shared frequency domain resource set, the frequency domain width of the frequency domain resources included in the frequency domain resource set, and the interval between two adjacent frequency domain resources in the frequency domain resource set for different second devices, it is possible for different second devices to promptly and accurately determine multiple frequency domain resources based on the starting position of the frequency domain resource set, the frequency domain width of the frequency domain resources included in the frequency domain resource set, and the interval between two adjacent frequency domain resources in the frequency domain resource set. Furthermore, based on the number of their respective frequency domain resources, they can determine their corresponding frequency domain resources from among the multiple frequency domain resources. This further enables different second devices to interact with the first device on their respective corresponding frequency domain resources, which helps to effectively reduce resource conflicts when multiple second devices interact with the first device, thereby effectively improving the identification efficiency of the second device in the RFID system.

[0038] Based on the second aspect, in one possible implementation, the method further includes:

[0039] The second device can determine the frequency domain resources corresponding to the second device based on the starting position and frequency domain width of the frequency domain resources.

[0040] It enables the second device to determine the frequency domain resources corresponding to the second device in a timely and accurate manner based on the starting position and frequency domain width of the frequency domain resources corresponding to the second device.

[0041] Based on the second aspect, in one possible implementation, the method further includes:

[0042] The second device can determine multiple frequency domain resources based on the starting position of the frequency domain resource set, the frequency domain width of the frequency domain resources, and the interval between two adjacent frequency domain resources in the frequency domain resource set. Then, the second device can determine the frequency domain resource corresponding to the second device from among the multiple frequency domain resources based on the number of the frequency domain resource corresponding to the second device.

[0043] The above implementation method enables the second device to determine the frequency domain resource corresponding to the second device in a timely and accurate manner based on the starting position of the frequency domain resource set, the frequency domain width of the frequency domain resource, the interval between two adjacent frequency domain resources in the frequency domain resource set, and the number of the frequency domain resource corresponding to the second device.

[0044] Based on the first or second aspect, in one possible implementation, the information of the time-frequency resources corresponding to the second device may include the start position and length of the time-domain resources, and the start position and frequency width of the frequency-domain resources; or,

[0045] The information of the time-frequency resources corresponding to the second device may include the number of the time-domain resource and the number of the frequency-domain resource.

[0046] The above implementation method enables flexible configuration of time-frequency resource information corresponding to the second device, facilitating refined management of these resources. For example, by flexibly configuring or allocating the starting position and size (including the starting position and length of time-domain resources and the starting position and bandwidth of frequency-domain resources) of corresponding time-frequency resources for different second devices, efficient utilization of these resources can be achieved. Furthermore, it facilitates information interaction between different second devices and the first device on their respective time-frequency resources, effectively reducing resource conflicts when multiple second devices interact with the first device, thereby significantly improving the identification efficiency of the second device in the RFID system. In addition, since the starting position and size of the time-frequency resources corresponding to different second devices can be flexibly allocated according to actual needs, the configuration of these resources for different second devices is highly flexible.

[0047] Based on the first or second aspect, in one possible implementation, the first information may further include the starting position of the time-domain resource set, the length of the time-domain resources, the interval between two adjacent time-domain resources in the time-domain resource set, the starting position of the frequency-domain resource set, the frequency-domain width of the frequency-domain resources, and the interval between two adjacent frequency-domain resources in the frequency-domain resource set, wherein the time-domain resource set may include multiple time-domain resources, and the frequency-domain resource set may include multiple frequency-domain resources.

[0048] In the above implementation, by configuring or allocating the starting position of the shared time-domain resource set, the length of the time-domain resources included in the time-domain resource set, the interval between two adjacent time-domain resources in the time-domain resource set, the starting position of the frequency-domain resource set, the frequency-domain width of the frequency-domain resources included in the frequency-domain resource set, and the interval between two adjacent frequency-domain resources in the frequency-domain resource set for different second devices, it is possible for different second devices to determine their respective time-frequency resources (including time-domain resources and frequency-domain resources) in a timely and accurate manner. Furthermore, it enables different second devices to interact with the first device on their respective time-frequency resources, which helps to effectively reduce resource conflicts when multiple second devices interact with the first device, thereby effectively improving the identification efficiency of the second device in the RFID system.

[0049] Based on the second aspect, in one possible implementation, the method further includes:

[0050] The second device can determine the third time slot based on the system frame number and time slot number. Then, the second device can determine the time domain resources corresponding to the second device in the third time slot based on the start position and length of the time domain resources corresponding to the second device. In addition, the second device can determine the frequency domain resources corresponding to the second device based on the start position and frequency domain width of the frequency domain resources corresponding to the second device.

[0051] The above implementation method enables the second device to determine the time-domain resources and frequency-domain resources corresponding to the second device in a timely and accurate manner based on the starting position and length of the time-domain resources and the starting position and frequency-domain width of the frequency-domain resources corresponding to the second device.

[0052] Based on the second aspect, in one possible implementation, the method further includes:

[0053] The second device can determine the fourth time slot based on the system frame number and time slot number. Then, the second device can determine multiple time-domain resources in the fourth time slot based on the starting position of the time-domain resource set, the length of the time-domain resources, and the interval between two adjacent time-domain resources in the time-domain resource set. Then, the second device can determine the time-domain resource corresponding to the second device from among the multiple time-domain resources based on the number of the time-domain resource corresponding to the second device. Similarly, the second device can determine multiple frequency-domain resources based on the starting position of the frequency-domain resource set, the frequency-domain width of the frequency-domain resources, and the interval between two adjacent frequency-domain resources in the frequency-domain resource set. Then, the second device can determine the frequency-domain resource corresponding to the second device from among the multiple frequency-domain resources based on the number of the frequency-domain resource corresponding to the second device.

[0054] The above implementation method enables the second device to determine the time-domain resources and frequency-domain resources corresponding to the second device in a timely and accurate manner based on the starting position of the time-domain resource set, the length of the time-domain resources, the interval between two adjacent time-domain resources in the time-domain resource set, the number of the time-domain resources corresponding to the second device, the starting position of the frequency-domain resource set, the frequency-domain width of the frequency-domain resources, the interval between two adjacent frequency-domain resources in the frequency-domain resource set, and the number of the frequency-domain resources corresponding to the second device.

[0055] Based on the first or second aspect, in one possible implementation, the information of the code domain resource corresponding to the second device may include the code domain resource number.

[0056] Based on the second aspect, in one possible implementation, the method further includes:

[0057] The second device can determine the code domain resource corresponding to the second device from the preset code domain resource set based on the code domain resource number corresponding to the second device.

[0058] The above implementation method enables the second device to determine the code domain resource corresponding to the second device in a timely and accurate manner based on the code domain resource number corresponding to the second device.

[0059] Based on the first or second aspect, in one possible implementation, the method further includes:

[0060] The second device sends second information to the first device on the resource corresponding to the second device. The second information may include a random number, which can be used for the authentication of the second device. After receiving the second information from the second device on the resource corresponding to the second device, the first device may send third information to the second device on the resource corresponding to the second device. Then, the second device may receive the third information from the first device on the resource corresponding to the second device. The third information may include a random number.

[0061] The above implementation method can effectively complete the handshake operation between the second device and the first device by utilizing the existing handshake mechanism.

[0062] Based on the first or second aspect, in one possible implementation, the method further includes:

[0063] The second device sends a fourth message to the first device on the resource corresponding to the second device. The fourth message may include indication information, which can be used for the authentication of the second device. After receiving the fourth message from the second device on the resource corresponding to the second device, the first device may send a fifth message to the second device on the resource corresponding to the second device. Then, the second device may receive the fifth message from the first device on the resource corresponding to the second device. The fifth message may include indication information.

[0064] Since the number of bits occupied by indication information (such as 1-bit indication information) is less than the number of bits occupied by random numbers (such as 16-bit random numbers), the above implementation method can reduce bit overhead, thereby reducing the energy consumption of the first and second devices. This can effectively reduce (or alleviate) the processing load (or processing burden, such as computing load) of the first device and reduce the information (or data) transmission delay between the first and second devices.

[0065] Based on the first or second aspect, in one possible implementation, the indication information can be 1-bit indication information.

[0066] Thirdly, this application provides a communication device including units or means for performing the various steps of any of the implementation methods in the first aspect described above.

[0067] For example, the communication device can be a first device or a module within the first device (such as a processor, processing unit, chip system, circuit, or chip). The communication device has the functionality to implement the method in any possible implementation of the first aspect described above. This functionality can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the aforementioned functionality.

[0068] Fourthly, this application provides a communication device including units or means for performing the various steps of any implementation method in the second aspect described above.

[0069] For example, the communication device can be a second device, or a module within the second device (such as a processor, processing unit, chip system, circuit, or chip). The communication device has the functionality to implement the method in any of the possible implementations of the second aspect described above. This functionality can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the aforementioned functionality.

[0070] Fifthly, this application provides a communication device that has the functions involved in the first to second aspects described above. For example, the communication device includes modules, units, or means that perform the operations involved in the first to second aspects described above. The functions, units, or means can be implemented by software, or by hardware, or by hardware executing corresponding software.

[0071] In one possible implementation, the communication device may include a transceiver unit (or communication module, used for sending and receiving data). Optionally, the communication device may further include a processing unit (or processing module). The transceiver unit can be used to send and receive signals to enable communication between the communication device and other devices; for example, the transceiver unit can be used to send data to other communication devices. The processing unit can be used to perform some internal operations of the communication device. The functions performed by the transceiver unit and the processing unit may correspond to the operations described in the first to second aspects above.

[0072] In one possible implementation, the communication device includes a processor that can be coupled to a memory. The memory can store necessary computer programs or instructions for implementing the functions described in the first to second aspects above. The processor can execute the computer programs or instructions stored in the memory, causing the communication device to implement the methods in any possible implementation of any of the first to second aspects above when the computer programs or instructions are executed.

[0073] In one possible implementation, the communication device includes a processor and a memory, the memory of which may store necessary computer programs or instructions for implementing the functions involved in the first to second aspects described above. The processor may execute the computer programs or instructions stored in the memory, and when the computer programs or instructions are executed, cause the communication device to implement the methods in any possible implementation of any of the first to second aspects described above.

[0074] In one possible implementation, the communication device includes a processor and a transceiver (or communication interface or interface circuitry), wherein the processor is used to communicate with other devices via the transceiver and to execute the methods in any of the possible implementations of the first to second aspects described above. The transceiver is used to enable the communication device to communicate with other devices, for example, to receive signals from other communication devices and transmit them to the processor, or to send signals from the processor of the communication device to other communication devices, such as the transmission or reception of data and / or signals. Exemplarily, the communication interface may be a transceiver, circuit, bus, module, or other type of communication interface.

[0075] It is understood that, in the fifth aspect mentioned above, the processor can be implemented in hardware or software. When implemented in hardware, the processor can be a logic circuit, integrated circuit, etc.; when implemented in software, the processor can be a general-purpose processor that reads software code stored in memory. Furthermore, there can be one or more processors, and one or more memories. The memory can be integrated with the processor, or the memory and processor can be separate. In specific implementations, the memory can be integrated with the processor on the same chip, or it can be set on different chips. This application does not limit the type of memory or the arrangement of the memory and processor.

[0076] Sixthly, this application provides a possible communication system, which may include the first device and the second device mentioned in the first or second aspect above. The functional implementation of the first or second device can be found in the relevant descriptions mentioned in the first or second aspect above, and will not be repeated here.

[0077] In a seventh aspect, this application provides a computer program product comprising a computer program or instructions that, when executed on a communication device (or computer), cause the communication device (or computer) to perform the method in any possible implementation of any of the first to second aspects described above.

[0078] Eighthly, this application provides a computer-readable storage medium storing a computer program or instructions that, when executed by a communication device (or computer), cause the communication device (or computer) to perform the method in any possible implementation of any of the first to second aspects described above.

[0079] Ninthly, this application provides a chip that may include a processor and may also include a memory (or the chip may be coupled to the memory), the chip executing program instructions in the memory to cause the chip to perform any possible implementation of any of the first to second aspects described above. Here, "coupling" refers to two components being directly or indirectly connected to each other, such as coupling referring to an electrical connection between two components.

[0080] Tenthly, this application also provides a chip system including a processor for supporting a computer device in implementing any possible implementation of the methods in any of the first to second aspects described above. In one possible implementation, the chip system further includes a memory for storing programs and data necessary for the computer device. The chip system may be composed of chips or may include chips and other discrete devices.

[0081] Based on the implementation methods provided in the above aspects, this application can be further combined to provide more implementation methods. Attached Figure Description

[0082] Figure 1 illustrates an exemplary architecture diagram of a possible communication system provided in an embodiment of this application;

[0083] Figure 2 illustrates an exemplary schematic diagram of a conventional label inventory process provided in an embodiment of this application.

[0084] Figure 3 illustrates a flowchart of a communication method provided in an embodiment of this application;

[0085] Figure 4a illustrates a schematic diagram of a time-domain resource provided in an embodiment of this application;

[0086] Figure 4b illustrates a schematic diagram of a time-domain resource set provided in an embodiment of this application;

[0087] Figure 4c illustrates a frequency domain resource diagram provided by an embodiment of this application;

[0088] Figure 4d illustrates a schematic diagram of a frequency domain resource set provided in an embodiment of this application;

[0089] Figure 5a illustrates a flowchart of another communication method provided in an embodiment of this application;

[0090] Figure 5b illustrates a flowchart of another communication method provided in an embodiment of this application;

[0091] Figure 6a illustrates a flowchart of another communication method provided in an embodiment of this application;

[0092] Figure 6b illustrates a flowchart of another communication method provided in an embodiment of this application;

[0093] Figure 6c illustrates a flowchart of another communication method provided in an embodiment of this application;

[0094] Figure 6d illustrates a flowchart of another communication method provided in an embodiment of this application;

[0095] Figure 6e illustrates a flowchart of another communication method provided in an embodiment of this application;

[0096] Figure 7 illustrates a schematic diagram of a possible communication device provided in an embodiment of this application;

[0097] Figure 8 illustrates a schematic diagram of another possible communication device provided in an embodiment of this application. Detailed Implementation

[0098] Before introducing the technical solutions provided in this application, some of the terms used in this application will be explained in order to facilitate understanding by those skilled in the art.

[0099] (1) Inventory Operation (also known as Stocktaking or Checking): The reader can obtain the identification information of one or more tags (also known as electronic tags) through an inventory operation. Optionally, the reader can also send the obtained identification information to other devices (such as computing devices or servers). For example, the reader can perform an inventory operation on all tags within its coverage area to obtain the identification information of all tags within the reader's coverage area. It is understood that an inventory operation for all tags within the coverage area is also called a full-tag inventory operation or an unrestricted inventory operation. Optionally, when the identification range in the above inventory operation is not limited, the inventory operation can be to obtain the identification information of tags within the reader's coverage area.

[0100] Understandably, each tag has corresponding identification information, and each tag can be identified based on its unique identification information. Optionally, the tag's identification information can be globally unique, temporary, or not globally unique. For example, the tag's identification information may include one or more of the following: the tag's user identifier, and a serial number. The serial number is used to indicate a unique tag. For example, the serial number can be an electronic product code (EPC) or a tag identifier (TID). Optionally, the serial number can also be a number assigned by the user or operator.

[0101] (2) Resources: The protocol does not directly use the term "beam" to characterize beams, but uses other methods to implicitly describe beam-related operations. For example, in beam measurement, there is a correspondence between beams and resources (network devices use a beam to transmit their corresponding resources), and the quality of the resource measured by the terminal device is equivalent to the quality of the beam. Resources in the embodiments of this application may include, for example, the resources of reference signals.

[0102] The resources in the embodiments of this application may include at least one of time-domain resources or frequency-domain resources.

[0103] Time-domain resources may include at least one of the following: radio frames, subframes, slots, mini slots, or orthogonal frequency division multiplexing (OFDM) symbols. A radio frame may include multiple subframes, a subframe may include one or more slots, and a slot may include at least one symbol. Alternatively, a radio frame may include multiple slots, and a slot may include at least one symbol. It should be noted that, in this embodiment, an OFDM symbol may also be simply referred to as a symbol.

[0104] Frequency domain resources (also known as frequency resources) may include at least one of the following: resource element (RE), resource block (RB), channel, subchannel, carrier, or bandwidth part (BWP). In the embodiments of this application, a channel may also be equivalently replaced by a resource block set (RB set), and the frequency domain bandwidth of an RB set may be 20 megahertz (MHz).

[0105] The embodiments of this application will now be described in detail with reference to the accompanying drawings.

[0106] The following describes the communication systems to which the communication method provided in this application is applicable. It should be noted that this description is for the convenience of those skilled in the art and does not constitute a limitation on the scope of protection claimed in this application.

[0107] The technical solutions of this application embodiment can be used in various communication systems, including 3GPP communication systems such as Long Term Evolution (LTE), 4th Generation (4G), 5th Generation (5G), LTE and 5G hybrid networking systems, integrated communication and sensing systems, non-terrestrial networks (NTN), device-to-device (D2D) communication systems, vehicle-to-everything (V2X) communication systems, machine-type communication (MTC) systems, Internet of Things (IoT) systems, or other future communication systems. The communication system can also be a non-3GPP communication system; there is no limitation.

[0108] This application supports the Spark Link / NearLink protocol, or it supports IEEE protocols such as IEEE 802.11be / WiFi 7 / EHT (extremely high throughput), IEEE 802.11bn / WiFi 8 / UHR (ultra high reliability), or IEEE 802.11bp AMP (ambient power).

[0109] The technical solutions of this application embodiment can also be applied to wireless short-range communication systems and wireless communication systems that support even shorter-range transmission (such as the future StarSpark wireless communication system). The wireless short-range communication system can include wireless short-range communication technologies (such as StarSpark 1.0 technology), which have advantages such as ultra-low latency, ultra-high reliability, and precise synchronization, making them suitable for applications in smart cars, smart homes, smart terminals, and smart manufacturing. For example, applications in smart car scenarios include: immersive in-vehicle sound field & noise reduction, wireless interactive screen projection, and 360-degree panoramic surround view, which can achieve an immersive interactive experience and improve vehicle safety.

[0110] Among them, wireless communication systems that support shorter distance transmission mainly include future StarSpark wireless communication systems, such as StarSpark 2.0 wireless communication system and StarSpark 3.0 wireless communication system. They are not only suitable for communication scenarios with low latency requirements, such as the above-mentioned vehicle communication and industrial control scenarios, but also suitable for communication scenarios with low latency requirements.

[0111] It is understood that the communication system described above is merely an example, and the communication system applicable to this application is not limited thereto. The communication system provided in this application does not impose any limitation on the solution of this application. This is explained uniformly here and will not be repeated below.

[0112] Figure 1 illustrates an exemplary architecture of a possible communication system applicable to embodiments of this application. As shown in Figure 1, the communication system may include a reader, a tag, and an antenna. The antenna is divided into reader antennas and tag antennas. Optionally, the communication system architecture may also include other devices (e.g., computing devices or servers).

[0113] A tag is a miniature wireless transceiver device, mainly consisting of a built-in tag antenna, a coupling element, and a chip. The chip contains storage space that allows a reader to read or write tag data. After receiving the radio frequency (RF) signal from the reader through the tag antenna, the tag can couple the RF signal through the coupling element. This coupling channel then provides power to the tag's chip and transmits the tag data stored in the chip back to the reader via the tag antenna.

[0114] It is understood that the tags involved in the embodiments of this application can be in the form of tags or any device. Alternatively, the second device involved in the embodiments of this application can be in the form of tags. For example, the second device in the embodiments of this application can be a tag.

[0115] For example, the second device or tag can be passive, semi-passive, semi-active, or active. The second device or tag may not have energy storage capability (e.g., it may not have a capacitor), or it may have energy storage capability (e.g., it may have a capacitor to store electrical energy).

[0116] A reader is a device capable of acquiring and processing data from tags. It can function as a standalone device or be embedded in other devices or systems. The reader can transmit radio frequency signals to the tag via its antenna to query or write data. Optionally, the reader can also connect to other devices (such as computing devices) via a communication interface to transfer data stored locally or retrieved from the tag to those devices.

[0117] For example, a reader can be an access network device, such as a base station, pole station, micro base station, macro station, integrated access and backhaul (IAB) node, mobile base station, etc. Alternatively, a reader can also be a terminal device, such as a mobile phone, Internet of Things (IoT) device, handheld reader, etc.

[0118] The following describes the process of information (or data) interaction between the reader and the tag in several ways. One method is that when the tag enters the reader's effective identification range, it receives the radio frequency signal emitted by the reader and uses the energy obtained from the induced current to emit the information stored in the chip (corresponding to passive tags). Another method is that the tag can store some electrical energy through solar energy or other means, enabling it to actively transmit a signal at a certain frequency (corresponding to active tags). The reader reads and decodes the information in the signal and sends it to a computing device for data processing.

[0119] It is understood that the communication system described in the embodiments of this application is for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and does not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of communication systems and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0120] The following describes an existing label inventory scheme. Figure 2 is a schematic diagram of an existing label inventory process provided in an embodiment of this application. As shown in Figure 2, the specific implementation process of the existing label inventory may include:

[0121] Step s1: The reader broadcasts a selection command.

[0122] The select command (also known as an inventory command or inventory message) can include the range of labels that need to be inventoried (such as EPCs or TIDs within a specific range).

[0123] When a tag detects a selection command, it determines whether it falls within the tag range included by that selection command. If it does, it will provide feedback upon detecting a subsequent query command or query response. If it does not fall within the range, it will not take any further action.

[0124] Alternatively, the reader broadcast selection instruction can be replaced with the description "reader sends selection instruction".

[0125] Step s2: The reader broadcasts a query command.

[0126] The query instruction (also known as a query command or query message) may include a slot parameter value (also known as a slot count parameter value), denoted as the Q value.

[0127] Upon receiving a query command, a tag can generate a random number based on the Q value included in the query command, for example, a random number between 0 and 2 to the power of Q. Then, the tag can decrement this random number by one after each query command or query response command sent by the reader. When the random number reaches zero, the tag will initiate random access.

[0128] Alternatively, the reader broadcast query instruction can be replaced with the description "reader sends query instruction".

[0129] Step s3: When a tag finds itself within the range of tags selected in the selection instruction, it will send a random number (RN)16 (which can be understood as a random number of 16 bits) back to the reader through a competition mechanism. For example, when the random number in step s2 decreases to zero, the tag will send an RN16 back to the reader through a competition mechanism.

[0130] Step s4: After the reader receives the RN16 from the tag, it sends an acknowledgment (ACK) instruction to the tag. This ACK instruction (also called ACK command, ACK message, ACK signaling, or ACK information) contains the random number (RN16) that was just received.

[0131] Step s5: When the tag receives the ACK instruction from the reader and verifies that the random number is correct, it will send the tag's EPC back to the reader, thus completing the inventory process.

[0132] The tag inventory scheme shown in Figure 2 is a TDMA-based scheme. While this scheme can automate inventory to some extent, it increases the collision probability when processing large numbers of tags. Each tag needs to send a random number RN16 and wait for reader confirmation, leading to numerous retries and waiting times, severely slowing down the inventory process and significantly reducing efficiency. Furthermore, the TDMA-based scheme clearly cannot meet the demands of efficient and rapid inventory processing for large numbers of tags. Additionally, the reader's confirmation after each tag response increases the reader's processing load and limits the overall system throughput, making it unsuitable for rapid inventory management of large numbers of tags.

[0133] In view of this, this application provides a communication method to effectively improve the efficiency of tag inventory.

[0134] The specific implementation of the communication method in the embodiments of this application will be described in detail below with reference to the accompanying drawings. It is understood that this application uses a first device and a second device as examples to illustrate the execution of the interaction, but this application does not limit the execution subject of the interaction. For example, the method executed by the first device in this application can also be executed by a module applied to the first device (e.g., a chip, chip system, or processor), or by a logical node, logical module, or software capable of implementing all or part of the functions of the first device; similarly, the method executed by the second device in this application can also be executed by a module applied to the second device (e.g., a chip, chip system, or processor), or by a logical node, logical module, or software capable of implementing all or part of the functions of the second device. For example, the first device can be a reader as shown in Figure 1, and the second device can be a tag as shown in Figure 1. Optionally, the solutions provided in the following embodiments can be applied to scenarios where the list of labels to be inventoried is known (which can be understood as a scenario where the identification information of the labels to be inventoried is known (or known in advance)), or can be applied to scenarios where the range of labels to be inventoried is known (which can be understood as a scenario where the range of identification information of the labels to be inventoried is known (e.g., the identification information range is 1-100)).

[0135] Figure 3 illustrates a flowchart of a communication method provided in an embodiment of this application. This method is applicable to the network architecture shown in Figure 1. As shown in Figure 3, the method includes:

[0136] Step 301: The first device sends the first information. Correspondingly, the second device receives the first information.

[0137] For example, the first information can be a query instruction (such as query instruction q1, query instruction q2, query instruction q3, query instruction q4 or query instruction q5 described below), or the first information can be contained in the query instruction.

[0138] The following examples illustrate the first piece of information.

[0139] Example A1: The first information includes a mapping relationship (also called a correspondence relationship or association relationship). This mapping relationship can describe (or include) the mapping relationship between the identification information of M second devices and the resources corresponding to those M second devices. That is, there exists (or has) a mapping relationship between the identification information of a second device and the resources corresponding to that second device. Optionally, this mapping relationship can also describe M mapping relationships, where one of the M mapping relationships describes the mapping relationship between the identification information of a second device and the resources corresponding to that second device. Here, M is an integer greater than or equal to 1.

[0140] For example, taking M as 3, and the three second devices as second device h1, second device h2, and second device h3. For instance, the mapping relationship included in the first information can describe the mapping relationship between the identification information of second device h1 and the resources corresponding to second device h1, the mapping relationship between the identification information of second device h2 and the resources corresponding to second device h2, and the mapping relationship between the identification information of second device h3 and the resources corresponding to second device h3.

[0141] For example, the first information may include three mapping relationships: mapping relationship 1, mapping relationship 2, and mapping relationship 3. Mapping relationship 1 describes the mapping between the identification information of the second device h1 and the resources corresponding to the second device h1. Mapping relationship 2 describes the mapping between the identification information of the second device h2 and the resources corresponding to the second device h2. Mapping relationship 3 describes the mapping between the identification information of the second device h3 and the resources corresponding to the second device h3.

[0142] For example, the identification information of the second device can refer to the device identifier, device model, device serial number, or other information that can identify the second device (such as TID or temporary identifier). The resources corresponding to the second device can include at least one of the following: time domain resources, frequency domain resources, and code domain resources.

[0143] In one possible implementation, the mapping relationship between the identification information of M second devices and the resources corresponding to the M second devices is described (or included) by the mapping relationship (also referred to as the first mapping relationship) included in the first information. The following possible examples will be used to introduce this mapping relationship.

[0144] Example a1: The first information includes a mapping relationship describing the mapping relationship between the identification information of M second devices and the information of the time-domain resources corresponding to the M second devices.

[0145] In one example, the information of a time-domain resource corresponding to a second device may include the start position and length of the time-domain resource. For example, the start position of the time-domain resource may refer to the start time (or start moment) of the time-domain resource, or it may refer to the start time slot of the time-domain resource, or it may refer to the start symbol of the time-domain resource, and so on.

[0146] For example, continuing with M=3, and the three second devices being second device h1, second device h2, and second device h3. Referring to Figure 4a, the starting position of time-domain resource k1 is t1, and its length is T1; the starting position of time-domain resource k2 is t2, and its length is T2; the starting position of time-domain resource k3 is t3, and its length is T3. For instance, assume that the time-domain resource corresponding to second device h1 is time-domain resource k1, the time-domain resource corresponding to second device h2 is time-domain resource k2, and the time-domain resource corresponding to second device h3 is time-domain resource k3. Thus, the information for time-domain resource k1 corresponding to second device h1 includes its starting position t1 and its length T1. The information for time-domain resource k2 corresponding to second device h2 includes its starting position t2 and its length T2. The information of the time-domain resource k3 corresponding to the second device h3 includes the starting position t3 and the length T3 of the time-domain resource k3.

[0147] In another example, the information of a time-domain resource corresponding to a second device may include the time-domain resource's number (or identifier). When the time-domain resource information includes the time-domain resource's number, the first information may also include the starting position of the time-domain resource set, the length of the time-domain resources, and the interval between two adjacent time-domain resources in the time-domain resource set. Optionally, the first information may also include system information required for synchronization between the first device and at least one second device, such as the system frame number and time slot number. The time-domain resource set may include multiple time-domain resources. It should be understood that the time-domain resource set is named based on its function (or role). In practical application scenarios, other names may be used instead, as long as the function reflected by the other name is the same as the function reflected by the time-domain resource set. This application embodiment does not impose any restrictions on this.

[0148] For example, the starting position of a time-domain resource set can refer to the starting time (or starting moment) of the time-domain resource set, or it can refer to the starting time slot of the time-domain resource set, or it can refer to the starting symbol of the time-domain resource set, and so on.

[0149] For example, continuing with M=3, and the three second devices being second device h1, second device h2, and second device h3, the first information may also include the starting position t1 of the time-domain resource set, the length T of the time-domain resources, and the interval Δt between two adjacent time-domain resources in the time-domain resource set, as shown in Figure 4b. The time-domain resource set includes three time-domain resources (e.g., time-domain resource k1', time-domain resource k2', and time-domain resource k3'), which are numbered k1', k2', and k3' in time-domain order, or k1', k2', and k3' in time-domain position order. For example, time-domain resource k1' is numbered k1', time-domain resource k2' is numbered k2', and time-domain resource k3' is numbered k3'. The interval between time-domain resources k1' and k2' is T, and the interval between time-domain resources k2' and k3' is T. In this embodiment, the time-domain resource corresponding to the second device h1 is numbered k1', the time-domain resource corresponding to the second device h2 is numbered k2', and the time-domain resource corresponding to the second device h3 is numbered k3'. It can be understood that the starting position of time-domain resource k1' is t1, and the length of time-domain resource k1' is T. The starting position of time-domain resource k2' is (t1+T+Δt), and the length of time-domain resource k2' is T. The starting position of time-domain resource k3' is (t1+T+Δt+T+Δt), and the length of time-domain resource k3' is T.

[0150] Example a2: The first information includes a mapping relationship describing the mapping relationship between the identification information of M second devices and the information of the frequency domain resources corresponding to the M second devices.

[0151] In one example, the information of the frequency domain resources corresponding to a second device may include the starting position and frequency domain length (also known as frequency width or frequency size) of the frequency domain resources. For example, the starting position of the frequency domain resources may refer to the starting frequency point or starting frequency of the frequency domain resources, or the starting subcarrier (i.e., from which subcarrier the frequency domain resources begin) or the number of the starting subcarrier, or the starting RE (i.e., from which RE the frequency domain resources begin), or the starting subband, or the starting frequency band (or starting frequency zone), and so on.

[0152] For example, continuing with M=3, and the three second devices being second device h1, second device h2, and second device h3. Referring to Figure 4c, the starting position of frequency domain resource K1 is f1, and its frequency domain width is F1; the starting position of frequency domain resource K2 is f2, and its frequency domain width is F2; ​​the starting position of frequency domain resource K3 is f3, and its frequency domain width is F3. For instance, assume that the frequency domain resource corresponding to second device h1 is frequency domain resource K1, the frequency domain resource corresponding to second device h2 is frequency domain resource K2, and the frequency domain resource corresponding to second device h3 is frequency domain resource K3. Thus, the information for frequency domain resource K1 corresponding to second device h1 includes its starting position f1 and frequency domain width F1. The information for frequency domain resource K2 corresponding to second device h2 includes its starting position f2 and frequency domain width F2. The information of the time-domain resource K3 corresponding to the second device h3 includes the starting position f3 and the frequency domain width F3 of the time-domain resource K3.

[0153] In another example, the information of the frequency domain resources corresponding to a second device may include the number of the frequency domain resources. When the information of the frequency domain resources includes the number of the frequency domain resources, the first information may also include the starting position of the frequency domain resource set, the frequency domain width of the frequency domain resources, and the interval between two adjacent frequency domain resources in the frequency domain resource set. Optionally, the first information may also include system information required for synchronization between the first device and at least one second device, such as the system frame number and time slot number. The frequency domain resource set may include multiple frequency domain resources. It should be understood that the frequency domain resource set is named based on function; in practical application scenarios, other names may be used instead, as long as the function reflected by the other name is the same as the function reflected by the frequency domain resource set. This application embodiment does not impose any restrictions on this.

[0154] For example, the starting position of a frequency domain resource set can refer to the starting frequency point or starting frequency of the frequency domain resource set, or the starting subcarrier (i.e., from which subcarrier the frequency domain resource set begins) or the number of the starting subcarrier, or the starting RE (i.e., from which RE the frequency domain resource set begins), or the starting subband, or the starting frequency band (or starting frequency zone) of the frequency domain resource set, and so on.

[0155] For example, continuing with M=3, and the three second devices being second device h1, second device h2, and second device h3, the first information may also include the starting position f1 of the frequency domain resource set, the frequency domain width F of the frequency domain resources, and the interval Δf between two adjacent frequency domain resources in the frequency domain resource set, as shown in Figure 4d. The frequency domain resource set includes three frequency domain resources (e.g., frequency domain resource K1', frequency domain resource K2', and frequency domain resource K3'), which are numbered sequentially in the frequency domain according to frequency order as K1', K2', and K3', or sequentially according to frequency domain position order as K1', K2', and K3'. For example, frequency domain resource K1' is numbered K1', frequency domain resource K2' is numbered K2', and frequency domain resource K3' is numbered K3'. The interval between frequency domain resource K1' and time domain resource K2' is F, and the interval between frequency domain resource K2' and frequency domain resource K3' is Δf. In this embodiment, the frequency domain resource corresponding to the second device h1 is numbered K1', the frequency domain resource corresponding to the second device h2 is numbered K2', and the frequency domain resource corresponding to the second device h3 is numbered K3'. It can be understood that the starting position of frequency domain resource K1' is f1, and the frequency domain width of frequency domain resource K1' is F. The starting position of frequency domain resource K2' is (f1+F+Δf), and the frequency domain width of frequency domain resource K2' is F. The starting position of frequency domain resource K3' is (f1+F+Δf+F+Δf), and the frequency domain width of frequency domain resource K3' is F.

[0156] Example a3: The first information includes a mapping relationship describing the mapping relationship between the identification information of M second devices and the time-frequency resource information corresponding to the M second devices.

[0157] In one example, the information of the time-frequency resources corresponding to a second device may include the start position and length of the time-domain resources, and the start position and frequency-domain width of the frequency-domain resources.

[0158] The description of the starting position of the time-domain resources in Example a3 can be found in the description of the starting position of the time-domain resources in Example a1 above, and the description of the starting position of the frequency-domain resources in Example a3 can be found in the description of the starting position of the frequency-domain resources in Example a2 above. They will not be repeated here.

[0159] For example, continuing with M=3, and the three second devices being second device h1, second device h2, and second device h3. The time-frequency resources corresponding to second device h1 can include time-domain resource k1 and frequency-domain resource K1, or the time-frequency resources corresponding to second device h1 can include time-domain resource k1 and frequency-domain resource K1', or the time-frequency resources corresponding to second device h1 can include time-domain resource k1' and frequency-domain resource K1, or the time-frequency resources corresponding to second device h1 can include time-domain resource k1' and frequency-domain resource K1'. Similarly, the time-frequency resources corresponding to second device h2 can include time-domain resource k2 and frequency-domain resource K2, or the time-frequency resources corresponding to second device h2 can include time-domain resource k2' and frequency-domain resource K2, or the time-frequency resources corresponding to second device h2 can include time-domain resource k2' and frequency-domain resource K2'. The time-frequency resources corresponding to the second device h3 may include time-domain resource k3 and frequency-domain resource K3, or the time-frequency resources corresponding to the second device h3 may include time-domain resource k3 and frequency-domain resource K3', or the time-frequency resources corresponding to the second device h3 may include time-domain resource k3' and frequency-domain resource K3, or the time-frequency resources corresponding to the second device h3 may include time-domain resource k3' and frequency-domain resource K3'.

[0160] For example, taking the time-frequency resources corresponding to the second device h1 as including time-domain resource k1 and frequency-domain resource K1, the time-frequency resources corresponding to the second device h2 as including time-domain resource k2 and frequency-domain resource K2, and the time-frequency resources corresponding to the second device h3 as including time-domain resource k3 and frequency-domain resource K3 as examples. Referring to Figures 4a and 4c above, the information of the time-frequency resources corresponding to the second device h1 includes the starting position t1 and length T1 of the time-domain resource k1, and the starting position f1 and frequency-domain width F1 of the frequency-domain resource K1. The information of the time-frequency resources corresponding to the second device h2 includes the starting position t2 and length T2 of the time-domain resource k2, and the starting position f2 and frequency-domain width F2 of the frequency-domain resource K2. The information of the time-frequency resources corresponding to the second device h3 includes the starting position t3 and length T3 of the time-domain resource k3, and the starting position f3 and frequency-domain width F3 of the frequency-domain resource K3.

[0161] In another example, the information of the time-frequency resources corresponding to a second device may include the number of the time-domain resources and the number of the frequency-domain resources. When the information of the time-frequency resources includes the number of the time-domain resources and the number of the frequency-domain resources, the first information may further include the starting position of the time-domain resource set, the length of the time-domain resources, the interval between two adjacent time-domain resources in the time-domain resource set, the starting position of the frequency-domain resource set, the frequency-domain width of the frequency-domain resources, and the interval between two adjacent frequency-domain resources in the frequency-domain resource set. Optionally, the first information may further include system information required for the first device to synchronize with at least one second device, such as the system frame number and time slot number. The time-domain resource set may include multiple time-domain resources, and the frequency-domain resource set may include multiple frequency-domain resources.

[0162] The description of the starting position of the time-domain resource set in Example a3 can be found in the description of the starting position of the time-domain resource set in Example a1 above. The description of the starting position of the frequency-domain resource set in Example a3 can be found in the description of the starting position of the frequency-domain resource set in Example a2 above. They will not be repeated here.

[0163] For example, the time-frequency resources corresponding to the second device h1 include time-domain resource k1' and frequency-domain resource K1', the time-frequency resources corresponding to the second device h2 include time-domain resource k2' and frequency-domain resource K2', and the time-frequency resources corresponding to the second device h3 include time-domain resource k3' and frequency-domain resource K3'. The first information may also include the starting position t1 of the time-domain resource set, the length T of the time-domain resources, the interval Δt between two adjacent time-domain resources in the time-domain resource set, the starting position f1 of the frequency-domain resource set, the frequency-domain width F of the frequency-domain resources, and the interval Δf between two adjacent frequency-domain resources in the frequency-domain resource set, as detailed in Figures 4b and 4d above. The time-domain resource set includes three time-domain resources, such as time-domain resource k1', time-domain resource k2', and time-domain resource k3'. The time-domain resource k1' is numbered k1', the time-domain resource k2' is numbered k2', and the time-domain resource k3' is numbered k3'. The frequency domain resource set includes three frequency domain resources, such as frequency domain resource K1', frequency domain resource K2', and frequency domain resource K3'. The frequency domain resource corresponding to the second device h1 is numbered K1', the frequency domain resource corresponding to the second device h2 is numbered K2', and the frequency domain resource corresponding to the second device h3 is numbered K3'. In this embodiment, the time domain resource corresponding to the second device h1 is numbered k1', and the frequency domain resource corresponding to the second device h1 is numbered K1'. The time domain resource corresponding to the second device h2 is numbered k2', and the frequency domain resource corresponding to the second device h2 is numbered K2'. The time domain resource corresponding to the second device h3 is numbered k3', and the frequency domain resource corresponding to the second device h3 is numbered K3'.

[0164] Example a4: The first information includes a mapping relationship describing the mapping relationship between the identification information of M second devices and the information of the code field resources corresponding to the M second devices.

[0165] For example, information about code domain resources can include the code domain resource's number. For example, a code domain resource can refer to a codeword.

[0166] For example, continuing with M=3, and the three second devices being second device h1, second device h2, and second device h3, the preset (or pre-configured or pre-defined) code domain resource set can include multiple code domain resources, such as four code domain resources (e.g., code domain resource i1, code domain resource i2, code domain resource i3, and code domain resource i4). Code domain resource i1 is numbered i1, code domain resource i2 is numbered i2, code domain resource i3 is numbered i3, and code domain resource i4 is numbered i4. For instance, the code domain resource corresponding to second device h1 is code domain resource i1, the code domain resource corresponding to second device h2 is code domain resource i2, and the code domain resource corresponding to second device h3 is code domain resource i3.

[0167] It is understood that examples a1 to a4 above can be implemented individually, or example a4 can be implemented in combination with example a1, example a2 or example a3.

[0168] In another possible implementation, taking the first information including the mapping relationship (also called the second mapping relationship) as an example, which includes M mapping relationships, the following possible examples will introduce one of the M mapping relationships.

[0169] Example a1': One of the M mapping relationships describes the mapping relationship between the identification information of a second device and the information of the time-domain resources corresponding to that second device.

[0170] The description of time-domain resources in example a1' can be found in the description of time-domain resources in example a1 above, and will not be repeated here.

[0171] Example a2': One of the M mapping relationships describes the mapping relationship between the identification information of a second device and the information of the frequency domain resources corresponding to that second device.

[0172] The description of frequency domain resources in Example a2' can be found in the above-mentioned introduction of frequency domain resources in Example a2, and will not be repeated here.

[0173] Example a3': One of the M mapping relationships describes the mapping relationship between the identification information of a second device and the information of the time and frequency resources corresponding to that second device.

[0174] The description of time-frequency resources in Example a3' can be found in the introduction of time-frequency resources in Example a3 above, and will not be repeated here.

[0175] Example a4': One of the M mapping relationships describes the mapping relationship between the identification information of a second device and the information of the code field resource corresponding to that second device.

[0176] The description of code field resources in Example a4' can be found in the introduction of code field resources in Example a4 above, and will not be repeated here.

[0177] It is understood that the above examples a1' to a4' can be implemented individually, or the above example a4' can be implemented in combination with examples a1', a2' or a3' respectively.

[0178] Example A2: The first information may include at least one mapping relationship. This at least one mapping relationship can describe the mapping relationship between the identification information of at least one second device and the resources corresponding to that at least one second device. That is, one of the at least one mapping relationships describes the mapping relationship between a second device and the resources corresponding to that second device.

[0179] For example, consider a first set of information comprising three mapping relationships (e.g., mapping relationship A, mapping relationship B, and mapping relationship C), and three second devices (e.g., second device h1, second device h2, and second device h3). Mapping relationship A describes the mapping between the identification information of second device h1 and the corresponding resources. Mapping relationship B describes the mapping between the identification information of second device h2 and the corresponding resources. Mapping relationship C describes the mapping between the identification information of second device h3 and the corresponding resources.

[0180] Understandably, the descriptions of the mapping relationships in Example A2 can be found in the descriptions of Examples a1' to a4' in Example A1 above, and will not be repeated here.

[0181] Step 302: When the second device is connected to the first device, it sends its attribute information to the resources corresponding to the second device. Correspondingly, the first device receives the attribute information of the second device on the resources corresponding to the second device.

[0182] For example, the attribute information of the second device may include its EPC or TID. Optionally, the attribute information of the second device may also include the manufacturer information of the second device, the location information of the second device (such as coordinates or latitude and longitude), or the capability information of the second device (such as support for inventory operations, read operations, or write operations).

[0183] The following example, using the mapping relationship described in the first information of Example A1 above to depict the mapping relationship between the identification information of M second devices and the resources corresponding to the M second devices, illustrates the implementation process of a certain second device among the M second devices sending its attribute information on the resource corresponding to that second device through several possible implementation methods. It is understood that, using the mapping relationship described in at least one of the first information in Example A2 above to depict the mapping relationship between the identification information of at least one second device and the resource corresponding to that at least one second device as an example, the implementation process of a second device sending its attribute information on the resource corresponding to the second device can refer to the relevant descriptions of methods B1 to B4 below, which will not be repeated here.

[0184] Method B1: When the mapping relationship included in the first information describes the mapping relationship between the identification information of M second devices and the information of the time-domain resources corresponding to the M second devices, after receiving the first information, the second device can determine the information of the time-domain resources corresponding to the second device based on the identification information of the second device and the mapping relationship included in the first information. Then, the second device can determine the time-domain resources corresponding to the second device based on the information of the time-domain resources corresponding to the second device. Finally, the second device can send its attribute information on the first resource. The first resource includes the time-domain resources corresponding to the second device.

[0185] Optionally, the first resource may also include frequency domain resources. These frequency domain resources are allocated for information interaction between the first device and at least one second device. That is, when at least one second device needs to interact with the first device, it shares (or uses) these frequency domain resources.

[0186] Optionally, the first resource may also include a code domain resource. This code domain resource is an allocated resource required for information interaction between the first device and at least one second device. In one example, at least one second device may share a single code domain resource. For example, this code domain resource may be predefined (or pre-configured) or carried within the first information. In another example, at least one second device may be assigned a separate code domain resource. That is, each second device can use its own dedicated code domain resource to interact with the first device. For example, the code domain resource corresponding to at least one second device may be predefined or carried within the first information.

[0187] For example, if the first information also includes the system frame number and timeslot number required for synchronization between the first device and the second device, and if the information of the time-domain resource corresponding to the second device includes the start position and length of the time-domain resource corresponding to the second device, then the second device can determine the first timeslot based on the system frame number and timeslot number. Subsequently, the second device can determine the time-domain resource corresponding to the second device within the first timeslot based on the start position and length of the time-domain resource corresponding to the second device.

[0188] For example, taking the temporal resource diagram shown in Figure 4a above, let's consider a second device, h1, and the temporal resource corresponding to h1, k1. The information of the temporal resource corresponding to h1 includes the starting position t1 and the length T1 of k1. h1 can determine the first time slot based on the system frame number and time slot number included in the first information. Then, h1 can determine the corresponding temporal resource k1 within the first time slot based on the starting position t1 and the length T1 of k1.

[0189] For example, if the first information also includes the starting position of the time-domain resource set, the length of the time-domain resources (which can be understood as the length of each time-domain resource included in the time-domain resource set), the interval between two adjacent time-domain resources in the time-domain resource set, and the system frame number and time slot number required for synchronization between the first device and the second device, then if the information of the time-domain resources corresponding to the second device includes the number of the time-domain resources corresponding to the second device, the second device can determine the second time slot based on the system frame number and time slot number. Then, the second device can determine multiple time-domain resources in the second time slot based on the starting position of the time-domain resource set, the length of the time-domain resources, and the interval between two adjacent time-domain resources in the time-domain resource set. Finally, the second device can determine the time-domain resource corresponding to the second device from among the multiple time-domain resources based on the number of the time-domain resources corresponding to the second device. It is understood that the multiple time-domain resources included in the time-domain resource set can each have their own number. Optionally, the numbering of the multiple time-domain resources included in the time-domain resource set can be determined according to the time order or time-domain position order of the multiple time-domain resources, or the numbering order of the multiple time-domain resources can be defined by a protocol, or the numbering order of the multiple time-domain resources can be defined according to other rules.

[0190] For example, taking the time-domain resource set diagram shown in Figure 4b above, a second device is designated as second device h1, and the time-domain resource corresponding to second device h1 is designated as k1'. The first information includes the starting position t1 of the time-domain resource set, the length T of the time-domain resource, the interval Δt between two adjacent time-domain resources in the time-domain resource set, and the system frame number and time slot number required for synchronization between the first device and at least one second device. Second device h1 can first determine the second time slot based on the system frame number and time slot number included in the first information. Optionally, the second time slot can be the same as the first time slot. Then, second device h1 can determine three time-domain resources in the second time slot based on the starting position t1 of the time-domain resource set, the length T of the time-domain resource, and the interval Δt between two adjacent time-domain resources in the time-domain resource set, such as time-domain resource k1', time-domain resource k2', and time-domain resource k3'. Among them, time-domain resource k1' is numbered k1', time-domain resource k2' is numbered k2', and time-domain resource k3' is numbered k3'. Then, the second device h1 can determine the time-domain resource k1' from the three time-domain resources based on the time-domain resource number k1' corresponding to the second device h1.

[0191] Method B2: When the mapping relationship included in the first information describes the mapping relationship between the identification information of M second devices and the information of the frequency domain resources corresponding to the M second devices, after receiving the first information, the second device can determine the information of the frequency domain resources corresponding to the second device based on the identification information of the second device and the mapping relationship included in the first information. Then, the second device can determine the frequency domain resources corresponding to the second device based on the information of the frequency domain resources corresponding to the second device. Finally, the second device can send its attribute information on the second resources. The second resources include the frequency domain resources corresponding to the second device.

[0192] Optionally, the second resource may also include a time-domain resource. This time-domain resource is an allocated resource required for information interaction between the first device and at least one second device. That is, when at least one second device needs to interact with the first device, it shares this time-domain resource.

[0193] Optionally, the second resource may also include a code domain resource. This code domain resource is an allocated resource required for information interaction between the first device and at least one second device. In one example, at least one second device may share a single code domain resource. For example, this code domain resource may be predefined (or pre-configured) or carried within the first information. In another example, at least one second device may be assigned a separate code domain resource. That is, each second device can use its own dedicated code domain resource to interact with the first device. For example, the code domain resources corresponding to each of the at least one second device may be predefined or carried within the first information.

[0194] For example, if the information of the frequency domain resources corresponding to the second device includes the starting position and frequency domain width of the frequency domain resources corresponding to the second device, then the second device can determine the frequency domain resources corresponding to the second device based on the starting position and frequency domain width of the frequency domain resources corresponding to the second device.

[0195] For example, taking the frequency domain resource diagram shown in Figure 4c above, let's consider a second device, h1, and the corresponding frequency domain resource, K1. The information of the frequency domain resource corresponding to the second device h1 includes the starting position f1 and the frequency domain width F1 of the frequency domain resource K1. The second device h1 can determine the corresponding frequency domain resource K1 based on the starting position f1 and the frequency domain width F1.

[0196] For example, if the first information also includes the starting position of the frequency domain resource set, the frequency domain width of the frequency domain resources (which can be understood as the frequency domain width of each frequency domain resource included in the frequency domain resource set), and the interval between two adjacent frequency domain resources in the frequency domain resource set, then if the information of the frequency domain resources corresponding to the second device includes the number of the frequency domain resources corresponding to the second device, the second device can determine multiple frequency domain resources based on the starting position of the frequency domain resource set, the frequency domain width of the frequency domain resources, and the interval between two adjacent frequency domain resources in the frequency domain resource set. Then, the second device can determine the frequency domain resource corresponding to the second device from among the multiple frequency domain resources based on the number of the frequency domain resources corresponding to the second device. It is understood that the multiple frequency domain resources included in the frequency domain resource set can each have their own number. Optionally, the numbers of the multiple frequency domain resources included in the frequency domain resource set can be determined according to the frequency order or frequency position order of the multiple frequency domain resources, or the numbering order of the multiple frequency domain resources can be defined by a protocol, or the numbering order of the multiple frequency domain resources can be defined according to other rules.

[0197] For example, taking the frequency domain resource set diagram shown in Figure 4d above, a second device is designated as device h1, and the time domain resource corresponding to device h1 is designated as K1'. The first information also includes the starting position f1 of the frequency domain resource set, the frequency domain width F of the frequency domain resource, and the interval Δf between two adjacent frequency domain resources in the set. Device h1 can first determine three frequency domain resources, such as frequency domain resource K1', frequency domain resource K2', and frequency domain resource K3', based on the starting position f1, the frequency domain width F, and the interval Δf. Here, frequency domain resource K1' is designated as K1', frequency domain resource K2' as K2', and frequency domain resource K3' as K3'. Then, device h1 can determine frequency domain resource K1' from these three frequency domain resources based on the frequency domain resource number K1' corresponding to device h1.

[0198] Method B3: When the mapping relationship described in the first information corresponds to the identification information of M second devices and the time-frequency resources corresponding to the M second devices, after receiving the first information, the second device can determine the time-frequency resource information corresponding to the second device based on its identification information and the mapping relationship included in the first information. Then, the second device can determine the time-frequency resources (time domain resources and frequency domain resources) corresponding to the second device based on the information of the time-frequency resources corresponding to the second device. Finally, the second device can send its attribute information on the third resource. The third resource includes the time domain resources and frequency domain resources corresponding to the second device.

[0199] Optionally, the third resource may also include a code domain resource. This code domain resource is an allocated resource required for information interaction between the first device and at least one second device. In one example, at least one second device may share a single code domain resource. For example, this code domain resource may be predefined (or pre-configured) or carried within the first information. In another example, at least one second device may be assigned a separate code domain resource. That is, each second device can use its own dedicated code domain resource to interact with the first device. For example, the code domain resource corresponding to at least one second device may be predefined or carried within the first information.

[0200] For example, if the first information also includes the system frame number and timeslot number required for synchronization between the first and second devices, and if the information of the time-frequency resources corresponding to the second device includes the start position and length of the time-domain resources and the start position and width of the frequency-domain resources corresponding to the second device, then the second device can determine the third timeslot based on the system frame number and timeslot number. Subsequently, the second device can determine its corresponding time-domain resources in the third timeslot based on the start position and length of its corresponding time-domain resources. Furthermore, the second device also determines its corresponding frequency-domain resources based on the start position and width of its corresponding frequency-domain resources. Here, the time-domain resources and frequency-domain resources corresponding to the second device constitute the time-frequency resources corresponding to the second device.

[0201] For example, taking the time-domain resource diagram shown in Figure 4a and the frequency-domain resource diagram shown in Figure 4c above, let's consider a second device as device h1, and the time-domain resource corresponding to device h1 as time-domain resource k1. The information of the time-frequency resource corresponding to device h1 includes the starting position t1 and length T1 of time-domain resource k1, and the starting position f1 and frequency width F1 of frequency-domain resource k1. Device h1 can determine a third time slot based on the system frame number and time slot number included in the first information. Optionally, the third time slot can be the same as the first time slot. Then, device h1 can determine the time-domain resource k1 corresponding to device h1 in the third time slot based on the starting position t1 and length T1 of time-domain resource k1. Furthermore, device h1 can also determine the frequency-domain resource k1 corresponding to device h1 based on the starting position f1 and frequency width F1 of frequency-domain resource k1. The time-domain resource k1 and frequency-domain resource k1 corresponding to device h1 are considered as the time-frequency resource corresponding to device h1.

[0202] For example, if the first information also includes the starting position of the time-domain resource set, the length of the time-domain resources, the interval between two adjacent time-domain resources in the time-domain resource set, the starting position of the frequency-domain resource set, the frequency-domain width of the frequency-domain resources, the interval between two adjacent frequency-domain resources in the frequency-domain resource set, and the system frame number and time slot number required for synchronization between the first and second devices, then if the information of the time-frequency resources corresponding to the second device includes the number of the time-domain resources and the number of the frequency-domain resources corresponding to the second device, the second device can determine the fourth time slot based on the system frame number and the time slot number. Then, the second device can determine multiple time-domain resources in the fourth time slot based on the starting position of the time-domain resource set, the length of the time-domain resources, and the interval between two adjacent time-domain resources in the time-domain resource set. Then, the second device can determine the time-domain resource corresponding to the second device from among the multiple time-domain resources based on the number of the time-domain resources corresponding to the second device. Furthermore, the second device also determines multiple frequency-domain resources based on the starting position of the frequency-domain resource set, the frequency-domain width of the frequency-domain resources, and the interval between two adjacent frequency-domain resources in the frequency-domain resource set. Subsequently, the second device can determine its corresponding frequency domain resource from among multiple frequency domain resources based on the resource number corresponding to the second device. The time domain resource and frequency domain resource corresponding to the second device are then considered as the time-frequency resource corresponding to the second device.

[0203] For example, taking the time-domain resource set diagram shown in Figure 4b and the frequency-domain resource set diagram shown in Figure 4d as an example, let's say a second device is a second device h1, the time-domain resource corresponding to second device h1 is numbered k1', and the frequency-domain resource corresponding to second device h1 is numbered K1'. The first information also includes the starting position t1 of the time-domain resource set, the length T of the time-domain resource, the interval Δt between two adjacent time-domain resources in the time-domain resource set, the starting position f1 of the frequency-domain resource set, the frequency-domain width F of the frequency-domain resource, the interval Δf between two adjacent frequency-domain resources in the frequency-domain resource set, and the system frame number and time slot number required for synchronization between the first device and at least one second device. The second device h1 can first determine the fourth time slot based on the system frame number and time slot number included in the first information. Optionally, the fourth time slot can be the same as the second time slot. Subsequently, the second device h1 can determine three time-domain resources in the second time slot based on the starting position t1 of the time-domain resource set, the length T of the time-domain resources, and the interval Δt between two adjacent time-domain resources in the time-domain resource set. These resources may be time-domain resources k1', k2', and k3'. The time-domain resource k1' is numbered k1', k2' is numbered k2', and k3' is numbered k3'. Then, the second device h1 can determine the time-domain resource k1' from these three resources based on the time-domain resource number k1' corresponding to the second device h1. Furthermore, the second device h1 can also determine three frequency-domain resources, such as frequency-domain resources K1', K2', and K3', based on the starting position f1 of the frequency-domain resource set, the frequency-domain width F of the frequency-domain resources, and the interval Δf between two adjacent frequency-domain resources in the frequency-domain resource set. Among them, frequency domain resource K1' is numbered K1', frequency domain resource K2' is numbered K2', and frequency domain resource K3' is numbered K3'. Then, the second device h1 can determine the frequency domain resource K1' from these three frequency domain resources based on the number K1' of the frequency domain resource corresponding to the second device h1. The time domain resource k1' and frequency domain resource K1' corresponding to the second device h1 are considered as the time-frequency resources corresponding to the second device h1.

[0204] Method B4: When the mapping relationship included in the first information describes the mapping relationship between the identification information of M second devices and the information of the corresponding code domain resources of the M second devices, after receiving the first information, the second device can determine the information of the code domain resource corresponding to the second device based on the identification information of the second device and the mapping relationship included in the first information. Then, the second device can determine the code domain resource corresponding to the second device based on the information of the code domain resource corresponding to the second device. Finally, the second device can send the attribute information of the second device on the fourth resource. The fourth resource includes the code domain resource corresponding to the second device.

[0205] Optionally, the fourth resource may also include a time-frequency resource. This time-frequency resource is an allocated resource required for information interaction between the first device and at least one second device. In one example, at least one second device may share a single time-frequency resource. For example, this time-frequency resource may be predefined (or pre-configured) or carried within the first information. In another example, at least one second device may be individually allocated a corresponding time-frequency resource. That is, each second device can use its own dedicated time-frequency resource to interact with the first device. For example, the time-frequency resources corresponding to each of the at least one second device may be predefined or carried within the first information.

[0206] For example, if the information of the code domain resource corresponding to the second device includes the number of the code domain resource corresponding to the second device, then the second device can determine the code domain resource corresponding to the second device from a preset code domain resource set based on the number of the code domain resource corresponding to the second device. The preset code domain resource set includes multiple code domain resources. These multiple code domain resources can each have their own number. Optionally, the preset code domain resource set can be pre-configured, pre-defined by a protocol, or carried in the first information. Optionally, the multiple code domain resources included in the preset code domain resource set are not the same.

[0207] For example, consider a preset set of code domain resources including four code domain resources (e.g., code domain resource i1, code domain resource i2, code domain resource i3, and code domain resource i4), and a second device named second device h1, with the code domain resource corresponding to second device h1 numbered i1. Here, code domain resource i1 is numbered i1, code domain resource i2 is numbered i2, code domain resource i3 is numbered i3, and code domain resource i4 is numbered i4. Second device h1 can determine its corresponding code domain resource i1 from the four code domain resources based on the code domain resource number i1.

[0208] It is understood that methods B1 to B4 can be implemented individually, or method B4 can be implemented in combination with method B1, method B2 or method B3.

[0209] Optionally, after receiving the attribute information of the second device on the resource corresponding to the second device, the first device may also send back response information (such as information n1, n2, n3, n4, or n5 described below) on the resource corresponding to the second device. In one example, if the first device fails to receive the attribute information of the second device, the response information can be used to indicate that the attribute information reception of the second device has failed. For example, the response information can be a negative acknowledgement (NAK) message. In another example, if the first device successfully receives the attribute information of the second device, the response information can be used to indicate that the attribute information reception of the second device has been successful. For example, the response information can be other information (or other signaling) besides NAK information (also called NAK command, NAK signaling, or NAK message).

[0210] For example, if the second device receives NAK information, it can determine that the first device failed to receive the attribute information of the second device, and the second device can return to the arbitration state. If the second device receives information other than NAK information, it can determine that the first device successfully received the attribute information of the second device, and the second device can enter the confirmation state.

[0211] In this embodiment, before the second device sends its attribute information on the resources corresponding to the second device, the second device needs to access the first device. That is, the second device needs to complete a handshake operation with the first device. The following describes several possible implementation methods for the second device to access the first device.

[0212] Method C1: The second device interacts with the first device to generate random numbers to complete the connection between the second device and the first device. For details, please refer to Figure 5a.

[0213] The above method C1 can effectively complete the handshake operation between the second device and the first device by utilizing the existing handshake mechanism (or verification mechanism).

[0214] As shown in Figure 5a, the implementation process may include:

[0215] Step 501a: The second device sends second information to the first device on the resource corresponding to the second device. Correspondingly, the first device receives the second information from the second device on the resource corresponding to the second device.

[0216] The second piece of information (such as information u1, information u2, information u3, information u4, or information u5 described below) includes a random number. This random number can be used for authentication of the second device, or for handshake authentication or access authentication between the second device and the first device.

[0217] For example, the random number mentioned above could be an RN16 or other form of random number.

[0218] Step 502a: The first device sends third information to the second device on the resource corresponding to the second device. Correspondingly, the second device receives the third information from the first device on the resource corresponding to the second device.

[0219] The third piece of information (such as response information r1, r2, r3, r4, or r5 described below) includes a random number. For example, the third piece of information can be an ACK message.

[0220] For example, the random number mentioned above could be an RN16 or other form of random number.

[0221] After receiving the third information, the second device can obtain a random number from the third information and verify it. If the random number in the third information is the same as the random number in the second information, the second device connects to the first device. That is, the handshake between the second and first devices is successful. If the random number in the third information is different from the random number in the second information, the second device does not connect to the first device. That is, the handshake between the second and first devices fails.

[0222] Optionally, the first device may also carry other information or data in the third information. In this way, when the second device receives the third information, it will fail to verify the other information or data included in the third information.

[0223] Method C2: The second device interacts with the first device to exchange instruction information to complete the access of the second device to the first device. For details, please refer to Figure 5b.

[0224] Since the number of bits occupied by the indication information in method C2 is less than the number of bits occupied by the random number in method C1, the bit overhead can be reduced, thereby reducing the energy consumption of the first device and the second device. This can effectively reduce the processing load of the first device and reduce the information transmission delay between the first device and the second device.

[0225] As shown in Figure 5b, the implementation process may include:

[0226] Step 501b: The second device sends fourth information to the first device on the resource corresponding to the second device. Correspondingly, the first device receives the fourth information from the second device on the resource corresponding to the second device.

[0227] The fourth information (such as information u1, information u2, information u3, information u4, or information u5 described below) may include indication information. Optionally, in some embodiments, the fourth information may be indication information. The indication information may be used for authentication of the second device, or for handshake verification or access verification between the second device and the first device.

[0228] For example, the above indication information can be 1-bit indication information or other forms of indication information.

[0229] Step 502b: The first device sends the fifth information to the second device on the resource corresponding to the second device. Accordingly, the second device receives the fifth information from the first device on the resource corresponding to the second device.

[0230] The fifth piece of information (such as response information r1, r2, r3, r4, or r5 described below) includes indication information. For example, the fifth piece of information can be an ACK message.

[0231] For example, the above indication information can be 1-bit indication information or other forms of indication information.

[0232] After receiving the fifth message, the second device can obtain indication information from it and verify it. If the indication information in the fifth message is the same as that in the fourth message, the second device connects to the first device. That is, the handshake between the second and first devices is successful. If the indication information in the fifth message is different from that in the fourth message, the second device does not connect to the first device. That is, the handshake between the second and first devices fails.

[0233] Optionally, the first device may also carry other information or data in the fifth message. In this case, when the second device receives the fifth message and attempts to verify the other information or data included in it, the verification will fail.

[0234] As can be seen from steps 301 to 302 above, by carrying the mapping relationship between the identification information of the second device and the corresponding resources of the second device in the first information, the first device can facilitate the second device receiving the first information to promptly and accurately determine the resources corresponding to the second device (which can be understood as the dedicated resources of the second device) based on the mapping relationship. Furthermore, this allows the second device to interact with the first device based on the resources corresponding to the second device. This effectively reduces the probability of resource collisions when multiple second devices interact with the first device separately, helping to reduce resource conflicts. Thus, multiple second devices can respond to the first device simultaneously without causing conflicts, effectively avoiding the waiting time of the time-division multiplexing-based inventory method in existing solutions. This significantly improves the inventory efficiency and accuracy of second devices (such as tags). In addition, this method can be effectively applied to scenarios involving the inventory of large-scale second devices (such as the inventory of large-scale tags), meeting the needs for efficient and rapid inventory in high-density second device environments (such as high-density tag environments).

[0235] Based on the technical solution of the communication method shown in Figure 3 above, the communication method shown in Figure 3 will be described in detail below through specific examples shown in Figures 6a to 6e. In the specific examples shown in Figures 6a to 6e, the first device is a reader, the second device is tag v1, and the attribute information of the second device is the EPC of the second device.

[0236] Figure 6a is a flowchart illustrating another communication method provided in an embodiment of this application. As shown in Figure 6a, the specific flow of this method may include:

[0237] Step 601a: The reader sends a selection instruction p1. Accordingly, the tag v1 receives the selection instruction p1.

[0238] Understandably, the selection instruction p1 can be used to select (or select) one or more tags that meet the set conditions. These tags can then be entered into the inventory cycle.

[0239] For example, the settings can include the range of tags that need to be inventoried (such as EPCs or TIDs within a certain range, or certain specific identification ranges), or the signal coverage range of the reader, and so on.

[0240] Optionally, the selection instruction p1 may include the above-mentioned setting conditions.

[0241] In one example, let's consider a range of tags that need to be inventoried, defined by conditions. After detecting a selection instruction p1, tag v1 can determine whether it belongs to the range of tags included in p1. If it does, tag v1 can provide feedback upon detecting a subsequent query instruction. If it does not belong to the range of tags included in p1, tag v1 will not take any further action.

[0242] In another example, let's consider a condition that includes the reader's signal coverage. If tag v1 detects the selection command p1, it means tag v1 is within the reader's signal coverage area, and therefore tag v1 can provide feedback after detecting a subsequent query command. If tag v1 does not detect the selection command p1, it means tag v1 may not be within the reader's signal coverage area, and therefore tag v1 may not take any further action.

[0243] Step 602a: The reader sends a query command q1. Accordingly, tag v1 receives the query command q1.

[0244] The query instruction q1 may include system information (such as system frame number and timeslot number) and mapping relationship d1 required for synchronization between the reader and the tags. Mapping relationship d1 describes the mapping relationship between the identification information of m tags and the information of their corresponding time-domain resources (also known as access time-domain resources). Here, m is an integer greater than or equal to 1. It can be understood that the information of the time-domain resource corresponding to each of the m tags can be represented by the starting position (such as the starting time or starting moment) and length (such as the time length) of the time-domain resource corresponding to that tag. Optionally, mapping relationship d1 may also describe m mapping relationships. Optionally, the query instruction q1 may also include m mapping relationships. One of the m mapping relationships describes the mapping relationship between the identification information of a tag and the information of the time-domain resource corresponding to that tag.

[0245] For example, taking a query instruction q1 with m = 2, which includes mapping relationship d1. Mapping relationship d1 describes the mapping relationship between the identification information of tag v1 and the information of time-domain resource z1, and the mapping relationship between the identification information of tag v2 and the information of time-domain resource z2. Time-domain resource z1 and time-domain resource z2 are not the same.

[0246] For example, the information of time-domain resource z1 can be represented by its starting position and length. The information of time-domain resource z2 can be represented by its starting position and length. Thus, mapping relationship d1 is used to describe the mapping relationship between the identification information of tag v1 and the starting position and length of time-domain resource z1, and the mapping relationship between the identification information of tag v2 and the starting position and length of time-domain resource z2.

[0247] For example, with m = 2, the query instruction q1 includes two mapping relationships (such as mapping relationship w1 and mapping relationship w2). Mapping relationship w1 describes the mapping relationship between the identification information of tag v1 and the information of time-domain resource z1. Mapping relationship w2 describes the mapping relationship between the identification information of tag v2 and the information of time-domain resource z2.

[0248] For example, the information of time-domain resource z1 can be represented by its starting position and length. Thus, mapping w1 describes the mapping relationship between the identification information of tag v1 and the starting position and length of time-domain resource z1. Similarly, the information of time-domain resource z2 can be represented by its starting position and length. Thus, mapping w2 describes the mapping relationship between the identification information of tag v2 and the starting position and length of time-domain resource z2.

[0249] For example, consider a tag v1 monitoring (or receiving) a query command q1 broadcast by a reader. Query command q1 includes at least one mapping relationship (such as mapping relationship w1, mapping relationship w2, etc.) and the system frame number and timeslot number required for synchronization between the reader and the tag. Mapping relationship w1 describes the mapping relationship between tag v1 and the starting position and length of time-domain resource z1. After receiving the query command q1 broadcast by the reader, tag v1 can obtain the mapping relationship w1 corresponding to tag v1, as well as the system frame number and timeslot number required for synchronization between the reader and the tag, from the query command q1. Then, tag v1 can determine a timeslot based on the system frame number and timeslot number. Finally, tag v1 can determine the corresponding time-domain resource z1 within that timeslot based on the starting position and length of the time-domain resource z1 included in mapping relationship w1.

[0250] Step 603a: Tag v1 sends information u1 on resource g1. Correspondingly, the reader receives information u1 from tag v1 on resource g1.

[0251] Wherein, resource g1 includes the time-domain resource z1 corresponding to tag v1. Optionally, resource g1 may also include frequency-domain resources. This frequency-domain resource is the allocated frequency-domain resource required for information interaction (or information transmission or data interaction) between at least one tag reader and reader. In the communication method shown in Figure 6a, tag v1 shares (or shares) a frequency-domain resource with other tags that meet the above-mentioned conditions (such as tag v2, tag v3, etc.).

[0252] For example, a frequency domain resource can be predefined (or preconfigured), or it can be carried by the reader in the selection command p1 or the query command q1.

[0253] Optionally, resource g1 may also include code field resources. These code field resources are allocated for information exchange between at least one tag reader and the reader. In one example, tag v1 and other tags that meet the above-mentioned conditions (such as tag v2, tag v3, etc.) may share a single code field resource. For example, this single code field resource may be predefined or carried by the reader in the selection instruction p1 or query instruction q1. In another example, each tag is assigned a code field resource. That is, each tag can use its own dedicated code field resource to interact with the reader. For example, code field resource e1 is assigned to tag v1, code field resource e2 is assigned to tag v2, and so on. For example, the code field resource corresponding to each tag may be predefined or carried (or included or contained) in the selection instruction p1 or query instruction q1. For example, the reader may carry the code field resource corresponding to each tag in the selection instruction p1 or query instruction q1, or the reader may carry the number of the code field resource corresponding to each tag in the selection instruction p1 or query instruction q1.

[0254] In one example, information u1 may include a random number, such as random number y1. This random number can be used for tag v1 authentication. Optionally, the random number can be used for handshake authentication or access authentication between tag v1 and the reader.

[0255] In another example, information u1 may include a 1-bit indication, such as indication o1. This 1-bit indication is used for tag v1 authentication. Optionally, this 1-bit indication can be used for handshake authentication or access authentication between tag v1 and the reader. For example, in some embodiments, information u1 may be a 1-bit indication. Optionally, the 1-bit indication can be used to indicate a random number, or it can be used to indicate other information or data.

[0256] Step 604a: The reader sends response information r1 on resource g1. Correspondingly, tag v1 receives response information r1 from the reader on resource g1.

[0257] In one example, let's assume that information u1 includes a random number (e.g., random number y1). After receiving information u1 from tag v1 on resource g1, the reader can obtain the random number y1 from information u1. Then, the reader can send a response message r1 back to tag v1. The response message r1 can include a random number (e.g., random number y1'). After receiving the response message r1 from the reader, tag v1 can obtain the random number y1' from the response message r1. Then, tag v1 can determine (or verify) whether the random number y1' is the same as the random number y1 previously sent to the reader. If the random number y1' is the same as the random number y1, then tag v1 connects to the reader; this can be understood as a successful handshake between tag v1 and the reader. If the random number y1' is different from the random number y1, then tag v1 does not connect to the reader; this can be understood as a failed handshake between tag v1 and the reader.

[0258] In another example, let's assume that information u1 includes a 1-bit indication (e.g., indication o1). After receiving information u1 from tag v1 on resource g1, the reader can retrieve the indication o1 from information u1. Then, the reader can send a response message r1 back to tag v1. The response message r1 can include a 1-bit indication (e.g., indication o1'). After receiving the response message r1 from the reader, tag v1 can retrieve the indication o1' from the response message r1. Then, tag v1 can determine whether the indication o1' is the same as the indication o1 previously sent to the reader; this can be understood as determining whether the value (or bit value) of the indication o1' is the same as the value of the indication o1 previously sent to the reader. If the indication o1' is the same as the indication o1 (meaning the bit value of the indication o1' is the same as the bit value of the indication o1), then tag v1 connects to the reader. If the indication information o1' is not the same as the indication information o1 (which can be understood as the bit value of the indication information o1' being different from the bit value of the indication information o1), then tag v1 will not be connected to the reader.

[0259] Optionally, if tag v1 is connected to a reader, this embodiment of the application may perform steps 605a to 606a as described below. If tag v1 is not connected to a reader, this embodiment of the application does not need to perform steps 605a to 606a as described below.

[0260] Step 605a: Tag v1 sends its EPC on resource g1. Correspondingly, the reader receives the EPC of tag v1 on resource g1.

[0261] In this embodiment of the application, when the tag v1 is connected to the reader, it can send its own attribute information (also known as its own information), such as EPC or other identification information, to the resource g1.

[0262] Step 606a: The reader sends information n1 on resource g1. Correspondingly, tag v1 receives information n1 from the reader on resource g1.

[0263] For example, in one instance, if the reader fails to receive EPC for tag v1, the reader can send information n1 on resource g1. Information n1 can indicate that EPC reception failed (or EPC was not successfully received). For instance, in this example, information n1 could be a NAK message. Afterwards, tag v1, upon receiving information n1 from the reader on resource g1, can return to the arbitration state.

[0264] In another example, if the reader successfully receives the EPC for tag v1, the reader can send information n1 on resource g1. Information n1 can be used to indicate successful EPC reception. For example, in this example, information n1 can be other information (or other signaling) besides NAK information. After receiving information n1 from the reader on resource g1, tag v1 can then enter the acknowledged state.

[0265] As can be seen from steps 601a to 606a above, by flexibly configuring or allocating the starting position and length of the corresponding time-domain resources for different tags, efficient utilization of time-domain resources can be achieved (which can be understood as high utilization rate of time-domain resources). This facilitates refined management of time-domain resources and allows different tags to interact with the reader on their respective time-domain resources. This effectively reduces resource conflicts when multiple tags interact with the reader separately, thereby effectively improving the tag identification efficiency of the RFID system (also known as tag inventory efficiency). Furthermore, since the starting position and length of the time-domain resources corresponding to different tags can be flexibly allocated according to actual needs, the configuration of time-domain resources corresponding to different tags is quite flexible.

[0266] Figure 6b is a flowchart illustrating another communication method provided in an embodiment of this application. As shown in Figure 6b, the specific flow of this method may include:

[0267] Step 601b: The reader sends selection instruction p2. Accordingly, tag v1 receives selection instruction p2.

[0268] The implementation process of step 601b can refer to the implementation process of step 601a above, only the instruction p1 is replaced with instruction p2, which will not be repeated here.

[0269] Step 602b: The reader sends a query command q2. Accordingly, tag v1 receives the query command q2.

[0270] The query instruction q2 may include system information required for reader-tag synchronization (such as system frame number and timeslot number), the starting position of time-domain resource set j1, the length of time-domain resources included in time-domain resource set j1, the interval between two adjacent time-domain resources in time-domain resource set j1, and mapping relationship d2. Mapping relationship d2 describes the mapping relationship between the identification information of m tags and the information of their corresponding time-domain resources (also called access time-domain resources). Here, m is an integer greater than or equal to 1. It can be understood that the information of the time-domain resource corresponding to each of the m tags can be represented by the number of the time-domain resource corresponding to that tag. Optionally, mapping relationship d2 may also describe m mapping relationships. Optionally, the query instruction q2 may also include m mapping relationships. One of the m mapping relationships describes the mapping relationship between the identification information of a tag and the information of the time-domain resource corresponding to that tag.

[0271] For example, taking m as 2, the query instruction q2 includes the mapping relationship d2. Here, mapping relationship d2 describes the mapping relationship between the identification information of tag v1 and the information of time-domain resource z1', and the mapping relationship between the identification information of tag v2 and the information of time-domain resource z2'. Time-domain resource z1' and time-domain resource z2' are not the same.

[0272] For example, the information of time-domain resource z1' can be represented by the number of time-domain resource z1'. The information of time-domain resource z2' can be represented by the number of time-domain resource z2'. Thus, mapping relationship d2 is used to describe the mapping relationship between the identification information of tag v1 and the number of time-domain resource z1', and the mapping relationship between the identification information of tag v2 and the number of time-domain resource z2'.

[0273] For example, with m = 2, the query instruction q2 includes two mapping relationships (such as mapping relationship w1' and mapping relationship w2'). Mapping relationship w1' describes the mapping relationship between the identification information of tag v1 and the information of time-domain resource z1'. Mapping relationship w2' describes the mapping relationship between the identification information of tag v2 and the information of time-domain resource z2'.

[0274] For example, the information of time-domain resource z1' can be represented by the number of time-domain resource z1'. Thus, the mapping relationship w1' describes the mapping relationship between the identification information of tag v1 and the number of time-domain resource z1'. Similarly, the information of frequency-domain resource z2' can be represented by the number of frequency-domain resource z2'. Thus, the mapping relationship w2' describes the mapping relationship between the identification information of tag v2 and the number of frequency-domain resource z2'.

[0275] For example, consider a tag v1 detecting a query command q2 broadcast by a reader. Query command q2 includes at least one mapping relationship (e.g., mapping relationship w1', mapping relationship w2', etc.), the starting position of time-domain resource set j1, the length of the time-domain resources included in time-domain resource set j1, the interval between two adjacent time-domain resources in time-domain resource set j1, and the system frame number and time slot number required for synchronization between the reader and the tag. Mapping relationship w1' describes the mapping relationship between the tag v1 and the numbering of time-domain resource z1'. After receiving the query command q2 broadcast by the reader, tag v1 can obtain the mapping relationship w1' corresponding to tag v1, the starting position of time-domain resource set j1, the length of the time-domain resources included in time-domain resource set j1, the interval between two adjacent time-domain resources in time-domain resource set j1, and the system frame number and time slot number required for synchronization between the reader and the tag from the query command q2. Then, tag v1 can determine a time slot based on the system frame number and time slot number. Next, label v1 can determine multiple time-domain resources within the time slot based on the starting position of time-domain resource set j1, the length of the time-domain resources included in time-domain resource set j1, and the interval between two adjacent time-domain resources in time-domain resource set j1. Understandably, the multiple time-domain resources included in time-domain resource set j1 can each have their own unique number. Then, label v1 can determine the time-domain resource z1' corresponding to label v1 from among these multiple time-domain resources based on the number of the time-domain resource z1' included in mapping relationship w1'.

[0276] Step 603b: Tag v1 sends information u2 on resource g2. Accordingly, the reader receives information u2 from tag v1 on resource g2.

[0277] Resource g2 includes the time-domain resource z1' corresponding to tag v1. Optionally, resource g2 may also include frequency-domain resources. These frequency-domain resources are allocated for information exchange between at least one tag reader and a tag reader. In the communication method shown in Figure 6b, tag v1 shares a frequency-domain resource with other tags that meet the above-mentioned conditions (such as tag v2, tag v3, etc.).

[0278] For example, a frequency domain resource can be predefined, or it can be carried by the reader in the selection instruction p2 or the query instruction q2.

[0279] Optionally, resource g2 may also include code field resources. These code field resources are allocated for information exchange between at least one tag reader and the reader. In one example, tag v1 and other tags that meet the above-mentioned conditions (such as tag v2, tag v3, etc.) may share a single code field resource. For example, this single code field resource may be predefined or carried by the reader in the selection instruction p2 or query instruction q2. In another example, each tag is assigned a code field resource. That is, each tag can use its own dedicated code field resource to interact with the reader. For example, code field resource e1' is assigned to tag v1, code field resource e2' is assigned to tag v2, and so on. For example, the code field resource corresponding to each tag may be predefined or carried in the selection instruction p2 or query instruction q2. For instance, the reader may carry the code field resource corresponding to each tag in the selection instruction p2 or query instruction q2, or the reader may carry the number of the code field resource corresponding to each tag in the selection instruction p2 or query instruction q2.

[0280] In one example, information u2 may include a random number, such as random number y2. This random number can be used for authentication of tag v1. Optionally, the random number can be used for handshake authentication or access authentication between tag v1 and the reader.

[0281] In another example, information u2 may include a 1-bit indication, such as indication o2. This 1-bit indication is used for tag v1 authentication. Optionally, this 1-bit indication can be used for handshake authentication or access authentication between tag v1 and the reader. For example, in some embodiments, information u2 may be a 1-bit indication. Optionally, the 1-bit indication can be used to indicate a random number, or it can be used to indicate other information or data.

[0282] Step 604b: The reader sends response information r2 on resource g2. Accordingly, tag v1 receives response information r2 from the reader on resource g2.

[0283] In one example, let's assume that information u2 includes a random number (e.g., random number y2). After receiving information u2 from tag v1 on resource g2, the reader can obtain the random number y2 from information u2. Then, the reader can send a response message r2 back to tag v1. The response message r2 can include a random number (e.g., random number y2'). After receiving the response message r2 from the reader, tag v1 can obtain the random number y2' from the response message r2. Then, tag v1 can determine whether the random number y2' is the same as the random number y2 previously sent to the reader. If the random number y2' is the same as the random number y2, then tag v1 connects to the reader; this can be understood as a successful handshake between tag v1 and the reader. If the random number y2' is different from the random number y2, then tag v1 does not connect to the reader; this can be understood as a failed handshake between tag v1 and the reader.

[0284] In another example, let's assume that information u2 includes a 1-bit indication (e.g., indication o2). After receiving information u2 from tag v1 on resource g2, the reader can retrieve the indication o2 from information u2. Then, the reader can send a response message r2 back to tag v1. The response message r2 can include a 1-bit indication (e.g., indication o2'). After receiving the response message r2 from the reader, tag v1 can retrieve the indication o2' from the response message r2. Then, tag v1 can determine whether the indication o2' is the same as the indication o2 previously sent to the reader; this can be understood as determining whether the value of the indication o2' is the same as the value of the indication o2 previously sent to the reader. If the indication o2' is the same as the indication o2, then tag v1 connects to the reader. If the indication o2' is different from the indication o2, then tag v1 does not connect to the reader.

[0285] Optionally, if tag v1 is connected to a reader, this embodiment of the application may perform steps 605b to 606b below. If tag v1 is not connected to a reader, this embodiment of the application does not need to perform steps 605b to 606b below.

[0286] Step 605b: Tag v1 sends its EPC on resource g2. Correspondingly, the reader receives the EPC of tag v1 on resource g2.

[0287] In this embodiment of the application, when the tag v1 is connected to the reader, it can send its own attribute information, such as EPC or other identification information, to the resource g2.

[0288] Step 606b: The reader sends information n2 on resource g2. Correspondingly, tag v1 receives information n2 from the reader on resource g2.

[0289] The implementation process of step 606b can refer to the implementation process of step 606a above, and will not be repeated here.

[0290] As can be seen from steps 601b to 606b above, by configuring or allocating the starting position of a shared time-domain resource set, the length of the time-domain resources included in the time-domain resource set, and the interval between two adjacent time-domain resources in the time-domain resource set for different tags, it is possible for different tags to promptly and accurately determine multiple time-domain resources based on the starting position of the time-domain resource set, the length of the time-domain resources included in the time-domain resource set, and the interval between two adjacent time-domain resources in the time-domain resource set. Furthermore, based on the number of their respective time-domain resources, they can determine their corresponding time-domain resources from among the multiple time-domain resources. This further enables different tags to interact with the reader on their respective time-domain resources, which helps to effectively reduce resource conflicts when multiple tags interact with the reader separately, thereby effectively improving the tag identification efficiency of the RFID system. Furthermore, when the reader sends information about time-domain resources corresponding to different tags, compared to the communication method shown in Figure 6a where query instruction q1 carries the starting position and length of time-domain resources corresponding to different tags, the communication method shown in Figure 6b only needs to carry the starting position of the time-domain resource set shared by different tags, the length of the time-domain resources, and the interval between two adjacent time-domain resources in the time-domain resource set. Therefore, the information about time-domain resources carried in query instruction q2 is less than that carried in query instruction q1, thereby reducing communication overhead.

[0291] Figure 6c is a flowchart illustrating another communication method provided in an embodiment of this application. As shown in Figure 6c, the specific flow of this method may include:

[0292] Step 601c: The reader sends selection instruction p3. Accordingly, tag v1 receives selection instruction p3.

[0293] The implementation process of step 601c can refer to the implementation process of step 601a above, only the instruction p1 is replaced with instruction p3, which will not be repeated here.

[0294] Step 602c: The reader sends a query command q3. Accordingly, tag v1 receives the query command q3.

[0295] The query instruction q3 may include system information (such as system frame number and time slot number) and mapping relationship d3 required for synchronization between the reader and the tags. Mapping relationship d3 describes the mapping relationship between the identification information of m tags and the information of their corresponding frequency domain resources (also called access frequency domain resources). Here, m is an integer greater than or equal to 1. It can be understood that the information of the frequency domain resources corresponding to each of the m tags can be represented by the starting position (such as the starting frequency point or starting subcarrier) and frequency domain width of the frequency domain resources corresponding to that tag. Optionally, mapping relationship d3 may also describe m mapping relationships. Optionally, the query instruction q3 may also include m mapping relationships. One of the m mapping relationships describes the mapping relationship between the identification information of a tag and the information of the frequency domain resources corresponding to that tag.

[0296] For example, taking m as 2, the query instruction q3 includes the mapping relationship d3. Mapping relationship d3 describes the mapping relationship between the identification information of tag v1 and the information of frequency domain resource x1, and the mapping relationship between the identification information of tag v2 and the information of frequency domain resource x2. Frequency domain resource x1 and frequency domain resource x2 are not the same.

[0297] For example, the information of frequency domain resource x1 can be represented by its starting position and frequency width. Similarly, the information of frequency domain resource x2 can be represented by its starting position and frequency width. Thus, mapping relationship d3 describes the mapping relationship between the identification information of tag v1 and the starting position and frequency width of frequency domain resource x1, as well as the mapping relationship between the identification information of tag v2 and the starting position and frequency width of frequency domain resource x2.

[0298] For example, with m = 2, the query instruction q3 includes two mapping relationships (such as mapping relationship w1” and mapping relationship w2”). Mapping relationship w1” describes the mapping relationship between the identification information of tag v1 and the information of frequency domain resource x1. Mapping relationship w2” describes the mapping relationship between the identification information of tag v2 and the information of frequency domain resource x2.

[0299] For example, the information of frequency domain resource x1 can be represented by its starting position and length. Thus, mapping w1” describes the mapping relationship between the identification information of tag v1 and the starting position and width of frequency domain resource x1. Similarly, the information of frequency domain resource x2 can be represented by its starting position and width. Thus, mapping w2” describes the mapping relationship between the identification information of tag v2 and the starting position and width of frequency domain resource x2.

[0300] For example, consider a tag v1 detecting a query command q3 broadcast by a reader. Query command q3 includes at least one mapping relationship (such as mapping relationship w1”, mapping relationship w2”, etc.) and the system frame number and timeslot number required for synchronization between the reader and the tag. Mapping relationship w1” describes the mapping relationship between tag v1 and the starting position and frequency domain width of frequency domain resource x1. After receiving the query command q3 broadcast by the reader, tag v1 can obtain the mapping relationship w1” corresponding to tag v1 from the query command q3. Then, tag v1 can determine the frequency domain resource x1 corresponding to tag v1 based on the starting position and frequency domain width of frequency domain resource x1 included in mapping relationship w1”.

[0301] Step 603c: Tag v1 sends information u3 on resource g3. Accordingly, the reader receives information u3 from tag v1 on resource g3.

[0302] Resource g3 includes the frequency domain resource x1 corresponding to tag v1. Optionally, resource g3 may also include a time domain resource. This time domain resource is allocated for information exchange between at least one tag reader and a tag reader. In the communication method shown in Figure 6c, tag v1 shares a time domain resource with other tags that meet the above-mentioned conditions (such as tag v2, tag v3, etc.).

[0303] For example, a time-domain resource can be predefined, or it can be carried by the reader in the selection command p3 or the query command q3.

[0304] Optionally, resource g3 may also include code field resources. These code field resources are allocated for information exchange between at least one tag reader and the reader. In one example, tag v1 and other tags that meet the above-mentioned conditions (such as tag v2, tag v3, etc.) may share a single code field resource. For example, this single code field resource may be predefined or carried by the reader in the selection instruction p3 or query instruction q3. In another example, each tag is assigned a code field resource. That is, each tag can use its own dedicated code field resource to interact with the reader. For example, code field resource e1” is assigned to tag v1, code field resource e2” is assigned to tag v2, and so on. For example, the code field resource corresponding to each tag may be predefined or carried in the selection instruction p3 or query instruction q3. For example, the reader may carry the code field resource corresponding to each tag in the selection instruction p3 or query instruction q3, or the reader may carry the number of the code field resource corresponding to each tag in the selection instruction p3 or query instruction q3.

[0305] In one example, information u3 may include a random number, such as random number y3. This random number can be used for tag v1 authentication. Optionally, the random number can be used for handshake authentication or access authentication between tag v1 and the reader.

[0306] In another example, information u3 may include a 1-bit indication, such as indication o3. This 1-bit indication is used for tag v1 authentication. Optionally, this 1-bit indication can be used for handshake authentication or access authentication between tag v1 and the reader. For example, in some embodiments, information u3 may be a 1-bit indication. Optionally, the 1-bit indication can be used to indicate a random number, or it can be used to indicate other information or data.

[0307] Step 604c: The reader sends response information r3 on resource g3. Accordingly, tag v1 receives response information r3 from the reader on resource g3.

[0308] In one example, let's assume that information u3 includes a random number (e.g., random number y3). After receiving information u3 from tag v1 on resource g3, the reader can obtain the random number y3 from information u3. Then, the reader can send a response message r3 back to tag v1. The response message r3 can include a random number (e.g., random number y3'). After receiving the response message r3 from the reader, tag v1 can obtain the random number y3' from the response message r3. Then, tag v1 can determine whether the random number y3' is the same as the random number y3 previously sent to the reader. If the random number y3' is the same as the random number y3, then tag v1 connects to the reader; this can be understood as a successful handshake between tag v1 and the reader. If the random number y3' is different from the random number y3, then tag v1 does not connect to the reader; this can be understood as a failed handshake between tag v1 and the reader.

[0309] In another example, let's assume that information u3 includes a 1-bit indication (e.g., indication o3). After receiving information u3 from tag v1 on resource g3, the reader can retrieve the indication o3 from information u3. Then, the reader can send a response r3 back to tag v1. The response r3 can include a 1-bit indication (e.g., indication o3'). After receiving the response r3 from the reader, tag v1 can retrieve the indication o3' from the response r3. Then, tag v1 can determine whether the indication o3' is the same as the indication o3 previously sent to the reader; this can be understood as determining whether the value of the indication o3' is the same as the value of the indication o3 previously sent to the reader. If the indication o3' is the same as the indication o3, tag v1 connects to the reader. If the indication o3' is different from the indication o3, tag v1 does not connect to the reader.

[0310] Optionally, if tag v1 is connected to a reader, this embodiment of the application may perform steps 605c to 606c below. If tag v1 is not connected to a reader, this embodiment of the application does not need to perform steps 605c to 606c below.

[0311] Step 605c: Tag v1 sends its EPC on resource g3. Correspondingly, the reader receives the EPC of tag v1 on resource g3.

[0312] In this embodiment of the application, when the tag v1 is connected to the reader, it can send its own attribute information, such as EPC or other identification information, to the resource g3.

[0313] Step 606c: The reader sends information n3 on resource g3. Correspondingly, tag v1 receives information n3 from the reader on resource g3.

[0314] The implementation process of step 606c can refer to the implementation process of step 606a above, and will not be repeated here.

[0315] As can be seen from steps 601c to 606c above, by flexibly configuring or allocating the starting position and frequency bandwidth of corresponding frequency domain resources for different tags, efficient utilization of frequency domain resources can be achieved (which can be understood as high utilization rate of frequency domain resources). This facilitates refined management of frequency domain resources and allows different tags to interact with the reader on their respective corresponding frequency domain resources. This effectively reduces resource conflicts when multiple tags interact with the reader separately, thereby effectively improving the tag identification efficiency of the RFID system. Furthermore, since the starting position and frequency bandwidth of the frequency domain resources corresponding to different tags can be flexibly allocated according to actual needs, the configuration of frequency domain resources corresponding to different tags is quite flexible.

[0316] Figure 6d is a flowchart illustrating another communication method provided in an embodiment of this application. As shown in Figure 6d, the specific flow of this method may include:

[0317] Step 601d: The reader sends selection instruction p4. Accordingly, tag v1 receives selection instruction p4.

[0318] The implementation process of step 601d can refer to the implementation process of step 601a above, only the instruction p1 needs to be replaced with instruction p4, which will not be repeated here.

[0319] Step 602d: The reader sends query command q4. Accordingly, tag v1 receives query command q4.

[0320] The query instruction q4 may include system information required for reader-tag synchronization (such as system frame number and time slot number), the starting position of frequency domain resource set J1, the frequency domain width of the frequency domain resources included in frequency domain resource set J1, the interval between two adjacent frequency domain resources in frequency domain resource set J1, and mapping relationship d4. Mapping relationship d4 describes the mapping relationship between the identification information of m tags and the information of their corresponding frequency domain resources. Here, m is an integer greater than or equal to 1. It can be understood that the information of the frequency domain resources corresponding to each of the m tags can be represented by the number of the frequency domain resources corresponding to that tag. Optionally, mapping relationship d4 may also describe m mapping relationships. Optionally, the query instruction q4 may also include m mapping relationships. One of the m mapping relationships describes the mapping relationship between the identification information of a tag and the information of the frequency domain resources corresponding to that tag.

[0321] For example, with m = 2, the query instruction q4 includes the mapping relationship d4. Mapping relationship d4 describes the mapping relationship between the identification information of tag v1 and the information of frequency domain resource x1', and the mapping relationship between the identification information of tag v2 and the information of frequency domain resource x2'. Frequency domain resource x1' and frequency domain resource x2' are not the same.

[0322] For example, the information of frequency domain resource x1' can be represented by the number of frequency domain resource x1'. The information of frequency domain resource x2' can be represented by the number of frequency domain resource x2'. Thus, mapping relationship d4 is used to describe the mapping relationship between the identification information of tag v1 and the number of frequency domain resource x1', and the mapping relationship between the identification information of tag v2 and the number of frequency domain resource x2'.

[0323] For example, with m = 2, the query instruction q4 includes two mapping relationships (such as mapping relationship w1”' and mapping relationship w2”'). Mapping relationship w1”' describes the mapping relationship between the identification information of tag v1 and the information of frequency domain resource x1'. Mapping relationship w2”' describes the mapping relationship between the identification information of tag v2 and the information of frequency domain resource x2'.

[0324] For example, the information of frequency domain resource x1' can be represented by the number of frequency domain resource x1'. Thus, the mapping relationship w1”' describes the mapping relationship between the identification information of tag v1 and the number of frequency domain resource x1'. Similarly, the information of frequency domain resource x2' can be represented by the number of frequency domain resource x2'. Thus, the mapping relationship w2”' describes the mapping relationship between the identification information of tag v2 and the number of frequency domain resource x2'.

[0325] For example, consider a query command q4 broadcast by a reader, where tag v1 detects this command. Query command q4 includes at least one mapping relationship (e.g., mapping relationship w1”', mapping relationship w2”', etc.), the starting position of frequency domain resource set J1, the frequency domain width of the frequency domain resources included in frequency domain resource set J1, the interval between two adjacent frequency domain resources in frequency domain resource set J1, and the system frame number and timeslot number required for synchronization between the reader and the tag. The mapping relationship w1”' describes the mapping relationship between the identification information of tag v1 and the number of frequency domain resource x1'. After receiving the query command q4 broadcast by the reader, tag v1 can obtain the mapping relationship w1”' corresponding to tag v1, the starting position of frequency domain resource set J1, the frequency domain width of the frequency domain resources included in frequency domain resource set J1, the interval between two adjacent frequency domain resources in frequency domain resource set J1, and the system frame number and timeslot number required for synchronization between the reader and the tag from the query command q4. Subsequently, label v1 can determine multiple frequency domain resources based on the starting position of frequency domain resource set J1, the frequency domain width of the frequency domain resources included in frequency domain resource set J1, and the interval between two adjacent frequency domain resources in frequency domain resource set J1. It is understood that the multiple frequency domain resources included in frequency domain resource set J1 can each have their own unique number. Then, label v1 can determine the frequency domain resource x1' corresponding to label v1 among these multiple frequency domain resources based on the number of the frequency domain resource x1' included in mapping relationship w1”'.

[0326] Step 603d: Tag v1 sends information u4 on resource g4. Accordingly, the reader receives information u4 from tag v1 on resource g4.

[0327] Resource g4 includes the frequency domain resource x1' corresponding to tag v1. Optionally, resource g4 may also include a time domain resource. This time domain resource is allocated for information exchange between at least one tag reader and a tag reader. In the communication method shown in Figure 6d, tag v1 shares a time domain resource with other tags that meet the above-mentioned conditions (such as tag v2, tag v3, etc.).

[0328] For example, a time-domain resource can be predefined, or it can be carried by the reader in the selection command p3 or the query command q3.

[0329] Optionally, resource g4 may also include code field resources. These code field resources are allocated for information exchange between at least one tag reader and the reader. In one example, tag v1 and other tags that meet the above-mentioned conditions (such as tag v2, tag v3, etc.) may share a single code field resource. For example, this single code field resource may be predefined or carried by the reader in the selection instruction p4 or query instruction q4. In another example, each tag is assigned a code field resource. That is, each tag can use its own dedicated code field resource to interact with the reader. For example, code field resource e1”' is assigned to tag v1, code field resource e2”' is assigned to tag v2, and so on. For example, the code field resource corresponding to each tag may be predefined or carried in the selection instruction p4 or query instruction q4. For example, the reader may carry the code field resource corresponding to each tag in the selection instruction p4 or query instruction q4, or the reader may carry the number of the code field resource corresponding to each tag in the selection instruction p4 or query instruction q4.

[0330] In one example, information u4 may include a random number, such as random number y4. This random number can be used for tag v1 authentication. Optionally, the random number can be used for handshake authentication or access authentication between tag v1 and the reader.

[0331] In another example, information u4 may include a 1-bit indication, such as indication o4. This 1-bit indication is used for tag v1 authentication. Optionally, this 1-bit indication can be used for handshake authentication or access authentication between tag v1 and the reader. For example, in some embodiments, information u4 may be a 1-bit indication. Optionally, the 1-bit indication can be used to indicate a random number, or it can be used to indicate other information or data.

[0332] Step 604d: The reader sends response information r4 on resource g4. Accordingly, tag v1 receives response information r4 from the reader on resource g4.

[0333] In one example, let's assume that information u4 includes a random number (e.g., random number y4). After receiving information u4 from tag v1 on resource g4, the reader can obtain the random number y4 from information u4. Then, the reader can send a response message r4 back to tag v1. The response message r4 can include a random number (e.g., random number y4'). After receiving the response message r4 from the reader, tag v1 can obtain the random number y4' from the response message r4. Then, tag v1 can determine whether the random number y4' is the same as the random number y4 previously sent to the reader. If the random number y4' is the same as the random number y4, then tag v1 connects to the reader; this can be understood as a successful handshake between tag v1 and the reader. If the random number y4' is different from the random number y4, then tag v1 does not connect to the reader; this can be understood as a failed handshake between tag v1 and the reader.

[0334] In another example, let's assume that information u4 includes a 1-bit indication (e.g., indication o4). After receiving information u4 from tag v1 on resource g4, the reader can retrieve the indication o4 from information u4. Then, the reader can send a response message r4 back to tag v1. The response message r4 can include a 1-bit indication (e.g., indication o4'). After receiving the response message r4 from the reader, tag v1 can retrieve the indication o4' from the response message r4. Then, tag v1 can determine whether the indication o4' is the same as the indication o4 previously sent to the reader; this can be understood as determining whether the value of the indication o4' is the same as the value of the indication o4 previously sent to the reader. If the indication o4' is the same as the indication o4, then tag v1 connects to the reader. If the indication o4' is different from the indication o4, then tag v1 does not connect to the reader.

[0335] Optionally, if tag v1 is connected to a reader, this embodiment of the application may perform steps 605d to 606d below. If tag v1 is not connected to a reader, this embodiment of the application does not need to perform steps 605d to 606d below.

[0336] Step 605d: Tag v1 sends its EPC on resource g4. Correspondingly, the reader receives the EPC of tag v1 on resource g4.

[0337] In this embodiment of the application, when the tag v1 is connected to the reader, it can send its own attribute information, such as EPC or other identification information, to the resource g4.

[0338] Step 606d: The reader sends information n4 on resource g4. Correspondingly, tag v1 receives information n4 from the reader on resource g4.

[0339] The implementation process of step 606d can refer to the implementation process of step 606a above, and will not be repeated here.

[0340] As can be seen from steps 601d to 606d above, by configuring or allocating the starting position of a shared frequency domain resource set, the frequency domain width of the frequency domain resources included in the frequency domain resource set, and the interval between two adjacent frequency domain resources in the frequency domain resource set for different tags, it is possible for different tags to promptly and accurately determine multiple frequency domain resources based on the starting position of the frequency domain resource set, the frequency domain width of the frequency domain resources included in the frequency domain resource set, and the interval between two adjacent frequency domain resources in the frequency domain resource set. Furthermore, based on the number of their respective frequency domain resources, different tags can determine their corresponding frequency domain resources from among the multiple frequency domain resources. This further enables different tags to interact with the reader on their respective corresponding frequency domain resources, which helps to effectively reduce resource conflicts when multiple tags interact with the reader separately, thereby effectively improving the tag identification efficiency of the RFID system. Furthermore, when the reader sends information about frequency domain resources corresponding to different tags, compared to the communication method shown in Figure 6c where query instruction q3 carries the starting position and frequency domain width of the frequency domain resources corresponding to different tags, the communication method shown in Figure 6d only needs to carry the starting position of the frequency domain resource set shared by different tags, the frequency domain width of the frequency domain resources, and the interval between two adjacent frequency domain resources in the frequency domain resource set. Therefore, the information about frequency domain resources carried in query instruction q4 is less than that carried in query instruction q3, thereby reducing communication overhead.

[0341] Figure 6e is a flowchart illustrating another communication method provided in an embodiment of this application. As shown in Figure 6e, the specific flow of this method may include:

[0342] Step 601e: The reader sends selection instruction p5. Accordingly, tag v1 receives selection instruction p5.

[0343] The implementation process of step 601e can refer to the implementation process of step 601a above, only the instruction p1 needs to be replaced with instruction p5, which will not be repeated here.

[0344] Step 602e: The reader sends a query command q5. Accordingly, tag v1 receives the query command q5.

[0345] The query instruction q5 may include system information (such as system frame number and time slot number) and mapping relationship d5 required for synchronization between the reader and the tags. Mapping relationship d5 describes the mapping relationship between the identification information of m tags and the information of their corresponding time-frequency resources (also called access time-frequency resources). Here, m is an integer greater than or equal to 1. It can be understood that the information of the time-frequency resources corresponding to each of the m tags can be represented by the starting position (e.g., starting time or starting moment), length (e.g., time length) of the time-domain resource corresponding to that tag, and the starting position (e.g., starting frequency point or starting subcarrier), and frequency-domain width of the frequency-domain resource corresponding to that tag. Optionally, mapping relationship d5 may also describe m mapping relationships. Optionally, the query instruction q5 may also include m mapping relationships. One of the m mapping relationships describes the mapping relationship between the identification information of a tag and the information of the time-frequency resource corresponding to that tag.

[0346] For example, taking m as 2, the query instruction q5 includes the mapping relationship d5. Mapping relationship d5 describes the mapping relationship between the identification information of tag v1 and the information of time-frequency resource S1, and the mapping relationship between the identification information of tag v2 and the information of time-frequency resource S2. Time-frequency resource S1 and time-frequency resource S2 are not the same.

[0347] For example, the information of time-frequency resource S1 can be represented by the starting position and length of time-domain resource z1, and the starting position and frequency width of frequency-domain resource x1. The information of time-frequency resource S2 can be represented by the starting position and length of time-domain resource z2, and the starting position and frequency width of frequency-domain resource x2. Thus, mapping relationship d5 is used to describe the mapping relationship between the identification information of tag v1 and the starting position, length, and frequency width of time-domain resource z1 and frequency-domain resource x1, and the mapping relationship between the identification information of tag v2 and the starting position, length, and frequency width of time-domain resource z2 and frequency-domain resource x2.

[0348] For example, with m = 2, the query instruction q5 includes two mapping relationships (such as mapping relationship w1"" and mapping relationship w2""). Mapping relationship w1"" describes the mapping relationship between the identification information of tag v1 and the information of time-frequency resource S1. Mapping relationship w2"" describes the mapping relationship between the identification information of tag v2 and the information of time-frequency resource S2.

[0349] For example, the information of time-frequency resource S1 can be represented by the starting position and length of time-domain resource z1, and the starting position and frequency width of frequency-domain resource x1. Thus, the mapping relationship w1"" describes the mapping relationship between the identification information of tag v1 and the starting position, length, and frequency width of time-domain resource z1 and frequency-domain resource x1. Similarly, the information of time-frequency resource S2 can be represented by the starting position and length of time-domain resource z2, and the starting position and frequency width of frequency-domain resource x2. Thus, the mapping relationship w2"" describes the mapping relationship between the identification information of tag v2 and the starting position, length, and frequency width of time-domain resource z2 and frequency-domain resource x2.

[0350] For example, consider a tag v1 detecting a query command q5 broadcast by a reader. Query command q5 includes at least one mapping relationship (such as mapping relationship w1"" and mapping relationship w2""), as well as the system frame number and time slot number required for synchronization between the reader and the tag. Mapping relationship w1"" describes the mapping relationship between the tag v1's identification information and the starting position and length of time-domain resource z1, and the starting position and frequency-domain width of frequency-domain resource x1. After receiving the query command q5 broadcast by the reader, tag v1 can obtain the mapping relationship w1"" corresponding to tag v1, as well as the system frame number and time slot number required for synchronization between the reader and the tag, from the query command q5. Then, tag v1 can determine a time slot based on the system frame number and time slot number. Finally, tag v1 can determine the corresponding time-domain resource z1 within that time slot based on the starting position and length of time-domain resource z1 included in the mapping relationship w1""". In addition, the frequency domain resource x1 corresponding to the tag v1 can also be determined based on the starting position and frequency domain width of the frequency domain resource x1 included in the mapping relationship w1””.

[0351] Optionally, the information of the time-frequency resource corresponding to each tag can also be represented by the number of the time-domain resource corresponding to the tag and the number of the frequency-domain resource corresponding to the tag.

[0352] For example, taking m as 2, the query instruction q5 includes the mapping relationship d5'. Here, mapping relationship d5' describes the mapping relationship between the identification information of tag v1 and the information of time-frequency resource S1', and the mapping relationship between the identification information of tag v2 and the information of time-frequency resource S2'. Time-frequency resource S1' and time-frequency resource S2' are not the same.

[0353] For example, the information of time-frequency resource S1' can be represented by the number of time-domain resource z1' and the number of frequency-domain resource x1'. The information of time-frequency resource S2' can be represented by the number of time-domain resource z2' and the number of frequency-domain resource x2'. Thus, the mapping relationship d5' is used to describe the mapping relationship between the identification information of tag v1 and the number of time-domain resource z1' and the number of frequency-domain resource x1', and the mapping relationship between the identification information of tag v2 and the number of time-domain resource z2' and the number of frequency-domain resource x2'.

[0354] For example, with m = 2, the query instruction q5 includes two mapping relationships (such as mapping relationship w1""' and mapping relationship w2""'). Mapping relationship w1""' describes the mapping relationship between the identification information of tag v1 and the information of time-frequency resource S1'. Mapping relationship w2""' describes the mapping relationship between the identification information of tag v2 and the information of time-frequency resource S2'.

[0355] For example, the information of time-frequency resource S1' can be represented by the number of time-domain resource z1' and the number of frequency-domain resource x1'. Thus, the mapping relationship w1””’ is used to describe the mapping relationship between the identification information of tag v1 and the numbers of time-domain resource z1' and frequency-domain resource x1'. Similarly, the information of time-frequency resource S2' can be represented by the number of time-domain resource z2' and the number of frequency-domain resource x2'. Thus, the mapping relationship w2””’ is used to describe the mapping relationship between the identification information of tag v1 and the numbers of time-domain resource z2' and frequency-domain resource x2'.

[0356] For example, consider a query command q5 broadcast by a reader when tag v1 detects it. Query command q5 includes at least one mapping relationship (e.g., mapping relationship w1""', mapping relationship w2""', etc.), the starting position of time-domain resource set j1, the length of the time-domain resources included in time-domain resource set j1, the interval between two adjacent time-domain resources in time-domain resource set j1, the starting position of frequency-domain resource set J1, the frequency-domain width of the frequency-domain resources included in frequency-domain resource set J1, the interval between two adjacent frequency-domain resources in frequency-domain resource set J1, and the system frame number and time slot number required for synchronization between the reader and the tag. Among these, the mapping relationship w1""' describes the mapping relationship between the identification information of tag v1 and the number of frequency-domain resource x1'.

[0357] After receiving the query command q5 broadcast by the reader, tag v1 can obtain the mapping relationship w1""' corresponding to tag v1, the starting position of time-domain resource set j1, the length of time-domain resources included in time-domain resource set j1, the interval between two adjacent time-domain resources in time-domain resource set j1, the starting position of frequency-domain resource set J1, the frequency-domain width of frequency-domain resources included in frequency-domain resource set J1, the interval between two adjacent frequency-domain resources in frequency-domain resource set J1, and the system frame number and time slot number required for synchronization between the reader and the tag. Then, tag v1 can determine a time slot based on the system frame number and time slot number. Next, tag v1 can determine multiple time-domain resources in that time slot based on the starting position of time-domain resource set j1, the length of time-domain resources included in time-domain resource set j1, and the interval between two adjacent time-domain resources in time-domain resource set j1. It is understood that the multiple time-domain resources included in time-domain resource set j1 can each have their own unique number. Then, label v1 can determine the time domain resource z1' corresponding to label v1 among the multiple time domain resources based on the number of the time domain resource z1' included in the mapping relationship w1'.

[0358] Furthermore, tag v1 can also determine multiple frequency domain resources based on the starting position of frequency domain resource set J1, the frequency domain width of the frequency domain resources included in frequency domain resource set J1, and the interval between two adjacent frequency domain resources in frequency domain resource set J1. Understandably, the multiple frequency domain resources included in frequency domain resource set J1 can each have their own unique number. Then, tag v1 can determine the frequency domain resource x1' corresponding to tag v1 among these multiple frequency domain resources based on the number of the frequency domain resource x1' included in mapping relationship w1”'.

[0359] Step 603e: Tag v1 sends information u5 on resource g5. Accordingly, the reader receives information u5 from tag v1 on resource g5.

[0360] Resource g5 may include time-domain resource z1 and frequency-domain resource x1 corresponding to label v1, or resource g5 may include time-domain resource z1' and frequency-domain resource x1' corresponding to label v1.

[0361] Optionally, resource g5 may also include code field resources. These code field resources are allocated for information exchange between at least one tag reader and the reader. In one example, tag v1 and other tags that meet the above-mentioned conditions (such as tag v2, tag v3, etc.) may share a single code field resource. For example, this single code field resource may be predefined or carried by the reader in the selection instruction p5 or query instruction q5. In another example, each tag is assigned a code field resource. That is, each tag can use its own dedicated code field resource to interact with the reader. For example, code field resource e1”” is assigned to tag v1, code field resource e2”” is assigned to tag v2, and so on. For example, the code field resource corresponding to each tag may be predefined or carried in the selection instruction p5 or query instruction q5. For example, the reader may carry the code field resource corresponding to each tag in the selection instruction p5 or query instruction q5, or the reader may carry the number of the code field resource corresponding to each tag in the selection instruction p5 or query instruction q5.

[0362] In one example, information u5 may include a random number, such as random number y5. This random number can be used for tag v1 authentication. Optionally, the random number can be used for handshake authentication or access authentication between tag v1 and the reader.

[0363] In another example, information u5 may include a 1-bit indication, such as indication o5. This 1-bit indication is used for tag v1 authentication. Optionally, this 1-bit indication can be used for handshake authentication or access authentication between tag v1 and the reader. For example, in some embodiments, information u5 may be a 1-bit indication. Optionally, the 1-bit indication can be used to indicate a random number, or it can be used to indicate other information or data.

[0364] Step 604e: The reader sends response information r5 on resource g5. Accordingly, tag v1 receives response information r5 from the reader on resource g5.

[0365] In one example, let's assume that information u5 includes a random number (e.g., random number y5). After receiving information u5 from tag v1 on resource g5, the reader can obtain the random number y5 from information u5. Then, the reader can send a response message r5 back to tag v1. The response message r5 can include a random number (e.g., random number y5'). After receiving the response message r5 from the reader, tag v1 can obtain the random number y5' from the response message r5. Then, tag v1 can determine whether the random number y5' is the same as the random number y5 previously sent to the reader. If the random number y5' is the same as the random number y5, then tag v1 connects to the reader; this can be understood as a successful handshake between tag v1 and the reader. If the random number y5' is different from the random number y5, then tag v1 does not connect to the reader; this can be understood as a failed handshake between tag v1 and the reader.

[0366] In another example, let's consider information u5 including a 1-bit indication (e.g., indication o5). After receiving information u5 from tag v1 on resource g5, the reader can retrieve the indication o5 from information u5. Then, the reader can send a response r5 back to tag v1. The response r5 can include a 1-bit indication (e.g., indication o5'). After receiving the response r5 from the reader, tag v1 can retrieve the indication o5' from the response r5. Then, tag v1 can determine whether the indication o5' is the same as the indication o5 previously sent to the reader; this can be understood as determining whether the value of the indication o5' is the same as the value of the indication o5 previously sent to the reader. If the indication o5' is the same as the indication o5, tag v1 connects to the reader. If the indication o5' is different from the indication o5, tag v1 does not connect to the reader.

[0367] Optionally, if tag v1 is connected to a reader, this embodiment of the application may perform steps 605e to 606e below. If tag v1 is not connected to a reader, this embodiment of the application does not need to perform steps 605e to 606e below.

[0368] Step 605e: Tag v1 sends its EPC on resource g5. Correspondingly, the reader receives the EPC of tag v1 on resource g5.

[0369] In this embodiment of the application, when the tag v1 is connected to the reader, it can send its own attribute information, such as EPC or other identification information, to the resource g5.

[0370] Step 606e: The reader sends information n5 on resource g5. Correspondingly, tag v1 receives information n5 from the reader on resource g5.

[0371] The implementation process of step 606e can refer to the implementation process of step 606a above, and will not be repeated here.

[0372] As can be seen from steps 601e to 606e above, by flexibly configuring or allocating the starting position and size (including the starting position and length of time-domain resources and the starting position and bandwidth of frequency-domain resources) of different tags, efficient utilization of time-frequency resources can be achieved (which can be understood as high utilization rate of time-frequency resources). This facilitates refined management of time-frequency resources and allows different tags to interact with the reader on their respective corresponding time-frequency resources. This effectively reduces resource conflicts when multiple tags interact with the reader separately, thereby effectively improving the tag identification efficiency of the RFID system. Furthermore, since the starting position and size of the time-frequency resources corresponding to different tags can be flexibly allocated according to actual needs, the configuration of time-frequency resources corresponding to different tags is quite flexible.

[0373] Furthermore, by configuring or assigning shared time-domain resource sets, including the starting position, length, and interval between adjacent time-domain resources, as well as the starting position, frequency-domain width, and interval between adjacent frequency-domain resources, to different tags, it is possible to facilitate the timely and accurate identification of multiple time-domain resources based on these parameters. Furthermore, it is possible to identify the corresponding time-domain resource from among these resources based on its assigned number. Similarly, it is possible to facilitate the timely and accurate identification of multiple frequency-domain resources based on the starting position, length, and interval between adjacent frequency-domain resources, as well as the starting position, frequency-domain width, and interval between adjacent frequency-domain resources, as well as the frequency-domain width ... This allows different tags to interact with the reader on their respective time-frequency resources (including time-domain and frequency-domain resources), which helps to effectively reduce resource conflicts when multiple tags interact with the reader separately, thereby effectively improving the tag identification efficiency of the RFID system.

[0374] It is understood that, in order to achieve the functions in the above embodiments, the first device and the second device include hardware structures and / or software modules corresponding to perform each function. Those skilled in the art should readily recognize that, based on the units and method steps of the various examples described in conjunction with the embodiments disclosed in this application, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application scenario and design constraints of the technical solution.

[0375] Figures 7 and 8 are schematic diagrams illustrating possible communication devices provided in embodiments of this application. These communication devices can be used to implement the functions of the first or second device in the above method embodiments, and thus can also achieve the beneficial effects of the above method embodiments. In the embodiments of this application, the communication device can be the first or second device, or it can be a module (such as a chip) applied to the first or second device.

[0376] The communication device 700 shown in Figure 7 includes a transceiver unit 710 (or a communication module, for sending and receiving data). Optionally, the communication device 700 shown in Figure 7 may further include a processing unit 720 (or a processing module). The communication device 700 can be used to implement the functions of the first or second device in the method embodiments shown in Figures 3, 5a, 5b, 6a, 6b, 6c, 6d, and 6e. For example, the transceiver unit 710 can perform the receiving and sending actions performed by the first or second device in the above method embodiments. The processing unit 720 can perform other actions besides the sending and receiving actions performed by the first or second device in the above method embodiments.

[0377] When the communication device 700 is used to implement the functions of the first device in the method embodiments shown in Figures 3, 6a, 6b, 6c, 6d, and 6e: the transceiver unit 710 is used to send first information. The first information may include a mapping relationship describing the mapping relationship between the identification information of the second device and the resources corresponding to the second device. The transceiver unit 710 is also used to receive attribute information of the second device on the resources corresponding to the second device. The processing unit 720 is used to perform corresponding processing operations, such as calling the transceiver unit 710 to execute the transmission and reception actions required by the first device in the above method embodiments, or determining the mapping relationship between the identification information of the second device and the resources corresponding to the second device, etc.

[0378] When the communication device 700 is used to implement the function of the second device in the method embodiments shown in Figures 3, 6a, 6b, 6c, 6d, and 6e: the transceiver unit 710 is used to receive first information. The first information may include a mapping relationship describing the mapping relationship between the identification information of the second device and the resources corresponding to the second device. The transceiver unit 710 is also used to send attribute information of the second device on the resources corresponding to the second device when the second device accesses the first device. The processing unit 720 is used to perform corresponding processing operations, such as calling the transceiver unit 710 to execute the transmission and reception actions required by the second device in the above method embodiments, or determining the resources corresponding to the second device according to the mapping relationship, etc.

[0379] When the communication device 700 is used to implement the function of the first device in the method embodiment shown in FIG5a above: the transceiver unit 710 is used to receive second information from the second device on the resources corresponding to the second device. The second information may include a random number. The random number can be used for authentication of the second device. The transceiver unit 710 is also used to send third information to the second device on the resources corresponding to the second device. The third information may include a random number.

[0380] When the communication device 700 is used to implement the function of the second device in the method embodiment shown in FIG5a: the transceiver unit 710 is used to send second information to the first device on the resources corresponding to the second device. The second information may include a random number. The random number is used for authentication of the second device. The transceiver unit 710 is also used to receive third information from the first device on the resources corresponding to the second device. The third information may include a random number.

[0381] When the communication device 700 is used to implement the function of the first device in the method embodiment shown in FIG5b: the transceiver unit 710 is used to receive fourth information from the second device on the resources corresponding to the second device. The fourth information may include indication information. The indication information can be used for authentication of the second device. The transceiver unit 710 is also used to send fifth information to the second device on the resources corresponding to the second device. The fifth information may include indication information.

[0382] When the communication device 700 is used to implement the function of the second device in the method embodiment shown in FIG5b: the transceiver unit 710 is used to send fourth information to the first device on the resources corresponding to the second device. The fourth information may include indication information. The indication information can be used for authentication of the second device. The transceiver unit 710 is also used to receive fifth information from the first device on the resources corresponding to the second device. The fifth information may include indication information.

[0383] For a more detailed description of the processing unit 720 and the transceiver unit 710, please refer to the relevant description in the method embodiment shown in Figure 3 above, which will not be repeated here.

[0384] It should be understood that the transceiver unit 710 in the embodiments of this application can be implemented by a transceiver or transceiver-related circuit components, and the processing unit 720 can be implemented by a processor or processor-related circuit components.

[0385] It should be noted that the module division in the embodiments of this application is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, exist as separate physical entities, or have two or more units integrated into one unit. The integrated units described above can be implemented in hardware or as software functional units.

[0386] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part 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, or a server, etc.) or processor to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as a USB flash drive, a portable hard drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0387] The communication device 800 shown in Figure 8 includes a processor 810. Optionally, the communication device 800 may also include at least one of a memory 820, a transceiver 830, and an antenna 840.

[0388] The transceiver 830 can be a transceiver unit, transceiver, or transceiver circuit, etc., used to implement transceiver functions. The transceiver 830 can include a receiver and a transmitter. The receiver can be a receiver or receiving circuit, etc., used to implement the receiving function; the transmitter can be a transmitter or transmitting circuit, etc., used to implement the transmitting function.

[0389] The memory 820 may store a computer program, software code, or instructions 850, which may also be referred to as firmware. The processor 810 can control the communication device 800 by running its own computer program, software code, or instructions 860, or by calling the computer program, software code, or instructions 850 stored in the memory 820, to implement the embodiments described above. The processor 810 may be a central processing unit (CPU), and the memory 820 may be a read-only memory (ROM) or a random access memory (RAM).

[0390] The processor 810 and transceiver 830 described in this application can be disposed on an integrated circuit (IC), analog IC, radio frequency integrated circuit (RFIC), mixed signal IC, application specific integrated circuit (ASIC), printed circuit board (PCB), or electronic device.

[0391] The modules included in the communication device 800 are merely illustrative examples, and this application does not impose any limitations on them.

[0392] When the communication device 800 is used to implement the above method embodiment, the processor 810 can implement the function of the processing unit 720, and the transceiver 830 can implement the function of the transceiver unit 710.

[0393] Based on the same concept, embodiments of this application also provide a possible communication system. This communication system may include a first device and a second device. The first device can be used to implement the technical solutions related to the first device in the above embodiments, and the second device can be used to implement the technical solutions related to the second device in the above embodiments.

[0394] Based on the same concept, this application also provides a computer program product, which includes a computer program or instructions that, when run on a communication device (or computer), cause the communication device (or computer) to perform the methods provided in the above embodiments.

[0395] Based on the same concept, embodiments of this application also provide a computer-readable storage medium storing a computer program or instructions that, when executed by a communication device (or computer), cause the communication device (or computer) to perform the methods provided in the above embodiments.

[0396] The storage medium can be any available medium that a computer can access. For example, but not limited to, a computer-readable medium can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer.

[0397] Based on the same concept, embodiments of this application also provide a chip, which may include a processor and a memory (or the chip may be coupled to the memory). The processor executes program instructions in the memory to cause the chip to perform the methods provided in the above embodiments. Here, "coupling" means that two components are directly or indirectly connected to each other, such as coupling can refer to an electrical connection between two components.

[0398] Based on the same concept, embodiments of this application also provide a chip system, which includes a processor for supporting a computer device in implementing the functions involved in the communication device in the above embodiments. In one possible implementation, the chip system further includes a memory for storing necessary programs and data of the computer device. This chip system may be composed of chips or may include chips and other discrete components.

[0399] It is understood that the processor in the embodiments of this application can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor can be a microprocessor or any conventional processor.

[0400] The method steps in this application embodiment can be implemented in hardware or by a processor executing software instructions. The software instructions can consist of corresponding software modules, which can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disks, portable hard disks, compact disc read-only memory (CD-ROM), or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Alternatively, the ASIC can reside in a communication device. Of course, the processor and storage medium can also exist as discrete components in the communication device.

[0401] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer programs or instructions. A computer program is a set of instructions that directs each step of an action of an electronic computer or other device with message processing capabilities. It is typically written in a programming language and runs on a target architecture. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of this application are performed, in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video optical disc; or it can be a semiconductor medium, such as a solid-state drive. The computer-readable storage medium can be volatile or non-volatile, or it can include both types of storage media.

[0402] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0403] In this application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. In the textual description of this application, the character " / " generally indicates an "or" relationship between the preceding and following related objects; in the formulas of this application, the character " / " indicates a "division" relationship between the preceding and following related objects.

[0404] It is understood that the various numerical designations used in the embodiments of this application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. The order of the process numbers described above does not imply the order of execution; the execution order of each process should be determined by its function and internal logic.

Claims

1. A communication method characterized by comprising: Applied to a first device, the method includes: Send first information, the first information including a mapping relationship, the mapping relationship describing the mapping relationship between the identification information of the second device and the resources corresponding to the second device; Receive the attribute information of the second device on the resource.

2. The method of claim 1, wherein, The resources include at least one of the following: time-domain resources, frequency-domain resources, and code-domain resources.

3. The method of claim 2, wherein, The mapping relationship describes the mapping relationship between the identification information of the second device and the resources corresponding to the second device, including: The mapping relationship describes the mapping relationship between the identification information of the second device and the information of the time-domain resources corresponding to the second device; The mapping relationship describes the mapping relationship between the identification information of the second device and the information of the frequency domain resources corresponding to the second device; The mapping relationship describes the mapping relationship between the identification information of the second device and the information of the code field resource corresponding to the second device; or... The mapping relationship describes the mapping relationship between the identification information of the second device and the information of the time and frequency resources corresponding to the second device.

4. The method of claim 3, wherein, The information of the time-domain resource includes the start position and length of the time-domain resource; or, The information of the time-domain resource includes the number of the time-domain resource.

5. The method of claim 4, wherein, The first information also includes the starting position of the time-domain resource set, the length of the time-domain resource, and the interval between two adjacent time-domain resources in the time-domain resource set, wherein the time-domain resource set includes multiple time-domain resources.

6. The method of claim 3, wherein, The information of the frequency domain resource includes the starting position and frequency domain width of the frequency domain resource; or, The information of the frequency domain resource includes the number of the frequency domain resource.

7. The method of claim 6, wherein, The first information also includes the starting position of the frequency domain resource set, the frequency domain width of the frequency domain resource, and the interval between two adjacent frequency domain resources in the frequency domain resource set, wherein the frequency domain resource set includes multiple frequency domain resources.

8. The method of claim 3, wherein, The information of the time-frequency resource includes the start position and length of the time-domain resource, and the start position and frequency width of the frequency-domain resource; or, The information of the time-frequency resources includes the number of the time-domain resources and the number of the frequency-domain resources.

9. The method of claim 8, wherein, The first information also includes the starting position of the time-domain resource set, the length of the time-domain resource, the interval between two adjacent time-domain resources in the time-domain resource set, the starting position of the frequency-domain resource set, the frequency-domain width of the frequency-domain resource, and the interval between two adjacent frequency-domain resources in the frequency-domain resource set, wherein the time-domain resource set includes multiple time-domain resources and the frequency-domain resource set includes multiple frequency-domain resources.

10. The method of any one of claims 1-9, wherein, The information of the code domain resource includes the code domain resource number.

11. The method of any one of claims 1-10, wherein, The first information also includes the system frame number and time slot number required for the first device and the second device to synchronize.

12. The method of any one of claims 1-11, wherein, The method further includes: Receive second information from the second device on the resource, the second information including a random number used for authentication of the second device; Send a third message to the second device on the resource, the third message including the random number.

13. The method of any one of claims 1-11, wherein, The method further includes: The resource receives fourth information from the second device, the fourth information including indication information used for authentication of the second device; A fifth message is sent to the second device on the resource, the fifth message including the indication information.

14. The method of claim 13, wherein, The indication information is a 1-bit indication information.

15. A method of communication, comprising: Applied to a second device, the method includes: Receive first information, the first information including a mapping relationship, the mapping relationship describing the mapping relationship between the identification information of the second device and the resources corresponding to the second device; When the second device is connected to the first device, the attribute information of the second device is sent on the resource.

16. The method of claim 15, wherein, The resources include at least one of the following: time-domain resources, frequency-domain resources, and code-domain resources.

17. The method of claim 16, wherein, The mapping relationship describes the mapping relationship between the identification information of the second device and the resources corresponding to the second device, including: The mapping relationship describes the mapping relationship between the identification information of the second device and the information of the time-domain resources corresponding to the second device; The mapping relationship describes the mapping relationship between the identification information of the second device and the information of the frequency domain resources corresponding to the second device; The mapping relationship describes the mapping relationship between the identification information of the second device and the information of the code field resource corresponding to the second device; or... The mapping relationship describes the mapping relationship between the identification information of the second device and the information of the time and frequency resources corresponding to the second device.

18. The method of claim 17, wherein, The information of the time-domain resource includes the start position and length of the time-domain resource; or, The information of the time-domain resource includes the number of the time-domain resource.

19. The method of claim 18, wherein, The first information also includes the system frame number and time slot number required for the first device and the second device to synchronize; The method further includes: The first time slot is determined based on the system frame number and the time slot number; Based on the starting position and length of the time-domain resource, the time-domain resource corresponding to the second device is determined in the first time slot.

20. The method of claim 18, wherein, The first information also includes the starting position of the time-domain resource set, the length of the time-domain resource, the interval between two adjacent time-domain resources in the time-domain resource set, and the system frame number and time slot number required for the first device and the second device to synchronize. The time-domain resource set includes multiple time-domain resources. The method further includes: The second time slot is determined based on the system frame number and the time slot number; Based on the starting position of the time-domain resource set, the length of the time-domain resource, and the interval between two adjacent time-domain resources in the time-domain resource set, a plurality of time-domain resources are determined in the second time slot; Based on the time domain resource number, the time domain resource corresponding to the second device is determined from among the multiple time domain resources.

21. The method of claim 17, wherein, The information of the frequency domain resource includes the starting position and frequency domain width of the frequency domain resource; or, The information of the frequency domain resource includes the number of the frequency domain resource.

22. The method of claim 21, wherein, The method further includes: The frequency domain resources corresponding to the second device are determined based on the starting position and frequency domain width of the frequency domain resources.

23. The method of claim 21, wherein, The first information also includes the starting position of the frequency domain resource set, the frequency domain width of the frequency domain resource, and the interval between two adjacent frequency domain resources in the frequency domain resource set, wherein the frequency domain resource set includes multiple frequency domain resources; The method further includes: Based on the starting position of the frequency domain resource set, the frequency domain width of the frequency domain resource, and the interval between two adjacent frequency domain resources in the frequency domain resource set, a plurality of frequency domain resources are determined; Based on the number of the frequency domain resource, the frequency domain resource corresponding to the second device is determined from among the multiple frequency domain resources.

24. The method of claim 17, wherein, The information of the time-frequency resource includes the start position and length of the time-domain resource, and the start position and frequency width of the frequency-domain resource; or, The information of the time-frequency resources includes the number of the time-domain resources and the number of the frequency-domain resources.

25. The method of claim 24, wherein, The first information also includes the system frame number and time slot number required for the first device and the second device to synchronize; The method further includes: The third time slot is determined based on the system frame number and the time slot number; the time domain resource corresponding to the second device is determined in the third time slot based on the start position and length of the time domain resource. The frequency domain resources corresponding to the second device are determined based on the starting position and frequency domain width of the frequency domain resources.

26. The method of claim 24, wherein, The first information also includes the starting position of the time-domain resource set, the length of the time-domain resource, the interval between two adjacent time-domain resources in the time-domain resource set, the system frame number and time slot number required for the first device and the second device to synchronize, the starting position of the frequency-domain resource set, the frequency-domain width of the frequency-domain resource, and the interval between two adjacent frequency-domain resources in the frequency-domain resource set. The time-domain resource set includes multiple time-domain resources, and the frequency-domain resource set includes multiple frequency-domain resources. The method further includes: Based on the system frame number and the time slot number, a fourth time slot is determined; based on the starting position of the time domain resource set, the length of the time domain resource, and the interval between two adjacent time domain resources in the time domain resource set, multiple time domain resources are determined in the fourth time slot; based on the number of the time domain resource, the time domain resource corresponding to the second device is determined from among the multiple time domain resources. Based on the starting position of the frequency domain resource set, the frequency domain width of the frequency domain resource, and the interval between two adjacent frequency domain resources in the frequency domain resource set, a plurality of frequency domain resources are determined; based on the number of the frequency domain resource, the frequency domain resource corresponding to the second device is determined from the plurality of frequency domain resources.

27. The method of any one of claims 17-26, wherein, The information of the code domain resource includes the code domain resource number.

28. The method of claim 27, wherein, The method further includes: Based on the code domain resource number, the code domain resource corresponding to the second device is determined from a preset code domain resource set.

29. The method of any one of claims 15-28, wherein, The method further includes: Send second information to the first device on the resource, the second information including a random number, the random number being used for authentication of the second device; The third information, including the random number, is received from the first device on the resource.

30. The method of any one of claims 15-28, wherein, The method further includes: Send a fourth message to the first device on the resource, the second message including indication information used for authentication of the second device; The fifth information received from the first device on the resource includes the indication information.

31. The method of claim 30, wherein, The indication information is a 1-bit indication information.

32. A communications device, characterized by It includes modules or units for performing the method as described in any one of claims 1-14, or modules or units for performing the method as described in any one of claims 15-31.

33. A communications device, characterized by Including processor and memory; The memory is used to store computer programs; The processor is configured to execute a computer program in the memory such that the method as described in any one of claims 1-14 or the method as described in any one of claims 15-31 is implemented.

34. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program or instructions that, when executed by a communication device, cause the method as described in any one of claims 1-14 or the method as described in any one of claims 15-31 to be implemented.

35. A computer program product, characterised in that, The computer program product includes a computer program or instructions that, when executed on a communication device, cause the method as described in any one of claims 1-14 or the method as described in any one of claims 15-31 to be implemented.

Images