Communication method and apparatus

Abstract

Provided in the present application are a communication method and apparatus, which can improve the efficiency of label checking. The method comprises: a first label management function network element sending a first message to a first label by means of an access network device, wherein the first message comprises an identifier of the first label management function network element, and the first label is a label registered in the first label management function network element; and the first label management function network element receiving a second message from the first label by means of the access network device, wherein the second message comprises service data of the first label, an identifier of the first label, and the identifier of the first label management function network element.

Description

Communication method and device

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of the People's Republic of China on November 25, 2023, with application number 202311600638.4 and application name "A Communication Method and Device", the entire contents of which are incorporated by reference into this application. Technical Field

[0003] The present application relates to the field of communication technology, and in particular to a communication method and device. Background Art

[0004] Currently, in passive IoT scenarios, IoT terminal devices, or tags, have the potential for large-scale deployment. For example, in logistics and warehousing, tags can be used for inventory and tracking, as well as for monitoring the environmental and cargo status of high-value goods (such as vaccines) during transportation. Another example is industrial manufacturing, where tags can be used for environmental and equipment status monitoring.

[0005] Tags have simple functions and typically rely on external stimulation to transmit information, typically from a reader. Some tags can communicate with readers by collecting and storing weak ambient energy (such as light or mechanical energy) or by using built-in microbatteries to power terminal devices. Readers can be integrated into access network equipment, which reads tags based on instructions from core network elements.

[0006] There is an urgent need in the prior art for a method for efficiently counting tags.

[0007] Summary of the Invention

[0008] The present application provides a communication method and apparatus for improving the efficiency of tag inventory.

[0009] In a first aspect, an embodiment of the present application provides a communication method, including: a first tag management function network element sends a first message to a first tag through an access network device, the first message including an identifier of the first tag management function network element, and the first tag is a tag registered in the first tag management function network element; the first tag management function network element receives a second message from the first tag through the access network device, the second message including the service data of the first tag, the identifier of the first tag and the identifier of the first tag management function network element.

[0010] In the above design, the tag actively sends data based on the identification of the tag management function network element, without the need for a reader to read the tag, which can improve the efficiency of tag inventory.

[0011] In a possible design, the first message also includes information for instructing the first tag to send service data. Based on this, the first tag can send service data after receiving the first message.

[0012] In one possible design, before the first tag management function network element sends a first message to the first tag through the access network device, it receives a third message from the first network element, where the third message is used to request the service data of the first tag, and the third message includes the identifier of the first tag and the information of the first network element, where the information of the first network element is used to determine whether the first network element has the authority to access the first tag. After the first tag management function network element receives the second message from the first tag through the access network device, it can also send the second message of the first tag to the first network element. In such a design, the first network element can be an application function network element, and the tag management function network element can forward the service data of the tag to the application function network element with access rights to the tag to complete the inventory operation on the tag.

[0013] In one possible design, the first message also includes data transmission periodic information for the first tag. Based on this, the first tag can periodically transmit service data according to the first message. Accordingly, the first tag management function network element can receive multiple second messages from the first tag through the access network device based on the data transmission periodic information for the first tag.

[0014] In one possible design, after receiving multiple second messages from the first label through the access network device, the first label management function network element receives a third message from the first network element, wherein the third message is used to request the service data of the first label, and the third message includes the identifier of the first label and the information of the first network element, and the information of the first network element is used to determine whether the first network element has access rights to the first label; then the first label management function network element sends a fourth message to the first network element, wherein the fourth message includes the identifier of the first label and the service data of the first label in the multiple second messages. In such a design, the first label management function network element can uniformly send multiple service data of the received labels to the corresponding first network element (such as the application function network element), which can reduce signaling overhead.

[0015] In one possible design, before receiving the second message from the first tag through the access network device, the first tag management function network element obtains the subscription information of the first tag from the second network element. The subscription information of the first tag includes one or more of the following: access permission information corresponding to the first tag, the access permission information is used to indicate the network element that has access permission to the first tag; data sending cycle information of the first tag; service data cache information of the first tag, the data cache information indicates the time for caching and / or deleting the service data of the first tag in the first tag management function network element. Such a design facilitates the first tag management function network element to quickly determine whether the first network element has access permission to the first tag.

[0016] In one possible design, before obtaining the subscription information of the first tag from the second network element, the first tag management function network element sends a fifth message to the second network element, where the fifth message indicates a mapping relationship between the first tag and the first tag management function network element.

[0017] In a second aspect, an embodiment of the present application provides a communication method, comprising: after completing registration of a first tag in a first tag management function network element, the first tag receives, via an access network device, a first message from the first tag management function network element, the first message including an identifier of the first tag management function network element. The first tag sends, via the access network device, a second message to the access network device, the second message including service data of the first tag, the identifier of the first tag, and an identifier of the first tag management function network element.

[0018] In one possible design, the process of registering the first tag in the first tag management function network element includes: the first tag determines the data to be sent, and establishes a communication connection with the access network device through a random access method; then the first tag registers the first tag in the first tag management function network element through the access network device.

[0019] In one possible design, the first message also includes information for instructing the first tag to send data.

[0020] In one possible design, the first message also includes data sending cycle information of the first label; the access network device sends a second message to the access network device, including: sending multiple second messages through the access network device based on the data sending cycle information of the first label.

[0021] In a third aspect, an embodiment of the present application provides a communication method, including: a first network element determines that the current location of a first tag belongs to the service scope of a first tag management function network element; the first network element sends a third message to the first tag management function network element, and the third message is used to request the service data of the first tag, and the third message includes an identifier of the first tag and information of the first tag management function network element, and the information of the first tag management function network element is used to determine that the first tag management function network element has the authority to access the first tag; the first network element receives one or more second messages of the first tag from the first tag management function network element, and the second message includes the service data of the first tag, the identifier of the first tag and the identifier of the first tag management function network element.

[0022] In such a design, based on the relationship between the tag location and the service scope of the tag management function network element, the first network element can request the service data of the first tag from the first tag management function network element corresponding to the first tag.

[0023] In a fourth aspect, an embodiment of the present application provides a communication method, which is applied to a first tag, wherein the first tag is a tag registered in a first tag management function network element, and the method includes: when the position of the first tag switches from the service scope of the first tag management function network element to the service scope of the second tag management function network element, the first tag sends a second message to the second tag management function network element through an access network device, and the second message includes the service data of the first tag and the identifier of the first tag management function network element; the first tag receives a sixth message from the second tag management function network element through the access network device, and the sixth message includes the identifier of the second tag management function network element; and sends a seventh message to the second tag management function network element through the access network device, and the seventh message includes the service data of the first tag and the identifier of the second tag management function network element.

[0024] This design can be applied to scenarios where tags are moved. Based on the identification configuration of the tag management function network element, the switching of the tag management function network element can be completed quickly to ensure the normal transmission of business data.

[0025] In one possible design, the first tag can determine the data to be sent and establish a communication connection with the access network device through random access; then send the second message to the second tag management function network element through the access network device.

[0026] In a fifth aspect, an embodiment of the present application provides a communication method, which is applied to a second label management function network element, including: receiving a second message from a first label through an access network device; wherein the second message includes the service data of the first label and the identifier of the first label management function network element, and the first label is a label registered in the first label management function network element; according to the identifier of the first label management function network element, obtaining the context information of the first label from the first label management function network element; sending a sixth message to the first label through the access network device, the sixth message including the identifier of the second label management function network element; and receiving a seventh message from the first label through the access network device, the seventh message including the service data of the first label and the identifier of the second label management function network element.

[0027] This design can be applied to scenarios where tags are moved. Based on the identification configuration of the tag management function network element, the switching of the tag management function network element can be completed quickly to ensure the normal transmission of business data.

[0028] In the sixth aspect, an embodiment of the present application provides a communication device, which can be used to execute the method of the first aspect. The device can be a first label management function network element, or the device can be a component in the first label management function network element (for example, a chip, or a chip system, or a circuit), or it can be a device that can be matched and used with the first label management function network element.

[0029] In one possible implementation, the communication device may include a module or unit corresponding to each of the methods / operations / steps / actions described in the first aspect. The module or unit may be a hardware circuit, software, or a combination of a hardware circuit and software. In one possible implementation, the device may include a processing unit (also referred to as a processing module) and a communication unit (also referred to as a communication module), wherein the communication unit may be used to perform the functions of receiving and / or sending, and the processing unit may be used to perform the above-mentioned first aspect or any possible implementation method of the first aspect.

[0030] The communication unit is used to send a first message to the first label through the first label management function network element under the control of the processing unit, wherein the first message includes the identifier of the first label management function network element, and the first label is a label registered in the first label management function network element.

[0031] The communication unit is further used to receive a second message from the first label through the first label management function network element, where the second message includes the service data of the first label, the identifier of the first label and the identifier of the first label management function network element.

[0032] In one possible design, the first message also includes information for instructing the first tag to send service data.

[0033] In one possible design, the communication unit is further configured to receive a third message from the first network element before sending the first message to the first label through the access network device, wherein the third message is used to request the service data of the first label, and the third message includes the identifier of the first label and information of the first network element, and the information of the first network element is used to determine whether the first network element has the authority to access the first label. The communication unit is further configured to send the second message of the first label to the first network element after receiving the second message from the first label through the access network device.

[0034] In one possible design, the first message also includes data transmission periodic information for the first tag. Based on this, the first tag can periodically transmit service data according to the first message. Accordingly, the first tag management function network element can receive multiple second messages from the first tag through the access network device based on the data transmission periodic information for the first tag.

[0035] In one possible design, the communication unit is further configured to receive a third message from the first network element after receiving multiple second messages from the first label through the access network device, wherein the third message is used to request the service data of the first label, and the third message includes an identifier of the first label and information of the first network element, and the information of the first network element is used to determine whether the first network element has access rights to the first label. The communication unit is further configured to send a fourth message to the first network element under the control of the processing unit, wherein the fourth message includes an identifier of the first label and the service data of the first label in the multiple second messages.

[0036] In one possible design, the communication unit is also used to obtain the signing information of the first tag from the second network element before receiving the second message from the first tag through the access network device, and the signing information of the first tag includes one or more of the following: access permission information corresponding to the first tag, and the access permission information is used to indicate the network element that has access permission to the first tag; data sending cycle information of the first tag; service data cache information of the first tag, and the data cache information indicates the time to cache and / or delete the service data of the first tag in the first tag management function network element.

[0037] In one possible design, the communication unit is further used to send a fifth message to the second network element before obtaining the subscription information of the first label from the second network element, and the fifth message indicates the mapping relationship between the first label and the first label management function network element.

[0038] In the seventh aspect, an embodiment of the present application provides a communication device, which can be used to execute the method of the second aspect. The device can be a first tag, or the device can be a component in the first tag (for example, a chip, or a chip system, or a circuit), or it can be a device that can be used in combination with the first tag.

[0039] In one possible implementation, the communication device may include a module or unit corresponding to each of the methods / operations / steps / actions described in the second aspect. The module or unit may be a hardware circuit, software, or a combination of a hardware circuit and software. In one possible implementation, the device may include a processing unit (also referred to as a processing module) and a communication unit (also referred to as a communication module), wherein the communication unit may be used to perform the functions of receiving and / or sending, and the processing unit may be used to perform the above-mentioned second aspect or any possible implementation method of the second aspect.

[0040] The communication unit is used to receive a first message from the first label management function network element through the access network device after completing the registration of the first label in the first label management function network element, where the first message includes an identifier of the first label management function network element.

[0041] The communication unit is also used to send a second message to the access network device through the access network device under the control of the processing unit, wherein the second message includes the business data of the first label, the identifier of the first label and the identifier of the first label management function network element.

[0042] In one possible design, the processing unit is also used to determine the data to be sent; the communication unit is also used to establish a communication connection with the access network device through a random access method; the processing unit is also used to register the first tag in the first tag management function network element through the access network device.

[0043] In one possible design, the first message also includes information for instructing the first tag to send data.

[0044] In one possible design, the first message also includes data sending cycle information of the first tag; the communication unit is specifically used to send multiple second messages through the access network device based on the data sending cycle information of the first tag.

[0045] In the eighth aspect, an embodiment of the present application provides a communication device, which can be used to execute the method of the third aspect. The device can be a first network element, or the device can be a component in the first network element (for example, a chip, or a chip system, or a circuit), or it can be a device that can be used in combination with the first network element.

[0046] In one possible implementation, the communication device may include a module or unit corresponding to each of the methods / operations / steps / actions described in the third aspect. The module or unit may be a hardware circuit, software, or a combination of a hardware circuit and software. In one possible implementation, the device may include a processing unit (also referred to as a processing module) and a communication unit (also referred to as a communication module), wherein the communication unit may be used to perform the functions of receiving and / or sending, and the processing unit may be used to perform the third aspect or any possible implementation method of the third aspect.

[0047] The processing unit is configured to determine that the current location of the first tag belongs to the service range of the first tag management function network element.

[0048] A communication unit is used to send a third message to the first label management function network element, wherein the third message is used to request the business data of the first label. The third message includes the identifier of the first label and the information of the first label management function network element. The information of the first label management function network element is used to determine whether the first label management function network element has the authority to access the first label.

[0049] The communication unit is also used to receive one or more second messages of the first label from the first label management function network element, where the second message includes the business data of the first label, the identifier of the first label and the identifier of the first label management function network element.

[0050] In a ninth aspect, an embodiment of the present application provides a communication device, which can be used to perform the method of the fourth aspect. The device can be a first tag, or the device can be a component in the first tag (for example, a chip, or a chip system, or a circuit), or can be a device that can be used in conjunction with the first tag. The first tag is a tag registered in a first tag management function network element.

[0051] In one possible implementation, the communication device may include a module or unit corresponding to each of the methods / operations / steps / actions described in the fourth aspect. The module or unit may be a hardware circuit, software, or a combination of a hardware circuit and software. In one possible implementation, the device may include a processing unit (also referred to as a processing module) and a communication unit (also referred to as a communication module), wherein the communication unit may be used to perform the functions of receiving and / or sending, and the processing unit may be used to perform the above-mentioned fourth aspect or any possible implementation method of the fourth aspect.

[0052] When the position of the first tag switches from the service scope of the first tag management function network element to the service scope of the second tag management function network element, the communication unit is used to send a second message to the second tag management function network element through the access network device under the control of the processing unit, and the second message includes the service data of the first tag and the identifier of the first tag management function network element.

[0053] The communication unit is also used to receive a sixth message from the second label management function network element through the access network device, wherein the sixth message includes the identifier of the second label management function network element; and send a seventh message to the second label management function network element through the access network device, wherein the seventh message includes the service data of the first label and the identifier of the second label management function network element.

[0054] In one possible design, the processing unit is also used to determine the data to be sent and establish a communication connection with the access network device through random access; the communication unit is also used to send the second message to the second label management function network element through the access network device.

[0055] In a tenth aspect, an embodiment of the present application provides a communication device, which can be used to perform the method of the fifth aspect. The device can be a second label management function network element, or the device can be a component (for example, a chip, or a chip system, or a circuit) in the second label management function network element, or can be a device that can be used in conjunction with the second label management function network element. The second label management function network element is a label registered in the second label management function network element.

[0056] In one possible implementation, the communication device may include a module or unit corresponding to each of the methods / operations / steps / actions described in the fifth aspect. The module or unit may be a hardware circuit, software, or a combination of a hardware circuit and software. In one possible implementation, the device may include a processing unit (also referred to as a processing module) and a communication unit (also referred to as a communication module), wherein the communication unit may be used to perform the functions of receiving and / or sending, and the processing unit may be used to perform the above-mentioned fifth aspect or any possible implementation method of the fifth aspect.

[0057] A communication unit, used to receive a second message from a first tag through an access network device; wherein the second message includes the business data of the first tag and the identifier of the first tag management function network element, and the first tag is a tag registered in the first tag management function network element.

[0058] The processing unit is configured to obtain context information of the first tag from the first tag management function network element according to the identifier of the first tag management function network element.

[0059] The communication unit is also used to send a sixth message to the first label through the access network device, wherein the sixth message includes the identifier of the second label management function network element; and receive a seventh message from the first label through the access network device, wherein the seventh message includes the service data of the first label and the identifier of the second label management function network element.

[0060] In an eleventh aspect, an embodiment of the present application provides a communication device, comprising a processor configured to implement the method described in any one of the first to fifth aspects above. The processor is coupled to a memory configured to store instructions and data. When the processor executes the instructions stored in the memory, the method described in the first aspect can be implemented. Optionally, the communication device may further comprise a memory; the communication device may further comprise a communication interface configured to enable the communication device to communicate with other devices. Exemplarily, the communication interface may be a transceiver, circuit, bus, module, pin, or other type of communication interface.

[0061] In the twelfth aspect, an embodiment of the present application provides a communication device, comprising a logic circuit and an interface circuit; the interface circuit is used to communicate with a module outside the communication device; the logic circuit is used to execute a computer program so that the communication device executes the method provided in any one of the above-mentioned first to fifth aspects.

[0062] In the thirteenth aspect, an embodiment of the present application further provides a computer program, which, when executed on a computer, enables the computer to execute the method provided in any one of the first to fifth aspects above.

[0063] In the fourteenth aspect, an embodiment of the present application further provides a computer program product, comprising instructions, which, when executed on a computer, enable the computer to execute the method provided in any one of the first to fifth aspects above.

[0064] In the fifteenth aspect, an embodiment of the present application further provides a computer-readable storage medium, in which a computer program or instruction is stored. When the computer program or instruction is run on a computer, the computer executes the method provided in any one of the first to fifth aspects above.

[0065] In the sixteenth aspect, an embodiment of the present application further provides a chip, which is used to read a computer program stored in a memory and execute the method provided in any one of the first to fifth aspects above.

[0066] In a seventeenth aspect, an embodiment of the present application further provides a chip system, which includes a processor for supporting a computer device to implement the method provided in any one of the first to fifth aspects above. In one possible design, the chip system also includes a memory for storing the necessary programs and data for the computer device. The chip system can be composed of a chip, or it can include a chip and other discrete devices.

[0067] For the effects of the solutions provided in any of the second to seventeenth aspects above, reference can be made to the corresponding description in the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0068] FIG1 is a schematic diagram of the architecture of a communication system;

[0069] FIG2 is a schematic diagram of the architecture of another communication system;

[0070] Figures 3 to 10 are flowcharts of several communication methods provided in embodiments of the present application;

[0071] FIG11 is a schematic structural diagram of a communication device according to an embodiment of the present application;

[0072] FIG12 is a schematic structural diagram of a communication device according to an embodiment of the present application. DETAILED DESCRIPTION

[0073] In order to make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the embodiments of the present application will be further described in detail below with reference to the accompanying drawings.

[0074] The at least one (item) involved in the embodiments of the present application as follows indicates one (item) or more (items). More (items) refers to two (items) or more than two (items). "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. In addition, it should be understood that although the terms first, second, etc. may be used to describe each object in the embodiments of the present application, these objects should not be limited to these terms. These terms are only used to distinguish each object from each other.

[0075] The terms "including" and "having" and any variations thereof mentioned in the following description of the embodiments of the present application are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally includes other steps or units that are not listed, or optionally includes other steps or units that are inherent to these processes, methods, products or devices. It should be noted that, in the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or descriptions. Any method or design described as "exemplary" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other methods or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a concrete way.

[0076] Figure 1 shows a schematic diagram of a network architecture applicable to a communication method provided in an embodiment of the present application. As shown in Figure 1, the network architecture may include an access network and a core network. Terminal devices access a data network (DN) through the access network and the core network.

[0077] Terminal devices can include tags, user equipment (UE), mobile stations, mobile terminals, and application clients. They can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), the Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, and smart cities. Terminal devices can include mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, urban air vehicles (such as drones and helicopters), ships, robots, robotic arms, and smart home devices.

[0078] In this application, the device for implementing the function of a terminal device can be a terminal device, or a device that can support the terminal device to implement the function, such as a chip system, which can be installed in the terminal device. In this application, the chip system can be composed of a chip, or it can include a chip and other discrete devices. In the technical solutions provided in this application, the technical solutions provided in the embodiments of this application are described by taking the terminal device as an example of the device for implementing the function of a tag.

[0079] The access network is used to implement access-related functions. It can provide network access for authorized users in a specific area and determine transmission links of varying quality for user data transmission based on user level and service requirements. The access network forwards control signals and user data between the UE and the core network. The access network may include access network equipment, which can be equipment that provides access to the UE and can include radio access network (RAN) equipment and wired access network equipment. RAN equipment is primarily responsible for radio resource management, quality of service (QoS) management, data compression and encryption, and other functions on the air interface side. RAN equipment can include various types of base stations, such as macro base stations, micro base stations (also known as small cells), relay stations, access points, and balloon stations. In systems using different radio access technologies, the names of devices with base station functions may vary. For example, in 5G systems, they are called RAN or next-generation Node basestation (gNB), and in long-term evolution (LTE) systems, they are called evolved NodeB (eNB or eNodeB).

[0080] In some deployments, a gNB may include a centralized unit (CU) and a distributed unit (DU). The gNB may also include an active antenna unit (AAU). The CU may implement some gNB functions, while the DU may implement other gNB functions. For example, the CU is responsible for processing non-real-time protocols and services, implementing the functions of the radio resource control (RRC) and packet data convergence protocol (PDCP) layers. The DU is responsible for processing physical layer protocols and real-time services, implementing the functions of the radio link control (RLC), media access control (MAC), and physical (PHY) layers. The AAU implements some physical layer processing functions, RF processing, and active antenna-related functions. RRC layer information is generated by the CU and ultimately encapsulated by the DU's PHY layer into PHY layer information, or is converted from PHY layer information. Therefore, in this architecture, higher-layer signaling, such as RRC layer signaling, can also be considered to be sent by the DU, or by a combination of the DU and the AAU. It is understood that the access network device may include one or more of a CU node, a DU node, and an AAU node. In addition, the CU may be classified as an access network device in the access network, or as an access network device in the CN, which is not limited in this application.

[0081] Access network equipment and terminal devices can be fixed or mobile. They can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; on water; or in the air on aircraft, balloons, and satellites. The embodiments of this application do not limit the application scenarios of access network equipment and terminal devices.

[0082] The core network is responsible for maintaining mobile network subscription data and providing UE with session management, mobility management, policy management, and security authentication functions. The core network includes but is not limited to one or more of the following network elements: application function (AF) network element, unified data management (UDM) network element, unified data repository (UDR) network element, policy control function (PCF) network element, session management function (SMF) network element, access and mobility management function (AMF) network element, network repository function (NRF) network element, authentication server function (AUSF) network element, network exposure function (NEF) network element, user plane function (UPF) network element, and network data analytics function (NWDAF) network element.

[0083] The access and mobility management function network element is mainly responsible for mobility management in the mobile network, such as user location update, user registration network, user switching, allocation of user temporary identity, authentication and authorization of users, etc. In 5G, the access and mobility management function network element can be an AMF network element. In future communications such as the 6th generation (6G), the mobility management network element can still be an AMF network element or have other names, which are not limited in this application.

[0084] The session management network element is responsible for managing the protocol data unit (PDU) session of the terminal device. The PDU session is a channel for transmitting PDUs, and the terminal device needs to transmit PDUs to each other with the DN through the PDU session. The SMF network element is responsible for establishing, maintaining and deleting PDU sessions. The session management network element includes session management (such as session establishment, modification and release, including tunnel maintenance between user plane network elements and access network equipment), selection and control of user plane network elements, service and session continuity (SSC) mode selection, roaming and other session-related functions. In 5G, the session management network element can be an SMF network element. In future communications such as 6G, the session management network element can still be an SMF network element, or have other names, which are not limited in this application.

[0085] The user plane function network element is the gateway for communication between the mobile network and the data network (DN). It is mainly responsible for forwarding and receiving user data. For example, it can receive user data from the data network and transmit it to the UE through the access network device; it can also receive user data from the UE through the access network device and forward it to the data network. In addition, the user plane function network element also includes user-plane related functions such as data packet detection, service usage reporting, Quality of Service (QoS) processing, legal monitoring, uplink data packet detection, downlink data packet storage, etc. In 5G, the user plane function network element can be a UPF network element. In future communications such as 6G, the user plane function network element can still be a UPF network element, or have other names, which are not limited in this application.

[0086] The unified data management network element is responsible for storing information such as the subscriber's subscriber permanent identifier (SUPI), credentials, security context, and subscription data. The information stored by the unified data management network element can be used for authentication and authorization of terminal devices to access the mobile network. The above-mentioned subscribers can specifically be users who use services provided by the mobile network, such as users who use China Telecom's mobile phone SIM cards, or users who use China Mobile's mobile phone SIM cards, etc. The subscriber's subscription permanent identifier (SUPI) can be the number of the mobile phone SIM card, etc. The subscriber's credentials and security context can be small files storing the encryption key of the mobile phone SIM card or information related to the encryption of the mobile phone SIM card, which are used for authentication and / or authorization. The above-mentioned security context can be data (cookie) or token stored on the user's local terminal (such as a mobile phone). The subscriber's subscription data can be the supporting services of the mobile phone SIM card, such as the data package of the mobile phone SIM card or the network used. It should be noted that permanent identifiers, credentials, security contexts, authentication data (cookies), and tokens are equivalent to authentication and authorization-related information. In this application document, for the sake of convenience of description, no distinction or restriction is made. Unless otherwise specified, the embodiments of this application will be described using security context as an example, but the embodiments of this application are also applicable to authentication and / or authorization information expressed in other ways. In 5G, the unified data management network element can be a UDM network element. In future communications such as 6G, the unified data management network element can still be a UDM network element, or have other names, which are not limited in this application.

[0087] The unified database network element is responsible for accessing data such as contract data, policy data, and application data. In 5G, the unified database network element can be a UDR network element. In future communications such as 6G, the unified database network element can still be a UDR network element or have other names, which are not limited in this application.

[0088] The network open network element opens the external interface of the mobile network to a third party in a secure manner. When the session management network element needs to communicate with the network element of a third party, the network open network element can serve as a relay for the communication between the session management network element and the network element of the third party. When the network open network element acts as a relay, it can translate the identification information of the subscriber, as well as the identification information of the third-party network element. For example, when the network open network element sends the SUPI of the subscriber from the mobile network to the third party, it can translate the SUPI into its corresponding external identity (identity, ID). Conversely, when the network open network element sends the external ID (the network element ID of the third party) to the mobile network, it can translate it into SUPI. In 5G, the network open network element can be a NEF network element. In future communications such as 6G, the network open network element can still be a NEF network element, or have other names, which are not limited in this application.

[0089] The application function network element is used to convey the requirements of the application side to the network side, such as QoS requirements or user status event subscriptions. The application function network element can be a third-party functional entity or an application server deployed by the operator, such as the IP Multimedia Subsystem (IMS) voice call service. In 5G, the application function network element can be an AF network element. In future communications such as 6G, the application function network element can still be an AF network element or have other names, which are not limited in this application.

[0090] The policy control network element is used to provide PDU session policies to the session management network element. Policies may include billing-related policies, QoS-related policies, and authorization-related policies. In 5G, the policy control network element may be a PCF network element. In future communications such as 6G, the policy control network element may still be a PCF network element or have other names, which are not limited in this application.

[0091] The network storage function network element can be used to provide network element discovery function, and provide network element information corresponding to the network element type based on the request of other network elements. The network storage function network element also provides network element management services, such as network element registration, update, deregistration, and network element status subscription and push. In 5G, the network storage function network element can be an NRF network element. In future communications such as 6G, the network storage function network element can still be an NRF network element, or have other names, which are not limited in this application.

[0092] The authentication server function network element is responsible for authenticating the terminal device and verifying the legitimacy of the terminal device. In 5G, the authentication server function network element can be an AUSF network element. In future communications such as 6G, the authentication server function network element can still be an AUSF network element, or have other names, which are not limited in this application.

[0093] The network data analysis function network element provides functions such as network data collection and analysis based on technologies such as big data and artificial intelligence. In 5G, the network data analysis function network element can be an NWDAF network element. In future communications such as 6G, the network data analysis function network element can still be an NWDAF network element or have other names, which are not limited in this application.

[0094] A DN can be deployed with a variety of services, providing data and / or voice services to terminal devices. For example, a DN is the private network of a smart factory. Sensors installed in the workshop can be terminal devices. The DN is also home to a sensor control server, which can provide services to the sensors. The sensors can communicate with the control server, receive instructions from the control server, and transmit collected sensor data to the control server based on the instructions. Another example is a DN that is a company's internal office network. Employees' mobile phones or computers can be terminal devices, allowing them to access information and data resources on the company's internal office network.

[0095] The above-mentioned AF network element, UDM network element, UDR network element, PCF network element, SMF network element, AMF network element, NRF network element, AUSF network element, NEF network element, UPF network element, and NWDAF network element can also be referred to as AF, UDM, UDR, PCF, SMF, AMF, NRF, AUSF, NEF, UPF, and NWDAF, respectively, as shown in Figure 1.

[0096] In Figure 1, Nausf, Nnef, Nnrf, Namf, Npcf, Nsmf, Nudm, Nudr, Naf, and Nnwdaf are service-oriented interfaces provided by the aforementioned AUSF, NEF, NRF, AMF, PCF, SMF, UDM, UDR, AF, and NWDAF, respectively, and are used to invoke corresponding service-oriented operations. N1, N2, N3, N4, and N6 are interface serial numbers, and their meanings are as follows:

[0097] 1) N1: The interface between AMF and terminal devices, which can be used to deliver non-access stratum (NAS) signaling (such as QoS rules from AMF) to terminal devices.

[0098] 2) N2: The interface between AMF and access network equipment, which can be used to transmit radio bearer control information from the core network side to the access network equipment.

[0099] 3) N3: The interface between the access network equipment and UPF, mainly used to transmit uplink and downlink user plane data between the access network equipment and UPF.

[0100] 4) N4: The interface between SMF and UPF can be used to transmit information between the control plane and the user plane, including controlling the issuance of forwarding rules, QoS rules, traffic statistics rules, etc. for the user plane and reporting information on the user plane.

[0101] 5) N6: Interface between UPF and DN, used to transmit uplink and downlink user data flows between UPF and DN.

[0102] It is understood that the above-mentioned network element or function can be a network element in a hardware device, a software function running on dedicated hardware, or a virtualized function instantiated on a platform (e.g., a cloud platform). As a possible implementation method, the above-mentioned network element or function can be implemented by a single device, or can be implemented by multiple devices together, or can be a functional module within a single device, which is not specifically limited in the embodiments of the present application.

[0103] Figure 2 shows a schematic diagram of another communication system architecture applicable to embodiments of the present application. As shown in Figure 2, the communication system may include tags, access network devices, tag management function network elements, UDMs, NEFs, and AFs. The details of the terminal devices, access network devices, UDMs, NEFs, and AFs can be found in the description of Figure 1, and any repetitions will not be repeated.

[0104] Among them, the tag management function network element can be a TAG Management Function (TMF) network element, abbreviated as TMF. The TMF can support the tag management function, which supports various operations for tag management. The TMF can communicate directly with the AF or communicate with the AF through the NEF. After receiving an operation request from the AF, the TMF can operate on the tag through the access network device. The TMF can also communicate with the UDM / UDR. For example, the TMF can obtain information stored in the UDM / UDR.

[0105] Furthermore, the TMF can be a standalone network element or can be co-located with other network elements. For example, the TMF can be co-located with the NEF or the AMF. In this way, the NEF or AMF can implement the functions of the TMF. Furthermore, the term "TMF" is merely an example. Any device that can implement the functions corresponding to the TMF in the embodiments of this application can be understood as the TMF described herein.

[0106] It is understood that the above-mentioned network element or function can be a network element in a hardware device, a software function running on dedicated hardware, or a virtualized function instantiated on a platform (e.g., a cloud platform). As a possible implementation method, the above-mentioned network element or function can be implemented by a single device, or can be implemented by multiple devices together, or can be a functional module within a single device, which is not specifically limited in the embodiments of the present application.

[0107] It should be noted that the communication system shown in Figure 1 or Figure 2 does not constitute a limitation on the communication system to which the embodiments of the present application can be applied. Therefore, the communication method provided in the embodiments of the present application can also be applied to communication systems of various standards, such as: long term evolution (LTE) communication system, 5G communication system, 6G communication system and future communication system, vehicle to everything (V2X), long term evolution-vehicle network (LTE-vehicle, LTE-V), vehicle to vehicle (V2V), vehicle network, machine type communication (MTC), IoT, long term evolution-machine to machine (LTE-machine to machine, LTE-M), machine to machine (M2M), Internet of Things, etc. In addition, it should be noted that the embodiments of the present application do not limit the names of the network elements in the communication system. For example, in communication systems of different standards, each network element may have other names; for example, when multiple network elements are integrated into the same physical device, the physical device may also have other names.

[0108] The embodiment of the present application provides an active tag that can actively communicate with the access network equipment, referred to as an active tag (Active tag), which can collect data and actively report it to the access network equipment. In the communication system shown in Figure 2, the AF can request the data of the active tag from the TMF, and the access network equipment can forward the business data reported by the active tag to the TMF, and then the TMF can feed back the business data of the active tag to the AF in response to the request of the AF. Such a design does not require the use of a reader to read and write tag data, can shorten the time to obtain the business data of the tag, and thus improve the efficiency of the tag inventory. The interaction process between the aforementioned network elements is further described in detail below with reference to the accompanying drawings.

[0109] FIG3 shows a first communication method provided by an embodiment of the present application, which can be applied to non-mobile scenarios, that is, communication scenarios where the tag is in a stationary state. The method mainly includes the following process.

[0110] S301: Register a first tag in a first tag management function network element.

[0111] Among them, the first tag management function network element can be the TMF in Figure 2, and the first tag is a terminal device within the coverage of the access network device that establishes an N2 connection with the TMF. Specifically, the first tag can establish a communication connection with the access network device through a random access method when it is determined that there is business data to be sent; then, the first tag can be registered in the first tag management function network element through the access network device. For example, the first tag can send a registration request message to the first tag management function network element through the access network device, and then the first tag and the first tag management function network element perform a tag authentication and security negotiation process to authenticate and authorize the initial access of the first tag. Optionally, the registration request message includes an identifier of the first tag, such as the IP address and ID of the first tag.

[0112] It can be understood that the access network device in the embodiment of the present application is a device that supports active tag communication.

[0113] S302: The first label management function network element sends a first message to the first label through the access network device.

[0114] The first message includes an identifier of the first tag management function network element, such as an IP address, ID, or other information indicating the first tag management function network element. Optionally, the first message may be a registration acceptance message sent by the first tag management function network element in response to a registration request message for the first tag. The first message also includes information indicating that the first tag is sending service data.

[0115] Optionally, the first message may further include data sending cycle information of the first tag, that is, specifically instructing the first tag to periodically update and send service data according to the data sending cycle information.

[0116] It is understandable that after receiving the identifier of the first tag management function network element, the first tag may save the identifier of the first tag management function network element locally, and may save it in a local storage space.

[0117] S303: The first label sends a second message to the first label management function network element through the access network device.

[0118] The second message includes the service data of the first tag, the identifier of the first tag, and the identifier of the first tag management function network element. Optionally, if the first message received by the first tag includes data transmission cycle information for the first tag, the first tag may periodically send multiple second messages to the first tag management function network element via the access network device according to the data transmission cycle information. It is understood that each of the multiple second messages may include different service data for the first tag, and the data transmission cycle information may be replaced by a service data update cycle. In a tag inventory scenario, the first tag management function network element may also send the service data for the first tag to other network elements with tag inventory requirements, such as application network elements AF. Specifically, in this embodiment of the present application, the other network elements with tag inventory requirements are referred to as first network elements. The first network element may initiate a request for service data for a specified tag from the first tag management function network element. Upon receiving the service data for the specified tag, the first tag management function network element may then feedback the service data for the specified tag to the first network element. For example, this may be implemented with reference to S304 and S305 below.

[0119] S304: The first network element sends a third message to the first label management function network element.

[0120] The third message is used to request the service data of the first tag. Specifically, the third message may include the identifier of the first tag and information about the first network element. Exemplarily, the first network element is the AF, and the first tag management function network element is the TMF. In a scenario where the TMF communicates directly with the AF, the AF may send the third message directly to the TMF; alternatively, in a scenario where the TMF communicates directly with the AF through the NEF, the AF may send the third message to the TMF through the NEF.

[0121] It is understandable that the embodiment of the present application does not limit the execution order of S304 and S301 to S303.

[0122] In one possible implementation, S304 may be executed first and then S301 to S303, that is, the first tag management function network element may complete the registration of the first tag in the first tag management function network element and send the identifier of the first tag management function network element to the first tag when the first network element requests the service data of the first tag, so that the first tag uses the identifier of the first tag management function network element to actively send service data to the first tag management function network element through the access network device. Specifically, after receiving the third message, the first tag management function network element may first determine whether the first network element has access rights to the first tag based on the information of the first network element, or alternatively describe that the first tag management function network element may determine whether the first network element can obtain the service data of the first tag based on the information of the first network element. For example, the information of the first network element may include the identifier of the first network element. The first label management function network element may query the contract information of the first label from the second network element (such as UDM or UDR) that stores the contract information of the first label. The contract information of the first label includes the identifier of the network element that has access rights to the first label; if the contract information of the first label includes the identifier of the first network element, then the first label management function network element can determine that the first network element has access rights to the first label; if the contract information of the first label does not include the identifier of the first network element, then the first label management function network element can determine that the first network element does not have access rights to the first label.

[0123] Based on this, when the first network element has access rights to the first tag, the first tag management function network element can continue to execute steps S301 to S303 and S305 after executing S304; when the first network element does not have access rights to the first tag, the first tag management function network element will no longer execute steps S301 to S303 and S305.

[0124] In another possible implementation, S301 to S303 can be executed first and then S304, that is, the first tag management function network element can complete the registration of the first tag in the first tag management function network element by itself and send the identifier of the first tag management function network element to the first tag, so that the first tag uses the identifier of the first tag management function network element to actively send business data to the first tag management function network element through the access network device; further, after receiving the third message, the first tag management function network element can first determine whether the first network element has access rights to the first tag based on the information of the first network element. For example, the information of the first network element may include the identifier of the first network element. The first label management function network element may query the contract information of the first label from the second network element (such as UDM or UDR) that stores the contract information of the first label. The contract information of the first label includes the identifier of the network element that has access rights to the first label; if the contract information of the first label includes the identifier of the first network element, then the first label management function network element can determine that the first network element has access rights to the first label; if the contract information of the first label does not include the identifier of the first network element, then the first label management function network element can determine that the first network element does not have access rights to the first label.

[0125] Based on this, when the first network element has access rights to the first tag, the first tag management function network element continues to execute S305 after executing S301 to S304; when the first network element does not have access rights to the first tag, the first tag management function network element will no longer execute step S305.

[0126] Optionally, the subscription information of the first TAG includes the following: the ID of at least one AF that has access rights to the first TAG, the data sending cycle information of the first TAG, and the cache policy information of the service data of the first TAG in the TMF.

[0127] S305: The first label management function network element sends the second message or the fourth message to the first network element.

[0128] In a possible implementation, the first label management function network element may forward the second message of the first label in real time, that is, the first label management function network element immediately sends each second message received to the first network element.

[0129] For example, the first message sent by the first tag management function network element in S302 includes information for indicating that the first tag sends service data, and the first message does not include data sending cycle information. Then the first tag only sends the second message once based on the first message, and the first tag management function network element feeds back to the first network element when receiving a second message.

[0130] In another possible implementation, the first tag management function network element can also cache multiple second messages, which correspond to multiple business data of the first tag, and then send a fourth message to the first network element, which includes the identifier of the first tag and multiple business data of the first tag.

[0131] For example, the first message sent by the first tag management function network element in S302 includes information for indicating that the first tag sends service data, and the first message includes data sending cycle information, then the first tag periodically sends the second message based on the first message, and the first tag management function network element can periodically receive the second message and cache it, that is, cache multiple second messages.

[0132] The above method can be applied to communication scenarios where the tags are non-mobile tags. By configuring the tag with the identifier of the tag management network element, when there is a need to report business data, the tag can actively report business data to the tag management network element based on the identifier of the tag network element. Then, the tag management network element can forward the tag business data to the network element with the tag inventory requirement, which can improve the efficiency of tag inventory.

[0133] In addition, it can be understood that in one possible design, the method shown in Figure 3 can be applied to the scenario where the first tag has the first need to report business data to the first tag management function network element. The first tag can save the identifier of the first tag management function network element, so that in the subsequent scenario where the first tag has the need to report business data, the first tag can directly send the business data to the first tag management function network element after random access. For example, the first tag can carry the business data in the registration request message. For example, the first tag can skip the registration process and, based on the obtained identifier of the first tag management function network element, directly send a message carrying the business data to be reported and the identifier of the first tag to the first tag management function network element; or it can also be described as the first tag skipping the registration process and directly sending data sending information, which carries the identifier of the first tag management function network element, the first tag identifier and the business data to be reported. In another possible design, the first tag can be implemented according to the method shown in Figure 3 each time there is a need to report business data.

[0134] For ease of implementation, the specific implementation process of the method described in Figure 3 is described in detail in Figures 4 and 5 below, taking the interactions among TAG, RAN, TMF, UDM, NEF, and AF as examples. It can be understood that the TAG in Figures 4 and 5 is an example of a first tag, the RAN is an example of an access network device, the UDM refers to a network element that stores subscription information for one or more tags, the TMF is an example of a first tag management function network element, the AF is an example of a first network element, and the TMF and AF communicate indirectly through the NEF.

[0135] Example 1, as shown in FIG4 , the communication method mainly includes the following steps.

[0136] S401: RAN establishes a communication connection with TMF.

[0137] Specifically, the RAN may send an N2 connection request message to the TMF, where the N2 connection request message includes a tag communication type supported by the RAN, such as an active tag. The TMF may then establish an N2 connection with the RAN based on the N2 connection request message.

[0138] S402: RAN sends broadcast information to TAGs within its coverage area.

[0139] Specifically, the RAN can broadcast some random access-related configuration information to the TAGs within the RAN coverage area, so that the TAGs within the RAN coverage area can establish a communication connection with the RAN through random access. Optionally, the TAGs within the RAN coverage area can be regarded as UEs, and the RAN can send air interface broadcast information periodically or based on event triggering.

[0140] As an example, FIG4 takes the first TAG as an example to illustrate a TAG within the coverage of the RAN.

[0141] S403: The AF sends a subscription request message for service data of at least one TAG to the TMF through the NEF.

[0142] First, the AF can send a subscription request message to the NEF, which includes the ID of at least one TAG. The NEF determines the TMF corresponding to at least one TAG based on the ID of at least one TAG in the subscription request message. For example, one TMF corresponds to a TAG ID group (or TAG ID segment). Optionally, the ID numbers of multiple TAGs in a TAG ID group are continuous. The NEF can determine the TAG ID group to which the ID of at least one TAG belongs based on the ID of at least one TAG in the subscription request message, and then determine the TMF corresponding to the first TAG ID group. Then, the NEF can send a subscription request message to the TMF.

[0143] It is understandable that the subscription request message in S403 is an example of the third message described in Figure 3. The subscription request message may also include information of the AF, such as the ID of the AF.

[0144] FIG4 is described by taking an example where the at least one TAG to which the AF requests to subscribe includes the first TAG, and the TMF executes S404 after receiving the subscription request message.

[0145] S404, TMF obtains the contract information of the first TAG from UDM.

[0146] Specifically, the TMF can send a contract information request message to the UDM based on the subscription request message. The contract information request message includes the ID of the first TAG in the subscription request message. Then, the UDM sends the contract information of the first TAG to the TMF. The contract information of the first TAG includes the ID of at least one AF, and the at least one AF has access rights to the first TAG. When multiple AFs have access rights to the same first TAG, the service data reported by the first TAG to different AFs can be the same or different, that is, different AFs can obtain the same or different service data for the same TAG.

[0147] In addition, optionally, in a scenario where the UDR stores the contract information of the first TAG, S404 may be replaced by: TMF may also obtain the contract information of the first TAG from the UDR.

[0148] The TMF may determine whether the AF sending the subscription request message has access rights to the first TAG based on the subscription information of the first TAG, and execute S405 if it is determined that the AF has access rights. It is understandable that if the AF sending the subscription request message does not have access rights to the first TAG to which the AF is requesting to subscribe, the TMF will not perform subsequent operations.

[0149] S405, TMF sends a subscription response message to AF through NEF.

[0150] Specifically, the TMF may send a subscription response message to the NEF, where the subscription response message indicates that the subscription is successful; then, the NEF may send the subscription response message to the AF or the NEF may notify the AF that the subscription is successful.

[0151] In addition, the TMF may also locally save the subscription relationship between the AF and the TMF, such as storing the identifier of the first TAG subscribed by the AF.

[0152] S406: When there is a demand to report service data, the first TAG initiates random access to the RAN.

[0153] For example, the first TAG can initiate random access to the RAN based on the broadcast information of the RAN. The specific understanding can refer to the random access process of the 5G UE, and this embodiment of the present application will not go into details.

[0154] S407: The first TAG sends a registration request message to the TMF via the RAN.

[0155] The registration request message includes the identifier of the first TAG.

[0156] S408: Register the first TAG in TMF.

[0157] Specifically, the TMF may execute the tag authentication and security negotiation process corresponding to the first TAG to authenticate and authorize the initial access of the first TAG, etc. Further, after the first TAG passes the security check, the TMF may continue to execute S409.

[0158] S409: TMF sends a registration acceptance message to the first TAG through RAN.

[0159] It is understood that the registration acceptance message is an example of the first message in S302. Specifically, the registration acceptance message includes a temporary identifier and information instructing the first tag to send service data. The temporary identifier includes identification information such as the TMF's IP or ID. It is understood that after receiving the temporary identifier, the first tag will store it locally, for example, in a local storage space.

[0160] S410: The first TAG sends service data sending information to the TMF via the RAN.

[0161] Specifically, the first TAG sends the service data sending information according to the information sent by the TMF instructing the first TAG to send service data. It can be understood that the service data sending information is an example of the second message in S303. The service data sending information includes the service data of the first TAG, the identifier of the first TAG, and the identifier of the TMF.

[0162] S411, TMF sends data sending response information to the first TAG through RAN.

[0163] Specifically, after receiving the data sending response information, the TMF may execute step S412 according to the subscription relationship between the saved AF and the TMF.

[0164] S412, TMF sends the identifier of the first TAG and service data to NEF.

[0165] S413, NEF sends data reception response information to TMF.

[0166] The data reception response information is used to indicate that the NEF has received the identifier and service data of the first TAG.

[0167] S414, NEF sends a subscription report to AF.

[0168] The subscription report includes the identifier of the first TAG and service data.

[0169] S415, the AF sends a response message of the subscription report to the NEF.

[0170] Furthermore, if the first TAG has a business data reporting requirement again, steps S406 to S415 may be repeated, which will not be described in detail in this embodiment of the application. Optionally, when S409 is repeated, that is, when the TMF sends a registration acceptance message to the first TAG again via the RAN, the registration acceptance message may not carry the TMF identifier.

[0171] Example 2, as shown in FIG5 , the communication method mainly includes the following steps.

[0172] S501: RAN establishes a communication connection with TMF.

[0173] Specifically, this step can be understood with reference to S401, and will not be described in detail in the implementation of this application.

[0174] S502: RAN sends broadcast information to TAGs within RAN coverage.

[0175] Specifically, this step can be understood with reference to S402, and will not be described in detail in the implementation of this application.

[0176] As an example, FIG5 takes the first TAG as an example to illustrate a TAG within the coverage of the RAN.

[0177] S503: When there is a demand to report service data, the first TAG initiates random access to the RAN.

[0178] Specifically, this step can be understood with reference to S406, and will not be described in detail in the implementation of this application.

[0179] S504: The first TAG sends a registration request message to the TMF via the RAN.

[0180] Specifically, this step can be understood with reference to S407, and will not be described in detail in the implementation of this application.

[0181] S505: Register the first TAG in TMF.

[0182] Specifically, this step can be understood with reference to S408, and will not be described in detail in the implementation of this application.

[0183] S506, TMF obtains the contract information of the first TAG from UDM.

[0184] Specifically, the TMF may send a contract information request message to the UDM, requesting the contract information of the first tag registered in S505. The contract information request message includes the ID of the first tag. Furthermore, the UDM may feedback the contract information of the first tag to the TMF. The contract information of the first tag includes the following: the ID of at least one AF with access rights to the first tag, the data transmission cycle information of the first tag, and the cache policy information of the service data of the first tag in the TMF.

[0185] Exemplarily, the data transmission cycle information of the first TAG indicates that the first TAG transmits service data once every certain time period (i.e., the service data transmission cycle). The cache policy information indicates the time for caching and / or deleting the service data of the first TAG in the TMF. For example, the cache policy information instructs the TMF to cache the identifier of the first TAG and multiple service data from the first TAG, and to delete the multiple service data of the first TAG cached in the TMF after the TMF sends the multiple service data of the TAF to the AF.

[0186] In addition, optionally, in a scenario where the UDR stores the contract information of the first TAG, S506 may be replaced by: TMF may also obtain the contract information of the first TAG from the UDR.

[0187] S507: TMF sends a registration acceptance message to the first TAG through RAN.

[0188] It is understood that the registration acceptance message is an example of the first message in S302. Specifically, the registration acceptance message includes a temporary identifier, information instructing the first tag to send service data, and data transmission cycle information. The temporary identifier includes identification information such as the TMF's IP or ID, and the data transmission cycle information is used to instruct the first tag to periodically update and send service data according to the data transmission cycle information. It is understood that after receiving the temporary identifier, the first tag will save the temporary identifier locally, for example, in a local storage space.

[0189] S508: The first TAG periodically sends data transmission information to the TMF through the RAN.

[0190] Specifically, the first TAG periodically sends data transmission information according to the data transmission cycle information in the registration acceptance message. In each service data transmission cycle, the first TAG executes S504 to S507 and then sends a data transmission information to the TMF via the RAN.

[0191] This data transmission information is an example of the second message in S303. The data transmission information sent by the first TAG in any cycle includes the service data of the first TAG, the identifier of the first TAG, and the identifier of the TMF. In addition, it can be understood that the service data in the data transmission information sent by the first TAG in a cycle is the current latest service data, and the first TAG service data in the data transmission information sent by the first TAG in different cycles is different.

[0192] S509 , the TMF sends data sending response information to the first TAG through the RAN.

[0193] In one possible implementation, the TMF may send a data sending response message to the first TAG once each time it receives a data sending message. In another possible implementation, the TMF may send a data sending response message to the first TAG once after receiving multiple (such as a preset number) data sending messages.

[0194] S510, TMF caches the received service data of the first TAG.

[0195] Specifically, the TMF may cache the service data periodically sent by the first TAG according to the cache policy information obtained in S506.

[0196] S511, the AF sends a read request message for the service data of the first TAG to the TMF through the NEF.

[0197] First, AF can send a read request message to NEF, and the read request message includes the ID of the first TAG. NEF determines the TMF corresponding to the first TAG based on the ID of the first TAG in the read request message. For example, one TMF corresponds to a TAG ID group (or TAG ID segment), and the TAG ID group includes one or more TAG IDs. Optionally, the multiple TAG IDs in a TAG ID group are numbered consecutively. NEF can determine the TAG ID group where the ID of the first TAG is located based on the ID of the first TAG in the read request message, and then determine the TMF corresponding to the TAG ID group. Then, NEF can send a read request message to TMF.

[0198] It is understandable that the read request information in S403 is an example of the fourth message described in Figure 3. The read request information may also include AF information, such as the AF ID.

[0199] S512: The TMF determines whether the AF has access rights to the first TAG based on the subscription information of the first TAG.

[0200] Specifically, if at least one AF ID in the contract information of the first TAG includes the AF ID carried in the read request information, TMF can determine that the AF has access rights to the first TAG and continue to execute step S513; if at least one AF ID in the contract information of the first TAG does not include the AF ID carried in the read request information, TMF can determine that the AF does not have access rights to the first TAG and no longer execute subsequent steps.

[0201] S513, TMF sends the identifier of the first TAG and service data to NEF.

[0202] S514, NEF sends data reception response information to TMF.

[0203] The data reception response information is used to indicate that the NEF has received the identifier and service data of the first TAG.

[0204] S515, NEF sends a read response message to AF.

[0205] The read response information includes the identifier of the first TAG and service data.

[0206] S516, TMF deletes the cached service data of the first TAG.

[0207] Specifically, the TMF may delete the cached multiple service data of the first TAG after receiving the data reception response information according to the aforementioned cache policy information.

[0208] In addition, optionally, in a specific implementation, the TMF may cache all received second messages of the first tag into the UDM (or UDR), that is, step S510 may be replaced with the description that the TMF sends the aforementioned data sending information to the UDM; the operations performed by the TMF in steps S511 to S516 may be replaced with those performed by the UDM.

[0209] FIG6 is a second communication method provided in an embodiment of the present application, which can be applied to a mobile scenario, that is, a communication scenario where the tag is in a mobile state. The method mainly includes the following process.

[0210] S601: Register a first tag in a first tag management function network element.

[0211] This step can be understood with reference to the description of S301, and will not be described in detail in this embodiment of the present application.

[0212] S602: The first label management function network element sends a first message to the first label through the access network device.

[0213] This step can be understood with reference to the description of S302, and will not be described in detail in this embodiment of the present application.

[0214] S603: The first label sends a second message to the first label management function network element through the access network device.

[0215] This step can be understood with reference to the description of S303, and will not be described in detail in this embodiment of the present application.

[0216] In the scenario applied to label inventory, the first label management function network element can also send the business data of the first label to other network elements with label inventory requirements, such as application network element AF. Specifically, the embodiment of the present application records other network elements with label inventory requirements as the first network element, and the first network element can initiate a request for the business data of the specified label to the first label management function network element, and then the first label management function network element can feedback the business data of the specified label to the first network element after receiving the business data of the specified label. For example, taking the first network element requesting the business data of the first label as an example, since the first label is a mobile label, the first network element can determine to request the business data of the first label from the first label management function network element by executing S604 and S605, and then obtain the business data of the first label by executing S606.

[0217] S604: The first network element determines that the current location of the first tag belongs to the service range of the first tag management function network element.

[0218] Specifically, the second network element stores a correspondence between the identifier of the first tag and the identifier of the first tag management function network element to which its current location belongs. The first network element can determine that the current location of the first tag belongs to the service scope of the first tag management function network element based on the identifier of the first tag and the correspondence stored in the second network element. For example, the first tag management function network element is the first TMF, the first network element is the AF, and the second network element is the UDM (or UDR). In a scenario where the UDM and the AF communicate directly, the AF can directly send the identifier of the first tag to the UDM, and the UDM feeds back the identifier of the first tag management function network element corresponding to the first tag to the AF, and the AF determines that the current location of the first tag belongs to the service scope of the first TMF; or, in a scenario where the UDM and the AF communicate directly through the NEF, the AF can send the identifier of the first tag to the UDM through the NEF, and the UDM feeds back the identifier of the first tag management function network element corresponding to the first tag to the AF through the NEF, and the AF determines that the current location of the first tag belongs to the service scope of the first TMF.

[0219] S605: The first network element sends a third message to the first label management function network element.

[0220] The third message is used to request the service data of the first tag. Specifically, the third message may include the identifier of the first tag and information about the first network element. Exemplarily, the first network element is an AF, and the first tag management function network element is a first TMF. In a scenario where the TMF communicates directly with the AF, the AF may send the third message directly to the TMF; alternatively, in a scenario where the TMF communicates directly with the AF through an NEF, the AF may send the third message to the TMF through the NEF.

[0221] It is understandable that the embodiment of the present application does not limit the execution order between S604 to S605 and S601 to S603.

[0222] For example, in one possible implementation, S604 to S605 may be executed first and then S601 to S603. That is, the first tag management function network element may complete the registration of the first tag in the first tag management function network element and send the identifier of the first tag management function network element to the first tag when the first network element requests the service data of the first tag, so that the first tag uses the identifier of the first tag management function network element to actively send service data to the first tag management function network element through the access network device. Specifically, after receiving the third message, the first tag management function network element may first determine whether the first network element has access rights to the first tag based on the information of the first network element, or alternatively, the first tag management function network element may determine whether the first network element can obtain the service data of the first tag based on the information of the first network element. For example, the information of the first network element may include the identifier of the first network element, and the first tag management function network element may query the subscription information of the first tag from the network element (such as UDM or UDR) that stores the subscription information of the first tag. The subscription information of the first tag includes the identifier of the network element that has access rights to the first tag; if the subscription information of the first tag includes the identifier of the first network element. The first tag management function network element can then determine that the first network element has access rights to the first tag. Further, if the first network element has access rights to the first tag, the first tag management function network element continues to execute steps S601 to S603 and S606 after executing S604 to S605; if the first network element does not have access rights to the first tag, the first tag management function network element will no longer execute steps S601 to S603 and S606.

[0223] For example, in another possible implementation, S601 to S603 can be executed first and then S604 to S605, that is, the first tag management function network element can complete the registration of the first tag in the first tag management function network element by itself and send the identifier of the first tag management function network element to the first tag, so that the first tag uses the identifier of the first tag management function network element to actively send business data to the first tag management function network element through the access network device; further, after receiving the third message, the first tag management function network element can first determine whether the first network element has access rights to the first tag based on the information of the first network element, or alternatively, the first tag management function network element can determine whether the first network element can obtain the business data of the first tag based on the information of the first network element. If the first network element has access rights to the first tag, the first tag management function network element will continue to execute S606 after executing S604 to S605; if the first network element does not have access rights to the first tag, the first tag management function network element will no longer execute step S606.

[0224] S606: The first label management function network element sends the second message or the fourth message to the first network element.

[0225] This step can be understood with reference to S305 and will not be described in detail in this embodiment of the present application.

[0226] For ease of implementation, the specific implementation process of the method described in Figure 6 is described in detail in Figures 7 and 8 below, taking the interactions among TAG, RAN, TMF, UDM, NEF, and AF as an example. It can be understood that the TAG in Figures 7 and 8 is an example of a first tag, the RAN is an example of an access network device, the UDM refers to a network element that stores subscription information of one or more tags and the association between the tag and the TMF, the first TMF is an example of a first tag management function network element, the AF is an example of a first network element, and the TMF and AF communicate indirectly through the NEF.

[0227] Example 3, as shown in FIG7 , the communication method mainly includes the following steps.

[0228] S701: RAN establishes a communication connection with a first TMF.

[0229] This step can be understood with reference to S401 and will not be described in detail in this embodiment of the present application.

[0230] S702: RAN sends broadcast information to TAGs within its coverage area.

[0231] This step can be understood with reference to S402, and will not be described in detail in this embodiment of the present application. As an example, FIG7 takes the first TAG as an example to illustrate a TAG within the coverage of the RAN.

[0232] S703: The AF sends a subscription request message for service data of at least one TAG to the NEF.

[0233] The subscription request message includes at least one tag identifier (such as ID) and AF information. It can be understood that the subscription request message in S703 is an example of the third message described in FIG. 3 .

[0234] Taking one TAG (denoted as the first TAG) in the at least one TAG as an example, the NEF may determine to obtain the service data of the first TAG from the first TMF through S704 and S705.

[0235] S704: NEF sends the identifier of the first TAG and AF information to UDM.

[0236] Exemplarily, the identifier of the first TAG may be the ID of the first TAG. The UDM may determine the TAG ID group in which the ID of the first TAG currently resides based on the ID of the first TAG; wherein, one TAG ID group (or TAG ID segment) corresponds to one TMF, and optionally, the ID numbers of multiple TAGs in a TAG ID group are continuous. The TAG ID group in which the ID of the first TAG currently resides is recorded as the first TAG ID group, and the first TAG ID group corresponds to the first TMF, then the UDM may determine that the business data of the first TAG can be obtained through the first TMF.

[0237] Furthermore, the UDM can determine whether the AF has access rights to the first TAG based on the subscription information of the first TAG, and execute S705 if it is determined that the AF has access rights. For example, the subscription information of the first TAG includes the ID of at least one AF, and the at least one AF has access rights to the first TAG. Optionally, when multiple AFs have access rights to the same first TAG, the service data reported by the first TAG to different AFs can be the same or different, that is, different AFs can obtain the same or different service data for the same TAG.

[0238] Based on this, if the subscription information of the first TAG includes the ID of the AF sent by the NEF, the UDM can continue to execute S705; if the subscription information of the first TAG does not include the ID of the AF sent by the NEF, the UDM will no longer perform subsequent operations.

[0239] S705: The UDM sends the identifier of the first TMF to the NEF.

[0240] This step can be understood as the UDM's response action to S704.

[0241] S706: The NEF may send a subscription request message to the first TMF.

[0242] S707: The first TMF sends a subscription response message to the AF through the NEF.

[0243] Specifically, the first TMF may send a subscription response message to the NEF, where the subscription response message indicates that the subscription is successful; then, the NEF sends the subscription response message to the AF or the NEF notifies the AF that the subscription is successful.

[0244] In addition, the first TMF may also locally store the subscription relationship between the AF and the first TMF, such as storing the identifier of the first TAG subscribed by the AF.

[0245] S708 : When there is a demand to report service data, the first TAG initiates random access to the RAN.

[0246] For example, the first TAG can initiate random access to the RAN based on the broadcast information of the RAN. The specific understanding can refer to the random access process of the 5G UE, and this embodiment of the present application will not go into details.

[0247] S709: The first TAG sends a registration request message to the first TMF through the RAN.

[0248] The registration request message includes the identifier of the first TAG.

[0249] S710: Register a first TAG in a first TMF.

[0250] Specifically, the first TMF may execute the tag authentication and security negotiation process corresponding to the first TAG to authenticate and authorize the initial access of the first TAG, etc. Further, after the first TAG passes the security check, the first TMF may continue to execute S711.

[0251] S711: The first TMF sends a registration acceptance message to the first TAG through the RAN.

[0252] It is understood that the registration acceptance message is an example of the first message in S302. Specifically, the registration acceptance message includes a temporary identifier and information instructing the first TAG to send service data. The temporary identifier includes identification information such as the IP address or ID of the first TMF. It is understood that after receiving the temporary identifier, the first TAG will store it locally, for example, in a local storage space.

[0253] S712: The first TAG sends data sending information to the first TMF via the RAN.

[0254] Specifically, the first TAG sends the data sending information according to the information sent by the first TMF instructing the first TAG to send service data. It can be understood that the data sending information is an example of the second message in S303, and the data sending information includes the service data of the first TAG, the identifier of the first TAG, and the identifier of the first TMF.

[0255] S713: The first TMF sends data sending response information to the first TAG through the RAN.

[0256] Specifically, after receiving the data sending response information, the first TMF may execute step S714 according to the subscription relationship between the saved AF and the first TMF.

[0257] S714: The first TMF sends information including the identifier of the first TAG and service data to the NEF.

[0258] S715, the NEF sends data reception response information to the first TMF.

[0259] The data reception response information is used to indicate that the NEF has received the identifier and service data of the first TAG.

[0260] S716: NEF sends a subscription report to AF.

[0261] The subscription report includes the identifier of the first TAG and service data.

[0262] S717: AF sends a subscription report response message to NEF.

[0263] Furthermore, if the first TAG has a service data reporting requirement again, steps S708 to S717 may be repeated, which will not be described in detail in this embodiment of the present application. Optionally, when S711 is repeated, that is, when the first TMF again sends a registration acceptance message to the first TAG via the RAN, the registration acceptance message may not repeatedly carry the identifier of the first TMF.

[0264] Example 4: The communication method shown in FIG8 mainly includes the following steps.

[0265] S801: RAN establishes a communication connection with a first TMF.

[0266] Specifically, this step can be understood with reference to S401, and will not be described in detail in the implementation of this application.

[0267] S802: RAN sends broadcast information to TAGs within RAN coverage.

[0268] Specifically, this step can be understood with reference to S402, and will not be described in detail in the implementation of this application.

[0269] As an example, FIG8 takes the first TAG as an example to illustrate a TAG within the coverage of the RAN.

[0270] S803: When there is a demand to report service data, the first TAG initiates random access to the RAN.

[0271] Specifically, this step can be understood with reference to S406, and will not be described in detail in the implementation of this application.

[0272] S804: The first TAG sends a registration request message to the first TMF via the RAN.

[0273] Specifically, the current location of the first TAG is within the service range of the first TMF. This step can be understood with reference to S407 and will not be described in detail in the implementation of this application.

[0274] S805: Register the first TAG in the first TMF.

[0275] Specifically, this step can be understood with reference to S408, and will not be described in detail in the implementation of this application.

[0276] S806: The first TMF obtains the contract information of the first TAG from the UDM.

[0277] This step can be understood with reference to S506 and will not be described in detail in this embodiment of the present application.

[0278] S807: The first TMF sends a registration acceptance message to the first TAG through the RAN.

[0279] This step can be understood with reference to S507 and will not be described in detail in this embodiment of the present application.

[0280] S808: The first TAG periodically sends data transmission information to the first TMF through the RAN.

[0281] This step can be understood with reference to S508 and will not be described in detail in this embodiment of the present application.

[0282] S809: The first TMF sends data sending response information to the first TAG through the RAN.

[0283] This step can be understood with reference to S509 and will not be described in detail in this embodiment of the present application.

[0284] S810: The first TMF caches the received service data of the first TAG.

[0285] This step can be understood with reference to S510 and will not be described in detail in this embodiment of the present application.

[0286] S811 , the AF sends a read request message for service data of at least one TAG to the NEF.

[0287] The read request information includes at least one TAG identifier (such as ID) and AF information. It can be understood that the read request message in S811 is an example of the third message described in FIG. 6 .

[0288] Taking one TAG in at least one TAG (denoted as the first TAG) as an example, the NEF may determine through S812 and S813 to obtain the service data of the first TAG from the first TMF.

[0289] S812: NEF sends the identifier of the first TAG and AF information to UDM.

[0290] Exemplarily, the identifier of the first TAG may be the ID of the first TAG. The UDM may determine the TAG ID group in which the ID of the first TAG currently resides based on the ID of the first TAG; wherein, one TAG ID group (or TAG ID segment) corresponds to one TMF, and optionally, the ID numbers of multiple TAGs in a TAG ID group are continuous. The TAG ID group in which the ID of the first TAG currently resides is recorded as the first TAG ID group, and the first TAG ID group corresponds to the first TMF, then the UDM may determine that the business data of the first TAG can be obtained through the first TMF.

[0291] Furthermore, the UDM can determine whether the AF has access rights to the first TAG based on the subscription information of the first TAG, and execute S813 if it is determined that the AF has access rights. For example, the subscription information of the first TAG includes the ID of at least one AF, and the at least one AF has access rights to the first TAG. Optionally, when multiple AFs have access rights to the same first TAG, the service data reported by the first TAG to different AFs can be the same or different, that is, different AFs can obtain the same or different service data for the same TAG.

[0292] Based on this, if the subscription information of the first TAG includes the ID of the AF sent by the NEF, the UDM can continue to execute S813; if the subscription information of the first TAG does not include the ID of the AF sent by the NEF, the UDM will no longer perform subsequent operations.

[0293] S813: The UDM sends the identifier of the first TMF to the NEF.

[0294] This step can be understood as the UDM's response action to S812.

[0295] S814: The NEF may send a read request message to the first TMF.

[0296] S815: The first TMF sends information including the identifier of the first TAG and service data to the NEF.

[0297] S816, the NEF sends data reception response information to the first TMF.

[0298] The data reception response information is used to indicate that the NEF has received the identifier and service data of the first TAG.

[0299] S817, NEF sends a read response message to AF.

[0300] The read response information includes the identifier of the first TAG and service data.

[0301] S818: The first TMF deletes the cached service data of the first TAG.

[0302] Specifically, the first TMF may delete the cached multiple service data of the first TAG after receiving the data reception response information according to the aforementioned cache policy information.

[0303] Optionally, in a specific implementation, the TMF may cache all received second messages of the first label into the UDM (or UDR), that is, step S810 may be replaced with the description of TMF sending data information to the UDM; the operations performed by the TMF in steps S811 to S816 may be replaced with those performed by the UDM.

[0304] In addition, in a communication scenario where the tag is in a mobile state, the tag's location may be updated and switched from the service scope of the first tag management function network element to the service scope of the second tag management function network element. In this case, the solution for the tag to actively report business data can be understood with reference to the third communication method illustrated in Figure 9. This method mainly includes the following steps.

[0305] S901: When the position of the first tag is switched from the service range of the first tag management function network element to the service range of the second tag management function network element, the first tag sends a second message to the second tag management function network element through the access network device.

[0306] The first tag is a tag registered with the first tag management function network element, and the second message includes the service data of the first tag and the identifier of the first tag management function network element. Specifically, the first tag can determine the service data to be sent and establish a communication connection with the access network device via random access. Furthermore, the first tag can send the second message to the second tag management function network element via the access network device.

[0307] S902: The second label management function network element obtains context information of the first label from the first label management function network element according to the second message.

[0308] Specifically, the second tag management function network element requests the first tag management function network element for context information of the first tag based on the identifier of the first tag management function network element in the second message, and then the first tag management function network element sends the context information of the first tag to the second tag management function network element. The context information of the first tag may include relevant information about the registration of the first tag in the first tag management function network element, as well as historical service data of the first tag. The second tag management function network element can save the context information of the first tag and complete the handover of the first tag from the first tag management function network element to the second tag management function network element, that is, complete the registration of the first tag in the second tag management function network element. Furthermore, the second tag management function network element can also send information to the second network element (such as UDM / UDR) to indicate that the first tag is registered in the second tag management function network element. The information includes the identifier of the second tag management function network element and the identifier of the first tag, and there is an association between the identifier of the second tag management function network element and the identifier of the first tag.

[0309] In addition, optionally, a timer can be configured to start timing after the first label management function network element sends the context information of the first label to the second label management function network element. When the timer expires, the first label management function network element deletes the context information of the first label; or, after receiving information indicating that the first label is registered in the second label management function network element, the second network element sends a message to the first label management function network element to instruct the first label management function network element to delete the context information of the first label.

[0310] S903: The second label management function network element sends a sixth message to the first label through the access network device.

[0311] The sixth message includes the identifier of the second label management function network element.

[0312] S904: The first label sends a seventh message to the second label management function network element through the access network device.

[0313] The seventh message includes the service data of the first label and the identifier of the second label management function network element.

[0314] In the scenario applied to label inventory, the second label management function network element can also send the business data of the first label to other network elements with label inventory requirements, such as application network element AF. Specifically, the embodiment of the present application records other network elements with label inventory requirements as the first network element, and the first network element can initiate a request for the business data of the specified label to the second label management function network element, and then the second label management function network element can feedback the business data of the specified label to the first network element after receiving the business data of the specified label. For example, taking the first network element requesting the business data of the first label as an example, since the first label is a mobile label, the first network element can determine to request the business data of the first label from the second label management function network element by executing S905 and S906, and then obtain the business data of the first label by executing S907.

[0315] S905: The first network element determines that the current location of the first tag belongs to the service range of the second tag management function network element.

[0316] Specifically, the second network element stores a correspondence between the identifier of the first tag and the identifier of the second tag management function network element to which its current location belongs. The first network element can determine that the current location of the first tag belongs to the service scope of the second tag management function network element based on the identifier of the first tag and the correspondence stored in the second network element. For example, the second tag management function network element is the first TMF, the first network element is the AF, and the second network element is the UDM (or UDR). In the scenario where the UDM and the AF communicate directly, the AF can directly send the identifier of the first tag to the UDM, and the UDM feeds back the identifier of the second tag management function network element corresponding to the first tag to the AF, and the AF determines that the current location of the first tag belongs to the service scope of the first TMF; or, in the scenario where the UDM and the AF communicate directly through the NEF, the AF can send the identifier of the first tag to the UDM through the NEF, and the UDM feeds back the identifier of the second tag management function network element corresponding to the first tag to the AF through the NEF, and the AF determines that the current location of the first tag belongs to the service scope of the first TMF.

[0317] S906: The first network element sends a third message to the second label management function network element.

[0318] The third message is used to request the service data of the first tag. Specifically, the third message may include the identifier of the first tag and information about the first network element. Exemplarily, the first network element is an AF, and the second tag management function network element is a first TMF. In a scenario where the TMF and the AF communicate directly, the AF can send the third message directly to the TMF; alternatively, in a scenario where the TMF communicates directly with the AF through an NEF, the AF can send the third message to the TMF through the NEF.

[0319] It is understandable that the embodiment of the present application does not limit the execution order between S905 to S906 and S901 to S904.

[0320] For example, in one possible implementation, S905 to S906 may be executed first and then S901 to S904, that is, the second tag management function network element may complete the registration of the first tag in the second tag management function network element and send the identifier of the second tag management function network element to the first tag when the first network element requests the service data of the first tag, so that the first tag uses the identifier of the second tag management function network element to actively send service data to the second tag management function network element through the access network device. Specifically, after receiving the third message, the second tag management function network element may first determine whether the first network element has access rights to the first tag based on the information of the first network element, or alternatively, the second tag management function network element may determine whether the first network element can obtain the service data of the first tag based on the information of the first network element. For example, the information of the first network element may include the identifier of the first network element, and the second tag management function network element may query the subscription information of the first tag from the network element (such as UDM or UDR) that stores the subscription information of the first tag, and the subscription information of the first tag includes the identifier of the network element that has access rights to the first tag; if the subscription information of the first tag includes the identifier of the first network element. The second tag management function network element can then determine that the first network element has access rights to the first tag. Further, if the first network element has access rights to the first tag, the second tag management function network element continues to execute steps S901 to S904 and S907 after executing S905 to S906. If the first network element does not have access rights to the first tag, the second tag management function network element will no longer execute steps S901 to S904 and S907.

[0321] For example, in another possible implementation, S901 to S904 can be executed first and then S905 to S906, that is, the second tag management function network element can complete the registration of the first tag in the second tag management function network element by itself and send the identifier of the second tag management function network element to the first tag, so that the first tag uses the identifier of the second tag management function network element to actively send business data to the second tag management function network element through the access network device; further, after receiving the third message, the second tag management function network element can first determine whether the first network element has access rights to the first tag based on the information of the first network element, or alternatively, the second tag management function network element can determine whether the first network element can obtain the business data of the first tag based on the information of the first network element. If the first network element has access rights to the first tag, the second tag management function network element will continue to execute S907 after executing S905 to S906; if the first network element does not have access rights to the first tag, the second tag management function network element will no longer execute step S907.

[0322] S907: The second label management function network element sends a second message or a fourth message to the first network element.

[0323] This step can be understood with reference to S305 and will not be described in detail in this embodiment of the present application.

[0324] For ease of implementation, the specific implementation process of the method described in Figure 9 is described in detail in Figure 10 below, taking the interaction between TAG, RAN, TMF, UDM, NEF, and AF as an example. It can be understood that the first TAG in Figure 10 is an example of a first tag, RAN is an example of an access network device, the first TMF is an example of a first tag management function network element, the second TMF is an example of a second tag management function network element, the UDM (or UDR) is an example of a second network element, the UDM stores the subscription information of one or more tags and the association between the tags and the TMF, the AF is an example of a first network element, and the TMF and AF communicate indirectly through the NEF.

[0325] Example 5: The communication method shown in FIG10 mainly includes the following steps.

[0326] S1001: When there is a demand to report service data, the first TAG initiates random access to the RAN.

[0327] The first TAG is a TAG registered in the first TMF, and the first TAG stores the identifier of the first TMF. For example, the first TAG can initiate random access to the RAN based on the broadcast information of the RAN. For details, please refer to the random access process of the 5G UE, which is not described in detail in this embodiment of the application.

[0328] When the location of the first TAG is switched from the service range of the first TMF to the service range of the second TMF, the first TAG may continue to execute S1002.

[0329] S1002: The first TAG sends service request information to the second TMF via the RAN.

[0330] It can be understood that the service request information is an example of the second message in S901. The service request information includes the service data of the first TAG and also includes the identifier of the first TAG and the identifier of the first TMF.

[0331] S1003: The second TMF requests the first TMF for context information of the first TAG according to the identifier of the first TMF.

[0332] S1004: The first TMF sends the context information of the first TAG to the second TMF.

[0333] S1005: The second TMF sends information to the UDM indicating that the first TAG is registered in the second TMF.

[0334] Specifically, this step can be understood with reference to the description in S902, and will not be described in detail in this embodiment of the present application. Optionally, the UDM can also be replaced by a UDR.

[0335] S1006: The UDM sends a deletion request message for the context information of the first TAG to the first TMF.

[0336] S1007: The first TMF sends a deletion response message for the context information of the first TAG to the UDM.

[0337] Specifically, after deleting the context information of the first TAG, the first TMF sends the deletion response message.

[0338] S1008, UDM sends the signing information of the first TAG to the second TMF.

[0339] The subscription information of the first TAG includes the following: the ID of at least one AF that has access rights to the first TAG, the data sending cycle information of the first TAG, and the cache strategy information of the service data of the first TAG in the TMF.

[0340] S1009: The second TMF sends service response information to the first TAG through the RAN.

[0341] Specifically, the service response information includes a temporary identifier, information instructing the first TAG to send service data, and data transmission cycle information; the temporary identifier includes identification information such as the IP or ID of the second TMF, and the data transmission cycle information is used to instruct the first TAG to periodically update and send service data according to the data transmission cycle information. It is understood that after receiving the temporary identifier, the first TAG will save the temporary identifier locally, for example, in a local storage space.

[0342] S1010: The first TAG periodically sends data transmission information to the second TMF through the RAN.

[0343] This step can be understood with reference to S508 and will not be described in detail in this embodiment of the present application.

[0344] S1011: The second TMF sends data sending response information to the first TAG through the RAN.

[0345] This step can be understood with reference to S509 and will not be described in detail in this embodiment of the present application.

[0346] S1012: The second TMF caches the received service data of the first TAG.

[0347] This step can be understood with reference to S510 and will not be described in detail in this embodiment of the present application.

[0348] S1013: The AF sends a read request message for service data of at least one TAG to the NEF.

[0349] The read request information includes at least one TAG identifier (such as ID) and AF information. It can be understood that the read request message in S1013 is an example of the third message described in FIG. 9 .

[0350] Taking one TAG in at least one TAG (denoted as the first TAG) as an example, the NEF may determine to obtain the service data of the first TAG from the second TMF through S1014 and S1015.

[0351] S1014: NEF sends the identifier of the first TAG and AF information to UDM.

[0352] This step can be understood with reference to S812 and will not be described in detail in this embodiment of the present application.

[0353] S1015: UDM sends the identifier of the second TMF to NEF.

[0354] This step can be understood as the UDM's response to S1013.

[0355] S1016: The NEF may send a read request message to the second TMF.

[0356] S1017: The second TMF sends information including the identifier of the first TAG and service data to the NEF.

[0357] S1018, the NEF sends data reception response information to the second TMF.

[0358] The data reception response information is used to indicate that the NEF has received the identifier and service data of the first TAG.

[0359] S1019, NEF sends a read response message to AF.

[0360] The read response information includes the identifier of the first TAG and service data.

[0361] S1020: The second TMF deletes the cached service data of the first TAG.

[0362] Specifically, the second TMF may delete the cached multiple service data of the first TAG after receiving the data reception response information according to the aforementioned cache policy information.

[0363] In addition, optionally, in a specific implementation, the second TMF may also cache all received second messages of the first TAG into the UDM (or UDR), that is, step S1012 may also be replaced with the description of TMF sending data information to UDM; the operations performed by the second TMF in steps S1013 to S1020 may be replaced with operations performed by UDM.

[0364] Based on the same concept, referring to FIG11 , an embodiment of the present application provides a communication device 1100, which includes a processing module 1101 and a communication module 1102. The communication device 1100 can be a first tag, or a communication device applied to or used in conjunction with the first tag to implement a communication method executed on the first tag side; or the communication device 1100 can be an access network device, or a communication device applied to or used in conjunction with the access network device to implement a communication method executed on the access network device side; or the communication device 1100 can be a core network element (such as a first tag management function network element, a first network element, a second network element, or a second tag management function network element), or a communication device applied to or used in conjunction with the core network element to implement a communication method executed on the core network element side.

[0365] A module may also be referred to as a transceiver module, transceiver, transceiver, or transceiver device. A processing module may also be referred to as a processor, processing board, processing unit, or processing device. Optionally, the communication module is used to perform the sending and receiving operations on the first tag side or the access network device side in the above method. The device in the communication module that implements the receiving function can be considered a receiving unit, and the device in the communication module that implements the sending function can be considered a sending unit. That is, the communication module includes a receiving unit and a sending unit.

[0366] When the communication device 1100 is applied to the first tag, the processing module 1101 can be used to implement the processing function of the first tag in any of the examples in Figures 3 to 10, and the communication module 1102 can be used to implement the sending and receiving functions of the first tag in any of the examples in Figures 3 to 10.

[0367] When the communication device 1100 is applied to an access network device, the processing module 1101 can be used to implement the processing function of the access network device in any of the examples in Figures 3 to 10, and the communication module 1102 can be used to implement the transceiver function of the access network device in any of the examples in Figures 3 to 10.

[0368] When the communication device 1100 is applied to the core network network element side, the processing module 1101 can be used to implement the processing function of the core network network element in any of the examples described in Figures 3 to 10, and the communication module 1102 can be used to implement the sending and receiving function of the core network network element in any of the examples described in Figures 3 to 10.

[0369] In addition, it should be noted that in one possible design, the aforementioned communication module and / or processing module can be implemented through a virtual module. For example, the processing module can be implemented through a software functional unit or a virtual device, and the communication module can be implemented through a software function or a virtual device. In another possible design, the processing module or the communication module can also be implemented through a physical device. For example, if the device is implemented using a chip / chip circuit, the communication module can be an input / output circuit and / or a communication interface that performs input operations (corresponding to the aforementioned receiving operations) and output operations (corresponding to the aforementioned sending operations); the processing module is an integrated processor or microprocessor or integrated circuit.

[0370] The division of modules in the embodiments of the present application is illustrative and is merely a logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional modules in the various examples of the embodiments of the present application may be integrated into a single processor, or may exist physically separately, or two or more modules may be integrated into a single module. The integrated modules may be implemented in either hardware or software functional modules.

[0371] Based on the same technical concept, the embodiment of the present application further provides a communication device 1200. For example, the communication device 1200 can be a chip or a chip system. Optionally, in the embodiment of the present application, the chip system can be composed of a chip, or can include a chip and other discrete devices.

[0372] The communication device 1200 can be used to implement the functions of any network element in the communication system described in the above examples. The communication device 1200 may include at least one processor 1210. Optionally, the processor 1210 is coupled to a memory, and the memory may be located within the device; or the memory may be integrated with the processor; or the memory may be located outside the device. For example, the communication device 1200 may also include at least one memory 1220. The memory 1220 stores the necessary computer programs, computer programs or instructions and / or data for implementing any of the above examples; the processor 1210 may execute the computer program stored in the memory 1220 to complete the method in any of the above examples.

[0373] The communication device 1200 may also include a communication interface 1230, through which the communication device 1200 can exchange information with other devices. Exemplarily, the communication interface 1230 may be a transceiver, circuit, bus, module, pin, or other type of communication interface. When the communication device 1200 is a chip-type device or circuit, the communication interface 1230 in the device 1200 may also be an input-output circuit that can input information (or receive information) and output information (or send information). The processor is an integrated processor or microprocessor or integrated circuit or logic circuit, and the processor can determine output information based on input information.

[0374] The coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units, or modules, which can be electrical, mechanical, or other forms, and is used for information exchange between devices, units, or modules. The processor 1210 may operate in conjunction with the memory 1220 and the communication interface 1230. The specific connection medium between the processor 1210, memory 1220, and communication interface 1230 is not limited in the embodiments of the present application.

[0375] Optionally, referring to FIG12 , the processor 1210, the memory 1220, and the communication interface 1230 are interconnected via a bus 1240. The bus 1240 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The bus may be classified as an address bus, a data bus, a control bus, etc. For ease of illustration, FIG12 shows only one thick line, but this does not mean that there is only one bus or only one type of bus.

[0376] In the embodiments of the present application, the processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or execute the various methods, steps, and logic block diagrams of the embodiments of the present application. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods of the embodiments of the present application may be directly implemented as being executed by a hardware processor, or may be executed by a combination of hardware and software modules in the processor.

[0377] In an embodiment of the present application, the memory may be a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), etc., or a volatile memory (volatile memory), such as a random-access memory (RAM). The memory is any other medium that can be used to carry or store a desired program code in the form of an instruction or data structure and can be accessed by a computer, but is not limited thereto. The memory in the embodiment of the present application may also be a circuit or any other device that can implement a storage function, for storing program instructions and / or data.

[0378] In one possible implementation, the communication device 1200 can be applied to a first tag. Specifically, the communication device 1200 can be a first tag, or a device that can support the first tag and implement the function of the first tag in any of the examples mentioned above. The memory 1220 stores a computer program (or instruction) and / or data that implements the function of the first tag in any of the above examples. The processor 1210 can execute the computer program stored in the memory 1220 to complete the method for executing the first tag in any of the above examples. If the communication device is applied to the first tag, the communication interface in the communication device 1200 can be used to interact with the access network device, send information to the access network device, or receive information from the access network device.

[0379] In one possible implementation, the communication device 1200 can be applied to a core network network element. Specifically, the communication device 1200 can be a core network network element, or it can be a device that can support a core network network element and implement the functions of the core network network element in any of the examples mentioned above. The memory 1220 stores computer programs (or instructions) and / or data that implement the functions of the core network network element in any of the above examples. The processor 1210 can execute the computer program stored in the memory 1220 to complete the method executed by the core network element in any of the above examples. If the communication device is applied to a core network network element, the communication interface in the communication device 1200 can be used to interact with other network elements or access network devices, such as sending information to other network elements or access network devices, or receiving information from other network elements or access network devices.

[0380] In another possible implementation, the communication device 1200 can be applied to an access network device. Specifically, the communication device 1200 can be an access network device, or a device that can support the access network device and implement the functions of the access network device in any of the above-mentioned examples. The memory 1220 stores computer programs (or instructions) and / or data that implement the functions of the access network device in any of the above-mentioned examples. The processor 1210 can execute the computer program stored in the memory 1220 to complete the method executed by the access network device in any of the above-mentioned examples. When the communication device is applied to an access network device, the communication interface in the communication device 1200 can be used to interact with the first tag or the core network network element, such as sending information to the core network network element or the first tag, or receiving information from the core network network element or the first tag.

[0381] Since the communication device 1200 provided in this example can be applied to an access network device to implement the method executed on the access network device side, or applied to a first tag to implement the method executed by the first tag, or applied to a core network element to implement the method executed by the core network element, the technical effects achieved can be referred to the above method examples and will not be repeated here.

[0382] The technical solutions provided in the embodiments of the present application can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, they can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a terminal device, an access network device, 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 computer-readable storage medium. 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 a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital video disc (DVD)), or a semiconductor medium.

[0383] In the embodiments of the present application, under the premise that there is no logical contradiction, the examples can reference each other, for example, the methods and / or terms between method embodiments can reference each other, for example, the functions and / or terms between device embodiments can reference each other, for example, the functions and / or terms between device examples and method examples can reference each other.

[0384] Obviously, those skilled in the art may make various changes and modifications to the embodiments of the present application without departing from the scope of the embodiments of the present application. Thus, if these modifications and variations of the embodiments of the present application fall within the scope of the claims of the embodiments of the present application and their equivalents, the embodiments of the present application are intended to include these modifications and variations.

Claims

1. A communication method, characterized in that: Applicable to the first label management function network element, including: Sending a first message to a first label through an access network device, wherein the first message includes an identifier of the first label management function network element, and the first label is a label registered in the first label management function network element; A second message from the first label is received through the access network device, where the second message includes the service data of the first label, the identifier of the first label, and the identifier of the first label management function network element.

2. The method according to claim 1, characterized in that The first message also includes information for instructing the first tag to send service data.

3. The method according to claim 1 or 2, characterized in that Before sending the first message to the first tag through the access network device, the method further includes: receiving a third message from the first network element, the third message being used to request service data of the first tag, the third message including an identifier of the first tag and information of the first network element, the information of the first network element being used to determine whether the first network element has authority to access the first tag; After receiving the second message from the first tag through the access network device, the method further includes: Send a second message with the first label to the first network element.

4. The method according to claim 1 or 2, characterized in that: The first message also includes data transmission cycle information of the first tag; and receiving the second message from the first tag through the access network device includes: Based on the data sending cycle information of the first tag, a plurality of the second messages from the first tag are received through the access network device.

5. The method according to claim 4, characterized in that After receiving a plurality of the second messages from the first tag through the access network device, the method further includes: receiving a third message from the first network element, the third message being used to request service data of the first label, the third message including an identifier of the first label and information of the first network element, the information of the first network element being used to determine that the first network element has access rights to the first label; A fourth message is sent to the first network element, where the fourth message includes an identifier of the first tag and service data of the first tag in a plurality of the second messages.

6. The method according to any one of claims 3 to 5, characterized in that: Before receiving, by the access network device, a second message from the first tag, the method further includes: Acquire the subscription information of the first tag from the second network element, where the subscription information of the first tag includes one or more of the following: access permission information corresponding to the first tag, the access permission information being used to indicate a network element having access permission to the first tag; data transmission cycle information of the first tag; The service data cache information of the first label, the data cache information indicates the time for caching and / or deleting the service data of the first label in the first label management function network element.

7. The method according to claim 6, characterized in that Before acquiring the subscription information of the first tag from the second network element, the method further includes: A fifth message is sent to the second network element, where the fifth message indicates a mapping relationship between the first label and the first label management function network element.

8. A communication method, characterized in that: Applied to the first tag, including: After completing registration in the first label management function network element, receiving a first message from the first label management function network element through an access network device, where the first message includes an identifier of the first label management function network element; A second message is sent to the access network device through the access network device, wherein the second message includes the service data of the first label, the identifier of the first label, and the identifier of the first label management function network element.

9. The method according to claim 8, characterized in that Also includes: Determine the data to be sent and establish a communication connection with the access network device through random access; The first tag is registered in the first tag management function network element through the access network device.

10. The method according to claim 8 or 9, characterized in that The first message also includes information for instructing the first tag to send data.

11. The method according to any one of claims 8 to 10, characterized in that: The first message also includes data transmission cycle information of the first label; and sending the second message to the first label management function network element through the access network device includes: Based on the data sending cycle information of the first tag, multiple second messages are sent through the access network device.

12. A communication method, characterized in that: Applied to the first network element, including: Determining that the current location of the first tag belongs to the service scope of the first tag management function network element; Sending a third message to the first label management function network element, where the third message is used to request the service data of the first label, and the third message includes an identifier of the first label and information of the first label management function network element, where the information of the first label management function network element is used to determine that the first label management function network element has the authority to access the first label; Receive one or more second messages of the first label from the first label management function network element, where the second messages include service data of the first label, an identifier of the first label, and an identifier of the first label management function network element.

13. A communication method, characterized in that: Applied to a first tag, where the first tag is a tag registered in a first tag management function network element, the method includes: When the position of the first label is switched from the service scope of the first label management function network element to the service scope of the second label management function network element, a second message is sent to the second label management function network element through the access network device, where the second message includes the service data of the first label and the identifier of the first label management function network element; receiving, through the access network device, a sixth message from the second label management function network element, wherein the sixth message includes an identifier of the second label management function network element; A seventh message is sent to the second label management function network element through the access network device, and the seventh message includes the service data of the first label and the identifier of the second label management function network element.

14. The method according to claim 13, characterized in that The sending the second message to the second label management function network element through the access network device includes: Determine the data to be sent, and establish a communication connection with the access network device by random access; The second message is sent to the second label management function network element through the access network device.

15. A communication method, characterized in that: Applicable to the second label management function network element, including: Receiving a second message from the first tag through the access network device; wherein the second message includes the service data of the first tag and the identifier of the first tag management function network element, and the first tag is a tag registered in the first tag management function network element; Acquire context information of the first tag from the first tag management function network element according to the identifier of the first tag management function network element; Sending a sixth message to the first label through the access network device, where the sixth message includes an identifier of the second label management function network element; A seventh message from the first label is received through the access network device, wherein the seventh message includes the service data of the first label and an identifier of the second label management function network element.

16. A communication device, characterized in that: Comprising modules for performing the method as claimed in any one of claims 1 to 15.

17. A communication device, characterized in that: include: A processor, wherein the processor is coupled to a memory, the memory is used to store a computer program or an instruction, and the processor is used to execute the computer program or the instruction to implement the method according to any one of claims 1 to 15.

18. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program or instruction, and when the instruction is executed on a computer, the method according to any one of claims 1 to 15 is implemented.

19. A computer program product, characterized in that The method comprises computer-executable instructions, and when the computer-executable instructions are executed on a computer, the computer is caused to execute the method according to any one of claims 1 to 15.

Images