A communication method and apparatus

By introducing tag identification and routing policy information into the reader, the problem of the reader being unable to identify the enterprise to which the tag belongs is solved, the accurate transmission of tag information is achieved, and communication efficiency is improved.

CN117319972BActive Publication Date: 2026-11-17HUAWEI TECH CO LTD
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
CN202210714032.2
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-06-22
Publication Date
2026-11-17
Estimated Expiration
2042-06-22

AI Technical Summary

Technical Problem

In existing technologies, readers cannot accurately identify the enterprise to which the tag belongs and provide it with personalized communication services, resulting in inaccurate and inefficient information transmission.

Method used

By introducing tag identification and routing policy information into the communication device, a dedicated communication session path is determined, ensuring that information is accurately transmitted to the target enterprise server.

Benefits of technology

It enables the effective and accurate transmission of tag information, improving the accuracy and efficiency of communication.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN117319972B_ABST
    Figure CN117319972B_ABST
Patent Text Reader

Abstract

A communication method and apparatus are disclosed. The method includes: a first communication device receiving a first request, the first request instructing the first communication device to acquire information of the first tag; the first communication device acquiring the information of the first tag according to the first request, the information of the first tag including an identifier of the first tag; the first communication device determining a first communication session based on the identifier of the first tag, the first communication session being used to transmit the information of the first tag; and the first communication device sending the information of the first tag through the first communication session. Through this method, after acquiring the information of the first tag, the first communication device determines a corresponding first communication session for the information of the first tag, thereby ensuring that the first communication device can effectively and accurately transmit the information of the first tag through the first communication session.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

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

[0002] With the development of IoT technology, its application scenarios are becoming increasingly widespread, such as warehouse / transportation / materials / fixed asset management. IoT technology typically includes passive or semi-passive IoT (P-IoT) technology, where network nodes can obtain energy from the environment to support data sensing, transmission, and distributed computing within the network.

[0003] In a passive or semi-passive IoT architecture, it typically includes passive or semi-passive tags, a reader, and a server. The reader can read and write to the tags (or RFID cards) via radio frequency to identify them and interact with them for information and data. The tags (i.e., semi-passive tags) can also store electrical energy through methods such as solar power and actively send signals of a specific frequency to the reader. The reader receives and decodes the information carried by this signal and then sends the decoded information to a central information system for corresponding data processing.

[0004] However, in existing tag reading and writing methods, when a terminal device acts as a reader, it may be shared by multiple enterprises, and the system does not involve providing enterprise information through the tag. This prevents the reader from directly establishing a user plane channel with the server of the enterprise to which the target tag belongs. Furthermore, the reader does not implement different routing strategies based on the enterprise information provided by different tags, making it impossible for the network to identify the enterprise to which the tag belongs and provide different communication services to different enterprises.

[0005] Therefore, there is an urgent need to propose a communication method that can effectively and accurately transmit tag information. Summary of the Invention

[0006] A communication method and apparatus that can effectively and accurately transmit tag information.

[0007] Firstly, this application provides a first communication method, which can be executed by a first communication device. The first communication device can be a reader (or a controller or chip corresponding to the reader) or a terminal device (or a controller or chip corresponding to the terminal device) that establishes a communication connection with the reader. The terminal device can be, but is not limited to, a computer, mobile phone, tablet computer, or other device capable of establishing a communication connection with the reader; no limitation is made in this regard. The method specifically includes the following steps: the first communication device receives a first request, which instructs the first communication device to obtain information about a first tag; the first communication device obtains the information about the first tag according to the first request, the information about the first tag including an identifier of the first tag; the first communication device determines a first communication session based on the identifier of the first tag, the first communication session being used to transmit the information about the first tag; and the first communication device sends the information about the first tag through the first communication session.

[0008] For example, if the device used to request information about the first tag is an application server of the enterprise to which the first tag belongs, then the first communication device can receive the first request from the application server. Furthermore, the first communication device sends the information about the first tag to the application server through a first communication session. This application does not specifically limit the transmission path used by the first communication device to send the information about the first tag to the application server.

[0009] In this application, after obtaining information of the first tag based on the first request, the first communication device can determine a first communication session specifically for transmitting the information of the first tag, thereby effectively improving the accuracy of the first communication device in transmitting the information of the first tag.

[0010] In one possible implementation, the first communication device determines a first communication session based on the identifier of the first tag, including: the first communication device determines the first communication session from at least one communication session based on the identifier of the first tag and first routing policy information, wherein the first routing policy information includes the correspondence between the identifier of the first tag and the identifier of the first communication session.

[0011] The first routing policy information can be an improvement on the existing user equipment routing selection policy (URSP), that is, the URSP policy adds a correspondence between the label identifier and the communication session identifier, so that the first communication device can also determine the appropriate communication session based on the label identifier.

[0012] It should be noted that the first routing policy information may also include the correspondence between the identifier of the first tag and the address information and / or port number information of the target server. Therefore, the first communication device can also determine the address information and / or port number information of the target server corresponding to the first tag based on the correspondence contained in the first routing policy information. Furthermore, based on the correspondence between the server's address information and / or port number information and the communication session (which may also be included in the first routing policy information or stored in the first communication device), the first communication session corresponding to the address information and / or port number information of the target server is determined. This application does not limit the specific method by which the first communication device determines the first communication session based on the first routing policy information.

[0013] With this implementation, since the first routing policy information includes the identifier of the first tag and the correspondence between the identifier of the first tag and the identifier of the first communication session, the first communication device can accurately determine the first communication session used to transmit the information of the first tag according to the first routing policy information, thereby improving the accuracy of transmitting the information of the first tag.

[0014] In one possible implementation, before the first communication device receives the first request, the method further includes: the first communication device establishing at least one communication session, the at least one communication session including the first communication session; and the first communication device establishing at least one routing policy information, each of the routing policy information including a correspondence between a corresponding tag and an identifier of the communication session.

[0015] In this implementation, before receiving a request to obtain information about a first tag, the first communication device needs to establish at least one communication session. This first communication session includes a first communication session and corresponding routing policy information, such that the routing policy information includes a correspondence between the tag and the communication session identifier. Therefore, the first communication device establishes at least one valid communication path and corresponding routing policy information for transmitting tag information. Subsequently, the first communication device can select a suitable communication session from the at least one communication session to transmit the first tag information based on the first tag identifier and the corresponding routing policy, thereby ensuring the validity and accuracy of the transmitted first tag information.

[0016] In this application, since the paths through which the first communication device transmits tag information may differ, the establishment of a first communication session by the first communication device may include, but is not limited to, the following methods:

[0017] In the first implementation, the first communication device establishes the first communication session by: the first communication device sending a first session request message, the first session request message containing first indication information indicating the home enterprise information of the first tag; the first communication device receiving a first response message, the first response message being used to respond to the first session request message, the first response message containing first target address information and / or first port number information, wherein the first target address information and / or the first port number information is determined based on the first indication information; the first communication device establishing the first communication session based on the first target address information and / or the first port number information; the first target address information and / or the first port number information being used to determine a target server, the target server being the server of the home enterprise.

[0018] For example, the process of establishing the first communication session by the first communication device can refer to the existing PDU session establishment process, which will not be described in detail here. However, the difference is that in this embodiment, the first communication device carries first indication information for indicating the tag's affiliated enterprise information in the session request message. The first target address information and / or the first port number information can be determined by the session management function (SMF) network element in the process based on the first indication information (or the first tag's affiliated enterprise information), or it can be determined by other network elements based on the first indication information (or the first tag's affiliated enterprise information) and then sent to the session management function (SMF) network element. This application does not specifically limit this.

[0019] The label-attributed enterprise information can be, but is not limited to, Data Network Element Name (DNN) and / or Network Slice Selection Assistance Information (NSSAI). The aforementioned first indication information can be used to indicate the DNN and / or NSSAI of the access label-attributed enterprise, or the first indication information can be the DNN and / or NSSAI of the access label-attributed enterprise; this application does not limit this. The DNN and / or NSSAI indicates the network information of the target enterprise that the first communication device requests to establish.

[0020] By means of implementation, the address and / or port number of the target server of the first tag are determined based on the enterprise information of the first tag, so that the communication connection (i.e. the first communication session) between the first communication device and the target server of the first tag can be established effectively and accurately.

[0021] Based on this first implementation, the first communication device can directly establish a first communication session with the target server. The first communication device sends information about the first tag through this first communication session, including sending the information about the first tag to the target server through the first communication session.

[0022] Through this implementation, the first communication device can effectively and accurately send the information of the first tag to the target server through the first communication session between the first communication device and the target server.

[0023] In the second implementation, the first communication device establishes the first communication session by: the first communication device sending a second session request message, the second session request message containing second indication information indicating the home enterprise information of the first tag; the first communication device receiving a second response message, the second response message being used to respond to the second session request message, the second response message containing second target address information and / or second port number information; wherein the second target address information and / or the second port number information is determined based on the second indication information; the first communication device establishing the first communication session based on the second target address information and / or the second port number information; the second target address information and / or the second port number information being used to determine a first user plane function network element, the first user plane function network element being a user plane network element providing services to the home enterprise.

[0024] For example, the process of establishing the first communication session by the first communication device can refer to the existing PDU session establishment / modification process, which will not be described in detail here. The second target address information and / or the second port number information can be determined by the session management function SMF network element in the process based on the second indication information (or the first tag's enterprise information), or it can be determined by other network elements based on the second indication information (or the first tag's enterprise information) and then sent to the session management function SMF network element. This application does not specifically limit this.

[0025] The tag-owning enterprise information can be, but is not limited to, a DNN and / or an NSSAI. The aforementioned second indication information can be used to indicate the DNN and / or NSSAI of the access tag-owning enterprise, or the second indication information can be the DNN and / or NSSAI of the access tag-owning enterprise; this application does not limit this. The DNN and / or NSSAI indicates the network information of the target enterprise that the first communication device requests to establish.

[0026] Optionally, the enterprise information to which the label belongs can be the data network element name (DNN).

[0027] The second implementation method determines the address information and / or port information of the first user plane function network element of the first tag based on the enterprise information of the first tag, thereby effectively and accurately establishing a communication connection (i.e., the first communication session) between the first communication device and the first user plane function network element of the first tag.

[0028] Based on this second implementation, the first communication device can establish a first communication session with the first user plane function network element. The first communication device sends information about the first tag through this first communication session, including: the first communication device sending the information about the first tag to the first user plane function network element through the first communication session.

[0029] Through this second implementation, the first communication device can also send the information of the first tag to the target server through the first user plane function network element.

[0030] Secondly, this application provides a first communication method, which can be executed by a first user plane function network element or by a chip corresponding to the first user plane function network element, without limitation. The method specifically includes the following steps: the first user plane function network element receives information from a first tag and first information, the first information being used to determine the target server of the first tag; the first user plane function network element determines the target server of the first tag based on the first information; the first user plane function network element sends the information of the first tag to the target server.

[0031] In this application, the first user plane function network element receives information from the first tag and first information. Since the first information is used to determine the target server of the first tag, the first user plane function network element can determine the target server of the first tag based on the first information, and then effectively and accurately send the information of the first tag to the target server.

[0032] In one possible implementation, the first user plane function network element receives first information, including: the first user plane function network element receives an N4 session request message, the N4 session request message includes the first information, the first information instructs a first tag filter, the first tag filter is used to match the corresponding server according to the tag identifier;

[0033] In this implementation, the first user plane function network element determines the target server of the first tag based on the first information, including: the first user plane function network element determines the first tag filter based on the first information; the first user plane function network element matches the target server of the first tag using the first tag filter based on the identifier of the first tag.

[0034] For example, the first user plane function UPF network element can receive the N4 session request message from the session management function SMF network element during the PDU session establishment / modification process. The N4 session request message includes the first message.

[0035] In this implementation, the first user plane function network element receives an N4 session request message and obtains the first message carried in the N4 session request message. The first message indicates a first tag filter. Therefore, the first user plane function network element can determine the first tag filter based on the first information. The first tag filter is used to match the corresponding server according to the tag identifier. Thus, the first user plane function network element can accurately match the target server of the first tag based on the identifier of the first tag and by using the first tag filter.

[0036] In one possible implementation, the first user plane function network element receiving information from the first tag includes: the first user plane function network element receiving information from the first communication device regarding the first tag.

[0037] In this implementation, the first user plane function network element receives the first information, including: the first user plane function network element receives an N4 session request message, the N4 session request message includes the first information, the first information indicating the address information of the first communication device and / or the third port number information of the first communication device for sending the information of the first tag;

[0038] Furthermore, the first user plane function network element determines the target server of the first tag based on the first information, including: the first user plane function network element determines the address information and / or the third port number information of the first communication device based on the first information; the first user plane function network element determines the target server of the first tag based on the address information and the third port number information of the first communication device, and the first mapping information; wherein, the first mapping information includes the correspondence between the address information and / or port number information of the first communication device and the identifier of the server.

[0039] The first mapping information includes the correspondence between the address information and / or port number information of the first communication device and the identifier of the server, which can be a pre-configured and known relationship.

[0040] In this implementation, when the first user plane function network element receives the information of the first tag from the first communication device, and the first user plane function network element receives an N4 session request message, which includes the address information of the first communication device and / or the third port number information of the first communication device for sending the information of the first tag, then the first user plane function network element can accurately determine the target server of the first tag based on the address information of the first communication device and / or the third port number information of the first communication device for sending the information of the first tag and the first mapping information.

[0041] In one possible implementation, the first user plane function network element receives first information, including: the first user plane function network element receives an N4 session request message, the N4 session request message including the first information, the first information indicating the fourth port number information on the first user plane function network element for receiving information of the first tag; the first user plane function network element determines the target server of the first tag based on the first information, including: the first user plane function network element determines the fourth port number information on the first user plane function network element for receiving information of the first tag based on the first information; the first user plane function network element determines the target server of the first tag based on the fourth port number information and second mapping information; wherein, the second mapping information includes the correspondence between the port number information on the first user plane function network element and the identifier of the server.

[0042] In this implementation, when the first user plane function network element receives an N4 session request message, which includes first information indicating the fourth port number information on the first user plane function network element that receives the information of the first tag, then the first user plane function network element can accurately determine the target server of the first tag based on the fourth port number information and the second mapping information.

[0043] In one possible implementation, the first user plane function network element receives first information, including: the first user plane function network element receives an N4 session request message, the N4 session request message including the first information, the first information indicating the address information of the target server and / or the fifth port number information of the target server used to receive information of the first tag; wherein, the address information of the target server and / or the fifth port number information is determined according to second indication information, the second indication information indicating the home enterprise information of the first tag, the second indication information being carried in a second session request message sent by the first communication device; the first user plane function network element determines the target server of the first tag according to the first information, including: the first user plane function network element determines the address information and / or the fifth port number information of the target server according to the first information; the first user plane function network element determines the target server according to the address information and / or the fifth port number information of the target server.

[0044] In this implementation, when the first user plane function network element receives an N4 session request message, which includes the address information of the target server and / or the fifth port number information on the target server used to receive the information of the first tag, the first user plane function network element can accurately determine the target server of the first tag based on the address information of the target server and / or the fifth port number information on the target server used to receive the information of the first tag.

[0045] Thirdly, this application provides a second communication method, which can be executed by a first network element or by a chip corresponding to the first network element, without limitation. The method specifically includes the following steps: the first network element receives a second message, which includes information about a first tag and a first identifier, the first identifier being used to determine the target server of the first tag; the first network element determines the target server of the first tag based on the first identifier; the first network element sends the information of the first tag to the target server.

[0046] For example, the first network element can receive the second message from the second network element. The first network element can be a Network Open Function (NEF) network element, and the second network element can be a first communication device (e.g., a terminal device with a reader / writer function) or an Access and Mobility Management Function (AMF) network element.

[0047] In this solution of the application, the first network element obtains the information of the first tag and the first identifier. Since the first identifier is used to determine the target server of the first tag, the first network element can determine the target server of the first tag based on the first identifier, and thus can accurately send the information of the first tag to the target server.

[0048] In one possible implementation, the first network element determines the target server of the first tag based on the first identifier, including: the first network element determines the target server of the first tag based on the first identifier and a first correspondence relationship, wherein the first correspondence relationship includes the correspondence relationship between the first identifier and the target server.

[0049] This implementation method enables the first network element to effectively and accurately determine the corresponding target server.

[0050] In one possible implementation, before the first network element obtains the second message from the second network element, the method further includes: the first network element sending a first message to the second network element, the first message including a first operation instruction and a second tag filter, and a first identifier, the first operation instruction being used to instruct the second network element to obtain the identifier of the first tag from the identifiers of at least one tag according to the first identifier, and the second tag filter being used to determine the information of the corresponding tag according to the identifiers of different tags.

[0051] It should be noted that the first identifier can be information used to identify the target server. For example, the first identifier can be the identifier of the first message or the identifier of the first operation instruction. The identifier of the first message and the target server have a one-to-one correspondence. This application does not make any specific limitations in this regard.

[0052] In this implementation, the first network element sends a first operation instruction, a second tag filter, and a first identifier to the second network element, so that the second network element can obtain the information of the first tag based on the first operation instruction, the first identifier, and the second tag filter. This ensures that the first network element can effectively obtain the information of the first tag and the first identifier from the second network element, and accurately determine the target server of the first tag based on the first identifier.

[0053] Fourthly, this application provides a second communication method, which can be executed by a second network element or by a chip corresponding to the second network element, without limitation. The method specifically includes the following steps: the second network element receives a first message, which includes a first operation instruction, a second tag filter, and a first identifier; wherein the first operation instruction instructs the second network element to acquire the identifier of at least one tag, the second tag filter determines the information of the corresponding tag based on the identifiers of different tags, and the first identifier determines the target server of the first tag; the second network element acquires the identifier of the first tag based on the first operation instruction and the first identifier, and matches the second tag filter based on the identifier of the first tag to obtain the information of the first tag; the second network element sends a second message, which includes the information of the first tag and the first identifier.

[0054] For example, the first network element can be a first communication device, such as a terminal device with a reader / writer function, and the second network element can be an access and access and mobility management function (AMF) network element.

[0055] In this application, a second network element receives a first message, which includes a first operation instruction, a second tag filter, and a first identifier. The second network element can then perform a tag operation according to the first operation instruction, obtain the identifier of the first tag from the identifiers of at least one tag, and match the second tag filter based on the identifier of the first tag to accurately obtain the information of the first tag. The second network element then sends the information of the first tag and the first identifier to the first network element, thereby enabling the first network element to quickly and accurately determine the target server of the first tag based on the first identifier.

[0056] In one possible implementation, the second network element receiving the first message includes: the second network element receiving the first message from the mobility management function network element; the second network element sending the second message includes: the second network element sending the second message to the mobility management function network element.

[0057] For example, the second network element is a first communication device, such as a terminal device with a reader / writer function. The terminal device can receive a first message from a NEF network element (i.e., the first network element) through an AMF network element (i.e., a mobility management function network element). After the terminal device determines a first tag based on the first message, it can send the information of the first tag to the AMF network element, and then the AMF network element can send the information of the first tag to the NEF network element.

[0058] Through this implementation, the second network element can effectively receive the first message from the mobility management function network element, and after determining the first tag, send a second message containing information about the first tag to the mobility management function network element.

[0059] In one possible implementation, the second network element receives the first message from the first network element; the second network element sends a second message, including sending the second message to the first network element.

[0060] For example, the second network element is an AMF network element (i.e., a mobility management function network element). The AMF network element receives a first message from the NEF network element (i.e., the first network element). Based on the first message, the AMF network element determines the first tag and then sends the information of the first tag to the NEF network element.

[0061] It should be noted that when the second network element is an AMF network element, the second network element can first obtain all tag information, including the information of the first tag, from the first communication device (such as a terminal device with reader / writer function).

[0062] In this implementation, the second network element directly receives the first message from the first network element, determines the first tag based on the first message, and then sends a second message containing information about the first tag to the first network element.

[0063] Fifthly, this application provides a communication device that can be applied to a first communication device and has the function of implementing the first aspect or any possible implementation of the first aspect; or, the communication device can be applied to a first user plane function network element and has the function of implementing the second aspect or any possible design method of the second aspect. The device may include: a receiving unit, a processing unit, and a transmitting unit.

[0064] Sixthly, this application also provides a communication device that can be applied to a first network element and has the function of implementing the third aspect or any possible implementation thereof; or, the communication device can be applied to a second network element and has the function of implementing the fourth aspect or any possible design thereof. The device may include: a receiving unit, a processing unit, and a transmitting unit.

[0065] In a seventh aspect, this application also provides a communication device that can be applied to a first communication device. The communication device includes a processor for implementing the functions of the first aspect or any possible implementation thereof; or, the communication device can be applied to a first user plane function network element for implementing the functions of the second aspect or any possible design thereof. Optionally, the communication device further includes a transceiver for implementing the communication functions of the communication device.

[0066] Eighthly, this application also provides another communication device, which can be applied to a first network element. The communication device includes a processor for implementing the functions of the third aspect or any possible implementation thereof; or, the communication device can be applied to a second network element for implementing the functions of the fourth aspect or any possible design thereof. Optionally, the communication device further includes a transceiver for implementing the communication functions of the communication device.

[0067] Ninthly, this application also provides a communication system, which includes a first communication device (such as a terminal device) for performing the method provided in the first aspect above, and a first user plane function network for performing the method provided in the second aspect above.

[0068] In a tenth aspect, this application also provides a communication system, which includes a first network element (such as a network capability open function network element) for performing the method provided in the third aspect above, and a second network element (a first communication device, such as a terminal device with read and write functions, or an access and mobility function management network element) for performing the method provided in the fourth aspect above.

[0069] Eleventhly, embodiments of this application also provide a computer storage medium storing a software program that, when read and executed by one or more processors, can implement the method provided in the first aspect or any of the possible implementations described above, or implement the method provided in the second aspect or any of the possible implementations described above; or, when read and executed by one or more processors, the software program can implement the method provided in the third aspect or any of the possible implementations described above, or implement the method provided in the fourth aspect or any of the possible implementations described above.

[0070] In a twelfth aspect, embodiments of this application also provide a computer program product containing instructions that, when run on a computer, cause the method provided in the first aspect or any of the possible implementations therein to be executed, or cause the method provided in the second aspect or any of the possible implementations therein to be executed; or, when run on a computer, cause the method provided in the third aspect or any of the possible implementations therein to be executed, or cause the method provided in the fourth aspect or any of the possible implementations therein to be executed.

[0071] In a thirteenth aspect, embodiments of this application also provide a chip system, the chip system including a processor, configured to support a first communication device in implementing the functions involved in the first aspect; or to support a first user plane function network element in implementing the functions involved in the second aspect; or to support a first network element in implementing the functions involved in the third aspect; or to support a second network element in implementing the functions involved in the fourth aspect.

[0072] In one possible design, the chip system further includes a memory for storing necessary program instructions and data to be executed by the loading device. The chip system may consist of chips or may include chips and other discrete components.

[0073] The technical effects that can be achieved by the fifth and seventh aspects and any of their possible implementations can be referred to the first and second aspects and any of their possible implementations. The technical effects that can be achieved by the sixth and eighth aspects and any of their possible implementations can be referred to the third and fourth aspects and any of their possible implementations. They will not be repeated here. Attached Figure Description

[0074] Figure 1 A schematic diagram illustrating tag reading and writing for a passive or semi-passive Internet of Things (IoT) system.

[0075] Figure 2 This is a schematic diagram illustrating the process of a reader / writer performing an inventory check on tags (such as P-IoT tags).

[0076] Figure 3A This is a schematic diagram of the transmission path for the first type of tag information;

[0077] Figure 3B This is a schematic diagram of the transmission path for the second type of tag information;

[0078] Figure 3C This is a schematic diagram of the transmission path for the third type of tag information;

[0079] Figure 4 A schematic diagram of a network architecture provided in an embodiment of this application;

[0080] Figure 5A A flowchart illustrating a communication method provided in an embodiment of this application;

[0081] Figure 5B A flowchart illustrating another communication method provided in an embodiment of this application;

[0082] Figure 6 A flowchart illustrating another communication method provided in an embodiment of this application;

[0083] Figure 7 A flowchart illustrating the first embodiment provided in this application;

[0084] Figure 8 A flowchart illustrating the second embodiment provided in this application;

[0085] Figure 9 A flowchart illustrating the third embodiment provided in this application;

[0086] Figure 10 A flowchart illustrating the fourth embodiment provided in this application;

[0087] Figure 11 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0088] Figure 12 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0089] Figure 13 This is a schematic diagram of the structure of a chip device provided in an embodiment of this application. Detailed Implementation

[0090] This application provides a communication method and apparatus, wherein the method and apparatus are based on the same or similar technical concepts. Since the methods and apparatus solve problems in similar principles, the implementation of the methods and apparatus can refer to each other, and repeated parts will not be described again.

[0091] To facilitate understanding of the technical solutions of the embodiments of this application, the existing passive or semi-passive Internet of Things (IoT) technologies will be briefly introduced below.

[0092] With the development of IoT technology, its application scenarios are becoming increasingly widespread, such as warehouse / transportation / materials / fixed asset management. IoT technology typically includes passive or semi-passive Internet of Things (P-IoT) technology, where network nodes can obtain energy from the environment to support data sensing, transmission, and distributed computing within the network.

[0093] In a passive or semi-passive IoT architecture, it typically includes passive or semi-passive tags, a reader, and a server. The reader can read and write to the tags (or RFID cards) via radio frequency to identify them and interact with them for information and data. Tags (i.e., semi-passive tags) can also store electrical energy through methods such as solar power and actively send signals of a specific frequency to the reader. The reader receives and decodes the information carried by this signal and then sends the decoded information to a central information system for corresponding data processing. Although this paper uses the term "passive tag / semi-passive tag" to define the terminal name in IoT technology, this application is also applicable to other terminal names using similar IoT technologies, such as energy storage tags, passive energy storage tags, and zero-power terminals.

[0094] like Figure 1 The diagram illustrates a passive or semi-passive IoT tag reading and writing process, which may include the following steps:

[0095] S101: The P-IoT application (P-IoT APP) sends inventory / access rules to the reader.

[0096] Accordingly, the reader receives the inventory / access rule.

[0097] For example, the inventory / access rule could be: to conduct an inventory check every hour, and to obtain information about the storage areas of tag 1, tag 2, and tag 3.

[0098] S102: The reader performs an inventory of the tags (such as P-IoT Tag) and obtains the tag identifier.

[0099] For example, the reader performs an inventory check on the tags according to the received inventory / access rules, such as performing an inventory check on the tags to be accessed once per hour, and obtaining the identifier of the tags to be accessed.

[0100] It should be understood that the process of the reader inventorying tags can be understood as the process of the reader establishing a connection and interacting with the tag (such as P-IoTTag) to obtain information from each other. Typically, each tag has a corresponding identifier, including but not limited to an electronic product code (EPC) and a tag identifier (TID).

[0101] During the inventory process, the tag sends its EPC or TID to the reader, so that the reader can know which tags are within its coverage area and report to the middleware and server.

[0102] S103: The reader performs tag access on the P-IoT tag.

[0103] After the reader completes the inventory count, the tags to be connected are connected to the reader to complete the tag connection process, so that subsequent readers can obtain the information of the connected tags.

[0104] S104: The reader feeds back the inventory information and tag access information to the P-IoT APP.

[0105] The reader feeds back the tag inventory information / tag access information to the P-IoT APP.

[0106] Regarding the process of the reader performing an inventory check on the tag (such as a P-IoT Tag) in step S102 above, refer to... Figure 2 As shown, the specific process is as follows:

[0107] S201: The reader sends a Select command to the P-IoT Tag.

[0108] Correspondingly, the P-IoT Tag receives the Select command.

[0109] Specifically, after receiving the inventory command, the reader generates a Select command and then sends it to the P-IoT Tag. This inventory command includes the range of tags, such as EPC / TIDs within a specific range. Upon receiving (listening to) the Select command, the tag checks if it falls within the tag range required by the Select command. If it does, it continues to listen for subsequent Query commands; otherwise, the tag does not perform any further steps (i.e., no action is taken).

[0110] S202: The reader sends a query command to the P-IoT Tag.

[0111] Correspondingly, when a P-IoT Tag receives a valid Query command, it will generate a random number.

[0112] S203: The P-IoT Tag sends RN-16 to the reader.

[0113] For example, a tag with a random number of 0, upon receiving a valid Query command, will send a temporary password RN-16, which is a 16-bit random number, back to the reader.

[0114] S204: The reader sends an acknowledgment (ACK) command to the P-IoT Tag.

[0115] When the reader receives a random number from the tag, it sends an ACK command to the tag, which contains the random number (RN16) that was just received.

[0116] S205: Verify the correctness of the random number in the P-IoT Tag ACK command.

[0117] If the random number in the P-IoT Tag verification ACK command is correct, proceed to the next step S206.

[0118] S206: The P-IoT Tag sends an EPC code to the reader.

[0119] At the same time, after the P-IoT Tag sends its own EPC code to the reader, it enters a brief sleep state.

[0120] After receiving the EPC code of the tag, the reader completes the inventory of the tag.

[0121] Optionally, the reader will continue to send QueryRep commands. The tag that receives the QueryRep will decrement the original random number by 1 and re-execute the above steps S203-S206 until all tags have been inventoried.

[0122] In existing 3GPP networks, when a UE is used as a reader / writer, the main transmission paths that support passive or semi-passive IoT read / write processes can include the following.

[0123] First transmission method: Reference Figure 3A As shown, the reader manages the tags and establishes a user plane connection directly with the enterprise server through the reader. Thus, the tag information (or instructions) can be transmitted through the user plane connection established by the reader.

[0124] Second transmission path: (Reference) Figure 3BAs shown, the UPF network element manages the tags, and the reader establishes a user plane connection with the UPF network element, and the UPF network element establishes a user plane connection with the enterprise server. Thus, the information (or instructions) of the tags read and written by the reader can be transmitted through the aforementioned user plane connection.

[0125] Third transmission path: (Reference) Figure 3C As shown, the data can be transmitted through the control plane channel. That is, the server sends instructions to the AMF network element through the NEF network element, and then the AMF network element can obtain the tag information and / or data from the UE. The AMF network element or the control plane (CP) network element performs tag management and can send the tag information to the application server through the NEF network element.

[0126] However, in existing tag reading and writing methods, when a terminal device acts as a reader, it may be shared by multiple enterprises, and the system does not involve providing enterprise information through the tag. This prevents the reader from directly establishing a user plane channel with the server of the enterprise to which the target tag belongs. Furthermore, the reader does not implement different routing strategies for different tags by providing enterprise information, making it impossible for the network to identify the enterprise to which the tag belongs and provide different communication services to different enterprises.

[0127] Therefore, this application proposes a communication method, which includes: a first communication device receiving a first request, the first request instructing the first communication device to obtain information of a first tag, the information of the first tag including an identifier of the first tag; then, the first communication device obtaining the information of the first tag according to the first request; secondly, the first communication device determining a first communication session, the first communication session being used to transmit the information of the first tag; and finally, the first communication device sending the information of the first tag through the first communication session. Through this method, after obtaining the information of the first tag (i.e., the target tag), the first communication device determines a corresponding first communication session for the information of the first tag, thereby ensuring that the first communication device can effectively and accurately transmit the information of the first tag through the first communication session.

[0128] The proposed solution can be applied to 5G system architecture, as well as to, but is not limited to, long-term evolution (LTE) communication systems and various future wireless communication systems.

[0129] Figure 4 This diagram illustrates a network architecture to which a communication method provided in an embodiment of this application applies. Figure 4 As shown, this network architecture can include an access network and a core network. Terminal devices access the data network (DN) through the access network and the core network.

[0130] Terminal devices can be user equipment (UE), mobile stations, mobile terminals, application clients, etc. They can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, etc. Terminal devices can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, urban air mobility vehicles (such as drones, helicopters, etc.), ships, robots, robotic arms, smart home devices, etc. The accompanying drawings and the following embodiments use a UE as an example of a terminal device for illustration; however, any subsequent mention of a UE can be replaced with a terminal device or other examples of terminal devices.

[0131] The access network is used to implement access-related functions. It can provide network access to authorized users in a specific area and determine transmission links of different qualities to transmit user data based on user level, service requirements, etc. The access network forwards control signals and user data between the UE and the core network. The access network can include access network equipment, which can be devices that provide access for the UE, and can include radio access network (RAN) equipment and wired access network equipment. RAN equipment is mainly responsible for functions such as radio resource management, quality of service (QoS) management, data compression, and encryption on the air interface side. RAN equipment can include various forms of base stations, such as macro base stations, micro base stations (also known as small stations), relay stations, access points, balloon stations, etc. In systems using different radio access technologies, the names of equipment with base station functions may differ. For example, in 5G systems, it is called RAN or next-generation Node base station (gNB), and in Long Term Evolution (LTE) systems, it is called evolved Node B (eNB or eNodeB).

[0132] Access network devices and UEs 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 the access network devices and UEs.

[0133] The core network is responsible for maintaining the subscription data of the mobile network and providing UEs with functions such as session management, mobility management, policy management, and security authentication. 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.

[0134] AMF network elements are primarily responsible for mobility management in mobile networks, such as user location updates, user network registration, and user handover.

[0135] SMF (Service Provider Function) network elements are primarily responsible for session management in mobile networks, such as session establishment, modification, and release. Specific functions include assigning Internet Protocol (IP) addresses to users and selecting a UPF (User Provider Function) to provide packet forwarding capabilities.

[0136] The UPF network element is mainly responsible for forwarding and receiving user data. It can receive user data from the data network and transmit it to the UE through the access network equipment; it can also receive user data from the UE through the access network equipment and forward it to the data network.

[0137] UDM network elements include functions such as managing contracted data and authorizing user access.

[0138] UDR network elements include functions for storing and retrieving data of various types, such as contract data, policy data, and application data.

[0139] NEF network elements are primarily used to support the opening of capabilities and events.

[0140] An AF (Application Provider) element conveys the application's requests to the network, such as QoS requirements or user state event subscriptions. AFs can be third-party functional entities or application services deployed by operators, such as the IP Multimedia Subsystem (IMS) voice call service.

[0141] The PCF network element primarily supports providing a unified policy framework to control network behavior, providing policy rules to control layer network functions, and is also responsible for acquiring user subscription information related to policy decisions. The PCF network element can provide policies, such as QoS policies and slice selection policies, to AMF and SMF network elements.

[0142] NRF network elements can be used to provide network element discovery functionality, providing network element information corresponding to the network element type based on requests from other network elements. NRF also provides network element management services, such as network element registration, updates, deregistration, and network element status subscription and push.

[0143] The AUSF network element is responsible for authenticating the UE and verifying its legitimacy.

[0144] NWDAF network elements have functions such as providing network data collection and analysis based on big data and artificial intelligence technologies.

[0145] A Data Network (DN) can be used to deploy various services, providing data and / or voice services to the User Equipment (UE). For example, a DN might be the private network of a smart factory. Sensors installed in the workshop can act as UEs, and a control server for these sensors is deployed within the DN. This control server provides services to the sensors. Sensors can communicate with the control server, receive instructions, and transmit collected sensor data back to the control server accordingly. Another example is a DN serving as the internal office network of a company. Employees' mobile phones or computers can act as UEs, accessing information and data resources within the company's internal office network.

[0146] Among them, 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 abbreviated as AF, UDM, UDR, PCF, SMF, AMF, NRF, AUSF, NEF, UPF, and NWDAF, respectively. Figure 1 As shown in the image.

[0147] Figure 1 Nausf, Nnef, Nnrf, Namf, Npcf, Nsmf, Nudm, Nudr, Naf, and Nnwdaf are the service interfaces provided by AUSF, NEF, NRF, AMF, PCF, SMF, UDM, UDR, AF, and NWDAF, respectively, used to invoke the corresponding service operations. N1, N2, N3, N4, and N6 are interface sequence numbers, with the following meanings:

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

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

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

[0151] 4) N4: The interface between SMF and UPF, which can be used to transmit information between the control plane and the user plane, including the distribution of forwarding rules, QoS rules, traffic statistics rules, etc. from the control plane to the user plane, as well as the reporting of information from the user plane.

[0152] 5) N6: The interface between UPF and DN, used to transmit uplink and downlink user data streams between UPF and DN.

[0153] It is understood that the aforementioned network element or function can be a network component in a hardware device, a software function running on dedicated hardware, or a virtualization function instantiated on a platform (e.g., a cloud platform). As one possible implementation method, the aforementioned network element or function can be implemented by a single device, multiple devices working together, or a functional module within a single device; this application does not specifically limit this.

[0154] The technical solution of this application is described below with reference to specific embodiments.

[0155] This application provides a communication method, which can be applied to, but is not limited to, [the following]. Figure 4 The network architecture described herein is described, and the method can be executed by the network element involved in this application, or by the chip corresponding to the network element involved. The network element in this application can be a physical entity network element or a virtual network element. This application does not specifically limit the form of the network element involved.

[0156] Furthermore, in this embodiment, the device primarily used for tag identification is referred to as the first communication device. This first communication device can be a reader (or a controller or chip corresponding to the reader), or a terminal device (or a controller or chip corresponding to the terminal device) that establishes a communication connection with the reader. The terminal device can be, but is not limited to, a computer, mobile phone, tablet computer, or other device capable of establishing a communication connection with the reader. It should be noted that the ordinal numbers such as "first" and "second" mentioned below are used to distinguish multiple objects for ease of description and are not intended to limit the order, timing, priority, or importance of the multiple objects. This application does not limit the specific form of the first communication device and the network elements involved in executing this embodiment.

[0157] See Figure 5A As shown in the figure, this is a flowchart of a communication method provided in an embodiment of this application, which may specifically include the following steps:

[0158] S501A: The first communication device receives the first request from the target server.

[0159] The first request instructs the first communication device to obtain information about a first tag, wherein the first tag may be a group of tags conforming to a certain inventory rule. For example, the first tag may be a group of tags within a certain area, a group of tags of a certain type, a group of tags containing certain fields, or a group of tags belonging to a certain enterprise / operator. For example, the first tag may also be a specific tag identifier, wherein the specific tag identifier may be included in the inventory rule.

[0160] For example, the first request may be a data transmission message sent through the user plane, or a non-access stratum message sent through the control plane, such as a downlink non-access stratum transmission message.

[0161] For example, the first communication device can be a reader, such as a UE. If the application server (such as a PIOT server) needs to obtain the information of the corresponding first tag, it can send a first request to the UE. The first request instructs the UE to obtain the information of the first tag, which includes the identifier of the first tag (such as EPC, TID). Accordingly, the UE receives the first request from the application server.

[0162] In this application, the first communication device further includes a tag inventory process before receiving the first request, or, after receiving the first request and before determining the first communication session (or after step S501A and before step S502A), the first communication device also performs a tag inventory process. That is, the first request message also includes instruction information required for the first communication device to perform tag inventory, wherein the instruction information may include, but is not limited to, one or more of the following: tag inventory range, tag type, tag owner company, and tag owner operator. The specific tag inventory process can be referred to the above. Figure 2 The process shown will not be described in detail here.

[0163] Through the above-described tag inventory process, it can be ensured that the first tag (i.e., the target tag) obtained by the first communication device as indicated by the first request information can be connected to the first communication device. Furthermore, the first communication device can effectively obtain the information of the first tag.

[0164] S502A: The first communication device obtains information about the first tag according to the first request, the information of the first tag including the identifier of the first tag.

[0165] S503A: The first communication device determines a first communication session based on the identifier of the first tag, the first communication session being used to transmit information of the first tag.

[0166] In one embodiment, the first communication device determines a first communication session based on the identifier of a first tag, including: the first communication device determines the first communication session from at least one communication session based on the identifier of the first tag and first routing policy information, wherein the first routing policy information includes a correspondence between the identifier of the first tag and the identifier of the first communication session.

[0167] The first routing policy information in this application can be an improved User Equipment Routing Policy (URSP policy), that is, adding label identification information to the existing URSP policy (routing policy), so that the communication session corresponding to the information of the label can be selected based on the label identification.

[0168] For example, the first routing policy information described above can be specifically referred to in Table 1 of the following specific embodiment.

[0169] Optionally, the first routing policy information may further include the correspondence between the identifier of the first tag and the address information and / or port number information of the target server. Therefore, the first communication device can also determine the address information and / or port number information of the target server corresponding to the first tag based on the correspondence contained in the first routing policy information. Furthermore, it can determine the first communication session corresponding to the address information and / or port number information of the target server based on the correspondence between the server's address information and / or port number information and the communication session. This application does not limit the specific method by which the first communication device determines the first communication session based on the first routing policy information.

[0170] In one embodiment, before the first communication device receives the first request, the method further includes: the first communication device establishing at least one communication session, the at least one communication session including the first communication session; the first communication device establishing at least one routing policy information, each of the routing policy information including a correspondence between a corresponding tag and an identifier of the communication session.

[0171] The first communication device may establish a first communication session in the following ways, including but not limited to:

[0172] Implementation Method 1: A first communication device establishes a first communication session, comprising: the first communication device sending a first session request message, the first session request message containing first indication information indicating the home enterprise information of the first tag; the first communication device receiving a first response message, the first response message being used to respond to the first session request message, the first response message containing first target address information and / or first port number information, wherein the first target address information and / or the first port number information is determined based on the first indication information; the first communication device establishing the first communication session based on the first target address information and / or the first port number information; the first target address information and / or the first port number information being used to determine a target server, the target server being the server of the home enterprise.

[0173] Optionally, the first indication information mentioned above may be the enterprise's data network name (DNN), or the enterprise information to which the first label indicated by the first indication information belongs may be the enterprise information corresponding to the DNN.

[0174] In this application, the enterprise information belonging to the first tag can also be directly carried in the first session request message and sent by the first communication device. However, in order to reduce the overhead of transmitting the first session request message, the enterprise information belonging to the first tag can be indicated by first indication information, and the first communication device can send a first session request message containing the first indication information.

[0175] The above implementation method one can be based on the above. Figure 3A In the first transmission path implementation shown, the first communication device can be regarded as a UE (user-writer).

[0176] For example, the UE sends a PDU session establishment request message (equivalent to a first session request message) to the AMF network element. This first session request message contains first indication information for indicating the first tag's home enterprise information. After receiving the PDU session establishment request message, the AMF network element selects a suitable SMF network element and sends a PDU session creation session context request message to that SMF network element. Then, the AMF network element receives a PDU session creation session context response message from the SMF network element and receives an N1N2 message from the SMF network element. This N1N2 message carries the target PIOT server address (equivalent to first target address information) and port number information (equivalent to first port number information). The SMF network element sends an N2 PDU session request message (carrying the target PIOT server address and port number information) to the RAN. The RAN establishes air interface resources with the UE and sends a NAS message (equivalent to a first response message) to the UE. This NAS message carries the target PIOT server address and port number information. Finally, the UE can establish a connection with the target PIOT server (equivalent to establishing a first communication session) based on the target PIOT server address and port number information in the NAS message.

[0177] Implementation Method Two: The first communication device establishes a first communication session, including: the first communication device sending a second session request message, the second session request message containing second indication information, the second indication information indicating the home enterprise information of the first tag; the first communication device receiving a second response message, the second response message being used to respond to the second session request message, the second response message containing second target address information and / or second port number information; wherein, the second target address information and / or the second port number information is determined based on the second indication information; the first communication device establishing a first communication session based on the second target address information and / or the second port number information; the second target address information and / or the second port number information being used to determine a first user plane function network element, the first user plane function network element being a user plane network element providing services to the home enterprise.

[0178] The above implementation method two can be based on the above. Figure 3B In the second transmission path implementation shown, the first communication device can be regarded as a UE (user-writer) and the first user plane function network element can be a UPF network element.

[0179] In this second implementation method, the following two situations may also be included:

[0180] In the first scenario, there is only one user plane function network element used to transmit tag information; that is, the first user plane function network element is a shared user plane function network element. During the establishment of at least one communication session by the first communication device, the second target address information and / or the second port number information received by the first communication device are identical, and both the second target address information and / or the second port number information are used to indicate the first user plane function network element.

[0181] On the first user plane function network element side, different target address information and / or port number information can be received from the session management function network element. Each target address information and / or port number information is determined according to the corresponding label owner information (or indication information used to indicate the corresponding label owner information). Each target address information and / or port number information is used to indicate a corresponding server.

[0182] Optionally, the enterprise information to which the label belongs, or the indication information indicating that the label belongs to the enterprise, can be the enterprise's Data Network Name (DNN).

[0183] For example, UE1 obtains the address information (equivalent to the second target address information) and / or the corresponding port number information (equivalent to the second port number information) of a UPF1 network element (equivalent to the first user plane function network element). The address information and / or the corresponding port number information of the UPF1 network element are determined based on the DNN of the first tag-owning enterprise or based on the indication information of the DNN instructing the first tag-owning enterprise. Further, UE1 establishes a first PDU session connection with the UPF1 network element based on the address information and / or the corresponding port number information (equivalent to establishing a first communication session). For other tag-owning enterprises, UE1 can establish PDU sessions in the same way as establishing a first PDU session for the first tag-owning enterprise; that is, all are PDU sessions between UE1 and the UPF1 network element.

[0184] It should be noted that, based on the first situation described above, when the first communication device establishes at least one communication session, the second target address information received by the first communication device each time is the same and is used to indicate the first user plane function network element. However, the second port number information received on the first user plane function network element may be different. Therefore, the first communication device can also establish a corresponding communication session based on each second port number information.

[0185] The second scenario involves multiple user plane function network elements used to transmit tag information. Each tag's enterprise information corresponds to one user plane function network element. For example, the first tag's enterprise information corresponds to the first user plane function network element.

[0186] During the process of establishing at least one communication session, the second target address information and / or second port number information received by the first communication device each time are different. Each second target address information and / or second port number information is used to indicate a corresponding user plane function network element.

[0187] Therefore, in this second scenario, after establishing at least one communication session connection, the first communication device can determine the second target address information and / or the second port number information corresponding to the first tag based on the enhanced URSP strategy, thereby determining the first communication session.

[0188] For example, UE1 obtains the address information and / or corresponding port number information of UPF1 network element and the address information and / or corresponding port number information of UPF2 network element. The address information and / or corresponding port number information of UPF1 network element are determined based on the DNN_(1) of the enterprise to which tag 1 belongs, and the address information and / or corresponding port number information of UPF2 network element are determined based on the DNN_(1) of the enterprise to which tag 2 belongs. UE1 can establish a connection with UPF1 network element (i.e., establish a first communication session) based on the address information and / or corresponding port number information of UPF1 network element, and UE1 can establish a connection with UPF2 network element based on the address information and / or corresponding port number information of UPF2 network element.

[0189] The third scenario involves multiple user plane function network elements used to transmit tag information, including at least one user plane function network element corresponding to the information of one tag-owning enterprise, and one user plane function network element corresponding to the information of multiple tag-owning enterprises.

[0190] The information of multiple tag-owned enterprises corresponding to one user plane function network element can be referred to in the first case above. The information of one tag-owned enterprise corresponding to one user plane function network element can be referred to in the second case above. The details will not be elaborated here.

[0191] Through the above two implementation methods, the first communication session determined by the first communication device can be used to transmit the information of the first tag between the first communication device and the target server, or the first communication session can be used to transmit the information of the first tag between the first communication device and the first user plane function network element.

[0192] Therefore, the first communication device transmits the information of the first tag through the first communication session via two transmission paths: the first transmission path (i.e., Figure 3A The transmission path shown) refers to step S504A below, the second transmission path (i.e. Figure 3B (The transmission path shown) refers to the following steps S505A-S508A.

[0193] S504A: The first communication device sends the information of the first tag to the target server through the first communication session.

[0194] The information of the first tag may be the data of the first identifier. The information of the first tag may also include only the identifier of the first tag, and this application does not limit this.

[0195] Based on the first implementation method in step S503A above, the first communication device sends the information of the first tag to the target server through a first communication session. The information of the first tag may include the identifier of the first tag.

[0196] Therefore, through the above-described implementation method one, the first communication device can directly and accurately send the information of the first tag to the target server through the first communication session. The transmission of information for other tags by the first communication device can be implemented in the same way as the first communication device sending information of the first tag to the target server, and will not be elaborated further here.

[0197] S505A: The first communication device sends information of the first tag to the first user plane function network element through the first communication session.

[0198] Based on the second implementation method in step S503A above, the first communication device sends the information of the first tag to the first user plane function network element through the first communication session.

[0199] S506A: The first user plane function network element receives the information of the first tag and the first information, which is used to determine the target server of the first tag.

[0200] S507A: The first user plane function network element determines the target server of the first tag based on the first information.

[0201] When performing steps S506A-507A, the specific implementation methods may include, but are not limited to, the following:

[0202] In the first implementation method, the first user plane function network element receives first information, including: the first user plane function network element receives an N4 session request message, the N4 session request message includes first information, the first information instructs a first tag filter, the first tag filter is used to match the corresponding server according to the tag identifier.

[0203] The first information may indicate the first tag filter, or the first information may be the first tag filter itself; this application does not specifically limit this.

[0204] Furthermore, the first user plane function network element determines the target server of the first tag based on the first information, including: the first user plane function network element determines the first tag filter based on the first information; the first user plane function network element uses the first tag filter to match the target server of the first tag based on the identifier of the first tag.

[0205] In the second implementation, if the first user plane function network element receives the information of the first tag from the first communication device; the first user plane function network element receiving the first information includes: the first user plane function network element receiving an N4 session request message, the N4 session request message including the first information, the first information indicating the address information of the first communication device and / or the third port number information of the first communication device for sending the information of the first tag.

[0206] The first information may be used to indicate the address information of the first communication device and / or the third port number information of the first communication device for sending the information of the first tag. The first information may also be the address information of the first communication device and / or the third port number information of the first communication device for sending the information of the first tag. This application does not specifically limit this.

[0207] Furthermore, the first user plane function network element determines the target server of the first tag based on the first information, including: the first user plane function network element determines the address information and / or the third port number information of the first communication device based on the first information; the first user plane function network element determines the target server of the first tag based on the address information and the third port number information of the first communication device, and the first mapping information; wherein, the first mapping information includes the correspondence between the address information and / or port number information of the first communication device and the identifier of the server.

[0208] In the third implementation method, the first user plane function network element receives the first information, including: the first user plane function network element receives an N4 session request message, the N4 session request message includes the first information, the first information indicating the fourth port number information of the first user plane function network element that receives the information of the first tag.

[0209] The first information can be used to indicate the fourth port number information on the first user plane function network element that receives the information of the first tag. The first information can also be the fourth port number information on the first user plane function network element that receives the information of the first tag. This application does not make a specific limitation on this.

[0210] Furthermore, the first user plane function network element determines the target server of the first tag based on the first information, including: the first user plane function network element determines the fourth port number information on the first user plane function network element that receives the information of the first tag based on the first information; the first user plane function network element determines the target server of the first tag based on the fourth port number information and the second mapping information; wherein, the second mapping information includes the correspondence between the port number information on the first user plane function network element and the identifier of the server.

[0211] In the fourth embodiment, the first user plane function network element receives first information, including: the first user plane function network element receives an N4 session request message, the N4 session request message including first information, the first information indicating the address information of the target server and / or the fifth port number information of the target server used to receive the information of the first tag; wherein, the address information of the target server and / or the fifth port number information is determined according to second indication information, the second indication information indicating the home enterprise information of the first tag, and the second indication information is carried in the second session request message sent by the first communication device.

[0212] The first information may be used to indicate the address information of the target server and / or the fifth port number information on the target server used to receive the information of the first tag. The first information may also be the address information of the target server and / or the fifth port number information on the target server used to receive the information of the first tag.

[0213] Furthermore, the first user plane function network element determines the target server of the first tag based on the first information, including: the first user plane function network element determines the address information and / or the fifth port number information of the target server based on the first information; the first user plane function network element determines the target server based on the address information and / or the fifth port number information of the target server.

[0214] S508A: The first user plane function network element sends the information of the first tag to the target server.

[0215] Based on the second scenario of implementation method two in step S503A above, after the first communication device establishes at least one communication session connection, each user plane function network element is configured with a mapping relationship between the address information and / or third port number information and / or fourth port number information of the first communication device and the corresponding target server. Therefore, after obtaining the information of the first tag, the first communication device can determine the first communication session corresponding to the first tag according to the routing rules, and then the first communication device sends the information of the first tag to the corresponding first user plane function network element through the first communication session. The first user plane function network element obtains the information of the first tag from the first communication device based on the address information and / or third port number of the first communication device, and can directly determine the target server corresponding to the first tag, and then send the information of the first tag to the target server.

[0216] In this embodiment of the application, the above-mentioned "address information" can be understood as information used to determine the address, and "port number information" can be understood as information used to determine the port number. The "address information" can be simply referred to as "address", and the two can have the same meaning. The "port number information" can also be simply referred to as "port number", and the two can have the same meaning.

[0217] Through the communication method provided in this application, a first communication device can establish a communication session with a corresponding server based on the information of the tag's owner enterprise. This allows the first communication device, upon receiving information from a first tag, to accurately determine the first communication session for transmitting the first tag's information based on first routing policy information containing the tag's identifier. Subsequently, the first communication device can effectively and accurately transmit the first tag's information to the target server through this first communication session. Furthermore, the first communication device can also determine the first communication session for the first tag based on the first routing policy information. This first communication session is a communication session between the first communication device and the corresponding user plane function network element. Therefore, the first communication device can send the first tag's information to the corresponding user plane function network element through this first communication session, and the user plane function network element can then effectively and accurately send the first tag's information to the target server.

[0218] See Figure 5B As shown in the figure, this is a flowchart of another communication method provided by an embodiment of this application, which may specifically include the following steps:

[0219] S501B: The first network element sends a first message to the second network element, the first message including a first operation instruction and a second tag filter, as well as a first identifier.

[0220] The first operation instruction is used to instruct the second network element to obtain the identifier of the first tag from the identifiers of at least one tag according to the first identifier. The second tag filter is used to determine the information of the corresponding tag according to the tag identifier. The first identifier is used to determine the target server of the first tag.

[0221] In one implementation, the first network element sends the first message to the second network element. Correspondingly, the second network element receives the first message from the first network element.

[0222] For example, the first network element is a Network Capability Open Function (NEF) network element, and the second network element is a Mobility Management Function (AMF) network element. That is, the NEF network element sends a first message to the AMF network element, and the AMF network element directly receives the first message from the NEF network element.

[0223] In another implementation, the first network element sends a first message to the second network element, including sending the first message to the mobility management function (MMF) network element. Correspondingly, the second network element receives the content of the first message from the MMF network element. The content of the first message may include a first operation instruction and a second tag filter.

[0224] For example, the first message mentioned above may be an AMF communication service message, an AMF event open service message, an AMF non-IP data transmission service message, or other messages provided by AMF through service interfaces. This application does not specifically limit this.

[0225] It should be noted that the content of the first message mentioned above can be obtained by forwarding the first message to the second network element through the mobility management function network element, or by sending a third message to the second network element through the mobility management function network element, such as a downlink NAS transmission message, and carrying the content of the first message mentioned above in the third message, such as the first operation instruction and the second tag filter.

[0226] For example, the first network element is a Network Capability Open Function (NEF) network element, and the second network element is a first communication device (such as a UE with a reader / writer function). That is, the NEF network element first sends a first message to the AMF network element, which includes a first operation command, a second tag filter, and a first identifier. The AMF network element then sends a third message to the UE, which includes the first operation command and the second tag filter.

[0227] S502B: The second network element obtains the identifier of the first tag according to the first operation instruction and the first identifier, and matches the second tag filter based on the identifier of the first tag to obtain the information of the first tag.

[0228] For example, the second network element performs a tag operation according to the first operation instruction, such as the tag inventory process described above, to obtain the identifier of at least one tag, and retrieves the identifier of a first tag from the identifiers of the at least one tag based on the first identifier. The second network element then obtains the information of the first tag by matching it through the second tag filter based on the identifier of the first tag.

[0229] For example, the second network element may first determine the range of the first tag based on the second tag filter and then perform tag operation according to the first operation instruction to obtain information about the first tag (including the identifier of the first tag).

[0230] If the second network element is a first communication device with reader / writer functionality, then the first communication device performs step S502B. If the second network element is a mobility management function network element, then the mobility management function network element performs step S502B.

[0231] If the second network element is a mobility management function network element, before the mobility management function network element performs step S502B, it further includes: the second network element obtaining information of the first tag from the first communication device with reader function, or the second network element obtaining information of all tags from the first communication device with reader function, wherein the information of all tags includes the information of the first tag.

[0232] S503B: The second network element sends a second message to the first network element, the second message including information about the first tag and the first identifier.

[0233] The first identifier is used to determine the target server of the first label.

[0234] Correspondingly, the first network element receives the second message.

[0235] In one implementation, based on the situation where the second network element receives the first message from the first network element, the second network element sends the second message to the first network element.

[0236] In another implementation, based on the situation where the second network element receives the first message from the mobility management function network element, the second network element sends a second message to the first network element, including: the second network element sending the second message to the mobility management function network element; and the mobility management function network element then sending the second message to the first network element.

[0237] It should be noted that the second network element sends a fourth message to the mobility management function network element, which includes information about the first tag. The mobility management function network element then sends a second message to the first network element, which includes information about the first tag and the first identifier.

[0238] For example, the second network element is a UE, the first network element is a NEF network element, the UE network element sends a NAS message (equivalent to the fourth message) to the AMF network element, the NAS message contains the information of the first tag, and the AMF network element sends a data transmission message (equivalent to the second message) to the NEF network element, the data transmission message includes the information of the first tag and the first identifier.

[0239] S504B: The first network element determines the target server of the first label based on the first identifier.

[0240] In one implementation, the first network element determines the target server of the first tag based on the first identifier, including: the first network element determines the target server of the first tag based on the first identifier and a first correspondence relationship, wherein the first correspondence relationship includes the correspondence relationship between the first identifier and the target server.

[0241] It should be noted that this first correspondence can be obtained in the following way:

[0242] The first network element receives control information from at least one server, and each control information includes a first operation identifier and a second tag filter. Based on the control information from at least one target server, the first network element can generate a first identifier and establish a correspondence between the first identifier and the server, i.e., a first correspondence. This first correspondence can be stored locally on the first network element or in other communicable network elements or devices; this application does not specifically limit this.

[0243] It should be noted that the first identifier can be information used to identify the target server, such as the target server address, target server identifier, etc. For example, the first identifier can be the identifier of the first message, or the first identifier can be the identifier of the first operation instruction. There is a one-to-one correspondence between the identifier of the first message or the identifier of the first operation instruction and the target server. This application does not specifically limit the first identifier.

[0244] S505B: The first network element sends the information of the first tag to the target server.

[0245] This implementation method is mainly based on the above. Figure 3CThe third transmission path shown in this embodiment allows the second network element to be either a first communication device with reader / writer functionality (such as a UE) or a Mobility Management Function (AMF) network element. When the second network element is a first communication device, it first receives a first message from the first network element (i.e., a Network Capability Opening Function) via the Mobility Management Function. Then, based on the first operation command and second tag filter in the first message, the second network element determines the first tag and sends a second message containing the first tag information and a first identifier to the first network element via the Mobility Management Function. Finally, the first network element sends the first tag information to the target server. When the second network element is a Mobility Management Function, it can directly receive the first message from the first network element (i.e., the Network Capability Opening Function), determine the first tag based on the first operation command and second tag filter in the first message, and then send the first tag information and the first identifier, read and written by the first communication device, in the second message to the first network element. Finally, the first network element accurately sends the first tag information to the target server based on the first identifier.

[0246] The communication method proposed in this application will be further illustrated in detail below through several specific embodiments.

[0247] The following Examples 1, 2, and 3 belong to the above. Figure 5A A specific example of a communication method is shown, wherein Embodiment 1 belongs to Figure 5A A specific example of one implementation method of the method shown, Embodiment 2 belongs to Figure 5A A specific example of another implementation of the method shown (the first case in step S502A above), embodiment two is based on Figure 5A A specific example of another implementation of the method shown (the second case in step S502A above). Examples four and five below pertain to the above. Figure 5B A specific example of another communication method is shown.

[0248] Example 1

[0249] In this first embodiment, taking the terminal device UE as the reader / writer as an example, based on the above... Figure 3A The first transmission path shown involves the UE (user-writer) managing the tag, establishing a user plane session, and transmitting the tag information. (Refer to...) Figure 6 As shown, the specific process is as follows:

[0250] S600: The UE (reader / writer) completes the registration process.

[0251] The specific registration process performed by the UE (reader / writer) can be found in existing technical implementations and will not be described here.

[0252] S601: The UE (i.e., the reader / writer) sends a PDU session establishment request message to the AMF network element.

[0253] Accordingly, the AMF network element receives the PDU session establishment request message (equivalent to the first session request message of this application mentioned above).

[0254] In one possible example, the UE (reader / writer) can also send the PDU session establishment request message to the RAN (such as a base station), which will then forward it to the AMF network element. The AMF network element will then receive the PDU session establishment request message from the RAN (such as the base station).

[0255] One possible example is that the PDU session establishment request message may include first indication information, which indicates the access label home enterprise information of the UE. The access label home enterprise information of the UE may be, but is not limited to, DNN and / or NSSAI; or the first indication information may be DNN and / or NSSAI. The DNN and / or NSSAI indicates the network information of the target enterprise that the UE requests to establish.

[0256] If the UE (i.e., the reader / writer) is shared by multiple enterprises, then for each access tag-owning enterprise, the PDU session establishment process in steps S601-S608 is initiated sequentially. Steps S601-S608 are described in detail using the establishment of a corresponding PDU session (i.e., communication session) for one enterprise as an example.

[0257] S602: Select the appropriate SMF network element for the AMF network element.

[0258] In addition to the existing technology regarding how the AMF network element selects the appropriate SMF network element, the AMF network element can also assist in selecting the SMF network element based on the first indication information in the aforementioned PDU session establishment request message (equivalent to the first session request message of this application).

[0259] One possible implementation is that the AMF network element selects the SMF network element that satisfies the DNN and / or NSSAI in the first indication information mentioned above.

[0260] S603: The AMF network element sends a PDU session creation session context request message to the SMF network element.

[0261] Correspondingly, the SMF network element receives the PDU session creation session context request message.

[0262] One possible implementation is that the PDU session creation session context request message carries the Access Label Home Enterprise's DNN and / or NSSAI. The aforementioned DNN and / or NSSAI indicates the network information of the target enterprise that the UE is requesting to establish.

[0263] Optionally, the PDU session creation session context request message may also carry parameters such as SUPI (i.e., the UE identifier), the DNN requested by the UE, and the PDU Session ID.

[0264] S604: The SMF network element sends a PDU session creation session context response message to the AMF network element.

[0265] Correspondingly, the AMF network element receives the PDU session creation session context response message.

[0266] S605: The SMF network element determines the UE's target PIOT server information based on the DNN and / or NSSAI in the received PDU session establishment request message, and sends an N1N2 message to the AMF network element.

[0267] In one possible example, the SMF network element can also request information about the UE's target server from the PCF network element. This target PIOT server information may include the target server's IP address and / or port number.

[0268] Correspondingly, the AMF network element receives the N1N2 message, which carries information such as the tunnel endpoint identifier of the UPF network element (this information is given to the RAN device). The N1N2 message also carries the PIOT server address and port number information (encapsulated in an N1 SM message and sent to the UE). For example, the N1N2 message can be an AMF communication N1N2 message forwarding message.

[0269] S606: The AMF network element sends an N2 PDU session request message to the RAN.

[0270] Accordingly, the RAN receives the N2 PDU session request message, which carries a NAS message containing the PIOT server address and port number information. For example, the NAS message can be a PDU session establishment response message. This NAS message also originates from the aforementioned N1 SM message.

[0271] S607: The RAN establishes air interface resources with the UE (reader / writer) and sends NAS messages to the UE.

[0272] Accordingly, the UE receives the NAS message (equivalent to the first response message of the present application mentioned above), which carries the PIOT server address (equivalent to the first target address information of the present application mentioned above) and port number information (equivalent to the first port number information of the present application mentioned above).

[0273] S608: The RAN sends an N2 PDU session response message to the AMF network element.

[0274] Correspondingly, the AMF network element receives the N2 PDU session response message.

[0275] Through the above steps S601-S608, the UE (reader) establishes a PDU session for an enterprise. For other different enterprises, the UE (reader) can refer to the above steps S601-S608 to establish the corresponding PDU session, which will not be described in detail here.

[0276] For example, the UE (reader) establishes a corresponding PDU1 session for tag 1 belonging to enterprise 1 through the above steps S601-S608; the UE (reader) establishes a corresponding PDU2 session for tag 2 belonging to enterprise 2 through the above steps S601-S608; and the UE (reader) establishes a corresponding PDU3 session for tag 3 belonging to enterprise 3 through the above steps S601-S608.

[0277] Furthermore, through the above steps, after the UE (reader / writer) establishes different PDU sessions for different enterprises, the UE obtains different PIOT server address information and port number information respectively. That is, establishing a PDU session obtains a corresponding PIOT server address information and port number information.

[0278] S609: The UE (reader / writer) establishes a connection with the corresponding PIOT server based on the PIOT server address information and port number information.

[0279] For example, the UE (user reader) obtains the address and corresponding port number of a PIOT1 server by establishing a PDU1 session, and then establishes a connection with the PIOT1 server based on the PIOT1 server address and port number. Similarly, the UE obtains the address and corresponding port number of a PIOT2 server by establishing a PDU2 session, and then establishes a connection with the PIOT2 server based on the PIOT2 server address and port number.

[0280] The following describes the process by which the application layer sends tag storage or read / write commands to the UE (reader / writer). The specific procedure is as follows:

[0281] S610: The PIOT server sends a first request message to the UE (reader / writer) through the established PDU session.

[0282] Accordingly, the UE (reader / writer) receives a first request message (equivalent to the first request in this application). This first request message contains commands for tag storage or reading / writing. Furthermore, the first request message may also contain the range of target tags and filtering rules.

[0283] S611: The UE (reader) establishes a connection with the target tag according to the first request message mentioned above, and executes the tag storage or read / write command mentioned above.

[0284] Specifically, the UE (reader / writer) can first perform tag inventory based on the tag inventory command, and the tag inventory process can be referred to the above. Figure 2 The steps involved are not detailed here.

[0285] Furthermore, in step S611, the UE (reader) can read the information of the accessed tag. How the UE (reader) specifically reads the accessed tag information can be found in existing technical implementations, and will not be described in detail here.

[0286] The information on the label includes, but is not limited to, the label's identifier, such as Electronic Product Code (EPC) and Tag Identification Number (TID).

[0287] For example, the accessed tags include tag 1, tag 2, and tag 3. The UE (reader) reads the information of tag 1, tag 2, and tag 3.

[0288] S612: The UE (reader / writer) selects the appropriate PDU session based on the enhanced URSP policy.

[0289] It should be understood that the UE (reader / writer) selecting an appropriate PDU session based on the enhanced URSP policy can be regarded as the first communication session mentioned above.

[0290] The UE (reader) determines the appropriate PDU session (equivalent to the communication session of the above application) for the accessed tag based on the information of the accessed tag and in conjunction with the enhanced user equipment routing policy (URSP policy) shown in Table 1 (equivalent to the first routing policy of the above application).

[0291] As shown in Table 1, the enhanced URSP policy adds an extra description of Passive IoT to the traffic description content. This description consists of the enterprise ID and the tag ID, used to match and identify different tags. The description of Passive IoT is bound to the corresponding PIOT server address and port number, and transmitted through the corresponding PDU session (i.e., the first communication session of this application). That is, one Passive IoT has a corresponding relationship with the PIOT server address and port number, as well as the PDU session. Therefore, the UE (reader / writer) can determine the description of Passive IoT in Table 1 based on the tag information (tag ID and the ID of the enterprise to which the tag belongs), and then determine the PIOT server address and port number corresponding to the description of Passive IoT, as well as the corresponding PDU session.

[0292] Table 1

[0293]

[0294] It should be understood that Table 1 above is only an example, and the enhanced URSP strategy may also include, but is not limited to, the descriptions in Table 1.

[0295] For example, the UE (reader) can determine the corresponding server address and port number (or obtain the server address and port number through the aforementioned session establishment process) and the PDU1 session based on the ID of tag 1 and the ID of the enterprise to which tag 1 belongs. Similarly, the UE (reader) can determine the corresponding server address and port number (or obtain the server address and port number through the aforementioned session establishment process) and the PDU2 session based on the ID of tag 2 and the ID of the enterprise to which tag 2 belongs. Likewise, the UE (reader) can determine the corresponding server address and port number (or obtain the server address and port number through the aforementioned session establishment process) and the PDU3 session based on the ID of tag 3 and the ID of the enterprise to which tag 3 belongs.

[0296] S613: The UE (user reader) sends the tag information to the corresponding PIOT server through the PDU session.

[0297] Specifically, the information of the label can be the label data, or the information of the label can only contain the identifier of the label.

[0298] The UE (Reader / Writer) sends the tag information to the corresponding PIOT server using the corresponding PDU session and through the corresponding port number, based on the PIOT server address information and port number.

[0299] For example, the UE (reader) sends the data of tag 1 to the corresponding PIOT1 server through the corresponding port number 1 using the corresponding PDU1 session.

[0300] The UE (reader) sends the data of tag 2 to the corresponding PIOT2 server through the corresponding port number 2 using the corresponding PDU2 session.

[0301] The UE (reader) uses the corresponding PDU3 session and port number 3 to send the data of tag 3 to the corresponding PIOT3 server using the PIOT3 server address information and port number 3.

[0302] In this first embodiment, when establishing a PDU session, the UE (reader / writer) sends a DNN and / or NSSAI carrying the home enterprise of the access tag (Passive IoT) to assist the core network in identifying and allocating different server address and port number information, thereby enabling the UE (reader / writer) to establish a user plane connection with the Passive IoT server. Furthermore, in this first embodiment, based on the enhanced URSP policy, the UE (reader / writer) can select the appropriate PDU session for different tag information, thereby routing and transmitting the information of different tags.

[0303] Example 2

[0304] In this second embodiment, taking the terminal device UE as the reader / writer as an example, based on the above... Figure 3B The second transmission path shown involves the UPF network element managing the tags, establishing user plane sessions, and transmitting tag information via the UPF network element. (See reference...) Figure 7 As shown, the specific process is as follows:

[0305] S700: The process of UE (user-writer) completing registration.

[0306] The specific registration process performed by the UE (reader / writer) can be found in existing technical implementations and will not be described here.

[0307] S701: The UE (reader / writer) sends a PDU session establishment request message to the AMF network element.

[0308] Accordingly, the AMF network element receives the PDU session establishment request information (equivalent to the first session request message of this application mentioned above), and the PDU session establishment request message carries the data network name DNN and / or NSSAI of the access tag home enterprise.

[0309] Specifically, step S701 can be referred to step S601 above, and will not be described in detail here.

[0310] If the UE (user device) is shared by multiple enterprises, then for each enterprise whose access tag belongs, the PDU session establishment process in steps S701-S708 will be initiated sequentially. Steps S701-S708 will be described in detail using the establishment of a corresponding PDU session (i.e., communication session) for a single enterprise as an example.

[0311] S702: Select the appropriate SMF network element for the AMF network element.

[0312] Specifically, step S702 can be referred to step S602 above, and will not be described in detail here.

[0313] S703: The AMF network element sends a PDU session creation session context request message to the SMF network element.

[0314] Correspondingly, the SMF network element receives the PDU session creation session context request message.

[0315] One possible implementation is that the PDU session creation session context request message carries the Access Label Home Enterprise's DNN and / or NSSAI. The aforementioned DNN and / or NSSAI indicates the network information of the target enterprise that the UE is requesting to establish.

[0316] Optionally, the PDU session creation session context request message may also carry parameters such as the UE identifier (e.g., SUPI), the data network name (DNN) requested by the UE, and the PDU session ID.

[0317] Specifically, step S702 can be referred to step S602 above, and will not be described in detail here.

[0318] S704: The SMF network element sends a PDU session creation session context response message to the AMF network element.

[0319] Correspondingly, the AMF network element receives the PDU session creation session context response message.

[0320] S705: The SMF network element initiates an N4 session establishment / modification request to the UPF network element.

[0321] Accordingly, the UPF network element receives the N4 session establishment / modification request (equivalent to the N4 session request message of this application). The N4 session establishment / modification request carries the UE's IP address (equivalent to the third target address information of this application) and corresponding port number information (equivalent to the third target address information of this application), the PIOT server's IP address (including the fully qualified domain name) (equivalent to the second target address information of this application) and corresponding port number information (equivalent to the second port number information of this application), and the first tag filter.

[0322] For example, an SMF network element can determine the target PIOT server information of a UPF network element based on the received DNN and / or IP address. This target PIOT server information may include the target server's IP address and / or port number. An SMF network element may also request the aforementioned target PIOT server information from a PCF network element.

[0323] The first tag filter described above is used to identify tags. The UPF network element can select the appropriate PIOT server by recognizing the tag's identifier or the enterprise identifier carried by the tag, in order to send the tag's information. In this embodiment, the UPF network element can identify tags based on the first tag filter and determine the target PIOT server for that tag.

[0324] S706: The UPF network element sends an N4 session establishment / modification response message to the SMF network element.

[0325] The UPF network element sends an N4 session establishment / modification response message to the SMF network element, which is used to provide the SMF network element with its own IP address and port number.

[0326] S707: The SMF network element sends an N1N2 message to the AMF network element.

[0327] Correspondingly, the AMF network element receives the N1N2 message, which carries the IP address and port number information of the aforementioned UPF network element. For example, the aforementioned N1N2 message can be a message forwarded by the AMF network element via the N1N2 message.

[0328] It should be noted that the IP address and port number information of this UPF network element are encapsulated in the N1 SM message, and this information will be sent to the UE (reader / writer).

[0329] S708: The AMF network element sends an N2 PDU session request message to the RAN.

[0330] Correspondingly, the RAN receives the N2 PDU session request message, which carries a NAS message. This NAS message is the aforementioned N1 SM message, and it carries the IP address and port number information of the UPF network element.

[0331] For example, the NAS message could be a PDU session establishment response message.

[0332] S709: The RAN allocates air interface resources, establishes a radio connection with the UE (reader / writer), and sends the received NAS message to the UE (reader / writer).

[0333] Accordingly, the UE (reader / writer) receives the NAS message (equivalent to the second response message of the present application mentioned above), which carries the IP address of the UPF network element (equivalent to the second target address information of the present application mentioned above) and port number information (equivalent to the second port number information of the present application mentioned above).

[0334] S710: The RAN sends an N2 PDU session response message to the AMF network element.

[0335] Specifically, the RAN successfully establishes a connection with the UE (reader / writer), and after the UE (reader / writer) successfully receives the NAS message, it sends an N2 PDU session response message to the AMF network element.

[0336] S711: The UE (user-writer) establishes a connection with the UPF network element based on the IP address and port number of the UPF network element.

[0337] Through step S711, the first communication session between the UE (reader / writer) and the UPF network element can be established.

[0338] S712: The UPF network element establishes a connection with the corresponding PIOT server based on the address and port information of the PIOT server.

[0339] For example, in steps S701-S705 above, the UPF network element can receive the IP address and corresponding port number information of the PIOT server. Then, the UPF network element can establish a connection with the PIOT server based on the PIOT server's IP address and corresponding port number information. Specifically, the process of the UPF network element establishing a connection with the PIOT server can be referred to in step S609 above, where the UE (reader / writer) establishes a connection with the PIOT server; it will not be described in detail here.

[0340] Therefore, the UPF network element can sequentially execute steps S701-S705 above for each different tag-owning enterprise accessed by the UE (i.e., the reader / writer) to obtain the corresponding PIOT server's IP address and port number information, and then establish a connection with the corresponding PIOT server. Ultimately, the UPF network element creates connections to different PIOT servers for different tag-owning enterprises for subsequent use.

[0341] The following describes the process by which the application layer sends tag storage or read / write commands to the UE (reader / writer). The specific procedure is as follows:

[0342] S713: The PIOT server sends a first request message to the UE (i.e., the reader / writer) through the established PDU session.

[0343] Accordingly, the UE (i.e., the reader / writer) receives the first request message (equivalent to the first request in this application). The first request message contains a command for tag storage or reading / writing. In addition, the first request message may also contain the range of target tags and filtering rules.

[0344] This step S713 can be referenced in conjunction with the above step S610.

[0345] S714: The UE (reader) establishes a connection with the target tag according to the first request message mentioned above, and executes the tag storage or read / write command mentioned above.

[0346] Specifically, the UE (user-writer) can first perform tag inventory based on the tag inventory command, and the tag inventory process can be referred to the above. Figure 2 The steps involved are not detailed here.

[0347] Furthermore, in step S714, the UE (reader) reads the information of the accessed tag. How the UE (reader) specifically reads the accessed tag information can be found in existing technical implementations, and will not be described in detail here.

[0348] The information on the label includes, but is not limited to, the label's identifier, such as Electronic Product Code (EPC) and Tag Identification Number (TID).

[0349] For example, the accessed tags include tag 1, tag 2, and tag 3. The UE (reader) reads the information of tag 1, tag 2, and tag 3.

[0350] This step S714 can be referenced in conjunction with the above step S611.

[0351] S715: The UE (reader / writer) selects the appropriate PDU session based on the enhanced URSP policy.

[0352] It should be understood that the UE (reader / writer) selecting an appropriate PDU session based on the enhanced URSP policy can be regarded as the first communication session mentioned above.

[0353] The UE (reader / writer) determines the appropriate PDU session for each access tag based on the information obtained from the access tag and the enhanced URSP policy (routing policy) shown in Table 1 above. It is worth noting that, unlike Embodiment 1, the IP descriptor in the enhanced URSP policy of this embodiment is the IP address and port number of the UPF received by the UE, along with the corresponding protocol ID.

[0354] For example, the UE (reader / writer) can determine the PDU1 session based on the information obtained from the access tag 1 and the enhanced URSP policy shown in Table 1 above. The UE (reader / writer) can determine the PDU2 session based on the information obtained from the access tag 2 and the enhanced URSP policy shown in Table 1 above. The UE (reader / writer) can determine the PDU3 session based on the information obtained from the access tag 3 and the enhanced URSP policy shown in Table 1 above.

[0355] Step S715 is the same as step S612 above and can be referred to each other. It will not be described in detail here.

[0356] S716: The UE (user reader) sends the tag information to the UPF network element through the PDU session.

[0357] Correspondingly, the UPF network element receives information from the tag.

[0358] For example, the UE (user reader) transmits the information of tag 1 to the UPF network element through the PDU1 session. The UE (user reader) transmits the information of tag 2 to the UPF network element through the PDU2 session. The UE (user reader) transmits the information of tag 3 to the UPF network element through the PDU3 session.

[0359] S717: The UPF network element selects the corresponding PIOT server connection based on the first tag filter.

[0360] The first tag filter contains filtering rules for tag identifiers or enterprise identifiers carried by the tags, as well as information about the target PIOT server corresponding to each filtering rule, namely the IP address and port number of the target PIOT. For example, if a UPF network element receives information from three tags, it can identify the three tags using the first tag filter to determine that they are data from tag 1, tag 2, and tag 3, respectively. Furthermore, the UPF network element can determine the connection to the corresponding PIOT server for different tag information; that is, the UPF network element determines the connection to the PIOT1 server for tag 1 data, the connection to the PIOT2 server for tag 2 data, and the connection to the PIOT3 server for tag 3 data.

[0361] S718: The UPF network element transmits the tag information to the corresponding PIOT server.

[0362] Specifically, the information of the label can be the label data, or the information of the label can only contain the identifier of the label.

[0363] For example, a UPF network element transmits the data of tag 1 to server PIOT1 via a connection to server PIOT1. The same UPF network element transmits the data of tag 2 to server PIOT2 via a connection to server PIOT2. Finally, the same UPF network element transmits the data of tag 3 to server PIOT3 via a connection to server PIOT3.

[0364] In this second embodiment, when the UE cannot obtain the address information and corresponding port number information of the PIOT server, the UE can establish a connection with the UPF network element and send the tag information to the UPF network element. The UPF network element then identifies the received tag information and determines the connection (i.e., routing data) of the corresponding PIOT server for the tag information. Finally, the UPF network element accurately transmits the tag information to the corresponding PIOT server through the connection of the corresponding PIOT server.

[0365] Example 3

[0366] In this third embodiment, taking the terminal device UE as the reader / writer as an example, based on the above... Figure 3B The second transmission path shown involves tag management performed by the UPF network element, which establishes user plane sessions and transmits tag information. However, this third embodiment may include multiple UPF network elements. During the creation of a communication session (Passive IoT session) by the UE (user-writer), each communication session may correspond to a different UPF network element, and each communication session ultimately corresponds to a different enterprise's target PIOT server. The correspondence between different communication sessions and different target PIOT servers is stored on the UPF network element, and the UPF network element performs tag routing management. (Reference) Figure 8 As shown, the specific process is as follows:

[0367] S800: The process of UE (user-writer) completing registration.

[0368] The specific registration process performed by the UE (reader / writer) can be found in existing technical implementations and will not be described here.

[0369] S801: The UE (i.e., the reader / writer) sends a PDU session establishment request to the AMF network element.

[0370] Accordingly, the AMF network element receives the PDU session establishment request message.

[0371] In one possible example, the UE (reader / writer) can also send the PDU session establishment request message to the RAN device (such as a base station), which then forwards it to the AMF network element. The AMF network element receives the PDU session establishment request message from the RAN device (such as the base station).

[0372] One possible example is that the PDU session establishment request message may include first indication information, which indicates the access label home enterprise information of the UE. The access label home enterprise information of the UE may be, but is not limited to, DNN and / or NSSAI; or the first indication information may be DNN and / or NSSAI. The DNN and / or NSSAI indicates the network information of the target enterprise that the UE requests to establish.

[0373] This step S801 can refer to steps S601 and S701 above.

[0374] If the UE (i.e., the reader / writer) is shared by multiple enterprises, then for each enterprise whose access tag belongs, the PDU session establishment process in steps S801-S808 will be initiated sequentially. Steps S801-S808 can be described in detail as an example of establishing a corresponding PDU session (i.e., communication session) for a single enterprise.

[0375] S802: Select the appropriate SMF network element for the AMF network element.

[0376] In addition to the existing technology regarding how the AMF network element selects the appropriate SMF network element, the AMF network element can also assist in selecting the SMF network element based on the first indication information in the aforementioned PDU session establishment request message (equivalent to the first session request message of this application).

[0377] One possible implementation is that the AMF network element selects the SMF network element that satisfies the DNN and / or NSSAI in the first indication information mentioned above.

[0378] This step S802 can refer to steps S602 and S702 above.

[0379] S803: The AMF network element sends a PDU session creation session context request message to the SMF network element.

[0380] Correspondingly, the SMF network element receives the PDU session creation session context request message.

[0381] One possible implementation is that the PDU session creation session context request message carries the Access Label Home Enterprise's DNN and / or NSSAI. The aforementioned DNN and / or NSSAI indicates the network information of the target enterprise that the UE is requesting to establish.

[0382] Optionally, the PDU session creation session context request message may also carry parameters such as the UE identifier (e.g., SUPI), the data network name (DNN) requested by the UE, and the PDU session ID.

[0383] Step S804 can be referenced from steps S604 and S704 above.

[0384] S804: The SMF network element sends a PDU session creation session context response message to the AMF network element.

[0385] Correspondingly, the AMF network element receives the PDU session creation session context response message.

[0386] S805: The SMF network element sends an N4 session establishment / modification request to the corresponding UPF network element based on the received DNN.

[0387] Correspondingly, the corresponding UPF network element receives the N4 session establishment / modification request (equivalent to the N4 session request message in this application). The N4 session establishment / modification request carries the UE's IP address and / or port number information, the PIOT server's IP address (including the fully qualified domain name), and the corresponding port number information.

[0388] For example, the SMF network element determines the IP address (including fully qualified domain name) and corresponding port number information of the appropriate PIOT server based on the DNN of the enterprise to which the tag 1 belongs. If the SMF network element determines that the IP address (including fully qualified domain name) and corresponding port number information of the PIOT1 server are the same, the SMF network element sends an N4 session establishment / modification request to the corresponding UPF(1) network element. The N4 session establishment / modification request carries the IP address (including fully qualified domain name) and corresponding port number information of the PIOT1 server.

[0389] It is important to note that in step S805 above, the SMF network element only reports the IP address and port number of the corresponding PIOT server to the corresponding UPF network element for the DNN and / or NSSAI of one tag home enterprise. Therefore, the SMF network element can refer to this method to report the IP address and port number of the corresponding PIOT server to the corresponding UPF network element for the DNN and / or NSSAI of other tag home enterprises accessed by the UE.

[0390] For different tags, the corresponding UPF network elements can be the same or different. If the UPF network elements corresponding to the different communication sessions are the same (i.e., the IP addresses of the UPF network elements are all the same), then their corresponding port numbers will be different. If the UPF network elements corresponding to the different communication sessions are different (i.e., the IP addresses of the UPF network elements are different), then their corresponding port numbers may be the same. In general, different communication sessions can be identified by the IP address and port number of the UPF network element.

[0391] For example, the SMF network element can, for the DNN and / or NSSAI of the enterprise to which the UE accesses tags 1, 2, and 3 belong, respectively, feed back the IP address and port number of the corresponding PIOT1 server to the corresponding UPF(1), UPF(2), and UPF(3) network elements. That is, the SMF network element determines different UFP network elements (i.e., the IP addresses of the UFP network elements are all different) for different tags accessed by the UE, and the port numbers corresponding to the different UFP network elements are also different, and the communication sessions corresponding to the different UFP network elements are also different.

[0392] Alternatively, the SMF network element can determine the IP address and port number of the corresponding PIOT1 server to be fed back to the same UPF(1) network element for the DNN and / or NSSAI of the enterprise to which the UE accesses tags 1, 2, and 3 belong. However, the SMF network element can determine different port numbers of the corresponding UPF(1) network element for the tags 1, 2, and 3 accessed by the UE. That is, tag 1 corresponds to port number 1 of the UPF(1) network element, tag 2 corresponds to port number 2 of the UPF(1) network element, and tag 3 corresponds to port number 3 of the UPF(1) network element. Moreover, port number 1, port number 2, and port number 3 all correspond to different communication sessions.

[0393] S806: The UPF network element sends an N4 session establishment / modification response message to the SMF network element.

[0394] For example, after receiving the N4 session establishment / modification request, the UPF(1) network element sends an N4 session establishment / modification response message to the SMF network element, which is used to report its own IP address and port number to the SMF network element, that is, the IPF address and corresponding port number of the UPF(1) network element.

[0395] S807: The SMF network element sends an N1N2 message to the AMF network element.

[0396] Correspondingly, the AMF network element receives the N1N2 message, which carries the IP address and port number information of the aforementioned UPF network element. For example, the aforementioned N1N2 message can be an AMF network element communication N1N2 message forwarding message.

[0397] For example, the SMF network element sends an N1N2 message to the AMF network element based on the received DNN and / or NSSAI of the enterprise to which tag 1 belongs. This N1N2 message carries the IP address and port number 1 information of the UPF(1) network element. The SMF network element sends an N1N2 message to the AMF network element based on the received DNN and / or NSSAI of the enterprise to which tag 2 belongs. This N1N2 message carries the IP address and port number 2 information of the UPF(2) network element. The SMF network element sends an N1N2 message to the AMF network element based on the received DNN and / or NSSAI of the enterprise to which tag 3 belongs. This N1N2 message carries the IP address and port number 3 information of the UPF(3) network element. Alternatively, the SMF network element sends an N1N2 message to the AMF network element based on the received DNN and / or NSSAI of the enterprise to which tag 1 belongs. This N1N2 message carries the IP address and port number 1 information of the UPF(1) network element. The SMF network element sends an N1N2 message to the AMF network element based on the received DNN and / or NSSAI of the enterprise to which tag 2 belongs. The N1N2 message carries the IP address and port number 2 information of the UPF(1) network element. The SMF network element sends an N1N2 message to the AMF network element based on the received DNN and / or NSSAI of the enterprise to which tag 3 belongs. The N1N2 message carries the IP address and port number 3 information of the UPF(1) network element.

[0398] S808: The AMF network element sends an N2 PDU session request message to the RAN.

[0399] Accordingly, the RAN receives the N2 PDU session request message, which carries a NAS message. The NAS message is the aforementioned N1 SM message, and it carries the IP address and port number information of the UPF network element received by the aforementioned AMF network element.

[0400] For example, the NAS message could be a PDU session establishment response message.

[0401] S809: The RAN allocates air interface resources, establishes a radio connection with the UE (reader / writer), and sends the received NAS message to the UE (reader / writer).

[0402] Accordingly, the UE (reader / writer) receives the NAS message (which may be equivalent to the second response message of the present application mentioned above), which carries the IP address of the UPF network element (equivalent to the second target address information of the present application mentioned above) and port number information (equivalent to the second port number information of the present application mentioned above).

[0403] S810: The RAN sends an N2 PDU session response message to the AMF network element.

[0404] Specifically, the RAN successfully establishes a connection with the UE (reader / writer), and after the UE (reader / writer) successfully receives the NAS message, it sends an N2 PDU session response message to the AMF network element.

[0405] S811: The UE (user reader) establishes a connection with the corresponding UPF network element based on the IP address and port number of the UPF network element.

[0406] By following step S811, connections between multiple UEs (users / writers) and UPF network elements can be established.

[0407] For example, the UE (i.e., the reader / writer) establishes a connection with the corresponding UPF(1) network element based on the IP address and port number 1 of the UPF(1) network element. The UE (i.e., the reader / writer) establishes a connection with the corresponding UPF(2) network element based on the IP address and port number 2 of the UPF(2) network element. The UE (i.e., the reader / writer) establishes a connection with the corresponding UPF(3) network element based on the IP address and port number 3 of the UPF(3) network element. Or, the UE (i.e., the reader / writer) establishes a connection with the corresponding UPF(1) network element based on the IP address and port number 1 of the UPF(1) network element. The UE (i.e., the reader / writer) establishes a connection with the corresponding UPF(1) network element based on the IP address and port number 2 of the UPF(1) network element. The UE (i.e., the reader / writer) establishes a connection with the corresponding UPF(1) network element based on the IP address and port number 3 of the UPF(1) network element.

[0408] S812: The UPF network element establishes a connection with the corresponding PIOT server based on the address and port information of the PIOT server.

[0409] Through the above step S805, different UPF network elements can obtain the address information and port number information of the corresponding PIOT server for the corresponding access tag-owning enterprise, and establish a connection with the corresponding PIOT server based on the obtained address information and port number information of the corresponding PIOT server.

[0410] For example, the UPF(1) network element establishes a connection with the PIOT1 server based on the IP address and port number 1 of the UPF(1) network element, as well as the IP address and corresponding port number 1 of the PIOT1 server. The UPF(2) network element establishes a connection with the PIOT2 server based on the IP address and port number 2 of the UPF(2) network element, as well as the IP address and corresponding port number 2 of the PIOT2 server. The UPF(3) network element establishes a connection with the PIOT3 server based on the IP address and port number 3 of the UPF(3) network element, as well as the IP address and corresponding port number 3 of the PIOT3 server.

[0411] Alternatively, the UPF(1) network element establishes a connection with the PIOT1 server based on the IP address and port number 1 of the UPF(1) network element, as well as the IP address and corresponding port number 1 of the PIOT1 server. The UPF(1) network element establishes a connection with the PIOT2 server based on the IP address and port number 2 of the UPF(1) network element, as well as the IP address and corresponding port number 2 of the PIOT2 server. The UPF(1) network element also establishes a connection with the PIOT3 server based on the IP address and port number 3 of the UPF(1) network element, as well as the IP address and corresponding port number 3 of the PIOT3 server.

[0412] Therefore, referring to step S812, multiple UPF network elements can be connected to multiple PIOT servers, or a single UPF network element can be connected to multiple PIOT servers.

[0413] Simultaneously, an association (or correspondence) can be established between the connection of the UE (reader) to multiple UPF network elements and the connection of the multiple UPF network elements to multiple PIOT servers. That is, when multiple UPF network elements are included, the connection between the UE (reader) and one of the multiple UPF network elements corresponds to a connection between the UPF network element and one of the multiple PIOT servers. For example, the connection between a UE and a UPF(x) network element corresponds to a connection between the UPF(x) network element and the PIOT(x) server, where x is a variable positive integer.

[0414] Alternatively, an association (or correspondence) can be established between the connection of the UE (reader / writer) to a UPF network element and the connection of the UPF network element to multiple PIOT servers. That is, when there is only one UPF network element, the connection between the UE (reader / writer) and the UPF network element corresponds to a connection between the UPF network element and one of the multiple PIOT servers. For example, the connection between the UE and UPF(1) corresponds to a connection between the UPF(1) and the PIOT(x) server, where x is a variable positive integer.

[0415] The following describes the process by which the application layer sends tag storage or read / write commands to the UE (reader / writer). The specific procedure is as follows:

[0416] S813: The PIOT server sends the first request message to the UE (i.e., the reader / writer) through the established PDU session.

[0417] Accordingly, the UE (i.e., the reader / writer) receives the first request message (equivalent to the first request in this application). The first request message contains a command for tag storage or reading / writing. In addition, the first request message may also contain the range of target tags and filtering rules.

[0418] This step S813 can be referenced in conjunction with the above steps S610 and S713.

[0419] S814: The UE (reader) establishes a connection with the target tag according to the first request message mentioned above, and executes the tag storage or read / write command mentioned above.

[0420] Specifically, the UE (user-writer) can first perform tag inventory based on the tag inventory command, and the tag inventory process can be referred to the above. Figure 2 The steps involved are not detailed here.

[0421] Furthermore, in step S814, the UE (reader) reads the information of the access tag.

[0422] The information on the label includes, but is not limited to, the label's identifier, such as Electronic Product Code (EPC) and Tag Identification Number (TID).

[0423] For example, the accessed tags include tag 1, tag 2, and tag 3. The UE (reader) reads the information of tag 1, tag 2, and tag 3.

[0424] This step S814 can be referenced in conjunction with the above steps S611 and S714.

[0425] S815: The UE (reader / writer) selects the appropriate PDU session based on the enhanced URSP policy.

[0426] The UE (reader / writer) determines the appropriate PDU session for each access tag based on the information obtained from the access tag and the enhanced URSP policy (routing policy) shown in Table 1 above. Unlike Embodiment 1, the IP descriptor for the URSP policy described above consists of the UPF's IP address, port number, and protocol ID.

[0427] For example, the UE (reader / writer) determines the PDU1 session based on the information of the access tag 1 and the enhanced URSP policy shown in Table 1 above. The UE (reader / writer) determines the PDU2 session based on the information of the access tag 2 and the enhanced URSP policy shown in Table 1 above. The UE (reader / writer) determines the PDU3 session based on the information of the access tag 3 and the enhanced URSP policy shown in Table 1 above.

[0428] It should be noted that step S815 is the same as step S715 above and can be referred to each other. It will not be described in detail here.

[0429] S816: The UE (user reader) sends the tag information to the corresponding UPF network element through the PDU session.

[0430] Correspondingly, the UPF network element receives information from the tag.

[0431] For example, the UE (reader) sends the information of tag 1 to the UPF (1) network element through the PDU1 session; the UE (reader) sends the information of tag 2 to the UPF (2) network element through the PDU2 session; and the UE (reader) sends the information of tag 3 to the UPF (3) network element through the PDU3 session.

[0432] Alternatively, the UE (reader) can send the information of tag 1 to the UPF(1) network element through the PDU1 session; the UE (reader) can send the information of tag 2 to the UPF(1) network element through the PDU2 session; and the UE (reader) can send the information of tag 3 to the UPF(1) network element through the PDU3 session.

[0433] S817: The UPF network element determines the target enterprise server of the tag based on the tag information obtained from different IP addresses and / or port numbers, and selects the connection from the UPF network element to the PIOT server.

[0434] Specifically, the UPF network element can determine its connection to the PIOT server based on the association established in step S812 above.

[0435] For example, in step S816 above, the UE (reader) sends the information of tag 1 to the UPF (1) network element. Then, in step S817, the UPF (1) network element selects the connection from the UPF (1) network element to the PIOT1 server based on the association relationship. In step S816 above, the UE (reader) sends the information of tag 2 to the UPF (2) network element. Then, in step S817, the UPF (2) network element selects the connection from the UPF (2) network element to the PIOT2 server based on the association relationship. In step S816 above, the UE (reader) sends the information of tag 3 to the UPF (3) network element. Then, in step S817, the UPF (3) network element selects the connection from the UPF (3) network element to the PIOT3 server based on the association relationship.

[0436] Alternatively, in step S816 above, if the UE (reader) sends the information of tag 1 to the UPF (1) network element, then in step S817, the UPF (1) network element selects the connection from the UPF (1) network element to the PIOT1 server based on the association relationship. In step S816 above, if the UE (reader) also sends the information of tag 2 to the UPF (1) network element, then in step S817, the UPF (1) network element selects the connection from the UPF (1) network element to the PIOT2 server based on the association relationship. In step S816 above, if the UE (reader) sends the information of tag 3 to the UPF (1) network element, then in step S817, the UPF (1) network element selects the connection from the UPF (1) network element to the PIOT3 server based on the association relationship.

[0437] S818: The UPF network element sends the tag information to the corresponding PIOT server.

[0438] The information of the label can be the label data, or the information of the label can only contain the label's identifier.

[0439] For example, in the case of multiple UPF network elements: UPF(1) network element selects a connection from UPF network element(1) to PIOT1 server through step S817 above, and then in step S818, the information of tag 1 is transmitted to PIOT1 server through the connection from UPF network element(1) to PIOT1 server. UPF(2) network element selects a connection from UPF network element(2) to PIOT2 server through step S817 above, and then in step S818, the information of tag 2 is transmitted to PIOT2 server through the connection from UPF network element(2) to PIOT2 server. UPF(3) network element selects a connection from UPF network element(3) to PIOT3 server through step S817 above, and then in step S818, the information of tag 3 is transmitted to PIOT3 server through the connection from UPF network element(3) to PIOT3 server.

[0440] In the case of having only one UPF network element, namely UPF(1) network element: UPF(1) network element selects the connection from UPF network element (1) to PIOT1 server through the above step S817, and then in step S818, the information of tag 1 is transmitted to PIOT1 server through the connection from UPF network element (1) to PIOT1 server. UPF(1) network element selects the connection from UPF network element (1) to PIOT2 server through the above step S817, and then in step S818, the information of tag 2 is transmitted to PIOT2 server through the connection from UPF network element (1) to PIOT2 server. UPF(1) network element selects the connection from UPF network element (1) to PIOT3 server through the above step S817, and then in step S818, the information of tag 3 is transmitted to PIOT3 server through the connection from UPF network element (1) to PIOT3 server.

[0441] In this third embodiment, when the UE cannot obtain the address information and corresponding port number information of the PIOT server, the UE can request the DNN / NSSAI of different tag-owning enterprises and establish different communication sessions through UPF. Then, the UE selects the first communication session based on the enhanced URSP policy and sends the target tag information to the corresponding UPF network element. The corresponding UPF network element then determines the corresponding PIOT server for the tag based on the IP address and port number and accurately transmits the tag information to the PIOT server.

[0442] Example 4

[0443] In this fourth embodiment, taking the terminal device UE as the reader / writer as an example, based on the above... Figure 3C The third transmission path shown primarily involves the UE (user-defined device) managing the tag and transmitting it through the control plane channel; that is, the PIOT server sends commands to the AMF network element via the NEF network element. (Reference) Figure 9 As shown, the specific process is as follows:

[0444] S900: UE (reader / writer) completes the registration process.

[0445] The specific registration process performed by the UE (reader / writer) can be found in existing technical implementations and will not be described here.

[0446] S901: The PIOT server sends a disk storage request message to the NEF network element.

[0447] Accordingly, the NEF network element (equivalent to the first network element of this application) receives the inventory request message, which carries tag operation commands, second tag filters (such as inventory area, inventory type, inventory rules, etc.) and information such as reporting trigger events (such as inventory cycle, new tag access event, tag departure).

[0448] S902: The NEF network element records the address of the PIOT server that sent the disk storage request message.

[0449] Specifically, for each received disk storage request message, the NEF network element records the address of the PIOT server (i.e., the enterprise's application server) from which the disk storage request message originates.

[0450] S903: The NEF network element generates an operation identifier and sends the first signaling to the AMF network element.

[0451] For example, the first signaling can be the first message.

[0452] Specifically, this operation identifier (relative to the first identifier mentioned above in this application) can be used by the NEF network element to uniquely identify the first signaling. The NEF network element can determine the inventory request message that triggered the first signaling by determining the first signaling, thereby determining the address information of the recorded PIOT server.

[0453] Accordingly, the AMF network element receives the first signaling, which carries an operation identifier and information included in the inventory request message, namely, the tag operation command, the second tag filter (inventory area), and the reporting trigger event. Since the first signaling is triggered by the inventory request message, the operation identifier can also be used to identify the first message.

[0454] S904: The AMF network element sends the first message to the UE (reader / writer).

[0455] For example, the first message could be a NAS message.

[0456] Accordingly, the UE (equivalent to the second network element of the present application) receives the first message, which contains the first signaling, and therefore also contains the operation identifier (first message identifier), tag operation command, second tag filter (inventory area), and reporting trigger event information.

[0457] S905: The UE (reader) identifies and determines the first tag based on the second tag filter.

[0458] The first tag can be a set of tags that satisfy the tag filter rules, or it can be a tag with a specific tag identifier. This application embodiment does not limit this.

[0459] For example, the tag accessed by the UE (reader) side is matched with the tag ID (1) based on the second tag filter, and the corresponding operation identifier (1) is identified according to the tag (1).

[0460] It should be understood that the aforementioned second tag filter can be used to match the corresponding ID for the accessed tag, and it can also be used to determine the corresponding operation identifier based on the tag ID. For example, the second tag filter can include the correspondence between tag IDs and operation identifiers, i.e., one tag ID corresponds to one operation identifier, or multiple tag IDs correspond to one operation identifier. Furthermore, an operation identifier can be used to identify a unique target server, but one target server may correspond to multiple operation identifiers; that is, the same target server may generate different operation identifiers on the NEF network element in multiple tag inventory requests.

[0461] S906: The UE (user-writer) executes tag operations according to the tag operation command.

[0462] S907: The UE (reader / writer) sends a second message to the AMF network element.

[0463] For example, the second message could be an uplink NAS transmission message.

[0464] Correspondingly, the AMF network element receives the second message, which carries information about the access tag and the corresponding operation identifier.

[0465] For example, the uplink NAS transmission message carries the data (or information) of tag (1) and the operation identifier (1) corresponding to tag (1).

[0466] S908: The AMF network element sends a data transmission message to the NEF network element.

[0467] For example, the data transmission message can also be a second message.

[0468] Correspondingly, the NEF network element receives the data transmission message, which carries information about the access tag and the corresponding operation identifier (i.e., the first message identifier).

[0469] The information of the label can be the label data, or the information of the label can only contain the label's identifier.

[0470] S909: The NEF network element identifies the operation identifier in the data transmission message and determines the address of the corresponding PIOT server.

[0471] Since the NEF network element has pre-recorded the first message and generated a unique operation identifier for it in step S903, thus recording the correspondence between the operation identifier and the first message, when the NEF network element determines that the data transmission message is associated with the first message, it can further determine the address information of the PIOT server based on the first message and the inventory request message that triggered the first message. Therefore, when the NEF network element receives the operation identifier fed back by the UE (reader / writer) through the AMF network element, it can determine the address of the corresponding PIOT server.

[0472] S910: The NEF network element sends the tag information carried in the data transmission message to the corresponding PIOT server.

[0473] The NEF network element sends the tag information to the corresponding PIOT server based on the address of the PIOT server.

[0474] In this fourth embodiment, a connection is established between the tag and the PIOT server (i.e., the enterprise's application server) based on the control plane, and the reader / writer performs tag identification and management. Furthermore, since this fourth embodiment transmits tag information through the control plane, there is no need for a session establishment process, thus saving signaling processes and reducing the latency required to transmit tag information.

[0475] Example 5

[0476] In this fifth embodiment, taking the terminal device UE as the reader / writer as an example, based on the above... Figure 3C The third transmission path shown primarily involves the UE (reader) managing the tags, transmitted via the control plane channel; that is, the PIOT server sends instructions to the AMF network element through the NEF network element. However, in this fifth embodiment, the UE (reader) can send information about all accessed tags to the AMF network element (equivalent to the second network element mentioned above), allowing the AMF network element to manage and identify the tags on behalf of the UE (reader). (See reference...) Figure 10 As shown, the specific process for transmitting tag information is as follows:

[0477] S1000: The UE (reader / writer) has completed the registration process.

[0478] The specific registration process performed by the UE (reader / writer) can be found in existing technical implementations and will not be described here.

[0479] S1001: The PIOT server sends a disk storage request message to the NEF network element.

[0480] Accordingly, the NEF network element (equivalent to the first network element of this application) receives the inventory request message, wherein the inventory request message carries tag operation commands, a second tag filter (such as inventory area, inventory type, inventory rules, etc.) and information such as reporting trigger events (such as inventory cycle, new tag access event, tag departure).

[0481] This step S1001 can be referenced in conjunction with the above step S901.

[0482] S1002: NEF network element records the address of the PIOT server that sent the disk storage request message.

[0483] Specifically, NEF network elements can record the address of the PIOT server (i.e., the enterprise's application server) from which each disk storage request message is received.

[0484] This step S1002 can be referenced in conjunction with the above step S902.

[0485] S1003: The NEF network element generates an operation identifier and sends the first message to the AMF network element.

[0486] Specifically, the operation identifier (equivalent to the first identifier mentioned above in this application) can be used by the NEF network element to uniquely identify the first message. By identifying the first message, the NEF network element can further identify the inventory request message that triggered the first message, thereby determining the address information of the recorded PIOT server.

[0487] Accordingly, the AMF network element (equivalent to the second network element of this application) receives the first message, which carries an operation identifier and information included in the inventory request message, namely, tag operation command, second tag filter (inventory area), and reporting trigger event information. Since the first message is triggered by the inventory request message, the operation identifier can also be used to identify the first message.

[0488] This step S1003 can be referenced in conjunction with the above step S903.

[0489] S1004: The AMF network element sends a third message to the UE (reader / writer).

[0490] For example, the third message could be a NAS message.

[0491] Accordingly, the UE (reader) receives the third message, which carries the tag operation command from the first message and information such as the reporting trigger event.

[0492] S1005: The UE (reader) performs tag operations on all tags within the signal range according to the tag operation command.

[0493] S1006: The UE (reader / writer) sends the fourth message to the AMF network element.

[0494] For example, the fourth message could be an uplink NAS message.

[0495] The UE (Reader / Writer) performs tag operations on all tags within the signal range according to the tag operation command, carries the operation results (i.e., the collected tag information) in the fourth message (such as the uplink NAS message), and sends it to the AMF network element.

[0496] S1007: The AMF network element identifies and determines the first label based on the corresponding second label filter.

[0497] The first tag can be a set of tags that satisfy the tag filter rules, or it can be a tag with a specific tag identifier.

[0498] After the AMF network element identifies and determines the first tag, the AMF network element can also add the corresponding operation identifier to the information of the first tag.

[0499] S1008: The AMF network element sends a second message to the NEF network element.

[0500] For example, the second message could be a data transmission message.

[0501] Correspondingly, the NEF network element receives the second message, which carries information about the access tag and the corresponding operation identifier.

[0502] S1009: The NEF network element identifies the operation identifier in the second message and determines the address of the corresponding PIOT server.

[0503] Since the NEF network element has pre-recorded the first message and generated a unique operation identifier for it in step S1003, thus recording the correspondence between the operation identifier and the first message, when the NEF network element determines that the second message is associated with the first message, it can further determine the address information of the corresponding PIOT server based on the first message and the inventory request message that triggered the first message. Therefore, when the NEF network element receives the operation identifier fed back by the UE (reader / writer) through the AMF network element, it can determine the address of the corresponding PIOT server.

[0504] S1010: The NEF network element sends the tag information carried in the second message to the corresponding PIOT server.

[0505] The information of the label can be the label data, or the information of the label can only contain the label's identifier.

[0506] The NEF network element sends the tag information to the corresponding PIOT server based on the address of the PIOT server.

[0507] In this fifth embodiment, a connection between the UE (reader / writer) and the PIOT server (i.e., the enterprise's application server) is established based on the control plane. This means that tag information is transmitted via the control plane, eliminating the need for a session establishment process, thus saving signaling steps and reducing latency for transmitting tag information. Furthermore, the UE (reader / writer) can send tag information collected based on operation commands to the AMF network element, which then manages and identifies the tags on behalf of the UE (reader / writer), reducing the reader's capability requirements (i.e., eliminating the need for the reader / writer to store and process information related to the second tag filter).

[0508] Based on the same technical concept, embodiments of this application provide a communication device. This communication device may include modules or units corresponding to the methods / operations / steps / actions described in the first method embodiment above. These modules or units may be hardware circuits, software, or a combination of hardware circuits and software. The device may have the following characteristics: Figure 11 The structure shown.

[0509] like Figure 11 As shown, the communication device 1100 may include a receiving unit 1101, a processing unit 1102, and a sending unit 1103. The specific details of each unit are described below. Specifically, the receiving unit 1101 is used to receive a first request, which instructs the first communication device to obtain information about a first tag; the receiving unit 1101 is also used to obtain information about the first tag according to the first request, the information of the first tag including its identifier; the processing unit 1102 is used to determine a first communication session based on the identifier of the first tag, the first communication session being used to transmit the information of the first tag; and the sending unit 1103 is used to send the information of the first tag through the first communication session.

[0510] Optionally, the communication device 1100 may further include a storage unit ( Figure 11 (Not shown in the diagram), the storage unit can be used to store computer programs and / or instructions and / or information that execute the methods / operations / steps / actions described by the communication device.

[0511] In one possible implementation, when the processing unit 1102 determines the first communication session based on the identifier of the first tag, it is specifically configured to: determine the first communication session from at least one communication session based on the identifier of the first tag and first routing policy information, wherein the first routing policy information includes the correspondence between the identifier of the first tag and the identifier of the first communication session.

[0512] In one possible implementation, the processing unit 1102 is further configured to: establish at least one communication session before the receiving unit 1101 receives the first request, wherein the at least one communication session includes the first communication session; and establish at least one routing policy information, wherein each routing policy information includes a correspondence between a corresponding tag and an identifier of the communication session.

[0513] In one possible implementation, when establishing the first communication session, the processing unit 1102 is specifically used for:

[0514] The sending unit 1103 sends a first session request message, which includes first indication information indicating the home enterprise information of the first tag; the receiving unit 1101 receives a first response message, which responds to the first session request message and includes first target address information and / or first port number information, wherein the first target address information and / or the first port number information are determined based on the first indication information; the first communication session is established based on the first target address information and / or the first port number information; the first target address information and / or the first port number information are used to determine the target server, which is the server of the home enterprise.

[0515] In one possible implementation, when the sending unit 1103 sends the information of the first tag through the first communication session, it is specifically used to: send the information of the first tag to the target server through the first communication session.

[0516] In one possible implementation, when establishing the first communication session, the processing unit 1102 is specifically used for:

[0517] The sending unit 1103 sends a second session request message, which includes second indication information indicating the home enterprise information of the first tag; the receiving unit 1101 receives a second response message, which responds to the second session request message and includes second target address information and / or second port number information; wherein the second target address information and / or the second port number information are determined based on the second indication information; the first communication session is established based on the second target address information and / or the second port number information; the second target address information and / or the second port number information are used to determine a first user plane function network element, which is a user plane network element that provides services to the home enterprise.

[0518] In one possible implementation, when the sending unit 1103 sends the information of the first tag through the first communication session, it is specifically used to: send the information of the first tag to the first user plane function network element through the first communication session.

[0519] Based on the same technical concept, embodiments of this application provide a communication device. This communication device may include modules or units corresponding to the methods / operations / steps / actions described by the first user plane functional network element in the first method embodiment described above. These modules or units may be hardware circuits, software, or a combination of hardware circuits and software. The device may also have, for example,... Figure 11 The communication device 1100, as shown in the diagram, may include a receiving unit 1101, a processing unit 1102, and a sending unit 1103. The receiving unit 1101 is used to receive information about a first tag and first information, wherein the first information is used to determine the target server of the first tag. The processing unit 1102 is used to determine the target server of the first tag based on the first information. The sending unit 1103 is used to send the information of the first tag to the target server.

[0520] Optionally, the communication device 1100 may further include a storage unit ( Figure 11 (Not shown in the diagram), the storage unit can be used to store computer programs and / or instructions and / or information, etc., that execute the methods / operations / steps / actions described by the first user plane functional network element.

[0521] In one possible implementation, when receiving the first information, the receiving unit 1101 is specifically configured to: receive an N4 session request message, the N4 session request message including the first information, the first information indicating a first tag filter, the first tag filter being used to match the corresponding server according to the tag identifier;

[0522] When the processing unit 1102 determines the target server of the first tag based on the first information, it can specifically be used to: determine the first tag filter based on the first information; and match the target server of the first tag using the first tag filter based on the identifier of the first tag.

[0523] In one possible implementation, when receiving information from the first tag, the receiving unit 1101 can specifically be used to: receive information from the first communication device;

[0524] When receiving the first information, the receiving unit 1101 is specifically used to: receive an N4 session request message, wherein the N4 session request message includes the first information, and the first information indicates the address information of the first communication device and / or the third port number information of the first communication device for sending the information of the first tag;

[0525] When the processing unit 1102 determines the target server of the first tag based on the first information, it can specifically be used to: determine the address information of the first communication device and / or the third port number information based on the first information; determine the target server of the first tag based on the address information of the first communication device, the third port number information, and the first mapping information; wherein, the first mapping information includes the correspondence between the address information and / or port number information of the first communication device and the identifier of the server.

[0526] In one possible implementation, when receiving the first information, the receiving unit 1101 can specifically be used to: receive an N4 session request message, wherein the N4 session request message includes the first information, and the first information indicates the fourth port number information of the first user plane function network element that receives the information of the first tag;

[0527] When the processing unit 1102 determines the target server of the first tag based on the first information, it can specifically be used to: determine the fourth port number information of the first user plane function network element that receives the information of the first tag based on the first information; and determine the target server of the first tag based on the fourth port number information and the second mapping information; wherein, the second mapping information includes the correspondence between the port number information of the first user plane function network element and the identifier of the server.

[0528] In one possible implementation, when receiving the first information, the receiving unit 1101 may specifically be used to: receive an N4 session request message, the N4 session request message including the first information, the first information indicating the address information of the target server and / or the fifth port number information on the target server used to receive the information of the first tag; wherein, the address information of the target server and / or the fifth port number information is determined according to second indication information, the second indication information indicating the home enterprise information of the first tag, the second indication information being carried in a second session request message sent by the first communication device;

[0529] When the processing unit 1102 determines the target server of the first tag based on the first information, it can specifically be used to: determine the address information and / or the fifth port number information of the target server based on the first information; and determine the target server based on the address information and / or the fifth port number information of the target server.

[0530] Based on the same technical concept, this application provides a communication device, which may include modules or units that correspond one-to-one with the methods / operations / steps / actions described by the first network element (such as the network capability opening function network element) in the second method embodiment described above. The modules or units may be hardware circuits, software, or hardware circuits combined with software.

[0531] The device can also have, for example Figure 11 The communication device 1100, as shown in the diagram, may include a receiving unit 1101, a processing unit 1102, and a sending unit 1103. The receiving unit 1101 is used to receive a second message, which includes information about a first tag and a first identifier, the first identifier being used to determine the target server of the first tag. The processing unit 1102 is used to determine the target server of the first tag based on the first identifier. The sending unit 1103 is used to send the information of the first tag to the target server.

[0532] Optionally, the communication device 1100 may further include a storage unit ( Figure 11 (Not shown in the diagram), the storage unit can be used to store computer programs and / or instructions and / or information that execute the methods / operations / steps / actions described by the first network element.

[0533] In one possible implementation, when the processing unit 1102 determines the target server of the first tag based on the first identifier, it is specifically configured to: determine the target server of the first tag based on the first identifier and a first correspondence, wherein the first correspondence includes the correspondence between the first identifier and the target server.

[0534] In one possible implementation, the sending unit 1103 is further configured to: send a first message to the second network element before the receiving unit 1101 receives the second message, the first message including a first operation instruction and a second tag filter, and a first identifier, the first operation instruction being used to instruct the second network element to acquire the identifier of at least one tag, and the second tag filter being used to determine the corresponding tag based on the identifier of different tags.

[0535] Based on the same technical concept, embodiments of this application provide a communication device, which may include modules or units corresponding to the methods / operations / steps / actions described by the second network element in the second method embodiment described above. The modules or units may be hardware circuits, software, or a combination of hardware circuits and software.

[0536] The device can also have, for example Figure 11 The communication device 1100, as shown in the diagram, may include a receiving unit 1101, a processing unit 1102, and a sending unit 1103. The receiving unit 1101 is used to receive a first message, which includes a first operation instruction, a second tag filter, and a first identifier. The first operation instruction instructs a second network element to acquire the identifier of at least one tag. The second tag filter determines corresponding tags based on the identifiers of different tags, and the first identifier determines the target server of the first tag. The processing unit 1102 is used to match the identifier of the first tag with the second tag filter according to the first operation instruction to obtain the first tag. The sending unit 1103 is used to send a second message, which includes information about the first tag and the first identifier.

[0537] Optionally, the communication device 1100 may further include a storage unit ( Figure 11 (Not shown in the diagram), the storage unit can be used to store computer programs and / or instructions and / or information that execute the methods / operations / steps / actions described by the second network element.

[0538] In one possible implementation, when receiving the first message, the receiving unit 1101 can be specifically used to: receive the first message from the mobility management network element; when sending the second message, the sending unit 1103 can be specifically used to: send the second message to the mobility management network element.

[0539] In one possible implementation, when receiving the first message, the receiving unit 1101 can be specifically used to: receive the first message from the first network element; when sending the second message, the sending unit 1103 can be specifically used to: send the second message to the first network element.

[0540] Based on the same inventive concept, embodiments of this application also provide a communication device, which adopts... Figure 5A ,as well as Figures 6-8 The steps performed by the first communication device in the method provided in the corresponding embodiment may be related to... Figure 11 The communication device 1100 shown is the same equipment. See also Figure 12As shown, the communication device 1200 includes a transceiver 1201, a processor 1202, and a memory 1203. The transceiver 1201, processor 1202, and memory 1203 are connected via a bus to enable data exchange.

[0541] The communication bus 1204 can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The communication bus 1204 can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 12 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0542] It should be understood that the transceiver 1201 in the communication device 1200 includes the functions of the receiving unit 1101 and the transmitting unit 1103 in the communication device 1100. The transceiver 1201 supports the transmission and reception of information and data between the communication device 1100 and the first user plane functional network element in the above embodiment. The memory 1203 stores the program code and data of the communication device 1200. The processor 1202 calls the program code and data stored in the memory 1203 and executes it. Figure 5A ,as well as Figures 6-8 The method shown involves the processing of the first communication device and / or other processes used in the technology described in this application.

[0543] In addition, the communication device 1200 may also include other interfaces, such as fiber optic link interfaces, Ethernet interfaces, microwave link interfaces, copper wire interfaces, etc., to enable the communication device 1200 to interact with other devices (e.g., access network devices, policy control network elements).

[0544] Optionally, the processor 1202 may be a central processing unit, ASIC, FPGA, or CPLD.

[0545] It should be noted that, Figure 12 The communication device 1200 shown includes only one transceiver 1201, one processor 1202, and one memory 1203. In actual implementation, the number of transceivers 1201, processors 1202, and memory 1203 can be one or more.

[0546] The same applies. Figure 12 The communication device 1200 shown can also achieve this. Figure 5A as well as Figures 6-8 The method executed by the first user plane functional network element in the corresponding embodiment may be implemented as follows: Figure 5B as well as Figures 9-10 The method executed by the first network element in the corresponding embodiment may be implemented as follows: Figure 5B as well as Figures 9-10 The method executed by the second network element in the corresponding embodiment. Figure 12 The communication device 1200 shown can also be the same as described above. Figure 11 The communication device 1100 shown is the same device. Therefore, the implementation of the communication device 1200, which is not described in detail, can be referred to... Figures 5A-5B ,as well as Figures 6-10 The corresponding embodiments provide methods described above, or refer to the above descriptions. Figure 12 The relevant description of the communication device 1200 shown is omitted here.

[0547] Figure 13 This is a schematic diagram of a chip device structure provided in an embodiment of this application. The chip 1300 includes an interface circuit 1301 and one or more processors 1302. Optionally, the chip 1300 may also include a bus. Wherein:

[0548] The processor 1302 may be an integrated circuit chip with signal processing capabilities. In implementation, each step of the aforementioned eye-tracking method can be completed through integrated logic circuits in the hardware of the processor 1302 or through software instructions. The processor 1302 may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods and steps disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor.

[0549] The interface circuit 1301 can be used to send or receive data, instructions or information. The processor 1302 can use the data, instructions or other information received by the interface circuit 1301 to process the data, instructions or other information, and can send the processed information out through the interface circuit 1301.

[0550] Optionally, the chip also includes memory 1303, which may include read-only memory and random access memory, and provides operation instructions and data to the processor. A portion of memory 1303 may also include non-volatile random access memory (NVRAM).

[0551] Optionally, the memory stores executable software modules or data structures, and the processor can execute corresponding operations by calling the operation instructions stored in the memory (which may be stored in the operating system).

[0552] Optionally, the chip can be used in the first communication device involved in the embodiments of this application. Optionally, the interface circuit 1301 can be used to output the execution result of the processor 1302. For the communication methods provided by one or more embodiments of this application, please refer to the foregoing embodiments, which will not be repeated here.

[0553] It should be noted that the functions of the interface circuit 1301 and the processor 1302 can be implemented through hardware design, software design, or a combination of hardware and software; no restrictions are imposed here.

[0554] Based on the same concept as the above-described method embodiments, this application also provides a computer-readable storage medium storing some instructions. When these instructions are invoked and executed by a computer, the computer can perform the methods involved in any possible design of the above-described method embodiments. In this application, the computer-readable storage medium is not limited; for example, it can be RAM (random-access memory), ROM (read-only memory), etc.

[0555] Based on the same concept as the above method embodiments, this application also provides a computer program product that, when executed by a computer, can perform the methods involved in the method embodiments and any possible designs of the above method embodiments.

[0556] Based on the same concept as the above method embodiments, this application also provides a chip, which may include a processor and an interface circuit, for performing the methods involved in any possible implementation of the above method embodiments, wherein "coupling" means that two components are directly or indirectly combined with each other, and such combination may be fixed or movable, and such combination may allow fluid, electricity, electrical signals or other types of signals to communicate between the two components.

[0557] It should be noted that the "at least one" in the embodiments of this application includes one or more; wherein, "more" means two or more. Furthermore, it should be understood that in the description of this application, terms such as "first" and "second" are used only for descriptive purposes and should not be construed as indicating or implying relative importance, nor as indicating or implying order.

[0558] The terminology used in the following embodiments is for the purpose of describing particular embodiments only and is not intended to be limiting of this application. As used in the specification and appended claims of this application, the singular expressions “a,” “the,” “the,” “the,” and “this” are intended to also include expressions such as “one or more,” unless the context clearly indicates otherwise. It should also be understood that in the embodiments of this application, “one or more” means one or more (including two); “and / or” describes the relationship between related objects, indicating that three relationships may exist; for example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character “ / ” generally indicates that the preceding and following related objects are in an “or” relationship.

[0559] References to "one embodiment" or "some embodiments" as described in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0560] The module division in this embodiment is illustrative and represents only one logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional modules in each embodiment of this application can be integrated into a single processor, exist as separate physical entities, or be integrated into a single module. The integrated modules described above can be implemented in hardware or as software functional modules.

[0561] This application provides a computer-readable storage medium storing a computer program, the computer program including instructions for performing the above-described method embodiments.

[0562] This application provides a computer program product containing instructions that, when run on a computer, cause the computer to execute the above-described method embodiments.

[0563] The module division in this embodiment is illustrative and represents only one logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional modules in each embodiment of this application can be integrated into a single processor, exist as separate physical entities, or be integrated into a single module. The integrated modules described above can be implemented in hardware or as software functional modules.

[0564] Through the above description of the embodiments, those skilled in the art will clearly understand that the embodiments of this application can be implemented in hardware, firmware, or a combination thereof. When implemented in software, the above functions can be stored in a computer-readable medium or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any medium that facilitates the transfer of a computer program from one place to another. Storage media can be any available medium accessible to a computer. For example, but not limited to, computer-readable media can include RAM, ROM, electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, magnetic disk storage media, or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible to a computer. Furthermore, any connection can suitably be a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of the medium. As used in embodiments of this application, disks and discs include compact discs (CDs), laser discs, optical discs, digital video discs (DVDs), floppy disks, and Blu-ray discs, wherein disks typically magnetically copy data, while discs optically copy data using lasers. The combinations above should also be included within the scope of protection for computer-readable media.

[0565] In summary, the above descriptions are merely embodiments of this application and are not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made based on the disclosure of this application should be included within the scope of protection of this application.

Claims

1. A communication method, characterized in that, include: A first communication device receives a first request, the first request instructing the first communication device to obtain information about a first tag, the first request including instruction information required by the first communication device to perform tag inventory; The first communication device performs tag inventory according to the instruction information in the first request, and obtains the information of the first tag, wherein the information of the first tag includes the identifier of the first tag; The first communication device determines a first communication session from at least one communication session based on the identifier of the first tag and the first routing policy information. The first routing policy information includes the correspondence between the identifier of the first tag and the identifier of the first communication session. The first communication session is used to transmit information of the first tag. The first communication device sends the information of the first tag through the first communication session.

2. The method according to claim 1, characterized in that, Before the first communication device receives the first request, it further includes: The first communication device establishes at least one communication session, wherein the at least one communication session includes the first communication session; The first communication device establishes at least one routing policy information, each routing policy information including a correspondence between a corresponding tag and a communication session identifier, and the at least one routing policy information includes the first routing policy information.

3. The method according to claim 2, characterized in that, The first communication device establishes the first communication session, including: The first communication device sends a first session request message, which includes first indication information indicating the enterprise information to which the first tag belongs; The first communication device receives a first response message, which is used to respond to the first session request message. The first response message includes first target address information and / or first port number information, wherein the first target address information and / or the first port number information are determined according to the first indication information. The first communication device establishes the first communication session based on the first target address information and / or the first port number information; the first target address information and / or the first port number information are used to determine the target server, which is the server of the home enterprise.

4. The method according to claim 3, characterized in that, The first communication device sends information about the first tag through the first communication session, including: The first communication device sends the information of the first tag to the target server through the first communication session.

5. The method according to claim 2, characterized in that, The first communication device establishes the first communication session, including: The first communication device sends a second session request message, which includes second indication information indicating the enterprise information to which the first tag belongs; The first communication device receives a second response message, which is used to respond to the second session request message. The second response message contains second target address information and / or second port number information; wherein the second target address information and / or the second port number information are determined according to the second indication information. The first communication device establishes the first communication session based on the second target address information and / or the second port number information; the second target address information and / or the second port number information are used to determine the first user plane function network element, which is a user plane network element that provides services to the home enterprise.

6. The method according to claim 5, characterized in that, The first communication device sends information about the first tag through the first communication session, including: The first communication device sends the information of the first tag to the first user plane function network element through the first communication session.

7. A communication method, characterized in that, include: The first user plane function network element receives information about the first tag from the first communication device through the first communication session. The first communication session is determined by the first communication device from at least one communication session based on the identifier of the first tag and the first routing policy information. The first routing policy information includes the correspondence between the identifier of the first tag and the identifier of the first communication session. The first user plane function network element receives first information, which is used to determine the target server of the first tag. The first user plane function network element determines the target server of the first tag based on the first information; The first user plane function element sends the information of the first tag to the target server.

8. The method according to claim 7, characterized in that, The first user plane functional network element receives the first information, including: The first user plane function network element receives an N4 session request message, the N4 session request message including the first information, the first information indicating a first tag filter, the first tag filter being used to match the corresponding server according to the tag identifier; The first user plane function network element determines the target server of the first tag based on the first information, including: The first user plane function network element determines the first tag filter based on the first information; The first user plane function network element matches the target server of the first label using the first label filter based on the identifier of the first label.

9. The method according to claim 7, characterized in that, The first user plane functional network element receives information from the first tag, including: The first user plane function network element receives information from the first communication device regarding the first tag; The first user plane functional network element receives the first information, including: The first user plane function network element receives an N4 session request message, the N4 session request message including the first information, the first information indicating the address information of the first communication device and / or the third port number information of the first communication device for sending the information of the first tag; The first user plane function network element determines the target server of the first tag based on the first information, including: The first user plane function network element determines the address information of the first communication device and / or the third port number information based on the first information; The first user plane function network element determines the target server of the first tag based on the address information of the first communication device, the third port number information, and the first mapping information; wherein, the first mapping information includes the correspondence between the address information and / or port number information of the first communication device and the identifier of the server.

10. The method according to claim 7, characterized in that, The first user plane functional network element receives the first information, including: The first user plane function network element receives an N4 session request message, the N4 session request message including the first information, the first information indicating the fourth port number information on the first user plane function network element that receives the information of the first tag; The first user plane function network element determines the target server of the first tag based on the first information, including: The first user plane function network element determines the fourth port number information for receiving the information of the first tag on the first user plane function network element based on the first information; The first user plane function network element determines the target server of the first tag based on the fourth port number information and the second mapping information; wherein, the second mapping information includes the correspondence between the port number information on the first user plane function network element and the server identifier.

11. The method according to claim 7, characterized in that, The first user plane functional network element receives the first information, including: The first user plane function network element receives an N4 session request message, the N4 session request message including the first information, the first information indicating the address information of the target server and / or the fifth port number information on the target server used to receive the information of the first tag; wherein, the address information of the target server and / or the fifth port number information is determined according to the second indication information, the second indication information indicating the home enterprise information of the first tag, the second indication information being carried in the second session request message sent by the first communication device; The first user plane function network element determines the target server of the first tag based on the first information, including: The first user plane function network element determines the address information of the target server and / or the fifth port number information based on the first information; The first user plane function network element determines the target server based on the address information of the target server and / or the fifth port number information.

12. A communication device, characterized in that, It includes a unit or module for performing the method as described in any one of claims 1 to 6, or includes a unit or module for performing the method as described in any one of claims 7 to 11.

13. A communication device, characterized in that, include: processor; The processor is configured to read from memory and run a program to implement the method as described in any one of claims 1 to 6, or 7 to 11.

14. A communication system, characterized in that, include: A first communication device for performing the method according to any one of claims 1 to 6, and a first user plane function network element for performing the method according to any one of claims 7 to 11.

15. A computer program product, characterized in that, Includes a computer program that, when executed by a communication device, implements the method as described in any one of claims 1 to 11.

16. A computer-readable storage medium, characterized in that, The storage medium stores a computer-readable program or instructions that, when executed by a communication device, implement the method as described in any one of claims 1 to 11.

Citation Information

Patent Citations

  • User message transmission method and communication equipment

    CN110677345A