Communication method, communication device, and communication system

Abstract

The application discloses a communication method, a communication device and a communication system, and relates to the technical field of communication. A source data management function performs a subscription process of a first label, sends subscription information of the first label and flow transfer destination information of the first label to a subscription information management function, and the subscription information management function performs a subscription information flow transfer process, that is, the flow transfer destination information of the first label is used to trigger the subscription information management function to send the subscription information of the first label to the flow transfer destination of the first label, which can reduce the number of subscription processes, and in turn, reduce the complexity of a synchronization process of subscription information of a label in a label flow transfer scenario, that is, the method supports synchronization of the subscription information of the label through one subscription process. Compared with the source data management function and the destination data management function both performing the subscription process on the label, the number of subscription processes is reduced, and the complexity of the synchronization process of the subscription information of the label in the label flow transfer scenario is reduced.

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 will 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 signing process is overly complex because the data management functions at the signing location and the transfer destination each perform a separate signing process. Therefore, reducing 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 source data management function, which 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 implementation form of the source data management function.

[0007] In a first aspect, a communication method is provided, comprising: a source data management function receiving a subscription request message from a source tag management function, the subscription request message being used to request the source data management function to subscribe to a first tag, the subscription request message including identification information of the first tag, the source data management function being a data management function of the subscription location of the first tag, and the source tag management function being a tag management function of the subscription location of the first tag; the source data management function determining first subscription information of the first tag based on the subscription request message, the first subscription information including the identification information of the first tag; the source data management function receiving a subscription information export message from the source tag management function, the subscription information export message being used to request the source data management function to send the subscription information of the first tag to the subscription information management function, the subscription information export message including the identification information of the first tag and information of the destination of the first tag; the source data management function sending the first subscription information and the information of the destination of the first tag to the subscription information management function based on the subscription information export message, the information of the destination of the first tag being used to trigger the subscription information management function to send the subscription information of the first tag to the destination of the first tag.

[0008] Optionally, the first signing information may also include the authentication key of the first tag.

[0009] Optionally, the destination information of the first tag is used to trigger the contract information management function to send the contract information of the first tag to the destination of the first tag, or it can be replaced by: the destination information of the first tag is used to indicate the receiving end of the contract information of the first tag.

[0010] Through the architecture of source data management and contract information management functions, the source data management function executes the contract signing process for the first tag and sends the contract signing information of the first tag to the contract information management function. The contract information management function executes the contract information flow process (the flow destination information of the first tag can be used to trigger the contract information management function to send the contract signing information of the first tag to the flow destination of the first tag). This reduces the number of times the contract signing process is performed, thereby reducing the complexity of the tag contract information synchronization process in the tag flow scenario. That is, the above method can support the synchronization of tag contract information through a single contract signing process. Compared with the existing solution where both the source data management function and the destination data management function perform the contract signing process for the tag, the above method reduces the complexity of the tag contract information synchronization process in the tag flow scenario by reducing the number of times the contract signing process is performed.

[0011] In some implementations of the first aspect, the method further includes: the source data management function receiving a first contract information deletion message from the contract information management function, the first contract information deletion message requesting the source data management function to delete the contract information of a first tag, the first contract information deletion message including the identification information of the first tag; the source data management function deleting the first contract information according to the first contract information deletion message. After receiving the first contract information deletion message, the source data management function determines the first contract information according to the identification information of the first tag carried in the first contract information deletion message, and deletes the first contract information, thereby releasing the storage space of the source data management function.

[0012] Optionally, the first contract information deletion message may also include a tag list, which includes identification information for at least one tag. In this way, the source data management function can delete contract information for more tags, thereby freeing up more storage space for the source data management function.

[0013] In some implementations of the first aspect, the method further includes: the source data management function receiving a second contract information deletion message from the source tag management function, the second contract information deletion message requesting the source data management function to delete the contract information of the first tag, the second contract information deletion message including the identification information of the first tag; the source data management function deleting the first contract information according to the second contract information deletion message. After receiving the second contract information deletion message, the source data management function determines the first contract information according to the identification information of the first tag carried in the second contract information deletion message, and deletes the first contract information, thereby releasing the storage space of the source data management function.

[0014] Optionally, the second contract information deletion message may also include a tag list, which includes identification information for at least one tag. In this way, the source data management function can delete contract information for more tags, thereby freeing up more storage space for the source data management function.

[0015] In some implementations of the first aspect, the method further includes: the source data management function sending a first channel request message to the contract information management function, the first channel request message being used to request the establishment of a first data transmission channel between the source data management function and the contract information management function; the source data management function receiving a first channel response message from the contract information management function, the first channel response message being used to indicate that the first data transmission channel has been successfully established.

[0016] The first data transmission channel enhances the security of data transmission between the source data management function and the contract information management function. Through this channel, the source data management function can send the first contract information and the destination information of the first tag to the contract information management function; in other words, the information interaction between the source data management function and the contract information management function is based on this first data transmission channel.

[0017] Secondly, a communication system is provided, comprising a source data management function and a contract information management function. The source data management function receives a contract request message from a source tag management function, requesting the source data management function to sign a contract for a first tag. The contract request message includes the identification information of the first tag. The source data management function is a data management function for the contract location of the first tag, and the source tag management function is a tag management function for the contract location of the first tag. The source data management function also determines first contract information for the first tag based on the contract request message, the first contract information including the identification information of the first tag. The source data management function further receives a contract information export message from the source tag management function, requesting the source data management function to send the contract information of the first tag to the contract information management function. The contract information export message includes the identification information of the first tag and the destination information of the first tag. The source data management function also sends the first contract information and the destination information of the first tag to the contract information management function based on the contract information export message. The contract information management function is used to receive the first contract information and the destination information of the first tag, determine the second contract information based on the first contract information, and send the second contract information to the destination of the first tag based on the destination information of the first tag. The second contract information includes the identification information of the first tag.

[0018] For a detailed description of the effects, please refer to the relevant description in the first aspect.

[0019] In some implementations of the second aspect, the contract information management function is further configured to send a first contract information deletion message to the source data management function. The first contract information deletion message requests the source data management function to delete the contract information of the first tag, and includes the identification information of the first tag. The source data management function is further configured to receive the first contract information deletion message and delete the first contract information according to the first contract information deletion message.

[0020] Optionally, the first contract information deletion message may also include a tag list, which includes identification information for at least one tag.

[0021] In some implementations of the second aspect, the source data management function is further configured to receive a second contract information deletion message from the source tag management function. This second contract information deletion message requests the source data management function to delete the contract information of the first tag. The second contract information deletion message includes the identification information of the first tag. The source data management function is also configured to receive the second contract information deletion message and delete the first contract information based on it.

[0022] Optionally, the second contract information deletion message may further include a tag list, which includes identification information for at least one tag. In some implementations of the second aspect, the contract information management function is further configured to receive a subscription message from the transit destination of the first tag, the subscription message requesting to subscribe to the contract information of the tag, the subscription message including the transit destination information of the first tag. The contract information management function is further configured to send the second contract information to the transit destination of the first tag based on the subscription message and the transit destination information of the first tag.

[0023] The subscription information management function determines the destination of the first tag's traffic based on the subscription message and requests the subscription information for the subscribed tag. Upon receiving the first subscription information and the destination information of the first tag, the subscription information management function sends the second subscription information to the destination of the first tag's traffic according to the subscription message. This reduces the complexity of the subscription information management function; for example, it eliminates the need to determine the timing of sending the second subscription information.

[0024] Optionally, the subscription message also includes the identification information of the first tag. In this way, the subscription information management function can send the subscription information of the first tag to the transit destination of the first tag in a targeted manner, thereby reducing the signaling interaction overhead between the subscription information management function and the transit destination of the first tag.

[0025] In some implementations of the second aspect, the contract information management function is further configured to receive a contract information request message from the transit destination of the first tag. The contract information request message requests contract information for the tag, and includes information about the transit destination of the first tag. The contract information management function is also configured to send second contract information to the transit destination of the first tag based on the contract information request message and the transit destination information of the first tag.

[0026] Upon receiving a contract information request message, the contract information management function sends the second contract information to the destination of the first tag based on the destination information of the first tag. This reduces the complexity of the contract information management function; for example, it eliminates the need to determine when to send the second contract information.

[0027] Optionally, the contract information management function periodically or at regular intervals receives contract information request messages from the destination of the first tag.

[0028] Optionally, the tag information request message may also include the identification information of the first tag. In this way, the contract information management function can send the contract information of the first tag to the destination of the first tag in a targeted manner, thereby reducing the signaling interaction overhead between the contract information management function and the destination of the first tag.

[0029] In some implementations of the second aspect, the source data management function is further configured to send a first channel request message to the contract information management function. The first channel request message requests the establishment of a first data transmission channel between the source data management function and the contract information management function. The contract information management function is further configured to receive the first channel request message and, based on the first channel request message, send a first channel response message to the source data management function. The first channel response message indicates that the first data transmission channel has been successfully established. The source data management function is further configured to receive the first channel response message.

[0030] In some implementations of the second aspect, the contract information management function is further configured to receive a second channel request message from the transit destination of the first tag. The second channel request message requests the establishment of a second data transmission channel between the transit destination of the first tag and the contract information management function. The contract information management function is also configured to receive the second channel request message and, based on the second channel request message, send a second channel response message to the transit destination of the first tag. The second channel response message indicates that the second data transmission channel has been successfully established.

[0031] The second data transmission channel enhances the security of data transmission between the destination of the first tag and the contract information management function. Through this second channel, the contract information management function can send second contract information to the destination of the tag. In other words, the information exchange between the destination of the tag and the contract information management function is based on the aforementioned second data transmission channel.

[0032] Thirdly, a communication device is provided, which can be a source data management function, or a device or module for performing the source data management function.

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

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

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

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

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

[0038] Fifthly, a communication device is provided, including logic circuitry and an input / output interface for inputting and / or outputting signals, the logic circuitry for performing the method described in the first aspect and any possible implementation thereof.

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

[0040] In a seventh aspect, 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.

[0041] Eighthly, a chip or chip system is provided, 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.

[0042] In a ninth aspect, a chip is provided that 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 methods as described in the first aspect and any possible implementation thereof.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0065] Figure 1 This is a schematic diagram of the architecture of a communication system applicable to embodiments of this application. (Reference) Figure 1 The communication system includes source data management functions and contract information management functions.

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

[0067] Optionally, the communication system may also include source tag management functionality.

[0068] Optionally, the 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 one or more of the aforementioned tags, and the source data management function can manage or control the one or more of the aforementioned tags.

[0069] Both the source data management and destination data management functions can interact with the contract information management function. The source tag management function can also interact with the source data management function. When the contract information management function interacts with either the source or destination data management function, the contract information management function has pre-configured the address information of either function. In other words, the contract information management function, the source data management function, and the destination data management function can all determine the address information of the peer they are communicating with.

[0070] The term "source" can be understood as a concept related to the signing location of the tag. For example, source data management function can be understood as data management function of the signing location of the tag, and source tag management function can be understood as tag management function of the signing location of the tag. Specifically, the signing location of the tag includes one or more source data management functions, and the signing location of the tag includes one or more source tag management functions.

[0071] The term "purpose" can be understood as a concept related to the destination of the tag's movement. For example, the purpose data management function can be understood as the data management function for the destination of the tag's movement. The destination of the tag's movement includes one or more purpose data management functions.

[0072] The contract information management function is a feature in the environmental Internet of Things (IoT) used to manage the contract information of tags, providing a unified system for managing tag contract information. This function can also be replaced with other terms, such as operator contract information management function or operator contract information management center, etc., without limitation.

[0073] The source tag management function can be used to manage tags in the contracted location. For example, it can initiate tag signing processes and tag read / write processes. This function can include different entities, such as a source application function (AF), a source Internet of Things (IoT) entity, a source ambient power-enabled Internet of Things tag management function (AIOTF), or a source business operation support system (BOSS). The source IoT or source BOSS is responsible for initiating the tag signing process, the source AF is responsible for initiating the tag inventory and read / write processes, and the source AIOTF is responsible for processing tag processing requests received from the core network side. Alternatively, the source tag management function can be replaced with other terms, such as source tag control function or source tag management platform; this is not limited. Optionally, the source AF or source AIOTF can also be used to initiate tag signing processes; this is not limited either.

[0074] Data management functions (regardless of source or destination data management) can be used to manage tag contract information. For example, a source data management function stores data from tags located at the contracting location, including the tag's contract information, while a destination data management function stores data from tags located at the transit destination, also including the tag's contract information. An example of a data management function is the ambient power-enabled internet of things data manage (ADM). The term "data management function" can also be replaced with other terms, such as data management network element, without limitation.

[0075] The data management function can also execute the tag signing process. For example, when a tag signs a contract in the source data management function, the data management function can generate the tag's contract information. Here, "signing a contract" can also be understood as opening an account.

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

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

[0078] exist Figure 1 In the communication system shown, one or more of the following functions—contract information management, source tag management, destination data management, and source data management—can be physical entities or logical concepts, and there is no limitation in this regard. Furthermore, this application does not specifically limit the deployment method or location of the above functions; they can be flexibly designed according to specific application scenarios.

[0079] Figure 1 In the process, the contract information management function and the source data management function can exchange information as follows:

[0080] The source data management function receives a signing request message from the source tag management function. This signing request message is used to request the source data management function to sign a contract for the first tag. The signing request message includes the identification information of the first tag. The function also determines the first signing information of the first tag based on the signing request message. The first signing information includes the identification information of the first tag.

[0081] The source data management function receives a contract information export message from the source tag management function. The contract information export message is used to request the source data management function to send the contract information of the first tag to the contract information management function. The contract information export message includes the identification information of the first tag and the destination information of the first tag. The source data management function sends the first contract information and the destination information of the first tag to the contract information management function according to the contract information export message.

[0082] The contract information management function receives first contract information and the destination information of the first tag, determines the second contract information of the tag based on the first contract information, and sends the second contract information to the destination of the first tag based on the destination information of the first tag. The second contract information includes the identification information of the first tag.

[0083] The source data management function determines the first contract information based on the contract request message, which can be interpreted in several ways. For example, the source data management function may rename the contract request message to the first contract information; or the source data management function may set the identification information of the first tag carried in the contract request message into the new information, which can be understood as the first contract information.

[0084] The contract information management function sends second contract information to the destination of the first tag, including but not limited to the following interpretations: the contract information management function sends the second contract information to the destination data management function of the first tag's destination, or the contract information management function sends the second contract information to the receiving manufacturer of the first tag, where the receiving manufacturer of the first tag is located at the destination of the first tag's destination. The destination information of the first tag can be used to indicate the receiving manufacturer of the first tag.

[0085] Optionally, the first contract information may also include identification information for the source data management function.

[0086] The contract information management function determines the second contract information based on the first contract information, which can be interpreted in several ways. For example, the contract information management function may rename the first contract information to the second contract information; or the contract information management function may set the identification information of the first tag in the first contract information into new information, which can be understood as the second contract information; or the contract information management function may rename the first contract information to the second contract information and replace the identification information of the source data management function in the first contract information with the destination information of the tag.

[0087] The destination information of the first tag can be used to indicate the destination of the first tag. The destination information of the first tag includes, but is not limited to: the receiving manufacturer information of the first tag, and the identification information of the destination data management function of the receiving manufacturer of the first tag.

[0088] Through the architecture of source data management and contract information management functions, the source data management function executes the contract signing process for the first tag and sends the contract signing information of the first tag to the contract information management function. The contract information management function executes the contract information flow process (the flow destination information of the first tag can be used to trigger the contract information management function to send the contract signing information of the first tag to the flow destination of the first tag). This reduces the number of times the contract signing process is performed, thereby reducing the complexity of the tag contract information synchronization process in the tag flow scenario. That is, the above method can support the synchronization of tag contract information through a single contract signing process. Compared with the existing solution where both the source data management function and the destination data management function perform the contract signing process for the tag, the above method reduces the complexity of the tag contract information synchronization process in the tag flow scenario by reducing the number of times the contract signing process is performed.

[0089] The tag's identification information can be the tag's equipment serial number (ESN), the tag's index, the tag's identifier, the tag's code, the tag's number range, or both the tag's index and identifier, or both the tag's index and 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 include the tag code prefix, the region to which the tag belongs, and other information.

[0090] The difference between the first and second contract information lies in the identification information of their respective data management functions. 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 (when the destination information of the first tag is the identification information of the destination data management function). In other words, the first contract information is used for the source data management function to manage the first tag, and includes the identification information of the source data management function; the second contract information is used for the destination data management function to manage the first tag, and includes the identification information of the destination data management function. Apart from this, the information in the first and second contract information, except for the identification information of the source data management function, is the same.

[0091] One possible implementation is that both the first and second contract information include the authentication key of the first tag. The authentication key of the first tag is used in the 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 master key for storing or transmitting the tag, and is generally generated based on the AES-128 algorithm.

[0092] The authentication key for the first tag can be generated by either the source data management function or the source tag management function. When the source data management function generates the aforementioned authentication key, it can dynamically adjust the generation strategy of the tag's authentication key.

[0093] One possible implementation is to include the authentication key for the first tag in the contract request message. This eliminates the need for the source data management function to generate its own authentication key, thus reducing its functional complexity.

[0094] The contract information management function can send the second contract information to the destination of the first tag in several ways. The following describes each of these methods with specific examples.

[0095] Method A1: The contract information management function responds to the subscription request of the first tag's destination by sending the second contract information.

[0096] One possible implementation is that the contract information management function and the destination of the first tag can exchange information as follows:

[0097] The contract information management function receives subscription messages from the destination of the first tag. The subscription message is used to request the contract information of the subscribed tag (not limited to the contract information of one or more tags). The subscription message includes the destination information of the first tag.

[0098] The contract information management function sends the second contract information to the destination of the first tag based on the subscription message and the destination information of the first tag.

[0099] The subscription information management function determines the destination of the first tag's traffic based on the subscription message and requests the subscription information for the subscribed tag. Upon receiving the first subscription information and the destination information of the first tag's traffic, the subscription information management function sends the second subscription information to the destination of the first tag's traffic according to the subscription message. This reduces the complexity of the subscription information management function; for example, it eliminates the need to determine the timing of sending the second subscription information to the destination of the first tag's traffic.

[0100] In addition, the contract information management function can send contract information of multiple tags to the first tag's destination, so as to support the first tag's destination to manage the tag.

[0101] Optionally, the subscription message also includes the identification information of the first tag. In this way, the subscription information management function can send the subscription information of the first tag to the transit destination of the first tag in a targeted manner, thereby reducing the signaling interaction overhead between the subscription information management function and the transit destination of the first tag.

[0102] One possible example is that when the destination information of the first tag includes the information of the receiving manufacturer of the first tag, the subscription message can be used for the receiving manufacturer of the first tag to request subscription to the tag's contract information.

[0103] One possible example is that when the destination information of the first tag includes the identification information of the destination data management function, the subscription message can be used for the destination data management function to request the subscription information of the tag.

[0104] Method A2: The contract information management function responds to the request of the first tag's transfer destination by sending the second contract information.

[0105] One possible implementation is that the contract information management function and the destination of the first tag can exchange information as follows:

[0106] The contract information management function receives a contract information request message from the destination of the first tag. The contract information request message is used to request the contract information of the tag (not limited to the contract information of one or more tags). The contract information request message includes the destination information of the first tag.

[0107] The contract information management function sends the second contract information to the destination of the first tag based on the contract information request message and the destination information of the first tag.

[0108] Upon receiving a contract information request message, the contract information management function sends the second contract information to the destination of the first tag based on the destination information of the first tag. This reduces the complexity of the contract information management function; for example, it eliminates the need to determine when to send the second contract information.

[0109] Optionally, the contract information management function periodically or at regular intervals receives contract information request messages from the destination of the first tag.

[0110] Optionally, the tag information request message may also include the identification information of the first tag. In this way, the contract information management function can send the contract information of the first tag to the destination of the first tag in a targeted manner, thereby reducing the signaling interaction overhead between the contract information management function and the destination of the first tag.

[0111] Method A3: The contract information management function proactively sends the second contract information to the destination of the first tag.

[0112] After determining the second contract information, the contract information management function can send the second contract information to the destination of the first tag after a period of time, or it can send the second contract information to the destination of the first tag immediately. This reduces the information interaction overhead between the contract information management function and other functions.

[0113] The above descriptions of methods A1 to A3 use the example of the contract information management function sending the second contract information. The following section describes the content after the source data management function sends the first contract information to the contract information management function.

[0114] The source data management function can delete the first contract information in a variety of ways, which are described below with specific examples.

[0115] Example B1: The source data management function deletes the first contract information in response to the instruction of the contract information management function.

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

[0117] The contract information management function sends a first contract information deletion message to the source data management function. The source data management function receives the first contract information deletion message. The first contract information deletion message is used to request the source data management function to delete the contract information of the first tag. The first contract information request message includes the identification information of the first tag.

[0118] The source data management function deletes the first contract information based on the first contract information deletion message.

[0119] After receiving the first contract information deletion message, the source data management function determines the first contract information based on the identification information of the first tag carried in the first contract information deletion message, and deletes the first contract information, thereby freeing up the storage space of the source data management function.

[0120] Optionally, the first contract information deletion message may also include a tag list, which includes identification information for at least one tag. In this way, the source data management function can delete contract information for more tags, thereby freeing up more storage space for the source data management function.

[0121] Example B2: The source data management function deletes the first contract information in response to the instruction of the source tag management function.

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

[0123] The source tag management function sends a second contract information deletion message to the source data management function. The source data management function receives the second contract information deletion message. The second contract information deletion message is used to request the source data management function to delete the contract information of the tag, and the second contract information request message includes the identification information of the first tag.

[0124] The source data management function deletes the first contract information based on the second contract information deletion message.

[0125] After receiving the second contract information deletion message, the source data management function determines the first contract information based on the identification information of the first tag carried in the second contract information deletion message, and deletes the first contract information, thereby freeing up the storage space of the source data management function.

[0126] Optionally, the second contract information deletion message may also include a tag list, which includes identification information for at least one tag. In this way, the source data management function can delete contract information for more tags, thereby freeing up more storage space for the source data management function.

[0127] Example B3: The source data management function actively deletes the first contract information.

[0128] After sending the first contract information to the contract information management function, the source data management function proactively deletes the first contract information. This reduces the information interaction overhead between the source data management function and other functions.

[0129] In this embodiment of the application, the information transmission between the source data management function, the contract information management function, and the destination of the tag is realized based on the data transmission channel. The following describes the content of establishing the data transmission channel between the source data management function, the contract information management function, and the destination of the tag.

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

[0131] The source data management function sends a first channel request message to the contract information management function. This first channel request message requests the establishment of a first data transmission channel between the source data management function and the contract information management function. The contract information management function receives the first channel request message and, based on the first channel request message, sends a first channel response message to the source data management function. The first channel response message indicates that the first data transmission channel has been successfully established.

[0132] The source data management function receives response messages from the first channel.

[0133] Specifically, the source data management function sends a first channel request message to the contract information management function via the Secure Shell File Transfer Protocol (SFTP). This first channel request message includes one or more of the following: the contract information management function's Internet Protocol (IP) address / port, session identifier, and security encryption parameters (supported symmetric encryption algorithms, and the source data management function's public / private key pair). Upon receiving the first channel request message, the contract information management function determines the first transmission channel based on the parameters carried in the message and sends a first channel response message to the source data management function. This first channel response message includes one or more of the following: the source data management function's user permissions, the contract information management function's public key, and the session identifier. This embodiment does not limit the specific method by which the source data management function and the contract information management function establish a data transmission channel.

[0134] One possible implementation is that the contract information management function and the destination of the first tag can also exchange information as follows:

[0135] The destination of the first tag sends a second channel request message to the contract information management function. This second channel request message requests the establishment of a second data transmission channel between the destination of the first tag and the contract information management function. The contract information management function receives the second channel request message and, based on it, sends a second channel response message to the destination of the first tag. This second channel response message indicates that the second data transmission channel has been successfully established.

[0136] The first tag is the destination for receiving the response message from the second channel.

[0137] Specifically, the destination of the first tag sends a second channel request message to the contract information management function via the SFTP protocol. The second channel request message includes one or more of the following parameters: the IP address / port of the contract information management function, a session identifier, and security encryption parameters (supported symmetric encryption algorithms, and the public / private key pair of the source data management function). Upon receiving the second channel request message, the contract information management function determines the second transmission channel based on the parameters carried in the second channel request message and sends a second channel response message to the destination of the first tag. The second channel response message includes one or more of the following parameters: user permissions of the destination of the first tag, the public key of the contract information management function, and a session identifier. This embodiment does not limit the specific method by which the data transmission channel is established between the source data management function and the contract information management function.

[0138] The following describes the specific application system of the communication system shown in the embodiments of this application.

[0139] The communication system described 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. Satellite communication systems include satellite base stations and terminal equipment. Satellite base stations provide communication services to terminal equipment. Satellite base stations can also communicate with terrestrial base stations. Satellites can act as base stations or as 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.

[0140] The following text combines Figure 2 The communication system shown in the embodiments of this application is described in its application to a 5G network architecture. (Reference) Figure 2 The network architecture includes: tags, radio access network (RAN), source-environment power IoT tag management function (AIOTF), network repository function (NRF), network exposure function (NEF), AF, source-environment power IoT data management function (ADM), subscription information management function, destination-environment power IoT data management function, and business operation support system / IoT platform. The IoT platform can also be understood as the management platform for the Internet of Things (IoT), i.e., the platform used to manage the IoT.

[0141] exist Figure 2 In this system, tags are accessed through the RAN (Radio Access Network). The source-environment power IoT tag management function has information exchange interfaces with the RAN, the source-environment power IoT data management function, the NRF (Network Radio Frequency), the NEF (Network Electronic Frame), and the AF (Ambient Air Filter). The source-environment power IoT data management function has information exchange interfaces with the subscription information management function, the NEF, the NRF, and the AF, and can also have information exchange interfaces with the business operation support system / IoT platform. The subscription information management function also has an information exchange interface with the destination-environment power IoT data management function. The business operation support system / IoT platform / AF / environment power IoT tag management function / RAN can be understood as an example of the aforementioned source tag management function.

[0142] The following text combines Figure 3 and Figure 4 right Figure 1The information interaction between the functions shown will be further described. For ease of description, the following description uses the source tag management function as the source application function and the destination information of the first tag as the identification information of the destination-environmental power IoT data management function. Furthermore, this application does not limit... Figure 3 and Figure 4 The sequential relationship between the execution order of the steps described herein.

[0143] 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:

[0144] S301, the source application function sends a subscription request message to the source-environmental power IoT data management function. Correspondingly, the source-environmental power IoT data management function receives the subscription request message.

[0145] The signing request message includes the identification information of the first tag.

[0146] Optionally, the subscription request message also includes the authentication key of the first tag. After receiving the authentication key of the first tag, the Source-Environment Power IoT Data Management function stores it as part of the first subscription information; that is, the first subscription information of the first tag generated by the Source-Environment Power IoT Data Management function includes the authentication key of the first tag. The Source-Environment Power IoT Data Management function can perform the authentication process for the first tag based on the authentication key. Simultaneously, the authentication key of the first tag can be used for two-way authentication between the first tag and the network, ensuring the confidentiality and integrity of data and sessions.

[0147] Optionally, the subscription request message may also include the allowed access area information of the first label. The allowed access area information of the first label is used to indicate the area where the first label can be transferred. For example, if the subscription location of the first label is location A, and the allowed access area information of the first label is used to indicate location B, then the first label cannot be transferred to location C.

[0148] S302, Source-Environmental Power IoT Data Management Function determines the first contract information of the first tag.

[0149] After receiving a contract request message, the source-environment power IoT data management function stores the information carried in the contract request message, that is, it uses the information carried in the contract request message as the first contract information of the first tag.

[0150] When the signing request message does not carry the authentication key of the first tag, the source-environment power IoT data management function will automatically determine the authentication key of the first tag and can use the authentication key of the first tag as part of the first signing information.

[0151] Optionally, the first contract information may also include identification information for the source-environment power IoT data management function.

[0152] In this embodiment of the application, "saving" may also include the meaning of the source-environment power IoT data management function processing the contract request message in order to obtain the first contract information.

[0153] Optionally, the S303 source-environment power IoT data management function sends a subscription response message to the source application function. Correspondingly, the source application function receives the subscription response message.

[0154] After saving the first signing information of the first tag, the source-environment power IoT data management function sends a signing response message to the source application function. The signing response message is used to indicate that the signing of the first tag has been completed.

[0155] Optionally, the signing response message includes the identification information of the first tag. The source application function determines that the first tag has completed the signing based on the identification information of the first tag.

[0156] Optionally, the subscription response message includes the identification information of the first tag and the authentication key of the first tag. Specifically, when the subscription request message includes the authentication key of the first tag, the subscription response message may or may not include the authentication key of the first tag. When the subscription request message does not include the authentication key of the first tag, the subscription response message may include the authentication key of the first tag so that the source application function can store the authentication key of the first tag for use in subsequent authentication processes of the first tag.

[0157] S304, the source-environment power IoT data management function sends a first-channel request message to the contract information management function. The contract message management function receives the first-channel request message. See the foregoing description for details.

[0158] S305, the contract information management function sends a first-channel response message to the source-environment power IoT data management function. Correspondingly, the source-environment power IoT data management function receives the first-channel response message. For details, please refer to the foregoing description.

[0159] The source-environment power IoT data management function interacts with the contract information management function through the first data transmission channel.

[0160] S306. The destination-environmental power IoT data management function sends a second-channel request message to the contract information management function. The contract message management function receives the second-channel request message. See the foregoing description for details.

[0161] S307. The contract information management function sends a second-channel response message to the destination-environmental power IoT data management function. Correspondingly, the destination-environmental power IoT data management function receives the second-channel response message. For details, please refer to the foregoing description.

[0162] The purpose of the environmental power IoT data management function is to conduct subsequent information interaction with the contract information management function through the second data transmission channel.

[0163] In this embodiment of the application, the first tag can be transferred, that is, the first tag can be transferred from the place of signing to the destination. For example, the first tag can be transferred from place A to place B, where place A is the place of signing the first tag and place B is the destination of the first tag.

[0164] S308, the source IoT sends a contract information export message to the source-environmental power IoT data management function. Correspondingly, the source-environmental power IoT data management function receives the contract information export message.

[0165] The exported contract information message includes the identification information of the first tag and the identification information of the purpose-environment power IoT data management function.

[0166] Optionally, the contract information export message may also include at least one of the following: identification information of the contract information management function and source manufacturer information, etc. The source manufacturer information can be understood as the manufacturer of the first label.

[0167] Optionally, the second contract information may also include information about the source manufacturer.

[0168] S309, the source-environmental power IoT data management function sends the first contract information and the identification information of the destination-environmental power data management function to the contract information management function. Correspondingly, the contract information management function receives the first contract information and the identification information of the destination-environmental power data management function.

[0169] S310, the contract information management function determines the second contract information of the first tag. For details, please refer to the previous description.

[0170] Optionally, the contract information management function sends a response message to the source-environmental power IoT data management function, which indicates that the contract information management function has successfully received the first contract information and the identification information of the destination-environmental power data management function.

[0171] After receiving the first contract information, the contract information management function determines the second contract information based on the first contract information and stores the second contract information in the storage space corresponding to the directory of the destination-environment power data management function, so as to realize the orderly storage of the tag's contract information.

[0172] S311, The destination-environmental power IoT data management function sends a contract information request message to the contract information management function. Correspondingly, the contract information management function receives the contract information request message.

[0173] Upon receiving the first tag, the destination-environmental power IoT data management function sends a contract information request message to the contract information management function. Alternatively, before receiving the first tag, the destination-environmental power IoT data management function sends a contract information request message to the contract information management function. This is because the source tag management function has already sent a message to the destination-environmental power IoT data management function indicating that the first tag has been transferred. The destination-environmental power IoT data management function can then send a contract information request message to the contract information management function based on this message.

[0174] Optionally, the destination-environment power IoT data management function can periodically or periodically send contract information request messages. This reduces the information interaction overhead between the destination-environment power IoT data management function and the contract information function; for example, the destination-environment power IoT data management function does not need to frequently send contract information request messages to the contract information management function.

[0175] S312, the contract information management function sends the second contract information to the destination-environmental power IoT data management function. Correspondingly, the destination-environmental power IoT data management function receives the second contract information.

[0176] Upon receiving a contract information request message, the contract information management function retrieves the second contract information from the directory associated with the destination-environment power IoT data management function and sends the second contract information to the destination-environment power IoT data management function.

[0177] The purpose of the environmental power IoT data management function is to store the second contract information after receiving it, and to manage the first tag based on the second contract information.

[0178] Optionally, S313, the source-environment power IoT data management function, sends a contract information export response message to the source application function. Correspondingly, the source application function receives the contract information export response message.

[0179] The contract message export response message is used to indicate that the contract information of the first tag has been sent to the contract information management function.

[0180] Optionally, the contract message export response message may include identification information of the first tag.

[0181] S314. The contract information management function sends a first contract information deletion message to the source-environment power IoT data management function. Correspondingly, the source-environment power IoT data management function receives the first contract information deletion message. See details in [link to documentation]. Figure 1 The description of method B2.

[0182] S315, Source-Environmental Power IoT Data Management Function: Delete First Contract Information.

[0183] Upon receiving the deletion message for the first subscription information, the Source-Environment Power IoT data function deletes the first subscription information accordingly. For details, please refer to [link / reference needed]. Figure 1 The description of method B2.

[0184] S316, the source-environment power IoT data management function sends a first contract information deletion response message to the contract information management function. Correspondingly, the contract information management function receives the first contract information deletion response message.

[0185] The first subscription information deletion response message indicates that the source-environment power IoT data management function has deleted the subscription information of the first tag. Optionally, the first subscription information deletion response message may include the identification information of the first tag.

[0186] Using the methods described above, the contract information management function can achieve flexible management of the contract information of tags.

[0187] Figure 3 This description uses the example of the Subscription Information Management function sending a second subscription information in response to a request from the Destination-Environment Power IoT Data Management function. However, it is not limited to the scenario where the Subscription Information Management function sends a second subscription information in response to a subscription from the Destination-Environment Power IoT Data Management function. For details, please refer to [link to relevant documentation]. Figure 4 .

[0188] Figure 4 This 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:

[0189] S401, the source application function sends a subscription request message to the source-environmental power IoT data management function. Correspondingly, the source-environmental power IoT data management function receives the subscription request message. See the description in S301 for details.

[0190] S402, the source-environment power IoT data management function determines the first contract information of the first tag. See the description in S302 for details.

[0191] Optionally, in S403, the source-environment power IoT data management function sends a subscription response message to the source application function. Correspondingly, the source application function receives the subscription response message. See the description in S303 for details.

[0192] S404, the source-environment power IoT data management function sends a first-channel request message to the contract information management function. The contract message management function receives the first-channel request message. See the foregoing description for details.

[0193] S405, the contract information management function sends a first-channel response message to the source-environment power IoT data management function. Correspondingly, the source-environment power IoT data management function receives the first-channel response message.

[0194] S406. The destination-environmental power IoT data management function sends a second-channel request message to the contract information management function. The contract message management function receives the second-channel request message. See the foregoing description for details.

[0195] S407, the contract information management function sends a second-channel response message to the destination-environmental power IoT data management function. Correspondingly, the destination-environmental power IoT data management function receives the second-channel response message.

[0196] The first tag can be used for tag flow; see details below. Figure 3 The relevant description in the document.

[0197] S408: The source application function sends a subscription information export message to the source-environmental power IoT data management function. Correspondingly, the source-environmental power IoT data management function receives the subscription information export message. For a detailed description, please refer to the description in S308.

[0198] S409, the source-environmental power IoT data management function sends the first contract information and the identification information of the destination-environmental power IoT data management function to the contract information management function. Correspondingly, the contract information management function receives the first contract information and the identification information of the destination-environmental power IoT data management function.

[0199] S410, the contract information management function determines the second contract information of the first tag. For details, please refer to the previous description.

[0200] S411, The destination-environmental power IoT data management function sends a subscription message to the subscription information management function. Correspondingly, the subscription information management function receives the subscription message.

[0201] One possible example is that the purpose-environment power IoT data management function sends a subscription message to the subscription information management function after establishing a second data transmission channel with the subscription information management function.

[0202] Optionally, the subscription message may also include a list of tags, which includes identification information for one or more tags.

[0203] Optionally, the subscription message may include identification information of the first tag.

[0204] Optionally, the subscription information management function can send a subscription response message to the destination-environment power IoT data management function, which indicates that the subscription process has been completed.

[0205] Optionally, the subscription response message includes identification information for the first tag.

[0206] In this embodiment, the destination-environment power IoT data management function can send a subscription message to the subscription information management function before the first tag is transferred. This is not limited to this.

[0207] S412, the contract information management function sends the second contract information to the destination-environmental power IoT data management function. Correspondingly, the destination-environmental power IoT data management function receives the second contract information.

[0208] The purpose of the environmental power IoT data management function is to store the second contract information after receiving it, and to manage the first tag based on the second contract information.

[0209] Optionally, the S413 source-environment power IoT data management function sends a contract information export response message to the source application function. Correspondingly, the source application function receives the contract information export response message.

[0210] The contract message export response message is used to indicate that the contract information of the first tag has been sent to the contract information management function.

[0211] Optionally, the contract message export response message may include identification information of the first tag.

[0212] S414, the contract information management function sends a first contract information deletion message to the source-environment power IoT data management function. Correspondingly, the source-environment power IoT data management function receives the first contract information deletion message.

[0213] S415, Source-Environmental Power IoT Data Management Function: Delete First Contract Information.

[0214] Upon receiving the message to delete the first signed-up information, the source-environment power IoT data management function deletes the first signed-up information accordingly.

[0215] S416, the source-environment power IoT data management function sends a first contract information deletion response message to the contract information management function. Correspondingly, the contract information management function receives the first contract information deletion response message.

[0216] Using the methods described above, the contract information management function can achieve flexible management of the contract information of tags.

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

[0218] To implement the functions of the method provided in this application, the source 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.

[0219] 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 source data management functionality.

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

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

[0222] When the communication device is a source 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 source data management function to subscribe to the first tag, the subscription request message including the identification information of the first tag; determine the first subscription information of the first tag based on the subscription information request message, the first subscription information including the identification information of the first tag; control the transceiver circuit 520 to receive a subscription information export message from the source tag management function, the subscription information export message being used to request the source data management function to send the subscription information of the first tag to the subscription information management function, the subscription information export message including the identification information of the first tag and the information of the first tag's destination; send the first subscription information and the information of the first tag's destination to the subscription information management function based on the subscription information export message, the information of the first tag's destination being used to trigger the subscription information management function to send the first tag's subscription information to the first tag's destination.

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

[0224] When the communication device is for source data management, the transceiver circuit 520 can be a transceiver.

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

[0226] For details, please refer to the content shown in the above method embodiments. 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.

[0227] Figure 5The description of the communication device shown can also be applied to other functions mentioned in the foregoing method embodiments, such as source tag management function or contract information management function.

[0228] Figure 6 This is a schematic block diagram of another communication device according to an embodiment of this application. This communication device can be a source data management function used to implement the methods involved in the above embodiments.

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

[0230] When the communication device is a source 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 is used to request the source data management function to subscribe to the first tag, and the subscription request message includes the identification information of the first tag. The processing unit 620 is used to determine the first subscription information of the first tag according to the subscription request message. The first subscription information includes the identification information of the first tag. The transceiver unit 610 is used to receive a subscription information export message from the source tag management function. The subscription information export message is used to request the source data management function to send the subscription information of the first tag to the subscription information management function. The subscription information export message includes the identification information of the first tag and the transfer destination information of the first tag. The processing unit 620 is used to send the first subscription information and the transfer destination information of the first tag to the subscription information management function according to the subscription information export message. The transfer destination information of the first tag is information used to trigger the subscription information management function to send the subscription information of the first tag to the transfer destination of the tag.

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

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

[0233] 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 6The description of the communication device shown can also be applied to other functions mentioned in the foregoing method embodiments, such as source tag management function or contract information management function.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0250] 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 source data management function receives a contract request message from the source tag management function. The contract request message is used to request the source data management function to sign a contract for the first tag. The contract request message includes the identification information of the first tag. The source data management function is the data management function of the signing location of the first tag. The source tag management function is the tag management function of the signing location of the first tag. The source data management function determines the first contract information of the first tag based on the contract request message, wherein the first contract information includes the identification information of the first tag; The source data management function receives a contract information export message from the source tag management function. The contract information export message is used to request the source data management function to send the contract information of the first tag to the contract information management function. The contract information export message includes the identification information of the first tag and the destination information of the first tag. The source data management function sends the first contract information and the destination information of the first tag to the contract information management function according to the contract information export message. The destination information of the first tag is used to trigger the contract information management function to send the contract information of the first tag to the destination of the first tag.

2. The method according to claim 1, characterized in that, The method further includes: The source data management function receives a first contract information deletion message from the contract information management function. The first contract information deletion message is used to request the source data management function to delete the contract information of the first tag. The first contract information deletion message includes the identification information of the first tag. The source data management function deletes the first contract information based on the first contract information deletion message.

3. The method according to claim 1, characterized in that, The method further includes: The source data management function receives a second contract information deletion message from the source tag management function. The second contract information deletion message is used to request the source data management function to delete the contract information of the first tag. The second contract information deletion message includes the identification information of the first tag. The source data management function deletes the first contract information based on the deletion message of the second contract information.

4. The method according to any one of claims 1 to 3, characterized in that, The method further includes: The source data management function sends a first channel request message to the contract information management function. The first channel request message is used to request the establishment of a first data transmission channel between the source data management function and the contract information management function. The source data management function receives a first channel response message from the contract information management function, which indicates that the first data transmission channel has been successfully established.

5. A communication system, characterized in that, This includes source data management functions and contract information management functions; The source data management function is used to receive a contract request message from the source tag management function. The contract request message is used to request the source data management function to sign a contract for the first tag. The contract request message includes the identification information of the first tag. The source data management function is the data management function of the signing location of the first tag, and the source tag management function is the tag management function of the signing location of the first tag. The function also determines the first contract information of the first tag based on the contract request message. The first contract information includes the identification information of the first tag. The source data management function is also used to receive a contract information export message from the source tag management function. The contract information export message is used to request the source data management function to send the contract information of the first tag to the contract information management function. The contract information export message includes the identification information of the first tag and the destination information of the first tag. And based on the contract information, export a message and send the first contract information and the first tag's destination information to the contract information management function; The contract information management function is used to receive the first contract information and the destination information of the first tag, determine the second contract information of the first tag based on the first contract information, and send the second contract information to the destination of the first tag based on the destination information of the first tag. The second contract information includes the identification information of the first tag.

6. The system according to claim 5, characterized in that, The contract information management function is also used to send a first contract information deletion message to the source data management function. The first contract information deletion message is used to request the source data management function to delete the contract information of the first tag. The first contract information deletion message includes the identification information of the first tag. The source data management function is also used to receive the first contract information deletion message and delete the first contract information according to the first contract information deletion message.

7. The system according to claim 5, characterized in that, The source data management function is further configured to receive a second contract information deletion message from the source tag management function. The second contract information deletion message is used to request the source data management function to delete the contract information of the first tag. The second contract information deletion message includes the identification information of the first tag. The source data management function is also used to receive the second contract information deletion message and delete the first contract information according to the second contract information deletion message.

8. The system according to any one of claims 5 to 7, characterized in that, The contract information management function is also used to receive a subscription message from the destination of the first tag, the subscription message being used to request the contract information of the subscription tag, the subscription message including the destination information of the first tag; The contract information management function is also used to send the second contract information to the destination of the first tag based on the subscription message and the destination information of the first tag.

9. The system according to any one of claims 5 to 7, characterized in that, The contract information management function is also used to receive a contract information request message from the destination of the first tag. The contract information request message is used to request the contract information of the tag and includes the destination information of the first tag. The contract information management function is also used to send the second contract information to the destination of the first tag according to the contract information request message and the destination information of the first tag.

10. The system according to any one of claims 5 to 7, characterized in that, The source data management function is also used to send a first channel request message to the contract information management function, the first channel request message being used to request the establishment of a first data transmission channel between the source data management function and the contract information management function; The contract information management function is also used to receive the first channel request message and send a first channel response message to the source data management function according to the first channel request message. The first channel response message is used to indicate that the first data transmission channel has been successfully established. The source data management function is also used to receive the response message from the first channel.

11. The system according to any one of claims 5 to 7, characterized in that, The contract information management function is also used to receive a second channel request message from the transfer destination of the first tag. The second channel request message is used to request the establishment of a second data transmission channel between the transfer destination of the first tag and the contract information management function. The contract information management function is also used to receive the second channel request message and send a second channel response message to the transfer destination of the first tag according to the second channel request message. The second channel response message is used to indicate that the second data transmission channel has been successfully established.

12. A communication device, characterized in that, Includes a unit for performing the method according to any one of claims 1 to 4.

13. 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 by executing a computer program or instructions, or by using logic circuitry.

14. 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 to be performed.

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

16. 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 perform the method of any one of claims 1 to 4.

Images