Communication method and apparatus

Abstract

This application provides a communication method and apparatus. The method includes: a first core network device receiving first information from an operation requester, the first information indicating at least one of the following: an area where a first operation is performed, and a target tag to which the first operation is performed, the first information being used to identify a first target reader; the first core network device sending second information to the first target reader based on the first information, the second information being used to instruct the first target reader to perform the first operation. The communication method and apparatus provided in this application manage readers and tags in a passive Internet of Things (IoT) through a core network device, reducing the operational costs for enterprises maintaining two networks simultaneously and reducing network resource consumption.

Description

Technical Field

[0001] This application relates to the field of communication technology, and more specifically, to a communication method and apparatus. Background Technology

[0002] Currently, enterprises with needs for warehousing, transportation management, and fixed asset management commonly use passive Internet of Things (IoT), consisting of tags, readers, and operation requesters, to manage goods or assets by attaching or embedding tags. In this IoT, the operation requester needs to store reader information and manage the reader and tags through signaling interaction, resulting in significant network resource consumption. Furthermore, these enterprises often need to deploy 3GPP (3rd Generation Partnership Project) networks, and supporting both networks simultaneously incurs high maintenance costs. Therefore, reducing enterprise maintenance costs and minimizing network resource consumption has become a pressing issue. Summary of the Invention

[0003] This application provides a communication method and apparatus that reduces network resource consumption by lowering enterprise operation and maintenance costs.

[0004] In a first aspect, a communication method is provided, comprising: a first core network device receiving first information from an operation requester, the first information indicating at least one of the following: an area where a first operation is performed, a target tag to which the first operation is performed, the first information being used to identify a first target reader; the first core network device sending second information to the first target reader based on the first information, the second information being used to instruct the first target reader to perform the first operation.

[0005] In other words, the communication method provided in the first aspect can also be:

[0006] The first core network device receives first information from the operation requester, which indicates: the area where the first operation is to be performed and / or the target label to which the first operation is to be performed;

[0007] The first core network device determines the first target reader based on the first information;

[0008] The first core network device sends second information to the first target reader based on the first information, and the second information is used to instruct the first target reader to perform the first operation.

[0009] In other words, the communication method provided in the first aspect can also be:

[0010] The first core network device receives first information from the operation requester, the first information indicating at least one of the following: the area where the first operation is performed, and the target tag to which the first operation is performed; the first core network device determines a first target reader based on the first information; the first core network device sends second information to the first target reader, the second information being used to instruct the first target reader to perform the first operation.

[0011] It should be understood that in the above scheme, the first core network device can directly send the second information to the first target reader, or it can indirectly send the second information to the first target reader through one or more devices. For example, if the first core network device is a network exposure function (NEF), the NEF can send the second information to the first target reader through a mobility management device.

[0012] The above solution manages readers and tags in the passive Internet of Things through core network equipment, reducing the operation and maintenance costs of enterprises maintaining two networks simultaneously and reducing network resource consumption.

[0013] In conjunction with the first aspect, in some implementations of the first aspect, the second information may be an N2 message or a non-access stratum (NAS) message.

[0014] In conjunction with the first aspect, in some implementations of the first aspect, the second information can also be the first information.

[0015] In conjunction with the first aspect, in some implementations of the first aspect, the second information may include a load.

[0016] It should be understood that the payload here can be application-layer data or application-layer information sent to the tag, or other tag-related information. It should also be understood that the tag here can include, but is not limited to, the target tag to which the first operation is performed; that is, the tag here can also include tags other than the target tag.

[0017] In conjunction with the first aspect, in some implementations of the first aspect, the first information indicates the region where the first operation is performed.

[0018] The method further includes: the first core network device determining the first target reader based on the area where the first operation is performed and third information, wherein the third information includes one or more of the following: reader identification information, reader location information, reader group identification information, reader address information, or reader port information.

[0019] or,

[0020] The first core network device sends the area of ​​the first operation to the second core network device; the first core network device receives the identifier of the first target reader from the second core network device, the identifier of the first target reader is determined by the second core network device based on the area of ​​the first operation and third information, the third information including one or more of the following: reader identification information, reader location information, reader group identification information, reader address information or reader port information.

[0021] In conjunction with the first aspect, in some implementations of the first aspect, the identifier of the first target reader includes one or more of the following information: reader identifier information, reader group identifier information, reader address information, or reader port information.

[0022] In conjunction with the first aspect, in some implementations of the first aspect, the third information is pre-configured, or the third information is received from a control plane device, which includes any one of the following devices: mobility management device, session management device, policy control device, unified data management device, network open functions, and user database.

[0023] It should be noted that in the above scheme, if the first core network device and the control plane device are of the same type, the first core network device receiving third information from the control plane device can be understood as the first core network device receiving third information from a control plane device of the same type other than the first core network device, or it can be understood as the first core network device generating the third information. For example, when both the first core network device and the control plane device are mobility management devices, the first core network device receiving third information from the control plane device can be understood as the first mobility management device (first core network device) receiving third information from a mobility management device other than the first mobility management device, or it can be understood as the first mobility management device generating the third information.

[0024] In conjunction with the first aspect, in some implementations of the first aspect, the first core network device determines the first target reader based on the first information, including: the first core network device determines the first target reader based on the first information and a first correspondence relationship, wherein the first correspondence relationship includes one or more of the following: a correspondence relationship between the first target reader and the region where the first operation is performed, and a correspondence relationship between the first target reader and the target tag to which the first operation is performed.

[0025] It should be noted that "acquiring" information in this application may include determining, generating, or receiving the information. Similarly, "acquiring" a correspondence in this application may include determining, generating, or receiving the relationship.

[0026] In conjunction with the first aspect, in certain implementations of the first aspect, the first information indicates the area where the first operation is performed, and the first core network device determines the first target reader based on the first information, including: the first core network device determines the first target reader based on the area where the first operation is performed and third information, wherein the third information includes one or more of the following: reader identification information, reader location information, reader group identification information, reader address information, or reader port information.

[0027] In conjunction with the first aspect, in some implementations of the first aspect, the first core network device is a user plane device, and the method further includes: the first core network device receiving the third information from a control plane device, the control plane device including any one of the following devices: mobility management device, session management device, policy control device, unified data management device.

[0028] In conjunction with the first aspect, in some implementations of the first aspect, when the control plane device is a mobility management device, the first core network device receives third information from the session management device, the third information being received by the session management device from the mobility management device; or, the first core network device receives the third information from the mobility management device through a dedicated interface or a service-oriented interface.

[0029] It should be understood that the control plane device can obtain the third information through the reader's registration process or based on the reader's subscription information or configuration information.

[0030] In conjunction with the first aspect, in some implementations of the first aspect, when the control plane device is a session management device, the first core network device receives the third information from the session management device through a session management process, or the first core network device receives the third information from the session management device through a dedicated interface or a service-oriented interface, wherein the session management process includes a session establishment process and a session modification process.

[0031] It should be understood that the session management device obtains third-party information through the reader's session management process or based on the reader's subscription information or configuration information.

[0032] In conjunction with the first aspect, in some implementations of the first aspect, when the control plane device is a policy control device, the first core network device receives third information from the session management device, which is received by the session management device from the policy control device; or, the first core network device receives third information from the policy control device through a dedicated interface or a service-oriented interface.

[0033] It should be understood that the policy control device obtains the third information through the reader's registration process or session management process, or obtains the third information based on the reader's subscription information or configuration information; wherein, the session management process includes the session establishment process and the session modification process.

[0034] In conjunction with the first aspect, in some implementations of the first aspect, when the control plane device is a unified data management device, the first core network device receives third information from the session management device, the third information being received by the session management device from the unified data management device; or, the first core network device receives third information from the unified data management device through a dedicated interface or a service-oriented interface.

[0035] It should be understood that the unified data management device obtains the third information through the reader's registration process or session management process, or obtains the third information based on the reader's subscription information or configuration information; wherein, the session management process includes the session establishment process and the session modification process.

[0036] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the first core network device acquiring reader identification information of one or more readers; wherein, the first core network device determining the first target reader based on the region where the first operation is performed and the third information includes: the first core network device determining the first target reader from the one or more readers based on the region where the first operation is performed and the reader identification information of the one or more readers.

[0037] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the first core network device acquiring reader address information or reader port information of one or more readers; wherein, the first core network device determining the first target reader based on the region where the first operation is performed and the third information includes: the first core network device determining the first target reader from the one or more readers based on the region where the first operation is performed and the reader address information or reader port information of the one or more readers.

[0038] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the first core network device acquiring reader identification information and reader address information of one or more readers; wherein, the first core network device determining the first target reader based on the region where the first operation is performed and the third information includes: the first core network device determining the first target reader from the one or more readers based on the region where the first operation is performed and the reader identification information and reader address information of the one or more readers.

[0039] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the first core network device acquiring reader identification information and reader port information of one or more readers; wherein, the first core network device determining the first target reader based on the region where the first operation is performed and the third information includes: the first core network device determining the first target reader from the one or more readers based on the region where the first operation is performed and the reader identification information and reader port information of the one or more readers.

[0040] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the first core network device acquiring location information of one or more readers; wherein, the first core network device determining the first target reader based on the region where the first operation is performed and third information includes: the first core network device determining the first target reader from the one or more readers based on the region where the first operation is performed and the location information of the one or more readers.

[0041] The above scheme obtains the location information of one or more readers, thereby enabling the determination of the target reader based on the area information sent by the operation requester.

[0042] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the first core network device acquiring reader identification information and reader location information of one or more readers; wherein, the first core network device determining the first target reader based on the region where the first operation is performed and the third information includes: the first core network device determining the first target reader from the one or more readers based on the region where the first operation is performed and the reader identification information and reader location information of the one or more readers.

[0043] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the first core network device acquiring reader group identification information and reader location information of one or more readers; wherein, the first core network device determining the first target reader based on the region where the first operation is performed and the third information includes: the first core network device determining the first target reader from the one or more readers based on the region where the first operation is performed and the reader group identification information and reader location information of the one or more readers.

[0044] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the first core network device acquiring reader identification information, reader group identification information, and reader location information of one or more readers; wherein, the first core network device determining the first target reader based on the region where the first operation is performed and the third information includes: the first core network device determining the first target reader from the one or more readers based on the region where the first operation is performed and the reader identification information, reader group identification information, and reader location information of the one or more readers.

[0045] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the first core network device acquiring reader identification information, reader location information, and reader port information of one or more readers; wherein, the first core network device determining the first target reader based on the region where the first operation is performed and the third information includes: the first core network device determining the first target reader from the one or more readers based on the region where the first operation is performed and the reader identification information, reader location information, and reader port information of the one or more readers.

[0046] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the first core network device acquiring reader identification information, reader location information, and reader address information of one or more readers; wherein, the first core network device determining the first target reader based on the region where the first operation is performed and the third information includes: the first core network device determining the first target reader from the one or more readers based on the region where the first operation is performed and the reader identification information, reader location information, and reader address information of the one or more readers.

[0047] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the first core network device acquiring reader group identification information, reader location information, and reader address information of one or more readers; wherein, the first core network device determining the first target reader based on the region where the first operation is performed and the third information includes: the first core network device determining the first target reader from the one or more readers based on the region where the first operation is performed and the reader group identification information, reader location information, and reader address information of the one or more readers.

[0048] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the first core network device acquiring reader identification information, reader group identification information, reader location information, and reader address information of one or more readers; wherein, the first core network device determining the first target reader based on the region where the first operation is performed and the third information includes: the first core network device determining the first target reader from the one or more readers based on the region where the first operation is performed and the reader identification information, reader group identification information, reader location information, and reader address information of the one or more readers.

[0049] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the first core network device acquiring location information, reader address information, and reader port information of one or more readers; wherein, the first core network device determining the first target reader based on the region where the first operation is performed and the third information includes: the first core network device determining the first target reader from the one or more readers based on the region where the first operation is performed and the location information, reader address information, and reader port information of the one or more readers.

[0050] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the first core network device acquiring reader identification information, reader location information, reader address information, and reader port information of one or more readers; wherein, the first core network device determining the first target reader based on the region where the first operation is performed and the third information includes: the first core network device determining the first target reader from the one or more readers based on the region where the first operation is performed and the reader identification information, reader location information, reader address information, and reader port information of the one or more readers.

[0051] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the first core network device acquiring reader group identification information, reader location information, reader address information, and reader port information of one or more readers; wherein, the first core network device determining the first target reader based on the region where the first operation is performed and the third information includes: the first core network device determining the first target reader from the one or more readers based on the region where the first operation is performed and the reader group identification information, reader location information, reader address information, and reader port information of the one or more readers.

[0052] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the first core network device acquiring reader identification information, reader group identification information, reader location information, reader address information, and reader port information of one or more readers; wherein, the first core network device determining the first target reader based on the region where the first operation is performed and the third information includes: the first core network device determining the first target reader from the one or more readers based on the region where the first operation is performed and the reader identification information, reader group identification information, reader location information, reader address information, and reader port information of the one or more readers.

[0053] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the first core network device sending reader location information of the one or more readers to an Internet of Things server.

[0054] The above scheme sends the reader's location information to the IoT server through the core network equipment, enabling the IoT server to obtain the reader's location information and manage the reader based on the reader's location information.

[0055] In conjunction with the first aspect, in some implementations of the first aspect, the first core network device is a mobility management device, and the first core network device obtains the location information of one or more readers, including: the first core network device initiates a positioning process, which is used to obtain the location information of the one or more readers.

[0056] In conjunction with the first aspect, in some implementations of the first aspect, the first core network device initiates a positioning process, including: the first core network device periodically initiates the positioning process.

[0057] The above scheme, by periodically acquiring the reader's location information, allows the core network equipment to obtain the latest location information of the reader, thereby further improving the success rate of determining the target reader based on the instructions sent by the operation requester.

[0058] In conjunction with the first aspect, in some implementations of the first aspect, the first core network device is a user plane device, and the first core network device obtains the location information of one or more readers, including: the first core network device receives the location information of the one or more readers from the mobility management device.

[0059] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the first core network device sending the third information to the Internet of Things server.

[0060] The above scheme sends third-party information to the IoT server through the core network equipment, enabling the IoT server to manage the reader based on the third-party information.

[0061] In conjunction with the first aspect, in some implementations of the first aspect, the first information indicates the target label to which the first operation is performed.

[0062] The method further includes: the first core network device determining the first target reader based on the target tag to which the first operation is performed and a first correspondence, wherein the first correspondence includes the correspondence between the target tag and the reader information of the first target reader.

[0063] or,

[0064] The first core network device sends the target tag of the first operation to the second core network device; the first core network device receives the identifier of the first target reader from the second core network device, the identifier of the first target reader is determined by the second core network device according to the target tag of the first operation and a first correspondence relationship, the first correspondence relationship including the correspondence relationship between the target tag and the reader information of the first target reader.

[0065] In conjunction with the first aspect, in some implementations of the first aspect, the identifier of the first target reader includes one or more of the following information: reader identifier information, reader group identifier information, reader address information, or reader port information.

[0066] In conjunction with the first aspect, in some implementations of the first aspect, the first information indicates the target tag to which the first operation is performed, and the first core network device determines the first target reader based on the first information, including: the first core network device determines the first target reader based on the target tag to which the first operation is performed and a first correspondence, the first correspondence including the correspondence between the target tag and the reader information of the first target reader.

[0067] The above scheme allows network or core network devices to determine the target reader based on the correspondence between the target tag and the reader by obtaining the correspondence between the tag and the reader.

[0068] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the first core network device determining that the first target reader has failed to execute the first operation; the first core network device sending the second information to the second target reader, the second information being used to instruct the second target reader to execute the first operation.

[0069] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the first core network device receiving fourth information from the first target reader, the fourth information indicating that the first target reader failed to execute the first operation; wherein, the first core network device determining that the first target reader failed to execute the first operation includes: the first core network device determining that the first target reader failed to execute the first operation based on the fourth information.

[0070] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the first core network device not receiving information from the first target reader; wherein, the first core network device determining that the first target reader has not successfully performed the first operation includes: the first core network device not receiving information from the first target reader, and determining that the first target reader has not successfully performed the first operation.

[0071] It should be understood that if the first core network does not receive information from the first target reader within the first time period, it can be determined that the first target reader has failed to execute the first operation.

[0072] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the first core network device receiving fourth information from the first target reader, the fourth information indicating that the first target reader failed to perform the first operation; the first core network device sending the second information to the second target reader, the second information being used to instruct the second target reader to perform the first operation.

[0073] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the first core network device receiving fifth information from the second target reader, the fifth information indicating that the second target reader has successfully performed the first operation; the first core network device updating the first correspondence based on the fifth information, so that the first correspondence includes the correspondence between the target tag to which the first operation was performed and the reader information of the second target reader.

[0074] In conjunction with the first aspect, in certain implementations of the first aspect, the first target reader or the second target reader comprises one or more readers.

[0075] In conjunction with the first aspect, in some implementations of the first aspect, the second target reader includes one or more readers that belong to a first and second reader group; or the multiple readers have the same location information.

[0076] In conjunction with the first aspect, in some implementations of the first aspect, the first target reader includes one or more readers, the plurality of readers belonging to a first reader group; or the location information of the plurality of readers is the same.

[0077] In conjunction with the first aspect, in some implementations of the first aspect, the reader information includes one or more of the following: reader identification information, reader location information, reader address information or reader port information, and reader group identification information.

[0078] The above scheme, by grouping readers, for example, grouping readers with similar geographical locations together, can identify some or all readers in the same group as target readers when determining the target reader. When the reader indicated by the first correspondence fails to perform the first operation on the target tag, the scheme can attempt to perform the first operation on the target tag in the adjacent area of ​​the reader that previously performed the first operation on the target tag. This increases the probability of successfully performing the first operation on the target tag or improves the efficiency of successfully performing the first operation on the target tag without consuming too much network resources.

[0079] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the first correspondence is pre-configured, or the method further includes: the first core network device acquiring the first correspondence.

[0080] In conjunction with the first aspect, in some implementations of the first aspect, when the first core network device is a user plane device, the acquisition of the first correspondence by the first core network device includes: the first core network device receiving the first correspondence from the mobility management device.

[0081] In conjunction with the first aspect, in certain implementations of the first aspect, the first core network device obtains the first correspondence by: the first core network device sending sixth information to one or more readers to cause the one or more readers to perform a second operation on tags within the coverage area based on the sixth information; the first core network device receiving seventh information from the one or more readers, the seventh information being used to identify some or all tags within the coverage area, the some or all tags including the target tag, and the one or more readers including the first target reader; the first core network device obtaining the first correspondence based on the seventh information and the one or more readers; or, the first core network device sending second information to the one or more readers to cause the one or more readers to perform the first operation on the target tag based on the second information, the one or more readers including the first target reader; the first core network device receiving seventh information from the one or more readers, the seventh information indicating that the one or more readers successfully performed the first operation; and the first core network device obtaining the first correspondence based on the seventh information.

[0082] In conjunction with the first aspect, in certain implementations of the first aspect, the first core network device sends the sixth information to one or more readers, including: the first core network device periodically sends the sixth information to the one or more readers.

[0083] In conjunction with the first aspect, in some implementations of the first aspect, the first core network device sends a sixth message to one or more readers, including: the first core network device starts a timer; when the timer expires, the first core network device sends the sixth message to the one or more readers.

[0084] In conjunction with the first aspect, in some implementations of the first aspect, the first core network device starts a timer, including: the first core network device periodically starts the timer.

[0085] In conjunction with the first aspect, in some implementations of the first aspect, the sixth information also instructs the one or more readers to periodically perform the second operation on the tags within the coverage area.

[0086] In the above scheme, network or core network equipment can actively or periodically obtain the correspondence between tags and readers. Thus, when receiving instructions from the operation requester, it can efficiently determine the target reader based on the tag information, thereby performing tag operations in a shorter time or with less signaling overhead. Alternatively, by having the reader periodically inventory the tags and send the inventory results to the core network equipment, the core network equipment can periodically obtain the correspondence between tags and readers.

[0087] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the first core network device sending the first correspondence to the Internet of Things server.

[0088] The above scheme sends the first correspondence relationship to the IoT server through the core network equipment, so that the IoT server can manage the reader according to the first correspondence relationship.

[0089] In conjunction with the first aspect, in some implementations of the first aspect, the first operation includes: obtaining tag information, inventory operation, read operation, write operation, invalidation operation, sending load to the tag, and message interaction operation with the tag.

[0090] In conjunction with the first aspect, in some implementations of the first aspect, the location information of the reader includes one or more of the following: cell identifier, tracking area identifier, registration area information, network identifier, coordinate value information, and latitude and longitude information.

[0091] In a second aspect, a communication method is provided, comprising: a reader sending an eighth message, the eighth message being used to instruct the reader; the reader receiving a ninth message sent by a tag, the ninth message indicating that the tag is within the reader's service range; and the reader sending a tenth message to a first core network device, the tenth message indicating that the tag is within the reader's service range.

[0092] In conjunction with the second aspect, in some implementations of the second aspect, the reader sends the eighth information, including: the reader sending the eighth information to the tag during the first operation performed on the tag; or the reader sending the eighth information via broadcast.

[0093] The above scheme, based on the function of storing reader identifiers in tags, enables tags to know whether their location has changed or whether the reader serving the tag has changed through periodically sent messages by the reader, such as periodically sent broadcast messages. When a change occurs, the tag sends information to the network, thereby enabling the network to obtain or update the correspondence between the tag and the reader.

[0094] Thirdly, a communication method is provided, comprising: a tag receiving a first reader identifier from a first reader; the tag storing the first reader identifier; and the tag sending tag information to the first reader, the tag information being used to identify the tag.

[0095] In conjunction with the third aspect, in some implementations of the third aspect, the method further includes: the tag receiving a second reader identifier; when the second reader identifier is different from the first reader identifier, the tag storing the second reader identifier, or the tag replacing the first reader identifier with the second reader identifier.

[0096] In conjunction with the third aspect, in some implementations of the third aspect, the method further includes: the tag sending the tag information to the second reader.

[0097] The above scheme, based on the tag's ability to store reader identifiers, allows tags to know whether their location has changed or whether the reader serving the tag has changed by periodically sending messages, such as periodically broadcast messages. Furthermore, for tags whose location or the reader serving them has not changed, they do not need to send their own identification information, thus reducing signaling overhead.

[0098] Fourthly, a communication method is provided, characterized by comprising: an IoT server receiving third information from a core network device, the third information indicating one or more of the following: reader identification information, reader location information, reader group identification information, reader address information, reader port information, area information, and tag-reader correspondence, wherein the area information includes the area where the first operation is performed. The IoT server may also send the third information to an operation requester, enabling the operation requester to determine the target reader for performing the first operation based on the third information.

[0099] The above scheme involves the core network equipment sending third-party information to the IoT server, enabling the IoT server to manage the readers based on this information. Simultaneously, the IoT server can send this third-party information to the operation requester, allowing the requester to identify the target reader when requesting the network to perform tag operations, thereby reducing the signaling consumed by the network in searching for or identifying the target reader.

[0100] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the IoT server can determine the target reader to perform the first operation based on the third information. After determining the first target reader to perform the first operation, the IoT server can send second information to the first target reader, which instructs the first target reader to perform the first operation.

[0101] Fifthly, a communication device is provided, comprising: a transceiver module for receiving first information from an operation requester, the first information indicating at least one of the following: an area for performing a first operation, and a target tag for performing the first operation; a processing module for determining a first target reader based on the first information; the transceiver module is further configured to send second information to the first target reader, the second information being used to instruct the first target reader to perform the first operation.

[0102] In other words, the communication device provided in the fifth aspect could also be:

[0103] The transceiver module is configured to receive first information from the operation requester, the first information indicating: the area where the first operation is performed and / or the target tag to which the first operation is performed; the processing module is configured to determine a first target reader based on the first information; the transceiver module is further configured to send second information to the first target reader, the second information being used to instruct the first target reader to perform the first operation.

[0104] In other words, the communication device provided in the fifth aspect could also be:

[0105] The transceiver module is configured to receive first information from the operation requester, the first information indicating at least one of the following: the area where the first operation is performed, and the target tag to which the first operation is performed, the first information being used to determine the first target reader;

[0106] The transceiver module is also used to send second information to the first target reader based on the first information, the second information being used to instruct the first target reader to perform the first operation.

[0107] The above solution manages readers and tags in the passive Internet of Things through core network equipment, reducing the operation and maintenance costs of enterprises maintaining two networks simultaneously and reducing network resource consumption.

[0108] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the first information indicates the region where the first operation is performed.

[0109] The device further includes a processing module, which is configured to determine the first target reader based on the area where the first operation is performed and third information, wherein the third information includes one or more of the following: reader identification information, reader location information, reader group identification information, reader address information, or reader port information.

[0110] or,

[0111] The transceiver module is also used to send the area of ​​the first operation to the second core network device; the transceiver module is also used to receive the identifier of the first target reader from the second core network device, the identifier of the first target reader is determined by the second core network device based on the area of ​​the first operation and third information, the third information including one or more of the following: reader identification information, reader location information, reader group identification information, reader address information or reader port information.

[0112] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the identifier of the first target reader includes one or more of the following information: reader identifier information, reader group identifier information, reader address information, or reader port information. In conjunction with the fifth aspect, in some implementations of the fifth aspect, the third information is pre-configured, or the third information is received from a control plane device, which includes any of the following devices: a mobility management device, a session management device, a policy control device, a unified data management device, or a user database.

[0113] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the processing module is specifically used to determine the first target reader based on the first information and the first correspondence, wherein the first correspondence includes one or more of the following: the correspondence between the first target reader and the region performing the first operation, and the correspondence between the first target reader and the target tag to which the first operation is performed.

[0114] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the processing module is further configured to determine the first target reader based on the region where the first operation is performed and the third information, wherein the third information includes one or more of the following: reader identification information, reader location information, reader group identification information, reader address information, or reader port information.

[0115] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the device further includes an acquisition module for acquiring reader identification information of one or more readers; and a processing module specifically for determining the first target reader from the one or more readers based on the region where the first operation is performed and the reader identification information of the one or more readers.

[0116] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the acquisition module is further configured to acquire reader address information or reader port information of one or more readers; the processing module is specifically configured to determine the first target reader from the one or more readers based on the region where the first operation is performed and the reader address information or reader port information of the one or more readers.

[0117] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the acquisition module is further configured to acquire reader identification information and reader address information of one or more readers; the processing module is specifically configured to determine the first target reader from the one or more readers based on the region where the first operation is performed and the reader identification information and reader address information of the one or more readers.

[0118] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the acquisition module is further configured to acquire reader identification information and reader port information of one or more readers; the processing module is specifically configured to determine the first target reader from the one or more readers based on the region where the first operation is performed and the reader identification information and reader port information of the one or more readers.

[0119] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the acquisition module is further configured to acquire the location information of one or more readers; the processing module is specifically configured to determine the first target reader from the one or more readers based on the area where the first operation is performed and the location information of the one or more readers.

[0120] The above scheme obtains the location information of one or more readers, thereby enabling the determination of the target reader based on the area information sent by the operation requester.

[0121] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the acquisition module is further configured to acquire reader identification information and reader location information of one or more readers; the processing module is specifically configured to determine the first target reader from the one or more readers based on the region where the first operation is performed and the reader identification information and reader location information of the one or more readers.

[0122] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the acquisition module is further configured to acquire reader group identification information and reader location information of one or more readers; the processing module is specifically configured to determine the first target reader from the one or more readers based on the region where the first operation is performed and the reader group identification information and reader location information of the one or more readers.

[0123] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the acquisition module is further configured to acquire reader identification information, reader group identification information, and reader location information of one or more readers; the processing module is specifically configured to determine the first target reader from the one or more readers based on the region where the first operation is performed and the reader identification information, reader group identification information, and reader location information of the one or more readers.

[0124] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the acquisition module is further configured to acquire reader identification information, reader location information, and reader port information of one or more readers; the processing module is specifically configured to determine the first target reader from the one or more readers based on the region where the first operation is performed and the reader identification information, reader location information, and reader port information of the one or more readers.

[0125] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the acquisition module is further configured to acquire reader identification information, reader location information, and reader address information of one or more readers; the processing module is specifically configured to determine the first target reader from the one or more readers based on the region where the first operation is performed and the reader identification information, reader location information, and reader address information of the one or more readers.

[0126] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the acquisition module is further configured to acquire reader group identification information, reader location information, and reader address information of one or more readers; the processing module is specifically configured to determine the first target reader from the one or more readers based on the region where the first operation is performed and the reader group identification information, reader location information, and reader address information of the one or more readers.

[0127] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the acquisition module is further configured to acquire reader identification information, reader group identification information, reader location information, and reader address information of one or more readers; the processing module is specifically configured to determine the first target reader from the one or more readers based on the region where the first operation is performed and the reader identification information, reader group identification information, reader location information, and reader address information of the one or more readers.

[0128] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the method further includes: the first core network device acquiring location information, reader address information, and reader port information of one or more readers; wherein, the first core network device determining the first target reader based on the region where the first operation is performed and the third information includes: the first core network device determining the first target reader from the one or more readers based on the region where the first operation is performed and the location information, reader address information, and reader port information of the one or more readers.

[0129] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the method further includes: the first core network device acquiring reader identification information, reader location information, reader address information, and reader port information of one or more readers; wherein, the first core network device determining the first target reader based on the region where the first operation is performed and the third information includes: the first core network device determining the first target reader from the one or more readers based on the region where the first operation is performed and the reader identification information, reader location information, reader address information, and reader port information of the one or more readers.

[0130] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the method further includes: the first core network device acquiring reader group identification information, reader location information, reader address information, and reader port information of one or more readers; wherein, the first core network device determining the first target reader based on the region where the first operation is performed and the third information includes: the first core network device determining the first target reader from the one or more readers based on the region where the first operation is performed and the reader group identification information, reader location information, reader address information, and reader port information of the one or more readers.

[0131] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the method further includes: the first core network device acquiring reader identification information, reader group identification information, reader location information, reader address information, and reader port information of one or more readers; wherein, the first core network device determining the first target reader based on the region where the first operation is performed and the third information includes: the first core network device determining the first target reader from the one or more readers based on the region where the first operation is performed and the reader identification information, reader group identification information, reader location information, reader address information, and reader port information of the one or more readers.

[0132] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the first information indicates the area where the first operation is performed, and the device further includes an acquisition module for acquiring location information of one or more readers; wherein, the processing module is specifically used to determine the first target reader from the one or more readers based on the area where the first operation is performed and the location information of the one or more readers.

[0133] The above scheme obtains the location information of one or more readers, thereby enabling the determination of the target reader based on the area information sent by the operation requester.

[0134] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the transceiver module is also used to send the location information of the one or more readers to the Internet of Things server.

[0135] The above scheme sends the reader's location information to the IoT server through the core network equipment, enabling the IoT server to obtain the reader's location information and manage the reader based on the reader's location information.

[0136] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the device is a mobility management device, and the acquisition module is specifically used to initiate a positioning process to acquire the location information of the one or more readers.

[0137] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the acquisition module is specifically used to periodically initiate the positioning process.

[0138] The above scheme, by periodically acquiring the reader's location information, allows the core network equipment to obtain the latest location information of the reader, thereby further improving the success rate of determining the target reader based on the instructions sent by the operation requester.

[0139] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the device is a user plane device, and the transceiver module is specifically used to receive location information from the one or more readers of the mobility management device.

[0140] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the device is a user plane device, and the transceiver module is also used to receive the third information from the control plane device, which includes any one of the following devices: a mobility management device, a session management device, a policy control device, and a unified data management device.

[0141] In conjunction with the fifth aspect, in some implementations of the fifth aspect, when the control plane device is a mobility management device, the transceiver module is used to receive third information from the session management device, the third information being received by the session management device from the mobility management device; or, the transceiver module is used to receive third information from the mobility management device through a dedicated interface or a service-oriented interface.

[0142] It should be understood that the control plane device obtains the third information through the reader's registration process or based on the reader's subscription information or configuration information.

[0143] In conjunction with the fifth aspect, in some implementations of the fifth aspect, when the control plane device is a session management device, the transceiver module is used to receive the third information from the session management device through a session management process, or the transceiver module is used to receive the third information from the session management device through a dedicated interface or a service interface, wherein the session management process includes a session establishment process and a session modification process.

[0144] It should be understood that the session management device obtains third-party information through the reader's session management process or based on the reader's subscription information or configuration information.

[0145] In conjunction with the fifth aspect, in some implementations of the fifth aspect, when the control plane device is a policy control device, the transceiver module is used to receive third information from the session management device, the third information being received by the session management device from the policy control device; or, the transceiver module is used to receive third information from the policy control device through a dedicated interface or a service-oriented interface.

[0146] It should be understood that the policy control device obtains the third information through the reader's registration process or session management process, or obtains the third information based on the reader's subscription information or configuration information; wherein, the session management process includes the session establishment process and the session modification process.

[0147] In conjunction with the fifth aspect, in some implementations of the fifth aspect, when the control plane device is a unified data management device, the transceiver module is used to receive third information from the session management device, the third information being received by the session management device from the unified data management device; or, the transceiver module is used to receive third information from the unified data management device through a dedicated interface or a service-oriented interface.

[0148] It should be understood that the unified data management device obtains the third information through the reader's registration process or session management process, or obtains the third information based on the reader's subscription information or configuration information; wherein, the session management process includes the session establishment process and the session modification process.

[0149] The above scheme sends third-party information to the IoT server through the core network equipment, enabling the IoT server to manage the reader based on the third-party information.

[0150] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the transceiver module is also used to send the third information to the IoT server.

[0151] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the first information indicates the target label to which the first operation is performed.

[0152] The device further includes a processing module for determining the first target reader based on the target tag to which the first operation is performed and a first correspondence, wherein the first correspondence includes the correspondence between the target tag and the reader information of the first target reader.

[0153] or,

[0154] The transceiver module is also configured to send the target tag of the first operation to the second core network device; the transceiver module is also configured to receive the identifier of the first target reader from the second core network device, the identifier of the first target reader being determined by the second core network device based on the target tag of the first operation and a first correspondence relationship, the first correspondence relationship including the correspondence relationship between the target tag and the reader information of the first target reader.

[0155] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the identifier of the first target reader includes one or more of the following information: reader identifier information, reader group identifier information, reader address information, or reader port information.

[0156] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the processing module is further configured to determine the first target reader based on the target tag to which the first operation is performed and the first correspondence, wherein the first correspondence includes the correspondence between the target tag and the reader information of the first target reader.

[0157] The above scheme allows network or core network devices to determine the target reader based on the correspondence between the target tag and the reader by obtaining the correspondence between the tag and the reader.

[0158] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the processing module is further configured to determine that the first target reader has failed to execute the first operation; the transceiver module is further configured to send the second information to the second target reader, the second information being used to instruct the second target reader to execute the first operation.

[0159] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the transceiver module is further configured to receive fourth information from the first target reader, the fourth information indicating that the first target reader failed to execute the first operation; the processing module is specifically configured to determine, based on the fourth information, that the first target reader did not successfully execute the first operation.

[0160] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the transceiver module does not receive information from the first target reader; wherein, the processing module is used to determine that the first target reader has not successfully executed the first operation, including: the first core network device does not receive information from the first target reader, and determines that the first target reader has not successfully executed the first operation.

[0161] It should be understood that if the processing module does not receive information from the first target reader within the first time period, it can be determined that the first target reader has failed to execute the first operation.

[0162] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the transceiver module is further configured to receive fourth information from the first target reader, the fourth information indicating that the first target reader failed to perform the first operation; the transceiver module is further configured to send the second information to the second target reader, the second information being used to instruct the second target reader to perform the first operation.

[0163] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the transceiver module is further configured to receive fifth information from the second target reader, the fifth information indicating that the second target reader has successfully performed the first operation; the processing module is further configured to update the first correspondence based on the fifth information, so that the first correspondence includes the correspondence between the target tag to which the first operation was performed and the reader information of the second target reader.

[0164] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the first target reader or the second target reader includes one or more readers.

[0165] The above scheme, by grouping readers, for example, grouping readers with similar geographical locations together, can identify readers in the same group as target readers when determining target readers. When the reader indicated by the first correspondence fails to perform the first operation on the target tag, it can attempt to perform the first operation on the target tag in the adjacent area of ​​the reader that previously performed the first operation on the target tag. This increases the probability of successfully performing the first operation on the target tag or improves the efficiency of successfully performing the first operation on the target tag without consuming too much network resources.

[0166] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the second target reader includes one or more readers that belong to a first and second reader group; or the multiple readers have the same location information.

[0167] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the first target reader includes one or more readers, which belong to a first reader group; or the location information of the multiple readers is the same.

[0168] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the reader information includes one or more of the following: reader identification information, reader location information, reader address information or reader port information, and reader group identification information.

[0169] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the device further includes: the first correspondence is pre-configured.

[0170] Alternatively, the device may further include: an acquisition module for acquiring the first correspondence.

[0171] In conjunction with the fifth aspect, in some implementations of the fifth aspect, when the device is a user plane device, the acquisition module is specifically used to acquire the first correspondence, including: the first core network device receiving the first correspondence from the mobility management device.

[0172] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the transceiver module is further configured to send sixth information to one or more readers, so that the one or more readers perform the first operation on tags within the coverage area according to the sixth information; the transceiver module is further configured to receive seventh information from the one or more readers, the seventh information being used to identify some or all of the tags within the coverage area, the some or all of the tags including the target tag, and the one or more readers including the first target reader; the processing module is further configured to obtain the first correspondence relationship according to the seventh information and the one or more readers; or, the transceiver module is further configured to send second information to the one or more readers, the second information being used to instruct the one or more readers to perform the first operation, the one or more readers including the first target reader; the transceiver module is further configured to receive seventh information from the one or more readers, the seventh information indicating that the one or more readers have successfully performed the first operation; the processing module is further configured to obtain the first correspondence relationship according to the seventh information.

[0173] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the transceiver module is specifically used to periodically send the sixth information to the one or more readers.

[0174] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the processing module is also used to start a timer, and when the timer expires, the transceiver module is also used to send the sixth information to the one or more readers.

[0175] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the processing module is specifically used to periodically turn on the timer.

[0176] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the sixth information also instructs the one or more readers to periodically perform the second operation on the tags within the coverage area.

[0177] In the above scheme, network or core network equipment can actively or periodically obtain the correspondence between tags and readers. Thus, when receiving instructions from the operation requester, it can efficiently determine the target reader based on the tag information, thereby performing tag operations in a shorter time or with less signaling overhead. Alternatively, by having the reader periodically inventory the tags and send the inventory results to the core network equipment, the core network equipment can periodically obtain the correspondence between tags and readers.

[0178] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the device further includes: the transceiver module, which is also used to send the first correspondence to the Internet of Things server.

[0179] The above scheme sends the first correspondence relationship to the IoT server through the core network equipment, so that the IoT server can manage the reader according to the first correspondence relationship.

[0180] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the first operation includes: obtaining tag information, inventory operation, read operation, write operation, invalidation operation, sending load to the tag, and message interaction operation with the tag.

[0181] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the location information of the reader includes one or more of the following: cell identifier, tracking area identifier, registration area information, network identifier, coordinate value information, and latitude and longitude information.

[0182] In a sixth aspect, a communication device is provided, comprising: a transceiver module for transmitting eighth information, the eighth information being used to instruct the reader; the transceiver module is further configured to receive ninth information transmitted by the tag, the ninth information indicating that the tag is within the service range of the reader; the transceiver module is further configured to transmit tenth information to a first core network device, the tenth information indicating that the tag is within the service range of the reader.

[0183] In conjunction with the sixth aspect, in some implementations of the sixth aspect, the transceiver module is specifically used to send the eighth information to the tag during the first operation performed on the tag; or, the transceiver module is specifically used to send the eighth information via broadcast.

[0184] The above scheme, based on the function of storing reader identifiers in tags, enables tags to know whether their location has changed or whether the reader serving the tag has changed through periodically sent messages by the reader, such as periodically sent broadcast messages. When a change occurs, the tag sends information to the network, thereby enabling the network to obtain or update the correspondence between the tag and the reader.

[0185] In a seventh aspect, a communication device is provided, comprising: a transceiver module for receiving a first reader identifier from a first reader; a processing module for storing the first reader identifier; the transceiver module is further configured to send tag information to the first reader, the tag information being used to identify the tag.

[0186] In conjunction with the seventh aspect, in some implementations of the seventh aspect, the transceiver module is further configured to receive a second reader identifier; when the second reader identifier is different from the first reader identifier, the processing module is further configured to store the second reader identifier, or the processing module is further configured to replace the first reader identifier with the second reader identifier.

[0187] In conjunction with the seventh aspect, in some implementations of the seventh aspect, the transceiver module is also used to send the tag information to the second reader.

[0188] The above scheme, based on the tag's ability to store reader identifiers, allows tags to know whether their location has changed or whether the reader serving the tag has changed by periodically sending messages, such as periodically broadcast messages. Furthermore, for tags whose location or the reader serving them has not changed, they do not need to send their own identification information, thus reducing signaling overhead.

[0189] Eighthly, a communication device is provided, characterized in that it includes: a transceiver module, configured to receive third information from a core network device, the third information indicating one or more of the following: reader identifier, reader location information, reader address information, reader port information, area information, and a tag-reader correspondence, wherein the area information includes the area where a first operation is performed; the transceiver module is further configured to send the third information to an operation requester, so that the operation requester determines the target reader for performing the first operation based on the third information.

[0190] The above scheme involves the core network equipment sending third-party information to the IoT server, enabling the IoT server to manage the readers based on this information. Simultaneously, the IoT server can send this third-party information to the operation requester, allowing the requester to identify the target reader when requesting the network to perform tag operations, thereby reducing the signaling consumed by the network in searching for or identifying the target reader.

[0191] In conjunction with the eighth aspect, in some implementations of the eighth aspect, the processing module can also be used to determine the target reader for performing the first operation based on the third information. The transceiver module can also be used to send second information to the first target reader, the second information being used to instruct the first target reader to perform the first operation.

[0192] A ninth aspect provides a communication device, comprising: a processor and a memory; the memory for storing a computer program; and the processor for executing the computer program stored in the memory, such that the communication device performs the communication method described in any one of the first to fourth aspects.

[0193] In a tenth aspect, a computer-readable storage medium is provided, on which a computer program is stored, which, when executed on a computer, causes the computer to perform the communication method as described in any one of the first to fourth aspects.

[0194] Eleventhly, a computer program product containing instructions is provided, which, when run on a computer, causes the computer to perform the method in any one of the possible implementations of the first to fourth aspects described above.

[0195] In a twelfth aspect, a chip system is provided, characterized in that it includes: a processor for calling and running a computer program from a memory, causing a communication device on which the chip system is installed to perform a communication method as described in any one of the first to fourth aspects.

[0196] In a thirteenth aspect, a communication system is provided, comprising one or more of the aforementioned first core network device, first target reader, second target reader, and operation requester. Attached Figure Description

[0197] Figure 1 The 5G network architecture is shown.

[0198] Figure 2 This diagram illustrates an interactive approach for tag inventory management in a passive Internet of Things (IoT) environment.

[0199] Figure 3 A schematic interactive diagram of the UE registration process is shown.

[0200] Figure 4 A schematic interactive diagram of the PDU session establishment process is shown.

[0201] Figure 5 The diagram shows the architecture of a 3GPP network supporting P-IoT.

[0202] Figure 6 A schematic interactive diagram of a communication method 400 according to an embodiment of this application is shown.

[0203] Figure 7 A schematic interactive diagram of a communication method 500 according to an embodiment of this application is shown.

[0204] Figure 8A schematic interactive diagram of a communication method 600 according to an embodiment of this application is shown.

[0205] Figure 9 A schematic interactive diagram of a communication method 700 according to an embodiment of this application is shown.

[0206] Figure 10 A schematic interactive diagram of a communication method 800 according to an embodiment of this application is shown.

[0207] Figure 11 A schematic interactive diagram of a communication method 900 according to an embodiment of this application is shown.

[0208] Figure 12 A schematic interactive diagram of a communication method 1000 according to an embodiment of this application is shown.

[0209] Figure 13 A schematic interactive diagram of a communication method 1100 according to an embodiment of this application is shown.

[0210] Figure 14 This application provides a schematic block diagram of a communication device.

[0211] Figure 15 This is a schematic diagram of the communication device 20 provided in an embodiment of this application. Detailed Implementation

[0212] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0213] The technical solutions provided in this application can be applied to various communication systems, such as: Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication systems, 5th Generation (5G) systems, New Radio (NR) systems, or future 3GPP systems, etc.

[0214] Traditional communication systems typically support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communication but also, for example, device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), vehicle-to-everything (V2X) communication (also known as vehicle-to-everything communication), such as vehicle-to-vehicle (V2V) communication, vehicle-to-infrastructure (V2I) communication, vehicle-to-pedestrian (V2P) communication, and vehicle-to-network (V2N) communication.

[0215] Figure 1 This illustrates the current 5G network architecture. The following section combines... Figure 1 Each network element that may be involved in the embodiments of this application will be described separately.

[0216] 1. User equipment (UE): can also be called terminal equipment, terminal, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, wireless communication equipment, user agent, or user device. The UE can also be a cellular phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA), handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, in-vehicle device, wearable device, terminal device in a 5G network, or terminal device in a future evolved public land mobile network (PLMN) or non-terrestrial networks (NTN). It can also be an end device, logical entity, smart device, such as a mobile phone, smart terminal, or other terminal device; or a server, gateway, base station, controller, or other communication device; or an Internet of Things (IoT) device, such as tags, passive tags, active tags, semi-passive tags, semi-active tags, sensors, electricity meters, water meters, and other IoT devices. It can also be an unmanned aerial vehicle (UAV) with communication capabilities. When the terminal is a passive, semi-active, or semi-passive terminal or tag, it can acquire energy to receive or transmit data. Energy can be acquired through radio frequency, radio wave, solar energy, solar energy, wind energy, hydropower, thermal energy, kinetic energy, etc. This application does not limit the energy acquisition method for passive, semi-active, or semi-passive terminals. The embodiments of this application are not limited in this respect. It is understood that when the terminal is passive, it does not have its own power supply or rely on batteries or other power devices, but acquires energy from the environment for functions such as data sensing, transmission, and distributed computing. When the terminal is semi-active, it can have a built-in battery, but the battery's function is to power the internal circuitry and not to actively transmit signals. When the terminal is semi-passive, it can have a built-in capacitor; this capacitor can store the energy acquired by the terminal; for example, the terminal can acquire energy through solar energy and store it in the capacitor.

[0217] It should be noted that the tags involved in this application can be in the form of tags, or in any terminal form.

[0218] 2. An Access and Mobility Management Function (AMF) entity (also referred to as Access and Mobility Management Function, Access and Mobility Management Equipment, Access and Mobility Management Network Element, Access Management Equipment, or Mobility Management Equipment) is a type of core network equipment primarily used for mobility management and access management. It can implement functions other than session management within the Mobility Management Entity (MME) functionality, such as lawful interception, access authorization (or authentication), user equipment registration, mobility management, tracking area update procedures, reachability detection, selection of session management network elements, and mobility state transition management. For example, in 5G, the Access and Mobility Management Network Element can be an Access and Mobility Management Function (AMF) network element. In future communications, such as 6G, the Access and Mobility Management Network Element can still be an AMF network element, or it may have other names; this application does not limit this. When the Access and Mobility Management Network Element is an AMF network element, the AMF can provide Namf services.

[0219] 3. User plane function (UPF) network elements (also known as user plane equipment) are a type of core network equipment. This equipment is responsible for forwarding and receiving user data from user equipment. It can receive user data from the data network and transmit it to the user equipment through access network elements; the UPF network element can also receive user data from the user equipment through access network elements and forward it to the data network. The transmission resources and scheduling functions providing services to user equipment in the UPF network element are managed and controlled by the session management function network element.

[0220] 4. A session management network element (also known as a session management device) is a type of core network equipment. This device is responsible for session management of the user equipment (including session establishment, modification, and release), selection and reselection of user plane function network elements, allocation of Internet Protocol (IP) addresses for the user equipment, and Quality of Service (QoS) control. For example, in 5G, the session management network element can be a Session Management Function (SMF) network element. In future communication systems, such as 6G, the session management network element can still be an SMF network element, or it may have other names; this application does not limit this. When the session management network element is an SMF network element, the SMF can provide NSMF services.

[0221] 5. A network open element (also known as a network open device) is a type of core network equipment. This device enables 3GPP to securely provide network service capabilities to third-party AFs (e.g., service capability servers (SCS), application servers (AS), etc.). For example, in 5G, the network open element can be a network exposure function (NEF) element. In future communication systems, such as 6G, the network open element can still be a NEF element, or it may have other names; this application does not limit this. When the network open element is a NEF, the NEF can provide NEF services to other network function elements.

[0222] 6. Access Network (AN) (also known as access network equipment or access network element): Provides network access functionality for authorized users in a specific area and can use transmission tunnels of different quality according to the user's level and service requirements. Access networks can employ different access technologies. Currently, there are two types of wireless access technologies: 3GPP access technologies (such as the wireless access technologies used in 3G, 4G, or 5G systems and future 3GPP wireless access technologies) and non-3GPP access technologies. 3GPP access technologies refer to access technologies that conform to 3GPP standards and specifications. Access networks using 3GPP access technologies are called radio access networks (RAN). In 5G systems, access network equipment is called next-generation node base station (gNB). Non-3GPP access technologies refer to access technologies that do not conform to 3GPP standards and specifications, such as air interface technologies represented by access points (APs) in Wi-Fi.

[0223] An access network that uses wireless communication technology to implement access network functions can be called a radio access network (RAN). A RAN manages radio resources, provides access services to terminals, and facilitates the forwarding of control signals and user data between terminals and the core network.

[0224] The wireless access network can be, for example, a base station (NodeB), an evolved NodeB (eNB or eNodeB), a base station (gNB) in a 5G mobile communication system, a base station in a future mobile communication system, or an access point (AP) in a Wi-Fi system. It can also be a wireless controller in a cloud radio access network (CRAN) scenario. Alternatively, the access network device can be a relay station, access point, vehicle-mounted equipment, wearable devices, or network equipment in a future 5G network or a future evolved PLMN network. The embodiments of this application do not limit the specific technology or device form used in the wireless access network device.

[0225] 7. Authentication Server Function (AUSF) entity: mainly used for user authentication, etc.

[0226] 8. Unified Data Management (UDM) entity: Used to handle user identification, access authentication, registration, or mobility management, etc.

[0227] exist Figure 1 In the network architecture shown, interface N1 is the reference point between the terminal and the AMF entity; interface N2 is the reference point between the AN and the AMF entities; interface N3 is the reference point between the (R)AN and the user plane function (UPF) entity, used for transmitting user plane data, etc.; interface N4 is the reference point between the session management function (SMF) entity and the UPF entity, used for transmitting information such as tunnel identification information for N3 connection, data buffer indication information, and downlink data notification messages, etc.; interface N6 is the reference point between the UPF entity and the data network (DN), used for transmitting user plane data, etc.

[0228] It should be understood that the aforementioned functions can be network elements in hardware devices, software functions running on dedicated hardware, or virtualization functions instantiated on a platform (e.g., a cloud platform). These functions can be divided into one or more services; furthermore, services existing independently of network functions may also exist. In this application, instances of the aforementioned functions, instances of services included in the aforementioned functions, or instances of services existing independently of network functions can all be referred to as service instances.

[0229] It should also be understood that the above Figure 1The network architecture shown can be applied to the embodiments of this application. However, the network architecture applicable to the embodiments of this application is not limited to this. Any network architecture that can realize the functions of the above-mentioned network elements is applicable to the embodiments of this application.

[0230] It should also be understood that Figure 1 The AMF, SMF, UPF, network exposure function (NEF), AUSF, network function (NF) repository function (NRF), policy control function (PCF), and UDM entities shown can be understood as network elements in the core network used to implement different functions, such as network slices that can be combined as needed. These core network elements can be independent devices or integrated into the same device to implement different functions; this application does not limit this. It should be noted that the aforementioned "network element" can also be referred to as an entity, device, apparatus, or module, etc., and this application does not specifically limit this.

[0231] It should also be understood that the above naming is only for distinguishing different functions and does not mean that these network elements are independent physical devices. This application does not limit the specific form of the above network elements. For example, they can be integrated into the same physical device or they can be different physical devices. In actual deployment, network elements or devices can be co-located. For example, the access and mobility management network element can be co-located with the session management network element; the session management network element can be co-located with the user plane network element. When two network elements are co-located, the interaction between the two network elements provided in the embodiments of this application becomes the internal operation of the co-located network element or can be omitted. In addition, the above naming is only for the convenience of distinguishing different functions and should not constitute any limitation on this application. This application does not exclude the possibility of using other names in 5G networks and other future networks. For example, in 6G networks, some or all of the above network elements can use the terminology in 5G, or they may use other names, etc. This is explained uniformly here and will not be repeated below.

[0232] It should also be understood that Figure 1 The various network elements communicate with each other based on service-oriented interfaces, such as using service-oriented interfaces to exchange information or call services. Figure 1 The interface names between the various network elements are merely examples; in actual implementations, the interface names may differ, and this application does not impose any specific limitations on them. Furthermore, the names of the messages (or signaling) transmitted between the aforementioned network elements are also merely examples and do not constitute any limitation on the function of the messages themselves.

[0233] Apart from Figure 1In addition to the network elements or entities shown, this application also relates to:

[0234] 1. Location Management Function (LMF) Entity: Used to determine the location of terminal equipment, obtain downlink location measurements or location estimates from terminal equipment, etc. For example, in future communication systems, such as 6G, the location management function network element may still be an LMF network element, or may have other names; this application does not limit this.

[0235] 2. Internet of Things (IoT) Server: This server acquires information related to the Internet of Things (IoT) and manages IoT-related devices. These IoT-related devices may include, but are not limited to, readers, tags, sensors, IoT terminal devices, terminal devices, IoT controllers, and operation requesters. The IoT-related information may include, but is not limited to, information about IoT-related devices, such as one or more of the following: address information, port information, device identification information, device location information, device status information, and device mapping relationships. The device mapping relationships may include the mapping relationship between a device and a geographical location, and the mapping relationship between a device and other devices, such as the mapping relationship between a device and a tag. It should be understood that the IoT server can also be named an IoT platform or other names; that is, the terms IoT server and IoT platform can be interchanged. This application does not limit the name of the IoT server.

[0236] 3. Operation Requestor: This can be a server or an application function. In this embodiment, the operation requestor can be understood as a device that sends operation instructions. For example, the operation requestor can be a server, a P-IoT server, an application function (AF), or other devices that send operation instructions. The operation requestor can correspond to a certain type of user, which can include enterprises, tenants, third parties, or companies, without restriction. The fact that the operation requestor corresponds to a certain type of user can be understood as the operation requestor belonging to that type of user and being managed by that type of user.

[0237] 4. The reader interacts with the tag via radio frequency signals or wireless signals. It should be understood that this application does not limit the name of the reader; the reader can also be named a reader-writer or other names, meaning the terms "reader" and "writer" are interchangeable. The reader-writer here possesses the functions involved in the reader described in this application, such as the ability to perform the operations described in this application on the terminal (e.g., the tag) (e.g., acquiring tag information, inventory operations, read operations, write operations, invalidation operations, or message interaction operations with the tag), the ability to acquire billing-related information and / or billing information, and the ability to send billing information to the CHF (CHF). In one possible implementation, the reader can send instructions from the server or application function to the tag, or the reader can send messages from the tag to the server or application function. In one possible implementation, the reader can acquire information stored in a specified tag according to instructions issued by the server. For example, in the case of an inventory operation (or storage operation), the reader acquires the tag's identification information; this identification information can be a unique identifier for the tag or a temporary identifier for the tag. For example, in a read operation, the reader reads the data from the tag's storage area. Optionally, in situations where it's necessary to rewrite the information stored within the tag, the reader can also have a write function; for example, in a write operation, the reader writes the data to the tag's storage area. In addition, the reader can perform an invalidation operation on the tag. After an invalidation operation is performed, the tag becomes invalid and cannot be used for operations such as retrieving tag information, inventory operations, read operations, message interaction with the tag, or write operations. In one possible implementation, the inability to retrieve tag information after tag invalidation can be understood as the reader being unable to obtain the tag information of the invalidated tag. In another possible implementation, the inability to perform message interaction with the tag after tag invalidation can be understood as the reader being unable to interact with the invalidated tag. In this application, the reader can be a terminal device, or an access network device, pole station, eNodeB, gNodeB, integrated access and backhaul (IAB) node, etc. This application does not limit the form of the reader.

[0238] To better understand the technical solutions of the embodiments of this application, some related concepts are introduced below.

[0239] I. Passive Internet of Things (P-IoT) Technology:

[0240] Passive IoT (P-IoT) refers to network nodes that are passive. These nodes do not have their own power source or primarily rely on batteries or other power devices, but instead obtain energy from the environment for functions such as data sensing, transmission, and distributed computing. A passive IoT architecture can include passive tags, readers, and servers. The reader uses radio frequency (RF) for contactless two-way data communication, reading and writing electronic tags or RFID cards to identify targets and exchange data. It operates in two ways: one is that when a tag enters the reader's effective identification range, it receives the RF signal emitted by the reader and uses the energy obtained from the induced current to transmit the information stored in the chip (corresponding to a passive tag). This technology is widely used in various industries; two application scenarios are briefly listed below:

[0241] 1. Warehouse / Transportation / Materials: Embed or attach passive IoT tags to goods stored in warehouses, shopping malls, etc. During the logistics process, the relevant information of the goods is automatically collected by the reader. Managers can quickly query the information of the goods in the system, reduce the risk of loss or theft, improve the speed of goods handover, improve accuracy, and prevent cross-selling and counterfeiting.

[0242] 2. Fixed Asset Management: Places with large assets or valuable items, such as libraries, art galleries, and museums, need complete management procedures or rigorous protection measures. When there are abnormal changes in the storage information of books or valuable items, the system will immediately alert the administrator to handle the relevant situation.

[0243] It should be noted that the communication method in this application is illustrated using passive Internet of Things (IoT) as an example. The method in this application is not limited to passive IoT technology, but can also be applied to other technologies, such as semi-active IoT technology, semi-passive IoT technology, active IoT technology, etc. Semi-active IoT technology can be understood as having a semi-active terminal. Semi-passive IoT technology can be understood as having a semi-passive terminal. Active IoT technology can be understood as having an active terminal.

[0244] II. Label Inventory Process

[0245] Figure 2 This diagram illustrates an interactive approach for tag inventory management in a passive Internet of Things (IoT) environment.

[0246] It should be understood that the so-called label inventory refers to taking stock of the existing labels or obtaining label identifiers.

[0247] S101, when the operation requester requests to conduct an inventory of tags in a certain area, it can send an inventory instruction to the reader. The instruction may include the location information of the inventory area, the identification information of the tags, etc.

[0248] It should be understood that each tag will have its own identifier. In one possible implementation, the tag identifier can be a globally unique code—such as an electronic product code (EPC)—or a temporary identifier, such as one assigned by the network or by the operation requester. The tag identification information included in the inventory instruction can be the identifiers of one or more tags, such as the range of tag identifiers.

[0249] For example, an inventory instruction could include "Inventory; Label Identifier: 1-100; Reader Identifier 1, Reader Identifier 2; Shanghai Pudong New Area". This instruction means requesting readers with reader identifiers 1 and 2 in Shanghai Pudong New Area to inventory labels with label identifiers ranging from 1 to 100.

[0250] S102, after the reader receives the inventory instruction, it performs the inventory operation according to the identification information of the tag in the instruction.

[0251] The reader will send a corresponding inventory message based on the inventory instruction, which includes the identifier of one or more tags.

[0252] For example, corresponding to the inventory instruction in S101, the inventory message includes "Label Identifier: 1-100". Then, tags with label identifiers belonging to 1-100 will send a response message to the reader after receiving the inventory message. This response message may include the label's identifier. Thus, the reader can determine which tags with label identifiers belonging to 1-100 are within its coverage area.

[0253] S103: After the reader completes the inventory operation, it sends the inventory results to the server.

[0254] III. Tag Operations:

[0255] 1. The label inventory operation (or storage operation) is as described above. In one possible implementation, the inventory operation may also include a full label inventory operation, i.e., obtaining the identifiers of labels within the reader's coverage area. Understandably, this type of operation can be given a different name to distinguish it from the above-mentioned inventory operation, such as a full label inventory operation or an unrestricted inventory operation; or, when the label identifier range in the above-mentioned inventory operation is not limited, it can be understood as obtaining the identifiers of labels within the reader's coverage area.

[0256] 2. Read operation, which involves reading data from the tag. Tags can have storage capabilities, and their storage area can store data. If a requester wants to read data from a tag, it sends a read command to the reader. The reader then reads the data from the tag's storage area according to the command and sends the data to the server.

[0257] 3. Write operation, which is the writing of data to the tag. The requesting party can send a write command to the reader, and the reader will perform the write operation on the tag according to the command, writing data to the tag's storage area.

[0258] 4. Invalidation Operation: Even if the tag is invalidated. The requesting party can send an invalidation command to the reader, which may include the tag identifier (i.e., the identifier of the tag to be invalidated). The reader performs the invalidation operation on the tag according to the invalidation command. After the operation is completed, the tag will be invalidated and cannot be inventoried or subjected to other operations.

[0259] 5. Acquiring Tag Information. In one possible implementation, the reader acquires or receives tag information sent by the tag. The reader then sends this tag information to the operation requester or the core network device. In another possible implementation, before acquiring the tag information sent by the tag, the reader may receive an operation instruction and send the operation instruction to the tag; this operation instruction may come from the operation requester or from the core network device, and this application is not limited thereto. In one possible implementation, the tag information may include tag identification information and / or information stored in the tag.

[0260] 6. Message interaction with the tag. In one possible implementation, the reader sends a message from the operation requester (server or application function) to the tag. In another possible implementation, the reader receives the message sent by the tag and sends a message from the tag to the operation requester (server or application function). In yet another possible implementation, the reader can interact with the tag by exchanging messages, such as exchanging random numbers, before receiving the message sent by the tag.

[0261] 7. Sending payload to the tag. In one possible implementation, the server or application function can send the payload to the tag via a reader. After receiving the payload from the server or application function, the reader sends the payload to the tag. In another possible implementation, the core network device can send the payload to the tag via a reader. After receiving the payload from the core network device, the reader sends the payload to the tag. For example, the payload here can be instructions sent to the tag by the core network device, server, or application function; data written to the tag by the core network device, server, or application function; application layer information sent to the tag by the core network device, server, or application function; or, the payload here can also be other tag-related information, which is not limited in this application.

[0262] IV. UE Registration Process:

[0263] Figure 3 A schematic interactive diagram of the UE registration process is shown.

[0264] In S201, the UE sends a registration request message to the RAN, which carries the registration type and the UE's identification information, such as a subscription concealed identifier (SUCI), a 5G globally unique temporary identity (5G-GUTI), or a permanent equipment identifier (PEI).

[0265] It should be understood that there are several types of registration:

[0266] 1) Initial registration: The registration process initiated when the UE is in the deregistration state;

[0267] 2) Mobility registration update: A registration process initiated by the UE when it needs to move;

[0268] 3) Periodic registration update: A registration process initiated when the UE is in the registration state and the periodic registration update timer expires;

[0269] 4) Emergency registration: A registration process initiated when the UE is in a service-restricted state;

[0270] For UE identification information, when the UE has a valid 5G-GUTI (a temporary identity identifier assigned by the AMF serving it), the 5G-GUTI is carried in the registration request; if the UE does not have a valid 5G-GUTI, the SUCI is carried; in emergency registration, if the UE does not have a valid 5G-GUTI and does not have a subscription permanent identifier (SUPI) (i.e., no SUCI, the SUCI is an encrypted SUPI), the PEI is carried.

[0271] S202, RAN selects the appropriate AMF.

[0272] S203, the RAN forwards the registration request message sent by the UE to the AMF.

[0273] S204, AMF selects a suitable AUSF to perform authentication and other security procedures; UE, AMF, AUSF, and UDM interact to complete authentication and other security procedures.

[0274] S205. After the UE and the network side successfully authenticate each other, the AMF can interact with the UDM to obtain the UE's subscription data.

[0275] In S206, the AMF sends an N2 message to the RAN, which includes a NAS message that the RAN needs to forward to the UE. This NAS message includes a registration acceptance message (NAS message) sent by the AMF to the UE.

[0276] S207, the RAN forwards the registration acceptance message (NAS message) sent by the AMF to the UE.

[0277] V. Protocol Data Unit (PDU) Session Establishment Process:

[0278] Figure 4 A schematic interactive diagram of the PDU session establishment process is shown.

[0279] S301, the UE sends a PDU session establishment request message (NAS message) to the AMF, which carries parameters such as PDU Session ID, UE Requested DNN, and S-NSSAI.

[0280] For S302, select the appropriate SMF for AMF.

[0281] S303, the AMF sends a PDU session creation session context request message to the SMF, which carries parameters such as SUPI (UE identifier), the DNN requested by the UE, and the PDU Session ID.

[0282] Optionally, in S304, the SMF obtains session management subscription data from the UDM.

[0283] S305, SMF sends a PDU session creation session context response message to AMF.

[0284] Optionally, S306, perform a PDU session authentication or authorization process.

[0285] S307 If dynamic PCC rules are required, the SMF selects a PCF and establishes a session policy association with that PCF.

[0286] For S308, SMF should select a suitable UPF.

[0287] S309, SMF initiates session policy association modification to PCF. In this step, SMF will send the IP address assigned to UE to PCF.

[0288] S310, SMF and UPF establish N4 connection.

[0289] In step S311, the SMF sends an N1N2 message to the AMF. This message carries information such as the UPF tunnel endpoint identifier. This information is then sent to the RAN to inform the RAN where the uplink data should be sent. If the PDU session is for IMS, the SMF will include the P-CSCF address in this message.

[0290] S312, the AMF sends an N2 PDU session request message to the RAN, which carries the NAS message that needs to be sent to the UE (if the PDU session is for IMS, it contains the P-CSCF address information).

[0291] S313, the RAN establishes air interface resources with the UE, and the RAN sends a NAS message to the UE; the NAS message carries a PDU session establishment and reception message and P-CSCF address information (if the PDU session is for IMS).

[0292] In S314, the RAN sends an N2 PDU session response message to the AMF, which carries the tunnel endpoint identifier on the RAN side. This information is used to tell the UPF where the downlink data should be sent.

[0293] S315, the AMF sends the message sent by the RAN to the SMF via the PDU session update session context request.

[0294] S316, SMF sends the AN tunnel endpoint identification information on the RAN side to UPF through the N4 session modification procedure.

[0295] S317, SMF sends a PDU session update session context response message to AMF.

[0296] Currently, enterprises with needs for warehousing, transportation management, and fixed asset management commonly use passive Internet of Things (IoT) systems consisting of tags, readers, and servers to manage goods or assets by attaching or embedding tags. In this system, the server needs to store reader information and interact with and manage the readers and tags through signaling communication, resulting in significant network resource consumption. Furthermore, these enterprises typically need to deploy 3GPP (3rd Generation Partnership Project) networks, and supporting both networks simultaneously incurs high operational costs. Therefore, reducing operational costs and minimizing network resource consumption has become a pressing issue.

[0297] This application provides a communication method and apparatus that reduces enterprise operation and maintenance costs and server resource consumption by integrating passive Internet of Things (IoT) with the 3GPP system. The following describes the method in conjunction with... Figure 5 This paper introduces several architecture diagrams of 3GPP networks supporting passive Internet of Things (P-IoT).

[0298] In one possible design, the architecture diagram of the 3GPP network supporting P-IoT is as follows: Figure 5 As shown in (a) in the figure.

[0299] In this architecture, the server sends instructions to the reader via the 3GPP network, and the reader operates on the tag according to the instructions.

[0300] The following is based on Figure 5 The following section provides a detailed description of several possible instruction transmission methods in the architecture shown in (a).

[0301] In the first possible implementation, instructions are transmitted via a user plane connection established between the reader and the operation requester. That is, the reader establishes a session, the operation requester sends instructions to the reader through the user plane connection, the reader executes the corresponding operation based on the instructions, and obtains the operation result. The reader then sends the operation result back to the operation requester through the user plane connection. Since this user plane connection is established between the reader and the operation requester, the operation requester needs to know the connection information established with the reader, such as address / port information. Furthermore, before sending instructions, the operation requester needs to know which readers are in the area where it wants to perform tag operations, so that it can send instructions to the corresponding readers.

[0302] The second possible implementation involves transmitting instructions via a user plane connection. Unlike the first implementation, this user plane connection includes a first connection between the user plane device (UPF) and the operation requester, and a second connection between the UPF and the reader. The UPF receives instructions from the server through the first connection and sends the instructions to the reader through the second connection. Therefore, when the UPF receives an instruction from the operation requester, it needs to determine the reader to which the instruction is to be received and send the instruction to that reader. In this implementation, the operation requester establishes a connection with the UPF; that is, the operation requester does not need to know the distribution of readers, only which UPFs are located in the area where the operation is to be performed. The operation requester only needs to send instructions to the UPF; which readers these instructions will subsequently be sent to can be determined by the UPF based on some correspondence or association information. Of course, the operation requester can also obtain reader information, thus determining the reader to receive the instruction and the UPF serving that reader before issuing the instruction.

[0303] The third possible implementation involves transmitting commands via the control plane channel. That is, the operation requester sends commands through core network equipment. In one possible implementation, the operation requester sends commands to the AMF via the NEF. The AMF then sends the commands to the reader. After the reader executes the commands, it sends the operation results to the AMF. The AMF then sends the operation results to the operation requester via the NEF. In this implementation, the operation requester does not need to know the distribution of the readers; it only needs to know which AMFs are located in the area where the operation is to be performed. The operation requester only needs to send commands to the NEF or AMF; the subsequent transmission of these commands to which readers can be determined by the NEF or AMF based on some correspondence or association information. Of course, the operation requester can also obtain reader information, thus determining the reader receiving the commands and the AMF or NEF serving that reader before issuing the commands.

[0304] It should be understood that for the second and third possible implementations described above, the operation requester can send instructions to the network without obtaining reader information. That is, the operation requester only needs to know the core network device (e.g., UPF in the second possible implementation and AMF or NEF in the third possible implementation) corresponding to the area where the operation is to be performed. Therefore, in this case, the instruction issued by the server can only include area information and does not need to include the reader identifier. For example, the instruction issued by the server could be "Inventory; Target area A, tag identifier range 1-100". In this case, the operation requester only needs to send this instruction to the core network device in the target area; or the operation requester can send this instruction to all core network devices it is connected to, and the core network device will determine whether the area indicated by the instruction is the area where the core network device is located. If so, it will continue to send the instruction; otherwise, it will not send the instruction. For the core network devices, they need to determine the reader receiving the instruction based on the area information included in the instruction; otherwise, the scope of the tag operation will not match the target area A. For details on how core network devices determine the reader based on the area information in the instructions, please refer to the description corresponding to method 500-600.

[0305] It should also be understood that when the requesting party needs to perform an operation on a specific tag, its issued instruction may be "Inventory; Tag Identifier 3"; this instruction means to inventory the tag with tag identifier 3. This instruction may not include the reader identifier or area information. When the core network device receives this instruction, since it does not include the reader identifier or area information (or, in other words, the instruction may include area information, but the area indicated by the area information is large), the core network device may instruct the readers to perform tag inventory one by one until the tag is inventoried (or until all readers have inventoried but have not found the tag). If the core network device starts the inventory from a single reader each time, the inventory efficiency is low and the network resource consumption is high. For details on how the core network device can efficiently determine the target reader based on tag information, please refer to the description corresponding to methods 700-1000.

[0306] In another possible design, the architecture diagram of the 3GPP network supporting P-IoT is as follows: Figure 5 As shown in (b) of the diagram.

[0307] In one possible implementation, the reader can be managed by an IoT platform (which can be understood as an IoT server). The IoT platform manages the reader by acquiring information related to it. For example, core network devices can perform mobility management, session management, and other management processes on the reader, obtaining its location information, address / port information, etc. The core network devices send this information to the IoT platform, allowing the IoT platform to obtain reader information in real time. The IoT platform can also interact with the operation requester, enabling the operation requester to determine the reader receiving the command and how to send the command to the network before sending it (e.g., determining the reader identifier if through the control plane channel; determining the reader address / port information if through the user plane channel). In this implementation, the IoT platform can send information to the reader through either the control plane or user plane channel; the operation requester can also send information to the reader through either the control plane or user plane channel. This technical path does not limit the method of sending information. In this implementation, the operation requester needs to obtain the reader's information to determine the reader receiving the command before sending it.

[0308] It should be understood that in this possible design, the IoT platform (i.e., the IoT server) needs to periodically acquire relevant information about the reader to obtain its latest status in real time (such as the reader's location or the correspondence between the reader and the tag). The IoT platform can then interact with the operation requester, enabling the requester to determine the target reader to receive the instruction before issuing it. For details on how the core network device collects reader information and sends it to the IoT platform, please refer to the description corresponding to method 1100.

[0309] It should be noted that this application uses 5G network as an example to introduce the communication method, but this application is not limited to it. This application is also applicable to 4G, 6G network, etc.

[0310] The following is combined Figure 6 The communication method 400 of the embodiments of this application will be described in detail. Figure 6 This is a schematic interactive diagram of method 400 of this application.

[0311] S401, the operation requester sends first information to the first core network device. Correspondingly, the first core network device receives the first information from the operation requester. The first information is used to determine the first target reader. The content indicated by the first information includes at least one of the following: the area where the first operation is performed, the target tag to which the first operation is performed, and the first information also indicates the first operation.

[0312] For example, the first operation here can be any one or more of the tag operations mentioned above, such as obtaining tag information, inventory operation (or storage operation), read operation, write operation, invalidation operation, sending payload to the tag, and message interaction operation with the tag. Depending on the first operation, the communication method in this application embodiment can be a tag inventory method, or it can also be a tag storage method, a tag read operation method, a tag write operation method, or a tag invalidation method. Alternatively, the communication method in this application embodiment can also be a method for determining the reader or a method for transmitting instructions.

[0313] It should be understood that if the operation requesting party needs to perform a first operation on tags within a certain area, then the operation requesting party can send information indicating that area, such as the aforementioned first information indicating the area where the first operation will be performed; or, if the operation requesting party needs to perform a first operation on one or more tags, then the operation requesting party can send information indicating those one or more tags, such as the aforementioned first information indicating the target tag to which the first operation will be performed; or, if the operation requesting method needs to perform a first operation on one or more tags within a certain area, then the first information can simultaneously indicate both the area where the first operation will be performed and the target tag to which the first operation will be performed. For example, the area here can be a cell, a network coverage area, a registration area, a tracking area, or a geographical location, such as Shanghai Pudong New Area or the Oriental Pearl Tower in Shanghai Pudong New Area. Correspondingly, the information indicating the area here can be location information at a granular level, such as the reader's cell ID, tracking area identity (TAI), registration area information, network identifier, etc., or it can be location information with higher precision, such as latitude and longitude, coordinate values, etc.

[0314] It should also be understood that the target label for which the first operation is performed can be interpreted as the label to which the first operation is to be performed. This application does not limit the "target label for which the first operation is performed" to the possibility that the first operation will be successfully performed.

[0315] Optionally, method 400 may also include the following steps.

[0316] One possible implementation, method 400, includes: a first core network device determining a first target reader based on first information.

[0317] The following describes how the first core network device determines the first target reader based on the different contents indicated by the first information, under several possible scenarios.

[0318] In one possible scenario, the first information indicates the area where the first operation is performed. The first core network device determines the first target reader based on the area where the first operation is performed and the third information. The third information includes one or more of the following: reader identification information, reader location information, reader group identification information, reader address information, or reader port information.

[0319] Alternatively, the first core network can determine the first target reader based on the region where the first operation is performed, the correspondence between the region where the first operation is performed and the third information. This correspondence can be presented in a table format or in other formats.

[0320] For example, when the first core network device is a user plane entity (or user plane device), the first core network device can receive third information from the mobility management device. This third information may include one or more of reader identification information, reader group identification information, and reader location information. It is understood that the first core network device can receive the third information directly from the mobility management device, or it can receive the third information from other devices after those devices have received it. That is, the mobility management device can send the third information to the first core network device directly or through other devices, and the number of other devices is not limited. In one possible implementation, the first core network device can receive third information from a control plane device. The control plane device may include any of the following: mobility management device, session management device, policy control device, unified data management device, or user database. Alternatively, the first core network device can also obtain third information, which may include reader address information or reader port information. Alternatively, when the first core network device is a mobility management device, the first core network device can obtain reader identification information or reader group identification information from the registration process, or it can obtain the reader's location information from processes such as registration process, handover process, tracking area update process, mobility registration update process, or positioning process.

[0321] Specifically, the first core network device can obtain the reader's location information. When the first core network device is a mobility management device, it can obtain the reader's location information through the reader's registration process (described in method 200), handover process, tracking area update process, mobility registration update process, or positioning process. Alternatively, when the first core network device is a user plane device, the user plane device can receive the reader's location information from the mobility management device. The implementation method of the mobility management device obtaining the reader's location information varies depending on the precision of the obtained location information. If it is to obtain location information at a granular level such as the reader's cell ID, tracking area identity (TAI), registration area information, and network identifier, the mobility management device can obtain it during the registration process, handover process, tracking area update process, or mobility update registration process. If it is to obtain more precise location information such as the reader's latitude and longitude coordinates, the mobility management device can perform a positioning process on the reader. Furthermore, if the mobility management device needs to obtain higher precision location information of the reader in real time, it can periodically execute or initiate a positioning process. See the descriptions of methods 500 and 600 for details.

[0322] Optionally, the first core network device can also send third-party information to the IoT service. See the corresponding description in method 1100 for details.

[0323] In a second possible scenario, the first information indicates the target tag to which the first operation is performed. The first core network device determines the first target reader based on the target tag to which the first operation is performed and a first correspondence, wherein the first correspondence includes the correspondence between the target tag and the reader information of the first target reader.

[0324] It should be understood that the first correspondence here may include a correspondence between one or more tags and one or more reader information, wherein the one or more tags include target tags and the one or more reader information includes reader information of the first target reader.

[0325] For example, the first core network device may pre-store the first correspondence, or the first core network device may obtain the first correspondence. Specifically, when the first core network device is a user plane device, it may obtain the first correspondence itself, or it may receive the first correspondence from an access network device, a mobility management device, a session management device, a policy control device, or a unified data management device.

[0326] For details, please refer to the description of method 700 or 800.

[0327] Another possible implementation, method 400, includes the following steps:

[0328] Step 1: The first core network device sends the first information to the second core network device.

[0329] Step two: The first core network device receives the identifier of the first target reader from the second core network device.

[0330] The following describes how the first core network device determines the first target reader based on the different contents indicated by the first information, under several possible scenarios.

[0331] In the first possible scenario, the first information indicates the area where the first operation will be performed. Steps one and two are as follows:

[0332] The first core network device sends the area of ​​the first operation to the second core network device;

[0333] The first core network device receives the identifier of the first target reader from the second core network device. The identifier of the first target reader is determined by the second core network device based on the area where the first operation is performed and third information. The third information includes one or more of the following: reader identification information, reader location information, reader group identification information, reader address information, or reader port information.

[0334] It should be understood that the second core network device involved in this application may be AMF, SMF, NEF, UDM, user data repository (UDR), or PCF.

[0335] In the second possible scenario, the first information indicates the target label to which the first operation is performed. Steps one and two are as follows:

[0336] The first core network device sends the target tag of the first operation to the second core network device;

[0337] The first core network device receives the identifier of the first target reader from the second core network device. The identifier of the first target reader is determined by the second core network device based on the target tag of the first operation and the first correspondence relationship. The first correspondence relationship includes the correspondence between the target tag and the reader information of the first target reader.

[0338] In one possible implementation, the identifier of the first target reader may include one or more of the following information: reader identifier information, reader group identifier information, reader address information, or reader port information.

[0339] It should be understood that the first correspondence can be pre-configured or obtained by the first core network device. There are multiple ways for the first core network device to obtain the first correspondence. Two possible methods are introduced below.

[0340] In Method 1, the first core network device sends sixth information to one or more readers, enabling the one or more readers to perform a second operation on the tags within its coverage area based on the sixth information. The first core network device receives seventh information from the one or more readers, which identifies some or all of the tags within the coverage area, including target tags. The one or more readers include a first target reader. The first core network device determines a first correspondence based on the seventh information or based on the seventh information and the one or more readers. In one possible implementation, the second operation can be the first operation, or the second operation can be a full tag inventory operation, a full tag storage operation, a tag inventory operation without restrictions, or a tag storage operation without restrictions. That is, the second operation can be understood as performing an inventory (or storage) operation on all tags within the reader's coverage area; or the second operation can also be understood as the reader obtaining the identification information of the tags within the coverage area.

[0341] It should be understood that in Method 1, the core network device can operate on the tags even without receiving instructions from the operation requester. That is, the network side can proactively obtain the correspondence between tags and reader information by inventorying or operating the tags within its coverage area. Optionally, the core network device can also periodically instruct the reader to perform the above operations. See the description of Method 900 for details.

[0342] Method 2: The first core network device sends second information to one or more readers, so that the one or more readers perform a first operation on the target tag according to the second information. The one or more readers include a first target reader. The first core network device receives a seventh message from the one or more readers. The seventh message indicates that the one or more readers have successfully performed the first operation. The first core network device determines a first correspondence according to the seventh message.

[0343] It should be understood that in Method 2, one or more readers may execute the first operation upon receiving instructions from the core network device or the operation requester, or the readers may periodically perform tag inventory and send the acquired tag identification information to the core network device when no instructions are received from the operation requester. For details, please refer to the description of Method 1000.

[0344] Optionally, if the first target reader determined by the first core network device fails to successfully perform the first operation, the first core network device may re-determine the second target reader. If the second target reader can successfully perform the first operation, the first core network device can re-determine or obtain the correspondence between the tag and the reader based on the tag information sent by the second target reader, thereby updating the first correspondence.

[0345] Optionally, the second target reader can be a reader belonging to the same reader group as the first target reader, or a reader located adjacent to the first target reader.

[0346] Specifically, the first core network device receives fourth information from the first target reader, indicating that the first target reader failed to execute the first operation. The first core network device then sends second information to the second target reader, causing the second target reader to execute the first operation based on the second information. The first core network device receives fifth information from the second target reader, indicating that the second target reader successfully executed the first operation. The first core network device updates the first correspondence based on the fifth information, so that the first correspondence includes the correspondence between the target tag whose first operation was performed and the reader information of the second target reader.

[0347] In another possible implementation, when the first core network device does not receive information from the first target reader or does not receive information from the first target reader within a first time period, the first core network device determines or considers that the first target reader has failed to successfully execute the first operation. The first core network device then sends second information to the second target reader, causing the second target reader to execute the first operation based on the second information. The first core network device receives fifth information from the second target reader, indicating that the second target reader has successfully executed the first operation. The first core network device updates the first correspondence based on the fifth information, so that the first correspondence includes the correspondence between the target tag for which the first operation was performed and the reader information of the second target reader.

[0348] For details, please refer to the description corresponding to method 800.

[0349] Optionally, the first core network device sends a first correspondence to the IoT server. This first correspondence includes a first correspondence used to determine the first target reader, and may also include a first correspondence updated based on the correspondence between the second target reader and the tag. See the description of method 1100 for details.

[0350] It should be noted that either the first target reader or the second target reader can include one or more readers. These multiple readers can belong to a first reader group. It is understood that a reader group can include one or more readers. In one possible implementation, one or more readers belonging to the same reader group can have the same priority or different priorities. When the core network device determines to send a command to a reader in this reader group, it can prioritize sending the command to the reader with the higher priority, and only send the command to the reader with the lower priority if the reader fails to perform the operation. If one or more readers in the reader group have the same priority or one or more readers in the reader group are not distinguished by priority, then when the core network device determines to send a command to a reader in this reader group, it can send the command to any one or more readers in the reader group. In another possible implementation, the location information of the multiple readers is the same or similar. The "sameness" here can be understood as the multiple readers having the same cell identifier, tracking area identifier, registration area information, and network identifier; the "similarity" here can be understood as the multiple readers having similar latitude and longitude information, coordinate values, or that the multiple readers are located adjacently, or that the multiple readers are neighboring readers. In another possible implementation, the reader group is a group of readers configured by the network. When the core network device cannot determine which reader's coverage a tag is under, it can send instructions to all or some of the readers in the reader group.

[0351] It should also be noted that the reader information involved in this application includes one or more of the following: reader identification information, reader location information, reader address information, reader port information, and reader group identification information.

[0352] S402, the first core network device sends second information to the first target reader, and correspondingly, the first target reader receives the second information from the first core network device so that the first target reader performs the first operation according to the second information.

[0353] It should be understood that the second information can be the first information, that is, the first core network device can send information to the reader by directly forwarding the first information, or the first core network device can determine the second information based on the first information and send the second information to the first target reader.

[0354] In one possible implementation, the first target reader performing the first operation based on the second information can be understood as the first reader sending the second information to one or more tags. The first target reader receives tag information sent by one or more of the one or more tags.

[0355] The second information includes information sent by the operation requester, which includes one or more of the following: a command to obtain tag information, an inventory operation command, a read operation command, a write operation command, an invalidation operation command, and a payload sent to the tag.

[0356] This application embodiment reduces the operation and maintenance costs of enterprises maintaining two networks simultaneously and reduces network resource consumption by integrating passive IoT with 3GPP networks, that is, by managing readers and tags in passive IoT through core network equipment.

[0357] It should be noted that, in one possible implementation, the correspondence involved in this application can be understood as a mapping table, mapping relationship, or association relationship. Information with correspondence can be stored in a table or other form. This application does not limit the storage form of information with correspondence.

[0358] The following sections, using methods 500-800, detail the specific implementation of "the first core network device determining the first target reader based on the first information" involved in method 400. Methods 500 and 600 primarily describe possible scenario one, i.e., how the first core network device determines the first target reader based on the first information when "the first information indicates the area where the first operation is performed." Methods 700 and 800 primarily describe possible scenario two, i.e., how the first core network device determines the first target reader based on the first information when "the first information indicates the target tag to which the first operation is performed."

[0359] The following is combined Figure 7 and Figure 8 The following describes two possible implementation methods for the above-mentioned possible scenario one, taking the first core network device as UPF or AMF as examples.

[0360] The following is combined Figure 7 The communication method 500 of the embodiments of this application will be described in detail. Figure 7 This is a schematic interactive diagram of method 500 of this application.

[0361] It should be understood that method 500 and above Figure 5 Taking the architecture diagram shown in (a) as an example, the specific implementation of method 500 corresponds to the second possible implementation method, that is, the first core network device in method 400 can be a UPF.

[0362] It should be noted that the tag operations involved in Method 500 can specifically be any of the following: obtaining tag information, inventory operations (or storage operations), read operations, write operations, invalidation operations, sending payloads to tags, and message interaction operations with tags. The server involved in Method 500 is one manifestation of the operation requester; the server here can also be an application function.

[0363] S501, the reader has completed the registration process. For details, please refer to [link / reference]. Figure 3 Related descriptions.

[0364] It should be understood that during the registration process, the AMF can determine that the device is a reader based on the contract data, or the AMF can determine that the device is a reader through the information sent by the reader.

[0365] It should be noted that one or more readers may complete the registration process. Figure 7 The readers shown are for illustrative purposes only and do not limit the registration process to only one reader in method 500, nor do they limit S501 to be executed only once in method 500. The readers involved in subsequent steps S502-S506 also correspond to those in S501, meaning that any reader that completes the registration process in S501 can proceed to S502-S503 or S504-S506.

[0366] This application involves some reader-related information, such as reader identification information, reader location information, reader group identification information, reader address information, and reader port information.

[0367] In subsequent steps, after the AMF obtains the reader's location information, it can send it to the UPF via the SMF. This can be achieved in various ways, such as Scheme 1 or Scheme 2 described below.

[0368] Option 1:

[0369] S502, AMF uses this device as a reader to perform the positioning process.

[0370] It should be understood that during the registration process, the AMF can obtain location information at a granular level, such as the reader's cell ID, tracking area identity (TAI), registration area information, and network identifier. By executing the positioning process, the AMF can obtain more precise location information of the reader, such as latitude and longitude coordinates.

[0371] It should also be understood that step S502 can be performed after the reader completes the registration process, before the session establishment process, during the session establishment process, or after the session establishment process, and this application does not limit it in this regard.

[0372] Optionally, the positioning process can be a periodic positioning process. That is, the AMF can periodically or continuously obtain the reader's location information before sending the reader's location information to the UPF via the SMF.

[0373] S503, the reader completes the session establishment process; for details, please refer to [link / reference]. Figure 4 The relevant description is as follows: During the session establishment process, the AMF can send the reader's location information to the UPF via the SMF. In one possible implementation, the AMF can also send the reader identification information to the UPF via the SMF.

[0374] Alternatively, during the session establishment process, the AMF can send the correspondence between the reader's location information and area information 01 to the UPF via the SMF. The AMF can then determine the correspondence between the reader's information and area information 01 based on the reader's location information and area information 01. For example, if the reader's location information is included in area information 01, it can be assumed that there is a correspondence between the reader's location information and area information 01.

[0375] It should be noted that the AMF can send reader identification information and reader location information during the session establishment process, or it can send reader identification information and reader location information before or after the session establishment process. This application does not limit this.

[0376] Option 2:

[0377] S504 After the reader completes the registration process (or session establishment process), the AMF can obtain the reader's location information through the location process (or periodic location process), handover process, tracking area update process, or mobility registration update process.

[0378] For example, the AMF can obtain higher-precision location information such as the reader's coordinates and latitude and longitude through the positioning process; and obtain one or more of the following information: cell identifier, tracking area identifier, registration area information, network identifier, etc., through the handover process, tracking area update process, or mobility registration update process.

[0379] S505, the AMF sends the reader's location information to the SMF; in one possible implementation, the AMF also sends the reader's identification information to the SMF; or, the AMF sends the correspondence between the reader and the area information 01 to the SMF.

[0380] The correspondence between the reader and the area information 01 is obtained by AMF based on the reader location information and the area information 01. For example, when the reader's location information is included in the area information 01, it can be assumed that there is a correspondence between the reader's location information and the area information 01.

[0381] S506, corresponding to S505, the SMF sends the reader's location information to the UPF; in one possible implementation, the SMF also sends reader identification information to the UPF; or the SMF sends the correspondence between the reader and the area information 01 to the UPF.

[0382] S507, when the UPF receives operation instruction 1 from the server, the instruction includes area information 02 and operation type. Optionally, it may also include tag information.

[0383] It should be understood that the area information 02 here may be the same as or different from the area information 01 in S503 or S505. When they are different, the area information 02 here may be a subset of the area information 01 in S503 or S505.

[0384] S508, the UPF determines the target reader based on area information 02 and the reader's location information, or the UPF determines the target reader based on the correspondence between area information 02, reader information, and area information 01. The reader information here can be one or more of the following: reader location information, reader identification information, reader address information, and reader port information.

[0385] In addition, the UPF changes the target address / port information of the downlink data (operation instruction 1) from the UPF's address / port information to the target reader's address / port information, thus obtaining operation instruction 2.

[0386] It should be understood that UPF can obtain the reader's address / port information during the session establishment process.

[0387] As an example, the UPF determines the target reader based on the correspondence between region information 02, reader address / port information, and region information 01. Assume the UPF stores the correspondence between region information 01 and reader address / port information. For example, region information 01 may include region A and region B, and reader address / port information may include reader address 1 / port 1 and reader address 2 / port 2. The correspondence is that region A corresponds to reader address 1 / port 1 and reader address 2 / port 2, and region B corresponds to reader address 3 / port 3 and reader address 4 / port 4. Then, when the region information 02 included in operation instruction 1 in S507 is region B, the UPF can determine the target reader as the reader corresponding to reader address 3 / port 3 or reader address 4 / port 4 based on the stored correspondence. It should be noted that the specific form of this correspondence may be presented as the association table shown in Table 1, or it may be in another form; this application does not limit this.

[0388] Table 1

[0389]

[0390] As another example, UPF determines the target reader based on area information 02 and the reader's location information. Specifically, UPF can identify the reader whose location information is contained in area information 02 as the target reader. For example, if area information 02 is Huangpu District, Shanghai, and the latitude / longitude / coordinates / cell identifier of a certain reader indicates that the reader is located on the Bund (which belongs to Huangpu District, Shanghai), then that reader can be identified as the target reader.

[0391] As another example, UPF determines the target reader based on the correspondence between area information 02, area information 01, and the reader's location information and address / port information. For instance, the correspondence between area information 01 and reader information is shown in the first, second, and third columns of Table 2. Assuming area information 02 is area B, and the reader's location information is latitude and longitude 4 / coordinate value 4 / cell identifier 3, then the target reader's address / port information is reader address 4 / port 4. Additionally, the reader's location information in the third column of Table 2 can also include tracking area identifier, registration area information, network identifier, etc.

[0392] It should be noted that the specific form of this correspondence may be presented as the association table shown in Table 2, or it may be in other forms. This application does not limit this.

[0393] It should also be noted that the correspondence between area information 01 and reader location information, reader address / port information can also be presented in the form of the correspondence between area information 01 and reader location information, or the correspondence between reader location information and reader address / port information, or it can be presented in other forms. This application does not limit this.

[0394] Table 2

[0395]

[0396] Alternatively, the UPF can also determine the target reader based on the correspondence between the area information 02 and the area information 01, the reader identifier and the reader address / port information, as described in the first, second and fourth columns of Table 2, or other forms of representation, which are not limited in this application.

[0397] Alternatively, the UPF can also determine the target reader based on the area information 02, and the correspondence between the area information 02, the reader identification information, the reader location information, and the reader address / port information, as shown in Table 2, or other forms of representation, which are not limited in this application.

[0398] It should be noted that, as shown in Table 2, Reader 1 (the reader corresponding to Reader Identifier 1) and Reader 2 (the reader corresponding to Reader Identifier 2) have different specific latitude and longitude coordinates and / or coordinate values, but they may belong to the same cell. That is, readers with different specific latitude and longitude coordinates and / or coordinate values ​​may access the network through the same cell. As shown in Table 2, Reader 3 (the reader corresponding to Reader Identifier 3) and Reader 4 (the reader corresponding to Reader Identifier 4) have different specific latitude and longitude coordinates and / or coordinate values, and belong to different cells. That is, readers with different specific latitude and longitude coordinates and / or coordinate values ​​can access the network through different cells.

[0399] S509, UPF sends operation instruction 2 to the target reader. The content of operation instruction 2 corresponds to the content of operation instruction 1 in S507.

[0400] S510, the target reader performs tag operations according to the content of operation instruction 2.

[0401] S511, the target reader in the reader sends the operation result to the UPF.

[0402] For example, when the tag operation is a read operation, if the operation result is successful, the operation result may also include the acquired data information, such as the tag identifier or data stored in the tag. If the operation result is a failure, the operation result may also include the reason for the failure. Subsequently, the UPF sends the operation result to the server.

[0403] For example, when the tag operation is an inventory operation, if the operation result is successful, the operation result may also include information about the tags that the reader has inventoried (e.g., the tag identifier).

[0404] In this embodiment, by acquiring the reader's location information, the target reader can be determined based on the region information in the server instruction. Furthermore, by periodically acquiring the reader's location information, the core network device can obtain the latest location information of the reader, thereby further improving the success rate of determining the target reader based on the instruction of the operation requester.

[0405] The following is combined Figure 8 The communication method 600 of the embodiments of this application will be described in detail. Figure 8 This is a schematic interactive diagram of method 600 of this application.

[0406] It should be understood that method 600 and above Figure 5 Taking the architecture diagram shown in (a) as an example, the specific implementation of method 500 corresponds to the third possible implementation method, that is, the first core network device in method 400 can be AMF.

[0407] It should be noted that the tag operation involved in Method 600 can specifically be any one of the following: inventory operation (or stocking operation), read operation, write operation, or expiration operation. The server involved in Method 600 is one manifestation of the operation requester; the server here can also be an application function.

[0408] For details, please refer to the description corresponding to S501.

[0409] For details, please refer to the description corresponding to S502.

[0410] S603, AMF received operation instruction 1 from the server.

[0411] In one possible implementation, the AMF receives operation instructions 1 from the server via the NEF. These instructions include area information and operation type. Optionally, tag information may also be included.

[0412] S604, the AMF determines the target reader based on the area information and the reader's location information, or based on the area information and the correspondence between the reader and the area information.

[0413] The correspondence between the reader and the area information can be obtained by the AMF based on the reader's location information and area information.

[0414] For details on how the AMF determines the target reader in S604, please refer to the description in S508.

[0415] Alternatively, the AMF may not need to store reader address / port information. As an example, the correspondence between stored reader addresses is shown in Table 3. Furthermore, the reader location information in the third column of Table 3 can also include tracking area identifier, registration area information, network identifier, etc. Assuming that area information 02 in operation instruction 1 is area A, then according to Table 3, the AMF can determine the destination reader as the reader corresponding to reader identifier 1 or reader identifier 2.

[0416] It should be understood that the reader identifier here can be obtained by AMF during the registration process or during the session establishment process. The correspondence between the reader identifier information and the reader's location information can also be obtained during the registration process, after the registration process, before the session establishment process, during the session establishment process, or after the session establishment process.

[0417] It should be noted that the specific form of this correspondence may be presented as the association table shown in Table 3, or it may be in other forms. This application does not limit this.

[0418] It should also be noted that the correspondence between area information 01 and the reader's location information and reader identification information can also be presented in the form of the correspondence between area information 01 and the reader's location information and the correspondence between the reader's location information and the reader identification information, or it can be presented in other forms. This application does not limit this.

[0419] Table 3

[0420]

[0421] S605, AMF sends operation instruction 2 to the target reader in the reader. The content of operation instruction 2 corresponds to the content of operation instruction 1 in S603.

[0422] One possible implementation is that the AMF sends instructions to the reader via NAS signaling or N2 messages.

[0423] S606, the target reader in the reader performs the tag operation according to the content of operation instruction 2.

[0424] S607, the target reader in the reader sends the operation result to the AMF.

[0425] For example, when the tag operation is a read operation, if the operation result is successful, the operation result may also include the acquired data information, such as the tag identifier or data stored in the tag. If the operation result is a failure, the operation result may also include the reason for the failure. Subsequently, the AMF sends the operation result to the server.

[0426] For example, when the tag operation is an inventory operation, if the operation result is successful, the operation result may also include information about the tags that the reader has inventoried (e.g., the tag identifier).

[0427] In this embodiment, by acquiring the reader's location information, the target reader can be determined based on the region information in the server instructions. Furthermore, by periodically acquiring the reader's location information, the core network device can obtain the latest location information of the reader, thereby further improving the success rate of determining the target reader based on the server instructions.

[0428] The following is combined Figure 9 and Figure 10 The following describes two possible implementation methods for the above-mentioned possible scenario two, taking the first core network device as UPF or AMF as examples.

[0429] The following is combined Figure 9 The communication method 700 of the embodiments of this application will be described in detail. Figure 9 This is a schematic interactive diagram of method 700 of this application.

[0430] It should be understood that method 700 and above Figure 5 Taking the architecture diagram shown in (a) as an example, the specific implementation of method 700 corresponds to the second possible implementation method, that is, the first core network device in method 400 can be a UPF.

[0431] It should be noted that the tag operation involved in Method 700 can specifically be any one of the following: inventory operation (or stocking operation), read operation, write operation, or expiration operation. The server involved in Method 700 is one manifestation of the operation requester; the server here can also be an application function.

[0432] S701, Reader 1 and Reader 2 complete the registration and session establishment processes. For details of the registration process, please refer to [link / reference needed]. Figure 3 For a detailed description of the session establishment process, please refer to [link / reference]. Figure 4 The description.

[0433] It should be understood that during the registration process, the AMF can determine that the device is a reader based on the contract data, or the AMF can determine that the device is a reader through the information sent by the reader.

[0434] It should be noted that multiple (more than two) readers may complete the registration and session establishment processes. Figure 9 The reader 1 and reader 2 shown are for illustrative purposes only and do not limit the registration process and session establishment process to only two readers in method 700, nor do they limit S701 to be executed only twice in method 700.

[0435] This application involves some reader-related information, such as reader identification information and reader address / port information.

[0436] S702, the UPF receives operation instruction 1 from the server, which includes operation type and tag information 01. Optionally, it may also include area information.

[0437] It should be understood that the label information 01 here refers to the label information of the operation that needs to be performed, as indicated by the operation type.

[0438] S703, UPF determines the first target reader. After the UPF determines the target reader, the destination address / port information of the instruction needs to be replaced with the address / port information of the target reader.

[0439] UPF determines a first target reader based on a stored mapping between one or more tags and one or more readers. The first target reader can be the reader indicated by the mapping or a group of readers indicated by the mapping. The network can group one or more readers into a group. In one possible implementation, the network can group one or more readers that are geographically close together. When determining the first target reader, it can either identify a group of readers as the first target reader or identify one or more readers within a group as the first target reader. This application embodiment involves some reader-related information, such as reader identification information and reader address / port information. This mapping can be represented as a mapping between the identifiers of one or more tags and the reader identifiers and / or reader address / port information of one or more readers.

[0440] For example, the correspondence stored in the UPF is shown in Table 4. Reader 1 can or has performed tag operations on tags 1 and 2, and reader 2 can or has performed tag operations on tags 3 and 4. Alternatively, this correspondence can also be represented by the first and second columns, or the second and third columns, of Table 4. Assuming that tag information 01 in operation instruction 1 is tag identifier 1 and / or tag identifier 2, then according to the correspondence shown in Table 4, the UPF can identify reader 1 as the first target reader.

[0441] Table 4

[0442]

[0443] It should be noted that the specific form of this correspondence may be presented as the association table shown in Table 4, or it may be in other forms. This application does not limit this.

[0444] It should also be noted that the correspondence shown in Table 4 can also be presented in the form of a correspondence between label identifier and reader identifier information, or a correspondence between reader identifier information and reader address / port information, or in other forms. This application does not limit this.

[0445] S704, UPF sends operation command 2 to the first target reader.

[0446] S705, the first target reader executes the tag operation according to operation instruction 2.

[0447] S706, the first target reader sends the operation result to the UPF.

[0448] For example, when the tag operation is a read operation, if the operation result is successful, the operation result may also include the acquired data information, such as the tag identifier or data stored in the tag. If the operation result is a failure, the operation result may also include the reason for the failure. Subsequently, the UPF sends the operation result to the server.

[0449] For example, when the tag operation is an inventory operation, if the operation result is successful, the operation result may also include information about the tags that the reader has inventoried (e.g., the tag identifier).

[0450] Optionally, if the operation result in S706 is an operation failure, or if the UPF does not receive the information sent by the first target reader in S706, i.e. the first target reader has not successfully executed the operation, then method 700 may further include S707-S711.

[0451] S707, UPF identifies the second target reader.

[0452] The second target reader can be any one or a group of readers other than the first target reader, or it can be a reader or group of readers that is adjacent to the first target reader.

[0453] S708, the UPF sends operation instruction 3 to the second target reader. In one possible implementation, operation instruction 3 can be operation instruction 2.

[0454] S709, the second target reader performs tag operation according to operation instruction 3.

[0455] S710, the second target reader sends the operation result to the UPF.

[0456] For a detailed description, please refer to S706, which will not be elaborated here.

[0457] S711, if the operation result of step S710 is successful, then the UPF records or updates the correspondence between the tag and the reader, or more specifically, updates the correspondence between tag information 01 and the reader. If the operation result of step S710 is unsuccessful, then S707-S710 needs to be repeated, that is, the next target reader needs to be re-determined until the target tag (i.e., the tag corresponding to tag information 01) is successfully executed; or when all readers (or all readers in the area corresponding to the area information) fail to successfully execute the operation on the target tag, in this case, the operation result sent by the UPF to the server is unsuccessful.

[0458] For example, assuming the UPF stores the correspondence shown in Table 5, and assuming the tag information 01 in operation instruction 1 is tag identifier 1 and tag identifier 2, and the second target reader successfully performs a tag operation on the tag identified by tag identifier 1 and / or tag identifier 2, then the UPF can update the correspondence shown in Table 4 to Table 5. In one possible implementation, the UPF updates the correspondence between the successfully executed tag and the reader. Here, reader identifier 3 and reader address 3 / port 3 are the reader identifier and reader address / port information of the second target reader, respectively.

[0459] Table 5

[0460]

[0461] S712, UPF sends the operation result to the server.

[0462] In this embodiment, by storing the correspondence between tags and readers, the network can obtain the correspondence based on historical operation results. Simultaneously, the network can group readers, classifying those geographically close together. When determining a target reader, readers from the same group can be identified as target readers. If the reader indicated by the correspondence fails to successfully perform an operation on the tag, a reader in the adjacent area of ​​a reader that has historically operated on the tag can be selected to operate on the tag. This increases the probability of successful tag operation without consuming excessive network resources.

[0463] Optionally, method 700 further includes:

[0464] In S703, if the UPF does not obtain the correspondence between the tag information 01 in operation instruction 2 and the reader, that is, the tag indicated by the tag information 01 has never been operated, the UPF can determine the target reader in a variety of ways. Several possible implementation methods are given below.

[0465] In Method 1, if the operation instruction 1 includes area information, the target reader can be determined according to Method 500. That is, Method 500 can be implemented alone or in combination with Method 700.

[0466] Method 2: UPF can send instructions to any single reader or any group of readers, that is, randomly determine the target reader or target reader group.

[0467] In method three, UPF can also determine the region to be operated based on the server's address / port information or the information of the operation requester, and then determine the target reader based on the operation region information. The operation requester's information can be used to indicate the operation requester, the terminals that the operation requester can manage, and the region where the operation requester can perform the operation.

[0468] Method 4: UPF obtains the correspondence between one or more tag information and the operation area. The one or more tag information includes tag information. UPF determines the operation area based on the one or more tag information and the correspondence, and then determines the target reader based on the operation area.

[0469] Method 5, for details please refer to Method 900.

[0470] Method 6, please refer to Method 1000 for details.

[0471] The following is combined Figure 10 The communication method 800 of the embodiments of this application will be described in detail. Figure 10 This is a schematic interactive diagram of method 800 of this application.

[0472] It should be understood that method 800 and above Figure 5 Taking the architecture diagram shown in (a) as an example, the specific implementation of method 800 corresponds to the third possible implementation method, that is, the first core network device in method 400 can be AMF.

[0473] It should be noted that the tag operation involved in Method 800 can specifically be any one of the following: inventory operation (or stocking operation), read operation, write operation, or expiration operation. The server involved in Method 800 is one manifestation of the operation requester; the server here can also be an application function.

[0474] S801, Reader 1 and Reader 2 completed the registration process respectively. For details, please refer to... Figure 3 Related descriptions.

[0475] It should be understood that during the registration process, the AMF can determine that the device is a reader based on the contract data, or the AMF can determine that the device is a reader through the information sent by the reader.

[0476] It should be noted that multiple (more than two) readers may complete the registration process. Figure 10 The reader 1 and reader 2 shown are for illustrative purposes only and do not limit the registration process to only two readers in method 800, nor do they limit S801 to be executed only twice in method 800.

[0477] This application involves some reader-related information, such as reader identifier and reader address / port information.

[0478] S802, the AMF receives operation instruction 1 from the server, which includes operation type and tag identification information. Optionally, it may also include area information.

[0479] One possible implementation is that the AMF can receive operation instructions from the server via the NEF.

[0480] In S803, the AMF determines the first target reader. The specific implementation is similar to that of the UPF in S703, except that the UPF in S703 is replaced by the AMF. I will not go into details here.

[0481] S804, AMF sends operation command 2 to the first target reader.

[0482] S805, the first target reader executes the tag operation according to operation instruction 2.

[0483] S806, the reader sends the operation result to the AMF.

[0484] For example, when the tag operation is a read operation, if the operation result is successful, the operation result may also include the acquired data information, such as the tag identifier or data stored in the tag. If the operation result is a failure, the operation result may also include the reason for the failure. Subsequently, the AMF sends the operation result to the server.

[0485] For example, when the tag operation is an inventory operation, if the operation result is successful, the operation result may also include information about the tags that the reader has inventoried (e.g., the tag identifier).

[0486] Optionally, if the operation result in S806 is an operation failure, or if the AMF does not receive the information sent by the first target reader in S806, that is, the first target reader fails to execute the operation, then method 800 may further include S807-S811.

[0487] S807, AMF identifies the second target reader.

[0488] The second target reader can be any one or a group of readers other than the first target reader, or it can be a reader or group of readers that is adjacent to the first target reader.

[0489] S808, AMF sends operation instruction 3 to the second target reader. In one possible implementation, operation instruction 3 can be operation instruction 2.

[0490] S809, the second target reader performs tag operation according to operation instruction 3.

[0491] S810, the second target reader sends the operation result to the AMF.

[0492] For a detailed description, please refer to S806, which will not be elaborated here.

[0493] S811, if the operation result of step S810 is successful, then AMF records or updates the correspondence between the tag and the reader, or more specifically, updates the correspondence between the tag information 01 and the reader.

[0494] For details, please refer to the description in S711. If the operation result of step S810 is an operation failure, then S807-S810 need to be repeated, that is, the next target reader needs to be re-determined until the target tag (i.e., the tag corresponding to tag information 01) is successfully operated; or when all readers (or all readers in the area corresponding to the area information) fail to successfully operate on the target tag, the operation result sent by AMF to the server is an operation failure.

[0495] S812, the AMF sends the operation result to the server. Optionally, the AMF can send the operation result to the server via the NEF.

[0496] In this embodiment, by obtaining the correspondence between tags and readers, the network can obtain the correspondence between tags and readers based on historical operation results. Simultaneously, the network can group readers, for example, grouping readers with similar geographical locations together. When determining a target reader, readers from the same group can be identified as target readers. When the reader indicated by the correspondence fails to successfully perform an operation on the tag, a reader in the adjacent area of ​​a reader that has historically operated on the tag can be selected to operate on the tag. This increases the probability of successful tag operation or improves the efficiency of successfully performing an operation on the target tag without consuming excessive network resources.

[0497] Optionally, method 800 further includes:

[0498] In S803, if the AMF does not store the correspondence between the tag information 01 in operation instruction 2 and the reader, that is, the tag indicated by the tag information 01 has never been operated, the AMF can determine the target reader in a variety of ways. Several possible implementation methods are given below.

[0499] In Method 1, if the operation instruction 1 includes area information, the target reader can be determined according to Method 600. That is, Method 600 can be implemented alone or in combination with Method 800.

[0500] Method 2: AMF can send instructions to any single reader or any group of readers, that is, randomly determine the target reader or target reader group.

[0501] In method three, AMF can also determine the region to be operated based on the server's address / port information or the information of the operation requester, and then determine the target reader based on the operation region information. The operation requester's information can be used to indicate the operation requester, the terminals that the operation requester can manage, and the region where the operation requester can perform the operation.

[0502] Method 4: The AMF stores the correspondence between one or more tag information and the operating area. The one or more tag information includes tag information. The AMF determines the operating area based on the one or more tag information and the correspondence, and then determines the target reader based on the operating area.

[0503] Method 5, for details please refer to Method 900.

[0504] Method 6, please refer to Method 1000 for details.

[0505] The following is combined Figure 11 and Figure 12 The following sections provide detailed explanations of methods 1 and 2 for obtaining the first correspondence in method 400. Specifically, method 900 details method 1, and method 100 details method 2.

[0506] It should be noted that methods 900 and 1000 can be implemented independently to perform tag inventory, or they can be combined with methods 700 or 800, that is, the correspondence between the tag information obtained by method 900 or 1000 and the reader can be applied to method 700 or 800.

[0507] Figure 11 This is a schematic interactive diagram of method 900 of this application.

[0508] It should be understood that method 900... Figure 5 The architecture diagram shown in (a) is used as an example for illustration. The specific implementation of method 900 corresponds to the second or third possible implementation method therein.

[0509] The third possible implementation will be described in detail below.

[0510] S901, Reader 1 and Reader 2 completed the registration process respectively. For details, please refer to... Figure 3 Related descriptions.

[0511] It should be understood that during the registration process, the AMF can determine that the device is a reader based on the contract data, or the AMF can determine that the device is a reader through the information sent by the reader.

[0512] It should be noted that multiple (more than two) readers may complete the registration process. Figure 11The readers 1 and 2 shown are for illustrative purposes only and do not imply that only two readers complete the registration process in method 900, nor that S901 is executed only twice in method 900. Similarly, the steps performed by readers 1 and 2 in subsequent processes S903a, S903b, S904, S905, and S906 are for illustrative purposes only and do not imply that only two readers perform the above steps.

[0513] This application involves some reader-related information, such as reader identification information and reader address / port information.

[0514] After the reader completes the registration process, AMF instructs the reader to periodically obtain the tag's location. It should be noted that in this embodiment, performing an inventory operation (or inventory process) or performing a storage operation can be one of the ways for the reader to obtain the tag's location. The reader can also obtain the tag's location information in other ways, and this application does not limit this.

[0515] S902, one possible implementation: The AMF starts a timer. The function of this timer is to instruct the reader to perform an inventory count operation when the timer expires. Optionally, the AMF can periodically start this timer, or the timer can be a periodic timer. In another implementation, the AMF can instruct the reader to periodically execute the inventory count process; the reader starts a timer according to the instruction sent by the AMF; when the timer expires, the reader performs the inventory count operation. Optionally, this timer can be a periodic timer, or the reader can periodically start the timer.

[0516] For S903a and S903b, when the timer expires, the AMF instructs the reader to perform a tag inventory process within the coverage area.

[0517] One possible implementation is that the AMF sends an inventory command to the reader via an N2 message or a NAS message from the reader, instructing the reader to inventory the tags within its coverage area.

[0518] S904, the reader executes the tag inventory process according to the instructions.

[0519] For example, the reader sends an inventory message (e.g., a broadcast message) to the tags within its coverage area. This inventory message may not carry tag information (e.g., it may contain tag identifiers) or it may include information including each tag identifier. Tags receiving this message need to send a response message to the reader. Upon receiving the response message, the reader can determine that it has inventoried the tag within its coverage area.

[0520] After the reader completes the inventory process (S905a and S905b), it sends the inventory results, i.e., the inventory tag identifier, to the AMF. One possible implementation is that the reader sends the inventory results (tag identifier) ​​to the AMF via an N2 message or a NAS message.

[0521] S906, AMF obtains the correspondence between tags and readers based on the tag identification information sent by the reader.

[0522] For the second possible implementation, S901-S906 above also needs to be executed, the difference being:

[0523] In S901, reader 1 and reader 2 also need to perform a session establishment process.

[0524] In S902, the AMF can instruct the reader to execute an inventory count procedure (or inventory operation) before, during, or after the session establishment process. One possible implementation is that the AMF starts a timer, which, upon timeout, instructs the reader to execute the inventory count procedure. Optionally, the AMF can periodically start this timer, or the timer can be a periodic timer. Another implementation involves the AMF instructing the reader to periodically execute the inventory count procedure; the reader starts a timer based on the instruction sent by the AMF; upon timeout, the reader executes the inventory count procedure. Optionally, this timer can be a periodic timer, or the reader can periodically start the timer.

[0525] For the second possible implementation, S907 and S908 also need to be executed, among which,

[0526] S907, the AMF sends the tag-reader mapping relationship to the SMF. This mapping relationship can be complete, full, or an updated partial mapping relationship (i.e., a mapping relationship that has been updated or changed).

[0527] It should be understood that in S902, the AMF can periodically send inventory commands to Reader 1 and Reader 2, or the AMF can instruct Reader 1 and Reader 2 to periodically execute the inventory process. If, compared to the tag-to-reader correspondence obtained by the AMF after the last inventory, only a portion of the tag-to-reader correspondence obtained by the AMF after this inventory has changed, then the AMF can send all or all of the correspondence obtained after this inventory to the SMF, or it can send the portion of the correspondence obtained after this inventory that has changed compared to the correspondence obtained after the last inventory, i.e., the updated partial correspondence mentioned above. This can help save signaling overhead between the AMF and the SMF.

[0528] In S908, the SMF sends the mapping relationship between the tags and readers received in S907 to the UPF.

[0529] In this embodiment of the application, the network or core network device periodically obtains the correspondence between tags and readers, so that when it receives instructions from the server, it can efficiently determine the target reader based on the tag information, thereby performing tag operations in a shorter time or with less signaling overhead.

[0530] Figure 12 This is a schematic interactive diagram of method 1000 of this application.

[0531] It should be understood that method 1000 and above Figure 5 The architecture diagram shown in (a) is used as an example for illustration. The specific implementation of method 1000 corresponds to the second or third possible implementation method therein.

[0532] S1001, Reader 1 and Reader 2 complete the registration process respectively.

[0533] Specifically, in the third possible implementation, reader 1 and reader 2 complete the registration process respectively; in the second possible implementation, reader 1 and reader 2 complete the registration process and the session establishment process respectively.

[0534] It should be noted that multiple (more than two) readers may complete the registration process. Figure 12 The readers 1 and 2 shown are for illustrative purposes only and do not imply that only two readers complete the registration process in method 1000, nor that S1001 is executed only twice in method 1000. Similarly, in subsequent processes S1002-S1004, the execution of relevant steps by reader 1 is for illustrative purposes only and does not imply that only one reader performs the above steps. In S1006-S1008, the execution of relevant steps by reader 1 and reader 2 is for illustrative purposes only and does not imply that only two readers perform the above steps.

[0535] This application involves some reader-related information, such as reader identifier and reader address / port information.

[0536] In subsequent steps, the core network equipment (AMF or UPF) obtains the correspondence between tags and readers in a variety of ways, such as Scheme 1 or Scheme 2 below. Alternatively, it can be based on Scheme 1 and then updated using Scheme 2 to update the already obtained correspondence between tags and readers.

[0537] Option 1:

[0538] When the reader receives inventory command 1 from the core network device, the inventory command 1 includes identifiers of the tags for which inventory command 1 needs to be executed. Among these, [the text abruptly ends here, likely due to an incomplete sentence or missing information]. Figure 5 The second possible implementation corresponding to the architecture diagram shown in (a) is a UPF core network device, and the third possible implementation is an AMF core network device.

[0539] S1002, the reader performs a tag inventory according to the inventory instruction 1, wherein the reader 1 sends an inventory instruction 2 to the tag, and the inventory instruction 2 may include the reader identifier.

[0540] It should be understood that reader 1 here can be any reader or group of readers, or it can be a target reader or group of target readers determined according to, for example, method 500.

[0541] S1003-1, after one or more tags are inventoried, the tags also need to store the reader identifier included in inventory instruction 2. In one possible implementation, the tag stores the reader identifier in the tag's storage area.

[0542] S1003-2, One or more tags send tag identifiers to the reader.

[0543] S1004, the reader sends the inventory tag identifier to the AMF.

[0544] S1005-1, AMF obtains (or updates) the correspondence between tags and readers.

[0545] Optionally, when the core network device in S1001 is a UPF, the method 1000 further includes:

[0546] S1105-2, AMF sends the tag-reader correspondence to SMF.

[0547] S1005-3, SMF sends the tag-reader correspondence to UPF.

[0548] Option 2:

[0549] If the reader does not receive inventory instruction 1, it can also send a reader identifier to the tag. When Scheme 2 is executed alone, the reader here can be all or part of the reader that completes the registration process (and session establishment process) in S1001, or, when Scheme 2 is executed based on Scheme 1, the reader here can also be the reader that performs the tag inventory operation in Scheme 1.

[0550] S1006, the reader can send a reader identifier. In one possible implementation, the reader sends the reader tag via a broadcast message. Optionally, the reader can also periodically send the reader identifier or periodically broadcast the reader identifier.

[0551] S1007, after receiving the reader identifier sent by the reader, when the tag learns from the reader identifier sent by the reader that the currently acquired reader identifier is different from the reader identifier stored in the tag, the tag sends its own tag identifier to the reader, and the tag stores the acquired reader identifier. In one possible implementation, the tag stores the acquired reader identifier in the tag's storage area.

[0552] For example, tag 01 originally had a correspondence with reader 1, or reader 1 could access tag 01. In S1007, tag 01 received a reader identifier sent by reader 2. For instance, tag 01 received a broadcast message from reader 2, which included the reader identifier of reader 2. Tag 01 discovered that the reader identifier in the received broadcast message was different from the reader identifier previously stored in its storage area. Tag 01 then sent its own tag identifier to reader 2 and stored reader 2's reader identifier. In one possible implementation, tag 01 stores reader 2's reader identifier in its own storage area. Tag 01 can store reader 2's reader identifier in a different storage area than the storage area for reader 1's reader identifier, or it can replace the reader identifier of reader 1 stored in its storage area with the reader identifier of reader 2.

[0553] S1008, the reader receives the tag identifier sent by the tag, and the reader sends the tag identifier to the AMF.

[0554] S1009-1, AMF obtains (or updates) the correspondence between tags and readers.

[0555] Optionally, when the core network device in S1001 is a UPF, method 1000 further includes:

[0556] S1009-2, AMF sends the tag-reader correspondence to SMF.

[0557] S1009-3, SMF sends the tag-reader correspondence to UPF.

[0558] In this embodiment, by sending a reader identifier to the tag or periodically inventorying the tags and sending the inventory results to the core network equipment, the core network equipment can obtain the real-time correspondence between the tag and the reader. Simultaneously, based on the tag's ability to store the reader identifier, sending the reader identifier to the tag or periodically sending (or broadcasting) the reader identifier allows the tag to know whether its location has changed, or whether the reader serving the tag has changed. Furthermore, for tags whose location has not changed or whose serving reader has not changed, they do not need to report their identification information, which reduces signaling overhead.

[0559] The following is combined Figure 13 The communication method 1100 of the embodiments of this application will be described in detail. Figure 13 This is a schematic interactive diagram of method 1100 of this application.

[0560] It should be understood that method 1100 is... Figure 5 The architecture diagram shown in (b) is used as an example for illustration. Method 1100 is performed by the IoT server to manage tags.

[0561] S1101, the reader has completed the registration process. For details, please refer to [link / reference needed]. Figure 3 The description.

[0562] The network can obtain reader location information, reader-to-region information mapping, or tag-to-reader mapping in different ways. Four possible solutions are described below.

[0563] Option 1: Obtain the reader's location information through a positioning process, a switching process, a tracking area update process, or a mobility registration update process.

[0564] S1102a, the AMF obtains the reader's location information or learns of changes (or updates) in the reader's location information through a positioning process, a handover process, a tracking area update process, and a mobility registration update process. In one possible implementation, the AMF can initiate a positioning process periodically. The reader's location information can be coordinates, latitude and longitude, cell identifier, tracking area identifier, registration area information, or network identifier.

[0565] Option 2 involves an inventory process where the network obtains the correspondence between tags and readers. One possible implementation is a periodic inventory process.

[0566] S1102b-1, AMF starts the timer. The function of this timer is to instruct the reader to perform an inventory count operation when the timer expires. Optionally, the AMF can periodically start this timer, or the timer can be a periodic timer.

[0567] In S1102b-2, when the timer expires, the AMF instructs the reader to perform a tag inventory process within its coverage area. In another possible implementation, the AMF does not need to execute step S1102b-1; instead, the AMF instructs the reader to perform the inventory process. Alternatively, the AMF does not need to execute step S1102b-1; instead, the AMF instructs the reader to periodically perform the inventory process. The reader starts a timer according to the instruction sent by the AMF; when the timer expires, the reader performs the inventory process. Optionally, this timer can be a periodic timer, or the reader can periodically start the timer.

[0568] One possible implementation is that the AMF sends an inventory command to the reader via an N2 message or a NAS message from the reader, instructing the reader to inventory the tags within its coverage area.

[0569] S1102b-3, the reader executes the tag inventory process according to the instructions.

[0570] S1102b-4 After the reader inventory process is completed, the inventory results, i.e. the inventory label identification, are sent to the AMF.

[0571] One possible implementation is that the reader sends the inventory results (tag identifiers) to the AMF via N2 or NAS messages.

[0572] Option 3 involves the reader sending an inventory command, including a reader identifier, during the reader-tag inventory process. This enables the tag to detect whether the reader conducting the inventory has changed and stores the reader identifier. In one possible implementation, the tag stores the reader identifier in its storage area.

[0573] S1102c-1: When the reader receives the inventory instruction, it performs a tag inventory according to the instruction.

[0574] The inventory instructions sent by the reader to the tag may include the reader's identifier.

[0575] S1102c-2, after the tags are inventoried, the tag identifier is sent to the reader. At the same time, the tag also needs to store the reader identifier included in the instruction; in one possible implementation, the tag stores the reader identifier in the tag's storage area.

[0576] S1102c-3, the reader sends the tag identifiers of the items being inventoried to the AMF.

[0577] Option 4 involves the reader sending a reader identifier to the tag, enabling the tag to determine whether the reader checking its inventory or the reader serving the tag has changed. In one possible implementation, the reader sends a broadcast message including the reader identifier. When the tag learns that the reader checking its inventory or the reader serving the tag has changed, it sends its tag identifier to the network and stores the reader identifier. In another possible implementation, the tag stores the reader identifier in its storage area.

[0578] S1102d-1, when the reader does not receive an inventory command, the reader can send a reader identifier to the tag; in one possible implementation, the reader broadcasts the reader identifier to the tag; in another possible implementation, the reader sends the reader identifier periodically; in yet another possible implementation, the reader periodically broadcasts the reader identifier.

[0579] In S1102d-2, the tag can receive a reader identifier sent by the reader. When the tag learns that the currently received reader identifier is different from the reader identifier stored in the tag, the tag sends its own identifier to the reader, and the tag stores the currently received reader identifier. In one possible implementation, the tag stores the currently received reader identifier in its storage area. The tag can store the currently received reader identifier in a different storage area than previously stored, or it can replace the previously stored reader identifier with the currently received reader identifier.

[0580] S1102d-3, the reader receives the tag identifier sent by the tag. The reader then sends the tag identifier to the AMF.

[0581] S1103, through the above methods, AMF can obtain one or more of the following information: reader location information, correspondence between reader and region information, and correspondence between tag and reader.

[0582] S1104, AMF sends one or more of the following information to the IoT server: reader location information, correspondence between reader and area information, and correspondence between tag and reader.

[0583] One possible implementation is that the AMF sends the aforementioned information to the IoT server via the NEF.

[0584] Alternatively, in method 1100, the information sent by the AMF to the IoT server can also be sent by the UPF to the IoT server. For example, after the AMF obtains the information, it sends it to the UPF via the SMF, and then the UPF sends it to the IoT server via the N6 interface. Another possible implementation is that the reader's location information, the correspondence between the reader and the area information, and the correspondence between the tag and the reader are obtained by the reader, sent to the UPF, and then sent by the UPF to the IoT server.

[0585] In this embodiment, the core network device sends one or more of the following information to the IoT server: reader location information, the correspondence between reader and area information, and the correspondence between tag and reader. This allows the IoT server to obtain the aforementioned information and manage the reader accordingly. Simultaneously, the IoT server can send this information to the operation requester (e.g., a server or an application function), enabling other servers requesting network tag operations to pre-determine the target reader for the operation, thereby reducing the signaling consumed in locating the target reader.

[0586] The above is based on and Figures 1 to 13 The inventive concept is the same as that in the method embodiments. The embodiments of this application are implemented through... Figures 14 to 15 A communication device is provided for performing the steps described in the above method embodiments. The functions can be implemented in hardware, software, or hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.

[0587] Figure 14 This is a schematic block diagram of a communication device provided in an embodiment of this application. Figure 14 As shown, the communication device 10 may include a transceiver module 11 and a processing module 12.

[0588] The transceiver module 11 can be used to receive information sent by other devices and to send information to other devices. For example, it can receive first information or send second information. The processing module 12 can be used to process the content of the device, for example, to determine a first target reader based on the first information.

[0589] In one possible design, the communication device 10 may correspond to the first core network device in the above method embodiments.

[0590] Specifically, the communication device 10 may correspond to the first core network device, UPF, or AMF in any of the methods 400 to 1100 according to the embodiments of this application. The communication device 10 may include modules for performing the operations performed by the first core network device, UPF, or AMF in the corresponding method, and each unit in the communication device 10 is for implementing the operations performed by the first core network device, UPF, or AMF in the corresponding method.

[0591] For example, when the communication device 10 corresponds to the first core network device in method 400, the transceiver module 11 is used to execute steps S401 and S402.

[0592] For example, when the communication device 10 corresponds to the UPF in method 500, the transceiver module 11 is used to execute steps S503, S506, S507, S509, and S511, and the processing module 12 is used to execute S508.

[0593] For example, when the communication device 10 corresponds to the AMF in method 600, the transceiver module 11 is used to execute steps S603, S605, and S607, and the processing module 12 is used to execute S601, S602, and S604.

[0594] For example, when the communication device 10 corresponds to the UPF in method 700, the transceiver module 11 is used to execute steps S702, S704, S706, S708, S710, and S712, and the processing module 12 is used to execute steps S701, S703, S707, and S711.

[0595] For example, when the communication device 10 corresponds to the AMF in method 800, the transceiver module 11 is used to execute steps S802, S804, S806, S808, S810, and S812, and the processing module 12 is used to execute steps S801, S803, S807, and S811.

[0596] For example, when the communication device 10 corresponds to the AMF in method 900, the transceiver module 11 is used to execute steps S903a, S903b, S905a, S905b, and S907, and the processing module 12 is used to execute steps S901, S902, and S906.

[0597] For example, when the communication device 10 corresponds to the AMF in method 1000, the transceiver module 11 is used to execute steps S1004, S1005-2, S1008, and S1009-2, and the processing module 12 is used to execute S1005-1 and S1009-1.

[0598] For example, when the communication device 10 corresponds to the AMF in method 1100, the transceiver module 11 is used to execute steps S1102b-2, S1102b-4, S1102c-4, and S1102d-3, and the processing module 12 is used to execute S1101, S1102a, S1103, and S1009-1.

[0599] Specifically, the transceiver module 11 is used to receive first information from the operation requester, the first information indicating at least one of the following: the area where the first operation is performed, and the target tag to which the first operation is performed; the processing module 12 is used to determine a first target reader based on the first information; the transceiver module 11 is also used to send second information to the first target reader, the second information being used to instruct the first target reader to perform the first operation.

[0600] In other words, the communication device provided in the fifth aspect could also be:

[0601] The transceiver module 11 is configured to receive first information from the operation requester, the first information indicating: the area where the first operation is performed and / or the target tag to which the first operation is performed; the processing module 12 is configured to determine a first target reader based on the first information; the transceiver module 11 is further configured to send second information to the first target reader based on the first information, the second information being used to instruct the first target reader to perform the first operation.

[0602] In other words, the communication device provided in the fifth aspect could also be:

[0603] The transceiver module 11 is configured to receive first information from the operation requester, the first information indicating at least one of the following: the area where the first operation is performed, the target tag to which the first operation is performed, the first information being used to identify a first target reader; the transceiver module 11 is further configured to send second information to the first target reader, the second information being used to instruct the first target reader to perform the first operation.

[0604] The above solution manages readers and tags in the passive Internet of Things through core network equipment, reducing the operation and maintenance costs of enterprises maintaining two networks simultaneously and reducing network resource consumption.

[0605] In another possible design, the communication device 10 may correspond to the Internet of Things server in the above method embodiments.

[0606] Specifically, the communication device 10 may correspond to an Internet of Things (IoT) server in any of the methods 400 to 1100 according to the embodiments of this application. The communication device 10 may include a module for performing the operations performed by the IoT server in the corresponding method. Furthermore, each unit in the communication device 10 is for implementing the operations performed by the IoT server in the corresponding method.

[0607] Specifically, the transceiver module 12 is used to receive third information from the core network device. The third information is used to indicate one or more of the following: reader identifier, reader location information, reader address information, reader port information, area information, and one or more of the correspondence between tags and readers. The area information includes the area where the first operation is performed. The transceiver module 12 is also used to send the third information to the operation requester so that the operation requester can determine the target reader for performing the first operation based on the third information.

[0608] The above scheme involves the core network equipment sending third-party information to the IoT server, enabling the IoT server to manage the readers based on this information. Simultaneously, the IoT server can send this third-party information to the operation requester, allowing the requester to identify the target reader when requesting the network to perform tag operations, thereby reducing the signaling consumed by the network in searching for or identifying the target reader.

[0609] In another possible design, the communication device 10 may correspond to the reader in the above method embodiments.

[0610] Specifically, the communication device 10 may correspond to a reader in any of the methods 400 to 1100 according to the embodiments of this application. The communication device 10 may include a module for performing the operations performed by the reader in the corresponding method, and each unit in the communication device 10 is for implementing the operations performed by the reader in the corresponding method.

[0611] Specifically, the transceiver module 12 is used to send an eighth message, which is used to indicate the reader; the transceiver module 12 is also used to receive a ninth message sent by the tag, which indicates that the tag is within the service range of the reader; the transceiver module 12 is also used to send a tenth message to the first core network device, which indicates that the tag is within the service range of the reader.

[0612] In conjunction with the sixth aspect, in some implementations of the sixth aspect, the transceiver module 12 is specifically used to send the eighth information to the tag during the first operation performed on the tag; or, the transceiver module 12 is specifically used to send the eighth information via broadcast.

[0613] The above scheme, based on the function of storing reader identifiers in tags, enables tags to know whether their location has changed or whether the reader serving the tag has changed through periodically sent messages by the reader, such as periodically sent broadcast messages. When a change occurs, the tag sends information to the network, thereby enabling the network to obtain or update the correspondence between the tag and the reader.

[0614] In another possible design, the communication device 10 may correspond to the tag in the above method embodiments.

[0615] Specifically, the communication device 10 may correspond to a tag in any of the methods 400 to 1100 according to the embodiments of this application. The communication device 10 may include a module for performing the operation performed by the tag in the corresponding method, and each unit in the communication device 10 is for implementing the operation performed by the tag in the corresponding method.

[0616] Specifically, the transceiver module 12 is used to receive a first reader identifier from the first reader; the processing module 12 is used to store the first reader identifier; the transceiver module 12 is also used to send tag information to the first reader, the tag information being used to identify the tag.

[0617] In conjunction with the seventh aspect, in some implementations of the seventh aspect, the transceiver module 12 is further configured to receive a second reader identifier; when the second reader identifier is different from the first reader identifier, the processing module 12 is further configured to store the second reader identifier, or the processing module 12 is further configured to replace the first reader identifier with the second reader identifier.

[0618] In conjunction with the seventh aspect, in some implementations of the seventh aspect, the transceiver module 12 is also used to send the tag information to the second reader.

[0619] The above scheme, based on the tag's ability to store reader identifiers, allows tags to know whether their location has changed or whether the reader serving the tag has changed by periodically sending messages, such as periodically broadcast messages. Furthermore, for tags whose location or the reader serving them has not changed, they do not need to send their own identification information, thus reducing signaling overhead.

[0620] Figure 15 This is a schematic diagram of the communication device 20 provided in an embodiment of this application.

[0621] In one possible design, the device 20 can be a first core network device, or a chip or chip system located on the first core network device.

[0622] The device 20 may include a processor 21 (i.e., an example of a processing module) and a memory 22. The memory 22 is used to store instructions, and the processor 21 is used to execute the instructions stored in the memory 22 to cause the device 20 to perform, for example... Figures 6 to 13 The steps performed by the device in the various possible designs described above are corresponding to the methods described above.

[0623] Furthermore, the device 20 may also include an input port 23 (i.e., an example of a transceiver module) and an output port 24 (i.e., another example of a transceiver module). Furthermore, the processor 21, memory 22, input port 23, and output port 24 can communicate with each other through internal connection paths to transmit control and / or data signals. The memory 22 is used to store computer programs, and the processor 21 can be used to call and run the computer programs from the memory 22 to control the input port 23 to receive signals and control the output port 24 to send signals, thus completing the steps of the terminal device, wireless access network device, UE, or base station in the above method. The memory 22 may be integrated into the processor 21 or may be disposed separately from the processor 21.

[0624] Optionally, if the message transmission device 20 is a communication device, the input port 23 is a receiver, and the output port 24 is a transmitter. The receiver and transmitter can be the same or different physical entities. When they are the same physical entity, they can be collectively referred to as transceivers.

[0625] Optionally, if the device 20 is a chip or circuit, the input port 23 is an input interface and the output port 24 is an output interface.

[0626] As one implementation method, the functions of input port 23 and output port 34 can be implemented using transceiver circuits or dedicated transceiver chips. Processor 21 can be implemented using dedicated processing chips, processing circuits, processors, or general-purpose chips.

[0627] As another implementation method, the device provided in the embodiments of this application can be implemented using a general-purpose computer. The program code that implements the functions of processor 21, input port 23 and output port 24 is stored in memory 22, and the general-purpose processor implements the functions of processor 21, input port 23 and output port 24 by executing the code in memory 22.

[0628] Each module or unit in device 20 can be used to perform the actions or processes performed by the device (e.g., terminal device) that performs random access in the above method. Here, to avoid redundancy, its detailed description is omitted.

[0629] For the concepts, explanations, detailed descriptions, and other steps related to the technical solutions provided in the embodiments of this application involved in the device 20, please refer to the descriptions of these contents in the foregoing methods or other embodiments, which will not be repeated here.

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

[0631] This application also provides a computer-readable storage medium storing computer instructions for implementing the method executed by the first core network device in the above method embodiments.

[0632] For example, when the computer program is executed by the computer, it enables the computer to implement the method executed by the first core network device in the above method embodiments.

[0633] This application also provides a computer-readable storage medium storing computer instructions for implementing the method executed by the first core network device in the above method embodiments.

[0634] For example, when the computer program is executed by the computer, it enables the computer to implement the method executed by the first core network device in the above method embodiments.

[0635] It should also be understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0636] The above embodiments can be implemented, in whole or in part, by software, hardware, firmware, or any other combination thereof. When implemented using software, the above embodiments can be implemented, in whole or in part, as a computer program product. This computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer program are loaded or executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more sets of available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium. A semiconductor medium can be a solid-state drive.

[0637] In this application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0638] It should be understood that the term "and / or" in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0639] It should be understood that in the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0640] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative; for example, the division of units is merely a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interface, device or unit, and can be electrical, mechanical or other forms.

[0641] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs. Furthermore, the functional units in the various embodiments of this application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. If the function is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, mobile hard drives, ROM, RAM, magnetic disks, or optical disks.

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

Claims

1. A communication method, characterized in that, include: The first core network device receives first information from the operation requester, the first information being used to determine the first target reader, and the first information also indicating at least one of the following: the area where the first operation is performed, and the target tag to which the first operation is performed; The first core network device sends second information to the first target reader based on the first information, the second information being used to instruct the first target reader to perform the first operation; Wherein, the first information indicates the area where the first operation is performed, and the method further includes: The first core network device determines the first target reader based on the area where the first operation was performed and the third information. The third information includes one or more of the following: reader identification information, reader location information, reader group identification information, reader address information, or reader port information, or... The first core network device sends the area of ​​the first operation to the second core network device; The first core network device receives the identifier of the first target reader from the second core network device. The identifier of the first target reader is determined by the second core network device based on the area where the first operation is performed and third information. The third information includes one or more of the following: reader identification information, reader location information, reader group identification information, reader address information, or reader port information. or, Wherein, the first information indicates the target label to which the first operation is performed, and the method further includes: The first core network device determines the first target reader based on the target tag to which the first operation was performed and a first correspondence, wherein the first correspondence includes the correspondence between the target tag and the reader information of the first target reader, or... The first core network device sends the target tag of the first operation to the second core network device; The first core network device receives the identifier of the first target reader from the second core network device. The identifier of the first target reader is determined by the second core network device based on the target tag of the first operation and a first correspondence relationship. The first correspondence relationship includes the correspondence between the target tag and the reader information of the first target reader.

2. The method according to claim 1, characterized in that, The third information is pre-configured, or the third information is received from a control plane device, which includes any one of the following devices: a mobility management device, a session management device, a policy control device, a unified data management device, or a user database.

3. The method according to claim 1, characterized in that, The method further includes: The first core network device sends the third information to the Internet of Things server.

4. The method according to any one of claims 1 to 3, characterized in that, The first target reader includes one or more readers, and the multiple readers belong to a first reader group; or the multiple readers have the same location information.

5. The method according to claim 1, characterized in that, The method further includes: The first core network device determines that the first target reader has failed to execute the first operation; The first core network device sends the second information to the second target reader, the second information being used to instruct the second target reader to perform the first operation.

6. The method according to claim 5, characterized in that, The method further includes: The first core network device receives a fifth message from the second target reader, the fifth message indicating that the second target reader has successfully executed the first operation; The first core network device updates the first correspondence relationship according to the fifth information, so that the first correspondence relationship includes the correspondence between the target tag to which the first operation is performed and the reader information of the second target reader.

7. The method according to claim 5 or 6, characterized in that, The second target reader includes one or more readers, which belong to a second reader group; or the multiple readers have the same location information.

8. The method according to any one of claims 1, 5 to 6, characterized in that, The reader information includes one or more of the following: reader identification information, reader location information, reader address information, reader port information, and reader group identification information.

9. The method according to any one of claims 1, 5 to 6, characterized in that, The first correspondence is pre-configured. Alternatively, the method may further include: The first core network device obtains the first correspondence.

10. The method according to claim 9, characterized in that, When the first core network device is a user plane device, the first core network device obtains the first correspondence, including: The first core network device receives the first correspondence from the mobility management device.

11. The method according to claim 9, characterized in that, The first core network device obtains the first correspondence, including: The first core network device sends a sixth message to one or more readers, so that the one or more readers perform a second operation on the tags within the coverage area based on the sixth message; The first core network device receives seventh information from the one or more readers, the seventh information being used to identify some or all of the tags within the coverage area, the some or all of the tags including the target tag, and the one or more readers including the first target reader; The first core network device obtains the first correspondence relationship based on the seventh information and the one or more readers; or, The first core network device sends second information to the one or more readers, the second information being used to instruct the one or more readers to perform the first operation on the target tag, the one or more readers including the first target reader; The first core network device receives a seventh message from the one or more readers, the seventh message indicating that the one or more readers have successfully executed the first operation; The first core network device obtains the first correspondence relationship based on the seventh information.

12. The method according to claim 10 or 11, characterized in that, The method further includes: The first core network device sends the first correspondence to the IoT server.

13. The method according to any one of claims 1 to 3, 5 to 6, and 10 to 11, characterized in that, The first operation includes one or more of the following operations: obtaining tag information, inventory operation, read operation, write operation, failure operation, sending load to the tag, and message interaction operation with the tag.

14. The method according to claim 1, characterized in that, The location information of the reader includes one or more of the following: cell identifier, tracking area identifier, registration area information, network identifier, coordinate value information, and latitude and longitude information.

15. A communication device, characterized in that, include: The transceiver module is configured to receive first information from the operation requester, the first information being used to determine a first target reader, and the first information further indicating at least one of the following: the area where the first operation is performed, and the target tag to which the first operation is performed; The transceiver module is further configured to send second information to the first target reader based on the first information, wherein the second information is used to instruct the first target reader to perform the first operation; Wherein, the first information indicates the area where the first operation is performed, and the device further includes: a processing module, the processing module being configured to determine the first target reader based on the area where the first operation is performed and third information, the third information including one or more of the following: reader identification information, reader location information, reader group identification information, reader address information, or reader port information, or... The transceiver module is also used to send the area of ​​the first operation to the second core network device; The transceiver module is further configured to receive the identifier of the first target reader from the second core network device. The identifier of the first target reader is determined by the second core network device based on the area where the first operation is performed and the third information. The third information includes one or more of the following: reader identifier information, reader location information, reader group identifier information, reader address information, or reader port information. or, The first information indicates the target tag to which the first operation is performed. The device further includes a processing module, which is configured to determine the first target reader based on the target tag to which the first operation is performed and a first correspondence, wherein the first correspondence includes a correspondence between the target tag and reader information of the first target reader. or, The transceiver module is also used to send the target tag of the first operation to the second core network device; The transceiver module is further configured to receive the identifier of the first target reader from the second core network device. The identifier of the first target reader is determined by the second core network device based on the target tag of the first operation and a first correspondence relationship. The first correspondence relationship includes the correspondence between the target tag and the reader information of the first target reader.

16. The apparatus according to claim 15, characterized in that, The third information is pre-configured, or the third information is received from a control plane device, which includes any one of the following devices: a mobility management device, a session management device, a policy control device, a unified data management device, or a user database.

17. The apparatus according to claim 15, characterized in that, The transceiver module is also used to send the third information to the IoT server.

18. The apparatus according to any one of claims 15 to 17, characterized in that, The first target reader includes one or more readers, and the multiple readers belong to a first reader group; or the multiple readers have the same location information.

19. The apparatus according to claim 17, characterized in that, The processing module is further configured to determine that the first target reader has failed to execute the first operation; The transceiver module is further configured to send the second information to the second target reader, the second information being used to instruct the second target reader to perform the first operation.

20. The apparatus according to claim 19, characterized in that, The transceiver module is further configured to receive fifth information from the second target reader, the fifth information indicating that the second target reader has successfully executed the first operation; The processing module is further configured to update the first correspondence relationship according to the fifth information, so that the first correspondence relationship includes the correspondence between the target tag to which the first operation is performed and the reader information of the second target reader.

21. The apparatus according to claim 19 or 20, characterized in that, The second target reader includes one or more readers, which belong to a second reader group; or the multiple readers have the same location information.

22. The apparatus according to any one of claims 17, 19 to 20, characterized in that, The reader information includes one or more of the following: reader identification information, reader location information, reader address information or reader port information, and reader group identification information.

23. The apparatus according to any one of claims 17, 19 to 20, characterized in that, The first correspondence is pre-configured. Alternatively, the device may further include: The acquisition module is used to acquire the first correspondence.

24. The apparatus according to claim 23, characterized in that, When the device is a user plane device, the acquisition module is specifically used to acquire the first correspondence relationship, including: Receive the first mapping relationship from the mobile management device.

25. The apparatus according to claim 23, characterized in that, The transceiver module is also configured to send a sixth message to one or more readers, so that the one or more readers perform a second operation on the tags within the coverage area based on the sixth message; The transceiver module is further configured to receive seventh information from the one or more readers, the seventh information being used to identify some or all of the tags within the coverage area, the some or all of the tags including the target tag, and the one or more readers including the first target reader; The processing module is further configured to obtain the first correspondence relationship based on the seventh information and the one or more readers; or, The transceiver module is further configured to send second information to the one or more readers, the second information being used to instruct the one or more readers to perform the first operation on the target tag, the one or more readers including the first target reader; The transceiver module is further configured to receive a seventh message from the one or more readers, the seventh message indicating that the one or more readers have successfully executed the first operation; The processing module is further configured to obtain the first correspondence relationship based on the seventh information.

26. The apparatus according to claim 24 or 25, characterized in that, The device further includes: The transceiver module is also used to send the first correspondence relationship to the IoT server.

27. The apparatus according to any one of claims 15 to 17, 19 to 20, and 24 to 25, characterized in that, The first operation includes one or more of the following operations: obtaining tag information, inventory operation, read operation, write operation, failure operation, sending load to the tag, and message interaction operation with the tag.

28. The apparatus according to claim 15, characterized in that, The location information of the reader includes one or more of the following: cell identifier, tracking area identifier, registration area information, network identifier, coordinate value information, and latitude and longitude information.

29. A communication device, characterized in that, include: Processor and memory; The memory is used to store computer programs; The processor is configured to execute a computer program stored in the memory, so that the communication device performs the communication method according to any one of claims 1 to 14.

30. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when run on a computer, causes the computer to perform the communication method as described in any one of claims 1 to 14.

31. A chip system, characterized in that, include: A processor for retrieving and running a computer program from memory, causing a communication device on which the chip system is installed to perform the communication method as described in any one of claims 1 to 14.

Images