Communication method, communication device, and communication system

Abstract

The application relates to a communication method, a communication device and a communication system, which belong to the technical field of communication. In response to a subscription request message and a subscription information change message of a source tag management function successively, a center data management function determines first subscription information and second subscription information, the first subscription information comprises identification information of a tag and identification information of a source data management function, the second subscription information comprises identification information of the tag and identification information of a destination data management function, and the center data management function sends the second subscription information to the destination data management function, the destination data management function is a data management function of a flow transfer destination of the tag, and the source data management function is a data management function of a subscription place of the tag. Since the center data management function executes a subscription process and sends subscription information to the destination data management function, the center data management function supports synchronization of subscription information of the tag through one subscription process, thereby reducing the complexity of a synchronization process of the subscription information of the tag in a flow transfer scene of the tag.

Description

Technical Field

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

[0002] Passive Internet of Things (IoT) refers to IoT terminals (such as sensors, tags, etc.) that do not have their own power supply, but obtain the power needed to drive the operation of IoT terminals by collecting energy from the surrounding environment (such as the energy of radio frequency signals, ambient heat, etc.).

[0003] With the technological development of passive IoT and environmental protection requirements, tags in passive IoT will be widely used. In production application scenarios, a large number of tags will be transferred, for example, tags will move from location A to location B. In the tag transfer scenario, in order to synchronize the tag's contract information, the data management functions at both the tag's contract location and the tag's destination need to perform a contract process for the tag. For example, the data management function at location A first performs a contract process for the tag to obtain the tag's contract information. Then, the tag moves from location A to location B, and the data management function at location B then performs a contract process for the tag to obtain the tag's contract information.

[0004] In tag circulation scenarios, the tag needs to undergo a signing process in both the data management functions at the signing location and the data management functions at the circulation destination, which makes the synchronization process of tag signing information overly complex. Therefore, how to reduce the complexity of the tag signing information synchronization process in tag circulation scenarios is a pressing technical problem that needs to be solved. Summary of the Invention

[0005] This application provides a communication method, communication device, and communication system that can reduce the complexity of the synchronization process of tag contract information in tag circulation scenarios.

[0006] The communication method described in the first aspect is executed by a central data management function. The central data management function can be a physical entity or a logical concept, such as a logical node, logical module, or logical software. In other words, this application does not limit the specific implementation form of the central data management function.

[0007] Firstly, a communication method is provided, in which a central data management function successively receives a signing request message and a signing information change message from a source tag management function. The signing request message is used to request the central data management function to sign a tag, and includes the tag's identification information and the identification information of the source data management function. The source data management function is the data management function of the tag's signing location, and the source tag management function is the tag management function of the tag's signing location, used to manage the tag. The signing information change message includes the identification information of the destination data management function and the tag's identification information, and the destination data management function is the data management function of the tag's transit destination. The central data management function determines the tag's first signing information based on the signing request message and determines the tag's second signing information based on the signing information change message. The first signing information includes the tag's identification information and the source data management function's identification information, and the second signing information includes the tag's identification information and the destination data management function's identification information. The central data management function sends the second signing information to the destination data management function.

[0008] In the above method, the central data management function executes the tag signing process and the signing information modification process. Specifically, the central data management function completes the tag signing process in response to the signing request message, that is, the central data management function determines the tag's first signing information based on the signing request message. Furthermore, the central data management function completes the tag's signing information modification process in response to the signing information modification message, that is, the central data management function determines the tag's second signing information based on the signing information modification message. Afterwards, the central data management function sends the tag's second signing information to the destination data management function.

[0009] The central data management function can both execute the tag signing process and send tag signing information to the destination data management function. This reduces the number of signing processes, thereby lowering the complexity of synchronizing tag signing information in tag circulation scenarios. In other words, the above method can achieve tag signing information synchronization with a single signing process. Compared to existing solutions where both source and destination data management functions require tag signing processes, this method reduces the complexity of synchronizing tag signing information in tag circulation scenarios by minimizing the number of signing processes.

[0010] In some implementations of the first aspect, the central data management function sends second contract information to the destination data management function, including: the central data management function responding to a first contract information request message from the source tag management function, sending the second contract information to the destination data management function. The first contract information request message requests the central data management function to send the contract information of the tag to the destination data management function, and the first contract information request message includes the identification information of the tag and the identification information of the destination data management function. Thus, the central data management function can respond to a request from the source tag management function to send the second contract information to the destination data management function. This method also reduces the complexity of the central data management function; for example, the central data management function does not need to determine the timing of sending the second contract information to the destination data management function.

[0011] In some implementations of the first aspect, the method further includes: the central data management function sending a first address request message to the warehousing function, the first address request message being used to request address information of the target data management function, the first address request message including identification information of the target data management function; and the central data management function receiving the address information of the target data management function from the warehousing function. Through the above method, the central data management function can obtain the address information of the target data management function through the warehousing function, thereby enabling the central data management function to send second contract information to the target data management function.

[0012] In some implementations of the first aspect, the central data management function sends second contract information to the target data management function, including: the central data management function receiving a second contract information request message from the target data management function, the second contract information request message being used to request the contract information of the tag, and the second contract information request message including the tag's identification information; the central data management function sending the second contract information to the target data management function according to the second contract information request message. In this way, the central data management function can respond to the request of the target data management function by sending the second contract information to the target data management function, which can support the target data management function actively requesting and obtaining the tag's contract information. Through the above method, this can also reduce the complexity of the central data management function; for example, the central data management function does not need to determine the timing of sending the second contract information to the target data management function.

[0013] In some implementations of the first aspect, the method further includes: the destination data management function sending a second address request message to the warehousing function, the second address request message being used to request address information of the central data management function, the second address request message including the identification information of the tag; and the destination data management function receiving the address information from the central data management function of the warehousing function. Through the above method, the destination data management function can obtain the address information of the central data management function through the warehousing function, thereby enabling the destination data management function to send a second contract information request message to the central data management function.

[0014] In some implementations of the first aspect, the method further includes: the central data management function receiving a third contract information request message from the source tag management function, the third contract information request message being used to request the central data management function to send the contract information of the tag to the source data management function, the third contract information request message including the identification information of the tag and the identification information of the source data management function; the central data management function sending a third address request message to the warehousing function, the third address request message being used to request the address information of the source data management function, the third address request message including the identification information of the source data management function; the central data management function receiving the address information of the source data management function from the warehousing function; and the central data management function sending first contract information to the source data management function according to the third contract information request message. Thus, after receiving the third contract information request message, the central data management function requests the address information of the source data management function from the warehousing function according to the identification information of the source data management function carried in the third contract information request message, and sends the first contract information to the source data management function according to the address information of the source data management function. This method can also reduce the complexity of the central data management function; for example, the central data management function does not need to determine the timing of sending the first contract information to the source data management function.

[0015] In some implementations of the first aspect, the method further includes: the source data management function sending a fourth address request message to the warehousing function, the fourth address request message requesting address information from the central data management function, the fourth address request message including the tag's identification information; the source data management function receiving the address information from the central data management function of the warehousing function; the central data management function receiving a fourth contract information request message from the source data management function, the fourth contract information request message requesting contract information for the tag, the fourth contract information request message including the tag's identification information; and the central data management function sending first contract information to the source data management function. Thus, the central data management function can respond to a request from the source data management function by sending first contract information to the source data management function, which supports the source data management function actively requesting and obtaining the tag's contract information. This method also reduces the complexity of the central data management function; for example, the central data management function does not need to determine the timing of sending the first contract information to the destination data management function.

[0016] In some implementations of the first aspect, the contract information change message also includes the identification information of the source data management function. The method further includes: the central data management function sending a fifth address request message to the warehouse function, the fifth address request message requesting the address information of the source data management function, and the fifth address request message including the identification information of the source data management function; the central data management function receiving the address information of the source data management function from the warehouse function; and the central data management function sending a contract information deletion message to the source data management function, the contract information deletion message requesting the source data management function to delete the contract information of the tag, the contract information request message including the identification information of the tag. When the contract information change message also includes the identification information of the source data management function, the central data management function requests the address information of the source data management function from the warehouse function based on the identification information of the source data management function in the contract information change message. Furthermore, since the identification information of the source data management function can be obtained through the contract information change message without needing to obtain it through the first contract information, the central data management function can delete the first contract information after generating the second contract information, thereby freeing up the storage space of the central data management function. Once the destination data management function obtains the second contract information, the source data management function no longer needs to store the first contract information. The central data management function can instruct the source data management function to delete the first contract information, thereby freeing up the storage space of the source data management function.

[0017] In some implementations of the first aspect, the subscription request message also includes the tag's authentication key, the first subscription information also includes the tag's authentication key, and the second subscription information also includes the tag's authentication key. The source data management function or the destination data management function can perform an authentication process for the tag based on this authentication key. Simultaneously, the tag's authentication key can be used for two-way authentication between the tag and the network, ensuring the confidentiality and integrity of data and sessions. When the subscription request message also includes the tag's authentication key, the central data management function does not need to generate the tag's authentication key, thereby reducing the functional complexity of the central data management function.

[0018] In a second aspect, a communication system is provided, which includes a central data management function and a source tag management function, the central data management function and the source tag management function being used to perform the methods described in the first aspect and any possible implementation thereof.

[0019] Thirdly, a communication system is provided, which includes a central data management function and a destination data management function, the central data management function and the destination data management function being used to perform the method described in the first aspect and any possible implementation thereof.

[0020] For further description of the communication systems described in the second and third aspects, please refer to the relevant descriptions in the first aspect above, which will not be repeated here.

[0021] Fourthly, a communication device is provided, which can be a central data management function, or a device or module for performing the central data management function.

[0022] One possible implementation is that the communication device may include modules or units corresponding to the methods / operations / steps / actions described in the first aspect and any possible implementation of the first aspect. These modules or units may be hardware circuits, software, or a combination of hardware circuits and software.

[0023] For example, the communication device includes a transceiver unit and a processing unit.

[0024] Fifthly, a communication device is provided, including a processor configured to, by executing a computer program or instructions, or by logic circuitry, cause the communication device to perform the method described in the first aspect and any possible implementation thereof.

[0025] In one possible implementation, the communication device also includes a memory for storing the computer program or instructions.

[0026] In one possible implementation, the communication device also includes a communication interface for inputting and / or outputting signals.

[0027] A sixth aspect provides a communication device including logic circuitry and an input / output interface for inputting and / or outputting signals, the logic circuitry being configured to perform the method described in the first aspect and any possible implementation thereof.

[0028] In a seventh aspect, a computer-readable storage medium is provided, on which a computer program or instructions are stored, which, when executed on a computer, cause the first aspect and any possible implementation thereof to be performed.

[0029] Eighthly, a computer program product is provided, comprising instructions that, when executed on a computer, cause the first aspect and any possible implementation thereof, and the method thereof, to be performed.

[0030] A ninth aspect provides a chip or chip system comprising: one or more processors for executing computer programs or instructions in the memory, such that the chip or chip system implements the methods of the first aspect and any possible implementation thereof.

[0031] In a tenth aspect, a chip is provided, which is installed in a communication device. The chip includes a processor and a communication interface. The processor reads and executes instructions through the communication interface, causing the communication device to perform the methods as described in the first aspect and any possible implementation thereof.

[0032] Optionally, the aforementioned chip can also be understood as a communication device.

[0033] For a description of the beneficial effects of any of the second to tenth aspects, please refer to the description of the beneficial effects of the first aspect, which will not be repeated here. Attached Figure Description

[0034] Figure 1 This is a schematic diagram of the architecture of a first type of communication system applicable to embodiments of this application.

[0035] Figure 2 This is a schematic diagram of the network architecture used in the two communication systems shown in the embodiments of this application.

[0036] Figure 3 This is a schematic diagram of the interaction flow of a communication method according to an embodiment of this application.

[0037] Figure 4 This is a schematic diagram of the interaction flow of another communication method according to an embodiment of this application.

[0038] Figure 5 This is a schematic block diagram of a communication device according to an embodiment of this application.

[0039] Figure 6 This is a schematic block diagram of another communication device according to an embodiment of this application. Detailed Implementation

[0040] To facilitate understanding of the embodiments of this application, the following points will be explained first.

[0041] 1. Unless otherwise stated, "multiple" means two or more. "At least one" means "one or more".

[0042] 2. Unless otherwise specified or in case of logical conflict, the terms and / or descriptions in different embodiments of this application are consistent and can be referenced in each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0043] III. The various numerical designations used in this application are merely for descriptive convenience and are not intended to limit the scope of protection of this application. The magnitude of the serial numbers used in this application does not imply a sequential order of execution; the execution order of each process should be determined by its function and internal logic. For example, the terms "first (as in the first contract information below)", "second (as in the second contract information below)", and other various terminology (if present) in the specification, claims, and drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. Where such data is used, it can be interchanged where appropriate so that the embodiments described herein can be implemented in a sequence other than that illustrated or described herein.

[0044] Furthermore, any embodiment or design described in this application as "exemplary" or "for example" should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner for ease of understanding.

[0045] IV. The terms “comprising” and “having” and any variations thereof are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are expressly listed, but may include other steps or units that are not expressly listed or that are inherent to such process, method, product or device.

[0046] V. In this application, "for indicating" can be understood as "enabling", and "enabling" includes direct enabling and indirect enabling. When describing information for enabling A, it may include whether the information directly enables A or indirectly enables A, but it does not mean that the information necessarily carries A.

[0047] The information that enables the information is called the information to be enabled. In the specific implementation process, there are many ways to enable the information to be enabled, such as, but not limited to, directly enabling the information to be enabled, such as the information to be enabled itself or its index. It can also be indirectly enabled by enabling other information, where there is a relationship between the other information and the information to be enabled. It can also enable only a part of the information to be enabled, while the other parts are known or pre-agreed upon. For example, enabling specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement of various pieces of information, thereby reducing enabling overhead to some extent. Simultaneously, common parts of various pieces of information can be identified and enabled uniformly to reduce the enabling overhead caused by individually enabling the same information.

[0048] In addition, "instruction" can include direct instruction, indirect instruction, explicit instruction, and implicit instruction. When describing a certain instruction information to indicate A, it can be understood that the instruction information carries A, directly indicates A, or indirectly indicates A.

[0049] In this application, the information indicated by the instruction information is called the information to be instructed. In specific implementations, there are many ways to indicate the information to be instructed, such as, but not limited to, directly indicating the information to be instructed, such as the information to be instructed itself or its index. It can also indirectly indicate the information to be instructed by indicating other information, where there is a relationship between the other information and the information to be instructed. It can also indicate only a part of the information to be instructed, while the other parts are known or pre-agreed upon. For example, the instruction of specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement of various pieces of information, thereby reducing instruction overhead to some extent. Furthermore, the information to be instructed can be sent as a whole or divided into multiple sub-information pieces, and the sending period and / or timing of these sub-information pieces can be the same or different.

[0050] VI. The term "storage" or "preservation" in this application can refer to storage in one or more memory devices. These memory devices can be separately configured or integrated into an encoder, decoder, processor, or communication device. Alternatively, some memory devices can be separately configured, while others can be integrated into a decoder, processor, or communication device. The type of memory can be any form of storage medium, and this is not limited.

[0051] VII. The arrows or boxes indicated by dashed lines in the schematic diagrams in the accompanying drawings of this application represent optional steps or optional modules.

[0052] 8. In this application, "send" and "receive" indicate the direction of signal transmission. For example, "send information to XX" can be understood as the destination of the information being XX, which may include direct transmission via the air interface or indirect transmission by other units or modules via the air interface. "Receive information from YY" can be understood as the source of the information being YY, which may include direct reception from YY via the air interface or indirect reception from YY by other units or modules via the air interface. "Send" can also be understood as the "output" of the chip interface, and "receive" can also be understood as the "input" of the chip interface. In other words, sending and receiving can occur between devices, such as between network devices and terminal devices, or within a device, such as between components, modules, chips, software modules, or hardware modules within the device via a bus, wiring, or interface.

[0053] The following sections describe the communication system, communication method, and communication device.

[0054] This application provides two communication systems: a first communication system and a second communication system. The first communication system includes central data management functions and source tag management functions, while the second communication system includes central data management functions and destination data management functions. A description of the first communication system can be found here. Figure 1 The description of the first communication system below also applies to the second communication system. For the sake of brevity, the following description mainly focuses on the first communication system.

[0055] Figure 1 This is a schematic diagram of the architecture of a first type of communication system applicable to embodiments of this application. (Reference) Figure 1 The first type of communication system includes: central data management function and source tag management function.

[0056] Optionally, the first communication system may also include destination data management functionality.

[0057] Optionally, the first communication system may also include source data management functionality.

[0058] Optionally, the first communication system may also include warehousing functionality.

[0059] Optionally, the first communication system may also include destination tag management functionality.

[0060] Optionally, the first communication system may also include one or more tags ( Figure 1 (Not shown in the text) When one or more of the aforementioned tags are located in the contracting location, the source tag management function manages or controls the aforementioned one or more tags. When one or more of the aforementioned tags are transferred from the contracting location to the transfer destination, the destination tag management function manages or controls the aforementioned one or more tags.

[0061] exist Figure 1 In the first communication system shown, the central data management function can interact with multiple data management functions, which can be located in different domains.

[0062] exist Figure 1 In the first communication system shown, the source tag management function, source data management function, destination data management function, warehousing function, and destination tag management function can all interact with the central data management function. The source tag management function can interact with the source data management function, the destination tag management function can interact with the destination data management function, and both the source and destination data management functions can interact with the warehousing function. Specifically, when the central data management function interacts with either the source or destination data management function, the central data management function can obtain the address information of either the source or destination data management function through the warehousing function; alternatively, the central data management function may have pre-configured the address information of either the source or destination data management function. Similarly, when either the source or destination data management function interacts with the central data management function, the source or destination data management function can obtain the address information of the central data management function through the warehousing function; alternatively, the source or destination data management function may have pre-configured the address information of the central data management function. Alternatively, the central data management function, the source data management function, and the destination data management function can all determine the address information of the peer with which they are communicating.

[0063] exist Figure 1 In the first communication system shown, the term "source" can be understood as a concept related to the contracting location of a tag. For example, a source data management function can be understood as a data management function of the tag's contracting location, and a source tag management function can be understood as a tag management function of the tag's contracting location. The contracting location of a tag can include one or more source data management functions, and the contracting location of a tag can include one or more source tag management functions.

[0064] exist Figure 1In the first communication system shown, the term "destination" can be understood as a concept related to the destination of the tag's movement. For example, the destination data management function can be understood as the data management function of the tag's destination, and the destination tag management function can be understood as the tag management function of the tag's destination. The destination of the tag's movement may include one or more destination data management functions, and the destination of the tag's movement may include one or more destination tag management functions.

[0065] The central data management function is the data management function for tags in the environmental Internet of Things (IoT). It is used to uniformly manage, store, and execute tag signing functions. For example, each tag can sign a contract at the central data management function. This signing can also be understood as opening an account; that is, the source data management function requests the central data management function to sign a tag, or it can be understood as the source data management function requesting the central data management function to open an account for the tag. Correspondingly, the central data management function can store or generate the tag's signing information. Furthermore, the central data management function can also be replaced with other terms, such as core data management function, global data management function, or central data management function, etc., without limitation.

[0066] Tag management functions (regardless of source or destination) can be used to manage tags. For example, tag management functions can initiate tag signing processes, tag inventory processes, and tag read / write processes. Tag management functions can include different entities, such as application functions (AF), Internet of Things (IoT) entities, ambient power-enabled Internet of Things tag management functions (AIOTF), or business operation support systems (BOSS). Source tag management functions can include source AF, source IoT, source AIOTF, or source BOSS. Destination tag management functions can include destination AF, destination IoT, destination AIOTF, or destination BOSS. IoT or BOSS is responsible for initiating tag signing processes, AF is responsible for initiating tag inventory and read / write processes, and AIOTF is responsible for processing tag processing requests received from the core network side. Additionally, tag management functions can be replaced with other terms, such as tag control functions or tag management platforms, without limitation. Optionally, AF or AIOTF can also be used to initiate the tag signing process, without limitation.

[0067] Both source data management and destination data management functions can be used to store or manage tag contract information. For example, source data management can store data from tags located at the contracting location, including the tag's contract information; similarly, destination data management can store data from tags located at the transit destination, also including the tag's contract information. One example of a source or destination data management function is ambient power-enabled internet of things data management (ADM). However, source or destination data management functions can be replaced with other terms, such as local data management or sub-data management, without limitation.

[0068] Tags can also be referred to as environmental IoT devices, terminals, access terminals, user units, user stations, mobile stations, mobile stations, remote terminals, mobile devices, user terminals, wireless communication devices, user agents, user devices, or target terminals. A terminal can be a passive IoT terminal or a tag. Terminals can be passive devices, which can be passive tags. Passive tags can collect energy through backscattering technology to transmit and receive messages. Passive tags include, but are not limited to, radio frequency identification (RFID), Bluetooth, Zigbee, and other power-free terminal tags. Terminals can also be semi-passive or active devices. An active device is a device with wireless transceiver capabilities, such as a mobile phone, a computer with wireless transceiver capabilities, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in autonomous driving, a wireless terminal in remote medical care, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, in-vehicle equipment, wearable devices, and fifth-generation communication systems (5G).th Terminals in 5G (generation, 5G) mobile communication systems or terminals in future evolved networks, etc.

[0069] Wearable devices, also known as wearable smart devices, are a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not merely hardware devices; they achieve powerful functions through software support and data or cloud interaction. Broadly defined, wearable smart devices include those with comprehensive functions, large sizes, and the ability to perform complete or partial functions without relying on a smartphone, such as smartwatches or smart glasses. They also include devices focused on a specific application function that require the use of other devices, such as smart bracelets and smart jewelry for vital sign monitoring.

[0070] A repository function stores registration information for functions. For example, it can store the address and identification information of a function and establish a mapping between these two information. In other words, the registration information for a function includes its address and identification information. Alternatively, a function can register with a repository function. For instance, a function can store both its identification and address information in the repository. The repository function can then respond to query requests from certain functions by sending the address information of the functions it requests to communicate with, thereby supporting information exchange between functions. An example of a repository function could be the network repository function (NRF) in a 5G core network, or an entity in a future communication network that is the same as or similar to an NRF function.

[0071] exist Figure 1 In the first communication system shown, one or more of the central data management function, source tag management function, destination data management function, source data management function, warehousing function, and destination tag management function can be physical entities or logical concepts, and there is no limitation in this regard. Furthermore, the embodiments of this application do not specifically limit the deployment method or location of the above functions, and can be flexibly designed according to specific application scenarios.

[0072] Figure 1 In this process, the central data management function, source tag management function, and destination data management function can exchange information in the following ways:

[0073] The source tag management function sends a contract request message to the central data management function. This message requests the central data management function to sign a contract for the tag. The contract request message includes the tag's identification information and the source data management function's identification information. The central data management function receives the contract request message and determines the tag's initial contract information based on it. This initial contract information includes the tag's identification information and the source data management function's identification information.

[0074] The source tag management function also sends a contract information change message to the central data management function. This message requests the central data management function to modify the tag's contract information. The contract information change message includes the identifier information of the destination data management function and the tag's identifier information. The central data management function receives the contract information change message and determines the tag's second contract information based on it. This second contract information includes the tag's identifier information and the identifier information of the destination data management function.

[0075] The central data management function sends the second contract information to the destination data management function. The destination data management function receives the second contract information.

[0076] In this embodiment of the application, the central data management function determines the first contract information based on the contract request message, which can be interpreted in various ways. For example, the central data management function may rename the contract request message to the first contract information. Or, the central data management function may set the identification information of the tag carried in the contract request message and the identification information of the source data management function into the new information, which can be understood as the first contract information.

[0077] In this embodiment, the central data management function determines the second contract information based on the contract information change message, which can be interpreted in several ways. For example, the central data management function renames the contract information change message to the second contract information; or, the central data management function sets the tag identification information and the target data management function identification information carried in the contract information change message into new information, which can be understood as the second contract information; or, the central data management function renames the first contract information to the second contract information and replaces the source data management function identification information in the first contract information with the target data management function identification information; or, the central data management function replaces the source data management function identification information in the first contract information with the target data management function identification information based on the contract information change message, thereby obtaining the second contract information.

[0078] In the above method, the central data management function executes the tag signing process and the signing information modification process. Specifically, the central data management function completes the tag signing process in response to the signing request message, that is, the central data management function determines the tag's first signing information based on the signing request message. Furthermore, the central data management function completes the tag's signing information modification process in response to the signing information modification message, that is, the central data management function determines the tag's second signing information based on the signing information modification message. Afterwards, the central data management function sends the tag's second signing information to the destination data management function.

[0079] The central data management function can both execute the tag signing process and send tag signing information to the destination data management function. This reduces the number of signing processes, thereby lowering the complexity of synchronizing tag signing information in tag circulation scenarios. In other words, the above method can support the synchronization of tag signing information through a single signing process. Compared to existing solutions where both source and destination data management functions need to perform tag signing processes, the above method reduces the complexity of synchronizing tag signing information in tag circulation scenarios by minimizing the number of signing processes.

[0080] In this embodiment, the tag's identification information can be the tag's equipment serial number (ESN), tag index, tag identifier, tag code, tag number range, or a combination of the tag index and identifier, or the tag index and tag code. In other words, the tag's identification information can be one or more of the aforementioned tag index, identifier, code, or number range. This application does not limit the specific form of the tag's identification information, as long as it can uniquely identify the tag. The tag code is a coding system designed for the unique identification of IoT devices, commonly including codes based on electronic product codes (EPC) and unified IoT device codes. Common tag number ranges can be prefixes of the tag code, the region to which the tag belongs, etc.

[0081] In this embodiment, the difference between the first contract information and the second contract information lies in the different identification information of the data management functions they include. Specifically, the first contract information includes the identification information of the source data management function, while the second contract information includes the identification information of the destination data management function. That is, the first contract information is used for the source data management function to manage the tag, and therefore requires the inclusion of the source data management function's identification information. The second contract information is used for the destination data management function to manage the tag, and therefore requires the inclusion of the destination data management function's identification information. Apart from this, the information in the first contract information other than the identification information of the source data management function is the same as the information in the second contract information other than the identification information of the destination data management function.

[0082] One possible implementation is that both the first and second contract information include the tag's authentication key. The tag's authentication key is used in the tag authentication process. The main types of authentication keys are a master key and a key encryption key. The master key is generated using the Advanced Encryption Standard (AES) or a Chinese commercial cryptographic algorithm. The key encryption key is used to encrypt the storage or transmission of the tag's master key and is generally generated based on the AES-128 algorithm.

[0083] In this embodiment, the authentication key can be generated by the central data management function or by the source tag management function. When the central data management function generates the authentication key, this allows the central data management function to dynamically adjust the generation strategy of the tag's authentication key.

[0084] One possible implementation is to include the tag's authentication key in the subscription request message. This eliminates the need for the central data management function to generate the tag's authentication key, thus reducing the functional complexity of the central data management function.

[0085] In this embodiment, the central data management function can send the second contract information to the target data management function in various ways. The various methods described below are illustrated with specific examples.

[0086] Method A1: The central data management function responds to the request of the source tag management function by sending the second contract information to the destination data management function.

[0087] One possible implementation is that the central data management function and the source tag management function can exchange information as follows:

[0088] The source tag management function sends a first contract information request message to the central data management function. This first contract information request message requests the central data management function to send the tag's contract information to the destination data management function. The first contract information request message includes the tag's identification information and the destination data management function's identification information. The central data management function receives the first contract information request message.

[0089] The central data management function sends the second contract information to the destination data management function based on the first contract information request message. The destination data management function receives the second contract information.

[0090] Since the central data management function has already stored the second contract information, after receiving the first contract information request message, the central data management function determines the second contract information based on the identification information of the tag carried in the first contract information request message, and sends the second contract information to the destination data management function.

[0091] In method A1, the central data management function can determine the address information of the target data management function in a variety of ways, which will be described below with specific examples.

[0092] Method A11: The central data management function obtains the address information of the target data management function through information exchange with the warehousing function.

[0093] One possible implementation is that the central data management function and the warehousing function can exchange information as follows:

[0094] The central data management function sends a first address request message to the warehouse function. This first address request message requests the address information of the target data management function and includes the identifier information of the target data management function. The warehouse function receives the first address request message, determines the address information of the target data management function based on its identifier information, and sends this address information to the central data management function. The central data management function receives the address information of the target data management function.

[0095] The warehousing function internally stores a mapping relationship between the identification information managed by the destination data management function and the address information of the destination data management function. After receiving the first address request message, the warehousing function determines the address information of the destination data management function based on the identification information of the destination data management function carried in the first address request message, and sends the address information of the destination data management function to the central data management function.

[0096] Method A12: The address information of the destination data management function is pre-configured in the central data management function. This reduces the information exchange overhead between the central data management function and the warehousing function.

[0097] Through method A11 or method A12, the central data management function can obtain the address information of the target data management function, and can send the second contract information to the target data management function based on the address information of the target data management function.

[0098] Method A2: The central data management function responds to the request of the target data management function by sending the second contract information to the target data management function.

[0099] One possible implementation is that the central data management function and the target data management function can exchange information as follows:

[0100] The target data management function sends a second contract information request message to the central data management function. This second contract information request message requests the contract information of the tag and includes the tag's identification information. The central data management function receives the second contract information request message.

[0101] The central data management function sends the second contract information to the destination data management function based on the second contract information request message.

[0102] Since the central data management function has already stored the second contract information, after receiving the second contract information request message, the central data management function determines the second contract information based on the identification information of the tag carried in the second contract information request message, and sends the second contract information to the destination data management function.

[0103] In method A2, the destination data management function can determine the address information of the central data management function in several ways. These are described below with specific examples.

[0104] Method A21: The purpose of the data management function is to obtain the address information of the central data management function through information interaction with the warehousing function.

[0105] One possible implementation is that the target data management function and the warehousing function can interact with each other as follows:

[0106] The destination data management function sends a second address request message to the warehousing function. This second address request message requests the address information of the central data management function and includes the tag's identification information. The warehousing function receives the second address request message. Based on the tag's identification information, the warehousing function determines the address information of the central data management function and sends that address information to the destination data management function. The destination data management function receives the address information from the central data management function.

[0107] The warehousing function internally stores a mapping relationship between the tag identification information managed by the central data management function and the address information of the central data management function. After receiving a second address request message, the warehousing function determines the address information of the central data management function based on the tag identification information carried in the second address request message, and sends the address information of the central data management function to the destination data management function.

[0108] Method A22: The address information of the central data management function is pre-configured in the destination data management function. This reduces the information exchange overhead between the destination data management function and the warehousing function.

[0109] Through method A21 or method A22, the target data management function can obtain the address information of the central data management function, and can send a second contract information request message to the central data management function based on the address information of the central data management function.

[0110] Method A3: The central data management function proactively sends the second contract information to the target data management function.

[0111] After determining the second contract information, the central data management function sends the second contract information to the destination data management function after a period of time, or it can send the second contract information to the destination data management function immediately. This reduces the information exchange overhead between the central data management function and other functions.

[0112] The above description of methods A1 to A3 is based on the example of the central data management sending the second contract information to the destination data management function.

[0113] The following section describes the scenario where the central data management function sends the first contract information to the source data management function.

[0114] In this embodiment, the central data management function can send the first contract information to the source data management function in various ways. The various methods described below are illustrated with specific examples.

[0115] Method B1: The central data management function responds to the request of the source tag management function by sending the first contract information to the source data management function.

[0116] One possible implementation is that the central data management function, the source data management function, and the source data management function can interact with each other in the following way:

[0117] The source tag management function sends a third-party contract information request message to the central data management function. This message requests the central data management function to send the tag's contract information to the source data management function. The third-party contract information request message includes the tag's identification information and the source data management function's identification information. The central data management function receives the third-party contract information request message.

[0118] The central data management function sends the first contract information to the source data management function based on the third contract information request message. The source data management function receives the first contract information.

[0119] Since the central data management function has already stored the first contract information, after receiving the third contract information request message, the central data management function determines the first contract information based on the identification information of the tag carried in the third contract information request message, and sends the first contract information to the source data management function.

[0120] In method B1, the central data management function can determine the address information of the source data management function in several ways. These are described below with specific examples.

[0121] Method B11: The central data management function obtains the address information of the source data management function through information exchange with the warehousing function.

[0122] One possible implementation is that the central data management function and the warehousing function can exchange information as follows:

[0123] The central data management function sends a third address request message to the warehouse function. This message requests the address information of the source data management function and includes the source data management function's identification information. The warehouse function receives the third address request message, determines the source data management function's address information based on its identification information, and then sends this address information back to the central data management function. The central data management function receives the address information from the source data management function.

[0124] The warehousing function internally stores a mapping relationship between the identification information and address information of the source data management function. Upon receiving a third address request message, the warehousing function determines the address information of the source data management function based on the information carried in the message and then sends this address information to the central data management function.

[0125] Method B12: The address information of the source data management function is pre-configured in the central data management function. This reduces the information exchange overhead between the central data management function and the warehousing function.

[0126] Through method B11 or method B12, the central data management function can obtain the address information of the source data management function, and can send the first contract information to the source data management function based on the address information of the source data management function.

[0127] Method B2: The central data management function responds to the request of the source data management function by sending the first contract information to the source data management function.

[0128] One possible implementation is that the central data management function and the source data management function can exchange information as follows:

[0129] The source data management function sends a fourth contract information request message to the central data management function. The central data management function receives the fourth contract information request message, which is used to request the contract information of the tag and includes the tag's identification information.

[0130] The central data management function sends the first contract information to the source data management function based on the fourth contract information request message. The source data management function receives the first contract information.

[0131] Since the central data management function has already stored the first contract information, after receiving the fourth contract information request message, the central data management function determines the first contract information based on the identification information of the tag carried in the fourth contract information request message, and sends the first contract information to the source data management function.

[0132] In method B2, the source data management function can determine the address information of the central data management function in several ways. These are described below with specific examples.

[0133] Method B21: The source data management function obtains the address information of the central data management function through information exchange with the warehousing function.

[0134] One possible implementation is that the source data management function and the warehousing function can exchange information as follows:

[0135] The source data management function sends a fourth address request message to the warehouse function. This message requests address information from the central data management function and includes tag identification information. The warehouse function receives the fourth address request message, determines the address information of the central data management function based on the tag identification information, and then sends this address information back to the source data management function. The source data management function receives the address information from the central data management function.

[0136] The warehousing function internally stores a mapping relationship between the tag identification information managed by the central data management function and the address information of the central data management function. After receiving a fourth address request message, the warehousing function determines the address information of the central data management function based on the tag identification information carried in the fourth address request message, and sends the address information of the central data management function to the destination data management function.

[0137] Method B22: The address information for the central data management function is pre-configured in the source data management function. This reduces the information exchange overhead between the source data management function and the warehousing function.

[0138] Through method B21 or method B22, the source data management function can obtain the address information of the central data management function, and can send a fourth contract information request message to the central data management function based on the address information of the central data management function.

[0139] In this embodiment of the application, after sending the second contract information to the destination data management function, the central data management function can instruct the source data management function to delete the first contract information it stores. See below for details.

[0140] One possible implementation is that the central data management function and the source data management function can also exchange information in the following way:

[0141] The central data management function sends a contract information deletion message to the source data management function. The source data management function receives the contract information deletion message. The contract information deletion message is used to request the source data management function to delete the contract information of the tag; the contract information request message includes the tag's identification information.

[0142] The source data management function deletes the first contract information based on the contract information.

[0143] After receiving a contract information deletion message, the source data management function identifies the first contract information based on the tag identification information carried in the contract information deletion message and deletes the first contract information.

[0144] In scenarios involving a central data management function requesting the source data management function to delete a tag's contractual information, the central data management function can determine the address information of the source data management function in several ways. The following description uses specific examples.

[0145] Method C11: The central data management function obtains the address information of the source data management function through information interaction with the warehousing function.

[0146] One possible implementation is that the central data management function and the warehousing function can exchange information as follows:

[0147] The central data management function sends a fifth address request message to the warehouse function. This message requests the address information of the source data management function and includes its identification information. The warehouse function receives the fifth address request message, determines the source data management function's address information based on its identification, and then sends this address information to the central data management function. The central data management function receives the address information from the source data management function.

[0148] The warehousing function internally stores a mapping relationship between the identification information and address information of the source data management function. After receiving the fifth address request message, the warehousing function determines the address information of the source data management function based on the identification information of the source data management function carried in the fifth address request message, and sends the address information of the source data management function to the central data management function.

[0149] Method C12: The address information of the source data management function is pre-configured in the central data management function. This reduces the information exchange overhead between the central data management function and the warehousing function.

[0150] Through method C11 or method C12, the central data management function can obtain the address information of the source data management function and send a contract information deletion message to the source data management function based on the address information of the source data management function.

[0151] Figure 1 The description uses the first type of communication system as an example, but the content can also be applied to the second type of communication system, which includes central data management functions and destination data management functions. For a description of the second type of communication system, please refer to the preceding description of the first type of communication system; it will not be repeated here.

[0152] The following describes the specific application systems of the two communication systems shown in the embodiments of this application.

[0153] The two communication systems illustrated in this application can be applied to the following systems: 5G systems, future communication systems, inter-satellite communication, and satellite communication, etc., which are non-terrestrial network (NTN) systems. Among them, the satellite communication system includes satellite base stations and terminal equipment. The satellite base station provides communication services to the terminal equipment. The satellite base station can also communicate with terrestrial base stations. A satellite can act as a base station or as a terminal equipment. Satellites can refer to non-terrestrial base stations or non-terrestrial equipment such as drones, hot air balloons, low-Earth orbit satellites, medium-Earth orbit satellites, and high-Earth orbit satellites.

[0154] The following text combines Figure 2The two communication systems illustrated in the embodiments of this application are described in their application to a 5G network architecture. (Reference) Figure 2 The network architecture includes: tags, radio access network (RAN), Ambient Internet of Things (AIOTF) tag management function, NRF, network exposure function (NEF), AF, local AIOTF data management, global AIOTF data management, and a service operation support system / IoT platform. The IoT platform can also be understood as an IoT management platform, i.e., a platform used to manage the Internet of Things.

[0155] exist Figure 2 In the network architecture shown, tags are accessed through the RAN to the core network. The environmental power IoT tag management function has information exchange interfaces with the RAN, local environmental power IoT data management, NRF, NEF, and AF. The local environmental power IoT data management function has information exchange interfaces with the environmental power IoT tag management function, NEF, NRF, AF, and global environmental power IoT data management, and can also have information exchange interfaces with the business operation support system / IoT platform. The global environmental power IoT data management function has information exchange interfaces with the local environmental power IoT data management, the business operation support system / IoT platform, and NRF. The business operation support system / IoT platform has an information exchange interface with the global environmental power IoT data management, and can also have an information exchange interface with the local environmental power IoT data management. The AF has information exchange interfaces with the NEF and the environmental power IoT tag management function. The NEF has information exchange interfaces with the NRF, AF, environmental power IoT tag management function, and local environmental power IoT data management. There are interfaces between NRF and local-environmental power IoT data management, global-environmental power IoT data management, environmental power IoT tag management functions, and NEF; the business operation support system / IoT platform / AF / environmental power IoT tag management function / RAN can be understood as an example of the aforementioned tag management function.

[0156] when Figure 2 When the network architecture shown is the network architecture of the tag's contracted location, local-environment power IoT data management is an example of source data management functionality. When Figure 2 The network architecture shown is an example of a local-environmental power IoT data management function when the network architecture is the destination network architecture for tag flow.

[0157] The following text combines Figure 3 and Figure 4right Figure 1 The information interaction between the functions shown will be further described below. For ease of description, the following description uses the following examples: the central data management function is global-environmental power IoT data management; the source data management function is source local-environmental power IoT data management (source local-ADM); the destination data management function is destination local-environmental power IoT data management (destination local-ADM); the warehousing function is network warehousing function (NRF); and the source tag management function is source IoT (source IoT) or source environmental power IoT tag management function (source AIOTF). Additionally, Figure 3 and Figure 4 The identification information of the label shown is Figure 1 The label identification information shown.

[0158] Figure 3 This is a schematic diagram of the interaction flow of a communication method according to an embodiment of this application. (Reference) Figure 3 The method includes:

[0159] Optionally, a first registration process is performed between S301, global-environmental power IoT data management, and network warehousing functions.

[0160] The global-environmental power IoT data management system first locally configures the following information: identification information for at least one tag, identification information for the global-environmental power IoT data management system, and address information for the global-environmental power IoT data management system. The identification information for the at least one tag includes... Figure 1 The label identification information mentioned in the document.

[0161] The first registration process includes: The Global-Environmental Power IoT Data Management system sends a first registration request message to the network repository function. This first registration request message includes identification information for at least one identifier, the identifier information for the Global-Environmental Power IoT Data Management system, and the address information for the Global-Environmental Power IoT Data Management system. The network repository function receives the first registration request message and stores the information carried in it. After completing the registration of the Global-Environmental Power IoT Data Management system, the network repository function sends a first registration response message to it. This first registration response message indicates that the registration of the Global-Environmental Power IoT Data Management system has been completed. The Global-Environmental Power IoT Data Management system receives the first registration response message and determines that registration has been completed based on it.

[0162] Optionally, a second registration process is performed between S302, source local-environment power IoT data management and network warehousing functions.

[0163] The source local-environment power IoT data management first configures the following information locally: the identification information and address information of the source local-environment power IoT data management.

[0164] The second registration process includes: The Source Local-Environmental Power IoT Data Management system sends a second registration request message to the Network Repository function. This second registration request message includes the identification information and address information of the Source Local-Environmental Power IoT Data Management system. The Network Repository function receives the second registration request message and stores the information carried in it. After completing the registration of the Source Local-Environmental Power IoT Data Management system, the Network Repository function sends a second registration response message to it. This second registration response message indicates that the registration of the Source Local-Environmental Power IoT Data Management system has been completed. The Source Local-Environmental Power IoT Data Management system receives the second registration response message and determines that registration has been completed based on it.

[0165] Optionally, a third registration process may be performed between S303, the target local-environment power IoT data management and network warehousing functions.

[0166] The destination local-environment power IoT data management first configures the following information locally: the identification information and the address information of the destination local-environment power IoT data management.

[0167] The third registration process includes: the destination local-environmental power IoT data management system sends a third registration request message to the network repository function. This message includes the identifier and address information of the destination local-environmental power IoT data management system. The network repository function receives the third registration request message and stores the information carried within it. After completing the registration of the destination local-environmental power IoT data management system, the network repository function sends a third registration response message to it. This response message indicates that the registration has been completed. The destination local-environmental power IoT data management system receives the response message and determines that registration is complete based on it.

[0168] S304. The source IoT sends a subscription request message to the global-environmental power IoT data management system. Correspondingly, the global-environmental power IoT data management system receives the subscription request message.

[0169] The contract request message includes the tag's identification information and the source local-environment power IoT data management identification information.

[0170] Optionally, the subscription request message also includes the tag's authentication key. Upon receiving the tag's authentication key, the global-environmental power IoT data management system can store it as part of the first subscription information; that is, the first subscription information generated by the global-environmental power IoT data management system includes the tag's authentication key. The source-local-environmental power IoT data management system or the destination-local-environmental power IoT data management system can then perform an authentication process on the tag based on this authentication key. Simultaneously, the tag's authentication key can be used for two-way authentication between the tag and the network, ensuring the confidentiality and integrity of data and sessions.

[0171] Optionally, the subscription request message may also include the tag's allowed access area information. The allowed access area information indicates the areas where the tag can be transferred. For example, if the tag's subscription location is location A, and the allowed access area information indicates location B, then the tag cannot be transferred to location C.

[0172] S305, Global-Environmental Power IoT Data Management saves the first contract information of the tag.

[0173] After receiving a subscription request message, the global-environmental power IoT data management system stores the information carried in the subscription request message, that is, it uses the information carried in the subscription request message as the first subscription information of the tag.

[0174] When the signing request message does not carry the tag's authentication key, the Global-Environmental Power IoT Data Management system automatically determines the tag's authentication key and can use the tag's authentication key as part of the first signing information.

[0175] Optionally, the first contract information may also include at least one of the identification information of the global-environmental power IoT data management and the address information of the global-environmental power IoT data management.

[0176] In this embodiment of the application, "saving" may also include the meaning of global-environmental power IoT data management processing the subscription request message to obtain the first subscription information.

[0177] Optionally, S306, the global-environmental power IoT data management system, sends a subscription response message to the source IoT. Correspondingly, the source IoT receives the subscription response message.

[0178] After saving the initial signing information of the tag, the global-environmental power IoT data management system sends a signing response message to the source IoT network. The signing response message indicates that the signing of the tag has been completed.

[0179] Optionally, the contract response message includes the tag's identification information. Source IoT determines that the tag has completed the contract signing based on this identification information.

[0180] Optionally, the subscription response message includes the tag's identification information and the tag's authentication key. Specifically, when the subscription request message includes the tag's authentication key, the subscription response message may or may not include the tag's authentication key. When the subscription request message does not include the tag's authentication key, the subscription response message may include the tag's authentication key so that the source IoT can store the tag's authentication key for use in subsequent tag authentication processes.

[0181] S307. The source IoT sends a third-signature information request message to the global-environmental power IoT data management system. Correspondingly, the global-environmental power IoT data management system receives the third-signature information request message. The third-signature information request message includes the identification information of the source local-environmental power IoT data management system and the identification information of the tag.

[0182] Optionally, the third contract information request message may only include the tag's identification information. The global-environmental power IoT data management determines the corresponding first contract information based on the tag's identification information in the third contract information request message, and also determines the source-local-environmental power IoT data management's identification information.

[0183] S308, Global-Environmental Power IoT Data Management sends a third address request message to the Network Repository function. Correspondingly, the Network Repository function receives the third address request message.

[0184] The third address request message is used to request address information for the source local-environmental power IoT data management system. The third address request message includes identification information for the source local-environmental power IoT data management system. Specifically, the identification information for the source local-environmental power IoT data management system in the third address request message originates from the third contract information request message.

[0185] Optionally, the identification information of the source local-environmental power IoT data management in the third address request message can also come from the first contract information. That is, the global-environmental power IoT data management determines the corresponding first contract information based on the identification information of the tag in the third contract information request message, and determines the identification information of the source local-environmental power IoT data management.

[0186] S309. The network storage function sends the address information of the source local environmental power IoT data management system to the global environmental power IoT data management system. Correspondingly, the global environmental power IoT data management system receives the address information of the source local environmental power IoT data management system.

[0187] After receiving the third address request message, the network warehousing function determines the address information of the source local-environmental power IoT data management according to the second registration process in S302, and sends the address information of the source local-environmental power IoT data management to the global-environmental power IoT data management.

[0188] S310, the global-environmental power IoT data management sends the first subscription information to the source-local-environmental power IoT data management. Correspondingly, the source-local-environmental power IoT data management receives the first subscription information.

[0189] After receiving the first contract information, the source local-environment power IoT data management system can perform corresponding operations on the tag, such as tag inventory and read / write processes.

[0190] One possible implementation is that after determining the first subscription information, the global-environmental power IoT data management can proactively send the first subscription information to the source-local-environmental power IoT data management. That is, the global-environmental power IoT data management does not need to respond to a request from the source IoT to send the first subscription information to the source-local-environmental power IoT data management. This reduces the information interaction overhead between the global-environmental power IoT data management and the source IoT.

[0191] In this embodiment of the application, the aforementioned label can be transferred, that is, the aforementioned label can be transferred from the place of contract to the destination. For example, the label can be transferred from place A to place B, where place A is the place of contract for the label and place B is the destination for the transfer of the label.

[0192] S311, the source IoT sends a subscription information change message to the global-environmental power IoT data management system. Correspondingly, the global-environmental power IoT data management system receives the subscription information change message.

[0193] The contract information change message includes the tag's identification information and the identification information of the target local-environmental power IoT data management system. The contract information change message is used to request changes to the tag's contract information, or to request changes to the mapping relationship between the tag and the local-environmental power IoT data management system.

[0194] S312, Global-Environmental Power IoT Data Management and Storage Tag's Second Contract Information.

[0195] After receiving a contract information change message, the global-environmental power IoT data management system can re-establish the second contract information of the tag and replace the original first contract information with the second contract information. Alternatively, after receiving a contract information change message, the global-environmental power IoT data management system can replace the source local-environmental power IoT data management system's identification information in the first contract information with the identification information of the destination local-environmental power IoT data management system, thereby obtaining the second contract information.

[0196] Optionally, the global-environmental power IoT data management can also send a subscription information change response message to the source IoT. The subscription information change response message is used to indicate to the source IoT the subscription information of the changed tag. Alternatively, the subscription information change response message is used to indicate to the source IoT the mapping relationship between the changed tag and the local-environmental power IoT data management.

[0197] In this embodiment of the application, "saving" may also include processing the contract information change message by global-environmental power IoT data management in order to obtain the meaning of the second contract information.

[0198] S313, the source IoT sends a first subscription information request message to the global-environmental power IoT data management system. Correspondingly, the global-environmental power IoT data management system receives the first subscription information request message.

[0199] For a description of the first contract information request message, please refer to [link / reference]. Figure 1 The relevant description in the document.

[0200] Optionally, the first contract information request message may also include identification information of the source local-environmental power IoT data management. In this way, the global-environmental power IoT data management can request the address information of the source local-environmental power IoT data management from the network repository function based on the identification information of the source local-environmental power IoT data management carried in the first contract information request message.

[0201] S314, Global-Environmental Power IoT Data Management sends a first address request message to the Network Repository function. Correspondingly, the Network Repository function receives the first address request message.

[0202] The first address request message is used to request address information for the destination local-environmental power IoT data management. The first address request message includes the identification information of the destination local-environmental power IoT data management.

[0203] S315, the network warehousing function sends the address information of the destination local environmental power IoT data management system to the global environmental power IoT data management system. Correspondingly, the global environmental power IoT data management system receives the address information of the destination local environmental power IoT data management system.

[0204] After receiving the first address request message, the network warehousing function can determine the address information of the destination local-environmental power IoT data management according to the third registration process in S303, and send the address information of the destination local-environmental power IoT data management to the global-environmental power IoT data management.

[0205] S316, The global-environmental power IoT data management sends the second contract information to the destination-local-environmental power IoT data management. Correspondingly, the destination-local-environmental power IoT data management receives the second contract information.

[0206] One possible implementation is that after determining the second subscription information, the global-environmental power IoT data management can proactively send the second subscription information to the destination local-environmental power IoT data management. That is, the global-environmental power IoT data management does not need to respond to a request from the source IoT to send the second subscription information to the destination local-environmental power IoT data management. This reduces the information exchange overhead between the global-environmental power IoT data management and the source IoT.

[0207] S317, Global-Environmental Power IoT Data Management sends a Fifth Address Request message to the Network Repository function. Correspondingly, the Network Repository function receives the Fifth Address Request message.

[0208] The fifth address request message is used to request address information for the source local-environmental power IoT data management system. The fifth address request message includes the identification information of the source local-environmental power IoT data management system.

[0209] In this embodiment of the application, the identification information of the source local-environmental power IoT data management in the fifth address request message may come from the first contract information request message, that is, the first contract information request message also includes the identification information of the source local-environmental power IoT data management, or it may come from the first contract information, that is, the first contract information request message does not include the identification information of the source local-environmental power IoT data management. There is no limitation on this.

[0210] S318, the network repository function sends the address information of the source local environmental power IoT data management system to the global environmental power IoT data management system. Correspondingly, the global environmental power IoT data management system receives the address information of the source local environmental power IoT data management system.

[0211] After receiving the fifth address request message, the network warehousing function can determine the address information of the source local-environmental power IoT data management according to the second registration process in S302, and send the address information of the source local-environmental power IoT data management to the global-environmental power IoT data management.

[0212] In this embodiment, when the first contract information request message includes both the identifier information of the source local-environmental power IoT data management and the identifier information of the destination local-environmental power IoT data management, the global-environmental power IoT data management can simultaneously request the address information of both the source local-environmental power IoT data management and the destination local-environmental power IoT data management from the network repository function. That is, the global-environmental power IoT data management can execute S314 and S317 simultaneously; in other words, the first address request message and the fifth address request message can be the same message. This reduces information interaction overhead and also reduces the total duration of information interaction.

[0213] S319, Global-Environmental Power IoT Data Management sends a subscription information deletion message to Source-Local-Environmental Power IoT Data Management. Correspondingly, Source-Local-Environmental Power IoT Data Management receives the subscription information deletion message.

[0214] The contract information deletion message is used to request the source local-environmental power IoT data management to delete the contract information of the tag. The contract information deletion message includes the tag's identification information.

[0215] S320, Source Local - Environmental Power IoT Data Management, delete the first contract information.

[0216] Upon receiving a message to delete the subscription information, the source local-environment power IoT data management system deletes the first subscription information based on the tag identification information carried in the message.

[0217] Optionally, in step S321, the source local-environmental power IoT data management sends a subscription information deletion response message to the global-environmental power IoT data management. Correspondingly, the global-environmental power IoT data management receives the subscription information deletion response message. The subscription information deletion response message indicates that the source local-environmental power IoT data management has deleted the subscription information of the tag.

[0218] Using the methods described above, the central data management function can achieve flexible management of the tag's contract information.

[0219] Figure 3 This description uses the example of the global-environmental power IoT data management sending second-signature information to the destination local-environmental power IoT data management in response to a request from the source IoT. However, it is not limited to the scenario where the destination local-environmental power IoT data management actively requests the tag's signature information from the global-environmental power IoT data management. For details, please refer to... Figure 4 .

[0220] Figure 4This is a schematic diagram of the interaction flow of another communication method according to an embodiment of this application. (Reference) Figure 4 The method includes:

[0221] Optionally, a first registration process is performed between S401, the global-environmental power IoT data management, and the network warehousing function. See the description in S301 for details.

[0222] Optionally, a second registration process may be performed between S402, the source local-environment power IoT data management and network warehousing functions. See the description of S302 for details.

[0223] Optionally, a third registration process may be implemented between S403, the target local-environment power IoT data management, and the network warehousing function. For details, please refer to the description in S303.

[0224] S404: The source application function sends a subscription request message to the global-environmental power IoT data management system. Correspondingly, the global-environmental power IoT data management system receives the subscription request message. See S304 for a detailed description.

[0225] S405, Global-Environmental Power IoT Data Management saves the first contract information of the tag. For details, please refer to the description of S305.

[0226] Optionally, S406, Global-Environmental Power IoT Data Management, sends a subscription response message to the source application function. Correspondingly, the source application function receives the subscription response message.

[0227] For a detailed description, please refer to the description in S306.

[0228] S407. The source application function sends a first inventory request message to the source environment power IoT tag management function. Correspondingly, the source environment power IoT tag management function receives the first inventory request message. The source environment power IoT tag management function is the tag management function on the core network side.

[0229] The first inventory request message is used to request the source environment power IoT tag management function to conduct an inventory of the tags. The first inventory request message may include tag identification information or inventory area information. The inventory area information can be used to indicate the areas where the source environment power IoT tag management function needs to conduct tag inventory.

[0230] S408, the source environmental power IoT tag management function sends a fifth contract information request message to the source local-environmental power IoT data management system. Correspondingly, the source local-environmental power IoT data management system receives the fifth contract information request message.

[0231] The fifth contract information request message is used to request the source local-environmental power IoT data management to obtain the contract information of the tag. The fifth contract information request message includes the tag's identification information.

[0232] S409, the source local-environment power IoT data management sends a fourth address request message to the network repository function. Correspondingly, the network repository function receives the fourth address request message.

[0233] The fourth address request message is used to request address information for global-environmental power IoT data management. The fourth address request message includes the tag's identification information.

[0234] S410, the network warehousing function sends the address information of the global environmental power IoT data management system to the source local environmental power IoT data management system. Correspondingly, the source local environmental power IoT data management system receives the address information of the global environmental power IoT data management system.

[0235] After receiving the tag identification information, the network warehousing function can determine the address information of the global-environmental power IoT data management according to the first registration process in S401, and send the address information of the global-environmental power IoT data management to the source local-environmental power IoT data management.

[0236] S411, the local environmental power IoT data management system sends a fourth contract information request message to the global environmental power IoT data management system. Correspondingly, the global environmental power IoT data management system receives the fourth contract information request message.

[0237] The fourth contract information request message is used to request the contract information of the tag. The fourth contract information request message includes the tag's identification information.

[0238] S412, Global-Environmental Power IoT Data Management sends the first subscription information to Source-Local-Environmental Power IoT Data Management. Correspondingly, Source-Local-Environmental Power IoT Data Management receives the first subscription information.

[0239] In this embodiment, after obtaining the first contract information, the source local-environmental power IoT data management performs a tag inventory process with the source environmental power IoT tag management function and the source application function. The specific process will not be described in detail.

[0240] In this embodiment of the application, the label will undergo a label transfer process.

[0241] S413, the source application function sends a subscription information change message to the global-environmental power IoT data management system. Correspondingly, the global-environmental power IoT data management system receives the subscription information change message.

[0242] For a detailed description, please refer to the description in S311.

[0243] S414, Global-Environmental Power IoT Data Management saves the second contract information of the tag. For details, please refer to the description of S312.

[0244] S415. The target application function sends a second inventory request message to the target environment power IoT tag management function. Correspondingly, the target environment power IoT tag management function receives the second inventory request message.

[0245] The second inventory request message is used to request the target environment power IoT tag management function to inventory the tags. The second inventory request message may include tag identification information or inventory area information. The inventory area information can be used to indicate the areas where the target environment power IoT tag management function needs to perform tag inventory.

[0246] S416, The destination environmental power IoT tag management function sends a sixth contract information request message to the destination local environmental power IoT data management. Correspondingly, the destination local environmental power IoT data management receives the sixth contract information request message.

[0247] The sixth contract information request message is used to request the local environmental power IoT data management to obtain the contract information of the tag. The sixth contract information request message includes the tag's identification information.

[0248] S417. The target local-environmental power IoT data management sends a second address request message to the network repository function. Correspondingly, the network repository function receives the second address request message.

[0249] The second address request message is used to request address information for global-environmental power IoT data management. The second address request message includes the tag's identification information.

[0250] Optionally, the second address request message can also be used to request address information of the source local-environment power IoT data management system, and the second address request message also includes identification information of the source local-environment power IoT data management system.

[0251] S418, the network warehousing function sends the address information of the global environmental power IoT data management system to the destination local environmental power IoT data management system. Correspondingly, the destination local environmental power IoT data management system receives the address information of the global environmental power IoT data management system.

[0252] S419. The local environmental power IoT data management system sends a second contract information request message to the global environmental power IoT data management system. Correspondingly, the global environmental power IoT data management system receives the second contract information request message.

[0253] The second contract information request message is used to request the contract information of the tag, and the second contract information request message includes the tag's identification information.

[0254] Optionally, the second contract information request message may also include address information for source local-environment power IoT data management.

[0255] S420: The global-environmental power IoT data management system sends the second contract information to the destination-local-environmental power IoT data management system. Correspondingly, the destination-local-environmental power IoT data management system receives the second contract information.

[0256] S421, the global-environmental power IoT data management sends a fifth address request message to the network repository function. Correspondingly, the network repository function receives the fifth address request message. See S317 for a detailed description.

[0257] S422, the network repository function sends the address information of the source local environmental power IoT data management system to the global environmental power IoT data management system. Correspondingly, the global environmental power IoT data management system receives the address information of the source local environmental power IoT data management system. For a detailed description, please refer to the description in S318.

[0258] In this embodiment of the application, when the second contract information request message also includes the address information of the source local-environmental power IoT data management, the global 0 environment IoT data management does not need to obtain the address information of the source local-environmental power IoT data management from the network repository function.

[0259] S423, Global-Environmental Power IoT Data Management sends a subscription information deletion message to Source-Local-Environmental Power IoT Data Management. Correspondingly, Source-Local-Environmental Power IoT Data Management receives the subscription information deletion message. For details, please refer to the description in S319.

[0260] S424, Source Local - Environmental Power IoT Data Management: Delete the first contract information. See S320 for a detailed description.

[0261] Optionally, in step S425, the local environmental power IoT data management system sends a subscription information deletion response message to the global environmental power IoT data management system. Correspondingly, the global environmental power IoT data management system receives the subscription information deletion response message.

[0262] For a detailed description, please refer to the description in S321.

[0263] Using the methods described above, the central data management function can achieve flexible management of the tag's contract information.

[0264] Finally, the device embodiments of this application will be described.

[0265] To implement the functions of the method provided in this application, the central data management function may include hardware structure and / or software modules, and may be implemented in the form of hardware structure, software modules, or a combination of hardware structure and software modules. Whether a particular function is implemented in the form of hardware structure, software module, or a combination of hardware structure and software modules depends on the specific application and design constraints of the technical solution.

[0266] Figure 5 This is a schematic block diagram of a communication device according to an embodiment of this application. The communication device includes a processing circuit 510 and a transceiver circuit 520, which can be interconnected or coupled to each other. For example, the processing circuit 510 and the transceiver circuit 520 can be interconnected via a bus 530. This communication device can provide a central data management function.

[0267] Optionally, the communication device may also include a memory 540. The memory 540 includes, but is not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or compact disc read-only memory (CD-ROM), and is used for related instructions and data.

[0268] The processing circuit 510 may be all or part of the processing circuitry in one or more processors, or it may be one or more processors. The processor may be a central processing unit (CPU). If the processing circuit 510 is a CPU, the CPU may be a single-core CPU or a multi-core CPU. The processing circuit 510 may be a signal processor, a chip, or other integrated circuit capable of implementing the methods of this application, or a portion of the circuitry within the aforementioned processor, chip, or integrated circuit used for processing functions. The transceiver circuit 520 may also be a transceiver or an input / output interface. The input / output interface is used for inputting or outputting signals or data and may also be referred to as an input / output circuit.

[0269] When the communication device is a central data management function, exemplarily, the processing circuit 510 is configured to perform the following operations: control the transceiver circuit 520 to receive a subscription request message from the source tag management function, the subscription request message being used to request the central data management function to subscribe to the tag, the subscription request message including the tag's identification information and the identification information of the source data management function, the source data management function being the data management function of the tag's subscription location, the source tag management function being the tag management function of the tag's subscription location, the source tag management function being used to manage the tag; determine the tag's first subscription information based on the subscription request message, the first subscription information including the tag's identification information and the source data management function's identification information; control the transceiver circuit 520 to receive a subscription information change message from the source tag management function, the subscription information change message being used to request the central data management function to change the tag's subscription information, the subscription information change message including the identification information of the destination data management function and the tag's identification information, the destination data management function being the data management function of the tag's transit destination; determine the tag's second subscription information based on the subscription information change message, the second subscription information including the tag's identification information and the destination data management function's identification information; control the transceiver circuit 520 to send the second subscription information to the destination data management function.

[0270] When the communication device is a central data management function, it will be responsible for executing the methods or steps related to the central data management function in the aforementioned method embodiments.

[0271] When the communication device is used for central data management, the transceiver circuit 520 can be a transceiver.

[0272] When the communication device is a chip used for central data management functions, the transceiver circuit 520 can be an input / output circuit.

[0273] The above description is merely exemplary. For details, please refer to the methods described in the above embodiments. Additionally, Figure 5 The description of the communication device shown can also be applied to other functions mentioned in the foregoing method embodiments, such as source AF or destination data management functions.

[0274] Figure 5 The implementation of each operation can also be found by referring to... Figure 1 , Figures 3 to 4 The corresponding description is shown.

[0275] Figure 6 This is a schematic block diagram of another communication device according to an embodiment of this application. This communication device can serve as a central data management function to implement the methods described in the above embodiments.

[0276] The communication device includes a transceiver unit 610 and a processing unit 620. The transceiver unit 610 may include a sending unit and a receiving unit. The sending unit is used to perform the sending action of the communication device, and the receiving unit is used to perform the receiving action of the communication device. For ease of description, the sending unit and the receiving unit are combined into one transceiver unit in this embodiment. This will be explained uniformly here and will not be repeated later.

[0277] When the communication device is a central data management function, exemplarily, the transceiver unit 610 is used to receive a subscription request message from the source tag management function. The subscription request message requests the central data management function to subscribe to the tag. The subscription request message includes the tag's identification information and the identification information of the source data management function. The source data management function is the data management function of the tag's subscription location, and the source tag management function is the tag management function of the tag's subscription location. The source tag management function is used to manage the tag. The processing unit 620 is used to determine the tag's first subscription information based on the subscription request message. The first subscription information includes the tag's identification information and the identification information of the source data management function. The transceiver unit 610 is used to receive a subscription information change message from the source tag management function. The subscription information change message requests the central data management function to change the tag's subscription information. The subscription information change message includes the identification information of the destination data management function and the tag's identification information. The destination data management function is the data management function of the tag's transit destination. The processing unit 620 is used to determine the tag's second subscription information based on the subscription information change message. The second subscription information includes the tag's identification information and the identification information of the destination data management function. The transceiver unit 610 is used to send the second subscription information to the destination data management function.

[0278] When the communication device is for central data management, it will also be responsible for executing one or more of the methods or steps related to the central data management function in the aforementioned method embodiments.

[0279] Optionally, the communication device further includes a storage unit 630 for storing programs or code for executing the aforementioned methods.

[0280] Figure 6 The transceiver unit in the middle can correspond to Figure 5 The transceiver circuit in the middle, Figure 6 The processing unit in can correspond to Figure 5 The processing circuitry within. Additionally... Figure 6 The description of the communication device shown can also be applied to other functions mentioned in the foregoing method embodiments, such as source AF or destination data management functions.

[0281] Figure 5 and Figure 6 The illustrated device embodiment is used to implement Figure 1 , Figures 3 to 4 The content described. Figure 5 and Figure 6 The specific execution steps and methods of the device shown can be found in the content described in the foregoing method embodiments.

[0282] This application also provides a chip, including a processor, for calling and executing instructions stored in a memory, causing a communication device on which the chip is installed to perform the methods described in the examples above. The memory may be integrated within the chip or located externally.

[0283] This application also provides another chip, including: an input interface, an output interface, and a processing circuit, wherein the input interface, the output interface, and the processor are connected through an internal connection path, and the processing circuit is used to execute code in memory. When the code is executed, the processing circuit is used to execute the methods in the above examples.

[0284] Optionally, the chip also includes a memory for storing computer programs or code. The input and output interfaces can be independent of each other, or they can be integrated into a single input / output interface.

[0285] The processing circuitry can be all or part of the processing circuitry in one or more processors, or one or more processors.

[0286] This application also provides a processor for coupling with a memory for performing the methods and functions of a network device or terminal device involved in any of the above embodiments.

[0287] In another embodiment of this application, a computer program product containing instructions is provided, which, when run on a computer, enables the implementation of the methods described in the foregoing embodiments.

[0288] This application also provides a computer program that, when run on a computer, enables the implementation of the methods described in the foregoing embodiments.

[0289] In another embodiment of this application, a computer-readable storage medium is provided, which stores a computer program that, when executed by a computer, implements the methods described in the foregoing embodiments.

[0290] In this embodiment, the processor can be a central processing unit (CPU), but it can also 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.

[0291] 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 random access memory (RAM) are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous linked DRAM (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0292] 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. A computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs 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 or wireless (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.

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

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

[0295] In the embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only 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. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0296] 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 above functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium.

[0297] Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a 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 a USB flash drive, portable hard drive, read-only memory, random access memory, magnetic disk, or optical disk. 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.

Claims

1. A communication method, characterized in that, include: The central data management function receives a signing request message from the source tag management function. The signing request message is used to request the central data management function to sign a tag. The signing request message includes the tag's identification information and the source data management function's identification information. The source data management function is the data management function of the tag's signing location, and the source tag management function is the tag management function of the tag's signing location. The source tag management function is used to manage the tag. The central data management function determines the first signing information of the tag based on the signing request message. The first signing information includes the tag's identification information and the source data management function's identification information. The central data management function receives a contract information change message from the source tag management function. The contract information change message is used to request the central data management function to change the contract information of the tag. The contract information change message includes the identification information of the destination data management function and the identification information of the tag. The destination data management function is the data management function of the destination of the tag's circulation. The central data management function determines the second contract information of the tag based on the contract information change message. The second contract information includes the tag's identification information and the identification information of the target data management function. The central data management function sends the second contract information to the target data management function.

2. The method according to claim 1, characterized in that, The central data management function sends the second contract information to the destination data management function, including: The central data management function receives a first contract information request message from the source tag management function. The first contract information request message is used to request the central data management function to send the contract information of the tag to the destination data management function. The first contract information request message includes the identification information of the tag and the identification information of the destination data management function. The central data management function sends the second contract information to the destination data management function based on the first contract information request message.

3. The method according to claim 2, characterized in that, The method further includes: The central data management function sends a first address request message to the warehousing function. The first address request message is used to request the address information of the destination data management function, and the first address request message includes the identification information of the destination data management function. The central data management function receives address information from the destination data management function of the warehousing function.

4. The method according to claim 1, characterized in that, The central data management function sends the second contract information to the destination data management function, including: The central data management function receives a second contract information request message from the destination data management function. The second contract information request message is used to request the contract information of the tag, and the second contract information request message includes the identification information of the tag. The central data management function sends the second contract information to the destination data management function according to the second contract information request message.

5. The method according to claim 4, characterized in that, The method further includes: The destination data management function sends a second address request message to the warehousing function. The second address request message is used to request the address information of the central data management function, and the second address request message includes the identification information of the tag. The destination data management function receives address information from the central data management function of the warehousing function.

6. The method according to any one of claims 1 to 5, characterized in that, The method further includes: The central data management function receives a third contract information request message from the source tag management function. The third contract information request message is used to request the central data management function to send the contract information of the tag to the source data management function. The third contract information request message includes the identification information of the tag and the identification information of the source data management function. The central data management function sends a third address request message to the warehousing function. The third address request message is used to request the address information of the source data management function, and the third address request message includes the identification information of the source data function. The central data management function receives address information from the source data management function of the warehousing function; The central data management function sends the first contract information to the source data management function according to the third contract information request message.

7. The method according to any one of claims 1 to 5, characterized in that, The method further includes: The source data management function sends a fourth address request message to the warehousing function. The fourth address request message is used to request the address information of the central data management function, and the fourth address request message includes the identification information of the tag. The source data management function receives address information from the central data management function of the warehousing function; The central data management function receives a fourth contract information request message from the source data management function. The fourth contract information request message is used to request the contract information of the tag, and the fourth contract information request message includes the identification information of the tag. The central data management function sends the first contract information to the source data management function according to the fourth contract information request message.

8. The method according to claim 7, characterized in that, The contract information change message also includes the identification information of the source data management function, and the method further includes: The central data management function sends a fifth address request message to the warehousing function. The fifth address request message is used to request the address information of the source data management function, and the fifth address request message includes the identification information of the source data function. The central data management function receives address information from the source data management function of the warehousing function; The central data management function sends a contract information deletion message to the source data management function. The contract information deletion message is used to request the source data management function to delete the contract information of the tag. The contract information request message includes the tag's identification information.

9. A communication system, characterized in that, Includes source tag management functions and central data management functions. The source tag management function is used to send a contract request message to the central data management function. The contract request message is used to request the central data management function to sign a contract for the tag. The contract request message includes the tag's identification information and the source data management function's identification information. The source data management function is the data management function of the tag's signing location, and the source tag management function is the tag management function of the tag's signing location. The source tag management function is used to manage the tag. The central data management function is used to receive the contract request message and determine the first contract information of the tag based on the contract request message. The first contract information includes the tag's identification information and the source data management function's identification information. The source tag management function is also used to send a contract information change message to the central data management function. The contract information change message is used to request the central data management function to change the contract information of the tag. The contract information change message includes the identification information of the destination data management function and the identification information of the tag. The destination data management function is the data management function of the destination of the tag's circulation. The central data management function is also used to receive the contract information change message; determine the second contract information of the tag according to the contract information change message, the second contract information including the tag's identification information and the identification information of the destination data management function; and send the second contract information to the destination data management function.

10. The system according to claim 9, characterized in that, The source tag management function is also used to send a first contract information request message to the central data management function. The first contract information request message is used to request the central data management function to send the contract information of the tag to the destination data management function. The first contract information request message includes the identification information of the tag and the identification information of the destination data management function. The central data management function is also used to receive the first contract information request message and send the second contract information to the destination data management function according to the first contract information request message.

11. The system according to claim 10, characterized in that, The central data management function is also used to send a first address request message to the warehousing function. The first address request message is used to request the address information of the destination data management function. The first address request message includes the identification information of the destination data management function and receives the address information of the destination data management function from the warehousing function.

12. The system according to claim 9, characterized in that, The central data management function is also used to receive a second contract information request message from the destination data management function. The second contract information request message is used to request the contract information of the tag, and the second contract information request message includes the identification information of the tag. The second contract information is sent to the target data management function according to the second contract information request message.

13. A communication device, characterized in that, Includes units for performing the method according to any one of claims 1 to 4 and 6.

14. A communication device, characterized in that, Includes a processor, the processor being configured to cause the communication device to perform the method of any one of claims 1 to 4 and 6 by executing a computer program or instructions, or by using logic circuitry.

15. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program or instructions that, when executed on a computer, cause the method of any one of claims 1 to 4 and 6 to be performed.

16. A computer program product, characterized in that, It includes instructions that, when executed on a computer, cause the method of any one of claims 1 to 4 and 6 to be performed.

17. A chip, characterized in that, The chip is installed in a communication device. The chip includes a processor and a communication interface. The processor reads instructions and runs them through the communication interface, causing the communication device to execute the method of any one of claims 1 to 4 and 6.

Images