Communication method and apparatus

Abstract

Provided in the embodiments of the present application are a communication method and apparatus. The method comprises: a first terminal device receiving a first message from a first device, wherein the first message is used for querying permanent identification information of a terminal device, and the first message comprises system information for synchronization and information of a first resource set; and on the basis of a first resource in the first resource set, the first terminal device sending a second message to the first device, wherein the second message is used for requesting access. In the method, a first device can allocate available resources for access of a terminal device, such that the terminal device can promptly use the corresponding resources to gain access, thereby avoiding waiting for access in a time-division multiple access manner, and thus effectively improving the efficiency of terminal device identification.

Description

A communication method and apparatus

[0001] Cross-reference of related applications

[0002] This application claims priority to Chinese Patent Application No. 202411458791.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 wireless communication technology, and in particular to a communication method and apparatus. Background Technology

[0004] Passive Internet of Things (AIoT) is a type of Internet of Things (IoT) technology. Its core characteristic is that terminal nodes / devices do not require external power cords or built-in batteries. Instead, they collect weak energy from the environment, such as radio wave energy, heat energy, vibration energy, and mechanical energy, and convert this energy into electrical energy to drive the device's circuitry. This enables functions such as data collection, transmission, and distributed computing. Passive IoT technology is of great significance for improving the energy efficiency and data transmission efficiency of IoT devices.

[0005] Radio Frequency Identification (RFID) technology, as a passive Internet of Things (IoT) technology, is widely used in various scenarios such as inventory management, logistics tracking, and security authentication. RFID technology is a non-contact automatic identification technology that uses wireless radio frequency for non-contact two-way data communication to read and write electronic tags or RFID cards, thereby completing data communication between the reader and the tag and achieving the purpose of identifying the target and exchanging data.

[0006] Current RFID technology typically employs Time Division Multiple Access (TDMA) for RFID tag inventory processes. This involves the reader using the Additive Link On-line Hawaii (ALOHA) protocol to identify each tag individually and retrieve information or data from its storage area. However, when processing large numbers of tags, this method of tag-by-tag identification via ALOHA leads to severe conflicts, significantly extending inventory time. Furthermore, each tag response requires reader confirmation, increasing the reader's processing load and limiting the overall system throughput, thus severely impacting inventory efficiency. Therefore, improving the efficiency of tag identification / inventory is a pressing issue that needs to be addressed. Summary of the Invention

[0007] This application proposes a communication method and apparatus that can effectively improve the efficiency of identifying / inventorying tags (terminal devices).

[0008] In a first aspect, embodiments of this application provide a communication method. This method can be applied to a first terminal device, or a component of the first terminal device (e.g., a processor, chip, or chip system), or a logical node, logical module, or software capable of implementing all or part of the functions of the first terminal device, or a device compatible with the first terminal device. Taking the application of this method to a first terminal device as an example, the method includes: the first terminal device receiving a first message from a first device, the first message being used to query permanent identification information of the terminal device, the first message including system information for synchronization and information of a first resource set; the first terminal device sending a second message to the first device based on a first resource in the first resource set, the second message being used to request access.

[0009] In this application embodiment, the terminal device (including the first terminal device) can be, but is not limited to, an IoT terminal device, i.e., a novel low-power, low-cost terminal device. The IoT terminal can include passive terminal devices, semi-passive terminal devices, energy storage passive terminal devices, energy storage terminal devices, energy storage semi-passive terminal devices, active terminal devices, etc. In this application embodiment, electronic tags or labels (e.g., passive IoT tags, AIoT tags) can also be used to represent the IoT terminal device. This application embodiment does not limit the specific form of the IoT terminal device. As mentioned above, the first device can be a device that supports terminal device access, such as an access network device or a reader / writer. The first device can also be a relay device with access and / or forwarding functions.

[0010] In this application, the first device can allocate available resources for the access of the terminal device, so that the terminal device can use the corresponding resources to access in a timely manner, thereby avoiding waiting for access based on time division multiplexing and thus effectively improving the efficiency of identifying the terminal device.

[0011] As mentioned above, time-division multiplexing can refer to the transmission of different signals through the same IoT connection at different time periods. The disadvantage of this method is, but is not limited to, the relatively large time delay it generates.

[0012] In conjunction with the first aspect, in one possible implementation, the system information includes radio frame information and / or time slot information, and the method further includes: the first terminal device performing synchronization processing with the first device based on the radio frame information and / or time slot information.

[0013] This implementation method ensures that the first terminal device and the first device are kept in the same time domain (synchronized), thereby guaranteeing the accuracy and efficiency of communication between the first terminal device and the first device.

[0014] In conjunction with the first aspect, in one possible implementation, the first resource set includes multiple resources, including time-domain resources and / or frequency-domain resources; the method further includes: the first terminal device selecting a first resource from the multiple resources.

[0015] Through this implementation, the first terminal device can select resources from the first resource set and communicate with the first device.

[0016] In conjunction with the first aspect, in one possible implementation, the second message includes first information for temporarily identifying the first terminal device, and the method further includes the following:

[0017] The first terminal device receives a third message from the first device; the third message is used to confirm acceptance of the request of the second message, and the third message includes first information and second information, the second information is used to indicate the resource corresponding to the first terminal device, and the first information is associated with the resource corresponding to the first terminal device; then, on the resource corresponding to the first terminal device, the permanent identification information of the first terminal device is sent to the first device.

[0018] Through this implementation, the first terminal device can accurately obtain its own corresponding resources and use those resources to send its own permanent identification information to the first device.

[0019] In conjunction with the first aspect, in another possible implementation, the second message includes first information for temporarily identifying the first terminal device, and the method further includes the following:

[0020] The first terminal device receives a third message from the first device; the third message is used to confirm acceptance of the request of the second message, the third message includes first information and second information, the second information is used to indicate the second resource corresponding to the first terminal device, the first information is associated with the second resource, the second resource is different from the first resource; then, on the second resource, the permanent identification information of the first terminal device is sent to the first device.

[0021] In the above, the second resource belongs to the second resource set, and the first resource set may include the second resource set.

[0022] Through this implementation, the first terminal device can accurately obtain its corresponding second resource. The second resource can be included in the first resource set, and the second resource is different from the first resource. Thus, the first terminal device can effectively and timely send its own permanent identification information to the first device using the second resource.

[0023] If the resource corresponding to the first terminal device (or the second resource corresponding to the first terminal device) is a time-domain resource, then the second information can be the information of the time-domain resource corresponding to the first terminal device, which includes, but is not limited to, one or more of the following:

[0024] (1) Identification information of time-domain resources; (2) Time-domain parameters.

[0025] If the resource corresponding to the first terminal device (or the second resource corresponding to the first terminal device) is a frequency domain resource, then the second information can be the information of the frequency domain resource corresponding to the first terminal device, which includes, but is not limited to, one or more of the following:

[0026] (1) Identification information of frequency domain resources; (2) Frequency shift parameters.

[0027] If the resources corresponding to the first terminal device (or the second resources corresponding to the first terminal device) include time-domain resources and frequency-domain resources, then the second information includes information about the time-domain resources and information about the frequency-domain resources corresponding to the first terminal device.

[0028] The information for this time-domain resource includes, but is not limited to, one or more of the following:

[0029] (1) Identification information of time-domain resources; (2) Time-domain parameters;

[0030] The information for this frequency domain resource includes, but is not limited to, one or more of the following:

[0031] (1) Identification information of frequency domain resources; (2) Frequency shift parameters.

[0032] For example, if the time domain resource corresponding to the first terminal device is the first subframe, then the identification information of the time domain resource corresponding to the first terminal device can be the frame number, number, or index of the first subframe, etc. If the frequency domain resource corresponding to the first terminal device is the first frequency band, then the identification information of the frequency domain resource corresponding to the first terminal device can be the frequency band number (such as the frequency band number specified in the protocol), number, or index of the first frequency band, etc.

[0033] In one possible implementation, the aforementioned time-domain parameter can be the ratio of time-domain resources to time-domain resource units, or the time-domain parameter can be the total number of time-domain resource units contained in the time-domain resources. This implementation minimizes the overhead of information used to indicate the corresponding time-domain resources of the first terminal device.

[0034] For example, suppose the first device allocates a corresponding time-domain resource, the first subframe, to the first terminal device. The first subframe includes M time slots, where M is a positive integer, and one time slot is one time-domain resource unit. The information of the time-domain resource corresponding to the first terminal device (i.e., the second information) is a time-domain parameter, which is a value M. The value M represents the ratio between the total number of time slots in the first subframe and the number of one time slot unit, or it represents the number of time slots contained in the first subframe.

[0035] In one possible implementation, the frequency shift parameter can be an offset of the frequency domain resource, or the frequency shift parameter can include a frequency shift unit and a frequency shift factor. This implementation minimizes the overhead of information used to indicate the corresponding frequency domain resource of the first terminal device.

[0036] For example, suppose the first device allocates a corresponding frequency domain resource, namely a first frequency band, to the first terminal device. The offset of the first frequency band is N, and the frequency shift unit is set to n, where N and n are positive integers, and N is greater than or equal to n. The information of the frequency domain resource corresponding to the first terminal device (i.e., the second information) is the frequency shift parameter. This frequency shift parameter can be the offset N corresponding to the first frequency band, or it can include the value n (frequency shift unit) and the value N / n (frequency shift multiple), where " / " is a division sign.

[0037] In one possible implementation, the first terminal device sends its permanent identification information on the corresponding resource. Specifically, this may include the first terminal device sending its permanent identification information to another device on the corresponding resource using Orthogonal Frequency Division Multiplexing (OFDM). This implementation can effectively improve transmission efficiency and reliability (as well as anti-interference capability).

[0038] In conjunction with the first aspect, in one possible implementation, the method further includes: the first terminal device receiving a fourth message from the first device, the fourth message indicating a preset condition; and determining that the preset condition is met. Optionally, this implementation can be performed before the first terminal device receives the first message from the first device. This implementation can trigger the first terminal device to execute subsequent steps.

[0039] Secondly, embodiments of this application provide a communication method. This method can be applied to a first device, or a component of the first device (e.g., a processor, chip, or chip system), or a logical node, logical module, or software capable of implementing all or part of the functions of the first device, or a device used in conjunction with the first device. Taking the application of this method to a first device as an example, the method includes: the first device sending a first message, the first message being used to query permanent identification information of a terminal device; the first message including system information for synchronization and information of a first resource set; the first device receiving a second message sent by the first terminal device based on a first resource in the first resource set; the second message being used to request access. In one possible implementation, the system information includes radio frame information and / or time slot information.

[0040] In this application embodiment, the terminal device (including the first terminal device) can be, but is not limited to, an IoT terminal device, i.e., a novel low-power, low-cost terminal device. The IoT terminal can include passive terminal devices, semi-passive terminal devices, energy storage passive terminal devices, energy storage terminal devices, energy storage semi-passive terminal devices, active terminal devices, etc. In this application embodiment, electronic tags or labels (e.g., passive IoT tags, AIoT tags) can also be used to represent the IoT terminal device. This application embodiment does not limit the specific form of the IoT terminal device. As mentioned above, the first device can be a device that supports terminal device access, such as an access network device or a reader / writer. The first device can also be a relay device with access and / or forwarding functions.

[0041] In this application, the first device can allocate available resources for the access of the terminal device, so that the terminal device can use the corresponding resources to access in a timely manner, thereby avoiding waiting for access based on time division multiplexing and thus effectively improving the efficiency of identifying the terminal device.

[0042] In conjunction with the second aspect, in one possible implementation, the second message includes first information for temporarily identifying the first terminal device; the method further includes: the first device sending a third message to the first terminal device; the third message is used to confirm acceptance of the request for the second message, the third message includes the first information and the second information, the second information is used to indicate the resource corresponding to the first terminal device, and the first information is associated with the resource corresponding to the first terminal device; then the first device receives the permanent identification information of the first terminal device on the resource corresponding to the first terminal device.

[0043] In conjunction with the second aspect, in another possible implementation, the method further includes: the first device allocating a corresponding second resource to the first terminal device based on the second resource set, wherein the second resource is different from the first resource. In one possible implementation, the first resource set includes the second resource set.

[0044] Furthermore, the method also includes: the first device sending a third message to the first terminal device; the third message is used to confirm acceptance of the request of the second message, the third message includes first information and second information, the second information is used to indicate the second resource corresponding to the first terminal device, and the first information is associated with the second resource; the first device receives the permanent identification information of the first terminal device on the second resource.

[0045] If the resource corresponding to the first terminal device (or the second resource corresponding to the first terminal device) is a time-domain resource, then the second information can be the information of the time-domain resource corresponding to the first terminal device. The information of the time-domain resource may include, but is not limited to, one or more of the following:

[0046] (1) Identification information of time-domain resources; (2) Time-domain parameters.

[0047] If the resource corresponding to the first terminal device (or the second resource corresponding to the first terminal device) is a frequency domain resource, then the second information can be the information of the frequency domain resource corresponding to the first terminal device. The information of the frequency domain resource may include, but is not limited to, one or more of the following:

[0048] (1) Identification information of frequency domain resources; (2) Frequency shift parameters.

[0049] If the resources corresponding to the first terminal device (or the second resources corresponding to the first terminal device) include time-domain resources and frequency-domain resources, then the second information may include information about the time-domain resources and information about the frequency-domain resources corresponding to the first terminal device.

[0050] The information of the time-domain resource may be, but is not limited to, the identification information and / or time-domain parameters of the time-domain resource, and the information of the frequency-domain resource may be, but is not limited to, the identification information and / or frequency-shifting parameters of the frequency-domain resource.

[0051] In one possible implementation, the aforementioned time-domain parameter can be the ratio of time-domain resources to time-domain resource units, or the time-domain parameter can be the total number of time-domain resource units contained in the time-domain resources.

[0052] For example, suppose the first device allocates a corresponding time-domain resource, the first subframe, to the first terminal device. The first subframe includes M time slots, where M is a positive integer, and one time slot is one time-domain resource unit. The information of the time-domain resource corresponding to the first terminal device (i.e., the second information) is a time-domain parameter, which is a value M. The value M represents the ratio between the total number of time slots in the first subframe and the number of one time slot unit, or it represents the number of time slots contained in the first subframe.

[0053] In one possible implementation, the frequency shift parameter can be the offset of a frequency domain resource, or the frequency shift parameter can include a frequency shift unit and a frequency shift factor.

[0054] For example, suppose the first device allocates a corresponding frequency domain resource, namely a first frequency band, to the first terminal device. The offset of the first frequency band is N, and the frequency shift unit is set to n, where N and n are positive integers, and N is greater than or equal to n. The information of the frequency domain resource corresponding to the first terminal device (i.e., the second information) is the frequency shift parameter. This frequency shift parameter can be the offset N corresponding to the first frequency band, or it can include the value n (frequency shift unit) and the value N / n (frequency shift multiple), where " / " is a division sign.

[0055] In one possible implementation, where the resources corresponding to the first terminal device and the second terminal device each include frequency domain resources, the frequency domain resources corresponding to the first terminal device and the frequency domain resources corresponding to the second terminal device conform to a subcarrier orthogonal relationship. Here, the second terminal device can refer to any terminal device other than the first terminal device.

[0056] This implementation method avoids interference between multiple terminal devices during transmission, thereby effectively improving spectrum utilization and system performance.

[0057] In conjunction with the second aspect, in one possible implementation, the first device sending the first message includes: sending the first message according to a preset period. For example, the first device may send the first message in a broadcast manner according to the preset period.

[0058] In conjunction with the second aspect, in one possible implementation, the method further includes: the first device sending a fourth message, the fourth message indicating a preset condition. For example, the first device may send the fourth message in a broadcast manner.

[0059] Thirdly, this application also provides a communication device, which is a first terminal device or a chip corresponding to the first terminal device. The communication device has the function of implementing the first aspect and any of its possible implementations. The communication device can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions.

[0060] In one possible design, the communication device includes a processor configured to support the communication device in performing corresponding functions of the first terminal device in the method described above. The communication device may also include a memory coupled to the processor, which stores necessary program instructions and data for the communication device. Optionally, the communication device further includes interface circuitry for supporting communication between the communication device and other communication devices, such as the transmission and reception of data or signals. Exemplarily, the communication interface may be a transceiver, circuit, bus, module, or other type of communication interface.

[0061] In one possible design, the communication device includes corresponding functional modules, each used to implement the steps in the above method. The functions can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.

[0062] In one possible design, the communication device includes a processing unit and a communication unit, which can perform the corresponding functions in the above method examples, as described in the method provided in the first aspect, and will not be repeated here.

[0063] Fourthly, this application also provides a communication device, which is a first device or a chip corresponding to the first device. The communication device has the function of implementing the second aspect described above and any of its possible implementations. The communication device can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions.

[0064] In one possible design, the communication device includes a processor configured to support the communication device in performing corresponding functions of the first device in the method described above. The communication device may also include a memory coupled to the processor, which stores necessary program instructions and data for the communication device. Optionally, the communication device further includes interface circuitry for supporting communication between the communication device and other communication devices, such as the transmission and reception of data or signals. Exemplarily, the communication interface may be a transceiver, circuit, bus, module, or other type of communication interface.

[0065] In one possible design, the communication device includes corresponding functional modules, each used to implement the steps in the above method. The functions can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.

[0066] In one possible design, the communication device includes a processing unit and a communication unit, which can perform the corresponding functions in the above method examples, as described in the method provided in the second aspect, and will not be repeated here.

[0067] Fifthly, a communication device is provided, including a processor and an interface circuit. The interface circuit is used to receive signals from other communication devices outside the communication device and transmit them to the processor, or to send signals from the processor to other communication devices outside the communication device. The processor is used to implement the methods of the first aspect and any possible implementation thereof through logic circuits or execution code instructions.

[0068] In a sixth aspect, a communication device is provided, including a processor and an interface circuit. The interface circuit is used to receive signals from other communication devices outside the communication device and transmit them to the processor, or to send signals from the processor to other communication devices outside the communication device. The processor is used to implement the methods in the second aspect and any of the possible implementations thereof through logic circuits or execution code instructions.

[0069] In a seventh aspect, a computer-readable storage medium is provided, which stores a computer program or instructions that, when executed by a processor, implement the methods of any one of the first and second aspects and any possible implementation thereof.

[0070] Eighthly, a computer program product storing instructions is provided, which, when executed by a processor, implement the methods of the first and second aspects and any possible implementation thereof.

[0071] A ninth aspect provides a chip system including a processor and potentially a memory for implementing the methods of the first and second aspects and any possible implementation thereof. The chip system may be composed of chips or may include chips and other discrete devices.

[0072] In a tenth aspect, a communication system is provided, the communication system comprising the first terminal device described in the first aspect and the first device described in the second aspect.

[0073] It should be noted that the technical effects that can be achieved by any of the third to tenth aspects or any of the third to tenth aspects can be referred to the description of the technical effects that can be achieved by any of the first and second aspects or any of the first and second aspects, which will not be repeated here. Attached Figure Description

[0074] Figure 1 is a schematic diagram of tag reading and writing in a passive or semi-passive Internet of Things (IoT) system.

[0075] Figure 2 is a schematic diagram of a reader performing an inventory of tags (such as AIoT tags);

[0076] Figure 3 is a schematic diagram of a communication system that can be applied to an embodiment of this application;

[0077] Figure 4 is a flowchart illustrating a communication method provided in an embodiment of this application;

[0078] Figure 5 is a schematic flowchart of the method of Embodiment 1 provided in this application;

[0079] Figure 6A is a schematic diagram of the interaction between a reader and a tag 1 in an embodiment of this application;

[0080] Figure 6B is a schematic diagram of the interaction between another reader and tag 1 in an embodiment of this application;

[0081] Figure 6C is a schematic diagram of the interaction between a reader and tag 1 in another embodiment of this application;

[0082] Figure 7 is a schematic flowchart of the method of Embodiment 2 provided in this application;

[0083] Figure 8A is a schematic diagram of the interaction between a reader and a tag 1 in an embodiment of this application;

[0084] Figure 8B is a schematic diagram of the interaction between another reader and tag 1 in an embodiment of this application;

[0085] Figure 8C is a schematic diagram of the interaction between a reader and tag 1 in another embodiment of this application;

[0086] Figure 9 is a schematic flowchart of the method of Embodiment 3 provided in this application;

[0087] Figure 10 is a schematic diagram of the structure of a communication device according to an embodiment of this application;

[0088] Figure 11 is a schematic diagram of another communication device according to an embodiment of this application;

[0089] Figure 12 is a schematic diagram of a chip device structure according to an embodiment of this application. Detailed Implementation

[0090] The scenarios described in this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0091] To better understand the solutions provided in the embodiments of this application, some terms, concepts, or processes involved in the embodiments of this application will be explained below. It should be noted that these explanations are intended to make the embodiments of this application easier to understand and should not be regarded as limiting the scope of protection claimed by this application.

[0092] 1) Time-domain resources: Time-domain resources refer to the resources available in the time domain in a wireless communication system. For example, in 5G communication, time-domain resources can include concepts such as frames, subframes, time slots, and symbols, which can be used to transmit data and signals.

[0093] For example, the base station allocating corresponding time-domain resources to UE1 can be understood as the base station allocating available resources such as frames, subframes, time slots, or symbols to UE1. For instance, if the base station allocates radio frame #1 to UE1, then UE1 can transmit data on radio frame #1.

[0094] 2) Frequency domain resources: Frequency domain resources refer to the resources in the frequency range used to transmit data in a wireless communication system.

[0095] Typically, frequency domain resources can include subcarriers (SC), resource blocks (RB), resource block groups (TBG), resource elements (RE), etc. These resources are allocated and managed in the frequency domain for transmitting data and control signals, etc.

[0096] For example, the base station allocating corresponding frequency domain resources for UE1 can be understood as the base station allocating available subcarriers such as SC, RB, TBG, or RE to UE1. For instance, if the base station allocates RB0 to UE1, then UE1 can transmit data on RB0.

[0097] 3) Time and frequency resources: Time and frequency resources refer to the resources in a wireless communication system that take into account both time and frequency information.

[0098] For example, the base station allocating corresponding time-frequency domain resources to UE1 can be understood as the base station allocating available time-domain resources (such as frames, subframes, time slots, or symbols) and available frequency-domain resources (such as subcarriers SC, RB, TBG, or RE) to UE1.

[0099] It should be noted that in the embodiments of this application, "at least one" refers to one or more, and "more than one" refers to 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. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, a and b, a and c, b and c, or a and b and c, where a, b, and c can be single or multiple.

[0100] Furthermore, unless otherwise stated, the ordinal numbers such as "first," "second," or "1," "2," etc. (except in special cases indicating numerical values) mentioned in the embodiments of this application are used to distinguish multiple objects and are not used to limit the size, content, order, timing, priority, or importance of the multiple objects. For example, "first terminal device" and "second terminal device" are only used to distinguish different terminal devices and do not indicate that the size, priority, or importance of the two terminal devices are different.

[0101] It should be noted that in this application, the terms "exemplary" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner. In the embodiments of this application, "of," "corresponding, relevant," and "corresponding" may sometimes be used interchangeably, and it should be pointed out that their intended meanings are consistent unless their distinction is emphasized.

[0102] The terms "comprising" and "having," and any variations thereof, used in the following description of embodiments of this application are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally include other steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or devices. Furthermore, the term "for indicating" used in the description of embodiments of this application can include both direct and indirect indication. When describing an indication message for indicating A, it may include whether the indication message directly indicates A or indirectly indicates A, but does not necessarily mean that the indication message carries A.

[0103] The preceding text introduced some terms, concepts, or processes involved in the embodiments of this application. The following text introduces the technical background, application scenarios, and devices involved in the embodiments of this application.

[0104] Figure 1 illustrates a schematic diagram of tag reading and writing in a passive or semi-passive Internet of Things (IoT) system, which may include the following steps:

[0105] Passive Internet of Things (AIoT) is a type of Internet of Things (IoT) technology. Its core characteristic is that terminal nodes / devices do not require external power cords or built-in batteries. Instead, they collect weak energy from the environment, such as radio wave energy, heat energy, vibration energy, and mechanical energy, and convert this energy into electrical energy to drive the device's circuitry. This enables functions such as data collection, transmission, and distributed computing. Passive IoT technology is of great significance for improving the energy efficiency and data transmission efficiency of IoT devices.

[0106] Radio Frequency Identification (RFID) technology, as a passive Internet of Things (IoT) technology, is widely used in various scenarios such as inventory management, logistics tracking, and security authentication. RFID technology is a non-contact automatic identification technology that uses wireless radio frequency for non-contact two-way data communication to read and write electronic tags or RFID cards, thereby completing data communication between the reader and the tag and achieving the purpose of identifying the target and exchanging data.

[0107] In current RFID technology, time division multiple access (TDMA) is typically used to perform RFID tag inventory processes. That is, the reader uses the additive link on-line hawaii (ALOHA) protocol to identify tags one by one and then obtain information or data from the tag's storage area.

[0108] Figure 1 illustrates a schematic diagram of passive Internet of Things (IoT) tag reading and writing, specifically including the following steps:

[0109] S101: The AIoT application sends inventory / access rules to the reader.

[0110] Accordingly, the reader receives the inventory / access rule.

[0111] For example, the inventory / access rule could be: to conduct an inventory check every hour, and to obtain information about the storage areas of tag 1, tag 2, and tag 3.

[0112] S102: The reader performs an inventory of the tags (such as AIoT Tags) and obtains the tag identifiers.

[0113] For example, the reader performs an inventory check on the tags according to the received inventory / access rules, such as performing an inventory check on the tags to be accessed once per hour, and obtaining the identifier of the tags to be accessed.

[0114] It should be understood that the process of a reader inventorying tags can be understood as the process by which the reader establishes a connection and interacts with the tags (such as AIoT tags) to obtain information from each other. Typically, each tag has a corresponding identifier, including but not limited to an electronic product code (EPC) and a tag identifier (TID).

[0115] During the inventory process, the tag sends its EPC or TID to the reader, so that the reader can know which tags are within its coverage area and report to the middleware and server.

[0116] S103: After obtaining the tag identification information, the reader performs further operations on the AIoT Tag (such as requesting the tag and obtaining information about the tag's storage area).

[0117] After the above operations are completed, the reader can obtain the information of the accessed tag. This step S103 is optional.

[0118] S104: The reader feeds back the inventory information and tag information to the AIoT APP.

[0119] The reader feeds back the tag inventory information / tag information to the AIoT APP.

[0120] Regarding the process of the reader / writer performing an inventory check on the tags (such as AIoT Tags) in step S102 above, referring to Figure 2, the specific process is as follows:

[0121] S201: The reader sends a Select command to the AIoT Tag.

[0122] Correspondingly, the AIoT Tag receives the Select command.

[0123] Specifically, after receiving the inventory command, the reader generates a Select command and then sends it to the AIoT Tag. This inventory command includes a range of tags, such as EPC / TIDs within a specific range. Upon receiving (listening to) the Select command, the tag checks if it falls within the tag range required by the Select command. If it does, it continues to listen for subsequent Query commands; otherwise, the tag does not perform any further steps (i.e., no action is taken).

[0124] S202: The reader sends a query command to the AIoT Tag.

[0125] Correspondingly, when the AIoT Tag receives a valid Query command, it will generate a random number.

[0126] S203: The AIoT Tag sends RN-16 to the reader.

[0127] For example, a tag with a random number of 0, upon receiving a valid Query command, will send a temporary password RN16, which is a 16-bit random number, back to the reader.

[0128] S204: The reader sends an acknowledgment (ACK) command to the AIoT Tag.

[0129] When the reader receives a random number from the tag, it sends an ACK command to the tag, which contains the random number (RN16) that was just received.

[0130] S205: AIoT Tag verifies whether the random number in the ACK command is correct.

[0131] If the random number in the AIoT Tag verification ACK command is correct, proceed to the next step S206.

[0132] S206: The AIoT Tag sends an EPC code to the reader.

[0133] Meanwhile, after sending its own EPC code to the reader, the AIoT Tag enters a brief sleep state.

[0134] After receiving the EPC code of the tag, the reader completes the inventory of the tag.

[0135] Optionally, the reader will continue to send a query response (QueryRep) to the AIoT Tag. If the query response is NAK, it means that the EPC code reception failed and the AIoT Tag needs to re-enter the arbitration state. Otherwise, it means that the EPC code reception was successful and the AIoT Tag enters the confirmation state. After receiving the query response, the AIoT Tag will decrement the original random number by 1. Furthermore, the above steps S203 to S206 are repeated until all tags are fully inventoried.

[0136] The processes shown in Figures 1 and 2 above can also be applied to passive IoT (P-IoT), where the AIoT Tag can be replaced with the P-IoT Tag.

[0137] While the process shown in Figure 2 achieves automated tag inventory to some extent, it presents several key issues. For instance, when handling a large number of tags, identifying each tag individually using the process in Figure 2 results in a high probability of collisions because each tag needs to send an RN16 to the reader and wait for confirmation. This leads to numerous retries and waiting times, significantly slowing down the inventory process and extending the inventory time. Furthermore, the need for reader confirmation after each tag response not only increases the reader's processing load but also limits the overall system throughput, severely impacting inventory efficiency.

[0138] To address the aforementioned problems, this application proposes a communication method and apparatus, which can effectively improve the efficiency of identifying / inventorying tags (terminal devices). The method and apparatus are based on the same inventive concept. Since the principles by which the method and apparatus solve the problems are similar, their implementations can be mutually referenced, and repeated details will not be elaborated further.

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

[0140] 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).

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

[0142] Wireless communication systems that support shorter distance transmission mainly include future StarSpark wireless communication systems, such as StarSpark 2.0 and StarSpark 3.0 wireless communication systems. These systems are suitable not only for communication scenarios with low latency requirements, such as the aforementioned vehicle communication and industrial control scenarios, but also for communication scenarios with less stringent latency requirements.

[0143] The communication systems described above are merely illustrative examples, and are not limited to those described herein. The communication systems provided in this application do not impose any limitations on the solutions described herein. This will be explained uniformly here and will not be repeated below.

[0144] Figure 3 is a schematic diagram of the architecture of a wireless communication system applicable to the embodiments of this application. As shown in Figure 3, the communication system 3000 includes an access network 100. Optionally, the communication system may also include a core network 200 and an Internet 300. The access network 100 may include at least one network device, such as 110a and 110b in Figure 3, and may also include at least one terminal device, such as 120a to 120j in Figure 3. Specifically, 110a is a base station, 110b is a micro-station, 120a, 120e, 120f, and 120j are mobile phones, 120b is a car, 120c is a fuel dispenser, 120d is a home access point (HAP) deployed indoors or outdoors, 120g is a laptop computer, 120h is a printer, and 120i is a drone. The same terminal device or network device can provide different functions in different application scenarios. For example, the mobile phones in Figure 3 are 120a, 120e, 120f and 120j. Mobile phone 120a can access base station 110a, connect to car 120b, communicate directly with mobile phone 120e and access HAP. Car 120b can access HAP and communicate directly with mobile phone 120a. Mobile phone 120f can access micro-station 110b, connect to laptop 120g and printer 120h. Mobile phone 120j can control drone 120i.

[0145] 1) Terminal equipment:

[0146] A terminal device is a user-side device with wireless transceiver capabilities. Terminal devices can also be called terminals, user equipment (UE), mobile stations, mobile terminals, etc. They are widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), the Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, and smart cities. Terminal devices can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, etc. Terminal devices typically contain communication modules, circuits, or chips that perform the corresponding communication functions. They can also be configured with program instructions to perform these functions.

[0147] In the embodiments of this application, the terminal device can also be an IoT terminal device, that is, a new type of low-power, low-cost terminal device. The IoT terminal can be a passive terminal device, a semi-passive terminal device, an energy storage passive terminal device, an energy storage terminal device, an energy storage semi-passive terminal device, an active terminal device, etc. In the embodiments and accompanying drawings of this application, tags (such as AIoT Tags) can also be used to refer to IoT terminal devices. The embodiments of this application do not limit the specific form of IoT terminal devices.

[0148] In the embodiments of this application, the apparatus for implementing the functions of the terminal device can be the terminal device itself, or it can be any apparatus capable of supporting the terminal device in implementing the functions, such as a chip system or a combination of devices or components capable of implementing the functions of the terminal device. This apparatus can be installed in the terminal device. The functions of the terminal device can also be executed by modules (such as chips or modems) within the terminal device, or by apparatus containing the functions of the terminal device. The embodiments of this application do not limit the specific technology or specific device form adopted by the terminal device. The accompanying drawings and the following embodiments use a UE as an example of a terminal device for illustration; any subsequent mention of a UE can be replaced with a terminal device or other examples of terminal devices.

[0149] 2) Network equipment:

[0150] A network device is a network-side device with wireless transceiver capabilities. A network device can be a device or module located on the network side of a communication system and possessing corresponding communication functions. Network devices typically contain communication modules, circuits, or chips that perform the corresponding communication functions. They also contain program instructions for performing these functions, as well as corresponding program instructions. A network device can be a device in a radio access network (RAN) that provides wireless communication functions to terminal devices; this is called an RAN device. The RAN can be an access network in the 3rd Generation Partnership Project (3GPP), such as 4G, 5G, or future-oriented 6G networks. The RAN can also be an open RAN (O-RAN or ORAN), a cloud radio access network (CRAN), or a communication network combining two or more of these.

[0151] RAN equipment can also be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next-generation NodeB (gNB) in a 5G mobile communication system, a base station in a 6G mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system, etc.

[0152] RAN equipment can also be modules or units that perform some of the functions of a base station. For example, it can be a central unit (CU), a distributed unit (DU), or a radio unit (RU). Here, the CU performs the functions of the base station's Radio Resource Control Protocol (RRC) and Packet Data Convergence Protocol (PDCP), and can also perform the functions of the Service Data Adaptation Protocol (SDAP). The DU performs the functions of the base station's Radio Link Control (RAN) and Medium Access Control (MAC) layers, and can also perform some or all of the physical layer functions. For specific descriptions of the above protocol layers, please refer to the relevant 3GPP technical specifications. The CU and DU can be set up separately or included in the same network element, such as in the baseband unit (BBU). The RU can be included in radio equipment or radio units, such as in a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH). In different systems, CU, DU, or RU may have different names, but those skilled in the art will understand their meanings. For example, in an ORAN system, CU can also be called O-CU (Open CU), DU can also be called O-DU, and RU can also be called O-RU. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules. The RA device can be a macro base station (as shown in Figure 3, 110a), a micro base station or an indoor station (as shown in Figure 3, 110b), or a relay node or donor node, etc. The embodiments of this application do not limit the specific technology or specific device form used in the network equipment.

[0153] In this embodiment of the application, when the RAN device can be used to establish a connection with an IoT terminal device for communication, the RAN device can be regarded as a reader.

[0154] In the embodiments of this application, the functions of the network device can be executed by modules (such as chips) within the network device, or by a control subsystem that includes the functions of the network device. This control subsystem, which includes the functions of the network device, can be a control center in the aforementioned application scenarios such as smart grids, industrial control, intelligent transportation, and smart cities.

[0155] Network devices and terminal devices can be fixed in location or mobile. They can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed in the air on airplanes, balloons, and artificial satellites. The embodiments of this application do not limit the application scenarios of the network devices and terminal devices.

[0156] The roles of network devices and terminal devices can be relative. For example, the helicopter or drone 120i in Figure 3 can be configured as a mobile network device. For terminal devices 120j that access the wireless access network 100 via 120i, terminal device 120i is a network device; however, for network device 110a, 120i is a terminal device. That is, 110a and 120i communicate via a wireless air interface protocol. Of course, 110a and 120i can also communicate via a network device-to-network device interface protocol. In this case, relative to 110a, 120i is also a network device. Therefore, both network devices and terminal devices can be collectively referred to as communication devices. 110a and 110b in Figure 3 can be called communication devices with network device functions, and 120a-120j in Figure 3 can be called communication devices with terminal device functions.

[0157] It should be noted that the communication system shown in Figure 3 does not constitute a limitation on the communication systems to which the embodiments of this application can be applied. Therefore, the method provided in the embodiments of this application is applicable to various wireless communication systems, such as Wi-Fi systems, 5G communication systems, or various future mobile communication systems, and this application does not limit it.

[0158] The communication system architecture or network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do 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 system or network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application can also be applied to similar technical problems.

[0159] In this application, "send" and "receive" refer to the direction of information / data / signal transmission. For example, "send information to XX" can be understood as the destination of the information being XX, and "send information" can include direct transmission or indirect transmission through other units or modules. "Receive information from YY" can be understood as the source of the information being YY, and "receive information" can include direct reception from YY or indirect reception from YY through other units or modules. Furthermore, "send" can also be understood as the "output" of a chip interface, and "receive" can be understood as the "input" of a chip interface. In other words, "send" or "receive" can occur between nodes / devices, such as a base station and a terminal transmitting or receiving data via an air interface. "Send" or "receive" can also occur within a device, such as between components, modules, chips, software modules, or hardware modules within the device via a bus, wiring, or interface.

[0160] It should be understood that the names of the messages (or information) in the following processes in this application are merely examples. As communication technology evolves, the names of the messages (or information, etc.) in the following processes may change. However, regardless of how their names change, as long as their meaning is the same as the function or meaning of the messages (or information, etc.) in this application, they all fall within the protection scope of this application. For example, in the scenario of tag inventory in the Internet of Things, the "terminal device" can be replaced with "tag," "electronic tag," or "communication device," etc. The "first device" in the embodiments of this application can be replaced with "reader," "access network device," etc., and "first message" can be replaced with "query message" or "query command," etc., and so on. These will not be listed individually here.

[0161] The solutions of the embodiments of this application will be described below.

[0162] This application provides a communication method, which can be applied to, but is not limited to, the network architecture shown in Figure 3. The method can be executed by a first terminal device (or simply a first device), by a module of the first terminal device (or simply a first device) (e.g., a processor, chip, or chip system), or by a logical node, logical module, or software capable of implementing all or part of the functions of the first terminal device (or simply a first device). Furthermore, this application does not specifically limit the specific structure and number of the execution entities (first terminal device, first device) of the method provided in this application, as long as communication can be performed by running a program that records the code of the method provided in this application. For ease of description, the interaction between two first terminal devices is used as an example in the following description. The order of steps in the following processes is merely an example; in actual applications, the execution order of steps in each process can be adjusted, and all or part of the following steps can be executed adaptively.

[0163] Referring to Figure 4, the method provided in this application embodiment may include the following steps:

[0164] S401: The first device sends a first message, and correspondingly, the first terminal device receives the first message; wherein, the first message is used to query the permanent identification information of the terminal device; the first message includes system information for synchronization and information of the first resource set.

[0165] In this application embodiment, the terminal device (including the first terminal device) can be, but is not limited to, an IoT terminal device, i.e., a novel low-power, low-cost terminal device. The IoT terminal can include passive terminal devices, semi-passive terminal devices, energy storage passive terminal devices, energy storage terminal devices, energy storage semi-passive terminal devices, active terminal devices, etc. In this application embodiment, electronic tags or labels (e.g., passive IoT tags, AIoT tags) can also be used to represent the IoT terminal device. This application embodiment does not limit the specific form of the IoT terminal device. As mentioned above, the first device can be a device that supports terminal device access, such as an access network device or a reader / writer. The first device can also be a relay device with access and / or forwarding functions.

[0166] In one possible implementation, the first device sends a first message, specifically including: the first device can send the first message in a broadcast manner according to a preset period. The preset period can be predefined by a protocol, or agreed upon or negotiated between the sender and receiver; there are no restrictions on this.

[0167] In this embodiment, the permanent identification information of the terminal device can refer to an identifier or information that can uniquely identify the terminal device and will not change. For example, in the tag identification scenario of RFID technology, the terminal device is an electronic tag, and the permanent identification information of the terminal device can be the Electronic Product Code (EPC) or Tag Identification Number (TID) of the electronic tag.

[0168] In one possible implementation, the system information includes wireless frame information and / or time slot information. The method in this application embodiment further includes: the first terminal device performing synchronization processing with the first device based on the wireless frame information and / or time slot information.

[0169] For example, the system information includes, but is not limited to, the frame number and the time slot number therein (optionally, it may also include a symbol); after receiving the system information, the first terminal device can adjust the position of its own frame and time slot based on the frame number and time slot number therein, so as to align with the frame and time slot on the first device side. In this way, the first terminal device and the first device can keep in line with time (i.e., synchronize), thereby ensuring the accuracy and efficiency of communication between the two.

[0170] S402: The first terminal device sends a second message to the first device based on the first resource in the first resource set, and the first device receives the second message accordingly; wherein the second message is used to request access.

[0171] In one possible implementation, the first resource set includes multiple resources, including time-domain resources and / or frequency-domain resources. Before executing S402, the method of this embodiment may further include: the first terminal device selecting a first resource from the multiple resources. Through this implementation, the first terminal device can effectively obtain available resources to initiate an access request to the first device for communication.

[0172] In one possible implementation, the second message includes first information for temporarily identifying the first terminal device. The method in this embodiment may further include the following steps:

[0173] The first device sends a third message to the first terminal device, and the first terminal device receives the third message accordingly. The third message is used to confirm acceptance of the request of the second message. The third message includes first information and second information. The second information is used to indicate the resource corresponding to the first terminal device, and the first information is associated with the resource corresponding to the first terminal device. The first terminal device sends the permanent identification information of the first terminal device to the first device on the resource corresponding to the first terminal device.

[0174] In one possible implementation, the first terminal device may send its permanent identification information to the first device in the form of orthogonal frequency division multiplexing (OFDM) on the resources corresponding to the first terminal device.

[0175] In the above, when the first device confirms that it has accepted the access of the first terminal device, it can allocate available resources to the first terminal device for the first terminal device to send its own permanent identification information. The first device also sends a third message to the first terminal device, which includes first information (i.e., information that temporarily identifies the first terminal device) and second information (i.e., information used to indicate the resources corresponding to the first terminal device). After receiving the third message, the first terminal device can confirm whether the resource indicated by the second information in the third message belongs to itself based on the first information in the third message, thereby ensuring the accuracy of the first terminal device obtaining available resources.

[0176] In another possible implementation, the second message includes first information for temporarily identifying the first terminal device. The method in this application embodiment may further include: the first device allocating a corresponding second resource to the first terminal device based on a second resource set, wherein the second resource is different from the first resource; in one possible implementation, the second resource belongs to the second resource set, and the first resource set includes the second resource set.

[0177] Furthermore, based on this implementation, the method may further include: the first device sending a third message to the first terminal device, and correspondingly, the first terminal device receiving the third message; the third message is used to confirm acceptance of the request for the second message, the third message includes first information and second information, the second information is used to indicate the second resource corresponding to the first terminal device, and the first information is associated with the second resource; then the first terminal device sends the permanent identification information of the first terminal device to the first device on the second resource.

[0178] In one possible implementation, the first terminal device may send its permanent identification information to the first device in the form of orthogonal frequency division multiplexing (OFDM) on the second resource corresponding to the first terminal device.

[0179] In the above scenario, upon confirming acceptance of the first terminal device's access, the first device can allocate available second resources to the first terminal device from a second resource set. This second resource set may be included in the previously allocated first resource set. The second resource differs from the first resource used by the first terminal device; it is used for the first terminal device to subsequently send its own permanent identification information. The first device sends a third message to the first terminal device. This third message includes first information from the first terminal device (i.e., information temporarily identifying the first terminal device) and second information (i.e., information indicating the second resource corresponding to the first terminal device). Upon receiving the third message, the first terminal device can confirm, based on the first information in the third message, whether the second resource indicated by the second information in the third message belongs to it, thereby ensuring the accuracy of the first terminal device obtaining available resources.

[0180] In the above, the first information in the second message (used to temporarily identify the first terminal device) can be, but is not limited to, a random number generated for the first terminal device. For example, the first information can be a 16-bit random number RN16 or a random number of smaller bits, or the first information can be used to indicate a 16-bit random number RN16 or a random number of smaller bits. For example, in the above, the permanent identification information of the first terminal device can be the Electronic Product Code (EPC) or the Tag Identification Number (TID) of the first terminal device.

[0181] Based on the above implementation, if the resource corresponding to the first terminal device (or the second resource corresponding to the first terminal device) is a time-domain resource, then the second information in the third message can be the information of the time-domain resource corresponding to the first terminal device. The information of the time-domain resource may include, but is not limited to, one or more of the following:

[0182] (1) Identification information of time-domain resources (e.g., identification, index, or number of time-domain resources); (2) Time-domain parameters.

[0183] Based on the above implementation, if the resource corresponding to the first terminal device (or the second resource corresponding to the first terminal device) is a frequency domain resource, then the second information in the third message can be the information of the frequency domain resource corresponding to the first terminal device. The information of the frequency domain resource may include, but is not limited to, one or more of the following:

[0184] (1) Identification information of frequency domain resources (e.g., identification, index, or number of frequency domain resources); (2) Frequency shift parameters.

[0185] Based on the above implementation, if the resources corresponding to the first terminal device (or the second resources corresponding to the first terminal device) include time-domain resources and frequency-domain resources, then the second information in the third message includes information about the time-domain resources and information about the frequency-domain resources corresponding to the first terminal device; wherein, the information about the time-domain resources may include, but is not limited to, the identification information and / or time-domain parameters of the time-domain resources; the information about the frequency-domain resources may include, but is not limited to, the identification information and / or frequency-shifting parameters of the frequency-domain resources.

[0186] For example, assuming the time-domain resource corresponding to the first terminal device is the first subframe, the identification information of the time-domain resource corresponding to the first terminal device can be the frame number, corresponding number, or index of the first subframe. Similarly, assuming the frequency-domain resource corresponding to the first terminal device is the first frequency band, the identification information of the frequency-domain resource corresponding to the first terminal device can be the frequency band number (such as the frequency band number specified in the protocol) or corresponding number or index of the first frequency band.

[0187] In one possible implementation, the aforementioned time-domain parameter can be the ratio of time-domain resources to time-domain resource units, or the time-domain parameter can be the total number of time-domain resource units contained in the time-domain resources.

[0188] For example, suppose the first device allocates a corresponding time-domain resource, the first subframe, to the first terminal device. The first subframe includes M time slots, where M is a positive integer, and one time slot is one time-domain resource unit. The information of the time-domain resource corresponding to the first terminal device (i.e., the second information) is a time-domain parameter, which is a value M. The value M represents the ratio between the total number of time slots and the number of time slot units in the first subframe, or it represents the number of time slots contained in the first subframe.

[0189] In one possible implementation, the frequency shift parameter can be the offset of the frequency domain resource, or the frequency shift parameter can include a frequency shift unit and a frequency shift factor.

[0190] For example, suppose the first device allocates a corresponding frequency domain resource, namely a first frequency band, to the first terminal device. The offset of the first frequency band is N, and the frequency shift unit is set to n, where N and n are positive integers, and N is greater than or equal to n. The information of the frequency domain resource corresponding to the first terminal device (i.e., the second information) is the frequency shift parameter. This frequency shift parameter can be the offset N corresponding to the first frequency band, or it can include the value n (frequency shift unit) and the value N / n (frequency shift multiple), where " / " is a division sign.

[0191] In one possible implementation, where the resources corresponding to the first terminal device and the second terminal device each include frequency domain resources, then the frequency domain resources corresponding to the first terminal device and the frequency domain resources corresponding to the second terminal device conform to a subcarrier orthogonal relationship. Here, the second terminal device can refer to other terminal devices besides the first terminal device that can access the first device.

[0192] In one possible implementation, the method of this application embodiment may further include: a first device may broadcast a fourth message, and correspondingly, a first terminal device receives the fourth message, which is used to indicate a preset condition; the first terminal device determines that the preset condition is met. Optionally, this implementation may be performed before S401.

[0193] The above S401-S402 and the contents thereof are used as examples to introduce the scheme of the embodiments of this application. In practical applications, when there are multiple terminal devices similar to the first terminal device, each terminal device can refer to the steps corresponding to the first terminal device to implement information interaction with the first device, etc., and will not be described in detail for each terminal device here.

[0194] In summary, embodiments of this application provide a communication method and apparatus. The method includes: a first terminal device receiving a first message from a first device, the first message being used to query permanent identification information of the terminal device, and the first message including system information for synchronization and information of a first resource set; the first terminal device sending a second message to the first device based on a first resource in the first resource set, the second message being used to request access. In this method, the first device can allocate available resources for the access of the terminal device, so that the terminal device can promptly utilize the corresponding resources for access, avoiding waiting for access based on time-division multiplexing, thereby effectively improving the efficiency of identifying the terminal device.

[0195] The following example uses the scheme shown in Figure 4 for tag inventory in the Internet of Things, and provides a detailed introduction to the scheme shown in Figure 4 through several specific implementation methods.

[0196] Implementation Method 1:

[0197] In Implementation Method 1, taking a reader as an example and tag #1 as an example, the implementation method of allocating time-domain resources to the terminal device by the first device in the scheme of this application embodiment is introduced. Referring to Figure 5, the method flow of Implementation Method 1 includes the following steps:

[0198] S501: The reader sends a Select message (an example of the fourth message in the scheme shown in Figure 4 above). The Select message is used to select a tag that meets the conditions. Accordingly, tag 1 receives the Select message and tag 1 enters the inventory cycle.

[0199] S501 can refer to the steps in S201 above, and will not be repeated here.

[0200] S502: The reader sends a query message (an example of the first message in the scheme shown in Figure 4 above). The query message includes system information and information about the time-domain resource pool 1 (an example of information about the first resource set in the scheme shown in Figure 4 above). Accordingly, tag 1 receives the query message.

[0201] In one possible implementation, when the reader sends a Query message, it can specifically be that the reader can periodically send Query messages according to a preset period, where the preset period can be predefined by the protocol, such as 1 millisecond (ms).

[0202] For example, the system information in the Query message may include time information (such as frame number, time slot number, etc.) for time-domain synchronization, and may also include frequency information (such as subcarrier number, RB number, etc.) for frequency-domain synchronization.

[0203] In one possible implementation, after receiving the Query message, tag 1 may also perform time-domain and / or frequency-domain synchronization with the reader / writer based on the system information in the Query message.

[0204] In the embodiments of this application, the specific implementation of the synchronization of tag 1 with the reader in the time domain and / or frequency domain based on system information can refer to existing synchronization technologies, and will not be described in detail here.

[0205] In this embodiment of the application, the information of the time-domain resource pool 1 (an example of the first resource set in the scheme shown in Figure 4 above) in the Query message may include the identification information of all time-domain resources in the time-domain resource pool 1, or other information that can indicate these time-domain resources; the way of indicating the time-domain resource pool 1 can be flexibly designed and is not specifically limited. In addition, the time-domain resources contained in the time-domain resource pool 1 can be continuous or non-continuous, and there is no limitation on this.

[0206] For example, if the time-domain resources in time-domain resource pool 1 are continuous, the information of time-domain resource pool 1 can be the information corresponding to the first and last time-domain resources of time-domain resource pool 1, or it can be the information corresponding to a segment of time-domain resources.

[0207] For example, assuming that time-domain resource pool 1 is one radio frame, i.e. radio frame #1, then the information of time-domain resource pool 1 can be (or indicate) the value 1, which is the number / index corresponding to radio frame #1.

[0208] For example, suppose that time-domain resource pool 1 is one radio frame, namely radio frame #1, which contains 10 time slots (i.e., time slot #0 to time slot #9). Then the information of time-domain resource pool 1 may include (or indicate) the values ​​0 and 9. The value 0 is the number / index corresponding to the first time slot in radio frame #1, and the value 9 is the number / index corresponding to the last time slot in radio frame #1.

[0209] S503: Tag 1 sends its RN16 (an example of the first information used to temporarily identify the first terminal device in the scheme shown in Figure 4) to the reader on time-domain resource 1 in time-domain resource pool 1 (an example of the first resource in the scheme shown in Figure 4 above). Accordingly, the reader receives the RN16.

[0210] Among them, RN16 of tag 1 can be a 16-bit random number randomly generated by tag 1 after receiving the Query message.

[0211] S504: The reader sends an ACK message to tag 1 on time domain resource 1 (an example of the third message in the scheme shown in Figure 4 above). Accordingly, tag 1 receives the ACK message, which includes the RN16 of tag 1 (an example of the first information in the scheme shown in Figure 4 above) and the information of the time domain resource 2 corresponding to tag 1 (an example of the second information in the scheme shown in Figure 4 above).

[0212] In one possible implementation, before S504, the reader may allocate time-domain resources 2 (examples of resources corresponding to the first terminal device or second resources in the scheme shown in Figure 4 above) to tag 1 from time-domain resource pool 2 (examples of the second resource set in the scheme shown in Figure 4 above).

[0213] In the embodiments of this application, the time-domain resource pool 2 and the aforementioned time-domain resource pool 1 can be independent of each other, and the time-domain resources therein do not intersect; or, there is some intersection between the time-domain resource pool 1 and the time-domain resource pool 2; or, the time-domain resource pool 1 contains the time-domain resource pool 2; or, the time-domain resource pool 2 contains the time-domain resource pool 1, and there is no specific limitation on this.

[0214] In one possible implementation, the RN16 of tag 1 and time-domain resource 2 are interconnected.

[0215] In this first implementation, when the reader receives random numbers RN16 from multiple tags (including tag 1), the time-domain resources allocated by the reader for each tag can be associated with the random number RN16 sent by the tag. Furthermore, for each tag, the correspondence between the time-domain resources allocated by the reader and the random number RN16 sent by the tag may be one-to-one, many-to-one, or one-to-many, and there are no restrictions on this.

[0216] For example, taking tags 1 and 2 as examples, tag 1 sends its RN16 to the reader on a randomly selected time-domain resource in time-domain resource pool 1; tag 2 can also send its RN16 to the reader on a randomly selected time-domain resource in time-domain resource pool 1. Further, after receiving the RN16 of tags 1 and 2, the reader can allocate a corresponding time-domain resource 2 for tag 1 and a corresponding time-domain resource 3 for tag 2 from time-domain resource pool 2. Of course, the reader can also allocate corresponding time-domain resources for tags 1 and 2 from different time-domain resource pools; this is not limited. Time-domain resource 2 is associated with or corresponds to the RN16 of tag 1, and time-domain resource 3 is associated with or corresponds to the RN16 of tag 2.

[0217] In one possible implementation, when the reader receives a random number RN16 from multiple tags (including tag 1), the reader can broadcast an ACK message. This ACK message can be used to acknowledge or respond to the access of tag 1, or to acknowledge or respond to the access of other tags.

[0218] For example, taking tag 1 and tag 2 as examples, after the reader receives the RN16 of tag 1 and the RN16 of tag 2, the reader can broadcast an ACK message to tag 1 and tag 2. The ACK message includes the RN16 of tag 1 and the information of the time domain resource 2 corresponding to tag 1, and also includes the RN16 of tag 2 and the information of the time domain resource 3 corresponding to tag 2.

[0219] Optionally, tag 1 can also obtain the association (or mapping) information between tag 1's RN16 and time domain resource 2 from the reader, and tag 2 can also obtain the association (or mapping) information between tag 2's RN16 and time domain resource 3 from the reader.

[0220] Furthermore, after receiving the ACK message, tag 1 can determine to use time domain resource 2 based on its own RN16 and the association (or mapping) relationship between tag 1's RN16 and time domain resource 2.

[0221] Tag 2 can determine which temporal resource 3 to use based on its own RN16 and the association (or mapping) information between Tag 2's RN16 and temporal resource 3.

[0222] In one possible implementation, the information of the time-domain resource 2 corresponding to the aforementioned label 1 can be the identification information of the time-domain resource 2 (such as identifier, index, etc.).

[0223] For example, if the temporal resource 2 corresponding to label 1 is a subframe, then the identification information of temporal resource 2 can be the subframe number or the subframe index, etc. If the temporal resource 2 corresponding to label 1 is a time slot, then the identification information of temporal resource 2 can be the time slot number or the time slot index, etc. If the temporal resource 2 corresponding to label 1 is a symbol, then the identification information of temporal resource 2 can be the symbol number or index, etc.

[0224] In another possible implementation, the information of the time-domain resource 2 corresponding to the aforementioned label 1 can be a time-domain parameter (or a time parameter).

[0225] For example, the time-domain parameter (or time parameter) can be the ratio (or time multiple) of time-domain resource 2 to time-domain resource unit, or the time-domain parameter (or time parameter) can be the total number of time-domain resource units contained in time-domain resource 2.

[0226] In the above, the time multiplier = total time (or time domain resource 2) / time unit (or time domain resource unit); where "=" is the equal sign and " / " is the division sign.

[0227] For example, suppose the reader allocates two time slots (time slot #0 and time slot #1) to tag 1 as corresponding time domain resource 2. One time slot is a time domain resource unit (or time unit). The reader sends an ACK message to tag 1. This ACK message includes tag 1's RN16 and the numbers of the two time slots (i.e., 0 and 1). Alternatively, the ACK message includes tag 1's RN16 and the value 2, where the value 2 represents the number of time slots (or a multiple of the number of time slots) contained in the time domain resource 2 corresponding to tag 1.

[0228] Similarly, if other tags exist, the information of the time-domain resources corresponding to other tags can be found in the description of the time-domain resources corresponding to tag 1, which will not be repeated here.

[0229] S505: Tag 1 sends its permanent identification information to the reader on time domain resource 2. Correspondingly, the reader receives the permanent identification information of Tag 1.

[0230] In one possible implementation, tag 1 sends its permanent identification information to the reader on time domain resource 2, including: tag 1 sending its permanent identification information to the reader in OFDM format on time domain resource 2.

[0231] For example, the permanent identification information of tag 1 can be an Electronic Product Code (EPC) or a Tag Identification Number (TID), etc.

[0232] After S505, the reader can also return a response message to tag 1. If the response message is NAK, it means that the reader failed to receive the permanent identification information of tag 1, and tag 1 will return to the arbitration state. Otherwise, it means that the reader successfully received the permanent identification information of tag 1, and tag 1 will enter the acknowledgment state.

[0233] Based on the content shown in S501 to S505 above, the following are some specific diagrams to illustrate the interaction process between the reader and tag 1.

[0234] Example 1: Referring to Figure 6A, firstly, the reader can broadcast a selection message, and tag 1 receives the selection message accordingly. Next, the reader broadcasts a query message, and tag 1 receives the query message. The query message includes system information and information about time-domain resource pool 1. Tag 1 determines the location of time-domain resource pool 1 based on the information of time-domain resource pool 1, and can then select time-domain resource 1 from time-domain resource pool 1. Tag 1 sends its RN16 to the reader on time-domain resource 1. After receiving the RN16 of tag 1, the reader can allocate time-domain resource 2 for tag 1 from time-domain resource pool 2. After this, the reader sends an ACK message to tag 1. The ACK message includes the RN16 of tag 1 and the corresponding information about time-domain resource 2. After receiving the ACK message, tag 1 can determine the location of time-domain resource 2 based on the information of time-domain resource 2, and then send its permanent identification information (e.g., EPC) to the reader on time-domain resource 2.

[0235] In Figure 6A, the time-domain resource pool 1 and the time-domain resource pool 2 do not overlap. The embodiments of this application do not impose specific limitations on the size of the time-domain resource pool 1 and the time-domain resource pool 2, nor do they impose specific limitations on the size of the time-domain resource 1 and the time-domain resource 2.

[0236] Example 2: Referring to Figure 6B, the difference between the schematic diagram shown in Figure 6A and the schematic diagram shown in Figure 6B is that: time-domain resource pool 1 can contain time-domain resource pool 2.

[0237] Example 3: Referring to Figure 6C, compared with the schematic diagrams shown in Figures 6A and 6B, the difference in the schematic diagram shown in Figure 6C is that: time-domain resource pool 2 can contain time-domain resource pool 1.

[0238] Figures 6A, 6B, and 6C above are merely partial examples of this first embodiment. In practice, this application does not limit the specific form of the time-domain resource pool or the time-domain resources. For example, the time-domain resources in time-domain resource pool 1 and / or time-domain resource pool 2 can be continuous or discontinuous; similarly, time-domain resource 1 and / or time-domain resource 2 can also be continuous or discontinuous, without specific limitations.

[0239] The following example uses time-domain resource pool 1 and time-domain resource 1:

[0240] For example, in the above S502, the time domain resource pool 1 allocated by the reader includes 5 consecutive time slots from time slot #1 to time slot #5; or, the time slot resource pool 1 includes 5 non-consecutive time slots: time slot #1, time slot #3, time slot #5, time slot #7, and time slot #9.

[0241] Taking the time domain resource pool 1 allocated by the reader as an example, which includes five consecutive time slots from time slot #1 to time slot #5, tag 1 can randomly select time domain resource 1 from the symbols of these five consecutive time slots. This time domain resource 1 can be five symbols in time slot #1, and these five symbols can be consecutive symbols or non-consecutive symbols.

[0242] Furthermore, in S503, tag 1 can send RN16 to the reader on the first of these 5 symbols; in S504, the reader can return an ACK message to tag 1 on the fifth of these 5 symbols.

[0243] In Implementation Method 1, tag 1 is used as an example to describe the method flow of Implementation Method 1 in detail. In the actual tag inventory process, there may be a larger number (or a large number) of tags. Each tag can be executed according to the implementation method corresponding to tag 1 (i.e., the content shown in S501 to S505). That is, each tag can interact with the reader or writer in a timely manner on its own corresponding and available time domain resources, without having to wait for identification to be completed one by one through the traditional tag inventory process. This can not only effectively improve the efficiency of tag inventory, but also significantly improve the identification efficiency, resource utilization and system performance of the RFID system.

[0244] Implementation Method Two:

[0245] Unlike Implementation Method 1, Implementation Method 2 mainly introduces the implementation method where the resources allocated by the first device to the terminal device in the scheme of this application are frequency domain resources. Referring to Figure 7, the method flow of Implementation Method 2 includes the following steps:

[0246] S701: The reader sends a Select message (an example of the fourth message in the scheme shown in Figure 4 above). The Select message is used to select a tag that meets the conditions. Accordingly, tag 1 receives the Select message and tag 1 enters the inventory cycle.

[0247] S701 can be referred to in the description in S201 above, and will not be repeated here.

[0248] S702: The reader sends a query message (an example of the first message in the scheme shown in Figure 4 above). The query message includes system information and information about frequency domain resource pool 1 (an example of information about the first resource set in the scheme shown in Figure 4 above). Accordingly, tag 1 receives the query message.

[0249] For details on S702, please refer to the description in S502. It will not be elaborated here. However, unlike S502, the Query message in S702 carries information about frequency domain resource pool 1.

[0250] In this embodiment, similar to the time-domain resource pool 1, the information of the frequency-domain resource pool 1 (an example of the first resource set in the scheme shown in Figure 4 above) in the Query message may include the identification information of all frequency-domain resources in the frequency-domain resource pool 1, or other information that can indicate these frequency-domain resources; the way of indicating the frequency-domain resource pool 1 can be flexibly designed and is not specifically limited. In addition, the frequency-domain resources contained in the frequency-domain resource pool 1 can be continuous or non-contiguous, and this is not limited.

[0251] For example, if frequency domain resource pool 1 includes all frequencies within the first frequency band, then the information of frequency domain resource pool 1 can be the first frequency band number, or the information of frequency domain resource pool 1 can include the frequency information corresponding to the beginning and end of the first frequency band respectively.

[0252] S703: Tag 1 sends its RN16 (an example of the first information used to temporarily identify the first terminal device in the scheme shown in Figure 4) to the reader on frequency domain resource 1 in frequency domain resource pool 1 (an example of the first resource in the scheme shown in Figure 4 above). Accordingly, the reader receives the RN16.

[0253] Among them, RN16 of tag 1 can be a 16-bit random number randomly generated by tag 1 after receiving the Query message.

[0254] S704: The reader sends an ACK message to tag 1 on frequency domain resource 1 (an example of the third message in the scheme shown in Figure 4 above). Accordingly, tag 1 receives the ACK message, which includes tag 1's RN16 (an example of the first information in the scheme shown in Figure 4 above) and information of the frequency domain resource 2 corresponding to tag 1 (an example of the second information in the scheme shown in Figure 4 above).

[0255] In one possible implementation, prior to S704, the reader may allocate frequency domain resources 2 (examples of resources corresponding to the first terminal device or second resources in the scheme shown in Figure 4 above) to tag 1 from frequency domain resource pool 2 (examples of the second resource set in the scheme shown in Figure 4 above).

[0256] In this second embodiment, the frequency domain resource pool 2 and the frequency domain resource pool 1 can be independent of each other, and the frequency domain resources therein do not intersect; or, there is some intersection between the frequency domain resource pool 1 and the frequency domain resource pool 2; or, the frequency domain resource pool 1 contains the frequency domain resource pool 2; or, the frequency domain resource pool 2 contains the frequency domain resource pool 1, and there is no specific limitation on this.

[0257] In one possible implementation, RN16 of tag 1 and frequency domain resource 2 are interconnected.

[0258] In this second implementation, similar to the time-domain resources described above, when the reader receives random numbers RN16 from multiple tags (including tag 1), the frequency-domain resources allocated by the reader for each tag can be correlated with the random number RN16 it sends. Furthermore, for each tag, the correspondence between the frequency-domain resources allocated by the reader and the random number RN16 it sends may be one-to-one, many-to-one, or one-to-many, and there are no restrictions on this.

[0259] For example, taking tags 1 and 2 as examples, tag 1 sends its RN16 to the reader on a randomly selected frequency domain resource in frequency domain resource pool 1; tag 2 can also send its RN16 to the reader on a randomly selected frequency domain resource in frequency domain resource pool 1. Further, after receiving the RN16 of tags 1 and 2, the reader can allocate corresponding frequency domain resource 2 for tag 1 and corresponding frequency domain resource 3 for tag 2 from frequency domain resource pool 2. Of course, the reader can also allocate corresponding frequency domain resources for tags 1 and 2 from different frequency domain resource pools; this is not limited. Frequency domain resource 2 is associated with or corresponds to the RN16 of tag 1, and frequency domain resource 3 is associated with or corresponds to the RN16 of tag 2.

[0260] In one possible implementation, the information of the frequency domain resource 2 corresponding to tag 1 carried in the above ACK message can be the identification information of the frequency domain resource 2 (such as identifier, index, etc.).

[0261] For example, if the frequency domain resource 2 corresponding to label 1 is the first frequency band, then the identification information of the frequency domain resource 2 can be the number or index of the first frequency band, etc.

[0262] In another possible implementation, the information of the frequency domain resource 2 corresponding to tag 1 carried in the above ACK message can be a frequency shift parameter.

[0263] In this second implementation, in the scenario of inventorying tags, if there are multiple tags (including tag 1), if the time domain resources corresponding to these multiple tags are the same, the frequency domain resources corresponding to these multiple tags can be indicated by frequency shift parameters. The frequency shift parameters corresponding to these multiple tags are different and satisfy the subcarrier orthogonal relationship.

[0264] For example, the frequency shift parameter corresponding to tag 1 is the offset of frequency domain resource 2, or the frequency shift parameter corresponding to tag 1 includes a frequency shift unit and a frequency shift factor. Wherein, the frequency shift factor = offset of frequency domain resource 2 / frequency shift unit; "=" is the equal sign, and " / " is the division sign.

[0265] For example, if the reader determines that the offset of the frequency domain resource 2 corresponding to tag 1 is N, and sets the frequency shift unit to n (N and n are positive integers, N is greater than or equal to n), then the frequency shift parameter corresponding to tag 1 is the offset N, or the frequency shift parameter corresponding to tag 1 includes the frequency shift unit n and the frequency shift multiple N / n.

[0266] S705: Tag 1 sends its permanent identification information to the reader on frequency domain resource 2.

[0267] In one possible implementation, tag 1 sends its permanent identification information to the reader on frequency domain resource 2, including: tag 1 sending its permanent identification information to the reader in OFDM format on frequency domain resource 2.

[0268] For example, the permanent identification information of tag 1 can be an Electronic Product Code (EPC) or a Tag Identification Number (TID), etc.

[0269] S705 can be referred to in the above description of S505, and will not be elaborated here.

[0270] Based on the content shown in S701 to S705 above, the following are some specific diagrams to illustrate the interaction process between the reader and tag 1.

[0271] Example 1: First, the reader can broadcast a selection message, and tag 1 receives the selection message accordingly. Then, the reader broadcasts a query message, and tag 1 receives the query message accordingly. The query message includes system information and information about frequency domain resource pool 1. Tag 1 determines the location of frequency domain resource pool 1 based on the information about frequency domain resource pool 1.

[0272] Furthermore, referring to Figure 8A, tag 1 can randomly select frequency domain resource 1 from frequency domain resource pool 1 and send tag 1's RN16 to the reader on frequency domain resource 1. After receiving tag 1's RN16, the reader can allocate frequency domain resource 2 for tag 1 from frequency domain resource pool 2. After that, the reader sends an ACK message to tag 1. The ACK message includes tag 1's RN16 and the corresponding information of frequency domain resource 2. After receiving the ACK message, tag 1 determines the location of frequency domain resource 2 based on the information of frequency domain resource 2, and then sends tag 1's permanent identification information (such as EPC) to the reader on frequency domain resource 2.

[0273] In Figure 8A, frequency domain resource pool 1 and frequency domain resource pool 2 do not overlap. In this embodiment, the size of frequency domain resource pool 1 and frequency domain resource pool 2 is not specifically limited, and the size of frequency domain resource 1 and frequency domain resource 2 is not specifically limited either.

[0274] Example 2: Referring to Figure 8B, the difference between the schematic diagram shown in Figure 8A and the schematic diagram shown in Figure 8B is that frequency domain resource pool 1 can include frequency domain resource pool 2.

[0275] Example 3: Referring to Figure 8C, compared with the schematic diagrams shown in Figures 8A and 8B, the difference in the schematic diagram shown in Figure 8C is that frequency domain resource pool 2 can include frequency domain resource pool 1.

[0276] Figures 8A, 8B, and 8C above are merely partial examples of this second embodiment. In practice, this application does not limit the specific form of the frequency domain resource pool and the frequency domain resources. For example, the frequency domain resources in frequency domain resource pool 1 and / or frequency domain resource pool 2 can be continuous or discontinuous; similarly, frequency domain resource 1 and / or frequency domain resource 2 can also be continuous or discontinuous, without specific limitations.

[0277] In Implementation Method 2, tag 1 is used as an example to describe the method flow of Implementation Method 2 in detail. In the actual tag inventory process, there may be a larger number (or a large number) of tags. Each tag can be executed according to the implementation method corresponding to tag 1 (i.e., the content shown in S701 to S705). That is, each tag can interact with the reader or writer in a timely manner on its own corresponding and available frequency domain resources, without having to wait for identification to be completed one by one through the traditional tag inventory process. This can not only effectively improve the efficiency of tag inventory, but also significantly improve the identification efficiency, resource utilization and system performance of the RFID system.

[0278] Implementation Method 3:

[0279] Unlike Implementation Method 1 and Implementation Method 2, Implementation Method 3 mainly introduces the implementation method of allocating time-frequency resources (i.e., time domain resources and frequency domain resources) to the terminal device by the first device in the scheme of this application embodiment. Referring to Figure 9, the method flow of Implementation Method 3 includes the following steps:

[0280] S901: The reader sends a Select message (an example of the fourth message in the scheme shown in Figure 4 above). The Select message is used to select a tag that meets the conditions. Accordingly, tag 1 receives the Select message and tag 1 enters the inventory cycle.

[0281] S901 can be referred to in the description in S201 above, and will not be repeated here.

[0282] S902: The reader sends a query message (an example of the first message in the scheme shown in Figure 4 above). The query message includes system information and information about the time-frequency resource pool 1 (an example of information about the first resource set in the scheme shown in Figure 4 above). Accordingly, tag 1 receives the query message.

[0283] For details on S902, please refer to the descriptions in S502 and S702. They will not be elaborated here. However, unlike S502 and S702, the Query message in S902 carries information about the time-frequency resource pool 1. The time-frequency resource pool 1 includes both time-domain resources and frequency-domain resources. The time-frequency resource pool 1 can be understood as a resource pool composed of or formed by the time-domain resource pool 1 and the frequency-domain resource pool 1.

[0284] In S902, the information of time-frequency resource pool 1 (an example of the first resource set in the scheme shown in Figure 4 above) in the Query message may include the identification information of all time-frequency resources in time-frequency resource pool 1, or other information that can indicate these time-frequency resources; the way of indicating time-frequency resource pool 1 can be flexibly designed without specific restrictions. In addition, the time-frequency resources contained in time-frequency resource pool 1 can be continuous or non-continuous, and there are no restrictions on this.

[0285] S903: Tag 1 sends its RN16 (an example of the first information used to temporarily identify the first terminal device in the scheme shown in Figure 4) to the reader on time-frequency resource 1 in time-frequency domain resource pool 1 (an example of the first resource in the scheme shown in Figure 4 above). Accordingly, the reader receives the RN16.

[0286] Among them, RN16 of tag 1 can be a 16-bit random number randomly generated by tag 1 after receiving the Query message.

[0287] For details on S903, please refer to the descriptions in S503 and S703; they will not be elaborated upon here.

[0288] S904: The reader sends an ACK message to tag 1 on time-frequency resource 1 (an example of the third message in the scheme shown in Figure 4 above). Accordingly, tag 1 receives the ACK message, which includes tag 1's RN16 (an example of the first information in the scheme shown in Figure 4 above) and the information of the time-frequency resource 2 corresponding to tag 1 (an example of the second information in the scheme shown in Figure 4 above).

[0289] In one possible implementation, prior to S904, the reader may allocate time-frequency resources 2 (the resources corresponding to the first terminal device or the second resource in the scheme shown in Figure 4 above) to the tag 1 from the time-frequency resource pool 2 (an example of the second resource set in the scheme shown in Figure 4 above).

[0290] In this third embodiment, the time-frequency resource pool 2 and the aforementioned time-frequency resource pool 1 can be independent of each other, and the time-frequency resources therein do not intersect; or, there is some intersection between the time-frequency resource pool 1 and the time-frequency resource pool 2; or, the time-frequency resource pool 1 contains the time-frequency resource pool 2; or, the time-frequency resource pool 2 contains the time-frequency resource pool 1, and there is no specific limitation on this.

[0291] In one possible implementation, the RN16 of tag 1 and the time-frequency resource 2 are interconnected.

[0292] In this third embodiment, similar to the time-domain resources and frequency-domain resources described above, when the reader receives random numbers RN16 from multiple tags (including tag 1), the time-frequency resources allocated by the reader for each tag can be correlated with the random number RN16 it sends. Furthermore, for each tag, the correspondence between the time-frequency resources allocated by the reader and the random number RN16 it sends may be one-to-one, many-to-one, or one-to-many, and there are no restrictions on this.

[0293] For example, taking tags 1 and 2 as examples, tag 1 sends its RN16 to the reader on a randomly selected time-frequency resource in time-frequency resource pool 1; tag 2 can also send its RN16 to the reader on a randomly selected time-frequency resource in time-frequency resource pool 1. Further, after receiving the RN16 of tags 1 and 2, the reader can allocate a corresponding time-frequency resource 2 for tag 1 and a corresponding time-frequency resource 3 for tag 2 from time-frequency resource pool 2. Of course, the reader can also allocate corresponding time-frequency resources for tags 1 and 2 from different time-frequency resource pools; this is not limited. Time-frequency resource 2 is associated with or corresponds to the RN16 of tag 1, and time-frequency resource 3 is associated with or corresponds to the RN16 of tag 2.

[0294] In one possible implementation, the information of the time-frequency resource 2 corresponding to tag 1 carried in the above ACK message can be the identification information of the time-frequency resource 2 (such as identifier, index, etc.).

[0295] For example, if the time-frequency resource 2 corresponding to tag 1 includes a first time slot in the time domain and a first frequency band in the frequency domain, then the identification information of the time-frequency resource 2 may include the number / index of the first time slot and the number / index of the first frequency band.

[0296] In another possible implementation, the information of the time-frequency resource 2 corresponding to tag 1 carried in the above ACK message may include time-domain parameters and frequency shift parameters.

[0297] In S904, the time-domain parameters can be referred to in the description of the time-domain parameters in S504, and the frequency shift parameters can be referred to in the description of the frequency shift parameters in S704. They will not be described in detail here.

[0298] S905: Tag 1 sends its permanent identification information to the reader on time and frequency resource 2.

[0299] In one possible implementation, tag 1 sends its permanent identification information to the reader on time-frequency resource 2, including: tag 1 sending its permanent identification information to the reader in OFDM format on time-frequency resource 2.

[0300] For example, the permanent identification information of tag 1 can be an Electronic Product Code (EPC) or a Tag Identification Number (TID), etc.

[0301] S905 can be referred to in the descriptions of S505 and S705 above, and will not be elaborated here.

[0302] In Implementation Method 3, tag 1 is used as an example to describe the method flow of Implementation Method 3 in detail. In the actual tag inventory process, there may be a larger number (or a large number) of tags. Each tag can be executed according to the implementation method corresponding to tag 1 (i.e., the content shown in S901 to S905). That is, each tag can interact with the reader or writer in a timely manner on its own corresponding and available time and frequency resources, without having to wait for identification to be completed one by one through the traditional tag inventory process. This can not only effectively improve the efficiency of tag inventory, but also significantly improve the identification efficiency, resource utilization and system performance of the RFID system.

[0303] Regarding the above-described embodiments one to three, it should be noted that:

[0304] (1) The above-mentioned implementation methods one to three can be implemented separately or in combination, and no specific limitation is made in this regard.

[0305] (2) The above focuses on describing the differences between implementation methods one to three. Except for the differences, implementation methods one to three can be referred to each other.

[0306] (3) The step numbers of the flowcharts described in Embodiments 1 to 3 above are only examples of the execution flow and do not constitute a restriction on the order of execution of the steps. There are no time dependencies between the steps in the various implementations of this application, and there is no strict execution order between them. In addition, not all the steps shown in the flowcharts are mandatory steps. Some steps can be added or deleted based on the actual needs of each flowchart.

[0307] In the embodiments provided above, the methods provided by the embodiments of this application have been described from the perspective of interaction between various devices. To implement the functions of the methods provided in the embodiments or implementations of this application, the first terminal device or the first device may include hardware structures and / or software modules, implementing the above functions in the form of hardware structures, software modules, or a combination of hardware structures and software modules. Whether a particular function is executed in the form of hardware structures, software modules, or a combination of hardware structures and software modules depends on the specific application and design constraints of the technical solution.

[0308] The module division in this embodiment is illustrative and represents only one logical functional division; in actual implementation, other division methods may be used. Furthermore, the functional modules in the various embodiments or implementations of this application can be integrated into a single processor, exist as separate physical entities, or be integrated into a single module. The integrated modules described above can be implemented in hardware or as software functional modules.

[0309] Similar to the above concept, as shown in FIG10, this application embodiment also provides a communication device 1000 for implementing the functions of the first terminal device or the first device in the above method. For example, the communication device 1000 can be a software module or a chip system. In this application embodiment, the chip system can be composed of chips or can include chips and other discrete devices. The communication device 1000 may include: a communication unit 1001 and a processing unit 1002.

[0310] In this embodiment, the communication unit 1001, also known as the transceiver unit, may include a sending unit and / or a receiving unit, respectively used to execute the sending and receiving steps of the first terminal device or the first device in the above method embodiments. The processing unit 1002 may be used to read instructions and / or data from the storage module so that the communication device 1000 implements the aforementioned method embodiments.

[0311] Optionally, the communication device 1000 may further include a storage unit 1003, which is equivalent to a storage module and can be used to store instructions and / or data.

[0312] The communication device provided in the embodiments of this application will be described in detail below with reference to Figures 10 and 11. It should be understood that the description of the device embodiments corresponds to the description of the method embodiments. Therefore, the contents not described in detail can be referred to the manner shown in Figures 4 and 5, Figure 7 and Figure 9 above. For the sake of brevity, they will not be repeated here.

[0313] The communication unit 1001 can also be referred to as a transceiver, transceiver, or transceiver device. The processing unit can also be referred to as a processor, processing board, processing module, or processing device. Optionally, the device in the communication unit 1001 used to implement the receiving function can be considered as a receiving unit, and the device in the communication unit 1001 used to implement the transmitting function can be considered as a transmitting unit; that is, the communication unit 1001 includes both a receiving unit and a transmitting unit. The communication unit can sometimes also be referred to as a transceiver, transceiver circuit, or transceiver unit. The receiving unit can sometimes be referred to as a receiver, receiver, or receiving circuit. The transmitting unit can sometimes be referred to as a transmitter, transmitter, or transmitting circuit.

[0314] When the communication device 1000 executes the process shown in Figure 4 of the above embodiment, the first terminal device is used:

[0315] The communication unit 1001 is used to receive a first message, the first message being used to query the permanent identification information of the terminal device, and the first message including system information for synchronization and information of a first resource set;

[0316] The communication unit 1001 is further configured to send a second message based on a first resource in the first resource set, the second message being used to request access.

[0317] The processing unit 1002 is used to process information and / or data, etc.

[0318] When the communication device 1000 executes the first device in the process shown in Figure 4 of the above embodiment:

[0319] The communication unit 1001 is used to send a first message, which is used to query the permanent identification information of the terminal device; the first message includes system information for synchronization and information of a first resource set.

[0320] The communication unit 1001 is further configured to receive a second message sent by the first terminal device based on a first resource in the first resource set; the second message is used to request access.

[0321] The processing unit 1002 is used to process information and / or data, etc.

[0322] The above are just examples. The processing unit 1002 and the communication unit 1001 can also perform other functions. For a more detailed description, please refer to the relevant descriptions in the method embodiments shown in Figures 4 and 5, Figure 7 and Figure 9 above. They will not be repeated here.

[0323] Figure 11 shows a communication device 1100 provided in an embodiment of this application. The communication device shown in Figure 11 can be a hardware circuit implementation of the communication device shown in Figure 10. This communication device 1100 can be applied to the flowcharts shown above to perform the functions of the first terminal device or the first device in the above method embodiments. For ease of explanation, Figure 11 only shows the main components of the communication device.

[0324] As shown in Figure 11, the communication device 1100 includes a communication interface 1101 and a processor 1102. The communication interface 1101 and the processor 1102 are coupled to each other. It is understood that the communication interface 1101 can be a transceiver or an input / output interface, or an interface circuit such as a transceiver circuit. Optionally, the communication device 1100 may further include a memory 1103 for storing instructions executed by the processor 1102, or storing input data required by the processor 1102 to execute instructions, or storing data generated after the processor 1102 executes instructions.

[0325] When the communication device 1100 is used to implement the methods shown in Figures 4, 5, 7 and 9, the communication interface 1101 is used to implement the functions of the communication unit 1001, and the processor 1102 is used to implement the functions of the processing unit 1002.

[0326] This embodiment does not limit the specific connection medium between the communication interface 1101, processor 1102, and memory 1103. In Figure 11, the memory 1103, processor 1102, and communication interface 1101 are connected via a communication bus 1104, which is represented by a thick line. The connection methods between other components are merely illustrative and not intended to be limiting. The communication bus 1104 can be divided into an address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used in Figure 11, but this does not indicate that there is only one bus or one type of bus.

[0327] When the aforementioned communication device is a chip, Figure 12 shows a simplified schematic diagram of the chip's device structure. The chip 1200 includes an interface circuit 1201 and one or more processors 1202. Optionally, the chip 1200 may also include a bus. Wherein:

[0328] The processor 1202 may be an integrated circuit chip with signal processing capabilities. In implementation, each step of the method for determining the service node information described above can be completed through integrated logic circuits in the hardware of the processor 1202 or through software instructions. The processor 1202 may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods and steps disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor.

[0329] The interface circuit 1201 can be used to send or receive data, instructions or information. The processor 1202 can use the data, instructions or other information received by the interface circuit 1201 to process the data, instructions or other information, and can send the processed information out through the interface circuit 1201.

[0330] Optionally, chip 1200 also includes memory 1203, which may include read-only memory and random access memory, and provides operation instructions and data to the processor. A portion of memory 1203 may also include non-volatile random access memory (NVRAM).

[0331] Optionally, the memory stores executable software modules or data structures, and the processor can execute corresponding operations by calling the operation instructions stored in the memory (which may be stored in the operating system).

[0332] Optionally, the chip can be used in the first terminal device or first device involved in the embodiments of this application. Optionally, the interface circuit 1201 can be used to output the execution result of the processor 1202. For the communication methods provided by one or more embodiments of this application, please refer to the foregoing embodiments, which will not be repeated here.

[0333] It should be noted that the functions of the interface circuit 1201 and the processor 1202 can be implemented through hardware design, software design, or a combination of hardware and software; no restrictions are imposed here.

[0334] This application also provides a computer-readable storage medium storing computer instructions for implementing the methods executed by the first terminal device or the first device in the above method embodiments.

[0335] For example, when the computer program is executed by the computer, it enables the computer to implement the method executed by the first terminal device or the first device in the above method embodiments.

[0336] This application also provides a computer program product containing instructions that, when executed by a computer, cause the computer to implement the method described above, which is executed by the first terminal device or the first device.

[0337] This application embodiment also provides a chip, including a processor, for calling computer programs or computer instructions stored in the memory, so that the processor executes the communication method of the implementation shown in Figures 4 and 5, Figure 7 and Figure 9.

[0338] In one possible implementation, the input of the chip corresponds to the receiving operation in the implementations shown in Figures 4 and 5, 7 and 9 above, and the output of the chip corresponds to the transmitting operation in the implementations shown in Figures 4 and 5, 7 and 9 above.

[0339] Optionally, the processor is coupled to the memory via an interface.

[0340] Optionally, the chip also includes a memory that stores computer programs or computer instructions.

[0341] The processor mentioned above can be a general-purpose central processing unit, a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits used to control the execution of a program through a communication method for the implementation shown in Figures 4, 5, 7, and 9. The memory mentioned above can be read-only memory (ROM) or other types of static storage devices capable of storing static information and instructions, such as random access memory (RAM).

[0342] It should be noted that, for the sake of convenience and brevity, the explanations and beneficial effects of the relevant content in any of the communication devices provided above can be referred to the corresponding service node information determination method embodiments provided above, and will not be repeated here.

[0343] In this application, the communication devices may further include a hardware layer, an operating system layer running on top of the hardware layer, and an application layer running on the operating system layer. The hardware layer may include hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory (also known as main memory). The operating system layer may be any one or more computer operating systems that implement business processing through processes, such as Linux, Unix, Android, iOS, or Windows. The application layer may include applications such as browsers, address books, word processing software, and instant messaging software.

[0344] The module division in this embodiment is illustrative and represents only one logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional modules in each embodiment of this application can be integrated into a single processor, exist as separate physical entities, or be integrated into a single module. The integrated modules described above can be implemented in hardware or as software functional modules.

[0345] Through the above description of the embodiments, those skilled in the art will clearly understand that the embodiments of this application can be implemented in hardware, firmware, or a combination thereof. When implemented in software, the above functions can be stored in a computer-readable medium or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any medium that facilitates the transfer of a computer program from one place to another. Storage media can be any available medium accessible to a computer. For example, but not limited to, computer-readable media can include RAM, ROM, electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, magnetic disk storage media, or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible to a computer. Furthermore, any connection can suitably be a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of the medium. As used in embodiments of this application, disks and discs include compact discs (CDs), laser discs, optical discs, digital video discs (DVDs), floppy disks, and Blu-ray discs, wherein disks typically magnetically copy data, while discs optically copy data using lasers. The combinations above should also be included within the scope of protection for computer-readable media.

[0346] In summary, the above descriptions are merely embodiments of this application and are not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made based on the disclosure of this application should be included within the scope of protection of this application.

Claims

1. A communication method characterized by comprising: A chip applied to a first terminal device or a terminal device, comprising: receiving a first message, the first message being used for querying permanent identification information of a terminal device, and the first message comprising system information used for synchronization and information of a first resource set; sending a second message based on a first resource in the first resource set, the second message being used for requesting access.

2. The method of claim 1, wherein, The system information comprises radio frame information and / or time slot information, and the method further comprises: performing synchronization processing based on the radio frame information and / or time slot information.

3. The method according to claim 1 or 2, characterized in that, The first resource set comprises a plurality of resources, and the resources comprise time domain resources and / or frequency domain resources; the method further comprises: selecting the first resource from the plurality of resources.

4. The method according to any one of claims 1 to 3, characterized in that, The second message comprises first information used for temporarily identifying the first terminal device, and the method further comprises: receiving a third message; the third message is used for confirming acceptance of the request of the second message, and the third message comprises the first information and second information, the second information being used for indicating a resource corresponding to the first terminal device, and the first information being associated with the resource corresponding to the first terminal device; sending the permanent identification information of the first terminal device on the resource corresponding to the first terminal device.

5. The method according to any one of claims 1-3, characterized in that, The second message comprises first information used for temporarily identifying the first terminal device, and the method further comprises: receiving a third message; the third message is used for confirming acceptance of the request of the second message, and the third message comprises the first information and second information, the second information being used for indicating a second resource corresponding to the first terminal device, and the first information being associated with the second resource, the second resource being different from the first resource; sending the permanent identification information of the first terminal device on the second resource.

6. The method of claim 5, wherein, The second resource belongs to a second resource set, and the first resource set comprises the second resource set.

7. The method according to claim 4 or 5, characterized in that, The resource is a time domain resource, the second information is information of a time domain resource corresponding to the first terminal device, and the information of the time domain resource comprises one or more of the following: identification information of the time domain resource, a time domain parameter.

8. The method according to claim 4 or 5, characterized in that, The resource is a frequency domain resource, the second information is information of a frequency domain resource corresponding to the first terminal device, and the information of the frequency domain resource comprises one or more of the following: identification information of the frequency domain resource, a frequency shift parameter.

9. The method of claim 4 or 5, wherein, The resource comprises a time domain resource and a frequency domain resource, and the second information comprises information of the time domain resource corresponding to the first terminal device and information of the frequency domain resource. The information of the time domain resource comprises one or more of the following: identification information of the time domain resource, a time domain parameter. The information of the frequency domain resource comprises one or more of the following: identification information of the frequency domain resource, a frequency shift parameter.

10. The method according to claim 8 or 9, characterized in that, The first terminal device sends the permanent identification information of the first terminal device in an orthogonal frequency division multiplexing (OFDM) form on the corresponding frequency domain resource.

11. The method according to claim 7 or 9, characterized in that, The time domain parameter is a ratio of the time domain resource to a time domain resource unit, or the time domain parameter is a total number of time domain resource units contained in the time domain resource.

12. The method of claim 8 or 9, wherein, The frequency shift parameter is an offset of the frequency domain resource, or the frequency shift parameter includes a frequency shift unit and a frequency shift multiple.

13. The method according to any one of claims 1-12, characterized in that, The method further includes: receiving a fourth message, the fourth message being used to indicate a preset condition; determining that the preset condition is met.

14. A communication method, comprising: application to a first device or a chip of the first device, comprising: sending a first message, the first message being used to query permanent identification information of a terminal device; the first message including system information used for synchronization and information of a first resource set; receiving a second message sent by the first terminal device based on a first resource in the first resource set; the second message being used to request access.

15. The method of claim 14, wherein, The second message includes first information used to temporarily identify the first terminal device; the method further includes: sending a third message to the first terminal device; the third message being used to confirm acceptance of the request of the second message, the third message including the first information and second information, the second information being used to indicate a resource corresponding to the first terminal device, and the first information being associated with the resource corresponding to the first terminal device; receiving the permanent identification information of the first terminal device on the resource corresponding to the first terminal device.

16. The method of claim 14, wherein, The method further includes: allocating a corresponding second resource to the first terminal device based on a second resource set, the second resource being different from the first resource.

17. The method of claim 16, wherein, The second message includes first information used to temporarily identify the first terminal device; the method further includes: sending a third message to the first terminal device; the third message being used to confirm acceptance of the request of the second message, the third message including the first information and second information, the second information being used to indicate the second resource, and the first information being associated with the second resource; receiving the permanent identification information of the first terminal device on the second resource.

18. The method of claim 16 or 17, wherein, The first resource set includes the second resource set.

19. The method of claim 15 or 17, wherein, The resource is a time domain resource, the second information is information of a time domain resource corresponding to the first terminal device, and the information of the time domain resource includes one or more of the following: identification information of the time domain resource, a time domain parameter.

20. The method of claim 15 or 17, wherein, The resource is a frequency domain resource, the second information is information of a frequency domain resource corresponding to the first terminal device, and the information of the frequency domain resource includes one or more of the following: identification information of the frequency domain resource, a frequency shift parameter.

21. The method of claim 15 or 17, wherein, The resource includes a time domain resource and a frequency domain resource, and the second information includes information of the time domain resource and information of the frequency domain resource corresponding to the first terminal device. The information of the time domain resource includes one or more of the following: identification information of the time domain resource, a time domain parameter. The information of the frequency domain resource includes one or more of the following: identification information of the frequency domain resource, a frequency shift parameter.

22. The method of claim 19 or 21, wherein, The time domain parameter is a ratio of the time domain resource to a time domain resource unit, or the time domain parameter is a total number of time domain resource units in the time domain resource.

23. The method of claim 20 or 21, wherein, The frequency shift parameter is an offset of the frequency domain resource, or the frequency shift parameter includes a frequency shift unit and a frequency shift multiple.

24. The method of claim 20 or 21, wherein, The frequency domain resource corresponding to the first terminal device and the frequency domain resource corresponding to the second terminal device satisfy a subcarrier orthogonal relationship.

25. The method of any one of claims 14-24, wherein, The system information comprises radio frame information and / or time slot information.

26. The method of any one of claims 14-25, wherein, The sending the first message comprises: The first message is sent according to a preset period.

27. The method of any one of claims 14-26, wherein, The method further comprises: A fourth message is sent, the fourth message being used to indicate a preset condition.

28. A communications device, characterized by The computer program product comprises computer programs or instructions, which, when executed on a computer, cause the computer to perform the method according to any one of claims 1 to 27.

29. A communications device, characterized by The computer program product comprises computer programs or instructions, which, when executed on a computer, cause the computer to perform the method according to any one of claims 1 to 27.

30. A computer-readable storage medium, characterized in that, The computer program product comprises computer programs or instructions, which, when executed on a computer, cause the computer to perform the method according to any one of claims 1 to 27.

31. A computer program product, characterised in that, The chip is used to read and execute computer programs or instructions in the memory, so as to realize the method according to any one of claims 1 to 27.

32. A chip, comprising: ​

Images