A communication method and a communication device

Abstract

This application provides a communication method and a communication device. The method includes: a terminal device receiving a first message from an access device, the first message including information about at least one transmission resource set corresponding to a terminal type, the at least one terminal type including the type of the terminal device; then the terminal device sending a second message to the access device based on the transmission resource set corresponding to the type of the terminal device, the second message being used to request access to the network. Therefore, in this method, the access device can allocate corresponding transmission resource sets for different types of terminal devices. This allows the terminal device to request network access from the access device based on the transmission resource set corresponding to its own type, avoiding waiting for network access based on time-division multiplexing, thereby improving the efficiency of terminal device network access and, consequently, the efficiency of network identification of terminal device types.

Description

Technical Field

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

[0002] Passive Internet of Things (AIoT) is a type of Internet of Things (IoT) technology. Its core characteristic is that terminal 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.

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

[0004] Currently, there are many types of passive terminal devices, such as backscatter and active transmitter types. However, when different types (or different capabilities) of terminal devices are inventoried in the same area, there is currently no solution to provide a unified resource allocation method for these different types (or different capabilities) of terminal devices to improve the efficiency of network identification / inventory of terminal devices. Summary of the Invention

[0005] This application proposes a communication method and a communication device for allocating corresponding transmission resources to different types of terminal devices to access the network, thereby improving the efficiency of the network in identifying the type of terminal device.

[0006] In a first aspect, embodiments of this application provide a communication method. This method can be applied to a terminal device, or a component of the 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 terminal device, or a device compatible with the terminal device. Taking the application of this method to a terminal device as an example, the method includes: the terminal device receiving a first message from an access device, the first message including information on a transmission resource set corresponding to at least one terminal type, the at least one terminal type including the type of the terminal device; the terminal device sending a second message to the access device based on the transmission resource set corresponding to the type of the terminal device, the second message being used to request access to the network.

[0007] In this application embodiment, the terminal device can be, but is not limited to, an IoT terminal device, namely a novel low-power, low-cost terminal device. The IoT terminal device 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. For example, the terminal device can be a tag, and the above-mentioned at least one terminal type can be at least one tag type. The access device can be a device that supports terminal device access, such as an access network device or a reader / writer, etc. The access device can also be a relay device with access and / or forwarding functions.

[0008] In one possible implementation, the aforementioned at least one terminal type can be terminal type information determined based on the capabilities (or characteristics, etc.) of the terminal device. For example, the aforementioned at least one terminal type includes terminal types with frequency shifting capabilities and terminal types without frequency shifting capabilities. The terminal types with frequency shifting capabilities and terminal types without frequency shifting capabilities are two types of terminal types determined based on whether the terminal device has frequency shifting capabilities.

[0009] In this application, the access device can allocate corresponding transmission resource sets for different types of terminal devices. This allows terminal devices to request network access from the access device based on the transmission resource set corresponding to their type, avoiding the waiting time for network access based on time-division multiplexing. This improves the efficiency of terminal device network access and, consequently, the efficiency of network identification of terminal device types. Time-division multiplexing refers to transmitting different signals from the same IoT connection at different time periods. The disadvantage of this method is that it generates relatively large latency, etc.

[0010] In conjunction with the first aspect, in one possible implementation, the first message also includes information indicating the at least one terminal type.

[0011] For example, the first message includes first information and second information, where the first information is used to indicate / identify the first terminal type and the second information is used to indicate / identify the second terminal type.

[0012] With this implementation, the terminal device can accurately determine whether the at least one terminal type includes the type of the terminal device based on the information used to indicate the at least one terminal type, and thus accurately determine the transmission resource set corresponding to the type of the terminal device.

[0013] In conjunction with the first aspect, in one possible implementation, the first message is used to query the type identification information of the terminal device, and the second message includes the temporary identification information of the terminal device. The method further includes: the terminal device receiving a third message sent by the access device, the third message including the temporary identification information of the terminal device and the first indication information, the first indication information being used to indicate the information of the first transmission resource corresponding to the type of the terminal device, and the temporary identification information of the terminal device being associated with the first transmission resource; and the terminal device sending the type identification information of the terminal device to the access device on the first transmission resource.

[0014] With this implementation, the terminal device can accurately determine its corresponding transmission resources based on its own temporary identification information, and then use its corresponding transmission resources to send the terminal device's type identification information to the access device.

[0015] In conjunction with the first aspect, in one possible implementation, the aforementioned first transmission resource belongs to the transmission resource set corresponding to the type of the terminal device. Through this implementation, the access device can continue to allocate corresponding available transmission resources to the terminal device based on the transmission resource set corresponding to the type of the terminal device.

[0016] In conjunction with the first aspect, in one possible implementation, the at least one terminal type may include, but is not limited to, one or more of the following:

[0017] Terminal types with frequency shifting capability, terminal types without frequency shifting capability, terminal types with active transmission carrier frequency capability, terminal types without active transmission carrier frequency capability, terminal types with power, or terminal types without power.

[0018] In the above scheme, the terminal types with frequency shifting capability and those without (or the terminal types with active transmission carrier frequency capability and those without active transmission carrier frequency capability, or the terminal types with energy and those without energy) are determined based on the capabilities of the terminal equipment itself, which can also be regarded as the type information determined based on the same classification standard.

[0019] For example, the unified classification standard for terminal types with and without frequency shifting capabilities is whether the terminal device has the ability to shift frequencies. Similarly, the unified classification standard for terminal types with and without active carrier frequency transmission capabilities is whether the terminal device has the ability to actively transmit carrier frequencies. Finally, the unified classification standard for terminal types with and without power is whether the terminal device itself has power.

[0020] For example, terminal types with frequency shifting capabilities and terminal types without active transmission carrier frequency capabilities (or terminal types with active transmission carrier frequency capabilities, or terminal types with energy, or terminal types without energy) can be regarded as type information determined based on different classification criteria.

[0021] In this embodiment, the access device can allocate corresponding transmission resources for different terminal types determined based on the same classification standard, or it can allocate corresponding transmission resources for different terminal types determined based on different classification standards. Through this implementation, one or more different terminal types can have corresponding transmission resources for transmission.

[0022] Secondly, embodiments of this application provide a communication method. This method can be applied to an access device, or a component of the access 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 access device, or a device compatible with the access device. Taking the application of this method to an access device as an example, the method includes: the access device sending a first message, the first message including information on at least one transmission resource set corresponding to a terminal type; the access device receiving a second message sent by the terminal device based on the transmission resource set corresponding to the terminal device's tag type, the second message being used to request access to the network.

[0023] In this application embodiment, the terminal device can be, but is not limited to, an IoT terminal device, namely a novel low-power, low-cost terminal device. The IoT terminal device 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. The access device can be a device that supports terminal device access, such as an access network device or a reader / writer. The access device can also be a relay device with access and / or forwarding functions.

[0024] In this application, the access device can allocate corresponding transmission resource sets for different types of terminal devices. This allows terminal devices to request network access from the access device based on the transmission resource set corresponding to their type, avoiding the waiting time for network access based on time-division multiplexing. This improves the efficiency of terminal device network access and, consequently, the efficiency of network identification of terminals (or tags). Time-division multiplexing refers to transmitting different signals from the same IoT connection at different time periods. The disadvantage of this method is that it generates significant latency, among other issues.

[0025] In conjunction with the second aspect, in one possible implementation, the first message also includes information indicating the at least one terminal type.

[0026] This implementation method enables the terminal device to determine whether the terminal device type is included in the at least one terminal type, thereby accurately determining the transmission resource set corresponding to the terminal device.

[0027] In conjunction with the second aspect, in one possible implementation, the first message is used to query the type identification information of the terminal device, and the second message includes temporary identification information of the terminal device. The method further includes: the access device sending a third message to the terminal device, the third message including the temporary identification information of the terminal device and first indication information, the first indication information indicating the information of the first transmission resource corresponding to the type of the terminal device, and the temporary identification information of the terminal device being associated with the first transmission resource; the access device receiving the type identification information of the terminal device on the first transmission resource. Through this implementation, the terminal device can accurately obtain its corresponding transmission resource, and thus can transmit the type identification information of the terminal device on the corresponding transmission resource.

[0028] In conjunction with the second aspect, in one possible implementation, the first transmission resource belongs to the transmission resource set corresponding to the type of the terminal device. Through this implementation, the access device can allocate corresponding transmission resources for the terminal device from the transmission resource set corresponding to the type of the terminal device for subsequent transmission.

[0029] In conjunction with the second aspect, in one possible implementation, the at least one terminal type includes one or more of the following:

[0030] Terminal types with frequency shifting capability, terminal types without frequency shifting capability, terminal types with active transmission carrier frequency capability, terminal types without active transmission carrier frequency capability, terminal types with power, or terminal types without power.

[0031] In this embodiment, the access device can allocate corresponding transmission resources for different terminal types determined based on the same classification standard, or it can allocate corresponding transmission resources for different terminal types determined based on different classification standards. Through this implementation, one or more different terminal types can have corresponding transmission resources for transmission.

[0032] Thirdly, this application also provides a communication device, which is a terminal device or a chip corresponding to a 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.

[0033] In one possible design, the communication device includes a processor configured to support the communication device in performing corresponding functions of the terminal device 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.

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

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

[0036] Fourthly, this application also provides a communication device, which is an access device or a chip corresponding to an access device. The communication device has the function of implementing the second 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.

[0037] In one possible design, the communication device includes a processor configured to support the communication device in performing the corresponding functions of the access device 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.

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

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

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

[0041] 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 possible implementation thereof through logic circuits or execution code instructions.

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

[0043] Eighthly, a computer program product storing instructions is provided, which, when executed by a processor, implements the methods of either the first or second aspect and any possible implementation thereof.

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

[0045] In a tenth aspect, a communication system is provided, the communication system comprising a terminal device and an access device, the terminal device being configured to implement the first aspect and any possible implementation thereof, and the access device being configured to implement the second aspect and any possible implementation thereof.

[0046] 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 described with reference to the technical effects that can be achieved by any of the first and second aspects or any of the first and second aspects, and will not be repeated here. Attached Figure Description

[0047] Figure 1 A schematic diagram illustrating tag reading and writing for a passive or semi-passive Internet of Things (IoT) system.

[0048] Figure 2 This is a schematic diagram illustrating the process of a reader / writer performing an inventory check on tags.

[0049] Figure 3 This is a schematic diagram of a communication system applicable to an embodiment of this application;

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

[0051] Figure 5 This application provides a schematic flowchart of the method for Embodiment 1.

[0052] Figure 6 This application provides a schematic flowchart of the method for Embodiment 2.

[0053] Figure 7 A schematic diagram of the method flow for Embodiment 3 provided in this application;

[0054] Figure 8A This is a schematic diagram illustrating the interaction between a reader / writer and tags 1 and 2 in an embodiment of this application.

[0055] Figure 8B This is a schematic diagram illustrating the interaction between another reader / writer in an embodiment of this application and tag 1 and tag 2 respectively;

[0056] Figure 9 This is a schematic diagram of the structure of a communication device according to an embodiment of this application;

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

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

[0059] The 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. 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.

[0060] The following explanations will cover some terms and concepts used in the embodiments of this application. It should be noted that these explanations are intended to make the embodiments of this application easier to understand and should not be construed as limiting the scope of protection claimed in this application.

[0061] 1) Terminal type:

[0062] In this embodiment of the application, terminal devices can be classified according to a set classification standard, and then one or more terminal types can be assigned / set. The set classification standard may include, but is not limited to, one or more of the following:

[0063] (1) The capabilities (or functions, or characteristics) of the terminal equipment; (2) The types of terminal equipment; (3) The usage level of the terminal equipment.

[0064] Furthermore, the terminal type involved in the embodiments of this application can also be a terminal type defined by current standards / solutions.

[0065] When the terminal device is a tag, the terminal type is also called the tag type. When the terminal device is an RFID card, the terminal type is also called the RFID card type.

[0066] For example, taking the terminal device as a tag, 3GPP defines three types of tags for Ambient IoT as follows:

[0067] Tag type A: No energy storage, no independent signal generation / amplification, i.e., backscatter transmission;

[0068] Tag type B: It has energy storage but no independent signal generation, i.e., backscatter transmission, and the stored energy can be used to amplify the reflected signal;

[0069] Tag type C: It has energy storage and independent signal generation, i.e., it is a radio frequency (RF) device used for transmission.

[0070] For example, taking the terminal device as a tag, IEEE 802.11bp defines four tag types for ambient power (AMP) as follows:

[0071] Tag type 1: Monostatic backscatter with fullduplex;

[0072] Tag type 2: Bistatic backscatter;

[0073] Tag type 3: Active transmitter;

[0074] Tag type 4: Allows 802.11 devices to enhance AMP features.

[0075] The above description uses the tag types defined by 3GPP for passive IoT and the tag types defined by IEEE 802.11bp for AMP as examples. However, the embodiments of this application are not limited to the above tag types, and different tag types can be obtained according to other preset standards.

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

[0077] Among them, time-domain resources can also be called time-domain resources or time-domain resources, etc.

[0078] For example, a network device is used as the reader / writer, and a terminal device is used as the tag. The reader / writer allocating corresponding time-domain resources to the tag can be understood as the reader / writer allocating available resources such as frames, subframes, time slots, or symbols to the tag. For example, if the reader / writer allocates radio frame #1 to the tag, then the tag can transmit data on radio frame #1.

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

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

[0081] Frequency domain resources can also be called frequency domain resources or frequency resources, etc.

[0082] For example, taking a network device as the reader and a terminal device as the tag, the reader allocating corresponding frequency domain resources to the tag can be understood as the reader allocating available subcarriers such as SC, RB, TBG, or RE to the tag. For example, if the reader allocates RB0 to the tag, then the tag can transmit data on RB0.

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

[0084] Among them, time-frequency domain resources include time-domain resources and frequency-domain resources.

[0085] For example, taking a network device as the reader and a terminal device as the tag, the reader's allocation of corresponding time-frequency domain resources to the tag can be understood as the reader allocating both available time-domain resources and available frequency-domain resources to the tag.

[0086] Time-domain resources can include resources such as frames, subframes, time slots, or symbols. Frequency-domain resources can include resources such as subcarriers (SC, RB, TBG, or RE).

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

[0088] Furthermore, unless otherwise stated, the ordinal numbers such as "first," "second," or "1," "2," etc. (except in special cases representing 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, sequence, priority, or importance of multiple objects. For example, label 1 and label 2 are only used to distinguish different labels and do not indicate that the size, priority, or importance of these two labels are different.

[0089] In this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. 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 noted that their intended meanings are consistent unless the distinction is emphasized.

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

[0091] The foregoing has introduced some terms and concepts involved in the embodiments of this application. The following describes the technical background, application scenarios and devices involved in the embodiments of this application.

[0092] Figure 1This diagram illustrates tag reading and writing in a passive or semi-passive Internet of Things (IoT) system. Current RFID technology employs Time Division Multiple Access (TDMA) to perform RFID tag inventory processes. The reader uses the Additive Link On-line Hawaii (ALOHA) protocol to identify each tag individually and retrieve information or data from its storage area. The reader is a specific example of an access device, and the tag is a specific example of a terminal device. This tag could be an AIoT tag, for example.

[0093] like Figure 1 As shown, it illustrates a schematic diagram of tag reading and writing in a passive Internet of Things (IoT) system, specifically including the following steps:

[0094] S101: The AIoT application (AIoT APP) sends the inventory rules to the reader.

[0095] Accordingly, the reader receives the inventory rules.

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

[0097] Among them, inventory rules are also called access rules.

[0098] S102: The reader performs an inventory check on the tags and obtains the tag identifiers.

[0099] The reader performs an inventory check on the tags according to the inventory rules, for example, an inventory check is performed on the tags to be connected every hour, and the identifier of the tags to be connected is obtained.

[0100] It should be understood that the process of a reader inventorying tags can be understood as the process of the reader establishing a connection and interacting with the tags to obtain information from each other. Typically, each tag has a corresponding identifier, which can be an electronic product code (EPC) or a tag identifier (TID), etc.

[0101] During the inventory process, the tag sends its identifier to the reader, allowing the reader to know which tags are within its coverage area. The reader can then report the identifiers of the tags within its coverage area to the middleware and / or server.

[0102] S103: The reader obtains information about the tag's storage area from the tag based on the tag's identifier.

[0103] After completing the above operations, the reader can obtain information about the storage area of ​​the connected tag.

[0104] Step S103 is an optional step.

[0105] S104: The reader / writer feeds back the inventory information and the information in the tag's storage area to the AIoT APP.

[0106] Regarding the process of the reader performing an inventory check on the tags in step S102 above, refer to... Figure 2 As shown, the specific process is as follows:

[0107] S201: The reader sends a Select command to the tag.

[0108] Prior to S201, the reader first receives the inventory command and then generates the selection command. This inventory command can include a range of tags, which can refer to a location range or an identification range, such as an EPC / TID within a specific location range.

[0109] After receiving (listening to) a selection command, the tag checks whether it falls within the tag's scope. If it does, it continues to listen for subsequent query commands; if it does not, the tag will not perform the following steps, i.e., it will not take any action.

[0110] S202: The reader sends a query command to the tag.

[0111] Correspondingly, when the tag receives a query command, it generates a random number.

[0112] S203: The tag sends a random number to the reader.

[0113] For example, the random number is a 16-bit random number, which can also be represented as RN-16.

[0114] S204: The reader sends an acknowledgment (ACK) command to the tag.

[0115] After receiving the random number, the reader sends an acknowledgment command to the tag, which contains the random number.

[0116] S205: Verify that the random number in the label verification command is correct.

[0117] If the random number in the confirmation command is the same as the random number sent by the tag to the reader, the verification result is correct, and the subsequent steps are executed; if the random number in the confirmation command is different from the random number sent by the tag to the reader, the verification result is incorrect, and the subsequent steps are not executed.

[0118] S206: The tag sends its identifier to the reader. For example, the tag's EPC.

[0119] After the tag sends its identifier to the reader, it enters a brief sleep state.

[0120] After receiving the tag's identifier, the reader completes the inventory of that tag.

[0121] Optionally, the reader will continue to send query responses (QueryRep) to the tags. If the query response is a negative acknowledgment (NAK) response, it indicates that the reader failed to receive the tag's identifier, and the tag needs to re-enter the arbitration state. Conversely, if the response is positive, it indicates that the reader successfully received the tag's identifier, and the tag enters the acknowledgment state. After receiving the query response, the tag will decrement its original random number by 1. Furthermore, steps S203 to S206 above will be re-executed until all tags have been inventoried.

[0122] The above Figure 1 and Figure 2 The process shown can also be applied to passive IoT (P-IoT), where the AIoT tags can be replaced with P-IoT tags accordingly.

[0123] Based on the above, RFID technology uses radio frequency to read and write tags (or RFID cards) to identify them and exchange information and data. However, currently, there are many types of passive tags, such as backscattering and active transmitting types. But when different types of tags (or tags with different capabilities) are inventoried in the same area, there is currently no solution to provide a unified and efficient inventory method for these different types of tags (or tags with different capabilities) to achieve better system transmission.

[0124] To address the aforementioned problems, this application proposes a communication method and a communication device to provide a unified and efficient inventory method for different types of tags (or tags with different capabilities), thereby achieving better system transmission. The method and device are based on the same inventive concept. Since the methods and devices solve problems based on similar principles, their implementations can be mutually referenced, and repeated details will not be elaborated further.

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

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

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

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

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

[0130] For example, Figure 3 This is a schematic diagram of the architecture of a wireless communication system applicable to embodiments of this application. Figure 3 As shown, 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... Figure 3 110a and 110b may also include at least one terminal device, such as Figure 3 The series consists of 120a to 120j. 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, 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... Figure 3 The mobile phones included 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 connect to micro-station 110b, connect to laptop 120g, and connect to printer 120h. Mobile phone 120j can control drone 120i.

[0131] 1) Terminal equipment:

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

[0133] 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, a label (such as an AIoT label) can also be used to refer to the IoT terminal device. The embodiments of this application do not limit the specific form of the IoT terminal device.

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

[0135] 2) Network equipment:

[0136] 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 the corresponding program instructions themselves. 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.

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

[0138] 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). The CU performs the functions of the base station's Radio Resource Control (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 a 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 meaning. 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. RA equipment can be a macro base station (such as...) Figure 3 110a in the text), can also be a micro base station or an indoor station (such as... Figure 3 In 110b), it can also be a relay node or a donor node, etc. The embodiments of this application do not limit the specific technology or device form used in the network equipment.

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

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

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

[0142] The roles of network devices and terminal devices can be relative, for example, Figure 3 The helicopter or drone 120i 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, meaning that 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, 120i is also a network device relative to 110a. Therefore, both network devices and terminal devices can be collectively referred to as communication devices. Figure 3 110a and 110b can be referred to as communication devices with network equipment functions. Figure 3 The 120a-120j in the text can be referred to as communication devices with terminal equipment functions.

[0143] It should be noted that, Figure 3 The communication system shown is not intended to limit the communication systems to which the embodiments of this application can be applied. Therefore, the methods provided in the embodiments of this application are 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 them.

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

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

[0146] 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 the 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 "first device," etc. The "access device" in the embodiments of this application can be replaced with "reader," "second 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.

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

[0148] This application provides a communication method, which can be applied to, but is not limited to, other methods. Figure 3The network architecture is shown. This method can be executed by a terminal device (or an access device), by a module of the terminal device (or access 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 terminal device (or access device). Furthermore, this application does not specifically limit the specific structure and number of the execution entities (such as terminal devices and access devices) of the method provided in the embodiments of this application, as long as communication can be performed according to the method provided in the embodiments of this application by running a program that records the code of the method provided in the embodiments of this application. For ease of description, the interaction between a terminal device and an access device 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 adaptively executed.

[0149] See Figure 4 As shown, the method provided in this application embodiment may include the following steps:

[0150] S401: The access device sends the first message, and the corresponding terminal device receives the first message.

[0151] The first message includes information about a set of transmission resources corresponding to at least one terminal type, wherein the at least one terminal type includes the type of the terminal device.

[0152] In one possible implementation, the aforementioned at least one terminal type can be terminal type information determined based on the capabilities (or characteristics, etc.) of the terminal device. For example, the aforementioned at least one terminal type includes terminal types with frequency shifting capabilities and terminal types without frequency shifting capabilities. The terminal types with frequency shifting capabilities and terminal types without frequency shifting capabilities are two types of terminal types determined based on whether the terminal device has frequency shifting capabilities.

[0153] For example, the above-mentioned at least one terminal type may include, but is not limited to, one or more of the following:

[0154] (1) Terminal types with frequency shifting capability;

[0155] For example, a terminal type with frequency shifting capability can refer to a type of terminal equipment that supports switching or changing the frequency of signals.

[0156] (2) Terminal types without frequency shifting capability;

[0157] For example, a terminal type without frequency shifting capability can refer to a type of terminal equipment that does not support switching or changing signal frequencies.

[0158] (3) Terminal types with active carrier frequency transmission capability;

[0159] For example, a terminal type with active carrier frequency transmission capability refers to a type of terminal device that can combine baseband signals or information signals with high-frequency carrier signals to form a new composite signal and transmit it in wireless communication.

[0160] (4) Terminal types that do not have the ability to actively transmit carrier frequencies;

[0161] For example, a terminal type with active carrier frequency transmission capability can refer to a type of terminal device that cannot combine baseband signals or information signals with high-frequency carrier signals to form a new composite signal and transmit it in wireless communication.

[0162] (5) Types of terminals with energy;

[0163] For example, an energy-enabled terminal type can refer to a type of terminal device that can store or generate energy.

[0164] (6) Terminal types without energy.

[0165] For example, a terminal type without energy can refer to a type of terminal device that cannot store or generate energy.

[0166] In one possible implementation, the first message also includes information indicating the at least one terminal type.

[0167] For example, the first message also includes first information and second information. The first information is used to indicate / identify a first terminal type (such as a terminal type with frequency shift capability), and the second information is used to indicate / identify a second terminal type (such as a terminal type without frequency shift capability). The first information corresponds to or is associated with the transmission resource set corresponding to the first terminal type (or information about the transmission resource set corresponding to the first terminal type), and the second information corresponds to or is associated with the transmission resource set corresponding to the second terminal type (or information about the transmission resource set corresponding to the second terminal type).

[0168] For example, the first information may be indication or identification information of a first terminal type, and the second information may be indication or identification information of a second terminal type.

[0169] In one possible implementation, the information of the transmission resource set corresponding to the terminal type can be the index, identifier, or number of the transmission resource set.

[0170] In this embodiment of the application, the set of transmission resources corresponding to the terminal type may include one or more transmission resources. Furthermore, the transmission resources may include, but are not limited to, time-domain resources and / or frequency-domain resources.

[0171] In one possible implementation, the first message may further include system information, which includes radio frame information and / or time slot information; the method in this application embodiment may further include: the first terminal device performing synchronization processing with the access device based on the radio frame information and / or time slot information.

[0172] For example, the system information mentioned above includes the radio frame number and the timeslot number. Optionally, the system information may also include symbols. After receiving the system information, the terminal device can adjust the position of its own frames and timeslots based on the radio frame number and timeslot number, or based on the radio frame number, timeslot number, and symbols, to align with the radio frames and timeslots on the access device side. This ensures that the terminal device and the access device are in time synchronization, thereby guaranteeing the accuracy and efficiency of communication between them.

[0173] S402: The terminal device sends a second message based on the transmission resource set corresponding to its type. Correspondingly, the access device receives the second message.

[0174] The second message is used to request network access.

[0175] In one possible implementation, the first message is used to query the type identification information of the terminal device, and the second message includes temporary identification information of the terminal device. The method of this application embodiment may further include the following steps:

[0176] The access device sends a third message to the terminal device, and the terminal device receives the third message accordingly. The third message is used to confirm or respond to the access request of the terminal device. The third message includes temporary identification information of the terminal device and first indication information. The first indication information is used to indicate the information of the first transmission resource corresponding to the type of the terminal device. The temporary identification information of the terminal device is associated with the first transmission resource. Then, the terminal device sends its type identification information to the access device on the first transmission resource. Accordingly, the access device receives the type identification information of the terminal device on the first transmission resource.

[0177] In the above, the temporary identification information of the terminal device can be, but is not limited to, a random number generated for the terminal device, such as a 16-bit random number RN16 or a random number of smaller / larger bits; or the temporary identification information of the terminal device can be used to indicate a 16-bit random number RN16 or a random number of smaller / larger bits generated by the terminal device.

[0178] In this embodiment, the first transmission resource allocated by the access device to the terminal device after receiving the second message from the terminal device may or may not belong to the transmission resource set corresponding to the type of the terminal device; no specific limitation is imposed in this regard. In one possible implementation, the first transmission resource belongs to the transmission resource set corresponding to the type of the terminal device.

[0179] In the embodiments of this application, the first transmission resource may include, but is not limited to, time domain resources and / or frequency domain resources, and may also include spatial domain resources or code domain resources.

[0180] For example, the information of the first transmission resource mentioned above may be an index, identifier, or number of the first transmission resource, etc.

[0181] For example, if the first transmission resource is a time-domain resource and corresponds to the first subframe, then the information of the first transmission resource can be the frame number, number, or index corresponding to the first subframe.

[0182] For example, if the first transmission resource is a frequency domain resource, corresponding to the first frequency band, then the information of the first transmission resource can be the frequency band number, corresponding number, or index of the first frequency band. For instance, the frequency band number corresponding to the first frequency band can be the frequency band number specified in the protocol.

[0183] The above steps S401-S402 are an example of an interaction between a terminal device and an access device to illustrate the solution of this application embodiment. In practical applications, there may be multiple terminal devices. Each terminal device can be implemented by referring to the above steps S401-S402. Here, each terminal device will not be described in detail.

[0184] Based on the above, in this application, the access device can allocate corresponding transmission resource sets for different types of terminal devices. In this way, the terminal device can request network access from the access device based on the transmission resource set corresponding to its own type, which can avoid waiting to access the network based on time division multiplexing, thereby improving the efficiency of terminal device access to the network and thus improving the efficiency of the network in identifying the type of terminal device.

[0185] The following is based on Figure 4 The scheme shown is applied to the tag inventory scenario of the Internet of Things as an example, and several specific implementation methods are used to illustrate the above. Figure 4 The proposed solution will be described in detail.

[0186] Implementation Method 1:

[0187] In implementation method one, based on the above... Figure 4The illustrated scheme uses tag 1 (Tag#1) and tag 2 (Tag#2) as examples of terminal devices. Tag 1 has a first tag type, and tag 2 has a second tag type. The first tag type refers to a tag type with frequency shift capability, and the second tag type refers to a tag type without frequency shift capability. The scheme of this application embodiment is described in detail below. See also... Figure 5 As shown, the method flow of this first embodiment includes the following steps:

[0188] S501: The reader sends a Select message (as described above) Figure 4 (Example of the fourth message in the scheme shown) Accordingly, tag 1 and tag 2 receive the selection message, and then tag 1 and tag 2 enter the inventory cycle.

[0189] The selection message is used to select tags that meet the criteria.

[0190] S501 can be referred to the above introduction of S201, and will not be repeated here.

[0191] S502: The reader sends a query message (as described above). Figure 4 (Example of the first message in the scheme shown) Accordingly, tag 1 and tag 2 receive the query message.

[0192] The query message includes information about time-frequency domain resource pool #1 corresponding to tag types with frequency shift capability and information about time-frequency domain resource pool #2 corresponding to tag types without frequency shift capability (as mentioned above). Figure 4 (Example of information about the resource set corresponding to at least one terminal type in the scheme shown).

[0193] In this embodiment, the time-frequency domain resources in time-frequency domain resource pool #1 can be continuous or discontinuous, without specific limitations. The same applies to time-frequency domain resource pool #2.

[0194] In one possible implementation, the query message also includes indication information (or identification information) for tag types with frequency shift capability and indication information (or identification information) for tag types without frequency shift capability.

[0195] For example, the query message includes a first field and a second field. The first field includes a tag type field #1 and a resource indication field #2. The tag type field #1 (e.g., the ID corresponding to a tag type with frequency shift capability) indicates a tag type with frequency shift capability, and the resource indication field #2 indicates information about the time-frequency domain resource pool #1 corresponding to the tag type with frequency shift capability. The second field includes a tag type field #3 and a resource indication field #4. The tag type field #3 (e.g., the ID corresponding to a tag type without frequency shift capability) indicates a tag type without frequency shift capability, and the resource indication field #4 indicates information about the time-frequency domain resource pool #2 corresponding to the tag type without frequency shift capability.

[0196] In one possible implementation, the query message may also include system information for synchronization, which may include radio frame information and / or time slot information. Then, after receiving this system information, tags 1 and 2 can perform synchronization processing with the reader based on the radio frame information and / or time slot information.

[0197] For example, the system information includes the radio frame number and the timeslot number. Optionally, the system information may also include a symbol. Tag 1 and Tag 2 adjust the positions of their own radio frames and timeslots based on the radio frame number and timeslot number, or based on the radio frame number, timeslot number, and symbol, respectively, to align with the radio frames and timeslots on the reader side. This ensures that Tag 1 and Tag 2 are synchronized with the reader in time, thereby guaranteeing the accuracy and efficiency of communication.

[0198] In addition, the system information mentioned above may also include frequency domain information. Tag 1 and Tag 2 can also synchronize with the reader in the frequency domain based on this frequency domain information. The specific implementation can be referred to the time domain synchronization method described above, which will not be detailed here.

[0199] S503: Tag 1 determines the time-frequency domain resource pool #1 corresponding to the tag type with frequency shift capability based on its own tag type with frequency shift capability.

[0200] In S503, since tag 1 is a tag type with frequency shift capability, the information of time-frequency domain resource pool #1 corresponding to the tag type with frequency shift capability is determined from the query message. Then, the location of time-frequency domain resource pool #1 can be determined based on the information of time-frequency domain resource pool #1.

[0201] For example, the information for time-frequency domain resource pool #1 could be the number, index, or identifier corresponding to time-frequency domain resource pool #1.

[0202] S504: Tag 2 determines the time-frequency domain resource pool #2 corresponding to the tag type without frequency shift capability based on its own tag type without frequency shift capability.

[0203] In S504, since tag 2 is a tag type without frequency shift capability, the information of time-frequency domain resource pool #2 corresponding to the tag type without frequency shift capability is determined from the query message. Then, the location of time-frequency domain resource pool #2 can be determined based on the information of time-frequency domain resource pool #2.

[0204] For example, the information for time-frequency domain resource pool #2 could be the number, index, or identifier corresponding to time-frequency domain resource pool #2.

[0205] The above S503 and S504 can be executed synchronously or asynchronously, and there is no specific restriction on the order of execution. For example, S503 can be executed before S504, or S504 can be executed before S503, or S503 and S504 can be executed simultaneously.

[0206] S505: Tag 1 sends its RN16 to the reader on time-frequency domain resource #1 in time-frequency domain resource pool #1. Correspondingly, the reader receives Tag 1's RN16.

[0207] In one possible implementation, label 1 can randomly select time-frequency domain resource #1 from time-frequency domain resource pool #1. Here, time-frequency domain resource #1 can be either a continuous time-frequency domain resource in time-frequency domain resource pool #1 or a non-contiguous time-frequency domain resource in time-frequency domain resource pool #1; there is no restriction on which one is selected.

[0208] In this embodiment of the application, the reader can also allocate the corresponding time-frequency domain resource #1 from the time-frequency domain resource pool #1 for tag 1, and then send the information of the allocated time-frequency domain resource #1 to tag 1.

[0209] S506: Tag 2 sends its RN16 to the reader on time-frequency domain resource #2 in time-frequency domain resource pool #2. The reader receives Tag 2's RN16 accordingly.

[0210] In one possible implementation, label 2 can randomly select time-frequency domain resource #2 from time-frequency domain resource pool #2. Here, time-frequency domain resource #2 can be either a continuous time-frequency domain resource in time-frequency domain resource pool #2 or a non-contiguous time-frequency domain resource in time-frequency domain resource pool #2; there is no restriction on which one is selected.

[0211] In this embodiment of the application, the reader can also allocate the corresponding time-frequency domain resource #2 from the time-frequency domain resource pool #2 for the tag 2, and then send the information of the allocated time-frequency domain resource #2 to the tag 2.

[0212] The above-mentioned S505 and S506 can be executed synchronously or asynchronously, and there is no specific restriction on the order of execution. For example, S505 can be executed before S506, or S506 can be executed before S505, or S505 and S506 can be executed simultaneously.

[0213] S507: The reader sends an acknowledgment (ACK) message 1 to tag 1, and tag 1 receives the acknowledgment message 1 accordingly.

[0214] Confirmation message 1 is used to confirm or respond to the access of tag 1. Confirmation message 1 includes information about the time-frequency domain resource #3 corresponding to tag 1 and RN16 of tag 1.

[0215] In one possible implementation, prior to S507, the reader can allocate a corresponding time-frequency domain resource #3 for tag 1 from the time-frequency domain resource pool #1.

[0216] In another possible implementation, prior to S507, the reader can allocate a corresponding time-frequency domain resource #3 for tag 1 from other time-frequency domain resource pools. These other time-frequency domain resource pools can be mutually exclusive (i.e., they do not have the same time-frequency domain resources) or partially overlapping (i.e., they have some of the same time-frequency domain resources), without restriction.

[0217] In another possible implementation, prior to S507, it also includes: the reader / writer can allocate corresponding time-frequency domain resources #3 for tag types with frequency shift capability.

[0218] In the above, time-frequency domain resource #3 can be a continuous time-frequency domain resource or a non-continuous time-frequency domain resource; no specific restrictions are imposed here.

[0219] S508: The reader sends confirmation message 2 to tag 2, and tag 2 receives confirmation message 2 accordingly.

[0220] Confirmation message 2 is used to confirm or respond to the access of tag 2. Confirmation message 2 includes information about the time-frequency domain resource #4 corresponding to tag 2 and RN16 of tag 2.

[0221] In one possible implementation, prior to S508, the reader can allocate a corresponding time-frequency domain resource #4 for tag 2 from the time-frequency domain resource pool #2.

[0222] In another possible implementation, prior to S508, the reader can allocate corresponding time-frequency domain resources #4 for tag 2 from other time-frequency domain resource pools. These other time-frequency domain resource pools and time-frequency domain resource pool #2 can be mutually exclusive (i.e., they do not have the same time-frequency domain resources) or partially overlapping (i.e., they have some of the same time-frequency domain resources); there are no restrictions on this.

[0223] In another possible implementation, prior to S508, it also includes: the reader / writer can allocate corresponding time-frequency domain resources #4 for tag types that do not have frequency shift capability.

[0224] In the above, time-frequency domain resource #4 can be a continuous time-frequency domain resource or a non-continuous time-frequency domain resource; no specific restrictions are imposed here.

[0225] In one possible implementation, the reader can also broadcast the same acknowledgment message to both tag 1 and tag 2 (i.e., S507 and S508 above can be combined into one step). This acknowledgment message includes information about time-frequency domain resource #3 corresponding to tag 1 and RN16 of tag 1, as well as information about time-frequency domain resource #4 corresponding to tag 2 and RN16 of tag 2; wherein, the information about time-frequency domain resource #3 and RN16 of tag 1 are mutually associated / bound, and the information about time-frequency domain resource #4 and RN16 of tag 2 are mutually associated / bound.

[0226] After receiving the acknowledgment message, tag 1 can accurately determine the corresponding time-frequency domain resource #3 as its subsequent transmission resource based on tag 1's RN16. After receiving the acknowledgment message, tag 2 can accurately determine the corresponding time-frequency domain resource #4 as its subsequent transmission resource based on tag 2's RN16.

[0227] S509: Tag 1 determines the location of time-frequency domain resource #3 based on the information of time-frequency domain resource #3.

[0228] For example, if time-frequency domain resource #3 corresponds to subframe #1 and frequency band #1, the information of time-frequency domain resource #3 can include the subframe #1 number and the frequency band number, number, or index corresponding to frequency band #1. Thus, tag 1 can determine subframe #1 and frequency band #1 based on the subframe #1 number and the frequency band number / number / index corresponding to frequency band #1. The frequency band number corresponding to frequency band #1 can be the frequency band number specified in the protocol.

[0229] S510: Tag 2 determines the location of time-frequency domain resource #4 based on the information of time-frequency domain resource #4.

[0230] For example, if time-frequency domain resource #4 corresponds to subframe #2 and frequency band #2, the information of time-frequency domain resource #4 may include the subframe #2 number and the frequency band number, number, or index corresponding to frequency band #2. Thus, tag 2 can determine subframe #2 and frequency band #2 based on the subframe #2 number and the frequency band number / number / index corresponding to frequency band #2. The frequency band number corresponding to frequency band #2 can be the frequency band number specified in the protocol.

[0231] S511: Tag 1 sends its type identification information to the reader at location #3 in the time-frequency domain resource. Correspondingly, the reader receives the type identification information of Tag 1.

[0232] S512: Tag 2 sends its type identification information to the reader at location #4 in the time-frequency domain. Correspondingly, the reader receives the type identification information of Tag 2.

[0233] In the above, the execution order of steps (S507, S509, S511) corresponding to label 1 and steps (S508, S510, S512) corresponding to label 2 is not specifically restricted. They can be executed synchronously or asynchronously, and the order can be adjusted according to the actual situation. For example, S508 may be executed after S509 (or S511).

[0234] The above steps illustrate how the reader can allocate corresponding time-frequency domain resources for tag types with and without frequency-shift capabilities. In practical applications, the reader can also allocate corresponding time-domain (or frequency-domain) resources for tag types with and without frequency-shift capabilities, as described above. Further details are omitted here.

[0235] In Implementation Method 1, the reader can allocate corresponding time-frequency domain resources to tag types with and without frequency-shift capability, respectively. Then, it broadcasts the information of the time-frequency domain resources corresponding to the tag types with and without frequency-shift capability to each tag. In this way, each tag can choose to use the time-frequency domain resources corresponding to its own tag type (with or without frequency-shift capability) to exchange information or data with the reader in a timely manner, without having to wait for each tag to be identified one by one through the traditional tag inventory process. This can effectively improve the efficiency of tag inventory, and significantly improve the identification efficiency, resource utilization, and system performance of the RFID system.

[0236] Implementation Method Two:

[0237] Compared to Implementation Method 1, the main difference in Implementation Method 2 is that the first tag type is a tag type with active carrier frequency transmission capability, while the second tag type is a tag type without active carrier frequency transmission capability. See also Figure 6 As shown, the method flow of this second embodiment includes the following steps:

[0238] S601: The reader sends a selection message (as described above) Figure 4 (Example of the fourth message in the scheme shown); accordingly, tag 1 and tag 2 receive the selection message, and then tag 1 and tag 2 enter the inventory cycle.

[0239] The selection message is used to select tags that meet the criteria.

[0240] S601 can refer to the steps of S501 above, and will not be repeated here.

[0241] S602: The reader sends a query message (as described above) Figure 4 (Example of the first message in the scheme shown) Accordingly, tag 1 and tag 2 receive the query message.

[0242] The query information includes information on time-frequency domain resource pool #1 corresponding to tag types with active carrier frequency transmission capability and information on time-frequency domain resource pool #2 corresponding to tag types without active carrier frequency transmission capability (as mentioned above). Figure 4 (Example of information about the resource set corresponding to at least one terminal type in the scheme shown).

[0243] In one possible implementation, the query message also includes indication information (or identification information) for tag types with active carrier frequency transmission capability and indication information (or identification information) for tag types without active carrier frequency transmission capability.

[0244] For details on S602, please refer to the introduction / content of S502 above; it will not be elaborated here.

[0245] S603: Tag 1 determines the information of time-frequency domain resource pool #1 corresponding to the tag type with active transmission carrier frequency capability, based on its own tag type.

[0246] S604: Tag 2 determines the information of time-frequency domain resource pool #2 corresponding to the tag type that does not have the ability to actively transmit carrier frequencies, based on its own tag type.

[0247] S605: Tag 1 sends its RN16 to the reader on time-frequency domain resource #1 in time-frequency domain resource pool #1. Correspondingly, the reader receives Tag 1's RN16.

[0248] S606: Tag 2 sends its RN16 to the reader on time-frequency domain resource #2 in time-frequency domain resource pool #2. The reader receives Tag 2's RN16 accordingly.

[0249] S607: The reader sends confirmation message 1 to tag 1, and tag 1 receives confirmation message 1 accordingly.

[0250] Confirmation message 1 is used to confirm or respond to the access of tag 1. Confirmation message 1 includes information about the time-frequency domain resource #3 corresponding to tag 1 and RN16 of tag 1.

[0251] S608: The reader sends confirmation message 2 to tag 2, and tag 2 receives confirmation message 2 accordingly.

[0252] Confirmation message 2 is used to confirm or respond to the access of tag 2. Confirmation message 2 includes information about the time-frequency domain resource #4 corresponding to tag 2 and RN16 of tag 2.

[0253] S609: Tag 1 determines the location of time-frequency domain resource #3 based on the information of time-frequency domain resource #3.

[0254] S610: Tag 2 determines the location of time-frequency domain resource #4 based on the information of time-frequency domain resource #4.

[0255] S611: Tag 1 sends its type identification information to the reader at location #3 in the time-frequency domain. Correspondingly, the reader receives the type identification information of Tag 1.

[0256] S612: Tag 2 sends its type identification information to the reader at location #4 in the time-frequency domain. Correspondingly, the reader receives the type identification information of Tag 2.

[0257] The above S605-S612 can be referred to one by one as S505-S512 in the first embodiment above, and will not be repeated here.

[0258] The above steps illustrate how the reader can allocate corresponding time-frequency domain resources to tag types with and without active carrier frequency transmission capabilities. In practical applications, the reader can also allocate corresponding time-domain (or frequency-domain) resources to tag types with and without active carrier frequency transmission capabilities, as described above. Further details are omitted here.

[0259] In implementation method two, the reader can allocate corresponding time-frequency domain resources to tag types with and without active carrier frequency transmission capabilities, respectively. Then, it broadcasts the information of the corresponding time-frequency domain resources to each tag. In this way, each tag can choose to use either the tag type with or without active carrier frequency transmission capabilities to interact with the reader in a timely manner, eliminating the need for the traditional tag inventory process of waiting for each tag to be identified individually. This effectively improves the efficiency of tag inventory and significantly enhances the identification efficiency, resource utilization, and system performance of the RFID system.

[0260] Implementation Method 3:

[0261] Compared to Implementation Method 1 or Implementation Method 2 described above, the main difference in Implementation Method 3 is that the first tag type is an energy-containing tag type, and the second tag type is a non-energy-containing tag type. See also... Figure 7 As shown, the method flow of this third embodiment includes the following steps:

[0262] S701: The reader sends a selection message (as described above) Figure 4 (Example of the fourth message in the scheme shown) Accordingly, tag 1 and tag 2 receive the selection message, and then tag 1 and tag 2 enter the inventory cycle.

[0263] The selection message is used to select tags that meet the criteria.

[0264] S701 can refer to the steps of S501 above, and will not be repeated here.

[0265] S702: The reader sends a query message (as described above) Figure 4 (Example of the first message in the scheme shown) Accordingly, tag 1 and tag 2 receive the query message.

[0266] The query message includes information about time-frequency domain resource pool #1 corresponding to tag types with energy and information about time-frequency domain resource pool #2 corresponding to tag types without energy (as mentioned above). Figure 4 (Example of information about the resource set corresponding to at least one terminal type in the scheme shown).

[0267] In one possible implementation, the query message may also include indications of tag types with energy and tag types without energy, or the query message may also include identification information of tag types with energy and tag types without energy.

[0268] For details on S702, please refer to the description / content in S502 (or S602) above. It will not be elaborated here.

[0269] S703: Tag 1 determines the information of the time-frequency domain resource pool #1 corresponding to the tag type with energy based on its own energy tag type.

[0270] S704: Tag 2 determines the information of the time-frequency domain resource pool #2 corresponding to the tag type without energy, based on its own tag type without energy.

[0271] S705: Tag 1 sends its RN16 to the reader on time-frequency domain resource #1 in time-frequency domain resource pool #1. Correspondingly, the reader receives Tag 1's RN16.

[0272] S706: Tag 2 sends its RN16 to the reader on time-frequency domain resource #2 in time-frequency domain resource pool #2. The reader receives Tag 2's RN16 accordingly.

[0273] S707: The reader sends confirmation message 1 to tag 1, and tag 1 receives confirmation message 1 accordingly.

[0274] Confirmation message 1 is used to confirm or respond to the access of tag 1. Confirmation message 1 includes information about the time-frequency domain resource #3 corresponding to tag 1 and RN16 of tag 1.

[0275] S708: The reader sends confirmation message 2 to tag 2, and tag 2 receives confirmation message 2 accordingly.

[0276] Confirmation message 2 is used to confirm or respond to the access of tag 2. Confirmation message 2 includes information about the time-frequency domain resource #4 corresponding to tag 2 and RN16 of tag 2.

[0277] S709: Tag 1 determines the location of time-frequency domain resource #3 based on the information of time-frequency domain resource #3.

[0278] S710: Tag 2 determines the location of time-frequency domain resource #4 based on the information of time-frequency domain resource #4.

[0279] S711: Tag 1 sends its type identification information to the reader at location #3 in the time-frequency domain. Correspondingly, the reader receives the type identification information of Tag 1.

[0280] S712: Tag 2 sends its type identification information to the reader at location #4 in the time-frequency domain resource. Correspondingly, the reader receives the type identification information of Tag 2.

[0281] The above S705-S712 can be referred to one-to-one with S505-S512 in the first embodiment or S605-S612 in the second embodiment, which will not be repeated here.

[0282] The above steps illustrate how the reader can allocate corresponding time-frequency domain resources to tag types with and without power. In practical applications, the reader can also allocate corresponding time-domain (or frequency-domain) resources to tag types with and without power respectively. The specific implementation can be found in the steps described above, and will not be detailed here.

[0283] In implementation method three, the reader can allocate corresponding time-frequency domain resources for powered and unpowered tag types respectively. Then, it broadcasts the information of the time-frequency domain resources corresponding to powered and unpowered tag types to each tag. In this way, each tag can choose to use the time-frequency domain resources corresponding to powered or unpowered tag types to interact with the reader in a timely manner, without having to wait for each tag to be identified one by one through the traditional tag inventory process. This can effectively improve the efficiency of tag inventory, and significantly improve the identification efficiency, resource utilization, and system performance of the RFID system.

[0284] For example, based on the above-described implementation methods, Figure 8A This example illustrates an interaction between the reader and tags 1 and 2, respectively. (See attached diagram) Figure 8A As shown, see Figure 8A As shown, firstly, the reader can broadcast a selection message, which is received by tag 1. Next, the reader broadcasts a query message, which is also received by tag 1. This query message includes system information, information about time-domain resource pool #1 corresponding to the first tag type, and information about time-domain resource pool #2 corresponding to the second tag type. Tag 1, based on its first tag type, determines the use of time-domain resource pool #1 and its location based on that information. Tag 2, based on its second tag type, also determines the use of time-domain resource pool #1 and its location based on that information. Furthermore, tag 1 can select time-domain resource 1 from time-domain resource pool 1 and send its RN16 to the reader on time-domain resource 1; tag 2 can select time-domain resource 2 from time-domain resource pool 2 and send its RN16 to the reader on time-domain resource 2.

[0285] After receiving the RN16 of tag 1, the reader can allocate time domain resource 3 for tag 1 from time domain resource pool 1; after receiving the RN16 of tag 2, the reader can allocate time domain resource 4 for tag 2 from time domain resource pool 2.

[0286] After this, the reader sends an acknowledgment message 1 to tag 1, which includes the RN16 of tag 1 and the information of the corresponding time domain resource 3; the reader can also send an acknowledgment message 2 to tag 2, which includes the RN16 of tag 2 and the information of the corresponding time domain resource 4.

[0287] After receiving confirmation message 1, tag 1 can determine the location of time domain resource 3 based on the information of time domain resource 3, and then send the type identification information of tag 1 to the reader on time domain resource 3. After receiving confirmation message 2, tag 2 can determine the location of time domain resource 4 based on the information of time domain resource 4, and then send the type identification information of tag 2 to the reader on time domain resource 4.

[0288] For example, based on the above-described implementation methods, Figure 8B This example illustrates another interaction between the reader and tags 1 and 2, respectively. Figure 8B The interactive diagram shown is Figure 8A The interaction content in the diagrams shown is the same, but the main difference is that after the reader receives the RN16 of tag 1, it can allocate time-domain resource 3 for tag 1 from the new time-domain resource pool #3; after the reader receives the RN16 of tag 2, it can allocate time-domain resource 4 for tag 2 from the new time-domain resource pool #4. Time-domain resource pool #3 can be different from time-domain resource pool #1, and time-domain resource pool #4 can be different from time-domain resource pool #2.

[0289] Figure 8A and Figure 8B In this context, the sizes of time-domain resource pools 1 and 2, as well as time-domain resource pools 3 and 4, are not specifically limited. Furthermore, the time-domain resources in each time-domain resource pool can be contiguous or non-contiguous. Figure 8A and Figure 8B The continuous cases shown are merely one example.

[0290] For example, in Figures 8A-8B In this context, the first tag type and the second tag type can be one-to-one correspondences between tag types with frequency shifting capability and tag types without frequency shifting capability; or, the first tag type and the second tag type can be one-to-one correspondences between tag types with active transmission carrier frequency capability and tag types without active transmission carrier frequency capability; or, the first tag type and the second tag type can be one-to-one correspondences between tag types with energy and tag types without energy.

[0291] Of course, the above Figure 8A and Figure 8B The example of a reader allocating resources for the first and second tag types is merely an illustration. In practical applications, the reader can allocate resources for more or fewer tag types. For instance, the reader can allocate resources for one or more of the following tag types: tag types with frequency shifting capability, tag types without frequency shifting capability, tag types with active carrier frequency transmission capability, tag types without active carrier frequency transmission capability, tag types with power, or tag types without power.

[0292] The following explanations are provided regarding the above-described embodiments one through three:

[0293] (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.

[0294] (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.

[0295] (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.

[0296] 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 terminal device or access 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.

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

[0298] Similar to the above concept, such as Figure 9 As shown, this application embodiment also provides a communication device 900 for implementing the functions of the terminal device or access device in the above method. For example, the communication device 900 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 900 may include: a communication unit 901 and a processing unit 902.

[0299] In this embodiment, the communication unit 901, also referred to as the transceiver unit, may include a sending unit and / or a receiving unit, respectively used to perform the sending and receiving steps of the terminal device or access device in the above method embodiments. The processing unit 902 may be used to read instructions and / or data from the storage module so that the communication device 900 implements the aforementioned method embodiments.

[0300] Optionally, the communication device 900 may also include a storage unit 903, which is equivalent to a storage module and can be used to store instructions and / or data.

[0301] The following, combined with Figures 9 to 10 This application provides a detailed description of the communication device provided in its embodiments. It should be understood that the descriptions of the device embodiments correspond to the descriptions of the method embodiments; therefore, any content not described in detail can be found above. Figures 4 to 7 The method shown is used to achieve this, and for the sake of simplicity, it will not be described in detail here.

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

[0303] When the communication device 900 is applied in the above embodiment Figure 4 In the process shown, when the terminal device is: the communication unit 901 is used to receive a first message, the first message including information on a transmission resource set corresponding to at least one terminal type, the at least one terminal type including the type of the terminal device; the communication unit 901 is also used to send a second message based on the transmission resource set corresponding to the type of the terminal device, the second message being used to request network access.

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

[0305] When the communication device 900 is applied in the above embodiment Figure 4 When accessing a device in the process shown: the communication unit 901 is used to send a first message, the first message including information on at least one transmission resource set corresponding to a terminal type; the communication unit 901 is also used to receive a second message sent by the terminal device based on the transmission resource set corresponding to the tag type of the terminal device, the second message being used to request access to the network.

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

[0307] The above is just an example. Processing unit 902 and communication unit 901 can also perform other functions. For a more detailed description, please refer to the above. Figure 4 and Figure 5 , Figure 7 as well as Figure 9 The relevant descriptions in the method embodiments shown are not repeated here.

[0308] like Figure 10 The image shown is a communication device 1000 provided in an embodiment of this application. Figure 10 The communication device shown can be Figure 9 The diagram illustrates one hardware circuit implementation of the communication device 1000. This communication device 1000 can be applied to the flowchart shown above, performing the functions of the terminal device or access device in the method embodiments described above. For ease of explanation, Figure 10 Only the main components of the communication device are shown.

[0309] like Figure 10 As shown, the communication device 1000 includes a communication interface 1001 and a processor 1002. The communication interface 1001 and the processor 1002 are coupled to each other. It is understood that the communication interface 1001 can be a transceiver or an input / output interface, or an interface circuit such as a transceiver circuit. Optionally, the communication device 1000 may further include a memory 1003 for storing instructions executed by the processor 1002, or storing input data required by the processor 1002 to execute instructions, or storing data generated after the processor 1002 executes instructions.

[0310] When the communication device 1000 is used to achieve the above Figures 4 to 7 In the method shown, the communication interface 1001 is used to implement the functions of the communication unit 901, and the processor 1002 is used to implement the functions of the processing unit 902.

[0311] This application embodiment does not limit the specific connection medium between the communication interface 1001, processor 1002, and memory 1003. This application embodiment... Figure 10 The memory 1003, processor 1002, and communication interface 1001 are connected via a communication bus 1004. The communication bus 1004 is in... Figure 10 The connections between other components are shown in bold lines only and are not intended to be limiting. The communication bus 1004 can be divided into address bus, data bus, control bus, etc. For ease of illustration, Figure 10 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0312] When the aforementioned communication device is a chip. Figure 11 A simplified schematic diagram of a chip device structure is shown. The chip 1100 includes interface circuitry 1101 and one or more processors 1102. Optionally, the chip 1100 may also include a bus. Wherein:

[0313] Processor 1102 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 by the integrated logic circuitry in the hardware of processor 1102 or by instructions in software form. The processor 1102 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.

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

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

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

[0317] Optionally, the chip can be used in the terminal device or access device involved in the embodiments of this application. Optionally, the interface circuit 1101 can be used to output the execution result of the processor 1102. 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.

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

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

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

[0321] This application also provides a computer program product containing instructions that, when executed by a computer, cause the computer to implement the method executed by the terminal device or access device in the above method embodiments.

[0322] This application also provides a chip, including a processor, for calling computer programs or computer instructions stored in the memory, so that the processor executes the above-mentioned... Figures 4 to 7 The communication method shown is a specific implementation method.

[0323] In one possible implementation, the chip's input corresponds to the above... Figures 4 to 7 The receiving operation shown in the implementation corresponds to the output of the chip described above. Figures 4 to 7 The sending operation in the implementation shown.

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

[0325] Optionally, the chip may also include a memory that stores computer programs or computer instructions.

[0326] The processor mentioned above can be a general-purpose central processing unit, a microprocessor, an application-specific integrated circuit (ASIC), or one or more devices used to control the above. Figures 4 to 7 The illustrated implementation is an integrated circuit for program execution using a communication method. 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).

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

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

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

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

[0331] 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 in that, Chips used in terminal devices or terminal devices include: Receive a first message, the first message including information on a set of transmission resources corresponding to at least one terminal type, the at least one terminal type including the type of the terminal device; Based on the set of transmission resources corresponding to the type of the terminal device, a second message is sent, which is used to request network access.

2. The method according to claim 1, characterized in that, The first message also includes information indicating the at least one terminal type.

3. The method according to claim 1 or 2, characterized in that, The first message is used to query the type identification information of the terminal device, the second message includes the temporary identification information of the terminal device, and the method further includes: Receive a third message, the third message including the temporary identification information and the first indication information, the first indication information being used to indicate the information of the first transmission resource corresponding to the type of the terminal device, and the temporary identification information being associated with the first transmission resource; On the first transmission resource, the type identification information of the terminal device is sent.

4. The method according to claim 3, characterized in that, The first transmission resource belongs to the transmission resource set corresponding to the type of the terminal device.

5. The method according to any one of claims 1-4, characterized in that, The at least one terminal type includes one or more of the following: Terminal types with frequency shifting capability, terminal types without frequency shifting capability, terminal types with active transmission carrier frequency capability, terminal types without active transmission carrier frequency capability, terminal types with power, or terminal types without power.

6. A communication method, characterized in that, Chips used in access devices or access devices include: Send a first message, the first message including information on at least one set of transmission resources corresponding to a terminal type; The receiving terminal device sends a second message based on the transmission resource set corresponding to the tag type of the terminal device, the second message being used to request network access.

7. The method according to claim 6, characterized in that, The first message also includes information indicating the at least one terminal type.

8. The method according to claim 6 or 7, characterized in that, The first message is used to query the type identification information of the terminal device, the second message includes the temporary identification information of the terminal device, and the method further includes: Send a third message, the third message including the temporary identification information and the first indication information, the first indication information being used to indicate the information of the first transmission resource corresponding to the type of the terminal device, and the temporary identification information being associated with the first transmission resource; On the first transmission resource, the type identification information of the terminal device is received.

9. The method according to claim 8, characterized in that, The first transmission resource belongs to the transmission resource set corresponding to the tag type of the terminal device.

10. The method according to any one of claims 6-9, characterized in that, The at least one terminal type includes one or more of the following: Terminal types with frequency shifting capability, terminal types without frequency shifting capability, terminal types with active transmission carrier frequency capability, terminal types without active transmission carrier frequency capability, terminal types with power, or terminal types without power.

11. A communication device, characterized in that, It includes units or modules for performing the method as described in any one of claims 1 to 5, or units or modules for performing the method as described in any one of claims 6 to 10.

12. A communication device, characterized in that, It includes a processor and a memory, the memory being used to store program instructions, the processor causing the method as described in any one of claims 1 to 5, or the method as described in any one of claims 6 to 10, to be executed when the program instructions are executed.

13. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer-readable program or instructions that, when executed on a communication device, cause the method as described in any one of claims 1 to 5 to be performed, or the method as described in any one of claims 6 to 10 to be performed.

14. A computer program product, characterized in that, The computer program product includes a computer program or instructions that, when run on a computer, cause the computer to perform the method as described in any one of claims 1 to 5, or the method as described in any one of claims 6 to 10.

15. A chip, characterized in that, The chip is configured to read and execute computer programs or instructions in a memory to implement the method as described in any one of claims 1 to 5, or the method as described in any one of claims 6 to 10.

Images