Tag status management method and communication device

Abstract

The present application provides a tag state management method and a communication device. The method includes: a first tag receives a first message from an access network device, the first message is used to request inventorying of an inventory target tag, and the first tag belongs to the inventory target tag; the first tag accesses the access network device; the first tag sends a second message, the second message is used to request registration with a core network device; the first tag switches from a deregistered state to a registered state after sending the second message; according to the method, after the second message is sent, the state of the first tag switches from a deregistered state to a registered state, thereby properly managing the state of the tag in a scenario where the tag is inventoried by using air interface wireless technology.

Description

[Technical Field]

[0001] This application claims priority to Chinese Patent Application No. 202211174355.3, entitled "TAG STATE MANAGEMENT METHOD AND COMMUNICATION APPARATUS," filed with the State Intellectual Property Office of the People's Republic of China on September 26, 2022, which is incorporated herein by reference in its entirety.

[0002] TECHNICAL FIELD Embodiments of the present application relate to the field of communications, and more particularly to a tag status management method and a communication device. [Background technology]

[0003] With the development of technology and environmental protection requirements, the passive Internet of Things is expected to have larger application and deployment, and it is predicted that hundreds of billions of devices will be covered in the future. However, tags in the passive Internet of Things (e.g., passive tags or semi-passive tags) have simple functions and usually need to rely on external excitation to transmit information to the outside. The external excitation is usually from a reader / writer. Currently, the passive Internet of Things has characteristics such as a short communication distance between a card reader and a tag and complex implementation of the tag's state. This limits the deployment of the passive Internet of Things.

[0004] In terms of features, in the solution, the inventory capabilities of the reader / writer (including operations such as reading, writing, killing, and locking tags) are integrated into the access network device, so that tags in the passive Internet of Things are excited and then inventoried by using air interface wireless technology, increasing the communication distance between tags in the passive Internet of Things and card readers, and implementing unified management for tags in the passive Internet of Things through the access network device.

[0005] However, it does not specify how to manage the state of tags in a scenario where tags in a passive Internet of Things are inventoried by using air interface wireless technology. Summary of the Invention

[0006] The present application provides a tag status management method and communication device to manage the status of tags in a scenario where tags are inventoried by using air interface wireless technology.

[0007] According to a first aspect, there is provided a tag state management method. The method may be performed by a first tag or by a module or unit in the first tag. For ease of description, the module or unit in the first tag will hereinafter be collectively referred to as the first tag.

[0008] The method includes: a first tag receiving a first message from an access network device, the first message being used to request inventorying of an inventory target tag, the first tag belonging to the inventory target tag; the first tag accessing the access network device; the first tag sending a second message, the second message being used to request registration with a core network device; and the first tag switching from an unregistered state to a registered state after sending the second message.

[0009] There can be one or more inventoried tags.

[0010] The method may alternatively be described as follows: a first tag receives a first message from an access network device, the first message being used to request that the first tag be inventoried; the first tag accesses the access network device; the first tag sends a second message, the second message being used to request registration with the core network device; and the first tag switches from an unregistered state to a registered state after sending the second message.

[0011] Optionally, the first message includes a selection command, which is used to select one or more inventoried tags, and the selection command may include conditions that must be met by the tags. After receiving the first message, the first tag determines whether the first tag meets the conditions in the selection command, and when the first tag meets the conditions in the selection command, the first tag knows that the first tag is inventoried.

[0012] According to the method, after the second message used to request registration to the core network device is sent, the state of the first tag is switched from the unregistered state to the registered state, thereby properly managing the state of the tag in a scenario where the tag is inventoried by using air interface wireless technology. Furthermore, compared with the complicated state changes in the prior art, the simplification of the state of the tag to the registered state and the unregistered state helps to simplify the management of the state of the tag.

[0013] Regarding the first aspect, in a possible implementation, the first message is further used to excite the inventoried tag.

[0014] For example, when the inventoried tag is a passive tag or a semi-passive tag, the first message may also be used to excite the inventoried tag.

[0015] Regarding the first aspect or any implementation thereof, in another possible implementation, after the first tag sends the second message, the method further includes: the first tag receiving a third message, where the third message indicates that the first tag has successfully registered with the core network device. Switching from an unregistered state to a registered state after the first tag sends the second message includes: the first tag switching from an unregistered state to a registered state after receiving the third message. In other words, the third message after the second message triggers the first tag to switch from an unregistered state to a registered state.

[0016] According to the method, when the first tag is successfully registered, the state of the first tag is switched from a deregistered state to a registered state to properly manage the state of the tag in a scenario where the tag is inventoried by using air interface wireless technology.

[0017] Regarding the first aspect or any implementation thereof, in another possible implementation, after the first tag sends the second message, the method further includes: the first tag sends a fourth message, where the fourth message is used to request that authentication be performed on the first tag; the first tag receives a fifth message, where the fifth message indicates that authentication on the first tag has been successful; and switching from an unregistered state to a registered state after the first tag sends the second message includes: the first tag switches from an unregistered state to a registered state after receiving the fifth message. In other words, the fifth message after the second message triggers the first tag to switch from an unregistered state to a registered state.

[0018] According to the method, when authentication for the first tag is successful, the state of the first tag is switched from a deregistered state to a registered state to properly manage the state of the tag in a scenario where the tag is inventoried by using air interface wireless technology.

[0019] Regarding the first aspect or any implementation thereof, in another possible implementation, after the first tag sends the second message, the method further includes: the first tag receiving a sixth message, where the sixth message is used to request the first tag to perform authentication on an authentication server; the first tag sending a seventh message when the authentication on the authentication server is successful, where the seventh message indicates that the authentication on the authentication server is successful; switching from an unregistered state to a registered state by the first tag after sending the second message includes: the first tag switching from an unregistered state to a registered state after sending the seventh message.

[0020] In other words, the seventh message after the second message triggers the first tag to switch from an unregistered state to a registered state.

[0021] According to the method, when authentication on the authentication server corresponding to the first tag is successful, the state of the first tag is switched from an unregistered state to a registered state to properly manage the state of the tag in a scenario where the tag is inventoried by using air interface wireless technology.

[0022]

[0013] With respect to the first aspect or any implementation thereof, in another possible implementation, the method further includes: the first tag starting a first timer; the first tag switching from a registered state to a deregistered state when the first timer expires.

[0023] According to the method, the registered state of the first tag is maintained through a timer to properly manage the state of the tag in a scenario where the tag is inventoried by using air interface wireless technology.

[0024] Regarding the first aspect or any implementation thereof, in another possible implementation, the method further includes: the first tag in the registered state resets a first timer based on a message between the first tag and the core network device.

[0025]

[0013] With respect to the first aspect or any implementation thereof, in another possible implementation, the method further includes: a first tag in a registered state receives an eighth message, the eighth message indicating to inventory a next tag; and the first tag switches from the registered state to the unregistered state based on the eighth message.

[0026] According to the method, when the inventory for the first tag is completed, the state of the first tag is switched from an unregistered state to a registered state to properly manage the state of the tag in a scenario where the tag is inventoried by using air interface wireless technology.

[0027] Regarding the first aspect or any implementation thereof, in another possible implementation, a packet header of at least one of the second message, the third message, the fourth message, the fifth message, the sixth message, or the seventh message includes a protocol identification code, and the packet header is 1 byte in length.

[0028] According to the method, the packet header of the message between the first tag and the core network device occupies one byte, which is reduced compared to the two-byte packet header of existing common non-access stratum (NAS) messages, which is useful for implementing inventory in the tag by using air interface wireless technology.

[0029] Regarding the first aspect or any implementation thereof, in another possible implementation, the packet header of at least one of the second message, the third message, the fourth message, the fifth message, the sixth message, or the seventh message includes a protocol identification code and a security header type, and the sum of the length of the protocol identification code and the length of the security header type is 1 byte.

[0030] According to the method, the sum of the length of the protocol identification code and the length of the security header type in the packet header of the message between the first tag and the core network device is 1 byte, which is reduced by 1 byte compared to 2 bytes in existing common NAS messages, which is useful for implementing inventory in the tag by using air interface wireless technology.

[0031] Regarding the first aspect or any implementation thereof, in another possible implementation, when the security header type indicates that security protection is implemented, the packet header further includes a message authentication code and a sequence number.

[0032] According to a second aspect, there is provided a tag state management method. The method may be performed by a core network device, or by a module or unit in the core network device. For ease of description, the modules or units in the core network device will hereinafter be collectively referred to as the core network device.

[0033] The method includes: a core network device receives a first request message used to request inventorying of inventoried tags; the core network device sends a first message to the inventoried tags through an access network device, the first message used to request inventorying of the inventoried tags; the core network device receives a second message from a first tag among the inventoried tags, the second message used to request registration with the core network device; and after receiving the second message, the core network device switches the state of the first tag stored in the core network device from an unregistered state to a registered state.

[0034] The method may alternatively be described as follows: a core network device receives a first request message used to request inventorying of tags to be inventoried, the tags to be inventoried including a first tag; the core network device sends a first message to the first tag through an access network device, the first message used to request inventorying of the first tag; the core network device receives a second message from the first tag, the second message used to request registration with the core network device; and after receiving the second message, the core network device switches the state of the first tag stored in the core network device from an unregistered state to a registered state. Regarding the second aspect, in a possible implementation, the first message is further used to excite the inventoried tag.

[0035] For example, when the inventoried tag is a passive tag or a semi-passive tag, the first message may also be used to excite the inventoried tag.

[0036] Regarding the second aspect, in a possible implementation, after the second message is received, the method further includes: the core network device sending a third message to the first tag, where the third message indicates that the first tag has been successfully registered with the core network device. Switching the state of the first tag stored in the core network device from a deregistered state to a registered state after the core network device receives the second message includes: after the core network device sends the third message, switching the state of the first tag stored in the core network device from a deregistered state to a registered state.

[0037] Regarding the second aspect or any implementation thereof, in another possible implementation, after the second message is received, the method further includes: the core network device receiving a fourth message from the first tag, where the fourth message is used to request performing authentication on the first tag; the core network device sending a fifth message to the first tag, where the fifth message indicates that the authentication on the first tag has been successful; switching the state of the first tag stored in the core network device from a deregistered state to a registered state after the core network device receives the second message includes: the core network device switching the state of the first tag stored in the core network device from a deregistered state to a registered state after sending the fifth message.

[0038] Regarding the second aspect or any implementation thereof, in another possible implementation, after the second message is received, the method further includes: the core network device sending a sixth message to the first tag, where the sixth message is used to request performing authentication on an authentication server; the core network device receiving a seventh message from the first tag, where the seventh message indicates that the authentication on the authentication server has been successful; switching the state of the first tag stored in the core network device from a deregistered state to a registered state after the core network device receives the second message includes: the core network device switching the state of the first tag stored in the core network device from a deregistered state to a registered state after receiving the seventh message.

[0039] Regarding the second aspect or any implementation thereof, in another possible implementation, the method further includes: the core network device starts a second timer when the state of the first tag is switched from an unregistered state to a registered state; and when the second timer expires, the core network device switches the state of the first tag stored in the core network device from the registered state to the unregistered state.

[0040] Regarding the second aspect or any implementation thereof, in another possible implementation, the method further includes: the core network device resets a second timer based on a message between the first tag and the core network device.

[0041] Regarding the second aspect or any implementation thereof, in another possible implementation, the method further includes: when the inventory for the first tag is completed, the core network device switches the state of the first tag stored in the core network device from a registered state to a deregistered state.

[0042] Regarding the second aspect or any implementation thereof, in another possible implementation, the method further includes: the core network device sends a ninth message to the access network device, where the ninth message indicates that the inventory for the first tag has finished.

[0043] Regarding the second aspect or any implementation thereof, in another possible implementation, the method further includes: the core network device assigns a first identifier to the first tag after receiving the second message, and the core network device sends a correspondence between the first identifier and the first tag to the access network device.

[0044] Regarding the second aspect or any implementation thereof, in another possible implementation, the method further includes: the core network device receives a correspondence between the second identifier and the first tag from the access network device.

[0045] Regarding the second aspect or any implementation thereof, in another possible implementation, the method further includes: when the state of the first tag is switched from a registered state to a deregistered state, the core network device releases the correspondence between the first identifier and the first tag and / or the correspondence between the second identifier and the first tag.

[0046] Based on the above method, when the state of the first tag is switched from a registered state to a deregistered state, the identifier used for transmitting messages of the first tag between the access network device and the core network device can be released, which helps to appropriately use network resources.

[0047] With respect to the second aspect or any implementation thereof, in another possible implementation, a packet header of at least one of the second message, the third message, the fourth message, the fifth message, the sixth message, or the seventh message includes a protocol identification code, and the packet header is 1 byte in length.

[0048] With respect to the second aspect or any implementation thereof, in another possible implementation, the packet header of at least one of the second message, the third message, the fourth message, the fifth message, the sixth message, or the seventh message includes a protocol identification code and a security header type, and the sum of the length of the protocol identification code and the length of the security header type is 1 byte.

[0049] Regarding the second aspect or any implementation thereof, in another possible implementation, when the security header type indicates that security protection is implemented, the packet header further includes a message authentication code and a sequence number.

[0050] According to a third aspect, there is provided a tag state management method. The method may be performed by an access network device, or by a module or unit in the access network device. For ease of description, a module or unit in the access network device will hereinafter be collectively referred to as the access network device.

[0051] The method includes: an access network device receives a second request message used to request inventorying of inventoried tags; the access network device sends a first message to the inventoried tags based on the second request message, the first message being used to request inventorying of the inventoried tags; after a first tag among the inventoried tags accesses the access network device, the access network device receives a second message from the first tag, the second message being used to request registration with a core network device; and the access network device sends the second message to the core network device.

[0052] The method may alternatively be described as follows: The access network device receives a second request message used to request inventorying of tags to be inventoried, where the tags to be inventoried include a first tag; The access network device sends a first message to the first tag based on the second request message, where the first message is used to request inventorying of the first tag; After the first tag accesses the access network device, the access network device receives a second message from the first tag, where the second message is used to request registration with a core network device; The access network device sends the second message to the core network device.

[0053] Regarding the third aspect, in a possible implementation, the first message is further used to excite the inventoried tag.

[0054] Regarding the third aspect or any implementation thereof, in another possible implementation, the method further includes: the access network device assigning a second identifier to the first tag based on the second message, the access network device sending the correspondence between the second identifier and the first tag to the core network device, and / or the access network device receiving the correspondence between the first identifier and the first tag from the core network device.

[0055] Regarding the third aspect or any implementation thereof, in another possible implementation, the method further includes: the access network device starts a third timer; and when the third timer expires, the access network device releases the correspondence between the first identifier and the first tag and / or the correspondence between the second identifier and the first tag.

[0056] Regarding the third aspect or any implementation thereof, in another possible implementation, the method further includes: the access network device resets a third timer based on a message between the first tag and the core network device.

[0057] Regarding the third aspect or any implementation thereof, in another possible implementation, the method further includes: the access network device receives a ninth message from the core network device, the ninth message indicating that an inventory for the first tag has been completed; and the access network device releases the correspondence between the first identifier and the first tag and / or the correspondence between the second identifier and the first tag based on the ninth message.

[0058]

[0023] With respect to the third aspect or any implementation thereof, in another possible implementation, the method further includes: the access network device sends an eighth message to the first tag, where the eighth message indicates to inventory the next tag.

[0059] With respect to the third aspect or any implementation thereof, in another possible implementation, the packet header of the second message includes a protocol identification code and the length of the packet header is 1 byte.

[0060] With respect to the third aspect or any implementation thereof, in another possible implementation, the packet header of the second message includes a protocol identification code and a security header type, and the sum of the length of the protocol identification code and the length of the security header type is 1 byte.

[0061] With respect to the third aspect or any implementation thereof, in another possible implementation, when the security header type indicates that security protection is implemented, the packet header further includes a message authentication code and a sequence number.

[0062] According to a fourth aspect, a tag state management method is provided. The method may be implemented by an access network device and a core network device, or may be implemented by a module or unit in the access network device and the core network device. For ease of description, the modules or units in the access network device and the core network device are hereinafter collectively referred to as the access network device and the core network device. For technical effects of the method in the fourth aspect and their possible implementations, please refer to the second aspect and their possible implementations. Details will not be described again below.

[0063] The method includes: a core network device receives a first request message used to request inventorying of inventoried tags; the core network device sends a second request message used to request inventorying of the inventoried tags to an access network device; the access network device sends a first message to the inventoried tags based on the second request message, the first message used to request inventorying of the inventoried tags; after a first tag among the inventoried tags accesses the access network device, the access network device receives a second message from the first tag, the second message used to request registration with the core network device; the access network device sends the second message to the core network device; after receiving the second message, the core network device switches the state of the first tag stored in the core network device from an unregistered state to a registered state.

[0064] The method may alternatively be described as follows: A core network device receives a first request message used to request inventorying of tags to be inventoried, where the tags to be inventoried include a first tag. The core network device sends a second request message used to request inventorying of the tags to be inventoried to an access network device. The access network device sends a first message to the first tag based on the second request message, where the first message is used to request inventorying of the first tag. After the first tag accesses the access network device, the access network device receives a second message from the first tag, where the second message is used to request registration with the core network device. The access network device sends the second message to the core network device. After receiving the second message, the core network device switches the state of the first tag stored in the core network device from an unregistered state to a registered state.

[0065] Regarding the fourth aspect, in a possible implementation, the first message is further used to excite the inventoried tag.

[0066] Regarding the fourth aspect or any implementation thereof, in another possible implementation, after the second message is received, the method further includes: the core network device sending a third message to the first tag through the access network device, where the third message indicates that the first tag has been successfully registered with the core network device. Switching the state of the first tag stored in the core network device from a deregistered state to a registered state after the core network device receives the second message includes: the core network device switching the state of the first tag stored in the core network device from a deregistered state to a registered state after sending the third message.

[0067] Regarding the fourth aspect or any implementation thereof, in another possible implementation, after the second message is received, the method further includes: the core network device receiving a fourth message from the first tag, where the fourth message is used to request performing authentication on the first tag; the core network device sending a fifth message to the first tag, where the fifth message indicates that the authentication on the first tag has been successful; switching the state of the first tag stored in the core network device from a deregistered state to a registered state after the core network device receives the second message includes: the core network device switching the state of the first tag stored in the core network device from a deregistered state to a registered state after sending the fifth message.

[0068] Regarding the fourth aspect or any implementation thereof, in another possible implementation, after the second message is received, the method further includes: the core network device sending a sixth message to the first tag, where the sixth message is used to request performing authentication on an authentication server; the core network device receiving a seventh message from the first tag, where the seventh message indicates that the authentication on the authentication server has been successful; switching the state of the first tag stored in the core network device from a deregistered state to a registered state after the core network device receives the second message includes: the core network device switching the state of the first tag stored in the core network device from a deregistered state to a registered state after receiving the seventh message.

[0069] Regarding the fourth aspect or any implementation thereof, in another possible implementation, the method further includes: when the inventory for the first tag is completed, the core network device switches the state of the first tag stored in the core network device from a registered state to an unregistered state.

[0070] Regarding the fourth aspect or any implementation thereof, in another possible implementation, the method further includes: the core network device assigning a first identifier to the first tag after receiving the second message, and the core network device sending a correspondence between the first identifier and the first tag to the access network device.

[0071] Regarding the fourth aspect or any implementation thereof, in another possible implementation, the method further includes: the access network device assigns a second identifier to the first tag based on the second message, and the access network device sends a correspondence between the second identifier and the first tag to the core network device.

[0072] Regarding the fourth aspect or any implementation thereof, in another possible implementation, the method further includes: when the state of the first tag is switched from a registered state to a deregistered state, the core network device releases the correspondence between the first identifier and the first tag and / or the correspondence between the second identifier and the first tag.

[0073] Regarding the fourth aspect or any implementation thereof, in another possible implementation, the method further includes: the core network device sends a ninth message to the access network device, where the ninth message indicates that the inventory for the first tag has been completed, and the access network device releases the correspondence between the first identifier and the first tag and / or the correspondence between the second identifier and the first tag based on the ninth message.

[0074]

[0023] With respect to the fourth aspect or any implementation thereof, in another possible implementation, the method further includes: the access network device sends an eighth message to the first tag, where the eighth message indicates to inventory the next tag.

[0075] With respect to the fourth aspect or any implementation thereof, in another possible implementation, a packet header of at least one of the second message, the third message, the fourth message, the fifth message, the sixth message, or the seventh message includes a protocol identification code, and the packet header is 1 byte in length.

[0076] With respect to the fourth aspect or any implementation thereof, in another possible implementation, the packet header of at least one of the second message, the third message, the fourth message, the fifth message, the sixth message, or the seventh message includes a protocol identification code and a security header type, and the sum of the length of the protocol identification code and the length of the security header type is 1 byte.

[0077] With respect to the fourth aspect or any implementation thereof, in another possible implementation, when the security header type indicates that security protection is implemented, the packet header further includes a message authentication code and a sequence number.

[0078] For the technical effects of the methods in the second to fourth aspects and their possible implementations, please refer to the first aspect and their possible implementations, and the details will not be described again.

[0079] According to a fifth aspect, there is provided a tag inventory method. The method may be performed by a first tag or by a module or unit in the first tag. For ease of explanation, the module or unit in the first tag will hereinafter be collectively referred to as the first tag.

[0080] The method includes: a first tag receives a first message from an access network device, the first message being used to request inventorying of an inventory target tag, the first tag belonging to the inventory target tag; the first tag accesses the access network device; the first tag receives a quick inventory command from the access network device; and the first tag sends an identifier of the first tag to the access network device based on the quick inventory command.

[0081] There can be one or more inventoried tags.

[0082] The method may alternatively be described as follows: a first tag receives a first message from an access network device, the first message being used to request that the first tag be inventoried; the first tag accesses the access network device; the first tag receives a quick inventory command from the access network device; and the first tag sends an identifier of the first tag to the access network device based on the quick inventory command.

[0083] Optionally, the first message includes a selection command, which is used to select one or more inventoried tags, and the selection command may include conditions that must be met by the tags. After receiving the first message, the first tag determines whether the first tag meets the conditions in the selection command, and when the first tag meets the conditions in the selection command, the first tag knows that the first tag is inventoried.

[0084] According to the method, a quick inventory for a tag can be implemented. During the quick inventory for a tag, the access network device performs an inventory for the tag and feeds the tag back to the core network device in a unified manner. The first tag and the core network device may not need to switch the state of the first tag between a registered state and a deregistered state as described in the first to fourth aspects.

[0085] Regarding the fifth aspect, in a possible implementation, the first message is further used to excite the inventoried tag.

[0086] For example, when the inventoried tag is a passive tag or a semi-passive tag, the first message may also be used to excite the inventoried tag.

[0087] According to a sixth aspect, there is provided a tag inventory method. The method may be performed by a core network device, or may be performed by a module or unit in the core network device. For ease of description, the modules or units in the core network device will hereinafter be collectively referred to as the core network device.

[0088] The method includes: a core network device receives a third request message used to request performing a quick inventory on inventoried tags, where the inventoried tags include a first tag; the core network device sends a fourth request message used to request performing a quick inventory on the inventoried tags to an access network device; the core network device receives an identifier of the first tag from the access network device; and the core network device sends the identifier of the first tag to an application function network element.

[0089] According to a seventh aspect, there is provided a tag inventory method. The method may be performed by an access network device, or may be performed by a module or unit in the access network device. For ease of description, a module or unit in the access network device will hereinafter be collectively referred to as the access network device.

[0090] The method includes: the access network device receives a fourth request message used to request performing a quick inventory on the inventoried tags; the access network device sends a first message to the inventoried tags based on the fourth request message, the first message used to request inventorying the inventoried tags; after a first tag among the inventoried tags accesses the access network device, the access network device sends a quick inventory command to the first tag; the access network device receives an identifier of the first tag from the first tag; and the access network device sends the identifier of the first tag to the core network device.

[0091] The method may alternatively be described as follows: The access network device receives a fourth request message used to request performing a quick inventory on inventoried tags, where the inventoried tags include a first tag; The access network device sends a first message to the first tag based on the fourth request message, where the first message is used to request inventorying the first tag; After the first tag accesses the access network device, the access network device sends a quick inventory command to the first tag; The access network device receives an identifier of the first tag from the first tag; The access network device sends the identifier of the first tag to the core network device.

[0092] Regarding the seventh aspect, in a possible implementation, the first message is further used to excite the inventoried tag.

[0093] According to an eighth aspect, there is provided a tag inventory method. The method may be performed by an access network device and a core network device, or may be performed by modules or units in the access network device and the core network device. For ease of description, the modules or units in the access network device and the core network device are hereinafter collectively referred to as the access network device and the core network device.

[0094] The method includes: a core network device receives a third request message used to request performing a quick inventory on the inventoried tags; the core network device sends a fourth request message used to request performing a quick inventory on the inventoried tags to an access network device; the access network device sends a first message to the inventoried tags based on the fourth request message, the first message used to request inventorying the inventoried tags; after a first tag among the inventoried tags accesses the access network device, the access network device sends a quick inventory command to the first tag; the access network device receives an identifier of the first tag from the first tag; the access network device sends the identifier of the first tag to the core network device; and the core network device sends the identifier of the first tag to an application function network element.

[0095] The method may alternatively be described as follows: The core network device receives a third request message used to request performing a quick inventory on tags to be inventoried, where the tags to be inventoried include a first tag. The core network device sends a fourth request message used to request performing a quick inventory on the tags to be inventoried, to the access network device. The access network device sends a first message to the first tag based on the fourth request message, where the first message is used to request inventorying the first tag. After the first tag accesses the access network device, the access network device sends a quick inventory command to the first tag. The access network device receives an identifier of the first tag from the first tag. The access network device sends the identifier of the first tag to the core network device. The core network device sends the identifier of the first tag to an application function network element.

[0096] Regarding the eighth aspect, in a possible implementation, the first message is further used to excite the inventoried tag.

[0097] For the technical effects of the methods in the sixth to eighth aspects and their possible implementations, please refer to the fifth aspect and their possible implementations, and the details will not be described again.

[0098] According to a ninth aspect, there is provided a communication device configured to perform the method provided in any one of the above aspects or implementations of the above aspects. In particular, the device may include units and / or modules, such as a processing unit and / or a communication unit, configured to perform the method provided in any one of the above aspects or implementations of the above aspects.

[0099] In one implementation, the apparatus is a first tag, a core network device, or an access network device. When the apparatus is a first tag, a core network device, or an access network device, the communication unit may be a transceiver, an input / output interface, or a communication interface, and the processing unit may be at least one processor. Optionally, the transceiver is a transceiver circuit. Optionally, the input / output interface is an input / output circuit.

[0100] In another implementation, the apparatus is a chip, chip system, or circuit used in the first tag, core network device, or access network device. When the apparatus is a chip, chip system, or circuit used in the first tag, core network device, or access network device, the communication unit may be an input / output interface, interface circuit, output circuit, input circuit, pin, associated circuit, etc. on the chip, chip system, or circuit, and the processing unit may be at least one processor, processing circuit, logic circuit, etc.

[0101] According to a tenth aspect, there is provided a communications device, the device including: a memory configured to store a program; and at least one processor configured to execute a computer program or instructions stored in the memory to perform a method provided in any one of the above aspects or implementations of the above aspects. In one implementation, the device is a first tag, a core network device, or an access network device.

[0102] In another implementation, the apparatus is a chip, chip system, or circuit used in a first tag, a core network device, or an access network device.

[0103] According to an eleventh aspect, there is provided a communication device. The device includes at least one processor and a communication interface. The at least one processor is configured to retrieve, via the communication interface, a computer program or instructions stored in a memory to perform the method provided in any one of the above aspects or implementations of the above aspects. The communication interface may be implemented by hardware or software. In one implementation, the apparatus further includes a memory.

[0104] According to a twelfth aspect, there is provided a processor configured to perform the method provided in the above aspect.

[0105] Unless otherwise specified, or when operations such as transmitting and acquiring / receiving related to a processor do not conflict with actual functions or internal logic in the relevant description, operations may be understood as operations such as output, reception, and input of a processor, or as operations such as transmitting and receiving performed by a radio frequency circuit and an antenna, which is not limited in this application.

[0106] According to a thirteenth aspect, there is provided a computer-readable storage medium, the computer-readable storage medium storing program code to be executed by a device, the program code being used to implement the method provided in any one of the above aspects or implementations of the above aspects.

[0107] According to a fourteenth aspect, there is provided a computer program product comprising instructions, which, when executed on a computer, enable the computer to perform the method provided in any one of the above aspects or implementations of the above aspects.

[0108] According to a fifteenth aspect, a chip is provided. The chip includes a processor and a communication interface. The processor reads instructions stored in a memory through the communication interface to perform the method provided in any one of the above aspects or implementations of the above aspects. The communication interface may be implemented by hardware or software.

[0109] Optionally, in one implementation, the chip further includes a memory. The memory stores a computer program or instruction. The processor is configured to execute the computer program or instruction stored in the memory. When the computer program or instruction is executed, the processor is configured to perform the method provided in any one of the above aspects or implementations of the above aspects.

[0110] According to a sixteenth aspect, there is provided a communication system including at least one of a first tag, a core network device, or an access network device. [Brief explanation of the drawings]

[0111] [Figure 1] FIG. 10 is a diagram showing the types of reader / writer commands and the state of the tag. [Figure 2] FIG. 1 is a diagram of a terminal state machine. [Figure 3] FIG. 1 is a diagram of a network architecture to which an embodiment of the present application is applicable. [Figure 4] 4 is a schematic flow chart of a tag state management method 400 according to the present application. [Figure 5] 1 is an example of a lightweight common NAS message according to the present application. [Figure 6] 1 is an example of a lightweight secure NAS message according to the present application. [Figure 7] 7 is a schematic flow chart of a tag inventory method 700 according to the present application. [Figure 8] FIG. 2 is a diagram of a tag state machine according to one embodiment of the present application. [Figure 9] 1 is an example of a tag state change procedure according to an embodiment of the present application. [Figure 10A] 10 is another example of a tag state change procedure according to an embodiment of the present application. [Figure 10B] 10 is another example of a tag state change procedure according to an embodiment of the present application. [Figure 11] 1 is a diagram of the structure of an apparatus according to an embodiment of the present application; [Figure 12] FIG. 2 is another diagram of the structure of the device according to an embodiment of the present application. DETAILED DESCRIPTION OF THE INVENTION

[0112] Below, the technical solutions in the embodiments of the present application are described with reference to the accompanying drawings.

[0113] To facilitate understanding of the embodiments of the present application, the following explanation is first provided before the embodiments of the present application are described.

[0114] In this application, "indicating" or "indicating" may include direct and indirect indication, or "indicating" or "indicating" may be explicit and / or implicit indication. For example, when a piece of indication information is described as indicating information I, the information may directly indicate I or indirectly indicate I, but does not necessarily indicate that the information carries I. In another example, an implicit indication may be based on location and / or resources used for transmission, and an explicit indication may be based on one or more parameters, one or more indexes, and / or one or more bit patterns represented by the explicit indication.

[0115] The definitions listed for many features in this application are only used to explain the function of the features by using examples, and for detailed content of the definitions, please refer to the prior art.

[0116] In the following embodiments, the first, second, third, fourth, and various numbers are used for distinction only to facilitate description and are not used to limit the scope of the embodiments of the present application, for example, numbers are used to distinguish between different fields and different information.

[0117] "Predefined" may be implemented by prestoring a corresponding code or table in the device, or in another manner that can be used to indicate related information. The specific implementation of "predefined" is not limited in this application. "Storage" may be storage in one or more memories. The type of memory may be any form of storage medium. This is not limited in this application.

[0118] The "protocol" in the embodiments of the present application may be a standard protocol in the communication field, and may include, for example, a long term evolution (LTE) protocol, a new radio (NR) protocol, and related protocols applied to future communication systems, which are not limited in the present application.

[0119] Each aspect, embodiment, or feature is presented herein in the context of a system that includes multiple devices, components, modules, etc. It is appreciated and understood that each system may include other devices, components, modules, etc. and / or may not include all of the devices, components, modules, etc. described with reference to the accompanying drawings. Furthermore, combinations of these solutions may be used.

[0120] In the embodiments of this application, terms such as "example," "for example," and "in another example" are used to denote serving as an example, illustration, or explanation. Any embodiment or design manner described in this application as an "example" should not be described as preferred or having more advantages over another embodiment or design manner. Rather, the term "example" is used to present a concept in a particular way. The terms "including," "having," and variations thereof all mean "including but not limited to," unless specifically stated otherwise.

[0121] "At least one" means one or more, and "multiple" means two or more. The term "and / or" refers to an association relationship between related objects and indicates that three relationships may exist. For example, A and / or B may refer to the following cases: when only A is present, when both A and B are present, and when only B is present, where A and B may be singular or plural. The character " / " generally indicates an "or" relationship between related objects. "At least one of the following items (moieties)" or similar expressions refers to any combination of these items, including a single item (moiety) or any combination of multiple items (moieties). For example, at least one item (moiety) of a, b, and c may refer to a, b, c, a and b, a and c, b and c, or a, b, and c. Each of a, b, and c may be singular or plural.

[0122] In the embodiments of the present application, the related descriptions of sending a message, information, or data by network element A to network element B and receiving a message, information, or data by network element B from network element A are intended to describe the network element to which the message, information, or data is to be sent. Whether the message, information, or data is sent directly or indirectly through another network element is not limited.

[0123] In the embodiments of the present application, the descriptions such as "when", "in the case of", "if" and the like all mean that the device performs the corresponding processing in the objective case, and are not limited in time, and the device is not required to perform a decision-making act during implementation, which does not imply any other limitation.

[0124] To facilitate understanding of the embodiments of the present application, terms used in the present application will first be briefly explained.

[0125] 1. Reader / writer and tag Wireless radio frequency identification (RFID) technology is one of the automatic identification technologies, and is used for contactless two-way data communication through wireless radio frequency. Wireless radio frequency identification technology can be used to implement reading / writing by a reader / writer to a tag through wireless radio frequency to identify the target and exchange data.

[0126] A wireless radio frequency identification system may include a reader / writer and a tag.

[0127] (1) Reader / Writer

[0128] A reader / writer is also called a read / write device, reader, scanner, read head, communicator, reader, interpreter, device having reading and / or writing capabilities, etc. For ease of explanation, these devices are collectively referred to as reader / writers in this application. A reader / writer is a device that reads information from a tag and / or writes information to a tag.

[0129] (2) Tags

[0130] Tags are also referred to as answerback devices, electronic tags, RFID tags, radio frequency tags, transponders, data carriers, recording media, radio frequency cards, Internet of Things devices, Internet of Things device terminals, etc. For ease of explanation, these devices are collectively referred to as tags in this application. Each tag has a unique electronic code, for example, a tag identifier (TID). Each tag also has an electronic product code (EPC). Tags can be attached to objects or devices to identify the target object.

[0131] The tag's storage areas can be classified into a reserved storage area, an EPC storage area, a TID storage area, and a user storage area. The reserved storage area is mainly used to store a kill password, an access password, etc. The EPC storage area is mainly used to store the tag's EPC, etc. The TID storage area is mainly used to store the tag's TID. The user storage area is mainly used to store user-defined data.

[0132] Tags can include active tags, semi-passive tags, and passive tags.

[0133] Active tags are also called active tags. The tag's operating power is provided by a battery within the tag, and the battery energy can be converted into radio frequency energy required for communication between the tag and a reader / writer.

[0134] A semi-passive tag is a tag that has a battery but does not actively transmit radio frequency signals, but receives and responds to radio frequency signals from a reader / writer.

[0135] Passive tags are also called passive tags. They do not have a battery inside them. When the tag is out of the reading range of a reader / writer, it is in a passive state. When the tag is within the reading range of a reader / writer, it extracts the energy it needs to operate from the radio frequency energy emitted by the reader / writer.

[0136] 2. Reader / writer commands and tag status

[0137] FIG. 1 is a diagram of reader / writer command types and tag states.

[0138] As shown in Figure 1, from a functional point of view, reader / writer commands can be of three types: select, inventory, and access. The select-type commands include the select command. The inventory-type commands include the query command, query adjust command, query repeat command, acknowledgment (ACK) command, negative acknowledgment (NAK) command, etc. The access-type commands include the request random number (Req_RN) command, read command, write command, kill command, lock command, access command, block write command, block erase command, etc. The access command, block write command, and block erase command are optional. Furthermore, codes of different lengths are reserved for future command extensions.

[0139] For commands from a reader / writer, the tag states may be shown in Figure 1. In particular, the tag states include ready, arbitrated, replied, acknowledged, open, secured, and killed.

[0140] In particular, the Ready state is the initial state of a non-killed, powered-on tag. In this state, the tag is ready to respond to commands. In the Arbitrated state, the tag mainly waits to respond to a query command, etc. After responding to a query command, the tag enters the Reply state. In this state, the tag may further return its EPC to the reader / writer in response to an Acknowledge command. After returning the EPC to the reader / writer, the tag enters the Acknowledged state. In this state, the tag may further respond to a Random Number Request command. When the access password is not 0, the tag may enter the Open state. In this state, operations such as read and write may be performed on the tag. When the access password is known, the tag may enter the Secured state. In this state, operations such as read, write, and locking may be performed on the tag. When the tag enters the Killed state, it remains in the Killed state and no longer generates a modulated signal to activate a radio frequency field; therefore, the tag is permanently disabled. To cause the tag to enter a state, a set of valid commands in the proper order are required, with each command only valid when the tag is in the appropriate state.

[0141] 3. Terminal State Machine and Core Network Device State Machine

[0142] FIG. 2 is a diagram of a terminal state machine.

[0143] In a wireless communication system, a terminal state change on the terminal side and a state change on the core network device (e.g., AMF) side are implemented based on NAS messages.

[0144] On the terminal side, for example, as shown in Figure 2, when the terminal receives a registration accept message, the terminal changes from a deregistered state to a registered state. When the terminal receives a registration update accept message, the terminal remains in a registered state. When the terminal receives a deregistration registration reject message, the terminal changes from a registered state to a deregistered state. When the terminal receives a registration reject message, the terminal remains in a deregistered state.

[0145] On the core network device (e.g., AMF) side, for example, as shown in Figure 2, when the core network device sends a registration accept message to the terminal, the core network device switches the state of the terminal stored in the core network device from a deregistered state to a registered state. When the core network device sends a registration update accept message to the terminal, the core network device keeps the state of the terminal stored in the core network device as a registered state. When the core network device sends a deregistration registration reject message to the terminal, the core network device changes the state of the terminal stored in the core network device from a registered state to a deregistered state. When the core network device sends a registration reject message to the terminal, the core network device keeps the state of the terminal stored in the core network device as a deregistered state. The unregistered state is sometimes referred to as the unregistered state.

[0146] Currently, terminals (e.g., passive tags or semi-passive tags) in the passive internet of things (PIoT) have the following mainstream application scenarios:

[0147] (1) Logistics and warehousing: Includes inventory and tracking of goods, as well as monitoring of the transport handling environment and goods conditions for high-value goods (such as vaccines).

[0148] (2) Industrial manufacturing: including environmental and device condition monitoring.

[0149] With the development of technology and environmental protection requirements, the passive Internet of Things is expected to have larger application and deployment, and it is predicted that hundreds of billions of devices will be covered in the future. However, tags in the passive Internet of Things (passive tags or semi-passive tags) have simple functions and usually need to rely on external excitation to transmit information to the outside. The external excitation usually comes from a reader / writer. At present, the deployment of the passive Internet of Things has characteristics such as a short communication distance between the card reader and the tag and complex implementation of the tag's state.

[0150] In terms of features, in the solution, the inventory capabilities of the reader / writer (including operations such as reading, writing, killing, and locking tags) are integrated into the access network device, so that tags in the passive Internet of Things are excited and inventoried by using air interface wireless technology, increasing the communication distance between tags in the passive Internet of Things and card readers, and implementing unified management for tags in the passive Internet of Things through the access network device.

[0151] However, it does not specify how to manage the state of a tag in a scenario where tags in a passive Internet of Things are inventoried by using air interface wireless technology. In view of the above problems, the present application provides a tag state management method to manage the state of a tag in this scenario. For ease of understanding, a communication system to which an embodiment of the present application may be applied is first described.

[0152] Embodiments of the present application may be applied to various communication systems, such as a long term evolution (LTE) system, an LTE frequency division duplex (FDD) system, an LTE time division duplex (TDD) system, a public land mobile network (PLMN) system, a fifth generation (5G) system, a sixth generation (6G) system, or a future communication system. A 5G system in this application includes a non-standalone (NSA) 5G mobile communication system or a standalone (SA) 5G mobile communication system. Embodiments of the present application may also be applied to a non-terrestrial network (NTN) communication system, such as a satellite communication system. Embodiments of the present application may further be applied to a device to device (D2D) communication system, a sidelink (SL) communication system, a machine to machine (M2M) communication system, a machine type communication (MTC) system, an Internet of things (IoT) communication system, a vehicle to everything (V2X) communication system, an unmanned aerial vehicle (UAV) communication system, or another communication system.

[0153] For example, FIG. 3 is a diagram of a network architecture.

[0154] As shown in Figure 3, the network architecture may include a tag, an access network device, a tag management function (TMF), and an application function (AF). The tag may interact with the TMF through the access network device. The access network device may communicate with the TMF through an interface (e.g., an N2 interface). Optionally, the network architecture may further include a session management function (SMF), a charging function (CHF), a network exposure function (NEF), etc. In Figure 3, dashed lines and dashed boxes represent optional connections and optional network elements.

[0155] The following is a brief description of the network elements in Figure 3.

[0156] 1. For tag descriptions, please refer to the above description, and the details will not be repeated here.

[0157] 2. The access network device has an inventory capability to inventory tags and may excite and inventory tags in a passive Internet of Things by using air interface wireless technology. The access network device may be a device configured to communicate with a terminal (the tag shown in FIG. 3) or a device that connects a terminal to a wireless network. The access network device may be a node in a wireless access network. The access network device may be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a home base station (e.g., a home evolved NodeB or Home NodeB, HNB), a Wi-Fi access point (AP), a mobile switching center, a next generation NodeB (gNB) in a 5G mobile communication system, an access network device in an open radio access network (O-RAN or open RAN), a next generation base station in a 6th generation (6G) mobile communication system, a base station in a future mobile communication system, etc. Alternatively, the access network device may be a module or unit that implements some functions of a base station, such as a central unit (CU), a distributed unit (DU), a remote radio unit (RRU), or a baseband unit (BBU). Alternatively, the access network device may be a device that functions as a base station in a D2D communication system, a V2X communication system, an M2M communication system, an IoT communication system, etc. Alternatively, the access network device may be a network device in an NTN. In other words, the access network device may be deployed on a stratospheric platform or a satellite.The access network device may be a macro base station, a micro base station or an indoor base station, or may be a relay node, a donor node, etc.

[0158] The specific technology, device form, and name used by the access network device are not limited to the embodiments of the present application.

[0159] 3. The TMF is responsible for managing tags. The TMF may be an independent network element. Alternatively, the TMF may be integrated with another network element, for example, as shown in FIG. 3, the TMF is integrated with the access and mobility management function (AMF). Alternatively, the TMF may be a function of another network element, or may be understood as an enhancement of another network element, such that the network element has the functionality provided by the TMF. For example, the AMF is enhanced, such that the AMF has the functionality of the TMF. In other words, the AMF may have the functionality of the TMF in addition to functions such as user registration management, reachability detection, SMF node selection, and mobility state switching management.

[0160] 4. The AF primarily supports interaction with the 3rd generation partnership project (3GPP) core network, for example, to influence data routing decisions and policy control functions, or to provide third-party services to the network. The AF may be an AF deployed on the operator network, or may be a third-party AF.

[0161] 5. The SMF is mainly responsible for controlling session establishment, modification, and deletion, user plane node selection, etc.

[0162] 6. CHF is primarily responsible for billing data record generation and service allocation management.

[0163] 7. The NEF is primarily configured to securely expose services and capabilities provided by 3GPP network functions and to support secure interactions between 3GPP networks and third-party applications.

[0164] In the network architecture shown in Figure 3, network elements may communicate with each other through interfaces. The interfaces between network elements may be point-to-point interfaces or service-based interfaces, which is not a limitation of this application.

[0165] It should be understood that the above network architecture is merely an example for the purpose of explanation, and that the network architecture applicable to the embodiments of the present application is not limited thereto. Any network architecture capable of implementing the functions of the network elements is applicable to the embodiments of the present application.

[0166] Furthermore, it should be understood that the functions or network elements such as the AMF, SMF, TMF, NEF, and AF shown in Figure 3 may be understood as network elements configured to implement different functions and may be combined into a network slice based on requirements, for example. These network elements may be independent devices, may be integrated into the same device and implement different functions, may be network elements in a hardware device, may be software functions running on dedicated hardware, or may be virtualized functions instantiated on a platform (e.g., a cloud platform). The specific form of the network elements is not limited in this application.

[0167] Furthermore, it should be understood that the above names are defined merely to distinguish between different functions and should not constitute any limitation to the present application. The present application does not exclude the possibility of using other names in 6G networks and other future networks. For example, in a 6G network, some or all of the network elements may still use the terminology in 5G, or may use other names.

[0168] The following describes the tag state management method provided in this application.

[0169] FIG. 4 is a schematic flow chart of a tag state management method 400 according to the present application.

[0170] The method 400 may include at least some of the following:

[0171] Note that the initial state of an inventoried tag may be in an unregistered state.

[0172] Step 401: A core network device receives a first request message used to request to inventory an inventory target tag.

[0173] For example, as shown in FIG. 4, the core network device receives a first request message from the AF; in other words, the AF sends a first request message to the core network device.

[0174] The core network device may be a TMF or may be another network element having the functionality of a TMF, for example, an AMF.

[0175] The first request message may carry information about the inventoried tag.

[0176] The information about the inventoried tags may include at least one of the following information: an identifier of each tag among the inventoried tags, a value interval to which the identifier of the inventoried tag belongs, a group identifier of the inventoried tag, an identifier of a user to which the inventoried tag belongs, a type of the inventoried tag, an identifier of an application to which the inventoried tag belongs, etc. The identifier of a tag may be the TID or EPC of the tag.

[0177] For example, the inventoried tags include three tags, and the identifiers of the three tags are TID#1, TID#2, and TID#3, respectively. The first request message may carry the identifiers of the tags in the inventoried tags, i.e., TID#1, TID#2, and TID#3.

[0178] In another example, the inventoried tags include three tags, and the TID values ​​of the three tags are 101, 101, and 102. The first request message may carry the value interval to which the TIDs of the inventoried tags belong, i.e., 100 to 102.

[0179] In another example, the inventoried tags include three tags, and the three tags belong to one tag group, and the group identifier of the tag group is Group #1. The first request message may carry the group identifier of the inventoried tags, i.e., Group #1.

[0180] In another example, the inventoried tags include three tags, the three tags belong to one user, and the identifier of the user is User #1. The first request message may carry the identifier of the user to which the inventoried tags belong, i.e., User #1.

[0181] In another example, the terminals to be inventoried include three terminals, and the three terminals are all passive terminals or all semi-passive terminals. The first request message may carry the type of the tag to be inventoried, i.e., passive tag or semi-passive tag.

[0182] In another example, the inventoried tags include three tags, and the three tags belong to one application, and the identifier of the application is Application #1. The first request message may carry the identifier of the application to which the inventoried tags belong, i.e., Application #1.

[0183] Please note that the group identifier, user identifier, tag type, application identifier, etc. are written to the tag's memory area (e.g., TID memory area, EPC memory area, or another memory area), in other words, the tag's memory area stores the above information.

[0184] Optionally, the first request message may further carry an inventory command and / or information about the geographic area in which the inventoried tag is located. The inventory command may be an operation request on the tag, such as inventory, read, or write. The information about the geographic area in which the inventoried tag is located is used to determine the access network device to which the inventoried tag belongs.

[0185] Step 402: The access network device receives a second request message used to request to inventory the inventoried tag.

[0186] For example, as shown in FIG. 4, the access network device receives a second request message from the core network device, in other words, the core network device sends a second request message to the core network device.

[0187] In particular, after receiving the first request message, the core network device sends a second request message to the access network device based on the first request message. For example, when the first request message includes information about the geographical area where the inventory target tag is located, the core network device determines the access network device to which the inventory target tag belongs based on the information about the geographical area where the inventory target tag is located, and sends a second request message to the access network device.

[0188] The second request message may carry information about the inventoried tag. For a description of the information about the inventoried tag, please refer to the above description. The details will not be described again.

[0189] Optionally, the second request message may further carry an inventory command, which may be an operation request to the tag, such as inventory, read, or write.

[0190] Step 403: The access network device sends a first message to the inventoried tag based on the second request message.

[0191] In response, the inventoried tag receives a first message from the access network device.

[0192] The first message is used to request that the inventoried tag be inventoried.

[0193] For example, the access network device may learn about the tags to be inventoried based on the second request message and send a first message, where the first message includes a selection command, where the selection command is used to select the tags to be inventoried, where the selection command may include conditions that need to be satisfied by the tags, and where the tags to be inventoried may satisfy the conditions in the selection command. In this way, after receiving the first message, the tags to be inventoried may determine whether they satisfy the conditions in the selection command.

[0194] In this scheme, tags may be selected by matching the tag's storage area flags. In this case, the selection command may include a condition that must be met by the value of the tag's corresponding storage area. The TID storage area is used as an example. The selection command may include a value or a range of values ​​for the TID storage area. In this case, tags whose TID value is the value in the selection command or whose TID value is within the range of values ​​in the selection command are inventoried tags.

[0195] It should be noted that step 402 and step 403 can alternatively be described together as follows: The core network device sends a first message to the inventoried tag through the access network device.

[0196] Optionally, when the inventoried tag is a passive tag or a semi-passive tag, the first message is further used to power up the inventoried tag, in other words, the first message is further used to excite the inventoried tag. The following describes the method 400 by using the first tag in the inventoried tags as an example.

[0197] Step 404: After receiving the first message, the first tag accesses the access network device.

[0198] "The first tag accesses the access network device" may alternatively be described as the first tag successfully performing random access.

[0199] In particular, after receiving the first message, the first tag may determine whether the first tag satisfies the conditions in the selection command, and when the first tag satisfies the conditions in the selection command (i.e., the first tag belongs to the inventoried tags), the first tag may initiate a procedure to access the access network device to access the access network device.

[0200] The specific implementation of the tag accessing the access network device is not limited in this application. In a possible implementation, after sending the first message, the access network device sends a query message to the tag, and after receiving the query message, the tag that meets the conditions in the selection command returns a random number to the access network device. For example, the first tag sends a random number to the access network device. After receiving the random number from the first tag, the access network device returns an ACK message to the first tag, and the ACK message may carry the random number sent by the first tag. The first tag compares the received random number with the sent random number, and if the two random numbers are consistent, the random access by the first tag is successful.

[0201] Step 405: After accessing the access network device, the first tag sends a second message to the core network device.

[0202] The second message is used to request registration with the core network device. For example, the second message may be a registration request message. The second message may carry an identifier of the first tag. The identifier of the first tag may be the TID or EPC of the first tag.

[0203] For example, as shown in FIG. 4, the first tag may send the second message through the access network device to the core network device.

[0204] Step 406: The first tag switches from an unregistered state to a registered state after sending the second message.

[0205] Scheme A: After sending the second message, the first tag may switch from an unregistered state to a registered state. In other words, the second message triggers the first tag to switch from an unregistered state to a registered state.

[0206] Scheme B: Another message after the second message triggers the first tag, so that the first tag can switch from an unregistered state to a registered state. Scheme B can be implemented in multiple different ways. For example, implementations can be shown in Scheme 1 to Scheme 3 below.

[0207] Scheme 1: After the first tag sends the second message, method 400 further includes: after receiving the second message, the core network device sends a third message to the first tag, in other words, the first tag receives a third message from the core network device, where the third message indicates that the first tag has successfully registered with the core network device. Step 406 includes: after receiving the third message, the first tag switches from an unregistered state to a registered state, in other words, the third message after the second message triggers the first tag to switch from an unregistered state to a registered state.

[0208] For example, the third message may be a registration acceptance message.

[0209] That is, when the first tag is successfully registered, the first tag switches from an unregistered state to a registered state.

[0210] Scheme 2: After the first tag sends the second message, method 400 further includes: the first tag sends a fourth message to the core network device, in other words, the core network device receives a fourth message from the first tag, where the fourth message is used to request authentication for the first tag. When the authentication for the first tag is successful, the core network device sends a fifth message to the first tag, in other words, the first tag receives a fifth message from the core network device, where the fifth message indicates that authentication for the first tag is successful. Step 406 includes: after receiving the fifth message, the first tag switches from an unregistered state to a registered state, in other words, the fifth message after the second message triggers the first tag to switch from an unregistered state to a registered state.

[0211] For example, the fourth message may be an authentication request message and the fifth message may be an authentication success message.

[0212] That is, when the first tag is successfully authenticated, the first tag switches from an unregistered state to a registered state.

[0213] Scheme 3: After the first tag sends the second message, method 400 further includes: the first tag receives a sixth message from the core network device; in other words, the core network device sends the sixth message to the first tag, where the sixth message is used to request the first tag to perform authentication on an authentication server. When the authentication on the authentication server is successful, the first tag sends a seventh message to the core network device; in other words, the core network device receives a seventh message from the first tag, where the seventh message indicates that the authentication on the authentication server is successful. Step 406 includes: after sending the seventh message, the first tag switches from an unregistered state to a registered state; in other words, the seventh message after the second message triggers the first tag to switch from an unregistered state to a registered state.

[0214] For example, the sixth message may be an authentication request message and the seventh message may be an authentication success message.

[0215] That is, when authentication on the authentication server corresponding to the first tag is successful, the first tag switches from an unregistered state to a registered state.

[0216] Step 407: After receiving the second message, the core network device switches the state of the first tag stored in the core network device from an unregistered state to a registered state.

[0217] Scheme C: After receiving the second message, the core network device may switch the state of the first tag stored in the core network device from an unregistered state to a registered state. In other words, the second message triggers the core network device to switch the state of the first tag stored in the core network device from an unregistered state to a registered state.

[0218] Scheme D: Another message after the second message triggers the core network device to switch the state of the first tag stored in the core network device from an unregistered state to a registered state. Scheme D can be implemented in several different ways. For example, implementations can be shown in Schemes 1 to 3 below.

[0219] Scheme 1: For message exchange, please refer to Scheme 1 of Scheme B. Step 407 includes: After sending the third message, the core network device switches the state of the first tag stored in the core network device from an unregistered state to a registered state. In other words, the third message after the second message triggers the core network device to switch the state of the first tag stored in the core network device from an unregistered state to a registered state.

[0220] That is, when the first tag is successfully registered, the core network device switches the state of the first tag stored in the core network device from an unregistered state to a registered state.

[0221] Scheme 2: For message exchange, please refer to Scheme 2 of Scheme B. Step 407 includes: After sending the fifth message, the core network device switches the state of the first tag stored in the core network device from an unregistered state to a registered state. In other words, the fifth message after the second message triggers the core network device to switch the state of the first tag stored in the core network device from an unregistered state to a registered state.

[0222] That is, when authentication for the first tag is successful, the core network device switches the state of the first tag stored in the core network device from an unregistered state to a registered state.

[0223] Scheme 3: For message exchange, refer to Scheme 3 of Scheme B. Step 407 includes: After receiving the seventh message, the core network device switches the state of the first tag stored in the core network device from an unregistered state to a registered state. In other words, the seventh message after the second message triggers the core network device to switch the state of the first tag stored in the core network device from an unregistered state to a registered state.

[0224] That is, when authentication on the authentication server corresponding to the first tag is successful, the core network device switches the state of the first tag stored in the core network device from an unregistered state to a registered state.

[0225] Optionally, in another scenario of the above embodiment, method 400 further includes: the first tag starts a first timer when a state of the first tag is switched from a deregistered state to a registered state, the first timer being configured to maintain the registered state of the first tag, and the first tag switches from the registered state to the deregistered state when the first timer expires; and / or method 400 further includes: the core network device starts a second timer when a state of the first tag is switched from a deregistered state to a registered state, the second timer being configured to maintain the registered state of the first tag, and when the second timer expires, the core network device switches the state of the first tag stored in the core network device from the registered state to the deregistered state.

[0226] In this scenario, the registered state of the first tag is maintained through a timer.

[0227] Optionally, when the registered state of the first tag is maintained through a timer, the method 400 may further include: the first tag resetting or refreshing the first timer based on a message between the first tag and the core network device, and / or the core network device resetting or refreshing the second timer based on a message between the first tag and the core network device. That is, when no message exchange is performed between the first tag and the core network device, the state of the first tag is switched from the unregistered state to the registered state.

[0228] Optionally, the timing period of the first timer and / or the timing period of the second timer may be set based on a capability of the first tag, in which case the first tag may not reset or refresh the first timer based on a message between the first tag and the core network device, and / or the core network device may not reset or refresh the second timer based on a message between the first tag and the core network device.

[0229] The message between the first tag and the core network device may be any non-kill message, and a non-kill message in this specification may be understood as a message that is not used to kill the first tag. For example, the message may include an authentication-related message (e.g., when the above-described methods A and C are used) and / or a message in a (User Configuration Update, UCU) process (e.g., when any one of the above-described methods A to D is used).

[0230] Optionally, in another scenario of the above embodiment, method 400 further includes: when the inventory for the first tag is completed, the core network device switches the state of the first tag stored in the core network device from a registered state to a deregistered state; the core network device sends a ninth message to the access network device, in other words, the access network device receives a ninth message from the core network device, where the ninth message indicates that the inventory for the first tag is completed; the access network device sends an eighth message to the first tag, in other words, the first tag in the registered state receives an eighth message from the access network device, where the eighth message indicates to inventory the next tag; the first tag switches from the registered state to the deregistered state based on the eighth message.

[0231] The eighth message may be a query message used to access the access network device. A tag that is not inventoried and is in the inventoried tags is in a deregistered state. Upon receiving the query message, the uninventoried tag may respond to the query message from the access network device. The first tag is in a registered state. Upon receiving the query message, the first tag knows that the inventory for the first tag has finished, and the first tag switches from a registered state to a deregistered state.

[0232] In this scenario, when the inventory for the first tag is completed, the state of the first tag is switched from unregistered to registered.

[0233] Optionally, in another scenario of the above embodiment, the method 400 further includes: the core network device sends a message including a kill command to the first tag; after sending the message, the core network device switches the state of the first tag stored in the core network device from a registered state to a deregistered state; after receiving the message including the kill command, the first tag switches from a registered state to a deregistered state.

[0234] In this scenario, when killing is performed on the first tag, the state of the first tag is switched from an unregistered state to a registered state.

[0235] It should be noted that the first tag and the core network device may manage the state of the first tag in the same manner or in different manners, and may manage the state based on any combination of the above embodiments, without being limited thereto.

[0236] Optionally, in another scenario of the above embodiment, the method 400 further includes: after receiving the second message from the first tag, the core network device assigns a first identifier to the first tag based on the second message; the core network device sends the correspondence between the first identifier and the first tag to the access network device; in other words, the access network device receives the correspondence between the first identifier and the first tag from the core network device and stores the correspondence; in this way, both the access network device and the core network device store the correspondence between the first identifier and the first tag.

[0237] The first identifier is used for transmitting a message of the first tag between the access network device and the core network device; in other words, the first identifier is used to identify a transmission channel or resource used for transmitting a message of the first tag between the access network device and the core network device; in other words, the first identifier is used to identify that a message communicated between the access network device and the core network device is a message of the first tag. In one example, after receiving a message sent by the first tag to the core network device, the access network device sends the message to the core network device by using the first identifier corresponding to the first tag, and after receiving the message, the core network device determines that the message is from the first tag corresponding to the first identifier based on the first identifier carried in the message. In another example, when the core network device sends a message to the first tag, the core network device sends the message to the access network device by using the first identifier corresponding to the first tag, and after receiving the message, the access network device sends the message to the first tag corresponding to the first identifier based on the first identifier carried in the message.

[0238] In this scenario, the access network device and the core network device perform transmissions on messages for the first tag based on a first identifier assigned by the core network device to the first tag.

[0239] Optionally, in another scenario of the above embodiment, the method 400 further includes: after receiving the second message sent by the first tag to the core network device, the access network device assigns a second identifier to the first tag based on the second message; the access network device sends the correspondence between the second identifier and the first tag to the core network device; in other words, the core network device receives the correspondence between the second identifier and the first tag from the access network device and stores the correspondence; in this way, both the access network device and the core network device store the correspondence between the second identifier and the first tag.

[0240] The second identifier is used for transmitting the message of the first tag between the access network device and the core network device, in other words, the second identifier is used to identify the transmission channel or resource used for transmitting the message of the first tag between the access network device and the core network device, in other words, the second identifier is used to identify that the message communicated between the access network device and the core network device is the message of the first tag. The correspondence between the second identifier and the first tag can be carried in the second message or in another message. This is not limited.

[0241] The method for using the second identifier is the same as the method for using the first identifier. For details, please refer to the above description. The details will not be described again.

[0242] In this scenario, the access network device and the core network device perform transmissions on the message of the first tag based on a second identifier assigned by the access network device to the first tag.

[0243] Optionally, in another scenario of the above embodiment, method 400 further includes: after receiving a second message sent by the first tag to the core network device, the access network device assigns a second identifier to the first tag based on the second message; the access network device sends a correspondence between the second identifier and the first tag to the core network device, in other words, the core network device receives the correspondence between the second identifier and the first tag from the access network device and stores the correspondence; after receiving a second message from the first tag, the core network device assigns a first identifier to the first tag based on the second message; the core network device sends the correspondence between the first identifier and the first tag to the access network device, in other words, the access network device receives the correspondence between the first identifier and the first tag from the core network device and stores the correspondence; in this way, both the access network device and the core network device store the correspondence between the first identifier and the first tag and the correspondence between the second identifier and the first tag.

[0244] The first identifier and the second identifier are used for transmitting the message of the first tag between the access network device and the core network device, in other words, the first identifier and the second identifier are used to identify a transmission channel or resource used for transmitting the message of the first tag between the access network device and the core network device, in other words, the first identifier and the second identifier are used to identify that the message communicated between the access network device and the core network device is a message of the first tag. In one example, after receiving the message sent by the first tag to the core network device, the access network device sends the message to the core network device by using the first identifier and the second identifier corresponding to the first tag, and after receiving the message, the core network device determines that the message is from the first tag corresponding to the first identifier based on the first identifier carried in the message. In another example, when a core network device sends a message to a first tag, the core network device sends the message to an access network device by using a first identifier corresponding to the first tag and a second identifier, and after receiving the message, the access network device sends a message to the first tag corresponding to the second identifier based on the second identifier carried in the message.

[0245] In this scenario, the access network device and the core network device perform transmissions on the first tag message based on the first identifier and the second identifier.

[0246] The first identifier and / or the second identifier may be a next generation application protocol (NGAP) ID or a next generation application protocol ID.

[0247] Optionally, in another scenario of the above embodiment, method 400 further includes: the core network device releases the correspondence between the identifier and the first tag when the state of the first tag is switched from a registered state to a deregistered state, and the identifier is used for transmitting messages of the first tag between the core network device and the access network device; and / or method 400 further includes: when the state of the first tag is switched from a registered state to a deregistered state, the core network device sends a ninth message to the access network device; in other words, the access network device receives a ninth message from the core network device, and the ninth message indicates that the inventory for the first tag is completed; and the access network device releases the correspondence between the identifier and the first tag based on the ninth message. The identifier includes a first identifier assigned to the first tag by the core network device and / or a second identifier assigned to the first tag by the access network device.

[0248] For example, in a scenario in which an access network device and a core network device perform transmission on a message of a first tag based on a first identifier assigned to the first tag by the core network device, the access network device and the core network device release the correspondence between the first identifier and the first tag.

[0249] In another example, in a scenario in which an access network device and a core network device perform transmission on a message of a first tag based on a second identifier assigned by the access network device to the first tag, the access network device and the core network device release the correspondence between the second identifier and the first tag.

[0250] In another example, in a scenario in which an access network device and a core network device perform transmission on a message of a first tag based on a first identifier and a second identifier, the access network device and the core network device release a correspondence between the first identifier and the first tag and a correspondence between the second identifier and the first tag.

[0251] Optionally, in another scenario of the above embodiment, method 400 further includes: the core network device releases the correspondence between the identifier and the first tag when the state of the first tag is switched from a registered state to a deregistered state, and the identifier is used for transmitting messages of the first tag between the core network device and the access network device; and / or method 400 further includes: the access network device starts a third timer when the state of the first tag is switched from a deregistered state to a registered state, and the third timer is configured to maintain the correspondence between the identifier and the first tag; and the access network device releases the correspondence between the identifier and the first tag when the third timer expires. The identifier includes a first identifier assigned to the first tag by the core network device and / or a second identifier assigned to the first tag by the access network device.

[0252] For example, in a scenario in which an access network device and a core network device perform transmission on a message of a first tag based on a first identifier assigned to the first tag by the core network device, the access network device and the core network device release the correspondence between the first identifier and the first tag.

[0253] In another example, in a scenario in which an access network device and a core network device perform transmission on a message of a first tag based on a second identifier assigned by the access network device to the first tag, the access network device and the core network device release the correspondence between the second identifier and the first tag.

[0254] In another example, in a scenario in which an access network device and a core network device perform transmission on a message of a first tag based on a first identifier and a second identifier, the access network device and the core network device release a correspondence between the first identifier and the first tag and a correspondence between the second identifier and the first tag.

[0255] Optionally, when the access network device maintains the correspondence between the identifier and the first tag based on a third timer, the method 400 further includes: the access network device resets or refreshes the third timer based on a message between the first tag and the core network device. That is, when no message exchange is performed between the first tag and the core network device, the access network device may release the correspondence between the identifier and the first tag. For a description of the message between the first tag and the core network device, please refer to the above description. Details will not be described again.

[0256] Optionally, the timing period of the third timer may be set based on the capability of the first tag, in which case the access network device may not reset or refresh the third timer based on messages between the first tag and the core network device.

[0257] In this way, based on method 400, the tag state can be managed in a scenario where an inventory is performed on the tag by using air interface wireless technology. Furthermore, compared with the complex state changes in the prior art, the simplification of the tag state into registered and unregistered states helps to simplify the management of the tag state.

[0258] Optionally, in another scenario of the above embodiment, since the tag (e.g., a passive tag or a semi-passive tag) has weak capabilities, the message received or sent by the tag is as short as possible. Therefore, based on existing NAS messages, the present application provides a lightweight NAS message by compressing the packet header of the NAS message. All messages (e.g., the second message to the seventh message) between the first tag and the core network device may use the packet header below. In other words, all messages (e.g., the second message to the seventh message) between the first tag and the core network device may be the lightweight NAS message provided in the present application. FIG. 5 is an example of a lightweight common NAS message according to the present application.

[0259] Figure 5(a) shows the format of an existing common NAS message. The packet header includes an extended protocol discriminator and a security header type or PDU session identity. The extended protocol discriminator occupies one byte, and the security header type or PDU session identity occupies one byte, so in this case the packet header occupies a total of two bytes.

[0260] 5(b) shows Format 1 of a lightweight common NAS message according to the present application. When security protection does not need to be implemented for a message, the packet header of the lightweight common NAS message need only include a protocol discriminator, which may reuse an existing extended protocol discriminator. In this way, the packet header of the lightweight common NAS message in Format 1 occupies one byte, which is reduced compared to the existing common NAS message. However, Format 1 is not scalable, and NAS messages that support security protection cannot be extended.

[0261] 5(c) shows Format 2 of the lightweight common NAS message according to the present application. In Format 2, a short protocol discriminator of 4 bits is used, and the size of the protocol discriminator and security header type is compressed to 1 byte. In this way, the packet header of the lightweight common NAS message of Format 2 still occupies 1 byte, which is reduced by 1 byte compared to the existing common NAS message.

[0262] Furthermore, format 2 is compatible with and can be adapted to unsecured and secured messages. When security does not need to be enforced on a message, the security header type can be set to "unsecured" and the packet header may not include a message authentication code and a sequence number, as shown in Figure 5(c). When security needs to be enforced on a message, the security header type can be set to "secured". The format of a lightweight secure NAS message is shown in Figure 6.

[0263] FIG. 6 is an example of a lightweight secure NAS message according to the present application.

[0264] Figure 6(a) shows the format of an existing secure NAS message. The packet header includes an extended protocol discriminator, a security header type, a message authentication code, and a sequence number. The extended protocol discriminator and security header type each occupy one byte, the message authentication code occupies four bytes, and the sequence number occupies one byte. In this case, the packet header occupies a total of seven bytes.

[0265] 6(b) shows the format of a lightweight secure NAS message according to the present application. In particular, a 4-bit short protocol discriminator is used, and the size of the protocol discriminator and security header type is compressed to 1 byte. The message authentication code and sequence number may reuse existing message authentication codes and sequence numbers. In this way, the packet header of the lightweight secure NAS message occupies a total of 6 bytes, which is a 1-byte reduction compared to existing secure NAS messages.

[0266] Optionally, in another scenario of the above embodiment, after the core network device delivers an inventory command (e.g., a read command and a write command) to the tag, in some cases the tag needs to report data or parameters corresponding to the inventory command to the core network device, for example, data read by the core network device or alarm data of the tag.

[0267] Table 1 shows the content of the existing 3GPP UE configuration update complete message. As shown in Table 1, the content of the configuration update complete message includes an extended protocol discriminator, a security header type, a spare half octet, and a configuration update complete message identity. The existing configuration update complete message cannot carry data returned by a tag.

[0268] [Table 1]

[0269] In a possible implementation, the configuration update complete message may be extended so that the tag may report data or parameters corresponding to the inventory command to the core network device by using the configuration update complete message.

[0270] In one example, an information element identifier (IEI) type may be added to an existing configuration update complete message to correspond to an inventory command and carry data or parameters reported by the tag to the core network device. For example, a tag configuration response data IEI may be added to a configuration update complete message to correspond to an inventory command and carry data or parameters reported by the tag to the TMF or AMF.

[0271] Table 2 is an example of the contents of a configuration update complete message provided in this application. As shown in Table 2, the contents of the configuration update response message include an extended protocol discriminator, a security header type, a spare half-octet, a configuration update complete message identification, and tag configuration response data. 9.11.3.xx indicates a type or reference that can be distinguished from existing types or references.

[0272] [Table 2]

[0273] In another possible implementation, a new message may be added and the tag may report data or parameters corresponding to the inventory command to the core network device by using the new message.

[0274] In one example, a configuration update response message may be added, which carries a tag configuration response data information element to carry data or parameters reported by the tag in response to the inventory command to the core network device.

[0275] Table 3 is an example of the contents of a configuration update response message. As shown in Table 3, the contents of the configuration update response message include an extended protocol discriminator, a security header type, a spare half-octet, a configuration update response message identity, and tag configuration response data. 9.x and 9.11.3.xx indicate types or references that can be distinguished from existing types or references.

[0276] [Table 3]

[0277] FIG. 7 is a schematic flow chart of a tag inventory method 700 according to the present application.

[0278] The method 700 may include at least some of the following:

[0279] Note that the initial state of an inventoried tag may be in an unregistered state.

[0280] Step 701: A core network device receives a third request message used to request inventorying an inventory target tag.

[0281] For example, as shown in FIG. 7, the core network device receives a third request message from the AF; in other words, the AF sends a third request message to the core network device.

[0282] The core network device may be a TMF or may be another network element having the functionality of a TMF, for example, an AMF.

[0283] The third request message may carry information about the inventoried tag and / or the geographic area the inventoried tag is located in. See step 401 for a detailed description of the information about the inventoried tag.

[0284] Optionally, the third request message carries a quick inventory command.

[0285] Assume that the inventoried tags include a first tag, which is used in method 700 as an example to describe the tag inventory method provided in this application.

[0286] Step 702: The access network device receives a fourth request message used to request to inventory the inventoried tag.

[0287] For example, as shown in FIG. 7, the access network device receives a fourth request message from the core network device, in other words, the core network device sends a fourth request message to the core network device.

[0288] In particular, after receiving the third request message, the core network device sends a fourth request message to the access network device based on the third request message. For example, when the third request message includes information about the geographical area where the inventory target tag is located, the core network device determines the access network device to which the inventory target tag belongs based on the information about the geographical area where the inventory target tag is located, and sends a fourth request message to the access network device.

[0289] The fourth request message may carry information about the inventoried tags, see step 401 for a detailed description of the information about the inventoried tags. Optionally, the third request message carries a quick inventory command. Step 703: The access network device sends a first message to the inventory target tag based on the fourth request message.

[0290] The first message is used to request that the inventoried tag be inventoried.

[0291] Step 704: After receiving the first message, the first tag accesses the access network device.

[0292] For the implementation of steps 703 and 704, please refer to steps 403 and 404. The details will not be described again here.

[0293] Step 705: The access network device sends a quick inventory command to the first tag; in other words, the first tag receives a quick inventory command from the access network device.

[0294] Step 706: The first tag sends the identifier of the first tag to the access network device based on the quick inventory command; in other words, the access network device receives the identifier of the first tag.

[0295] Step 707: The access network device sends the identifier of the first tag to the core network device; in other words, the core network device receives the identifier of the first tag sent by the access network device.

[0296] Step 708: The core network device sends the identifier of the first tag to the AF, or the AF receives the identifier of the first tag sent by the core network device.

[0297] In this manner, a quick inventory for a tag can be implemented according to method 700. During the quick inventory for a tag, the access network device performs an inventory for the tag and feeds the tag back to the core network device or the AF in a unified manner. The first tag and the core network device may not need to switch the state of the first tag between registered and unregistered states as described in method 400.

[0298] The methods provided in this application are described in detail below with reference to specific examples.

[0299] In the following embodiments, an example in which the access network device is a base station and the core network device is a TMF or AMF is used for explanation. The tag does not have the ability to actively send messages or information, for example, a passive tag or a semi-passive tag. The access network device has the ability to inventory the tag.

[0300] Example 1

[0301] FIG. 8 is a diagram of a tag state machine according to one embodiment of the present application.

[0302] The solid arrows in Figure 8 indicate the transmission or reception of messages. Figure 8 describes the tag state machine on the tag side and the tag state machine on the network side (e.g., AMF side or TMF side) based on the network architecture shown in Figure 3.

[0303] (1) 5GMM-deregistered state

[0304] After receiving the excitation provided by the base station (i.e., the tag is powered on), the tag performs a simplified initial automatic network selection and enters the 5GMM de-registration state. 5GMM stands for 5GS mobility management, and 5GS stands for 5th generation system.

[0305] (2) Changing from 5GMM unregistered to 5GMM-registered

[0306] During inventory, the tag sends a registration request to the network by using a lightweight NAS message. After receiving the registration request from the tag, the network sends a registration accept to the tag by using a lightweight NAS message. Optionally, the network further performs authentication on the tag. When the authentication on the tag is successful (i.e., the tag is valid), the network sends an authentication accept to the tag by using a lightweight NAS message. For a detailed description of the lightweight NAS message, see the description of Figure 5.

[0307] In a possible implementation, when sending a registration request, after receiving a registration accept, or after receiving an authentication accept, the tag sets its state to the 5GMM registered state. Only tags in the registered state can receive lightweight NAS messages sent later by the network.

[0308] In a possible implementation, after receiving a registration request from the tag, after returning a registration accept to the tag, or after returning an authentication accept to the tag, the network sets the tag's state on the network side to 5GMM registered state.

[0309] The network may then perform the next operation on the tag in the 5GMM registered state, for example, an inventory operation, a paging operation, or a tag configuration update operation, where the tag configuration update operation may be reading or writing data, etc. Furthermore, in the process of performing the inventory operation, the paging operation, and the tag configuration update operation, the tag state machine no longer changes, i.e., the tag remains in the 5GMM registered state on both the tag side and the network side. For a tag, after the tag enters the registered state, the tag remains in the 5GMM registered state as long as lightweight NAS messages are sent or received.

[0310] (3) Change from 5GMM registered state to 5GMM unregistered state

[0311] On the tag side, the tag enters the 5GMM deregistered state from the 5GMM registered state when the tag is powered down, the tag is killed, the tag has not received a lightweight NAS message for a period of time, or the tag receives an indication to inventory the next tag.

[0312] On the network side, after performing local deregistration on the tag (e.g., when a timer expires or no action is performed on the tag for a certain period of time), the network sets the state of the tag, which is maintained on the network, to the 5GMM deregistered state.

[0313] Example 2

[0314] FIG. 9 is an example of a tag state change procedure according to one embodiment of the present application.

[0315] The dashed lines in Figure 9 represent optional steps. The tag is initially in an unregistered state.

[0316] Step 901: The AF sends an inventory request to the TMF or AMF.

[0317] Correspondingly, the TMF or AMF receives an inventory request from the AF.

[0318] An inventory request may be a request for an action on a tag, such as a quick inventory, inventory, read, or write. The inventory request may include tag identification information and information about the geographic area in which the tag is located. The tag identification information indicates the tag to be inventoried and may be the tag's TID, EPC, etc.

[0319] Note that there can be one or more tags. For example, when an inventory is performed on a tag, the tag identification can be the TID or EPC of the tag. In another example, when an inventory is performed on multiple tags, the tag identification can be a group of TIDs, a TID range, a group of EPCs, or an EPC range.

[0320] Step 902: The TMF or AMF determines the base station to which the tag belongs based on information about the geographic area in which the tag is located.

[0321] Step 903: The TMF or AMF parses the inventory request and delivers a corresponding inventory command to the base station based on the parsing result.

[0322] The inventory command may include tag identification information, which indicates the tag to be inventoried and may be the tag's TID, EPC, etc.

[0323] For example, when an inventory request is used to request that a quick inventory, inventory, read, or write be performed on a tag, the inventory command may be a quick inventory command, an inventory command, a read command, or a write command.

[0324] Step 904: The base station sends selection information (or selection command) to the tag based on the received inventory command.

[0325] In response, the tag receives selection information from the base station.

[0326] The selection information is used to select tags to be inventoried.

[0327] In a possible implementation, tags are selected by matching the tag's storage area flags (e.g., mask matching or decision value matching). In this case, the selection information may include conditions that must be met by the value of the tag's corresponding storage area. The TID storage area is used as an example. The selection information may include a value or a range of values ​​for the TID storage area. In this case, tags whose TID value is a value in the selection information or whose TID value is within the range of values ​​in the selection information are inventoried tags.

[0328] Step 905: The tag determines, based on the received selection information, that the requirements in the selection information are met, and initiates a random access procedure.

[0329] For example, the selection information is used to select tags with TID values ​​from 1 to 5. Tags with TID values ​​from 1 to 5 meet the requirements and the random access procedure is initiated.

[0330] The specific implementation of the random access procedure is not limited in this application. In a possible implementation, the base station sends a query message to the tag, and after receiving the query message, the tag returns a random number to the base station, and after receiving the random number from the tag, the base station returns an ACK message to the tag, and the ACK message may carry the random number sent by the tag. The random access by the tag may be implemented by using a message exchange process.

[0331] An explanation is given below by using an example in which tag 1 successfully performs random access.

[0332] Step 906: Tag 1 that successfully performs random access sends a registration request to TMF or AMF based on a lightweight NAS message.

[0333] In response, the TMF or AMF receives a registration request from tag 1.

[0334] The lightweight NAS message includes a registration request and an identifier of tag 1. The identifier of tag 1 can be the TID or EPC of tag 1, and EPC is used as an example in Figure 9. For a detailed description of the lightweight NAS message, please refer to the description of Figure 5.

[0335] In particular, as shown in steps 906a to 906c of FIG. 9, Tag 1 sends a lightweight NAS message carrying a registration request to the TMF or AMF through the base station.

[0336] Step 906a: Tag 1 sends a lightweight NAS message to the base station, and correspondingly, the base station receives the lightweight NAS message from Tag 1. Step 906b: When the lightweight NAS message is transmitted transparently, the base station assigns NGAP ID 1 to the EPC of Tag 1, and all messages transmitted thereafter by using NGAP ID 1 are from Tag 1. Step 906c: The base station sends a lightweight NAS message from Tag 1 to the TMF or AMF by using NGAP ID 1, and correspondingly, the TMF or AMF receives the lightweight NAS message.

[0337] Optionally, Tag1 sets its state to registered based on a sent lightweight NAS message containing a registration request.

[0338] Optionally, after receiving a registration request from tag 1, the TMF or AMF determines, based on the inventory request, that there is a command to be sent to tag 1 subsequently. In this case, the TMF or AMF sets the state of tag 1 maintained in the TMF or AMF to the registered state.

[0339] It should be noted that the base station's assignment of NGAP ID1 to the EPC of tag1 can alternatively be described as follows: the base station creates or initiates an association between the EPC of tag1 and NGAP ID1, or the base station creates an association relationship or correspondence between the EPC of the tag and NGAP ID1 and stores the association relationship or correspondence.

[0340] Step 907: The TMF or AMF assigns NGAP ID2 to the ECP with tag1.

[0341] Then, the TMF or AMF sends and receives messages for Tag 1 based on NGAP ID 2. In other words, all messages sent by using NGAP ID 2 are from Tag 1.

[0342] Similarly, the TMF or AMF assigning NGAP ID2 to the EPC of tag1 can alternatively be described as follows: the TMF or AMF creates or initiates an association between the EPC of tag1 and NGAP ID2, or the TMF or AMF creates an association relationship or correspondence relationship between the EPC of the tag and NGAP ID2 and stores the association relationship or correspondence relationship.

[0343] Step 908: If authentication needs to be performed for the tag type of tag 1, the authentication procedure for tag 1 may be performed after the registration request is sent to the TMF or AMF.

[0344] Whether tag1 is valid can be determined by using an authentication procedure. In the authentication procedure for tag1, authentication-related lightweight NAS messages are exchanged between tag1 and the TMF or AMF and between the TMF or AMF and the AF.

[0345] Optionally, tag 1 may alternatively set its state to registered based on an authentication-related lightweight NAS message. For example, when tag 1 receives an authentication accept sent by the TMF or AMF using a lightweight NAS message, tag 1 changes its state from unregistered to registered.

[0346] Optionally, after sending an authentication-related lightweight NAS message to tag 1, the TMF or AMF may set the state of tag 1 maintained in the TMF or AMF to registered. For example, after sending an authentication accept to tag 1 by using a lightweight NAS message, the TMF or AMF sets the state of tag 1 maintained in the TMF or AMF to registered.

[0347] Step 908 is an optional step.

[0348] Step 909: After receiving the registration request from Tag1, the TMF or AMF may send a registration response (eg, registration accept) to Tag1 by using a lightweight NAS message.

[0349] In response, Tag 1 receives a registration response from the TMF or AMF.

[0350] Optionally, tag1 may alternatively set its state to registered based on a lightweight NAS message carrying a registration response. For example, when tag1 receives a registration accept sent by the TMF or AMF using a lightweight NAS message, tag1 changes its state from unregistered to registered.

[0351] Optionally, after sending a registration response to tag1 by using a lightweight NAS message, the TMF or AMF may set the state of tag1 maintained in the TMF or AMF to registered. For example, after sending a registration accept to tag1 by using a lightweight NAS message, the TMF or AMF sets the state of tag1 maintained in the TMF or AMF to registered.

[0352] Step 909 is an optional step.

[0353] Step 910: Tag1 and the TMF or AMF perform a user configuration update (UCU) procedure.

[0354] In particular, after both the state of tag 1 on the tag 1 side and the state of tag 1 on the AMF side or AMF side are registered, the TMF or AMF sends a UCU command to tag 1 by using a lightweight NAS message, and after receiving the UCU command from the TMF or AMF, the tag 1 sends a reply to the UCU command to the TMF or AMF by using a lightweight NAS message. The UCU command may be an inventory command, a read command, a write command, a kill command, etc.

[0355] Optionally, Tag1 may alternatively set its state to unregistered based on a lightweight NAS message carrying a kill command.

[0356] Optionally, after sending a kill command to Tag1 by using a lightweight NAS message, the TMF or AMF may set the state of Tag1 maintained in the TMF or AMF to unregistered.

[0357] Step 910 is an optional step.

[0358] Step 911: When the TMF or AMF finds that the inventory operation performed on tag 1 is finished (i.e., there is no next lightweight NAS message that needs to be sent), the TMF or AMF releases NGAP ID2 between the TMF or AMF and the base station and sets the state of tag 1 maintained in the TMF or AMF to unregistered.

[0359] It should be noted that the TMF or AMF releasing NGAP ID2 can alternatively be described as follows: the TMF or AMF releases the association between the EPC of tag1 and NGAP ID2, or the TMF or AMF deletes the association or correspondence between the EPC of tag1 and NGAP ID2, or the TMF or AMF performs a local deregistration on tag1.

[0360] It is further noted that if step 910 is performed and in step 910 the TMF or AMF sets the state of tag 1 maintained in the TMF or AMF to an unregistered state based on a kill command sent to tag 1, the TMF or AMF may not change the state of tag 1 maintained in the TMF or AMF in step 911.

[0361] Step 912: The TMF or AMF sends a command to the base station to inventory the next tag.

[0362] In response, the base station receives a command from the TMF or AMF to inventory the next tag.

[0363] The command to inventory the next tag is not carried in a NAS message or a lightweight NAS message, ie, the message is sent to the base station, and the base station can identify or parse the message.

[0364] Step 913: The base station releases NGAP ID1 between the base station and the TMF or AMF based on the command to inventory the next tag.

[0365] It should be noted that the base station releasing NGAP ID1 can alternatively be described as follows: the base station releases the association between the EPC of tag1 and NGAP ID1, or the base station deletes the association relationship between the EPC of tag1 and NGAP ID1, or the base station performs local deregistration for tag1.

[0366] Step 914: The base station performs the next round of the inventory procedure.

[0367] In particular, the base station initiates a new round of random access procedures based on a command to inventory the next tag.

[0368] For example, the base station sends a query message to the tag, and the query message is refreshed. When receiving the query message from the base station again, tag 1 sets its state to unregistered based on the query message.

[0369] Furthermore, it should be noted that when the inventory command delivered by the TMF or AMF to the base station is a quick inventory command, no message exchange needs to be performed between the tag and the TMF or AMF, and the base station collects and feeds back the EPC of the tag in a unified manner. In this case, the state of the tag does not need to be changed on the tag and the TMF or AMF.

[0370] Example 3

[0371] 10A and 10B are another example of a tag state change procedure according to one embodiment of the present application.

[0372] The dashed lines in Figures 10A and 10B represent optional steps. The tag is initially in an unregistered state.

[0373] Step 1001: The AF sends an inventory request to the TMF or AMF.

[0374] Correspondingly, the TMF or AMF receives an inventory request from the AF.

[0375] An inventory request may be a request for an action on a tag, such as a quick inventory, inventory, read, or write. The inventory request may include tag identification information and information about the geographic area in which the tag is located. The tag identification information indicates the tag to be inventoried and may be the tag's TID, EPC, etc.

[0376] Note that there can be one or more tags. For example, when an inventory is performed on a tag, the tag identification can be the TID or EPC of the tag. In another example, when an inventory is performed on multiple tags, the tag identification can be a group of TIDs, a TID range, a group of EPCs, or an EPC range.

[0377] Step 1002: The TMF or AMF determines the base station to which the tag belongs based on information about the geographic area in which the tag is located.

[0378] Step 1003: The TMF or AMF parses the inventory request and delivers a corresponding inventory command to the base station based on the parsing result.

[0379] The inventory command may include tag identification information, which indicates the tag to be inventoried and may be the tag's TID, EPC, etc.

[0380] For example, when an inventory request is used to request that a quick inventory, inventory, read, or write be performed on a tag, the inventory command may be a quick inventory command, an inventory command, a read command, or a write command.

[0381] Step 1004: The base station sends selection information (or selection command) to the tag based on the received inventory command.

[0382] In response, the tag receives selection information from the base station.

[0383] The selection information is used to select tags to be inventoried.

[0384] In a possible implementation, tags are selected by matching the tag's storage area flags (e.g., mask matching or decision value matching). In this case, the selection information may include conditions that must be met by the value of the tag's corresponding storage area. The TID storage area is used as an example. The selection information may include a value or a range of values ​​for the TID storage area. In this case, tags whose TID value is a value in the selection information or whose TID value is within the range of values ​​in the selection information are inventoried tags.

[0385] Step 1005: The tag determines, based on the received selection information, that the requirements in the selection information are met, and initiates a random access procedure.

[0386] For example, the selection information is used to select tags with TID values ​​from 1 to 5. Tags with TID values ​​from 1 to 5 meet the requirements and the random access procedure is initiated.

[0387] The specific implementation of the random access procedure is not limited in this application. In a possible implementation, the base station sends a query message to the tag, and after receiving the query message, the tag returns a random number to the base station, and after receiving the random number from the tag, the base station returns an ACK message to the tag, and the ACK message may carry the random number sent by the tag. The random access by the tag may be implemented by using a message exchange process.

[0388] An explanation is given below by using an example in which tag 1 successfully performs random access.

[0389] Step 1006: Tag 1 that successfully performs random access sends a registration request to TMF or AMF based on a lightweight NAS message.

[0390] In response, the TMF or AMF receives a registration request from tag 1.

[0391] The lightweight NAS message includes a registration request and an identifier of tag 1. The identifier of tag 1 can be the TID or EPC of tag 1, and EPC is used as an example in Figures 10A and 10B. For a detailed description of the lightweight NAS message, please refer to the description of Figure 5.

[0392] In particular, as shown in steps 1006a to 1006c of FIG. 10A, tag 1 sends a lightweight NAS message carrying a registration request to the TMF or AMF through the base station.

[0393] Step 1006a: Tag 1 sends a lightweight NAS message to the base station, and correspondingly, the base station receives the lightweight NAS message from Tag 1. Step 1006b: When the lightweight NAS message is sent transparently, the base station assigns NGAP ID1 to the EPC of Tag 1 and starts Timer 1. All messages sent by using NGAP ID1 during the timing period of Timer 1 are from Tag 1. In other words, the base station maintains NGAP ID1 based on Timer 1. Step 1006c: The base station sends a lightweight NAS message from Tag 1 by using NGAP ID1 to the TMF or AMF, and correspondingly, the TMF or AMF receives the lightweight NAS message.

[0394] Optionally, tag 1 sets its state to registered based on a sent lightweight NAS message containing a registration request and starts timer 2. Timer 2 is configured to maintain the registered state of tag 1. Specifically, during the execution or timing period of timer 2, tag 1 remains in the registered state. When timer 2 expires or the timing period of timer 2 expires, tag 1 no longer maintains the registered state or tag 1 enters the unregistered state.

[0395] Optionally, after receiving a registration request from tag 1, the TMF or AMF determines, based on the inventory request, that there is a command to be sent to tag 1 thereafter. In this case, the TMF or AMF sets the state of tag 1 maintained in the TMF or AMF to a registered state and starts Timer 3. Timer 3 is configured to maintain the registered state of tag 1. Specifically, during the execution or timing period of Timer 3, the state of tag 1 maintained in the TMF or AMF remains in the registered state. When Timer 3 expires or the timing time of Timer 3 expires, the state of tag 1 that is no longer maintained in the TMF or AMF is the registered state; in other words, the TMF or AMF sets the state of tag 1 maintained in the TMF or AMF to a deregistered state.

[0396] It should be noted that the base station's assignment of NGAP ID1 to the EPC of tag1 can alternatively be described as follows: the base station creates or initiates an association between the EPC of tag1 and NGAP ID1, or the base station creates an association relationship or correspondence between the EPC of the tag and NGAP ID1 and stores the association relationship or correspondence.

[0397] Step 1007: The TMF or AMF assigns NGAP ID2 to the ECP of tag1 and starts timer4.

[0398] During the timing period of Timer 4, the TMF or AMF sends and receives messages of Tag 1 based on NGAP ID 2. In other words, all messages sent by using NGAP ID 2 are from Tag 1, or the TMF or AMF maintains NGAP ID 2 based on Timer 4.

[0399] Similarly, the TMF or AMF assigning NGAP ID2 to the EPC of tag1 can alternatively be described as follows: the TMF or AMF creates or initiates an association between the EPC of tag1 and NGAP ID2, or the TMF or AMF creates an association relationship between the EPC of the tag and NGAP ID2 and stores the association relationship.

[0400] It should be noted that Timer 3 or Timer 4 may be the same timer or may be different timers. This is not limited in the present application. Furthermore, in the present application, the initial value of Timer 1, Timer 2, Timer 3, or Timer 4 may be set based on the capability of Tag 1. During an exchange between Tag 1 and the TMF or AMF, Timer 1, Timer 2, Timer 3, or Timer 4 does not need to be refreshed. Alternatively, Timer 1, Timer 2, Timer 3, or Timer 4 may be refreshed based on an exchange message between Tag 1 and the TMF or AMF (e.g., an authentication-related lightweight NAS message or a lightweight NAS message in the following UCU procedure).

[0401] Step 1008: If authentication needs to be performed for the tag type of tag 1, the authentication procedure for tag 1 may be performed after the registration request is sent to the TMF or AMF.

[0402] Whether tag1 is valid can be determined by using an authentication procedure. In the authentication procedure for tag1, authentication-related lightweight NAS messages are exchanged between tag1 and the TMF or AMF and between the TMF or AMF and the AF.

[0403] Optionally, if the state of tag1 is already in registered state, timer1, timer2, timer3 or timer4 may be refreshed based on authentication-related lightweight NAS messages.

[0404] Optionally, Tag 1 may alternatively set its state to registered based on an authentication-related lightweight NAS message and start Timer 2. For a description of Timer 2, please refer to the above description. Details will not be described again here. For example, when Tag 1 receives an authentication accept sent by the TMF or AMF by using a lightweight NAS message, Tag 1 changes its state from unregistered to registered and starts Timer 2.

[0405] Optionally, after sending an authentication-related lightweight NAS message to Tag 1, the TMF or AMF may set the state of Tag 1 maintained in the TMF or AMF to registered and start timer 3. For a description of Timer 3, please refer to the description above. The details will not be described again here. For example, after sending an authentication-accept to Tag 1 by using a lightweight NAS message, the TMF or AMF sets the state of Tag 1 maintained in the TMF or AMF to registered and start timer 3.

[0406] Step 1008 is an optional step.

[0407] Step 1009: After receiving the registration request from Tag1, the TMF or AMF may send a registration response (eg, registration accept) to Tag1 by using a lightweight NAS message.

[0408] In response, Tag 1 receives a registration response from the TMF or AMF.

[0409] Optionally, if the state of tag1 is already in a registered state, timer1, timer2, timer3, or timer4 may be refreshed based on a lightweight NAS message carrying a registration response.

[0410] Optionally, Tag1 may alternatively set its state to registered based on a lightweight NAS message carrying a registration response and start Timer 2. For a description of Timer 2, please refer to the description above. Details will not be described again here. For example, when Tag1 receives a registration accept sent by TMF or AMF by using a lightweight NAS message, Tag1 changes its state from unregistered to registered and starts Timer 2.

[0411] Optionally, after sending a registration response to Tag1 by using a lightweight NAS message, the TMF or AMF may set the state of Tag1 maintained in the TMF or AMF to registered state and start timer 3. For a description of timer 3, please refer to the description above. The details will not be described again here. For example, after sending a registration accept to Tag1 by using a lightweight NAS message, the TMF or AMF sets the state of Tag1 maintained in the TMF or AMF to registered state and start timer 3.

[0412] Step 1009 is an optional step.

[0413] Step 1010: Tag 1 and the TMF or AMF perform the UCU procedure.

[0414] In particular, after both the state of tag 1 on the tag 1 side and the state of tag 1 on the AMF side or AMF side are registered, the TMF or AMF sends a UCU command to tag 1 by using a lightweight NAS message, and after receiving the UCU command from the TMF or AMF, the tag 1 sends a reply to the UCU command to the TMF or AMF by using a lightweight NAS message. The UCU command may be an inventory command, a read command, a write command, a kill command, etc.

[0415] Optionally, timer 1, timer 2, timer 3, or timer 4 may be refreshed based on a lightweight NAS message during the UCU procedure.

[0416] Step 1010 is an optional step.

[0417] Then, when Timer 1 expires, the base station releases NGAP ID1. When Timer 2 expires, Tag 1 sets its state to unregistered. When Timer 3 expires, the TMF or AMF sets the state of Tag 1, which was maintained in the TMF or AMF, to unregistered. When Timer 4 expires, the TMF or AMF releases NGAP ID2.

[0418] It should be noted that the base station releasing NGAP ID1 can alternatively be described as follows: the base station releases the association between the EPC of tag1 and NGAP ID1, or the base station deletes the association relationship between the EPC of tag1 and NGAP ID1, or the base station performs local deregistration for tag1. Similarly, the TMF or AMF releasing NGAP ID2 can alternatively be described as follows: the TMF or AMF releases the association between the EPC of tag1 and NGAP ID2, or the TMF or AMF deletes the association relationship between the EPC of tag1 and NGAP ID2, or the TMF or AMF performs local deregistration for tag1.

[0419] Furthermore, it should be further noted that when the inventory command delivered by the TMF or AMF to the base station is a quick inventory command, no message exchange needs to be performed between the tag and the TMF or AMF, and the base station collects and feeds back the EPC of the tag in a unified manner. In this case, the state of the tag does not need to be changed on the tag and the TMF or AMF.

[0420] The method provided in the present application has been described in detail above with reference to Figures 4 to 10A and 10B. The apparatus embodiment of the present application will be described in detail below with reference to Figures 11 and 12.

[0421] To implement the functions in the above embodiments, it can be understood that the device in Figure 11 or 12 includes corresponding hardware structures and / or software modules for implementing each function. Those skilled in the art should easily recognize that the present application can be implemented by hardware or a combination of hardware and computer software with reference to the units and method steps in the examples described in the embodiments disclosed herein.

[0422] 11 and 12 are diagrams of possible device structures according to embodiments of the present application, which may be configured to implement the functions of the first tag, the core network device, or the access network device in the above method embodiments, and thus can also implement the beneficial effects of the above method embodiments.

[0423] As shown in FIG. 11, the device 10 includes a transceiver unit 11 and a processing unit 12 .

[0424] When the apparatus 10 is configured to implement the function of the first tag in the above method embodiment, the transceiver unit 11 is configured to receive a first message from an access network device, where the first message is used to request inventorying of an inventoried tag, and the first tag belongs to the inventoried tag. The transceiver unit 11 and / or the processing unit 12 are configured to access the access network device. The transceiver unit 11 is further configured to send a second message, where the second message is used to request registration with a core network device. The processing unit 12 is further configured to switch the first tag from an unregistered state to a registered state after the second message is sent.

[0425] Optionally, the first message is further used to excite the inventoried tag.

[0426] Optionally, after the first tag sends the second message, the transceiver unit 11 is further configured to receive a third message, the third message indicating that the first tag has been successfully registered with the core network device, and the processing unit 12 is configured, in particular, to switch the first tag from an unregistered state to a registered state after the third message is received.

[0427] Optionally, after the first tag sends the second message, the transceiver unit 11 is further configured to send a fourth message, where the fourth message is used to request that authentication be performed on the first tag, and to receive a fifth message, where the fifth message indicates that authentication on the first tag has been successful, and the processing unit 12 is configured, in particular, to switch the first tag from an unregistered state to a registered state after the fifth message is received.

[0428] Optionally, after the first tag sends the second message, the transceiver unit 11 is further configured to receive a sixth message, which is used to request the first tag to perform authentication on an authentication server, and to send a seventh message when the authentication on the authentication server is successful, which seventh message indicates that the authentication on the authentication server has been successful, and the processing unit 12 is configured, in particular, to switch the first tag from an unregistered state to a registered state after the seventh message is sent.

[0429] Optionally, the processing unit 12 is further configured to start a first timer and change the first tag from a registered state to an unregistered state when the first timer expires.

[0430] Optionally, the processing unit 12 is further configured to reset the first timer based on a message between the first tag and the core network device.

[0431] Optionally, the transceiver unit 11 is further configured to receive an eighth message, the eighth message indicating to inventory the next tag, and the processing unit 12 is further configured to switch the first tag from a registered state to a deregistered state based on the eighth message.

[0432] When the apparatus 10 is configured to implement the functions of the core network device in the above method embodiments, the transceiver unit 11 is configured to receive a first request message used to request inventorying of an inventoried tag, send a first message to the inventoried tag through the access network device, the first message used to request inventorying of the inventoried tag, and receive a second message from a first tag among the inventoried tags, the second message used to request registration with the core network device, the first tag being a passive tag or a semi-passive tag. The processing unit 12 is configured to switch the state of the first tag stored in the core network device from an unregistered state to a registered state after the second message is received.

[0433] Optionally, after receiving the second message, the transceiver unit 11 is further configured to send a third message to the first tag, the third message indicating that the first tag has been successfully registered with the core network device, and the processing unit 12 is configured, in particular, to switch the state of the first tag stored in the core network device from an unregistered state to a registered state after the third message is sent.

[0434] Optionally, after sending the second message, the transceiver unit 11 is further configured to receive a fourth message from the first tag, the fourth message being used to request performing authentication on the first tag, and to send a fifth message to the first tag, the fifth message indicating successful authentication on the first tag. The processing unit 12 is configured, in particular, to switch the state of the first tag stored in the core network device from an unregistered state to a registered state after the fifth message is sent.

[0435] Optionally, after receiving the second message, the transceiver unit 11 is further configured to: send a sixth message to the first tag, the sixth message being used to request performing authentication on an authentication server, and receive a seventh message from the first tag, the seventh message indicating that the authentication on the authentication server has been successful. The processing unit 12 is particularly configured to switch the state of the first tag stored in the core network device from an unregistered state to a registered state after the seventh message is received.

[0436] Optionally, the processing unit 12 is further configured to start a second timer when the state of the first tag is switched from the unregistered state to the registered state, and to switch the state of the first tag stored in the core network device from the registered state to the unregistered state when the second timer expires.

[0437] Optionally, the processing unit 12 is further configured to reset the second timer based on a message between the first tag and the core network device.

[0438] Optionally, the processing unit 12 is configured to switch the state of the first tag stored in the core network device from a registered state to an unregistered state when the inventory for the first tag is completed.

[0439] Optionally, the transceiver unit 11 is further configured to send a ninth message to the access network device, the ninth message indicating that the inventory for the first tag is completed.

[0440] Optionally, the processing unit 12 is further configured to assign a first identifier to the first tag after the second message is received. The transceiver unit 11 is further configured to send the correspondence between the first identifier and the first tag to the access network device.

[0441] Optionally, the transceiver unit 11 is further configured to receive a correspondence between the second identifier and the first tag from the access network device.

[0442] Optionally, the processing unit 12 is further configured to release the correspondence between the first identifier and the first tag and / or the correspondence between the second identifier and the first tag when the state of the first tag is switched from a registered state to a deregistered state.

[0443] When the apparatus 10 is configured to implement the functions of the access network device in the above method embodiment, the transceiver unit 11 is configured to receive a second request message used to request that an inventory target tag be inventoried, and send a first message to the inventory target tag based on the second request message, where the first message is used to request that the inventory target tag be inventoried; receive a second message from a first tag among the inventory target tags after the first tag accesses the access network device, where the second message is used to request registration with the core network device; and send the second message to the core network device.

[0444] Optionally, the first message is further used to excite the inventoried tag.

[0445] Optionally, the processing unit 12 is configured to assign a second identifier to the first tag based on the second message, and the transceiver unit 11 is further configured to send a correspondence between the second identifier and the first tag to the core network device, and / or the transceiver unit 11 is further configured to receive the correspondence between the first identifier and the first tag from the core network device.

[0446] Optionally, the processing module 12 is further configured to start a third timer, and release the correspondence between the first identifier and the first tag and / or the correspondence between the second identifier and the first tag when the third timer expires.

[0447] Optionally, the processing unit 12 is further configured to reset a third timer based on a message between the first tag and the core network device.

[0448] Optionally, the transceiver unit 11 is further configured to receive a ninth message from the core network device, the ninth message indicating that an inventory for the first tag has been completed, and the processing unit 12 is further configured to release, based on the ninth message, a correspondence between the first identifier and the first tag and / or a correspondence between the second identifier and the first tag.

[0449] Optionally, the transceiver unit 11 is further configured to send an eighth message to the first tag, the eighth message indicating to inventory the next tag.

[0450] In another implementation, when the apparatus 10 is configured to implement the function of the first tag in the above method embodiment, the transceiver unit 11 is configured to receive a first message from an access network device, where the first message is used to request inventorying of an inventory target tag, and the first tag belongs to the inventory target tag. The transceiver unit 11 and / or the processing unit 12 are configured to access the access network device. The transceiver unit 11 is further configured to receive a quick inventory command from the access network device and send an identifier of the first tag to the access network device based on the quick inventory command.

[0451] Optionally, the first message is further used to excite the inventoried tag.

[0452] In another implementation, when the apparatus 10 is configured to implement the functions of the core network device in the above method embodiment, the transceiver unit 11 is configured to receive a third request message used to request a quick inventory to be performed on an inventory target tag, where the inventory target tag includes a first tag, send a fourth request message used to request a quick inventory to be performed on the inventory target tag to the access network device, receive an identifier of the first tag from the access network device, and send the identifier of the first tag to the application function network element.

[0453] In another implementation, when the apparatus 10 is configured to implement the functions of the access network device in the above method embodiment, the transceiver unit 11 is configured to receive a fourth request message used to request that a quick inventory be performed on the inventoried tag, and send a first message to the inventoried tag based on the fourth request message, where the first message is used to request that the inventoried tag be inventoried; send a quick inventory command to the first tag among the inventoried tags after the first tag accesses the access network device; receive an identifier of the first tag from the first tag; and send the identifier of the first tag to the core network device.

[0454] Optionally, the first message is further used to excite the inventoried tag.

[0455] For more detailed descriptions of the transceiver unit 11 and the processing unit 12, please refer to the related descriptions in the above method embodiments, and the details will not be described again here.

[0456] 12, the apparatus 20 includes a processor 21. The processor 21 is coupled to a memory 23, which is configured to store instructions. When the apparatus 20 is configured to implement the above-described method, the processor 21 is configured to execute the instructions in the memory 23 to implement the functions of the processing unit 12 described above.

[0457] Optionally, the device 20 further comprises a memory 23 .

[0458] Optionally, the device 20 further includes an interface circuit 22. The processor 21 and the interface circuit 22 are coupled to each other. It may be understood that the interface circuit 22 may be a transceiver or an input / output interface. When the device 20 is configured to implement the above-described method, the processor 21 is configured to execute instructions to implement the functions of the processing unit 12 described above, and the interface circuit 22 is configured to implement the functions of the transceiver unit 11 described above.

[0459] For example, when the device 20 is a chip used in a first tag, a core network device, or an access network device, the chip implements the functions of the first tag, the core network device, or the access network device in the above method embodiments. The chip receives information from another module (e.g., a radio frequency module or an antenna) in the first tag, the core network device, or the access network device, and the information is sent to the first tag, the core network device, or the access network device by the other device. Alternatively, the chip sends information to another module (e.g., a radio frequency module or an antenna) in the first tag, the core network device, or the access network device, and the information is sent to the other device by the first tag, the core network device, or the access network device.

[0460] The present application further provides a communication device including a processor. The processor is coupled to a memory. The memory is configured to store computer programs or instructions and / or data. The processor is configured to execute the computer programs or instructions stored in the memory or read the data stored in the memory to implement the method in the above method embodiments. Optionally, there are one or more processors. Optionally, the communication device includes a memory. Optionally, there are one or more memories. Optionally, the memory and the processor are integrated together or arranged separately.

[0461] The present application further provides a computer-readable storage medium, which stores computer instructions used to implement the method performed by the first tag, the core network device, or the access network device in the above method embodiments.

[0462] The present application further provides a computer program product including instructions, which, when executed by a computer, implement the method performed by the first tag, the core network device, or the access network device in the above method embodiments.

[0463] The present application further provides a communication system, which includes at least one of the first tag, the core network device, or the access network device in the above embodiments.

[0464] For the description of the relevant contents and beneficial effects of any one of the devices provided above, please refer to the corresponding method embodiments provided above, and the details will not be described again here.

[0465] It will be understood that the processor in the embodiments of the present application may be a central processing unit (CPU), or may be another general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a transistor logic device, a hardware device, or any combination thereof. A general-purpose processor may be a microprocessor or any conventional processor, etc.

[0466] The method steps in the embodiments of the present application may be implemented by hardware or by a processor executing software instructions. The software instructions may include corresponding software modules. The software modules may be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disk, removable hard disk, compact disc read-only memory (CD-ROM), or any other form of storage medium well known in the art. For example, the storage medium may be coupled to the processor, such that the processor can read information from and write information to the storage medium. Of course, the storage medium may alternatively be components of the processor. The processor and the storage medium may be disposed in an ASIC. Furthermore, the ASIC may be located in the first tag, the core network device, or the access network device. Of course, the processor and the storage medium may alternatively exist as separate components in the first tag, the core network device, or the access network device.

[0467] All or part of the above embodiments may be implemented by software, hardware, firmware, or any combination thereof. When software is used to implement an embodiment, all or part of the embodiment may be implemented in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, all or part of the procedures or functions in the embodiments of the present application are performed. The computer may be a general-purpose computer, a special-purpose computer, a computer network, a network device, user equipment, or another programmable device. The computer program or instructions may be stored in a computer-readable storage medium or transmitted from a computer-readable storage medium to another computer-readable storage medium. For example, the computer program or instructions may be transmitted from a website, computer, server, or data center to another website, computer, server, or data center via a wired or wireless method. The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device integrating one or more available media, such as a server or data center. The usable medium may be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape, or it may be an optical medium, such as a digital video disk, or it may be a semiconductor medium, such as a solid state drive.

[0468] In the embodiments of the present application, unless otherwise specified or there is no logical conflict, the terms and / or descriptions in different embodiments are consistent and may be cross-referenced, and the technical features in different embodiments may be combined based on their internal logical relationships to form new embodiments.

[0469] It can be understood that various numbers in the embodiments of the present application are only used for distinction to facilitate description, and are not used to limit the scope of the embodiments of the present application. The sequence numbers of the above processes do not mean the execution sequence, and the execution sequence of the processes should be determined based on the function and internal logic of the processes.

[0470] Unless otherwise specified, the meanings of all technical and scientific terms used in the embodiments of this application are the same as those commonly understood by those skilled in the art of this application. The terms used in this application are only intended to describe the purpose of specific embodiments and are not intended to limit the scope of this application. The above is an example for illustrative purposes, and the above example is only intended to help those skilled in the art understand the embodiments of this application and is not intended to limit the embodiments of this application to specific values ​​or specific scenario examples. It is clear that those skilled in the art can make various equivalent modifications or variations based on the examples described above, and such modifications and variations also fall within the scope of the embodiments of this application.

[0471] The above description is merely a specific implementation of the present application and does not limit the scope of protection of the present application. Any modifications or replacements that can be easily conceived by those skilled in the art within the technical scope disclosed in the present application shall fall within the scope of protection of the present application. Therefore, the scope of protection of the present application shall be subject to the scope of protection of the claims.

Claims

1. receiving a first message from an access network device by a first tag, the first message being used to request inventorying of an inventoried tag, the first tag belonging to the inventoried tag; accessing the access network device by the first tag; sending a second message with the first tag, the second message being used to request registration with a core network device; switching from an unregistered state to a registered state after sending the second message with the first tag; A tag state management method including:

2. the first message is further used to excite the inventoried tag. The method of claim 1.

3. After the step of sending a second message by the first tag, the method further comprises: receiving a third message by the first tag, the third message indicating that the first tag has successfully registered with the core network device; further comprising said step of switching from an unregistered state to a registered state after sending said second message by said first tag comprises: switching, by the first tag, from the unregistered state to the registered state after receiving the third message. Including, 3. The method according to claim 1 or 2.

4. After the step of sending a second message by the first tag, the method further comprises: sending a fourth message by the first tag, the fourth message being used to request that authentication be performed on the first tag; receiving a fifth message by the first tag, the fifth message indicating that the authentication for the first tag was successful; further comprising said step of switching from an unregistered state to a registered state after sending said second message by said first tag comprises: switching, by the first tag, from the unregistered state to the registered state after receiving the fifth message. Including, 3. The method according to claim 1 or 2.

5. After the step of sending a second message by the first tag, the method further comprises: receiving, by the first tag, a sixth message, the sixth message being used to request the first tag to perform authentication on an authentication server; sending a seventh message when the authentication on the authentication server is successful according to the first tag, the seventh message indicating that the authentication on the authentication server is successful; further comprising said step of switching from an unregistered state to a registered state after sending said second message by said first tag comprises: switching from the unregistered state to the registered state after sending the seventh message by the first tag. Including, 3. The method according to claim 1 or 2.

6. The method comprises: starting a first timer by the first tag; switching, by the first tag, from the registered state to the unregistered state when the first timer expires; further comprising: The method according to any one of claims 1 to 5.

7. The method comprises: resetting, by the first tag in the registered state, the first timer based on messages between the first tag and the core network device. further comprising: The method of claim 6.

8. The method comprises: receiving an eighth message by the first tag in the registered state, the eighth message indicating to inventory a next tag; switching, by the first tag, from the registered state to the unregistered state based on the eighth message; further comprising: The method according to any one of claims 1 to 5.

9. receiving, by a core network device, a first request message used to request inventorying of inventoried tags; sending a first message by the core network device through an access network device to the inventoried tag, the first message being used to request that the inventoried tag be inventoried; receiving, by the core network device, a second message from a first tag in the inventoried tags, the second message being used to request registration with the core network device, the first tag being a passive tag or a semi-passive tag; switching, by the core network device, a state of the first tag stored in the core network device from an unregistered state to a registered state after receiving the second message; A tag state management method including:

10. After the second message is received, the method comprises: sending, by the core network device, a third message to the first tag, the third message indicating that the first tag has successfully registered with the core network device; further comprising the step of switching, by the core network device, a state of the first tag stored in the core network device from an unregistered state to a registered state after receiving the second message, switching, by the core network device after sending the third message, the state of the first tag stored in the core network device from the unregistered state to the registered state. Including, 10. The method of claim 9.

11. After the second message is received, the method comprises: receiving, by the core network device, a fourth message from the first tag, the fourth message being used to request performing authentication on the first tag; sending, by the core network device, a fifth message to the first tag, the fifth message indicating that the authentication for the first tag was successful; further comprising switching, by the core network device, a state of the first tag stored in the core network device from an unregistered state to a registered state after receiving the second message, switching, by the core network device after sending the fifth message, the state of the first tag stored in the core network device from the unregistered state to the registered state. Including, 10. The method of claim 9.

12. After the second message is received, the method comprises: sending a sixth message by the core network device to the first tag, the sixth message being used to request performing authentication on an authentication server; receiving, by the core network device, a seventh message from the first tag, the seventh message indicating that the authentication on the authentication server was successful; further comprising switching, by the core network device, a state of the first tag stored in the core network device from an unregistered state to a registered state after receiving the second message, switching, by the core network device after receiving the seventh message, the state of the first tag stored in the core network device from the unregistered state to the registered state. Including, 10. The method of claim 9.

13. The method comprises: starting a second timer when the state of the first tag is switched from the unregistered state to the registered state by the core network device; switching, by the core network device, the state of the first tag stored in the core network device from the registered state to the unregistered state when the second timer expires; further comprising: The method according to any one of claims 9 to 12.

14. The method comprises: resetting, by the core network device, the second timer based on a message between the first tag and the core network device; further comprising: The method of claim 13.

15. The method comprises: switching, by the core network device, the state of the first tag stored in the core network device from the registered state to the unregistered state when the inventory for the first tag is completed. further comprising: The method according to any one of claims 9 to 12.

16. The method comprises: sending, by the core network device, a ninth message to the access network device, the ninth message indicating that the inventory for the first tag is completed; further comprising: The method according to any one of claims 13 to 15.

17. The method comprises: assigning, by the core network device, a first identifier to the first tag after receiving the second message; sending, by the core network device, to the access network device, a correspondence between the first identifier and the first tag; further comprising: The method according to any one of claims 13 to 16.

18. The method comprises: receiving, by the core network device, a correspondence between a second identifier and the first tag from the access network device; further comprising: The method according to any one of claims 13 to 17.

19. The method comprises: Releasing, by the core network device, the correspondence between the first identifier and the first tag and / or the correspondence between the second identifier and the first tag when the state of the first tag is switched from the registered state to the deregistered state. further comprising:

19. The method of claim 17 or 18.

20. receiving, by the access network device, a second request message used to request inventorying of inventoried tags, the inventoried tags including the first tag; sending, by the access network device, a first message to the inventoried tag based on the second request message, the first message being used to request that the inventoried tag be inventoried; receiving, by the access network device, a second message from the first tag in the inventoried tags after the first tag accesses the access network device, the second message being used to request registration with a core network device; sending, by the access network device, the second message to the core network device; A tag state management method including:

21. the first message is further used to excite the inventoried tag.

21. The method of claim 20.

22. The method comprises: assigning, by the access network device, a second identifier to the first tag based on the second message, and sending, by the access network device, a correspondence between the second identifier and the first tag to the core network device; and / or receiving, by the access network device, a correspondence between a first identifier and the first tag from the core network device; further comprising:

22. The method of claim 20 or 21.

23. The method comprises: starting, by the access network device, a third timer; releasing, by the access network device, the correspondence between the first identifier and the first tag and / or the correspondence between the second identifier and the first tag when the third timer expires; further comprising:

23. The method of claim 22.

24. The method comprises: resetting, by the access network device, the third timer based on a message between the first tag and the core network device; further comprising:

24. The method of claim 23.

25. The method comprises: receiving, by the access network device, a ninth message from the core network device, the ninth message indicating that the inventory for the first tag has finished; releasing, by the access network device based on the ninth message, the correspondence between the first identifier and the first tag and / or the correspondence between the second identifier and the first tag; further comprising:

23. The method of claim 22.

26. The method comprises: sending, by the access network device, an eighth message to the first tag, the eighth message indicating to inventory a next tag; further comprising: The method according to any one of claims 23 to 25.

27. receiving, by a core network device, a first request message used to request inventorying of inventoried tags; sending a second request message to the access network device, the second request message being used by the core network device to request that the access network device inventory the inventoried tag; sending, by the access network device, a first message to the inventoried tag based on the second request message, the first message being used to request that the inventoried tag be inventoried; receiving, by the access network device, a second message from a first tag among the inventoried tags after the first tag accesses the access network device, the second message being used to request registration with the core network device; sending, by the access network device, the second message to the core network device; switching, by the core network device, a state of the first tag stored in the core network device from an unregistered state to a registered state after receiving the second message; A tag state management method including:

28. After the second message is received, the method comprises: sending, by the core network device, a third message to the first tag through the access network device, the third message indicating that the first tag has successfully registered with the core network device; further comprising the step of switching, by the core network device, a state of the first tag stored in the core network device from an unregistered state to a registered state after receiving the second message, switching, by the core network device after sending the third message, the state of the first tag stored in the core network device from the unregistered state to the registered state. Including, 28. The method of claim 27.

29. After the second message is received, the method comprises: receiving, by the core network device, a fourth message from the first tag, the fourth message being used to request performing authentication on the first tag; sending, by the core network device, a fifth message to the first tag, the fifth message indicating that the authentication for the first tag was successful; further comprising the step of switching, by the core network device, a state of the first tag stored in the core network device from an unregistered state to a registered state after receiving the second message, switching, by the core network device after sending the fifth message, the state of the first tag stored in the core network device from the unregistered state to the registered state. Including, 28. The method of claim 27.

30. After the second message is received, the method comprises: sending a sixth message by the core network device to the first tag, the sixth message being used to request performing authentication on an authentication server; receiving, by the core network device, a seventh message from the first tag, the seventh message indicating that the authentication on the authentication server was successful; further comprising switching, by the core network device, a state of the first tag stored in the core network device from an unregistered state to a registered state after receiving the second message, switching, by the core network device after receiving the seventh message, the state of the first tag stored in the core network device from the unregistered state to the registered state. Including, 28. The method of claim 27.

31. The method comprises: switching, by the core network device, the state of the first tag stored in the core network device from the registered state to the unregistered state when the inventory for the first tag is completed. further comprising: The method according to any one of claims 27 to 30.

32. The following devices: A first tag configured to perform the method according to any one of claims 1 to 8; A core network device configured to implement the method according to any one of claims 9 to 19, or An access network device configured to implement the method of any one of claims 20 to 26.

1. A communication system comprising:

33. A communications device, comprising a processor configured to execute a computer program stored in a memory to enable the device to perform a method according to any one of claims 1 to 8, a method according to any one of claims 9 to 19, or a method according to any one of claims 20 to 26.

34. the device further comprising the memory; 34. The apparatus of claim 33.

35. A computer-readable storage medium that stores a computer program, and when the computer program is executed on a computer, enables the computer to perform the method according to any one of claims 1 to 8, the method according to any one of claims 9 to 19, or the method according to any one of claims 20 to 26.

36. 27. A computer program product comprising instructions for performing the method of any one of claims 1 to 8, instructions for performing the method of any one of claims 9 to 19, or instructions for performing the method of any one of claims 20 to 26.

37. A chip comprising a processor and a communication interface, wherein the processor reads instructions stored in a memory through the communication interface to perform the method of any one of claims 1 to 31.

Images