WO2023246431A1 - 一种通信方法和装置 - Google Patents

一种通信方法和装置 Download PDF

Info

Publication number
WO2023246431A1
WO2023246431A1 PCT/CN2023/096809 CN2023096809W WO2023246431A1 WO 2023246431 A1 WO2023246431 A1 WO 2023246431A1 CN 2023096809 W CN2023096809 W CN 2023096809W WO 2023246431 A1 WO2023246431 A1 WO 2023246431A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
network element
tag
communication device
message
Prior art date
Application number
PCT/CN2023/096809
Other languages
English (en)
French (fr)
Inventor
黄康
诸华林
徐艺珊
李汉涛
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2023246431A1 publication Critical patent/WO2023246431A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/80—Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup

Definitions

  • the present application relates to the field of communication technology, and in particular, to a communication method and device.
  • IoT technology can include passive or semi-passive IoT (P-IoT) technology, that is, the nodes of the network can obtain energy from the environment to support the perception, transmission and distributed computing of data in the network. wait.
  • P-IoT passive or semi-passive IoT
  • a passive or semi-passive IoT architecture it usually includes passive or semi-passive tags, readers and servers.
  • the readers can communicate with the tags (or RF card) reads and writes to identify the tag (or RF card) and interact with the tag (or RF card) for information and data.
  • Tags that is, semi-passive tags
  • Tags can also store electrical energy by obtaining solar energy and other methods, and actively send a signal of a certain frequency to the reader/writer.
  • the reader/writer receives the information carried by the signal and decodes it, and further decodes the decoded information. The information is sent to the central information system for corresponding data processing.
  • the reader/writer may be shared by multiple enterprises and does not involve providing enterprise information through the tag, so the reader/writer cannot directly communicate with the target.
  • the tag's own enterprise server establishes a user plane channel.
  • the reader/writer does not implement different routing strategies for 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 for different enterprises.
  • a communication method and device that can effectively and accurately transmit tag information.
  • the present application provides a first communication method.
  • the method 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 it can be a reader.
  • the terminal device (or the controller or chip corresponding to the terminal device) that establishes a communication connection.
  • the terminal device may be, but is not limited to, a computer, a mobile phone, a tablet, or other device that can establish a communication connection with the reader, and is not limited to this.
  • the method specifically includes the following steps: the first communication device receives a first request, the first request instructs the first communication device to obtain the information of the first tag; the first communication device obtains the information of the first tag according to the first request.
  • the information of the first tag includes the identification of the first tag; the first communication device determines a first communication session according to the identification of the first tag, and the first communication session is used to transmit the information of the first tag; The first communication device sends the information of the first tag through the first communication session.
  • the first communication device can receive the first request from the application server. And the first communication device sends the information of the first tag to the application server through the first communication session.
  • This application specifically determines which transmission path the first communication device uses to send the information of the first tag to the application server. No specific restrictions are made.
  • the first communication device can determine a first communication session specifically used to transmit the information of the first tag, thereby effectively improving the efficiency of the first communication device. The accuracy of the information transmitted for this first tag.
  • the first communication device determines the first communication session based on the identification of the first tag, including: the first communication device determines the first communication session from at least one based on the identification of the first tag and the first routing policy information.
  • the first communication session is determined in one communication session, and the first routing policy information includes a correspondence relationship between the identifier of the first label and the identifier of the first communication session.
  • the first routing policy information can be improved based on the existing user equipment routing policy (UE route selection policy, URSP), that is, the correspondence between the label identifier and the communication session identifier is added to the URSP policy. relationship, so that the first communication device can also determine an appropriate communication session based on the identification of the tag.
  • UE route selection policy URSP
  • the first routing policy information may also include the corresponding relationship between the identification of the first label and the address information and/or port number information of the target server. Therefore, the first communication device may also perform routing according to the first routing policy.
  • the corresponding relationship contained in the information determines the address information and/or port number information of the target server corresponding to the first tag, and further, based on the corresponding relationship between the address information and/or port number information of the server and the communication session ( It may also be included in the first routing policy information or stored in the first communication device) to determine the first communication session corresponding to the address information and/or port number information of the target server.
  • This application does not limit the specific manner in which the first communication device determines the first communication session based on the first routing policy information.
  • the first communication device can accurately calculate the information based on the first routing policy information.
  • the first communication session used to transmit the information of the first tag is determined accurately, thereby improving the accuracy of transmitting the information of the first tag.
  • the method before the first communication device receives the first request, the method further includes: the first communication device establishing at least one communication session, and the at least one communication session includes the first communication session; The device establishes at least one routing policy information, and each routing policy information includes a corresponding relationship between a corresponding label and an identifier of the communication session.
  • the first communication device before the first communication device receives a request for instructing to obtain the information of the first tag, the first communication device needs to establish at least one communication session, and the first communication session includes the first communication session, And establish corresponding routing policy information, so that the routing policy information includes the corresponding relationship between the corresponding label and the identification of the communication session. Therefore, the first communication device establishes at least one effective communication path for transmitting tag information and corresponding routing policy information. Subsequently, the first communication device can obtain information from the at least one communication session based on the identification of the first tag and the corresponding routing policy. An appropriate communication session is selected for transmitting the information of the first tag, thereby ensuring the effectiveness and accuracy of transmitting the information of the first tag.
  • the first communication device establishing the first communication session may include but is not limited to the following methods:
  • the first communication device establishing the first communication session includes: the first communication device sends a first session request message, the first session request message includes first indication information, and the first indication information Indicate the home enterprise information of the first tag; the first communication device receives a first response message, the first response message is used to respond to the The first session request message, the first response message includes the first target address information and/or the first port number information, wherein the first target address information and/or the first port number information is based on the first Determined by an indication information; the first communication device establishes the first communication session according to the first target address information, and/or the first port number information; the first target address information, and/or the first port The number information is used to determine the target server, which is the server belonging to the enterprise.
  • the process of establishing the first communication session by the first communication device can be implemented by referring to the existing process of establishing a PDU session, which will not be described in detail here.
  • the first communication device The session request message sent carries first indication information for indicating the enterprise information to which the label belongs.
  • the first target address information and/or the first port number information may be determined by the session management function SMF network element in the process based on the first indication information (or the first label belonging enterprise information), or may be It is determined by other network elements based on the first indication information (or the enterprise information to which the first label belongs) and then sent to the session management function SMF network element. This application does not specifically limit this.
  • the label ownership enterprise information can be but is not limited to the data network element name DNN and/or network element slice selection assistance information (NSSAI).
  • the above-mentioned first indication information may be used to indicate the DNN and/or NSSAI of the enterprise to which the access tag belongs, or the first indication information may be the DNN and/or NSSAI of the enterprise to which the access tag belongs. This application does not limit this.
  • the DNN and/or NSSAI indicate the network information of the target enterprise requested to be established by the first communication device.
  • the address and/or port number information of the target server of the first tag is determined based on the enterprise information of the first tag, so that the communication between the first communication device and the target server of the first tag can be effectively and accurately established.
  • Communication connection i.e. first communication session.
  • the first communication device can directly establish a first communication session with the target server.
  • the first communication device sends the information of 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.
  • 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.
  • the first communication device establishing the first communication session includes: the first communication device sending a second session request message, the second session request message including second indication information, and the second indication information Indicate the home enterprise information of the first tag; the first communication device receives a second response message, the second response message is used to respond to the second session request message, the second response message includes 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 is determined based on the second target address information, and /or the second port number information is used to establish the first communication session; the second target address information, and/or the second port number information is used to determine the first user plane functional network element, the first user plane functional network element The element is the user plane network element that provides services to the affiliated enterprise.
  • the process of establishing the first communication session by the first communication device can be implemented by referring 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 may be determined by the session management function SMF network element in the process based on the second indication information (or the first label belonging enterprise information), or may be It is determined by other network elements based on the second indication information (or the enterprise information to which the first label belongs) and then sent to the session management function SMF network element. This application does not specifically limit this.
  • the tag belonging enterprise information may be but is not limited to DNN and/or NSSAI.
  • the above-mentioned second indication information may be used to indicate the DNN and/or NSSAI of the enterprise to which the access tag belongs, or the second indication information may be the access tag's home enterprise's DNN and/or NSSAI.
  • the tag belongs to the enterprise's DNN and/or NSSAI, which is not limited in this application.
  • the DNN and/or NSSAI indicate the network information of the target enterprise requested to be established by the first communication device.
  • the label belonging enterprise information may be the data network element name DNN.
  • the address information and/or port information of the first user plane functional network element of the first tag is determined based on the enterprise information to which the first tag belongs, so that the first communication device and the first communication device can be effectively and accurately established.
  • the communication connection between the first user plane functional network elements of the first tag ie, the first communication session).
  • the first communication device can establish a first communication session with the first user plane functional network element.
  • the first communication device sends the information of 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 functional network element through the first communication session. .
  • the first communication device can also send the information of the first tag to the target server through the first user plane functional network element.
  • the present application provides a first communication method.
  • This method can be executed by the first user plane functional network element or by the chip corresponding to the first user plane functional network element.
  • This method is not limited.
  • the method specifically includes the following steps: the first user plane functional network element receives the information of the first label and the first information, the first information is used to determine the target server of the first label; the first user plane functional network element receives the first label according to the first user plane functional network element.
  • the first information determines the target server of the first label; the first user plane functional network element sends the information of the first label to the target server.
  • the first user plane functional network element receives the information of the first label and the first information. Since the first information is used to determine the target server of the first label, the first user plane functional network element can According to the first information, the target server of the first tag is determined, and then the information of the first tag can be effectively and accurately sent to the target server.
  • the first user plane functional network element receiving the first information includes: the first user plane functional network element receiving an N4 session request message, the N4 session request message including the first information, the The first information indicates a first tag filter, the first tag filter is used to match the corresponding server according to the identification of the tag;
  • the first user plane functional network element determines the target server of the first label based on the first information, including: the first user plane functional network element determines the first label based on the first information Filter; the first user plane functional network element uses the first label filter to match the target server of the first label based on the identification of the first label.
  • the first user plane function UPF network element may receive the N4 session request message from the session management function SMF network element during the PDU session establishment/modification process, and the N4 session request message includes the first message.
  • the first user plane functional network element obtains the first message carried in the N4 session request message by receiving the N4 session request message.
  • the first message indicates the first label filter. Therefore, the first user
  • the plane functional network element can determine a first label filter based on the first information.
  • the first label filter is used to match the corresponding server according to the identification of the label, and then the first user plane functional network element is based on the identification of the first label, And using the first label filter, the target server of the first label can be accurately matched.
  • the first user plane functional network element receiving the information of the first tag includes: the first user plane functional network element receiving the information of the first tag from the first communication device.
  • the first user plane functional network element receives the first information, including: the first user plane functional network element receives an N4 session request message, the N4 session request message includes the first information, and the first The information indicates the address information of the first communication device and/or the third port number information through which the first communication device sends the information of the first tag;
  • the first user plane functional network element determines the target server of the first label based on the first information
  • the method includes: the first user plane functional 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 functional network element determines the address information and/or the third port number information of the first communication device based on the first communication device.
  • the address information, the third port number information, and the first mapping information determine the target server of the first tag; wherein the first mapping information includes the address information and/or port number information of the first communication device and the server The corresponding relationship between the identifiers.
  • the first mapping information includes a corresponding relationship between the address information and/or port number information of the first communication device and the identity of the server, which may be a pre-configured and known relationship.
  • the first user plane functional network element receives the information of the first label from the first communication device.
  • the first user plane functional network element receives the N4 session request message, and the first information included therein indicates that the When the address information of the first communication device and/or the third port number information of the first communication device is sent by the first communication device, then the first user plane functional network element will use the address information of the first communication device and/or the third port number information of the first communication device. Or the first communication device sends the third port number information and the first mapping information of the first tag information, so that the target server of the first tag can be accurately determined.
  • the first user plane functional network element receiving the first information includes: the first user plane functional network element receiving an N4 session request message, the N4 session request message including the first information, the The first information indicates the fourth port number information on the first user plane functional network element that receives the information of the first label; the first user plane functional network element determines the target server of the first label based on the first information, The method includes: the first user plane functional network element determines the fourth port number information on the first user plane functional network element for receiving the information of the first label based on the first information; the first user plane functional network element determines the fourth port number information on the first user plane functional network element based on the first information.
  • the fourth port number information and the second mapping information determine the target server of the first label; wherein the second mapping information includes the corresponding relationship between the port number information on the first user plane functional network element and the identity of the server.
  • the first user plane functional network element when the first user plane functional network element receives the N4 session request message, and the first information included therein indicates the fourth port number information on the first user plane functional network element that receives the information of the first label, then The first user plane functional network element can accurately determine the target server of the first label based on the fourth port number information and the second mapping information.
  • the first user plane functional network element receiving the first information includes: the first user plane functional network element receiving an N4 session request message, the N4 session request message including the first information, the The first information indicates the address information of the target server and/or the fifth port number information on the target server for receiving the information of the first label; wherein the address information of the target server and/or the fifth port number information is determined based on the second indication information, the second indication information indicates the home enterprise information of the first tag, the second indication information is carried in the second session request message sent by the first communication device; the first user plane function The network element determines the target server of the first label 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 functional network element determines the target server based on the address information of the target server and/or the fifth port number information.
  • the first user plane function network element receives the N4 session request message, the first information included in it indicates the address information of the target server and/or the fifth node on the target server for receiving the information of the first label. port number information, then the first user plane functional network element can accurately determine the third port number information 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 label. A label for the target server.
  • the present application provides a second communication method.
  • This method can be executed by the first network element or by a chip corresponding to the first network element.
  • This method is not limited.
  • the method specifically includes the following steps: the first network element receives a second message, the second message includes information of the first label and a first identification, and the first identification is used to determine the first label.
  • Target server the first network element determines the target server of the first tag according to the first identification; the first network element sends the information of the first tag to the target server.
  • the first network element may receive the second message from the second network element.
  • the first network element may be a network opening function NEF network element.
  • the second network element may be a first communication device (for example, equipped with read and write capabilities). terminal equipment with server function) or access and mobility management function AMF network element.
  • the first network element obtains the information of the first label and the first identification. Since the first identification is used to determine the target server of the first label, the first network element can obtain the information of the first label according to the first identification. The identification determines the target server of the first tag, so that the information of the first tag can be accurately sent to the target server.
  • the first network element determines the target server of the first tag based on the first identifier, including: the first network element determines the first server based on the first identifier and the first corresponding relationship.
  • the target server of the tag wherein the first correspondence includes a correspondence between the first identification and the target server.
  • the first network element can effectively and accurately determine the corresponding target server.
  • the method before the first network element obtains the second message from the second network element, the method further includes: the first network element sends a first message to the second network element, and the first message includes the first message.
  • the operation instruction and the second tag filter, as well as the first identification the first operation instruction is used to instruct the second network element to obtain the identification of the first tag from the identification of at least one tag according to the first identification, and the third The two-tag filter is used to determine the information of the corresponding tag based on the identification of different tags.
  • the first identifier may be information used to identify the target server.
  • the first identifier may be the identifier of the first message, or the first identifier may be the identifier of the first operation instruction, and the first identifier may be the identifier of the first operation instruction.
  • the first network element sends the first operation instruction, the second label filter, and the first identification to the second network element, so that the second network element can, based on the first operation instruction and the first identification, and the second label filter obtains the information of the first label, thereby ensuring that the first network element can subsequently effectively obtain the information of the first label and the first identification from the second network element, based on the first identification Accurately determine the target server for this first label.
  • the present application provides a second communication method.
  • This method can be executed by the second network element or by the chip corresponding to the second network element.
  • This method is not limited.
  • the method specifically includes the following steps: the second network element receives a first message, the first message includes a first operation instruction, a second label filter, and a first identification; wherein the first operation instruction is used to indicate the first operation instruction.
  • the second network element obtains the identifier of at least one tag.
  • the second tag filter is used to determine the information of the corresponding tag according to the identifiers of different tags.
  • the first identifier is used to determine the target server of the first tag; the second network element determines the target server of the first tag according to the second tag filter.
  • the first operation instruction and the first identifier are used to obtain the identifier of the first tag, and the second tag filter is matched based on the identifier of the first tag to obtain the information of the first tag; the second network element sends the second message , the second message includes the information of the first tag and the first identification.
  • the first network element may be a first communication device, such as a terminal device with a reader/writer function
  • the second network element may also be an access and access and mobility management function AMF network element.
  • the second network element receives the first message, which includes the first operation instruction, the second tag filter, and the first identification, and then the second network element can execute the tag according to the first operation instruction. Operation, obtain the identity of the first label from the identity of at least one label, and match the second label filter based on the identity of the first label, so that the information of the first label can be accurately obtained, and the information of the first label can be sent to the first network element.
  • the information of the first tag and the first identification further enable the first network element to quickly and accurately determine the target server of the first tag based on the first identification.
  • the second network element receiving the first message includes: the second network element receives the first message from the mobility management The functional network element receives the first message; the second network element sends the second message, including: the second network element sends the second message to the mobility management functional network element.
  • the second network element is a first communication device, such as a terminal device with a reader/writer function.
  • the terminal device may receive the first message from the NEF network element (i.e., the first network element) through the AMF network element (i.e., the mobility management function network element). After determining the first label based on the first message, the terminal device may send a message to the NEF network element (i.e., the first network element).
  • the AMF network element sends the information of the first label, and then the AMF network element sends the information of the first label to the NEF network element.
  • the second network element can effectively receive the above-mentioned first message from the mobility management function network element, and after determining the first label, send the first message containing the first label to the mobility management function network element. Second message of information.
  • the second network element receives the first message from the first network element; the second network element sends the second message, including: the second network element sends the first message to the first network element. Two messages.
  • the second network element is an AMF network element (i.e., mobility management function network element).
  • the AMF network element receives the first message from the NEF network element (i.e., the first network element).
  • the AMF network element is based on the first message, and after determining the first label, send the information of the first label to the NEF network element.
  • the second network element can first obtain all tag information from the first communication device (such as a terminal device with a reader/writer function), including the first A label's information.
  • the first communication device such as a terminal device with a reader/writer function
  • the second network element directly receives the first message from the first network element, and after determining the first label based on the first message, sends the second network element containing the information of the first label to the first network element. information.
  • the present application provides a communication device, which can be applied to a first communication device and has the function of realizing the above-mentioned first aspect or any possible implementation manner of the above-mentioned first aspect; or, the communication device
  • the device can be applied to the first user plane functional network element and has the function of implementing the above second aspect or the method in any possible design of the above second aspect.
  • the device may include: a receiving unit, a processing unit and a sending unit.
  • the present application also provides a communication device, which can be applied to the first network element and has the function of realizing the above third aspect or any possible implementation manner of the above third aspect; or, the communication device
  • the device may be applied to the second network element and has the function of implementing the method in the fourth aspect or any possible design of the fourth aspect.
  • the device may include: a receiving unit, a processing unit and a sending unit.
  • the present application also provides a communication device that can be applied to a first communication device.
  • the communication device includes a processor for implementing the above-mentioned first aspect or any possible implementation of the above-mentioned first aspect. or, the communication device can be applied to the first user plane functional network element to implement the function of the method in the above-mentioned second aspect or any possible design of the above-mentioned second aspect.
  • the communication device further includes a transceiver for implementing the communication function of the communication device.
  • this application also provides another communication device, which can be applied to the first network element.
  • the communication device includes a processor for implementing the above third aspect or any one of the possible methods of the above third aspect.
  • the function of the embodiment; or, the communication device can be applied to the second network element to implement the function of the method in the above-mentioned fourth aspect or any possible design of the above-mentioned fourth aspect.
  • the communication device further includes a transceiver for implementing the communication function of the communication device.
  • the present application also provides a communication system, which includes a first communication device (such as a terminal device) for performing the method provided by the first aspect, and a third communication device (such as a terminal device) used for performing the method provided by the second aspect.
  • a communication system which includes a first communication device (such as a terminal device) for performing the method provided by the first aspect, and a third communication device (such as a terminal device) used for performing the method provided by the second aspect.
  • a user plane function network is a communication system, which includes a first communication device (such as a terminal device) for performing the method provided by the first aspect, and a third communication device (such as a terminal device) used for performing the method provided by the second aspect.
  • the present application also provides a communication system, which includes a first network element (such as a network capability opening function network element) for performing the method provided in the third aspect, and a first network element (such as a network capability opening function network element) for performing the method provided in the fourth aspect.
  • a first network element such as a network capability opening function network element
  • a first network element such as a network capability opening function network element
  • the second network element the first communication device, such as a terminal device with reading and writing functions, or an access and mobility function management network element.
  • embodiments of the present application further provide a computer storage medium, which stores a software program.
  • the software program can implement the first aspect or any of the above.
  • a method provided by a possible implementation manner, or the method provided by the above second aspect or any one of the possible implementation manners is implemented; or the software program can realize the above mentioned third aspect when read and executed by one or more processors.
  • embodiments of the present application also provide a computer program product containing instructions that, when run on a computer, cause the method provided by the above-mentioned first aspect or any of the possible implementations to be executed, or cause the above-mentioned
  • the method provided by the second aspect or any possible implementation manner thereof is executed; or when it is run on a computer, the method provided by the third aspect or any possible implementation manner thereof is executed, or the fourth aspect mentioned above is caused.
  • the method provided by the aspect or any possible implementation manner thereof is performed.
  • embodiments of the present application further provide a chip system.
  • the chip system includes a processor for supporting the first communication device to implement the functions involved in the above-mentioned first aspect; or for supporting the first user plane function.
  • the network element implements the functions involved in the above-mentioned second aspect; or is used to support the first network element to implement the functions involved in the above-mentioned third aspect; or is used to support the second network element to implement the functions involved in the above-mentioned fourth aspect. .
  • the chip system further includes a memory, and the memory is used to save necessary program instructions and data executed by the loading device.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • Figure 1 is a schematic diagram of tag reading and writing for a passive or semi-passive Internet of Things
  • FIG 2 is a schematic diagram of the process of a reader/writer performing inventory on tags (such as P-IoT Tag);
  • Figure 3A is a schematic diagram of the transmission path of the first tag information
  • Figure 3B is a schematic diagram of the transmission path of the second tag information
  • Figure 3C is a schematic diagram of the transmission path of the third tag information
  • Figure 4 is a schematic diagram of a network architecture provided by an embodiment of the present application.
  • Figure 5A is a schematic flow chart of a communication method provided by an embodiment of the present application.
  • Figure 5B is a schematic flow chart of another communication method provided by an embodiment of the present application.
  • Figure 6 is a schematic flow chart of another communication method provided by an embodiment of the present application.
  • Figure 7 is a schematic flow chart of the first embodiment provided by the embodiment of the present application.
  • Figure 8 is a schematic flow chart of the second embodiment provided by the embodiment of the present application.
  • Figure 9 is a schematic flow diagram of the third embodiment provided by the embodiment of the present application.
  • Figure 10 is a schematic flow diagram of the fourth embodiment provided by the embodiment of the present application.
  • Figure 11 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • Figure 12 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • FIG. 13 is a schematic structural diagram of a chip device provided by an embodiment of the present application.
  • the embodiments of the present application provide a communication method and device, wherein the method and the device are based on the same or similar technical concepts. Since the principles of the method and the device to solve problems are similar, the implementation of the method and the device can be referred to each other. No longer.
  • IoT technology can include passive or semi-passive Internet of things (P-IoT) technology, that is, the nodes of the network can obtain energy from the environment to support the perception, transmission and distribution of data in the network Formula calculations, etc.
  • P-IoT passive or semi-passive Internet of things
  • the passive or semi-passive IoT architecture it usually includes passive or semi-passive tags, readers and servers.
  • the readers can read the tags (or RF card) reads and writes to identify the tag (or RF card) and interact with the tag (or RF card) for information and data.
  • Tags can also store electrical energy by obtaining solar energy and other methods, and actively send a signal of a certain frequency to the reader/writer.
  • the reader/writer receives the information carried by the signal and decodes it, and further decodes the decoded information.
  • the information is sent to the central information system for corresponding data processing.
  • FIG. 1 shows a schematic diagram of tag reading and writing for passive or semi-passive IoT, which may include the following steps:
  • P-IoT APP The P-IoT application (P-IoT APP) sends inventory/access rules to the reader (Reader).
  • the reader/writer receives the inventory/access rule.
  • the inventory/access rule can be: inventory once every hour, and obtain information about the storage areas of tag 1, tag 2, and tag 3.
  • S102 The reader/writer performs inventory on the tag (such as P-IoT Tag) and obtains the tag's identity.
  • tag such as P-IoT Tag
  • the reader/writer performs inventory on the tags according to the received inventory/access rules, for example, performs an inventory of the tags to be accessed every hour, and obtains the identification of the tags to be accessed.
  • the process of the reader/writer taking inventory of tags can be understood as the process of the reader/writer establishing connection and interaction with the tag (such as P-IoT Tag), and obtaining each other's information.
  • the tag such as P-IoT Tag
  • each tag has a corresponding identification, including but not limited to electronic product code (EPC) and tag identifier (TID).
  • EPC electronic product code
  • TID tag identifier
  • the tag will send its EPC or TID to the reader/writer, so that the reader/writer can learn which tags are within its coverage and report them to the middleware and server.
  • S103 The reader/writer (Reader) performs tag access to the P-IoT Tag.
  • the tag to be accessed executes the tag access to the reader/writer (Reader) to complete the process of tag access so that the subsequent reader/writer (Reader) can obtain the accessed tag. Label information.
  • S104 The reader feeds back the inventory information and tag access information to the P-IoT APP.
  • the reader feeds back the tag inventory information/tag access information to the P-IoT APP.
  • S201 The reader/writer sends a Select command to the P-IoT Tag.
  • P-IoT Tag receives the Select command.
  • the reader/writer will generate a Select command, and then send the Select command to the P-IoT Tag.
  • the inventory command includes the range of tags, such as EPC/TID within certain specific ranges.
  • the tag receives (monitors) the Select command, it takes stock of whether it has data in the tag range that needs to be judged in the Select command. If it belongs, it will continue to monitor subsequent Query commands. If it does not belong, the tag will not perform the following steps (that is, it will not take any action).
  • S202 The reader/writer sends the Query command to the P-IoT Tag.
  • P-IoT Tag when P-IoT Tag receives a valid Query command, it will generate a random number.
  • a tag with a random number of 0 will feedback a temporary password RN-16, which is a 16-bit random number, to the reader.
  • S204 The reader/writer sends an acknowledgment (ACK) command to the P-IoT Tag.
  • ACK acknowledgment
  • the reader/writer When the reader/writer receives the random number sent from the tag, it will send an ACK command to the tag, which contains the random number (RN16) just received.
  • P-IoT Tag verifies whether the random number in the ACK command is correct.
  • P-IoT Tag sends the EPC code to the reader.
  • the P-IoT Tag After the P-IoT Tag sends its own EPC code to the reader, it enters a short sleep state.
  • the reader/writer After the reader/writer receives the EPC code of the tag, it completes the inventory of the tag.
  • the reader/writer will continue to send the QueryRep command, and 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 are counted.
  • the UE when used as a reader/writer, it supports passive or semi-passive IoT to perform the reading and writing process, which can mainly include the following transmission paths.
  • the first transmission method As shown in Figure 3A, the reader/writer performs tag management, and directly establishes a user plane connection with the enterprise server through the reader/writer, and then the tag information (or instructions) can be established through the reader/writer.
  • User plane connection implements transmission.
  • the second transmission path As shown in Figure 3B, the UPF network element performs tag management and establishes a user plane connection with the UPF network element through a reader/writer, and the UPF network element establishes a user plane connection with the enterprise server to read and write tags.
  • the tag information (or instructions) read and written by the device can be transmitted through the above user plane connection.
  • the third transmission path 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, and the AMF
  • the network element or control plane (CP) network element) performs label management and can send label information to the application server through the NEF network element.
  • the reader/writer may be shared by multiple enterprises and does not involve providing enterprise information through the tag, so the reader/writer cannot directly communicate with the target.
  • the tag's own enterprise server establishes a user plane channel.
  • the reader/writer does not provide enterprise information for different tags and implements different routing strategies, making it impossible for the network to identify the enterprise to which the tag belongs and provide different communication services for different enterprises.
  • this application proposes a communication method, which method includes: a first communication device receives a first request, the first The request instructs the first communication device to obtain the information of the first tag, and the information of the first tag includes the identification of the first tag; then, the first communication device obtains the information of the first tag according to the first request; secondly , the first communication device determines a first communication session, and the first communication session is used to transmit the information of the first tag; finally, the first communication device sends the information of the first tag through the first communication session.
  • the first communication device determines the corresponding first communication session for the information of the first tag, thereby ensuring that the first communication device passes the The first communication session can effectively and accurately transmit the information of the first tag.
  • This application solution can be applied to the 5G system architecture, and can also be applied to but not limited to long term evolution (LTE) communication systems, as well as various wireless communication systems that will evolve in the future.
  • LTE long term evolution
  • FIG. 4 shows a schematic diagram of a network architecture applicable to a communication method provided by an embodiment of the present application.
  • the network architecture may include an access network and a core network. Terminal equipment is connected to the data network (DN) through the access network and core network.
  • DN data network
  • the terminal device can be a user equipment (UE), a mobile station, a mobile terminal, an application client, etc.
  • Terminal devices can be widely used in various scenarios, such as device-to-device (D2D), vehicle to everything (V2X) communication, machine-type communication (MTC), and the Internet of Things (internet of things, IOT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart wear, smart transportation, smart city, etc.
  • Terminal devices can be mobile phones, tablets, computers with wireless transceiver functions, wearable devices, vehicles, urban air vehicles (such as drones, helicopters, etc.), ships, robots, robotic arms, smart home devices, etc.
  • a UE is used as an example of a terminal device for description. The UE appearing anywhere subsequently can also be replaced with a terminal device or other examples of a terminal device.
  • the access network is used to implement access-related functions. It can provide network access functions for authorized users in a specific area, and can determine transmission links of different qualities to transmit user data based on user levels, business needs, etc.
  • the access network forwards control signals and user data between the UE and the core network.
  • the access network may include access network equipment, which may be equipment that provides access for UEs, and may include wireless access network (radio access network, RAN) equipment and wired access network equipment.
  • RAN equipment is mainly responsible for wireless 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 called small stations), relay stations, access points, balloon stations, etc.
  • the names of equipment with base station functions may be different.
  • RAN next-generation Node base station
  • gNB next-generation Node base station
  • LTE long term evolution
  • eNB evolved NodeB
  • the access network equipment and UE can be fixed-positioned or mobile. Access network equipment and UE can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; they can also be deployed on aircraft, balloons and satellites in the sky.
  • the embodiments of this application do not limit the application scenarios of access network equipment and UE.
  • the core network is responsible for maintaining the subscription data of the mobile network and providing functions such as session management, mobility management, policy management, and security authentication for UEs.
  • 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 storage function ( network repository function, NRF) network element, authentication server function (AUSF) network element, network exposure function (NEF) network element, user plane function (UPF) network element, network data analysis function network Network Data Analytics Function (NWDAF) network element.
  • AF application function
  • UDM unified data management
  • UDR unified data repository
  • PCF policy control function
  • SMF session management function
  • AMF access and mobility management function
  • NRF network repository function
  • AUSF authentication server function
  • NEF network exposure function
  • UPF user plane function
  • the AMF network element is mainly responsible for mobility management in mobile networks, such as user location update, user registration network, user switching, etc.
  • the SMF network element is mainly responsible for session management in mobile networks, such as session establishment, modification, and release. Specific functions include assigning Internet Protocol (IP) addresses to users, selecting UPF that provides message forwarding functions, etc.
  • IP Internet Protocol
  • 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 device. It can also receive user data from the UE through the access network device and forward it to the data network.
  • UDM network elements include functions such as execution and management of contract data and user access authorization.
  • the UDR network element includes access functions for executing contract data, policy data, application data and other types of data.
  • NEF network elements are mainly used to support the opening of capabilities and events.
  • AF network element transmits the requirements from the application side to the network side, such as QoS requirements or user status event subscriptions.
  • AF can be a third-party functional entity or an application service deployed by an operator, such as IP Multimedia Subsystem (IMS) voice call service.
  • IMS IP Multimedia Subsystem
  • the PCF network element mainly supports providing a unified policy framework to control network behavior, provides policy rules to the control layer network functions, and is also responsible for obtaining user subscription information related to policy decisions.
  • PCF network elements can provide policies, such as QoS policies, slice selection policies, etc., to AMF network elements and SMF network elements.
  • NRF network elements can be used to provide network element discovery functions and provide network element information corresponding to network element types based on requests from other network elements.
  • NRF also provides network element management services, such as network element registration, update, de-registration, network element status subscription and push, etc.
  • the AUSF network element is responsible for authenticating the UE and verifying the legitimacy of the UE.
  • NWDAF network elements provide functions such as network data collection and analysis based on technologies such as big data and artificial intelligence.
  • DN on which a variety of services can be deployed, can provide data and/or voice services to UEs.
  • DN is a private network of a smart factory.
  • the sensors installed in the workshop of the smart factory can be UEs.
  • the control server of the sensor is deployed in the DN, and the control server can provide services for the sensor.
  • the sensor can communicate with the control server, obtain instructions from the control server, and transmit the collected sensor data to the control server according to the instructions.
  • DN is the internal office network of a company.
  • the mobile phones or computers of employees of the company can be UE.
  • the employees' mobile phones or computers can access information and data resources on the company's internal office network.
  • 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
  • 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
  • Nausf, Nnef, Nnrf, Namf, Npcf, Nsmf, Nudm, Nudr, Naf, and Nnwdaf are the service interfaces provided by the above-mentioned AUSF, NEF, NRF, AMF, PCF, SMF, UDM, UDR, AF, and NWDAF respectively. Used to call corresponding service operations.
  • N1, N2, N3, N4 and N6 are interface serial numbers. The meanings of these interface serial numbers are as follows:
  • N1 The interface between AMF and UE can be used to transmit non-access stratum (NAS) signaling (such as QoS rules from AMF) to UE.
  • NAS non-access stratum
  • N2 The interface between AMF and access network equipment can be used to transmit wireless data from the core network side to the access network equipment. Lines carry control information, etc.
  • N3 The interface between the access network equipment and UPF, mainly used to transmit uplink and downlink user plane data between the access network equipment and UPF.
  • N4 The interface between SMF and UPF can be used to transfer information between the control plane and the user plane, including controlling the delivery of forwarding rules, QoS rules, traffic statistics rules, etc. for the user plane, as well as user plane information. Report.
  • N6 The interface between UPF and DN, used to transmit uplink and downlink user data flows between UPF and DN.
  • the above network elements or functions can be network elements in hardware devices, software functions running on dedicated hardware, or virtualization functions instantiated on a platform (for example, a cloud platform).
  • a platform for example, a cloud platform.
  • the above network element or function can be implemented by one device, can be implemented by multiple devices, or can be a functional module in one device, which is not specifically limited in the embodiments of this application.
  • the embodiment of the present application provides a communication method, which method is applicable to but is not limited to the network architecture of Figure 4, and the method can be executed by the network element involved in this application, or by the chip corresponding to the involved network element,
  • the network elements in this application may be physical network elements or virtual network elements. This application does not specifically limit the form of the network elements involved.
  • the device mainly used to perform tag identification is called the first communication device.
  • the first communication device can be a reader (or a controller or chip corresponding to the reader), or it can be a reader.
  • the terminal device (or the controller or chip corresponding to the terminal device) that establishes a communication connection.
  • the terminal device may be, but is not limited to, a computer, a mobile phone, a tablet, or other devices that can establish a communication connection with the reader.
  • the ordinal numbers such as “first” and “second” mentioned below are used to distinguish multiple objects for ease of description, and are not used to limit the order, timing, and sequence of multiple objects. Priority or importance. This application does not limit the specific forms of the first communication device and the involved network elements in this embodiment.
  • FIG. 5A shows a flow chart of a communication method provided by an embodiment of the present application, which may specifically include the following steps:
  • S501A The first communication device receives the first request from the target server.
  • the first request instructs the first communication device to obtain information of a first tag
  • the first tag may include a group of tags that comply with a certain inventory rule.
  • the first tag may be a tag within a certain area.
  • the first tag may also be a tag with a specific tag identifier, where the specific tag identifier may be included in the inventory rule.
  • the first request may be a data transmission message sent through the user plane, or a non-access layer message sent through the control plane, such as a downlink non-access layer transmission message.
  • the first communication device may be a reader/writer, such as a UE.
  • the application server such as a PIOT server
  • the application server can send a first request to the UE.
  • the first request instructs the UE to obtain the information of the first tag.
  • the information of the first tag includes the first tag.
  • the identification of the tag (such as EPC, TID), correspondingly, the UE receives the first request from the application server.
  • the first communication device before receiving the first request, further includes a process of performing a tag inventory, or, after receiving the first request and before determining the first communication session ( Or after step S501A and before step S502A), the process of tag inventory is also performed, that is, the first request message also contains
  • the first communication device performs instruction information required for tag inventory, where the instruction information may include but is not limited to one or more of tag inventory range, tag type, tag belonging enterprise, and tag belonging operator.
  • the specific process of tag inventory please refer to the process shown in Figure 2 above, and will not be described in detail here.
  • the first tag ie, the target tag obtained by the first request information indicating that the first communication device can access the first communication device, and further, the first communication device can effectively obtain Information about the first tag.
  • the first communication device obtains the information of the first tag according to the first request, and the information of the first tag includes the identification of the first tag.
  • the first communication device determines a first communication session according to the identification of the first tag.
  • the first communication session is used to transmit information of the first tag.
  • the first communication device determines the first communication session based on the identification of the first tag, including: the first communication device determines from at least one communication session based on the identification of the first tag and the first routing policy information.
  • the first communication session and the first routing policy information include a corresponding relationship between the identifier of the first label and the identifier of the first communication session.
  • the first routing policy information in this application can be an improved user equipment routing policy (URSP policy), that is, the identification information about the label is added to the existing URSP policy (routing policy), so that it can also be based on the identification of the label. , select the communication session corresponding to the information for transmitting the tag.
  • URSP policy user equipment routing policy
  • the above-mentioned first routing policy information may refer to Table 1 in the following specific embodiment one.
  • the first routing policy information may also include a corresponding relationship between the identification of the first label and the address information and/or port number information of the target server. Therefore, the first communication device may also configure the first routing policy information according to the first routing policy information.
  • the corresponding relationship contained in the first tag is determined to determine the address information and/or port number information of the target server corresponding to the first tag. Further, based on the corresponding relationship between the address information and/or port number information of the server and the communication session, determine The first communication session corresponding to the address information and/or port number information of the target server. This application does not limit the specific manner in which the first communication device determines the first communication session based on the first routing policy information.
  • the method 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 communication session. Routing policy information, each routing policy information includes a corresponding relationship between a corresponding label and an identifier of a communication session.
  • the first communication device establishing the first communication session may include but is not limited to the following methods:
  • the first communication device establishes a first communication session, including: the first communication device sends a first session request message, the first session request message includes first indication information, and the first indication information indicates the first tag.
  • Home enterprise information the first communication device receives a first response message, the first response message is used to respond to the first session request message, the first response message includes the first target address information, and/or the 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 device is determined based on the first target address information, and/or the first
  • the port number information is used to establish the first communication session; the first target address information, and/or the first port number information is used to determine the target server, and the target server is the server of the home enterprise.
  • the above-mentioned first indication information may be the enterprise's data network name DNN, or the first tag belonging enterprise information indicated by the first indication information may be the enterprise information corresponding to the DNN.
  • the enterprise information to which the first tag belongs can also be directly carried in the first session request message and sent by the first communication device.
  • the first indication information may be used to indicate the first tag's belonging enterprise information, and the first communication device may send the first session request including the first indication information. information.
  • the above implementation method 1 can be implemented based on the first transmission path shown in FIG. 3A , and the first communication device can be regarded as a UE (reader/writer).
  • the UE sends a PDU session establishment request message (equivalent to a first session request message) to the AMF network element.
  • the first session request message contains first indication information used to indicate the home enterprise information of the first label.
  • the AMF network After receiving the PDU session establishment request message, the AMF network element selects the appropriate SMF network element and sends the PDU session creation session context request message to the SMF network element. Then, the AMF network element receives the PDU session creation session context response message from the SMF network element. And receives the N1N2 message from the SMF network element.
  • the N1N2 message carries the target PIOT server address (equivalent to the first target address information) and port number information (equivalent to the first port number information).
  • the SMF network element sends the N2 PDU session to the RAN.
  • Request message (carrying the target PIOT server address and port number information)
  • the RAN establishes air interface resources with the UE and sends a NAS message (equivalent to the first response message) to the UE.
  • the NAS message carries the target PIOT server address and port number information.
  • 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.
  • the first communication device establishes a first communication session, including: the first communication device sends a second session request message, the second session request message includes second indication information, and the second indication information indicates the first tag.
  • Home enterprise information the first communication device receives a second response message, the second response message is used to respond to the second session request message, the second response message contains second target address information, and/or a 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 device is determined based on the second target address information, and/or the second port number information.
  • number information to establish a first communication session; the second target address information and/or the second port number information are used to determine the first user plane functional network element, which is provided by the home enterprise. User plane network element of the service.
  • the above second implementation method can be implemented based on the second transmission path shown in Figure 3B.
  • the first communication device can be regarded as a UE (reader/writer), and the first user plane functional network element can be a UPF network element.
  • the first case there is only one user plane functional network element used to transmit label information, that is, the first user plane functional network element is a public user plane functional network element.
  • the second target address information and/or the second port number information received by the first communication device are the same, and the second target address information, and /Or the second port number information is used to indicate the first user plane functional network element.
  • Each target address information and/or port number information is based on the corresponding label belonging enterprise information ( Or the indication information used to indicate the corresponding tag belonging enterprise information), each target address information and/or port number information is used to indicate a corresponding server.
  • the enterprise information to which the tag belongs or the indication information indicating the enterprise information to which the tag belongs may be the data network name DNN of the enterprise.
  • 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 the UPF1 network element (equivalent to the first user plane functional network element), and the UPF1
  • the address information of the network element and/or the corresponding port number information are determined based on the DNN of the enterprise to which the first label belongs or based on the indication information indicating the DNN of the enterprise to which the first label belongs.
  • the UE1 establishes a first PDU session connection (equivalent to establishing a first communication session) with the UPF1 network element based on the address information and/or the corresponding port number information of the UPF1 network element.
  • UE1 can refer to the establishment of PDU sessions by UE1 for the enterprise where other tags belong to the enterprise where the first tag belongs.
  • the first PDU session is implemented, that is, it is a PDU session between UE1 and the UPF1 network element.
  • the second target address information received by the first communication device is the same every time and is used to indicate the first user plane function. network element, but the received second port number information on the first user plane functional network element may be different. Therefore, the first communication device can also establish a corresponding communication session based on each second port number information.
  • the second case There are multiple user plane functional network elements used to transmit tag information.
  • the information of each tag belonging to the enterprise corresponds to one user plane functional network element.
  • the information of the first tag belonging to the enterprise corresponds to the first user plane function. network element.
  • the second target address information and/or the second port number information received by the first communication device are different each time.
  • Each second target address information, and/or Or the second port number information is used to indicate a corresponding user plane functional network element.
  • the first communication device can determine the second target address information corresponding to the first tag and/or the second port number information based on the enhanced URSP policy. , thereby determining the first communication session.
  • UE1 obtains the address information and/or the corresponding port number information of the UPF1 network element, the address information and/or the corresponding port number information of the UPF2 network element, where the address information and/or the corresponding port number of the UPF1 network element
  • the information is determined based on the DNN_(1) of the enterprise to which tag 1 belongs.
  • the address information and/or corresponding port number information of the UPF2 network element is determined based on the DNN_(1) of the enterprise to which tag 2 belongs.
  • UE1 can establish a connection with the UPF1 network element (that is, establish a first communication session) based on the address information and/or corresponding port number information of the UPF1 network element, and UE1 can establish a connection with the UPF1 network element based on the address information and/or corresponding port number information of the UPF2 network element. Establish a connection with the UPF2 network element.
  • the third case There are multiple user plane functional network elements used to transmit label information, which at least include: one user plane functional network element corresponds to the information of the label belonging to the enterprise, and one user plane functional network element corresponds to multiple labels Information belonging to the enterprise.
  • One user plane functional network element corresponds to the information of multiple tags belonging to the enterprise. You can refer to the method in the first case above. One user plane functional network element corresponds to the information of one tag belonging to the enterprise. You can refer to the method in the second case above. This is not the case. Let’s go into more detail.
  • 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 is used for the third
  • the information of the first label is transmitted between a communication device and the first user plane functional network element.
  • the first communication device sends the information of the first tag through the first communication session including two transmission paths: the first transmission path (ie, the transmission path shown in FIG. 3A).
  • the first transmission path ie, the transmission path shown in FIG. 3A
  • the second transmission path i.e., the transmission path shown in Figure 3B
  • S504A The first communication device sends the information of the first tag to the target server through the first communication session.
  • the information of the first tag may be the data of the first identification.
  • the information of the first tag may also only include the identification of the first tag, which is not limited in this application.
  • the first communication device sends the information of the first tag to the target server through the first communication session.
  • the information of the first tag may include the identification of the first tag.
  • the first communication device can accurately send the information of the first tag to the target server directly through the first communication session.
  • the first communication device can be implemented by referring to the method in which the first communication device sends the information about the first tag to the target server, which will not be described in detail here.
  • S505A The first communication device sends the information of the first label to the first user plane functional network element through the first communication session. interest.
  • the first communication device sends the information of the first tag to the first user plane functional network element through the first communication session.
  • the first user plane functional network element receives the information of the first label and the first information, and the first information is used to determine the target server of the first label.
  • the first user plane functional network element determines the target server of the first label based on the first information.
  • the first user plane functional network element receives the first information, including: the first user plane functional network element receives an N4 session request message, the N4 session request message includes first information, and the first information indicates that the A tag filter, the first tag filter is used to match the corresponding server according to the identification of the tag.
  • the first information may indicate the first tag filter, and the first information may also be the first tag filter, which is not specifically limited in this application.
  • the first user plane functional network element determines the target server of the first label based on the first information, including: the first user plane functional network element determines the first label filter based on the first information; The first user plane functional network element uses the first label filter to match the target server of the first label based on the identification of the first label.
  • the first user plane functional network element receives the information of the first label from the first communication device; the first user plane functional network element receives the first information, including: the first user plane functional network element receives N4 Session request message, the N4 session request message includes first information, the first information indicates the address information of the first communication device and/or the third port number information through which the first communication device sends the information of the first tag.
  • the first information may be used to indicate the address information of the first communication device and/or the third port number information for the first communication device to send the information of the first tag, and the first information may also be the first communication device.
  • the address information of the communication device and/or the third port number information used by the first communication device to send the information of the first tag are not specifically limited in this application.
  • the first user plane functional network element determines the target server of the first label based on the first information, including: the first user plane functional network element determines the address information of the first communication device based on the first information. and/or the third port number information; the first user plane functional network element determines the target server of the first label based on the address information of the first communication device, the third port number information, and the first mapping information;
  • the first mapping information includes a correspondence between the address information and/or port number information of the first communication device and the identity of the server.
  • the first user plane functional network element receives the first information, including: the first user plane functional network element receives an N4 session request message, the N4 session request message includes first information, and the first information indicates that the The fourth port number information of the first user plane functional network element is used to receive the information of the first label.
  • the first information may be used to indicate the fourth port number information on the first user plane functional network element to receive the information of the first label.
  • the first information may also be received on the first user plane functional network element.
  • the fourth port number information of the first tag information is not specifically limited in this application.
  • the first user plane functional network element determines the target server of the first label based on the first information, including: the first user plane functional network element determines the first user plane functional network element based on the first information.
  • the second mapping information includes the corresponding relationship between the port number information on the first user plane functional network element and the identifier of the server.
  • the first user plane functional network element receives the first information, including: the first user plane functional network element receives an N4 session request message, the N4 session request message includes the first information, and the first information indicates 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 are based on the second
  • the second indication information indicates 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.
  • 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 for receiving the information of the first tag.
  • the first information may also be the address information of the target server.
  • the address information and/or the fifth port number information on the target server used to receive the information of the first tag.
  • the first user plane functional network element determines the target server of the first label based on the first information, including: the first user plane functional network element determines the address information of the target server based on the first information and /or the fifth port number information; the first user plane functional network element determines the target server based on the address information of the target server and/or the fifth port number information.
  • S508A The first user plane functional network element sends the first label information to the target server.
  • each user plane functional network element is configured with the address information and/or the third port number of the first communication device.
  • the first user plane functional network element obtains the information of the first tag from the first communication device according to the address information and/or the 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.
  • the above-mentioned "address information” can be understood as information used to determine the address
  • "port number information” can be understood as information used to determine the port number.
  • the “address information” can be referred to as "address” for short.
  • the two can have the same meaning
  • the "port number information” can also be referred to as the "port number” for short, and the two can also have the same meaning.
  • the first communication device can establish a communication session with the corresponding server based on the information of the enterprise to which the tag belongs, so that after receiving the information of the first tag, the first communication device The first communication session for transmitting the information of the first tag can be accurately determined according to the first routing policy information including the identification of the tag, and then the first communication device can effectively and accurately transmit the first communication session through the first communication session.
  • a tag's information is transmitted to the target server.
  • the first communication device can also determine a first communication session of the first tag according to the first routing policy information, and the 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 information of the first tag to the corresponding user plane functional network element through the first communication session, and then the user plane functional network element sends the information of the first tag effectively and accurately sent to the target server.
  • FIG. 5B shows a flow chart of another communication method provided by an embodiment of the present application, which may specifically include the following steps:
  • the first network element sends a first message to the second network element.
  • the first message includes the first operation instruction, the second label filter, and the first identifier.
  • the first operation instruction is used to instruct the second network element to select from the identification of at least one tag according to the first identification.
  • the identification of the first label is obtained, the second label filter is used to determine the information of the corresponding label according to the identification of the label, and the first identification is used to determine the target server of the first label.
  • the first network element sends the first message to the second network element.
  • the second network element receives the first message from the first network element.
  • the first network element is a network capability opening function network element (NEF network element)
  • the second network element is a mobility management function network element (AMF network element), that is, the NEF network element sends to the AMF network element
  • the first message is received directly by the AMF network element from the NEF network element.
  • the first network element sending the first message to the second network element includes: the first network element sending the first message to the mobility management function network element.
  • the second network element receives the content in the first message from the mobility management function network element.
  • the content in the first message may include a first operation instruction and a second tag filter.
  • the above-mentioned first message may be an AMF communication service message, or an AMF event open service message, or an AMF non-IP data transmission service message, or other messages provided by AMF through a service-oriented interface.
  • This application does not Make specific limitations.
  • the content in the above-mentioned first message can be obtained by forwarding the above-mentioned first message to the second network element through the mobility management function network element, or can also be obtained by sending a third message to the second network element through the mobility management function network element.
  • message such as a downstream NAS transmission message
  • the third message carries the content in the above-mentioned first message, such as the first operation instruction and the second label filter.
  • the first network element is a network capability opening function network element (NEF network element)
  • 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 communicates with the AMF network element. Send a first message, the first message including the first operation instruction, the second tag filter and the first identification, and then the AMF network element sends a third message to the UE, the third message includes the first operation instruction and the first identification.
  • the second tag filter is a network capability opening function network element
  • the second network element obtains 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 performs a tag operation, such as the above-mentioned tag inventory process, to obtain the identity of at least one tag, and obtains the first tag from the identity of the at least one tag according to the first identity.
  • a tag operation such as the above-mentioned tag inventory process
  • the second network element obtains the information of the first label through matching with the second label filter.
  • the second network element may also first determine the range of the first tag based on the second tag filter and perform a tag operation according to the first operation instruction to obtain the information of the first tag (including the identification of the first tag) .
  • the second network element is a first communication device with a reader/writer function
  • the first communication device executes step S502B.
  • the second network element is a mobility management function network element
  • the mobility management function network element executes step S502B.
  • 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 obtains the first communication device from the first communication device with a reader/writer function.
  • the information of the tags, or the second network element obtains the information of all tags from the first communication device equipped with the reader/writer function, and the information of all tags includes the information of the first tag.
  • S503B The second network element sends a second message to the first network element, where the second message includes the information of the first label and the first identifier.
  • the first identification is used to determine the target server of the first label.
  • the first network element receives the second message.
  • the second network element based on the situation that the second network element receives the first message from the first network element, the second network element The network element sends the second message to the first network element.
  • the second network element sends the second message to the first network element, including: the second network element The second message is sent to the mobility management function network element; the mobility management function network element then sends the two messages to the first network element.
  • the second network element sends a fourth message to the mobility management function network element.
  • the fourth message includes the information of the first label
  • the mobility management function network element then sends a second message to the first network element.
  • message, the second message includes the information of the first tag and the first identification.
  • the second network element is a UE
  • the first network element is an 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 label
  • the AMF The 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 label and the first identification.
  • the first network element determines the target server of the first label based on the first identifier.
  • the first network element determines the target server of the first label based on the first identification, including: the first network element determines the first label based on the first identification and the first corresponding relationship.
  • the target server wherein the first corresponding relationship includes the corresponding relationship between the first identification and the target server.
  • the first network element receives at least one server reception control information, and each control information includes a first operation identifier and a second label filter.
  • the first network element can generate a first identification based on the control information of at least one target server, and establish a correspondence between the first identification and the server, that is, a first correspondence.
  • the first correspondence can be stored in the first Local to the network element, or stored in other communicable network elements or devices, this application does not specifically limit this.
  • the first identification may be information used to identify the target server, such as the target server address, target server identification, etc.
  • the first identifier may be the identifier of the first message, or the first identifier may be the identifier of the first operation instruction, and the identifier of the first message or the identifier of the first operation instruction is consistent with the target server.
  • this application does not specifically limit the first identifier.
  • S505B The first network element sends the first label information to the target server.
  • the second network element in this implementation can be either a first communication device (such as a UE) with a reader function, or a mobility management device.
  • Functional network element that is, AMF network element.
  • the second network element first receives the first message from the first network element (ie, the network capability opening function network element) through the mobility management function network element, and then, the second network element
  • the second network element may determine the first label based on the first operation instruction and the second label filter in the first message, and then send the information including the first label and the third label to the first network element through the mobility management function network element.
  • a second message of identification and finally, the first network element sends the information of the first label to the target server.
  • the second network element is a mobility management function network element, it can directly receive the first message from the first network element (ie, the network capability opening function network element), and based on the first operation instruction in the first message, The second tag filter determines the first tag, and then carries the information and the first identification of the first tag read and written by the first communication device in a second message and sends it to the first network element.
  • the first network element sends the message to the first network element according to the The first identification accurately sends the information of the first tag to the target server.
  • Embodiment 1 is a specific example of an implementation mode of the method shown in FIG. 5A.
  • Embodiment The second is a specific example of another implementation mode in the method shown in Figure 5A (the first situation in the above step S502A).
  • the second embodiment is based on Figure 5A A specific example of another implementation in the method shown in 5A (the second case in step S502A above).
  • Embodiment 4 and Embodiment 5 are specific examples of another communication method shown in FIG. 5B.
  • the UE performs tag management, and the UE (reader/writer) ) Establish a user plane session and transmit tag information, as shown in Figure 6.
  • the specific process is as follows:
  • the specific registration process of the UE can be implemented with reference to the existing technology and will not be described here.
  • the UE i.e., the reader/writer
  • the AMF network element receives the PDU session establishment request message (equivalent to the above-mentioned first session request message of this application).
  • the UE can also send the PDU session establishment request message to the RAN (such as the base station), and the RAN device (such as the base station) forwards it to the AMF network element, and the AMF network element receives the message from the RAN (such as the base station).
  • the base station receives the PDU session establishment request message.
  • the PDU session establishment request message may include first indication information.
  • the first indication information is used to indicate the information of the enterprise to which the access tag of the UE belongs.
  • the information of the enterprise to which the access tag of the UE belongs may be It is but is not limited to DNN and/or NSSAI; or the first indication information is DNN and/or NSSAI.
  • the DNN and/or NSSAI indicate the network information of the target enterprise that the UE requests to establish.
  • Steps S601-S608 are introduced in detail by taking an enterprise's establishment of a corresponding PDU session (ie, communication session) as an example.
  • the AMF network element selects the appropriate SMF network element.
  • the AMF network element can also select the appropriate SMF network element based on the above-mentioned PDU session establishment request message (equivalent to the above-mentioned first session request message of this application). An instruction message to assist in selecting SMF network elements.
  • the AMF network element selects an SMF network element that satisfies the DNN and/or NSSAI in the above first indication information.
  • the AMF network element sends a PDU session creation session context request message to the SMF network element.
  • the SMF network element receives the PDU session creation session context request message.
  • the PDU session creation session context request message carries the DNN and/or NSSAI of the enterprise to which the access label belongs.
  • the above-mentioned DNN and/or NSSAI indicate the network information of the target enterprise that the UE requests to establish.
  • the PDU session creation session context request message also carries parameters such as SUPI (that is, the identification of the UE), the DNN requested by the UE, and the PDU Session ID.
  • SUPI that is, the identification of the UE
  • DNN the DNN requested by the UE
  • PDU Session ID the PDU Session ID
  • S604 The SMF network element sends a PDU session creation session context response message to the AMF network element.
  • the AMF network element receives the PDU session creation session context response message.
  • the SMF network element determines the target PIOT server information of the UE based on the DNN and/or NSSAI in the received PDU session establishment request message, and sends the N1N2 message to the AMF network element.
  • the SMF network element may also request the PCF network element to obtain information about the target server of the UE.
  • the target PIOT server information of the UE may include the IP address and/or port number of the target server.
  • the AMF network element receives the N1N2 message, where the N1N2 message carries the tunnel of the UPF network element. Endpoint identification and other information (this information is given to RAN equipment).
  • the N1N2 message also carries the PIOT server address and port number information (encapsulated in the N1 SM message and will be sent to the reader UE).
  • the N1N2 message may be an AMF communication N1N2 message forwarding message.
  • the AMF network element sends an N2 PDU session request message to the RAN.
  • the RAN receives the N2 PDU session request message, where the N2 PDU session request message carries a NAS message, and the NAS message carries PIOT server address and port number information.
  • the NAS message may be a PDU session establishment response message.
  • the NAS message also comes from the above-mentioned N1 SM message.
  • the RAN establishes air interface resources with the UE (reader/writer) and sends a NAS message to the UE.
  • the UE receives the NAS message (equivalent to the first response message of the above application), and the NAS message carries the PIOT server address (equivalent to the first target address information of the above application) and port number information (equivalent to the above The first port number information of this application).
  • S608 RAN sends the N2 PDU session response message to the AMF network element.
  • the AMF network element receives the N2 PDU session response message.
  • the UE reader/writer establishes an enterprise PDU session (PDU Session).
  • the UE reader/writer can refer to the above steps S601-S608 to establish the corresponding PDU session. , which will not be described in detail here.
  • the UE (reader/writer) establishes a corresponding PDU1 session for tag 1 belonging to enterprise 1 through the above steps S601-S608; the UE (reader/writer) establishes a corresponding PDU1 session for tag 2 belonging to enterprise 2 through the above steps S601-S608.
  • the corresponding PDU2 session is established; the UE (reader/writer) establishes the corresponding PDU3 session for the enterprise 3 to which tag 3 belongs, through the above steps S601-S608.
  • the UE obtains different PIOT server address information and port number information respectively, that is, it establishes a PDU session and obtains a corresponding PIOT server address. information and port number information.
  • S609 The UE (reader/writer) establishes a connection with the corresponding PIOT server based on the PIOT server address information and port number information.
  • the UE obtains a PIOT1 server address information and corresponding port number information by establishing a PDU1 session.
  • the reader/writer UE establishes a connection with the PIOT1 server based on the PIOT1 server address information and corresponding port number information.
  • the UE obtains a PIOT2 server address information and corresponding port number information by establishing a PDU2 session.
  • the UE establishes a connection with the PIOT2 server based on the PIOT2 server address information and corresponding port number information.
  • the UE (reader/writer) obtains a PIOT3 server address information and corresponding port number information by establishing a PDU3 session.
  • the UE (reader/writer) establishes a connection with the PIOT3 server based on the PIOT3 server address information and corresponding port number information.
  • the PIOT server sends the first request message to the UE (reader/writer) through the established PDU session.
  • the UE receives the first request message (equivalent to the above-mentioned first request in this application).
  • the first request message includes a command for tag inventory or reading and writing.
  • the first request message may also include a range of target tags and filtering rules.
  • the UE reader/writer establishes a connection with the target tag according to the above-mentioned first request message, and executes the above-mentioned tag inventory or read and write command.
  • the UE reader/writer
  • the UE can first execute the target tag (equivalent to the above) according to the tag inventory command.
  • the first tag applied for) is inventoried.
  • the process of performing the tag inventory can be performed with reference to the steps in Figure 2 above, which will not be described in detail here.
  • step S611 the UE (reader/writer) can read the information of the accessed tag. How the UE (reader/writer) specifically reads the information of the accessed tag can be implemented with reference to the existing technology, and will not be described in detail here.
  • the label information includes but is not limited to the label's identification, such as electronic product code EPC, label identification number TID, etc.
  • the accessed tags include tag 1, tag 2, and tag 3, and the UE (reader/writer) reads the information of tag 1, tag 2, and tag 3.
  • the UE reader/writer selects an appropriate PDU session according to the enhanced URSP policy.
  • the UE reader/writer selects an appropriate PDU session according to the enhanced URSP policy, which can be regarded as the above-mentioned first communication session.
  • the UE reader/writer determines the accessed tag information based on the acquired information, combined with the enhanced user equipment routing policy (URSP policy) shown in Table 1 (equivalent to the first routing policy of this application).
  • the tag determines the corresponding appropriate PDU session (equivalent to the above-mentioned communication session of this application).
  • URSP policy enhanced user equipment routing policy
  • the enhanced URSP policy adds an additional description about Passive IoT to the traffic description content, which consists of the enterprise ID and the tag ID and is used to match and identify different tags.
  • the description of Passive IoT is bound to the corresponding PIOT server address and port number, and is transmitted through the corresponding PDU session (i.e., the first communication session of this application), that is, a Passive IoT is respectively associated with the PIOT server address, port number, and PDU session There is a corresponding relationship.
  • the UE reader/writer
  • the UE can determine the description of Passive IoT in Table 1 based on the tag information (the ID of the tag 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. , and the corresponding PDU session.
  • the UE can determine the corresponding server address and port number based on the ID of tag 1 and the ID of the enterprise to which tag 1 belongs (or obtain the server address and port number through the above session establishment process), as well as the PDU1 session.
  • the UE reader/writer determines the corresponding server address and port number based on the ID of tag 2 and the ID of the enterprise to which tag 2 belongs (or obtains the server address and port number through the above session establishment process), as well as the PDU2 session.
  • the UE (reader/writer) determines the corresponding server address and port number (or obtains the server address and port number through the above 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.
  • S613 The UE (reader/writer) sends the tag information to the corresponding PIOT server through the PDU session.
  • the tag information may be tag data, or the tag information may only include the tag identifier.
  • the UE uses the corresponding PDU session and sends the tag information to the corresponding PIOT server through the corresponding port number based on the PIOT server address information and port number.
  • the UE uses the corresponding PDU1 session to send the data of tag 1 to the corresponding PIOT1 server through the corresponding port number 1 based on the PIOT1 server address information and port number 1.
  • the UE Based on the PIOT2 server address information and port number 2, the UE (reader/writer) uses the corresponding PDU2 session to send the data of tag 2 to the corresponding PIOT2 server through the corresponding port number 2.
  • the UE uses the corresponding data of tag 3 based on the PIOT3 server address information and port number 3.
  • the PDU3 session is sent to the corresponding PIOT3 server through the corresponding port number 3.
  • the DNN and/or NSSAI corresponding to the enterprise carrying the access tag is sent through the UE (reader/writer) to assist the core network in identifying and allocating different server address information. and port number information, so that the UE (reader/writer) can establish a user plane connection with the Passive IoT server.
  • the UE reader/writer
  • the UE can select the corresponding appropriate PDU session for the information of different tags, and then route and transmit the information of different tags.
  • the UPF network element performs label management, and establishes a user plane session through the UPF network element and Transmit tag information, as shown in Figure 7.
  • the specific process is as follows:
  • the specific registration process of the UE can be implemented with reference to the existing technology and will not be described here.
  • S701 The UE (reader/writer) sends a PDU session establishment request message to the AMF network element.
  • the AMF network element receives the PDU session establishment request message (equivalent to the first session request message of the present application).
  • the PDU session establishment request message carries the data network name DNN and/or the data network name of the enterprise to which the access tag belongs. NSSAI.
  • step S701 reference may be made to the above-mentioned step S601, which will not be described in detail here.
  • steps S701-S708 are initiated in sequence for the enterprises to which different tags accessed belong.
  • the steps S701-S708 are described in detail based on the example of establishing a corresponding PDU session (ie, communication session) for an enterprise.
  • the AMF network element selects the appropriate SMF network element.
  • step S702 reference may be made to the above-mentioned step S602, which will not be described in detail here.
  • the AMF network element sends a PDU session creation session context request message to the SMF network element.
  • the SMF network element receives the PDU session creation session context request message.
  • the PDU session creation session context request message carries the DNN and/or NSSAI of the enterprise to which the access label belongs.
  • the above-mentioned DNN and/or NSSAI indicate the network information of the target enterprise that the UE requests to establish.
  • the PDU session creation session context request message also carries parameters such as the UE's identification (such as SUPI), the data network name DNN requested by the UE, and the PDU session identification PDU Session ID.
  • step S702 reference may be made to the above-mentioned step S602, which will not be described in detail here.
  • S704 The SMF network element sends a PDU session creation session context response message to the AMF network element.
  • the AMF network element receives the PDU session creation session context response message.
  • S705 The SMF network element initiates an N4 session establishment/modification request to the UPF network element.
  • the UPF network element receives the N4 session establishment/modification request (equivalent to the above-mentioned N4 session request message of this application).
  • the N4 session establishment/modification request carries the IP address of the UE (equivalent to the third target address information of this application) and the corresponding port number information (equivalent to the third target address information of this application), and the IP address of the PIOT server.
  • the address (including fully qualified domain name) (equivalent to the second target address information of this application) and the corresponding port number information (equivalent to the second port number information of this application), and the first label filter.
  • the SMF network element may determine the target PIOT server information of the UPF network element based on the received DNN and/or IP address.
  • the target PIOT server information may include the IP address and/or port number of the target server.
  • SMF The network element can also request the PCF network element to obtain the above target PIOT server information.
  • the above-mentioned first label filter is used to identify the label.
  • the UPF network element can select the corresponding PIOT server by identifying the identifier of the label or the enterprise identity carried by the label to send the label information.
  • the UPF network element can identify the tag based on the first tag filter and determine the target PIOT server for the tag.
  • the UPF network element sends an N4 session establishment/modification response message to the SMF network element.
  • the UPF network element sends an N4 session establishment/modification response message to the SMF network element, which is used to feed back its own IP address and port number to the SMF network element.
  • S707 The SMF network element sends an N1N2 message to the AMF network element.
  • the AMF network element receives the N1N2 message, where the N1N2 message carries the IP address and port number information of the above-mentioned UPF network element.
  • the above N1N2 message may be a message forwarded by the AMF network element through the N1N2 message.
  • IP address and port number information of the UPF network element is encapsulated in the N1 SM message, and this information will be sent to the UE (reader/writer).
  • the AMF network element sends an N2 PDU session request message to the RAN.
  • the RAN receives the N2 PDU session request message, which carries the NAS message.
  • the NAS message is the above-mentioned N1 SM message.
  • the NAS message carries the IP address and port number information of the UPF network element.
  • the NAS message may be a PDU session establishment response message.
  • the RAN allocates air interface resources, establishes a wireless connection with the UE (reader/writer), and sends the above-received NAS message to the UE (reader/writer).
  • the UE receives the NAS message (equivalent to the second response message of the above application), and the NAS message carries the IP address of the UPF network element (equivalent to the second target address information of the above application) and port number information (equivalent to the second port number information of the above application).
  • S710 RAN sends the N2 PDU session response message to the AMF network element.
  • 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.
  • the UE reader/writer establishes a connection with the UPF network element based on the IP address and port number of the UPF network element.
  • step S711 the first communication session between the UE (reader/writer) and the UPF network element can be established.
  • the UPF network element establishes a connection with the corresponding PIOT server based on the address information and port number information of the PIOT server.
  • the UPF network element can receive the IP address and corresponding port number information of the PIOT server. Furthermore, the UPF network element can communicate with the PIOT server based on the IP address and corresponding port number information.
  • the PIOT server establishes a connection. Specifically, to establish a connection between the UPF network element and the PIOT server, reference may be made to the process of establishing a connection between the UE (reader/writer) and the PIOT server in the above step S609, which will not be described in detail here.
  • the UPF network element can refer to the above-mentioned steps S701-S705 for the different tags that the UE (reader/writer) accesses to belong to the enterprise in order to obtain the IP address and corresponding port number information of the corresponding PIOT server, and then communicate with The corresponding PIOT server establishes a connection. Finally, the UPF network element created different PIOT server connections for different label-owned enterprises for subsequent use.
  • the PIOT server sends the first request message to the UE (ie, the reader/writer) through the established PDU session.
  • the UE receives the first request message (equivalent to the above-mentioned first request in this application).
  • the first request message includes a command for tag inventory or reading and writing.
  • the first request message may also include a range of target tags and filtering rules.
  • This step S713 may be mutually referenced with the above-mentioned step S610.
  • S714 The UE (reader/writer) establishes a connection with the target tag according to the above-mentioned first request message, and executes the above-mentioned tag inventory or read and write command.
  • the UE reader/writer
  • the UE can first perform inventory of the target tag (equivalent to the first tag of the present application) according to the tag inventory command.
  • the tag inventory process can be performed with reference to the steps in Figure 2 above, which are not included here. Let’s go into more detail.
  • step S714 the UE (reader/writer) reads the information of the accessed tag. How the UE (reader/writer) specifically reads the information of the accessed tag can be implemented with reference to the existing technology, and will not be described in detail here.
  • the label information includes but is not limited to the label's identification, such as electronic product code EPC, label identification number TID, etc.
  • the accessed tags include tag 1, tag 2, and tag 3, and the UE (reader/writer) reads the information of tag 1, tag 2, and tag 3.
  • This step S714 may be mutually referenced with the above-mentioned step S611.
  • S715 The UE (reader/writer) selects an appropriate PDU session according to the enhanced URSP policy.
  • the UE reader/writer selects an appropriate PDU session according to the enhanced URSP policy, which can be regarded as the above-mentioned first communication session.
  • the UE (reader/writer) determines the corresponding appropriate PDU session for each accessed label based on the obtained accessed label information and combined with the enhanced URSP policy (routing policy) shown in Table 1 above. It is worth noting that the difference from Embodiment 1 is that the IP descriptor in the enhanced URSP policy in this embodiment is the IP address and port number of the UPF received by the UE, and the corresponding protocol ID.
  • the UE can determine the PDU1 session based on the acquired information of accessed tag 1 and the enhanced URSP policy shown in Table 1 above.
  • the UE can determine the PDU2 session based on the acquired information of the accessed tag 2 and the enhanced URSP policy shown in Table 1 above.
  • the UE can determine the PDU3 session based on the acquired information of accessed tag 3 and the enhanced URSP policy shown in Table 1 above.
  • This step S715 is the same as the above-mentioned step S612 and may be referred to each other, and will not be described in detail here.
  • S716 The UE (reader/writer) sends the label information to the UPF network element through the PDU session.
  • the UPF network element receives the label information.
  • the UE transmits the information of tag 1 to the UPF network element through the PDU1 session.
  • the UE transmits the information of tag 2 to the UPF network element through the PDU2 session.
  • the UE transmits the tag 3 information to the UPF network element through the PDU3 session.
  • the UPF network element selects the connection to the corresponding PIOT server based on the first label filter.
  • the first label filter contains the filtering rules of the label identification or the enterprise identification carried by the label, and the information of the target PIOT server corresponding to the corresponding filtering rules, that is, the IP address and port number of the target PIOT.
  • the UPF network element receives three tags of information.
  • the UPF network element can identify the received three tags of information through the first tag filter and determine them to be the data of tag 1, the data of tag 2, and the data of tag 3. data; further, the UPF network element can determine the connection to the corresponding PIOT server for the information of different tags, that is, the UPF network element determines the connection to the PIOT1 server for the data of tag 1, and the UPF network element determines the connection of PIOT2 for the data of tag 2.
  • the connection to the server, the UPF network element determines the connection to the PIOT3 server for the data of tag 3.
  • the UPF network element transmits the label information to the corresponding PIOT server.
  • the tag information may be tag data, or the tag information may only include the tag identifier.
  • the UPF network element transmits the data of tag 1 to the PIOT1 server through the connection of the PIOT1 server.
  • the UPF network element transmits the data of tag 2 to the PIOT2 server through the connection of the PIOT2 server.
  • the UPF network element transmits the data of tag 3 to the PIOT3 server through the connection of the PIOT3 server.
  • the UE when the UE cannot learn 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 label information to the UPF network element, which is further received by the UPF network element. Identify the tag information, and determine the corresponding PIOT server connection (i.e., routing data) for the tag information. Finally, the UPF network element accurately transmits the tag information to the corresponding PIOT through the connection of the corresponding PIOT server. server.
  • the UPF network element performs tag management, and establishes a user plane session through the UPF network element and Transfer tag information.
  • multiple UPF network elements may be included.
  • the UE reader/writer
  • creates a communication session Passive IoT session
  • each communication session may correspond to a different UPF network element, and each communication session
  • the sessions ultimately correspond to the target PIOT servers of different enterprises.
  • the correspondence between different communication sessions and different target PIOT servers is stored on the UPF network element, and the UPF network element performs label routing management.
  • the specific registration process of the UE can be implemented with reference to the existing technology and will not be described here.
  • the UE sends PDU session establishment request information to the AMF network element.
  • the AMF network element receives the PDU session establishment request message.
  • the UE can also send the PDU session establishment request message to the RAN device (such as the base station), and the RAN device (such as the base station) forwards it to the AMF network element, and the AMF network element receives the request message from the RAN.
  • the device (such as a base station) receives the PDU session establishment request message.
  • the PDU session establishment request message may include first indication information.
  • the first indication information is used to indicate the information of the enterprise to which the access tag of the UE belongs.
  • the information of the enterprise to which the access tag of the UE belongs may be It is but is not limited to DNN and/or NSSAI; or the first indication information is DNN and/or NSSAI.
  • the DNN and/or NSSAI indicate the network information of the target enterprise that the UE requests to establish.
  • This step S801 may refer to the above-mentioned steps S601 and S701.
  • Steps S801-S808 can be considered as taking an enterprise to establish a corresponding PDU session (ie, communication session) as an example, and will be introduced in detail.
  • the AMF network element selects the appropriate SMF network element.
  • the AMF network element can also select the appropriate SMF network element based on the above-mentioned PDU session establishment request message (equivalent to the above-mentioned first session request message of this application). An instruction message to assist in selecting SMF network elements.
  • the AMF network element selects an SMF network element that satisfies the DNN and/or NSSAI in the above first indication information.
  • This step S802 may refer to the above-mentioned steps S602 and S702.
  • S803 The AMF network element sends a PDU session creation session context request message to the SMF network element.
  • the SMF network element receives the PDU session creation session context request message.
  • the PDU session creation session context request message carries the DNN and/or NSSAI of the enterprise to which the access label belongs.
  • the above-mentioned DNN and/or NSSAI indicate the network information of the target enterprise that the UE requests to establish.
  • the PDU session creation session context request message also carries parameters such as the UE's identification (such as SUPI), the data network name DNN requested by the UE, and the PDU session identification PDU Session ID.
  • This step S804 may refer to the above-mentioned steps S604 and S704.
  • S804 The SMF network element sends a PDU session creation session context response message to the AMF network element.
  • the AMF network element receives the PDU session creation session context response message.
  • S805 The SMF network element sends an N4 session establishment/modification request to the corresponding UPF network element according to the received DNN.
  • the corresponding UPF network element receives the N4 session establishment/modification request (equivalent to the above-mentioned N4 session request message of this application).
  • the N4 session establishment/modification request carries the IP address and/or port number information of the UE, the IP address (including fully qualified domain name) and the corresponding port number information of the PIOT server.
  • the SMF network element determines the IP address (including the fully qualified domain name) of the appropriate PIOT server and the corresponding port number information based on the DNN of the enterprise to which the received label 1 belongs. If the SMF network element determines the IP address of the PIOT1 server ( Including fully qualified domain name) and corresponding port number information, 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 of the PIOT1 server (including fully qualified Domain name) and corresponding port number information.
  • the SMF network element only feeds back the IP address and corresponding port number information of the corresponding PIOT server to the corresponding UPF network element for the DNN and/or NSSAI of the enterprise to which a label belongs. Therefore, the SMF network element can refer to this method for the DNN and/or NSSAI of other enterprises whose labels are connected to the UE and feed back the IP address and corresponding port number information of the corresponding PIOT server to the corresponding UPF network element.
  • the corresponding UPF network elements can be the same or different. If the UPF network elements corresponding to the above different communication sessions are the same (that is, the IP addresses of the UPF network elements are the same), then the corresponding port numbers are different. If If the above-mentioned different communication sessions correspond to different UPF network elements (that is, the IP addresses of the UPF network elements are different), 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.
  • the SMF network element can provide the corresponding UPF (1) network element, UPF (2) network element, and UPF (3) network element with respect to the DNN and/or NSSAI of the enterprise where tags 1, 2, and 3 accessed by the UE belong to.
  • the different UFP network elements The communication sessions corresponding to network elements are also different.
  • the SMF network element can determine the IP address and corresponding port number of the corresponding PIOT1 server to be fed back to the same UPF(1) network element according to the DNN and/or NSSAI of the enterprise where tags 1, 2, and 3 accessed by the UE belong to. information, but the SMF network element determines that the port number of the corresponding UPF(1) network element for tags 1, 2, and 3 connected to the UE can be different, that is, tag 1 corresponds to the port number 1 of the UPF(1) network element.
  • Label 2 corresponds to port number 2 of the UPF(1) network element
  • label 3 corresponds to port number 3 of the UPF(1) network element
  • port number 1, port number 2, and port number 3 all correspond to different communication sessions.
  • the UPF network element sends an N4 session establishment/modification response message to the SMF network element.
  • the UPF(1) network element After receiving the N4 session establishment/modification request, the UPF(1) network element sends the N4 session establishment/modification request to the SMF network element.
  • the modification response message is used to feed back 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.
  • S807 The SMF network element sends an N1N2 message to the AMF network element.
  • the AMF network element receives the N1N2 message, where the N1N2 message carries the IP address and port number information of the above-mentioned UPF network element.
  • the above N1N2 message may be an AMF network element communication N1N2 message forwarding message.
  • the SMF network element sends an N1N2 message to the AMF network element based on the DNN and/or NSSAI of the enterprise to which the received label 1 belongs.
  • the 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 DNN and/or NSSAI of the enterprise to which the received label 2 belongs.
  • the 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 DNN and/or NSSAI of the enterprise to which the received label 3 belongs.
  • the N1N2 message carries the IP address and port number 3 information of the UPF(3) network element.
  • the SMF network element sends an N1N2 message to the AMF network element based on the DNN and/or NSSAI of the enterprise to which the received label 1 belongs.
  • the 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 DNN and/or NSSAI of the enterprise to which the received label 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 DNN and/or NSSAI of the enterprise to which the received label 3 belongs.
  • the N1N2 message carries the IP address and port number 3 information of the UPF(1) network element.
  • the AMF network element sends an N2 PDU session request message to the RAN.
  • the RAN receives the N2 PDU session request message.
  • the N2 PDU session request message carries a NAS message.
  • the NAS message is the above-mentioned N1 SM message.
  • the NAS message carries the IP address of the UPF network element received by the above-mentioned AMF network element. and port number information.
  • the NAS message may be a PDU session establishment response message.
  • the RAN allocates air interface resources, establishes a wireless connection with the UE (reader/writer), and sends the above-received NAS message to the UE (reader/writer).
  • the UE receives the NAS message (which may be equivalent to the second response message of the above application), and the NAS message carries the IP address of the UPF network element ((which is equivalent to the second target address of the above application) information)) and port number information (equivalent to the second port number information of the above application).
  • S810 RAN sends the N2 PDU session response message to the AMF network element.
  • 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.
  • the UE reader/writer establishes a connection with the corresponding UPF network element based on the IP address and port number of the UPF network element.
  • step S811 connections between multiple UEs (readers and writers) to the UPF network element can be established.
  • the UE i.e., the reader/writer
  • the UE 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 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 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.
  • the UE that is, the reader/writer
  • the UE (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 (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.
  • the UPF network element matches the corresponding PIOT server based on the address information and port number information of the PIOT server. establish connection.
  • different UPF network elements can obtain the address information and port number information of the corresponding PIOT server for the enterprise to which the corresponding access tag belongs, and based on the obtained address information and port number information of the corresponding PIOT server , establish a connection with the corresponding PIOT server.
  • the UPF(1) network element establishes a connection with the PIOT1 server based on the IP address of the UPF(1) network element and the 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 of the UPF(2) network element and the 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 of the UPF(3) network element and the port number 3 of the UPF(3) network element, as well as the IP address and corresponding port number 3 information of the PIOT3 server.
  • the UPF(1) network element establishes a connection with the PIOT1 server based on the IP address of the UPF(1) network element and the port number 1 of the UPF(1) network element, as well as the IP address information 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 of the UPF(1) network element and the 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 of the UPF(1) network element and the port number 3 of the UPF(1) network element, the IP address information of the PIOT3 server and the corresponding port number 3.
  • connections between multiple UPF network elements corresponding to multiple PIOT servers can be established, or connections between one UPF network element corresponding to multiple PIOT servers can be established.
  • an association can be established between the connections of the UE (reader/writer) to multiple UPF network elements and the connections of the multiple UPF network elements to multiple PIOT servers, that is, including multiple UFP network elements.
  • the connection between the UE (reader/writer) and one UPF network element among the multiple UPF network elements corresponds to a connection between the UPF network element and one PIOT server among the multiple PIOT servers.
  • a UE and The connection between UPF(x) network elements corresponds to a connection between the UPF(x) network element and the PIOT(x) server, where x is a variable positive integer.
  • the connection of the UE (reader/writer) to a UPF network element and the connection of the UPF network element to multiple PIOT servers can establish an association (or correspondence) 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 only one UFP network element is included, the UE ( The connection between the reader and writer) and the UPF network element corresponds to a connection between the UPF network element and one PIOT server among multiple PIOT servers.
  • the connection between the UE and UPF (1) corresponds to a connection between the UPF ( 1) Connection to PIOT(x) server, x is a variable positive integer.
  • the PIOT server sends the first request message to the UE (ie, the reader/writer) through the established PDU session.
  • the UE receives the first request message (equivalent to the above-mentioned first request in this application).
  • the first request message includes a command for tag inventory or reading and writing.
  • the first request message may also include a range of target tags and filtering rules.
  • This step S813 may be mutually referenced with the above-mentioned step S610 and step S713.
  • S814 The UE (reader/writer) establishes a connection with the target tag according to the above-mentioned first request message, and executes the above-mentioned tag inventory or read and write command.
  • the UE reader/writer
  • the UE can first perform inventory of the target tag (equivalent to the first tag of the present application) according to the tag inventory command.
  • the tag inventory process can be performed with reference to the steps in Figure 2 above, which are not included here. Let’s go into more detail.
  • step S814 the UE (reader/writer) reads the information of the accessed tag.
  • the label information includes but is not limited to the label's identification, such as electronic product code EPC, label identification number TID, etc.
  • the accessed tags include tag 1, tag 2, and tag 3, and the UE (reader/writer) reads the information of tag 1, tag 2, and tag 3.
  • This step S814 may be mutually referenced with the above-mentioned step S611 and step S714.
  • S815 The UE (reader/writer) selects an appropriate PDU session according to the enhanced URSP policy.
  • the UE reader/writer determines the corresponding appropriate PDU session for each accessed label based on the obtained accessed label information and combined with the enhanced URSP policy (routing policy) shown in Table 1 above.
  • the IP descriptor of the above-mentioned URSP policy is the IP address, port number, and protocol ID of the UPF.
  • the UE determines the PDU1 session based on the information of accessed tag 1 combined with the enhanced URSP policy shown in Table 1 above.
  • the UE determines the PDU2 session based on the information of the accessed tag 2 combined with the enhanced URSP policy shown in the above table 1.
  • the UE determines the PDU2 session based on the information of the accessed tag 3 combined with the enhanced URSP policy shown in the above table 1.
  • the enhanced URSP policy identifies PDU3 sessions.
  • step S815 is the same as the above-mentioned step S715 and can be referred to each other, and will not be described in detail here.
  • S816 The UE (reader/writer) sends the label information to the corresponding UPF network element through the PDU session.
  • the UPF network element receives the label information.
  • the UE sends the information of tag 1 to the UPF (1) network element through the PDU1 session; the UE (reader/writer) sends the information of tag 2 to the UPF (2) network element through the PDU2 session; The UE (reader/writer) sends the information of tag 3 to the UPF(3) network element through the PDU3 session.
  • the UE sends the information of tag 1 to the UPF (1) network element through the PDU1 session; the UE (reader/writer) sends the information of tag 2 to the UPF (1) network element through the PDU2 session; UE (Reader) sends the information of tag 3 to the UPF(1) network element through the PDU3 session.
  • the UPF network element determines the target enterprise server of the label based on the label information obtained from different IP addresses and/or port numbers, and selects the connection of the UPF network element to the PIOT server.
  • the UPF network element can determine the connection of the UPF network element to the PIOT server based on the association relationship established in the above step S812.
  • the UE sends the information of tag 1 to the UPF(1) network element.
  • the UPF(1) network element selects the UPF network element based on the association relationship. (1) Connection to PIOT1 server.
  • the UE sends the information of tag 2 to the UPF (2) network element.
  • the UPF (2) network element selects the UPF network element (2) based on the association relationship. ) connection to the PIOT2 server.
  • the UE sends the information of tag 3 to the UPF (3) network element.
  • the UPF (3) network element selects the UPF network element (3) based on the association relationship. ) connection to the PIOT3 server.
  • the UE (reader/writer) sends the information of tag 1 to the UPF(1) network element, then in the step S817, the UPF(1) network element selects the UPF network element ( 1) Connection to PIOT1 server. In the above step S816, the UE (reader/writer) also sends the information of tag 2 to the UPF(1) network element. Then in step S817, the UPF(1) network element selects the UPF network element ( 1) Connection to PIOT2 server. In the above step S816, the UE (reader/writer) sends the information of tag 3 to the UPF(1) network element. Then in the step S817, the UPF(1) network element selects the UPF network element (1) based on the association relationship. ) to the PIOT3 server connection catch.
  • the information of the tag may be the data of the tag, or the information of the tag may only include the identifier of the tag.
  • UPF (1) network element selects the connection from UPF network element (1) to the PIOT1 server through the above step S817, then in step S818, through the UPF network element (1) to PIOT1
  • the server connection transmits the information of tag 1 to the PIOT1 server.
  • the UPF (2) network element selects the connection between the UPF network element (2) and the PIOT2 server through the above step S817.
  • the information of tag 2 is transmitted through the connection between the UPF network element (2) and the PIOT2 server. to the PIOT2 server.
  • the UPF (3) network element selects the connection between the UPF network element (3) and the PIOT3 server through the above step S817.
  • the information of label 3 is transmitted through the connection between the UPF network element (3) and the PIOT3 server. to the PIOT3 server.
  • the UPF (1) network element selects the connection from the UPF network element (1) to the PIOT1 server through the above step S817, then in step S818, through the UPF
  • the connection between network element (1) and the PIOT1 server transmits the information of tag 1 to the PIOT1 server.
  • the UPF (1) network element selects the connection between the UPF network element (1) and the PIOT2 server through the above step S817. Then in this step S818, the information of tag 2 is transmitted through the connection between the UPF network element (1) and the PIOT2 server. to the PIOT2 server.
  • the UPF (1) network element selects the connection between the UPF network element (1) and the PIOT3 server through the above step S817. Then in this step S818, the information of label 3 is transmitted through the connection between the UPF network element (1) and the PIOT3 server. to the PIOT3 server.
  • the UE when the UE cannot learn the address information and corresponding port number information of the PIOT server, the UE can request the DNN/NSSAI of the enterprise with different labels and establish different communication sessions through UPF. Then, the UE can use the enhanced URSP based on the enhanced URSP The policy selects the first communication session and sends the target tag information to the corresponding UPF network element. The corresponding UPF network element further 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.
  • the UE reader/writer mainly performs tag management and transmits it through the control plane channel. That is, the PIOT server sends instructions to the AMF network element through the NEF network element.
  • the specific process is as follows:
  • the specific registration process of the UE can be implemented with reference to the existing technology and will not be described here.
  • the PIOT server sends an inventory request message to the NEF network element.
  • the NEF network element receives the inventory request message, wherein the inventory request message carries a tag operation command, a second tag filter (such as inventory area, inventory type, inventory rules, etc.) and report triggering events (such as inventory cycles, new tag access events, tag departures) and other information.
  • a tag operation command such as inventory area, inventory type, inventory rules, etc.
  • triggering events such as inventory cycles, new tag access events, tag departures
  • the NEF network element records the address of the PIOT server that sent the inventory request message.
  • the NEF network element For each inventory request message received, the NEF network element records the address of the PIOT server (that is, the enterprise's application server) from which the inventory request message originates.
  • the NEF network element generates an operation identifier and sends the first signaling to the AMF network element.
  • the first signaling may be a first message.
  • the operation identifier (relative to the above-mentioned first identifier in this application) can be used by the NEF network element to uniquely determine the first signaling.
  • the NEF network element may further determine the inventory request message that triggers the first signaling by determining the first signaling. information to determine the address information of the recorded PIOT server.
  • the AMF network element receives the first signaling, wherein the first signaling carries the operation identifier, and the information included in the above-mentioned inventory request message, that is, the label operation command, the second label filter (inventory area) and the reporting Trigger events and other information. Since the first signaling is triggered by the inventory request message, the operation identifier can also be used to identify the first message.
  • the AMF network element sends the first message to the UE (reader/writer).
  • the first message may be a NAS message.
  • the UE receives the first message.
  • the first message contains the above-mentioned first signaling. Therefore, the first message also contains the above-mentioned operation identifier (first Message identification), label operation commands, second label filter (inventory area), and reporting trigger events and other information.
  • the UE reader/writer identifies and determines the first tag based on the second tag filter.
  • the first tag may be a group of tags that satisfy tag filter rules, or may be a tag identified by a specific tag, which is not limited in this embodiment of the present application.
  • the tag accessed by the UE (reader/writer) side is matched to a tag ID of (1), and the corresponding operation identifier (1) is identified based on the tag (1).
  • the second tag filter can be used to match the corresponding ID for the accessed tag, and the second tag filter can also be used to determine the corresponding operation identifier according to the tag ID.
  • the second tag filter may include a correspondence between tag IDs and operation identifiers, that is, one tag ID corresponds to one operation identifier, or multiple tag IDs correspond to one operation identifier.
  • one operation ID can be used to determine a unique target server, but one target server may correspond to multiple operation IDs, that is, the same target server may generate different operations on the NEF network element in multiple tag inventory requests. logo.
  • S906 The UE (reader/writer) performs tag operations according to the tag operation command.
  • S907 The UE (reader/writer) sends the second message to the AMF network element.
  • the second message may be an uplink NAS transmission message.
  • the AMF network element receives the second message, which carries information about the accessed tag and the corresponding operation identifier.
  • the uplink NAS transmission message carries the data (or information) of label (1) and the operation identifier (1) corresponding to label (1).
  • the AMF network element sends a data transmission message to the NEF network element.
  • the data transmission message may also be a second message.
  • the NEF network element receives the data transmission message, which carries the information of the accessed tag and the corresponding operation identifier (ie, the first message identifier).
  • the information of the tag may be the data of the tag, or the information of the tag may only include the identifier of the tag.
  • the NEF network element identifies the operation identifier in the data transmission message and determines the address of the corresponding PIOT server.
  • step S903 the NEF network element has pre-recorded the first message and generated a unique operation identifier for it, that is, the corresponding relationship between the operation identifier and the first message has been recorded.
  • the address information of the PIOT server may be further determined 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.
  • the NEF network element sends the label information carried in the data transmission message to the corresponding PIOT server.
  • the NEF network element sends the label information to the corresponding PIOT server according to the address of the PIOT server.
  • a connection between the tag and the PIOT server (that is, the enterprise's application server) is established based on the control plane, and the reader/writer performs tag identification and management.
  • the solution of Embodiment 4 transmits tag information through the control plane, there is no need to establish a session process, thereby saving signaling processes and reducing the delay required for transmitting tag information.
  • the UE mainly performs tag management and transmits it through the control plane channel. That is, the PIOT server sends instructions to the AMF network element through the NEF network element.
  • the UE can send the information (information) of all accessed tags to the AMF network element (equivalent to the second network element in the above application), and the AMF network element replaces the UE. (reader/writer) performs tag management and identification. Referring to Figure 10, the specific process of transmitting tag information is as follows:
  • the specific registration process of the UE can be implemented with reference to the existing technology and will not be described here.
  • the PIOT server sends an inventory request message to the NEF network element.
  • the NEF network element receives the inventory request message, wherein the inventory request message carries a label operation command and a second label filter (such as inventory area, inventory type, Inventory rules, etc.) and reporting triggering events (such as inventory cycles, new tag access events, tag departures) and other information.
  • a label operation command such as inventory area, inventory type, Inventory rules, etc.
  • triggering events such as inventory cycles, new tag access events, tag departures
  • This step S1001 may be mutually referenced with the above-mentioned step S901.
  • the NEF network element records the address of the PIOT server that sends the inventory request message.
  • the NEF network element can separately record the address of the PIOT server (that is, the enterprise's application server) from which the inventory request message comes for each received inventory request message.
  • the PIOT server that is, the enterprise's application server
  • This step S1002 may be mutually referenced with the above-mentioned step S902.
  • the NEF network element generates an operation identifier and sends the first message to the AMF network element.
  • the operation identifier (equivalent to the above-mentioned first identifier in this application) can be used by the NEF network element to uniquely determine the first message.
  • the NEF network element may further determine the inventory request message that triggered the first message by determining the first message, thereby determining the recorded address information of the PIOT server.
  • the AMF network element receives the first message, wherein the first message carries the operation identifier, and the information included in the above-mentioned inventory request message, that is, the label operation command, the third Two tag filters (inventory area) and reporting trigger events and other information. Since the first message is triggered by the above-mentioned inventory request message, the above-mentioned operation identifier can also be used to identify the first message.
  • This step S1003 may be mutually referenced with the above-mentioned step S903.
  • the AMF network element sends the third message to the UE (reader/writer).
  • the third message may be a NAS message.
  • the UE receives the third message, which carries the tag operation command in the above-mentioned first message, and reports triggering events and other information.
  • S1005 The UE (reader/writer) performs tag operations on all tags within the signal range according to the tag operation command.
  • S1006 The UE (reader/writer) sends the fourth message to the AMF network element.
  • the fourth message may be an uplink NAS message.
  • the UE reader/writer performs tag operations on all tags within the signal range according to the tag operation command, carries the operation result (that is, the collected tag information) in the fourth message (such as the uplink NAS message), and sends it to the AMF network element.
  • the AMF network element identifies and determines the first label based on the corresponding second label filter.
  • the first tag may be a group of tags that satisfy tag filter rules, or may be a tag identified by a specific tag.
  • the AMF network element After the AMF network element identifies and determines the first label, the AMF network element can also add a corresponding operation identifier to the information of the first label.
  • S1008 The AMF network element sends the second message to the NEF network element.
  • the second message may be a data transmission message.
  • the NEF network element receives the second message, which carries information about the accessed tag and the corresponding operation identifier.
  • the NEF network element identifies the operation identifier in the second message and determines the address of the corresponding PIOT server.
  • step S1003 the NEF network element has pre-recorded the first message and generated a unique operation identifier for it, that is, the corresponding relationship between the operation identifier and the first message has been recorded.
  • the address information of the corresponding PIOT server may be further determined 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.
  • the NEF network element sends the label information carried in the second message to the corresponding PIOT server.
  • the information of the tag may be the data of the tag, or the information of the tag may only include the identifier of the tag.
  • the NEF network element sends the label information to the corresponding PIOT server based on the address of the PIOT server.
  • the connection between the UE (reader/writer) and the PIOT server (that is, the enterprise's application server) is established based on the control plane, that is, the tag information is transmitted through the control plane. Therefore, there is no need to establish a session process, thereby saving money.
  • the signaling process can also reduce the delay required to transmit tag information.
  • the UE (reader/writer) can send the tag information collected based on the operation command to the AMF network element, and the AMF network element replaces the UE (reader/writer) to perform tag management and identification to reduce the capability of the reader/writer. requirements (i.e. no need for the reader to store and process information related to the second tag filter).
  • the communication device may include modules that perform one-to-one correspondence with the methods/operations/steps/actions described in the first communication device in the above-mentioned first method embodiment or Unit, the module or unit can be a hardware circuit, software, or a combination of hardware circuit and software.
  • the device may have a structure as shown in Figure 11.
  • the communication device 1100 may include a receiving unit 1101, a processing unit 1102, and a sending unit 1103. Each unit will be introduced in detail below.
  • the receiving unit 1101 is configured to receive a first request, the first request instructs the first communication device to obtain the information of the first tag;
  • the receiving unit 1101 is also configured to, according to the first request, Obtain the information of the first tag, the information of the first tag includes the identification of the first tag;
  • the processing unit 1102 is used to determine the first communication session according to the identification of the first tag, the The first communication session is used to transmit the information of the first tag;
  • the sending unit 1103 is used to send the information of the first tag through the first communication session.
  • the communication device 1100 may also include a storage unit (not shown in FIG. 11 ), which may be used to store computer programs and/or that perform the methods/operations/steps/actions described by the communication device. instructions and/or information, etc.
  • the processing unit 1102 when determining the first communication session based on the identification of the first label, is specifically configured to: based on the identification of the first label and the first routing policy information, The first communication session is determined from at least one communication session, and the first routing policy information includes a correspondence relationship between the identifier of the first tag and the identifier of the first communication session.
  • the processing unit 1102 is further configured to: before the receiving unit 1101 receives the first request, establish at least one communication session, and the at least one communication session includes the first communication session. Session; establishing at least one routing policy information, each routing policy information including a corresponding relationship between a corresponding label and an identifier of the communication session.
  • the processing unit 1102 when establishing the first communication session, is specifically configured to:
  • the first session request message is sent by the sending unit 1103, and the first session request message includes first indication information, and the first indication information indicates the home enterprise information of the first tag; received by the receiving unit 1101
  • a first response message the first response message is used to respond to the first session request message, the first response message contains first target address information and/or first port number information, wherein the first response message A target address information and/or the first port number information is determined based on the first indication information; based on the first target address information and/or the first port number information, the first port number information is established.
  • a communication session; the first target address information and/or the first port number information are used to determine a target server, and the target server is a server of the home enterprise.
  • the sending unit 1103 when sending the information of the first tag through the first communication session, is specifically configured to: send the information to the target server through the first communication session. Send the information of the first tag.
  • the processing unit 1102 when establishing the first communication session, is specifically configured to:
  • the second session request message includes second indication information, the second indication information indicates the home enterprise information of the first tag; receive it through the receiving unit 1101
  • a second response message the second response message 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 response message
  • the second target address information and/or the second port number information are determined based on the second indication information; the second target address information and/or the second port number information is established based on the second target address information and/or the second port number information.
  • a communication session; the second target address information and/or the second port number information are used to determine the first user plane functional network element, and the first user plane functional network element provides services for the home enterprise user plane network elements.
  • the sending unit 1103 when the sending unit 1103 sends the information of the first tag through the first communication session, it is specifically configured to: send the information to the first tag through the first communication session.
  • the user plane functional network element sends the information of the first label.
  • the communication device may include a method/operation/step/action that performs one-to-one correspondence with the methods/operations/steps/actions described in the first user plane functional network element in the first method embodiment.
  • the module or unit may be a hardware circuit or a software, or may be a hardware circuit combined with software.
  • the device may also have a structure as shown in Figure 11.
  • the communication device 1100 may include a receiving unit 1101, a processing unit 1102, and a sending unit 1103. Among them, the receiving unit 1101 is used to receive the information of the first tag and the first information, and the first information is used to determine the target server of the first tag; the processing unit 1102 is used to calculate the target server according to the first tag. Information that determines the target server of the first tag; the sending unit 1103 is used to send the information of the first tag to the target server.
  • the communication device 1100 may also include a storage unit (not shown in Figure 11), which may be used to store instructions for performing the methods/operations/steps/actions described by the first user plane functional network element.
  • a storage unit not shown in Figure 11
  • the receiving unit 1101 when receiving the first information, is specifically configured to: receive an N4 session request message, where the N4 session request message includes the first information, and the first information Indicates the first tag filter, which is used to match the corresponding server according to the identification of the tag;
  • the processing unit 1102 determines the target server of the first tag based on the first information, it may be specifically configured to: determine the first tag filter based on the first information; The identification, using the first tag filter, matches the target server to the first tag.
  • the receiving unit 1101 when receiving the information of the first tag, may be specifically configured to: receive the information of the first tag from the first communication device;
  • the receiving unit 1101 When receiving the first information, the receiving unit 1101 is specifically configured to: receive an N4 session request message.
  • the N4 session request message includes the first information, and the first information indicates the address of the first communication device. information and/or third port number information for the first communication device to send the information of the first tag;
  • the processing unit 1102 may be specifically configured to: determine the address information of the first communication device and/or the first communication device based on the first information. Third port number information; determine the target server of the first tag according to the address information of the first communication device, the third port number information, and the first mapping information; wherein, in the first mapping information It includes a correspondence between the address information and/or port number information of the first communication device and the identity of the server.
  • the receiving unit 1101 when receiving the first information, may be specifically configured to: receive an N4 session request message, where the N4 session request message includes the first information, and the first information Indicates the fourth port number information on the first user plane functional network element to receive the information of the first label;
  • the processing unit 1102 determines the target server of the first tag based on the first information, it may be specifically configured to: determine based on the first information that the first user plane functional network element receives the third The fourth port number information of a label; determine the target server of the first label according to the fourth port number information and the second mapping information; wherein the second mapping information includes the first user The corresponding relationship between the port number information on the functional network element and the identity of the server.
  • the receiving unit 1101 when receiving the first information, may be specifically configured to: receive an N4 session request message, where the N4 session request message includes the first information, and the first information Indicates 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 label; wherein the address information of the target server and/or the fifth port The number information is determined based on the second indication information, the second indication information indicates 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;
  • the processing unit 1102 determines the target server of the first tag based on the first information, it may be specifically configured to: determine the address information of the target server and/or the fifth target server based on the first information. Port number information; determine the target server according to the address information of the target server and/or the fifth port number information.
  • the communication device may include performing the methods/operations/steps described for the first network element (such as the network capability opening function network element) in the above second method embodiment.
  • the module or unit can be a hardware circuit, a software, or a hardware circuit. Road combined with software implementation.
  • the device may also have a structure as shown in Figure 11.
  • the communication device 1100 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, the second message includes the information of the first tag and a first identification, and the first identification is used to determine the target server of the first tag;
  • the processing unit 1102 is configured to determine the target server of the first tag according to the first identification; the sending unit 1103 is used to send the information of the first tag to the target server.
  • the communication device 1100 may also include a storage unit (not shown in Figure 11), which may be used to store a computer program for executing the method/operation/step/action described by the first network element and /or instructions and/or information, etc.
  • a storage unit not shown in Figure 11
  • the communication device 1100 may also include a storage unit (not shown in Figure 11), which may be used to store a computer program for executing the method/operation/step/action described by the first network element and /or instructions and/or information, etc.
  • the processing unit 1102 when determining the target server of the first tag based on the first identification, is specifically configured to: determine based on the first identification and the first corresponding relationship.
  • the sending unit 1103 is further configured to: before the receiving unit 1101 receives the second message, send a first message to the second network element, where the first message includes a first message.
  • the operation instruction and the second tag filter, as well as the first identification, the first operation instruction is used to instruct the second network element to obtain the identification of at least one tag, and the second tag filter is used to according to the identification of different tags. Identifies the corresponding label.
  • the communication device may include modules that perform one-to-one correspondence with the methods/operations/steps/actions described by the second network element in the above second method embodiment or Unit, the module or unit can be a hardware circuit, software, or a combination of hardware circuit and software.
  • the device may also have a structure as shown in Figure 11.
  • the communication device 1100 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, the first message includes a first operation instruction, a second tag filter, and a first identification; wherein the first operation instruction is used to indicate that the The second network element obtains the identification of at least one label, the second label filter is used to determine the corresponding label according to the identification of different labels, the first identification is used to determine the target server of the first label;
  • the processing unit 1102 used to match the second tag filter based on the identity of the first tag according to the first operation instruction to obtain the first tag;
  • the sending unit 1103 is used to send a second message, the second The message includes the information of the first tag and the first identification.
  • the communication device 1100 may also include a storage unit (not shown in Figure 11), which may be used to store a computer program for executing the method/operation/step/action described by the second network element and /or instructions and/or information, etc.
  • a storage unit not shown in Figure 11
  • the communication device 1100 may also include a storage unit (not shown in Figure 11), which may be used to store a computer program for executing the method/operation/step/action described by the second network element and /or instructions and/or information, etc.
  • the receiving unit 1101 when receiving the first message, may be specifically configured to: receive the first message from the mobility management network element; when the sending unit 1103 sends the second message, Specifically, it may be used to: send the second message to the mobility management network element.
  • the receiving unit 1101 when receiving the first message, may be configured to: receive the first message from the first network element; when the sending unit 1103 sends the second message, specifically May be used to: send the second message to the first network element.
  • an embodiment of the present application also provides a communication device.
  • the communication device adopts the steps performed by the first communication device in the method provided in the embodiment corresponding to Fig. 5A and Fig. 6-8, which may be the same as in Fig.
  • the communication device 1100 shown in FIG. 11 is the same device.
  • the communication device 1200 includes: a transceiver 1201 , a processor 1202 and a memory 1203 . Among them, the transceiver 1201, the processor 1202 and the memory 1203 are connected through the communication bus 1204 to realize data exchange.
  • the communication bus 1204 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc.
  • PCI peripheral component interconnect
  • EISA extended industry standard architecture
  • the communication bus 1204 can be divided into an address bus, a data bus, a control bus, etc. For ease of presentation, only one thick line is used in Figure 12, but it does not mean that there is only one bus or one type of bus.
  • the transceiver 1201 in the communication device 1200 includes the functions of the receiving unit 1101 and the sending unit 1103 in the communication device 1100 described above.
  • the transceiver 1201 is used to support the sending and receiving of information, data, etc. between the communication device 1100 and the first user plane functional network element in the above embodiment.
  • Memory 1203 is used for program code and data of communication device 1200 .
  • the processor 1202 is used to call the program code and data stored in the memory 1203, execute FIG. 5A, and the processing procedures involving the first communication device in the methods shown in FIGS. 6-8 and/or for the technology described in this application. other processes.
  • the communication device 1200 may also include other interfaces, such as optical fiber link interfaces, Ethernet interfaces, microwave link interfaces, copper wire interfaces, etc., to implement communication between the communication device 1200 and other devices (such as access network equipment, policy control network element) interaction.
  • other interfaces such as optical fiber link interfaces, Ethernet interfaces, microwave link interfaces, copper wire interfaces, etc.
  • the processor 1202 may be a central processing unit, ASIC, FPGA or CPLD.
  • the communication device 1200 shown in FIG. 12 only includes a transceiver 1201, a processor 1202 and a memory 1203.
  • the number of transceiver 1201, processor 1202 and memory 1203 may be one or multiple.
  • the communication device 1200 shown in Figure 12 can also implement the method performed by the first user plane functional network element in the method provided by the embodiments corresponding to Figures 5A and Figures 6-8, or can implement the method performed by the first user plane functional network element in Figure 5B and Figure 5B.
  • 9-The method performed by the first network element in the method provided by the embodiment corresponding to Figure 10, or the method performed by the second network element in the method provided by the embodiment corresponding to Figure 5B and Figure 9- Figure 10 can be implemented.
  • the communication device 1200 shown in FIG. 12 may be the same device as the communication device 1100 shown in FIG. 11 described above. Therefore, the implementation of the communication device 1200 that is not described in detail may refer to FIGS. 5A-5B and the relevant descriptions in the methods provided by the embodiments corresponding to FIGS. 6-10 or refer to the relevant descriptions of the communication device 1200 shown in FIG. 12 above. . No more details will be given here.
  • FIG. 13 is a schematic structural diagram of a chip provided by an embodiment of the present application.
  • the chip 1300 includes an interface circuit 1301 and one or more processors 1302 .
  • the chip 1300 may also include a bus. in:
  • the processor 1302 may be an integrated circuit chip with signal processing capabilities. During the implementation process, each step of the above eye tracking method can be completed by instructions in the form of hardware integrated logic circuits or software in the processor 1302 .
  • the above-mentioned processor 1302 can be a general-purpose processor, a digital communicator (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. .
  • DSP digital communicator
  • ASIC application-specific integrated circuit
  • FPGA field programmable gate array
  • a general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.
  • 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, and can send the processed information through the interface circuit 1301.
  • the chip also includes a memory 1303.
  • the memory 1303 may include a read-only memory and a random access memory, and provides operating instructions and data to the processor. Portion of memory 1303 may also include non-volatile random access memory (NVRAM).
  • NVRAM non-volatile random access memory
  • the memory stores executable software modules or data structures
  • the processor can perform corresponding operations by calling operating instructions stored in the memory (the operating instructions can be stored in the operating system).
  • the chip may be used in the first communication device involved in the embodiment of the present application.
  • the interface circuit 1301 may be used to output execution results of the processor 1302.
  • the communication method provided by one or more embodiments of the present application reference may be made to the foregoing embodiments, which will not be described again here.
  • interface circuit 1301 and the processor 1302 can be realized through hardware design, software design, or a combination of software and hardware, which are not limited here.
  • embodiments of the present application also provide a computer-readable storage medium, which stores some instructions. When these instructions are called and executed by the computer, the computer can complete the above method embodiments and method implementation. Examples of any of the possible designs involved.
  • the computer-readable storage medium is not limited. For example, it may be RAM (dom-access memory), ROM (read-only memory), etc.
  • this application also provides a computer program product, which when called and executed by a computer can complete the method embodiments and the methods involved in any possible design of the above method embodiments.
  • this application also provides a chip, which may include a processor and an interface circuit, for completing the above method embodiments and any possible implementation of the method embodiments.
  • a chip which may include a processor and an interface circuit, for completing the above method embodiments and any possible implementation of the method embodiments.
  • method where "coupling" means that two components are directly or indirectly combined with each other. This combination can be fixed or movable. This combination can allow flowing liquid, electricity, electrical signals or other types of signals to be transmitted between the two components. communicate between components.
  • At least one involved in the embodiments of this application includes one or more; where multiple means greater than or equal to two.
  • words such as “first” and “second” are only used for the purpose of distinguishing the description, and cannot be understood as indicating or implying relative importance, nor can they be understood as indicating. Or suggestive order.
  • each functional module in each embodiment of the present application may be integrated into one processing unit. In the device, it can exist physically alone, or two or more modules can be integrated into one module.
  • the above integrated modules can be implemented in the form of hardware or software function modules.
  • Embodiments of the present application provide a computer-readable storage medium that stores a computer program.
  • the computer program package include instructions for executing the above method embodiments.
  • Embodiments of the present application provide a computer program product containing instructions that, when run on a computer, cause the computer to execute the above method embodiments.
  • each functional module in each embodiment of the present application may be integrated into one processing unit. In the device, it can exist physically alone, or two or more modules can be integrated into one module.
  • the above integrated modules can be implemented in the form of hardware or software function modules.
  • Computer-readable media includes computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • Storage media can be any available media that can be accessed by the computer.
  • computer readable media may include RAM, ROM, electrically erasable programmable read only memory (EEPROM), compact disc read-only memory (CD- ROM) or other optical disk storage, magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures that can be accessed by a computer. also. Any connection can be adapted to a computer-readable medium.
  • RAM random access memory
  • ROM read only memory
  • EEPROM electrically erasable programmable read only memory
  • CD- ROM compact disc read-only memory
  • magnetic disk storage media or other magnetic storage devices or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures that can be accessed by a computer.
  • Any connection can be adapted to a computer-readable medium.
  • disk and disc include compact disc (CD), laser disc, optical disc, digital video disc (digital video disc, DVD), floppy disk and Blu-ray disc, where Disks usually copy data magnetically, while discs use lasers to copy data optically. Combinations of the above should also be included within the scope of protection of computer-readable media.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Computer And Data Communications (AREA)
  • Communication Control (AREA)

Abstract

一种通信方法和装置，该方法包括：第一通信装置接收第一请求，该第一请求指示该第一通信装置获取第一标签的信息；该第一通信装置根据该第一请求，获取该第一标签的信息，该第一标签的信息包含该第一标签的标识；该第一通信装置根据该第一标签的标识，确定第一通信会话，该第一通信会话用于传输该第一标签的信息；该第一通信装置通过该第一通信会话，发送该第一标签的信息。通过该方法，该第一通信装置在获取该第一标签的信息后，为该第一标签的信息确定了对应的第一通信会话，进而可保证该第一通信装置通过该第一通信会话，能有效且准确地传输该第一标签的信息。

Description

一种通信方法和装置
相关申请的交叉引用
本申请要求在2022年06月22日提交中华人民共和国知识产权局、申请号为202210714032.2、发明名称为“一种通信方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种通信方法和装置。
背景技术
随着物联网技术的发展，其应用场景也越加广泛，例如仓库/运输/物资/固定资产管理。通常物联网技术可以包括无源或半无源物联网(Passive IoT，P-IoT)技术，即网络的节点可以从环境中获得能量，以用于支撑网络中数据的感知、传输和分布式计算等。
在无源或半无源物联网架构中，通常可包括无源的标签或半无源的标签、读写器(reader)以及服务器，读写器(Reader)可以通过无线射频方式对标签(或射频卡)进行读写，以识别标签(或射频卡)，并与标签(或射频卡)进行信息和数据的交互。标签(即半无源的标签)也可以通过获取太阳能等方式存储电能，主动地向读写器发送某一频率的信号，读写器接收该信号携带的信息并进行解码，进一步地将解码后的信息发送给中央信息系统进行对应的数据处理。
然而，在现有标签的读写方式中，当终端设备作为读写器时，由于读写器可能被多个企业共享，且未涉及通过标签提供企业的信息，使得读写器无法直接与目标标签的归属企业服务器建立用户面通道。另外，读写器也未针对不同标签提供的企业的信息，执行不同的路由策略，使得网络无法识别标签的归属企业并为不同的企业提供不同的通信服务。
因此，亟需提出一种通信方法，可以有效且准确地传输标签的信息。
发明内容
一种通信方法和装置，可以有效且准确地传输标签的信息。
第一方面，本申请实施提供第一种通信方法，该方法可以由第一通信装置执行，该第一通信装置可以为阅读器(或阅读器对应的控制器、芯片)，也可以为与阅读器建立通信连接的终端设备(或终端设备对应的控制器、芯片)。其中，终端设备可以为但不限于为计算机、手机、平板电脑、或其它能够实现与阅读器建立通信连接的设备，对此不做限定。该方法具体包括以下步骤：第一通信装置接收第一请求，该第一请求指示该第一通信装置获取第一标签的信息；该第一通信装置根据该第一请求，获取该第一标签的信息，该第一标签的信息包含该第一标签的标识；该第一通信装置根据该第一标签的标识，确定第一通信会话，该第一通信会话用于传输该第一标签的信息；该第一通信装置通过该第一通信会话，发送该第一标签的信息。
示例性的，若用于请求获取该第一标签的信息的设备为该第一标签归属企业的应用服 务器，因此，该第一通信装置可以从该应用服务器接收该第一请求。并且该第一通信装置通过第一通信会话，将该第一标签的信息发送给该应用服务器，本申请对该第一通信装置具体通过哪种传输路径向该应用服务器发送该第一标签的信息不做具体限定。
在本申请方案中，第一通信装置在基于第一请求获取第一标签的信息后，可以确定专门用于传输该第一标签的信息的第一通信会话，从而可以有效地提高第一通信装置传输该第一标签的信息的准确性。
一种可能的实施方式中，该第一通信装置根据该第一标签的标识，确定第一通信会话，包括：该第一通信装置根据该第一标签的标识和第一路由策略信息，从至少一个通信会话中确定该第一通信会话，该第一路由策略信息包含该第一标签的标识和该第一通信会话的标识的对应关系。
其中，该第一路由策略信息可以为基于现有的用户设备路由选择策略(ue route selection policy，URSP)进行改进的，即在该URSP策略中新增了标签的标识和通信会话的标识的对应关系，以使该第一通信装置还可以基于标签的标识，确定合适的通信会话。
需要注意的是，该第一路由策略信息还可以包括该第一标签的标识和目标服务器的地址信息和/或端口号信息的对应关系，因此，第一通信装置还可以根据该第一路由策略信息中包含的该对应关系，确定该第一标签对应的目标服务器的地址信息和/或端口号信息，进一步，再根据服务器的地址信息和/或端口号信息与通信会话之间的对应关系(也可包含在第一路由策略信息中或存储于第一通信装置)，确定该目标服务器的地址信息和/或端口号信息对应的第一通信会话。本申请对第一通信装置如何根据第一路由策略信息确定第一通信会话的具体方式不做限定。
通过该实施方式，由于第一路由策略信息中包含第一标签的标识以及该第一标签的标识和该第一通信会话的标识对应关系，该第一通信装置可以根据第一路由策略信息，准确地确定传输该第一标签的信息所使用的第一通信会话，从而可以提高传输该第一标签的信息的准确性。
一种可能的实施方式中，该第一通信装置接收第一请求之前，还包括：该第一通信装置建立至少一个通信会话，该至少一个通信会话中包括该第一通信会话；该第一通信装置建立至少一个路由策略信息，每个该路由策略信息包括对应的标签和通信会话的标识的对应关系。
通过该实施方式，该第一通信装置在接收用于指示获取第一标签的信息的请求之前，该第一通信装置需要建立至少一个通信会话，该第一通信会话中包括了第一通信会话，并建立对应的路由策略信息，使得该路由策略信息中包括对应标签和通信会话的标识的对应关系。因此，第一通信装置建立至少一个传输标签的信息的有效的通信路径和对应的路由策略信息，后续该第一通信装置可以根据第一标签的标识和对应的路由策略，从该至少一个通信会话为传输该第一标签的信息选择合适的通信会话，从而可保证传输该第一标签的信息的有效性和准确性。
在本申请方案中，因该第一通信装置传输标签的信息的路径可能不同，因此，该第一通信装置建立第一通信会话，可以包括但不限于包括以下几种方式：
第一种实现方式中，该第一通信装置建立该第一通信会话，包括：该第一通信装置发送第一会话请求消息，该第一会话请求消息包含第一指示信息，该第一指示信息指示该第一标签的归属企业信息；该第一通信装置接收第一响应消息，该第一响应消息用于响应该 第一会话请求消息，该第一响应消息中包含第一目标地址信息，和/或第一端口号信息，其中，该第一目标地址信息，和/或该第一端口号信息是根据该第一指示信息确定的；该第一通信装置根据该第一目标地址信息，和/或该第一端口号信息，建立该第一通信会话；该第一目标地址信息，和/或该第一端口号信息用于确定目标服务器，该目标服务器为该归属企业的服务器。
示例性的，该第一通信装置在建立该第一通信会话流程可以参考现有的PDU会话建立的流程实现，此处不再具体描述，但区别在于：本申请实施例中第一通信装置在发送会话请求消息中携带了用于指示标签归属企业信息的第一指示信息。其中，该第一目标地址信息，和/或该第一端口号信息可以为该流程中的会话管理功能SMF网元根据该第一指示信息(或第一标签归属企业信息)确定的，也可以由其它网元根据该第一指示信息(或第一标签归属企业信息)确定的，再发送给会话管理功能SMF网元，本申请对此不做具体限定。
其中，标签归属企业信息可以为但不限于为数据网元名称DNN和/或网元切片辅助选择信息(network slice selection assistance information，NSSAI)。上述的第一指示信息可以用于指示接入标签归属企业的DNN和/或NSSAI，或者该第一指示信息可以为该接入标签归属企业的DNN和/或NSSAI，本申请对此不做限定。该DNN和/或NSSAI指示该第一通信装置请求建立的目标企业的网络信息。
通过实施方式，基于第一标签归属企业信息确定第一标签的目标服务器的地址和/或端口号信息，从而可以有效地且准确地建立该第一通信装置与第一标签的目标服务器之间的通信连接(即第一通信会话)。
基于该第一种实现方式下，该第一通信装置可以与目标服务器之间直接建立第一通信会话。该第一通信装置通过该第一通信会话，发送该第一标签的信息，包括：该第一通信装置通过该第一通信会话，向该目标服务器发送该第一标签的信息。
通过该实施方式，第一通信装置可以通过该第一通信装置与目标服务器之间的第一通信会话，有效且准确地将该第一标签的信息发送给该目标服务器。
第二种实现方式中，该第一通信装置建立该第一通信会话，包括：该第一通信装置发送第二会话请求消息，该第二会话请求消息包含第二指示信息，该第二指示信息指示该第一标签的归属企业信息；该第一通信装置接收第二响应消息，该第二响应消息用于响应该第二会话请求消息，该第二响应消息中包含第二目标地址信息，和/或第二端口号信息；其中，该第二目标地址信息，和/或该第二端口号信息是根据该第二指示信息确定的；该第一通信装置根据该第二目标地址信息，和/或该第二端口号信息，建立该第一通信会话；该第二目标地址信息，和/或该第二端口号信息用于确定第一用户面功能网元，该第一用户面功能网元是为该归属企业提供服务的用户面网元。
示例性的，该第一通信装置在建立该第一通信会话流程可以参考现有的PDU会话建立/修改的流程实现，此处不再具体描述。其中，该第二目标地址信息，和/或该第二端口号信息可以为该流程中的会话管理功能SMF网元根据该第二指示信息(或第一标签归属企业信息)确定的，也可以由其它网元根据该第二指示信息(或第一标签归属企业信息)确定的，再发送给会话管理功能SMF网元，本申请对此不做具体限定。
其中，标签归属企业信息可以为但不限于为DNN和/或NSSAI。上述的第二指示信息可以用于指示接入标签归属企业的DNN和/或NSSAI，或者该第二指示信息可以为该接入 标签归属企业的DNN和/或NSSAI，本申请对此不做限定。该DNN和/或NSSAI指示该第一通信装置请求建立的目标企业的网络信息。
可选地，标签归属企业信息可以为数据网元名称DNN。
通过该第二种实现方式，基于第一标签归属企业信息确定第一标签的第一用户面功能网元的地址信息和/或端口信息，从而可以有效地且准确的建立该第一通信装置与该第一标签的第一用户面功能网元之间的通信连接(即第一通信会话)。
基于该第二种实现方式下，该第一通信装置可以与第一用户面功能网元之间建立第一通信会话。该第一通信装置通过该第一通信会话，发送该第一标签的信息，包括：该第一通信装置通过该第一通信会话，向该第一用户面功能网元发送该第一标签的信息。
通过该第二种实现方式，该第一通信装置还可以通过该第一用户面功能网元将该第一标签的信息发送给目标服务器。
第二方面，本申请实施提供第一种通信方法，该方法可以由第一用户面功能网元执行，也可以由第一用户面功能网元对应的芯片执行，对此不做限定。该方法具体包括以下步骤：第一用户面功能网元接收第一标签的信息和第一信息，该第一信息用于确定该第一标签的目标服务器；该第一用户面功能网元根据该第一信息，确定该第一标签的目标服务器；该第一用户面功能网元将该第一标签的信息发送给该目标服务器。
本申请方案中，第一用户面功能网元接收第一标签的信息和第一信息，由于该第一信息用于确定该第一标签的目标服务器，因此，该第一用户面功能网元可以根据该第一信息，确定该第一标签的目标服务器，进而可以将该第一标签的信息有效地且准确地发送给该目标服务器。
一种可能的实施方式中，该第一用户面功能网元接收第一信息，包括：该第一用户面功能网元接收N4会话请求消息，该N4会话请求消息中包括该第一信息，该第一信息指示第一标签过滤器，该第一标签过滤器用于根据标签的标识匹配对应的服务器；
在该实施方式下，该第一用户面功能网元根据该第一信息，确定该第一标签的目标服务器，包括：该第一用户面功能网元根据该第一信息，确定该第一标签过滤器；该第一用户面功能网元基于该第一标签的标识，使用该第一标签过滤器匹配到该第一标签的目标服务器。
示例性的，该第一用户面功能UPF网元可在PDU会话建立/修改的过程中，从会话管理功能SMF网元接收该N4会话请求消息，该N4会话请求消息中包括第一消息。
通过该实施方式，该第一用户面功能网元通过接收N4会话请求消息，获取该N4会话请求消息中携带的第一消息，该第一消息指示第一标签过滤器，因此，该第一用户面功能网元可以根据该第一信息确定第一标签过滤器，该第一标签过滤器用于根据标签的标识匹配对应的服务器，进而该第一用户面功能网元基于该第一标签的标识，并使用该第一标签过滤器，可以准确地匹配到该第一标签的目标服务器。
一种可能的实施方式中，该第一用户面功能网元接收第一标签的信息，包括：该第一用户面功能网元从第一通信装置接收该第一标签的信息。
在该实施方式下，该第一用户面功能网元接收第一信息，包括：该第一用户面功能网元接收N4会话请求消息，该N4会话请求消息中包括该第一信息，该第一信息指示该第一通信装置的地址信息和/或该第一通信装置发送该第一标签的信息的第三端口号信息；
进一步的，该第一用户面功能网元根据该第一信息，确定该第一标签的目标服务器， 包括：该第一用户面功能网元根据该第一信息，确定该第一通信装置的地址信息和/或该第三端口号信息；该第一用户面功能网元根据该第一通信装置的地址信息和该第三端口号信息，以及第一映射信息，确定该第一标签的目标服务器；其中，该第一映射信息中包括该第一通信装置的地址信息和/或端口号信息与服务器的标识的对应关系。
其中，该第一映射信息中包括第一通信装置的地址信息和/或端口号信息与服务器的标识的对应关系可以为事先配置好的且已知的关系。
通过该实施方式，第一用户面功能网元从第一通信装置接收该第一标签的信息，此时，该第一用户面功能网元接收N4会话请求消息，其中包括的第一信息指示该第一通信装置的地址信息和/或该第一通信装置发送该第一标签的信息的第三端口号信息时，那么该第一用户面功能网元根据该第一通信装置的地址信息和/或该第一通信装置发送该第一标签的信息的第三端口号信息以及第一映射信息，可以准确地确定第一标签的目标服务器。
一种可能的实施方式中，该第一用户面功能网元接收第一信息，包括：该第一用户面功能网元接收N4会话请求消息，该N4会话请求消息中包括该第一信息，该第一信息指示该第一用户面功能网元上接收该第一标签的信息的第四端口号信息；该第一用户面功能网元根据该第一信息，确定该第一标签的目标服务器，包括：该第一用户面功能网元根据该第一信息，确定该第一用户面功能网元上接收该第一标签的信息的第四端口号信息；该第一用户面功能网元根据该第四端口号信息和第二映射信息，确定该第一标签的目标服务器；其中，该第二映射信息中包括该第一用户面功能网元上的端口号信息和服务器的标识的对应关系。
通过该实施方式，第一用户面功能网元接收N4会话请求消息，其中包括的第一信息指示该第一用户面功能网元上接收该第一标签的信息的第四端口号信息时，那么该第一用户面功能网元根据该第四端口号信息和第二映射信息，可以准确地确定该第一标签的目标服务器。
一种可能的实施方式中，该第一用户面功能网元接收第一信息，包括：该第一用户面功能网元接收N4会话请求消息，该N4会话请求消息中包括该第一信息，该第一信息指示该目标服务器的地址信息和/或该目标服务器上用于接收该第一标签的信息的第五端口号信息；其中，该目标服务器的地址信息和/或该第五端口号信息是根据第二指示信息确定的，该第二指示信息指示该第一标签的归属企业信息，该第二指示信息携带在第一通信装置发送的第二会话请求消息中；该第一用户面功能网元根据该第一信息，确定该第一标签的目标服务器，包括：该第一用户面功能网元根据该第一信息，确定该目标服务器的地址信息和/或该第五端口号信息；该第一用户面功能网元根据该目标服务器的地址信息和/或该第五端口号信息，确定该目标服务器。
通过该实施方式，第一用户面功能网元接收N4会话请求消息，其中包括的第一信息指示该目标服务器的地址信息和/或该目标服务器上用于接收该第一标签的信息的第五端口号信息时，那么该第一用户面功能网元根据该目标服务器的地址信息和/或该目标服务器上用于接收该第一标签的信息的第五端口号信息，可以准确地确定该第一标签的目标服务器。
第三方面，本申请实施提供第二种通信方法，该方法可以由第一网元执行，也可以由第一网元对应的芯片执行，对此不做限定。该方法具体包括以下步骤：第一网元接收第二消息，该第二消息中包括第一标签的信息和第一标识，该第一标识用于确定该第一标签的 目标服务器；该第一网元根据该第一标识，确定该第一标签的目标服务器；该第一网元将该第一标签的信息发送给该目标服务器。
示例性的，第一网元可以从第二网元接收该第二消息，该第一网元可以为网络开放功能NEF网元，该第二网元可以为第一通信装置(例如具备读写器功能的终端设备)或接入与移动性管理功能AMF网元。
本申请的该方案中，第一网元获取第一标签的信息和第一标识，由于该第一标识用于确定该第一标签的目标服务器，因此，该第一网元可以根据该第一标识确定该第一标签的目标服务器，进而可以准确地将该第一标签的信息发送给该目标服务器。
一种可能的实施方式中，该第一网元根据该第一标识，确定该第一标签的目标服务器，包括：该第一网元根据该第一标识和第一对应关系，确定该第一标签的目标服务器，其中，该第一对应关系包括该第一标识与该目标服务器的对应关系。
通过该实施方式，使得该第一网元可以有效且准确地确定对应的目标服务器。
一种可能的实施方式中，该第一网元从第二网元获取第二消息之前，还包括：该第一网元向第二网元发送第一消息，该第一消息中包括第一操作指令和第二标签过滤器，以及该第一标识，该第一操作指令用于指示该第二网元根据该第一标识从至少一个标签的标识中获取该第一标签的标识，该第二标签过滤器用于根据不同标签的标识确定对应的标签的信息。
需要注意的是，该第一标识可以为用于标识目标服务器的信息，例如该第一标识可以为第一消息的标识，或者该第一标识可以为第一操作指令的标识，且该第一消息的标识与该目标服务器存在一一对应的关系，本申请对此不做具体限定。
通过该实施方式，第一网元向第二网元发送第一操作指令和第二标签过滤器，以及第一标识，以使得该第二网元可以基于该第一操作指令和第一标识，以及第二标签过滤器获得第一标签的信息，进而可保证后续该第一网元能从该第二网元有效地获取该第一标签的信息和该第一标识后，基于该第一标识准确地确定该第一标签的目标服务器。
第四方面，本申请实施提供第二种通信方法，该方法可以由第二网元执行，也可以由第二网元对应的芯片执行，对此不做限定。该方法具体包括以下步骤：第二网元接收第一消息，该第一消息中包括第一操作指令和第二标签过滤器，以及第一标识；其中，该第一操作指令用于指示该第二网元获取至少一个标签的标识，该第二标签过滤器用于根据不同标签的标识确定对应的标签的信息，该第一标识用于确定第一标签的目标服务器；该第二网元根据该第一操作指令和该第一标识，获取第一标签的标识，并基于该第一标签的标识匹配该第二标签过滤器，得到该第一标签的信息；该第二网元发送第二消息，该第二消息中包括该第一标签的信息和该第一标识。
示例性的，该第一网元可以为第一通信装置，例如具有读写器功能的终端设备，该第二网元也可以为接入和接入与移动性管理功能AMF网元。
在本申请中，第二网元接收第一消息，该第一消息中包括第一操作指令和第二标签过滤器以及第一标识，然后该第二网元可以根据该第一操作指令执行标签操作，从至少一个标签的标识中获取第一标签的标识，并基于第一标签的标识匹配该第二标签过滤器，可以准确地得到该第一标签的信息，并向第一网元发送该第一标签的信息和该第一标识，进而以使得该第一网元可以根据该第一标识，快速且准确地确定该第一标签的目标服务器。
一种可能的实施方式中，该第二网元接收第一消息，包括：该第二网元从移动性管理 功能网元接收该第一消息；该第二网元发送第二消息，包括：该第二网元向该移动性管理功能网元发送该第二消息。
示例性的，该第二网元为第一通信装置，例如具有读写器功能的终端设备。该终端设备可以通过AMF网元(即移动性管理功能网元)接收来自NEF网元(即第一网元)的第一消息，终端设备基于该第一消息确定第一标签后，可以向该AMF网元发送该第一标签的信息，进而该AMF网元再向该NEF网元发送该第一标签的信息。
通过该实施方式，该第二网元可以从移动性管理功能网元有效地接收上述的第一消息，并在确定第一标签后，向该移动性管理功能网元发送包含该第一标签的信息的第二消息。
一种可能的实施方式中，该第二网元从第一网元接收该第一消息；该第二网元发送第二消息，包括：该第二网元向该第一网元发送该第二消息。
示例性的，该第二网元为AMF网元(即移动性管理功能网元)，AMF网元从NEF网元(即第一网元)接收第一消息，该AMF网元基于该第一消息，确定该第一标签后，向该NEF网元发送该第一标签的信息。
需要注意的是，该第二网元为AMF网元的情况下，该第二网元可以先从第一通信装置(如具备读写器功能的终端设备)获取所有的标签的信息，包括第一标签的信息。
通过该实施方式，该第二网元从第一网元直接接收该第一消息，基于该第一消息确定第一标签后，向该第一网元发送包含该第一标签的信息的第二消息。
第五方面，本申请实施提供一种通信装置，该通信装置可应用于第一通信装置，具有实现上述第一方面或上述第一方面的任意一种可能的实施方式的功能；或者，该通信装置可应用于第一用户面功能网元，具有实现上述第二方面或上述第二方面的任意一种可能的设计中的方法的功能。该装置可以包括：接收单元、处理单元和发送单元。
第六方面，本申请还提供一种通信装置，该通信装置可应用于第一网元，具有实现上述第三方面或上述第三方面的任意一种可能的实施方式的功能；或者，该通信装置可应用于第二网元，具有实现上述第四方面或上述第四方面的任意一种可能的设计中的方法的功能。该装置可以包括：接收单元、处理单元和发送单元。
第七方面，本申请还提供一种通信装置，该通信装置可应用于第一通信装置，该通信装置包括处理器，用于实现上述第一方面或上述第一方面的任意一种可能的实施方式的功能；或者，该通信装置可应用于第一用户面功能网元，用于实现上述第二方面或上述第二方面的任意一种可能的设计中的方法的功能。可选地，该通信装置还包括收发器，用于实现该通信装置的通信功能。
第八方面，本申请还提供另一种通信装置，该通信装置可应用于第一网元，该通信装置包括处理器，用于实现上述第三方面或上述第三方面的任意一种可能的实施方式的功能；或者，该通信装置可应用于第二网元，用于实现上述第四方面或上述第四方面的任意一种可能的设计中的方法的功能。可选地，该通信装置还包括收发器，用于实现该通信装置的通信功能。
第九方面，本申请还提供一种通信系统，该系统包括用于执行上述第一方面提供的方法的第一通信装置(如终端设备)，以及用于执行上述第二方面提供的方法的第一用户面功能网。
第十方面，本申请还提供一种通信系统，该系统包括用于执行上述第三方面提供的方法的第一网元(如网络能力开放功能网元)，以及用于执行上述第四方面提供的方法的第 二网元(第一通信装置，例如具备读写功能的终端设备，或接入和移动性功能管理网元)。
第十一方面，本申请实施例还提供一种计算机存储介质，该存储介质中存储软件程序，该软件程序在被一个或多个处理器读取并执行时可实现上述第一方面或其中任意一种可能的实施方式提供的方法，或者实现上述第二方面或其中任意一种可能的实施方式提供的方法；或者该软件程序在被一个或多个处理器读取并执行时可实现上述第三方面或其中任意一种可能的实施方式提供的方法，或者实现上述第四方面或其中任意一种可能的实施方式提供的方法。
第十二方面，本申请实施例还提供一种包含指令的计算机程序产品，当其在计算机上运行时，使得上述第一方面或其中任一种可能的实施方式提供的方法执行，或者使得上述第二方面或其中任一种可能的实施方式提供的方法执行；或者当其在计算机上运行时，使得上述第三方面或其中任一种可能的实施方式提供的方法执行，或者使得上述第四方面或其中任一种可能的实施方式提供的方法执行。
第十三方面，本申请实施例还提供一种芯片系统，该芯片系统包括处理器，用于支持第一通信装置实现上述第一方面中所涉及的功能；或者用于支持第一用户面功能网元实现上述第二面中所涉及的功能；或者用于支持第一网元实现上述第三面中所涉及的功能；或者用于支持第二网元实现上述第四方面中所涉及的功能。
在一种可能的设计中，所述芯片系统还包括存储器，所述存储器，用于保存装载装置执行的必要的程序指令和数据。该芯片系统，可以由芯片构成，也可以包含芯片和其他分立器件。
上述第五方面和第七方面以及其中任一种可能的实施方式可以达到的技术效果，可以参照上述第一方面和第二方面以及其中任意一种可能的实施方式，上述第六方面和第八方面以及其中任一种可能的实施方式可以达到的技术效果，可以参照上述第三方面和第四方面以及其中任意一种可能的实施方式，这里不再重复赘述。
附图说明
图1为一种无源或半无源物联网的标签读写的示意图；
图2为一种读写器对标签(如P-IoT Tag)执行盘点的过程示意图；
图3A为第一种标签信息的传输路径的示意图；
图3B为第二种标签信息的传输路径的示意图；
图3C为第三种标签信息的传输路径的示意图；
图4为本申请实施例提供的一种网络架构的示意图；
图5A为本申请实施例提供的一种通信方法的流程示意图；
图5B为本申请实施例提供的另一种通信方法的流程示意图；
图6为本申请实施例提供的另一种通信方法的流程示意图；
图7为本申请实施例提供的第一个实施例的流程示意图；
图8为本申请实施例提供的第二个实施例的流程示意图；
图9为本申请实施例提供的第三个实施例的流程示意图；
图10为本申请实施例提供的第四个实施例的流程示意图；
图11为本申请实施例提供的一种通信装置的结构示意图；
图12为本申请实施例提供的一种通信设备的结构示意图；
图13为本申请实施例提供的一种芯片装置的结构示意图。
具体实施方式
本申请实施例提供了一种通信方法和装置，其中，方法和装置是基于相同或相似技术构思的，由于方法及装置解决问题的原理相似，因此方法与装置的实施可以相互参见，重复之处不再赘述。
为便于理解本申请实施例的技术方案，下面先对现有的无源或半无源物联网技术进行简单介绍。
随着物联网技术的发展，其应用场景也越加广泛，例如仓库/运输/物资/固定资产管理。通常物联网技术可以包括无源或半无源物联网(passive internet of things，P-IoT)技术，即网络的节点可以从环境中获得能量，以用于支撑网络中数据的感知、传输和分布式计算等。
在无源或半无源物联网架构中，通常可以包括无源的标签或半无源的标签、读写器(Reader)以及服务器，读写器(Reader)可以通过无线射频方式对标签(或射频卡)进行读写，以识别标签(或射频卡)，并与标签(或射频卡)进行信息和数据的交互。标签(即半无源的标签)也可以通过获取太阳能等方式存储电能，主动地向读写器发送某一频率的信号，读写器接收该信号携带的信息并进行解码，进一步地将解码后的信息发送给中央信息系统进行对应的数据处理。尽管本文以无源标签/半无源标签来定义物联网技术中的终端名称，本申请也同样适用于其他的使用相似物联网技术的终端名称，如储能标签，无源储能标签，零功耗终端等。
如图1所示，其示出了一种无源或半无源物联网的标签读写的示意图，具体可以包括以下步骤：
S101：P-IoT应用(P-IoT APP)向读写器(Reader)发送盘点/接入规则。
相应的，读写器接收该盘点/接入规则。
例如，该盘点/接入规则可以为：每小时盘点一次，以及获取标签1、标签2，以及标签3的存储区的信息。
S102：读写器对标签(如P-IoT Tag)执行盘点，获取标签的标识。
例如，读写器根据接收的盘点/接入规则对标签执行盘点，例如每小时对待接入的标签执行一次盘点，并获取待接入的标签的标识。
应理解的是，读写器对标签进行盘点的流程，可以理解为读写器与标签(如P-IoT Tag)建立连接和交互，并获取彼此信息的流程。通常每个标签有相应的标识，包括但不限于电子产品代码(electronic product code，EPC)和标签识别号(tag identifier，TID)。
在盘点的流程中，标签会将自己的EPC或TID发送给读写器，使得读写器可以获知有哪些标签在自己的覆盖范围内，并上报给中间件和服务器。
S103：读写器(Reader)对P-IoT Tag执行标签接入。
读写器(Reader)在执行盘点完成后，待接入的标签执行标签接入该读写器(Reader)，完成标签接入的过程，以使得后续读写器(Reader)可以获取接入的标签的信息。
S104：读写器(Reader)将盘点信息和标签接入的信息反馈给P-IoT APP。
读写器(Reader)将标签盘点信息/标签接入的信息反馈给P-IoT APP。
针对上述步骤S102中读写器对标签(如P-IoT Tag)执行盘点的过程，参考图2所示， 具体流程如下：
S201：读写器向P-IoT Tag发送选择Select命令。
相应的，P-IoT Tag接收Select命令。
具体的，读写器在接收盘点命令后，会生成Select命令，然后向P-IoT Tag发送Select命令。其中，该盘点命令中包括标签的范围，例如某些特定范围内的EPC/TID。标签在接收(监听)到Select命令后，盘点自己是否数据该Select命令中需要判断的标签范围。若属于，则继续监听后续的Query命令，若不属于，则该标签后续不再执行以下步骤(即不做任何动作)。
S202：读写器向P-IoT Tag发送Query命令。
相应的，当P-IoT Tag接收到有效的Query命令后，会产生一个随机数。
S203：P-IoT Tag向读写器发送RN-16。
例如，随机数为0的标签在收到有效的Query命令后，向读写器反馈一个临时口令RN-16，即一个16bit的随机数。
S204：读写器向P-IoT Tag发送确认(acknowledgement，ACK)命令。
当读写器收到来自标签发送的随机数后，会向该标签发送一个ACK命令，该命令中包含了刚刚收到的随机数(RN16)。
S205：P-IoT Tag验证ACK命令中的随机数是否正确。
若P-IoT Tag验证ACK命令中的随机数正确，则执行下一个步骤S206。
S206：P-IoT Tag向读写器发送EPC码。
同时该P-IoT Tag向读写器发送自身的EPC码之后，进入短暂的休眠状态。
读写器收到标签的EPC码后，完成对该标签的盘点。
可选地，读写器会继续发送QueryRep命令，收到QueryRep的标签会将原有的随机数减1，并重新执行上述步骤S203-S206，直至所有的标签全部盘点完成。
现有的3GPP网络中，以UE作为读写器时，其支持无源或半无源物联网执行读写过程主要可以包括以下几种传输路径。
第一种传输方式：参考图3A所示，由读写器执行标签的管理，并通过读写器直接与企业服务器建立用户面连接，进而标签的信息(或指令)可以通过读写器建立的用户面连接实现传输。
第二种传输路径：参考图3B所示，由UPF网元执行标签的管理，并通过读写器与UPF网元建立用户面连接，以及UPF网元与企业服务器建立用户面连接，进而读写器读写的标签的信息(或指令)均可以通过上述的用户面连接实现传输。
第三种传输路径：参考图3C所示，可以通过控制面通道传输，即服务器通过NEF网元向AMF网元发送指令，进而AMF网元可以从UE获取标签的信息和/或数据，由AMF网元或控制面(control plane，CP)网元)执行标签的管理，并可以通过NEF网元向应用服务器发送标签的信息。
然而，在现有标签的读写方式中，当终端设备作为读写器时，由于读写器可能被多个企业共享，且未涉及通过标签提供企业的信息，使得读写器无法直接与目标标签的归属企业服务器建立用户面通道。另外，读写器也未针对不同标签提供企业的信息，执行不同的路由策略，使得网络无法识别标签的归属企业并为不同的企业提供不同的通信服务。
因此，本申请提出一种通信方法，该方法包括：第一通信装置接收第一请求，该第一 请求指示该第一通信装置获取第一标签的信息，该第一标签的信息包含该第一标签的标识；然后，该第一通信装置根据该第一请求，获取该第一标签的信息；其次，该第一通信装置确定第一通信会话，该第一通信会话用于传输第一标签的信息；最后，该第一通信装置通过该第一通信会话，发送该第一标签的信息。通过该方法，该第一通信装置在获取该第一标签(即目标标签)的信息后，为该第一标签的信息确定了对应的第一通信会话，进而可保证该第一通信装置通过该第一通信会话，能有效且准确地传输该第一标签的信息。
本申请方案可以适用于5G系统架构中，还可以适用于但不限于长期演进(long term evolution，LTE)通信系统，以及未来演进的各种无线通信系统中。
图4示出了本申请实施例提供的一种通信方法所适用的一种网络架构的示意图。如图4所示，该网络架构中可以包括接入网以及核心网。终端设备通过接入网和核心网接入数据网络(data network，DN)。
终端设备可以为用户设备(user equipment，UE)、移动台、移动终端、应用客户端等。终端设备可以广泛应用于各种场景，例如，设备到设备(device-to-device，D2D)、车物(vehicle to everything，V2X)通信、机器类通信(machine-type communication，MTC)、物联网(internet of things，IOT)、虚拟现实、增强现实、工业控制、自动驾驶、远程医疗、智能电网、智能家具、智能办公、智能穿戴、智能交通、智慧城市等。终端设备可以是手机、平板电脑、带无线收发功能的电脑、可穿戴设备、车辆、城市空中交通工具(如无人驾驶机、直升机等)、轮船、机器人、机械臂、智能家居设备等。附图和以下实施例中以UE作为终端设备的一个示例进行说明，后续任意地方出现的UE也可以替换为终端设备或终端设备的其它示例。
接入网用于实现接入有关的功能，可以为特定区域的授权用户提供入网功能，并能够根据用户的级别，业务的需求等确定不同质量的传输链路以传输用户数据。接入网在UE与核心网之间转发控制信号和用户数据。接入网可以包括接入网设备，接入网设备可以是为UE提供接入的设备，可以包括无线接入网(radio access network，RAN)设备和有线接入网设备。RAN设备，主要负责空口侧的无线资源管理、服务质量(quality of service，QoS)管理、数据压缩和加密等功能。RAN设备可以包括各种形式的基站，例如宏基站，微基站(也可称为小站)，中继站，接入点，气球站等。在采用不同的无线接入技术的系统中，具备基站功能的设备的名称可能会有所不同，例如，在5G系统中，称为RAN或者下一代基站(next-generation Node basestation，gNB)，在长期演进(long term evolution，LTE)系统中，称为演进的节点B(evolved NodeB，eNB或eNodeB)。
接入网设备和UE可以是固定位置的，也可以是可移动的。接入网设备和UE可以部署在陆地上，包括室内或室外、手持或车载；也可以部署在水面上；还可以部署在空中的飞机、气球和人造卫星上。本申请的实施例对接入网设备和UE的应用场景不做限定。
核心网负责维护移动网络的签约数据，为UE提供会话管理、移动性管理、策略管理以及安全认证等功能。核心网中包括但不限于以下一个或多个网元：应用功能(application function，AF)网元、统一数据管理(unified data management，UDM)网元、统一数据库(unified data repository，UDR)网元、策略控制功能(policy control function，PCF)网元、会话管理功能(session management function，SMF)网元、接入与移动性管理功能(access and mobility management function，AMF)网元、网络存储功能(network repository function， NRF)网元、鉴权服务器功能(authentication server function，AUSF)网元、网络开放功能(network exposure function，NEF)网元、用户面功能(user plane function，UPF)网元、网络数据分析功能网元(Network Data Analytics Function，NWDAF)网元。
AMF网元，主要负责移动网络中的移动性管理，例如用户位置更新、用户注册网络、用户切换等。
SMF网元，主要负责移动网络中的会话管理，例如会话建立、修改、释放。具体功能例如为用户分配互联网协议(internet protocol，IP)地址，选择提供报文转发功能的UPF等。
UPF网元，主要负责用户数据的转发和接收，可以从数据网络接收用户数据，通过接入网络设备传输给UE；还可以通过接入网设备从UE接收用户数据，转发至数据网络。
UDM网元，包含执行管理签约数据、用户接入授权等功能。
UDR网元，包含执行签约数据、策略数据、应用数据等类型数据的存取功能。
NEF网元，主要用于支持能力和事件的开放。
AF网元，传递应用侧对网络侧的需求，例如，QoS需求或用户状态事件订阅等。AF可以是第三方功能实体，也可以是运营商部署的应用服务，如IP多媒体子系统(IP Multimedia Subsystem，IMS)语音呼叫业务。
PCF网元，主要支持提供统一的策略框架来控制网络行为，提供策略规则给控制层网络功能，同时负责获取与策略决策相关的用户签约信息。PCF网元可以向AMF网元、SMF网元提供策略，例如QoS策略、切片选择策略等。
NRF网元，可用于提供网元发现功能，基于其它网元的请求，提供网元类型对应的网元信息。NRF还提供网元管理服务，如网元注册、更新、去注册以及网元状态订阅和推送等。
AUSF网元，负责对UE进行鉴权，验证UE的合法性。
NWDAF网元，具有提供基于大数据和人工智能等技术的网络数据收集和分析等功能。
DN，其上可部署多种业务，可为UE提供数据和/或语音等服务。例如，DN是某智能工厂的私有网络，智能工厂安装在车间的传感器可为UE，DN中部署了传感器的控制服务器，控制服务器可为传感器提供服务。传感器可与控制服务器通信，获取控制服务器的指令，根据指令将采集的传感器数据传送给控制服务器等。又例如，DN是某公司的内部办公网络，该公司员工的手机或者电脑可为UE，员工的手机或者电脑可以访问公司内部办公网络上的信息、数据资源等。
其中，AF网元、UDM网元、UDR网元、PCF网元、SMF网元、AMF网元、NRF网元、AUSF网元、NEF网元、UPF网元、NWDAF网元，也可以分别简称为AF、UDM、UDR、PCF、SMF、AMF、NRF、AUSF、NEF、UPF、NWDAF，如图1中所示。
图1中Nausf、Nnef、Nnrf、Namf、Npcf、Nsmf、Nudm、Nudr、Naf、Nnwdaf分别为上述AUSF、NEF、NRF、AMF、PCF、SMF、UDM、UDR、AF、NWDAF提供的服务化接口，用于调用相应的服务化操作。N1、N2、N3、N4以及N6为接口序列号，这些接口序列号的含义如下：
1)、N1：AMF与UE之间的接口，可以用于向UE传递非接入层(non access stratum，NAS)信令(如包括来自AMF的QoS规则)等。
2)、N2：AMF与接入网设备之间的接口，可以用于传递核心网侧至接入网设备的无 线承载控制信息等。
3)、N3：接入网设备与UPF之间的接口，主要用于传递接入网设备与UPF间的上下行用户面数据。
4)、N4：SMF与UPF之间的接口，可以用于控制面与用户面之间传递信息，包括控制面向用户面的转发规则、QoS规则、流量统计规则等的下发以及用户面的信息上报。
5)、N6：UPF与DN的接口，用于传递UPF与DN之间的上下行用户数据流。
可以理解的是，上述网元或者功能既可以是硬件设备中的网络元件，也可以是在专用硬件上运行软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能。作为一种可能的实现方法，上述网元或者功能可以由一个设备实现，也可以由多个设备共同实现，还可以是一个设备内的一个功能模块，本申请实施例对此不作具体限定。
下面结合具体实施例介绍本申请的技术方案。
本申请实施例提供了一种通信方法，该方法可适用于但不限于图4的网络架构，并且该方法可以由本申请涉及到的网元执行，或者由涉及到的网元对应的芯片执行，本申请中的网元可以为物理上的实体网元，也可以是虚拟的网元，本申请对涉及的网元的形态不做具体限定。
此外，在本申请实施例中，主要用于执行标签识别的装置称为第一通信装置，该第一通信装置可以为阅读器(或阅读器对应的控制器、芯片)，也可以为与阅读器建立通信连接的终端设备(或终端设备对应的控制器、芯片)。其中，终端设备可以为但不限于为计算机、手机、平板电脑、或其它能够实现与阅读器建立通信连接的设备。并且，需要说明的是，下文中提及的“第一”、“第二”等序数词是用于对多个对象进行区分，以便于描述，并不用于限定多个对象的顺序、时序、优先级或者重要程度。针对执行该实施例中第一通信装置和涉及的网元的具体形态，本申请不做限定。
参阅图5A所示，该图示出了本申请实施例提供的一种通信方法的流程图，具体该可以包括如下步骤：
S501A：第一通信装置从目标服务器接收第一请求。
该第一请求指示该第一通信装置获取第一标签的信息，其中，该第一标签可以是包括符合某一盘存规则的一组标签，示例性的，第一标签可以是某一个区域内的一组标签，或者某一类型的一组标签，或者是包含某些字段的一组标签，或者是归属某个企业/运营商的一组标签。示例性的，第一标签也可以是具体的特定标签标识的标签，其中特定的标签标识可以包含在盘存规则中。
示例性地，第一请求可以是通过用户面发送的数据传输消息，也可以是通过控制面发送的非接入层消息，例如下行非接入层传输消息。
示例性地，第一通信装置可以为读写器，例如UE。若应用服务器(如PIOT服务器)需要获取对应的第一标签的信息，可以向UE发送第一请求，该第一请求指示该UE获取第一标签的信息，该第一标签的信息包含该第一标签的标识(如EPC、TID)，相应的，该UE从应用服务器接收该第一请求。
在本申请方案中，该第一通信装置在接收该第一请求之前，还包括执行标签盘存的过程，或者，该第一通信装置在接收该第一请求之后且在确定第一通信会话之前(或在步骤S501A之后，且步骤S502A之前)，还执行标签盘存的过程，即该第一请求消息中还包含 该第一通信装置执行标签盘存所需的指令信息，其中，该指令信息可以包括但不限于标签盘存范围，标签类型，标签归属企业，标签归属运营商中的一项或多项。具体的标签盘存的过程可以参考上述图2所示的流程，此处不再具体赘述。
通过上述的标签盘存的过程，可以保证第一请求信息指示第一通信装置获取的第一标签(即目标标签)能接入该第一通信装置，进一步的，该第一通信装置可以有效地获取该第一标签的信息。
S502A：第一通信装置根据第一请求，获取该第一标签的信息，该第一标签的信息包含该第一标签的标识。
S503A：第一通信装置根据第一标签的标识，确定第一通信会话，该第一通信会话用于传输第一标签的信息。
在一种实施方式中，第一通信装置根据第一标签的标识，确定第一通信会话，包括：第一通信装置根据第一标签的标识和第一路由策略信息，从至少一个通信会话中确定该第一通信会话，该第一路由策略信息包含该第一标签的标识和该第一通信会话的标识的对应关系。
本申请中的第一路由策略信息可以为改进的用户设备路由选择策略(URSP策略)，即在现有的URSP策略(路由策略)中增加了关于标签的标识信息，从而还可以依据标签的标识，选择传输该标签的信息对应的通信会话。
示例性地，上述的第一路由策略信息具体可以参考下述具体实施例一中表1所示。
可选地，该第一路由策略信息还可以包括该第一标签的标识和目标服务器的地址信息和/或端口号信息的对应关系，因此，第一通信装置还可以根据该第一路由策略信息中包含的该对应关系，确定该第一标签对应的目标服务器的地址信息和/或端口号信息，进一步，再根据服务器的地址信息和/或端口号信息与通信会话之间的对应关系，确定该目标服务器的地址信息和/或端口号信息对应的第一通信会话。本申请对第一通信装置如何根据第一路由策略信息确定第一通信会话的具体方式不做限定。
在一种实施方式中，第一通信装置接收第一请求之前，还包括：第一通信装置建立至少一个通信会话，该至少一个通信会话中包括第一通信会话；该第一通信装置建立至少一个路由策略信息，每个该路由策略信息包括对应的标签和通信会话的标识的对应关系。
其中，该第一通信装置建立第一通信会话可以包括但不限于以下方式：
实现方式一：第一通信装置建立第一通信会话，包括：第一通信装置发送第一会话请求消息，该第一会话请求消息包含第一指示信息，该第一指示信息指示该第一标签的归属企业信息；该第一通信装置接收第一响应消息，该第一响应消息用于响应所述第一会话请求消息，该第一响应消息中包含第一目标地址信息，和/或第一端口号信息，其中，该第一目标地址信息，和/或该第一端口号信息是根据该第一指示信息确定的；该第一通信装置根据该第一目标地址信息，和/或该第一端口号信息，建立该第一通信会话；该第一目标地址信息，和/或该第一端口号信息用于确定目标服务器，该目标服务器为该归属企业的服务器。
可选地，上述的第一指示信息可以是企业的数据网络名称DNN，或者该第一指示信息指示的第一标签归属企业信息可以为该DNN对应的企业信息。
本申请方案中，该第一标签归属企业信息也可以直接携带在第一会话请求消息，并由第一通信装置发送。但是为了减少传输第一会话请求消息的开销，可以通过第一指示信息指示该第一标签归属企业信息，由第一通信装置发送包含该第一指示信息的第一会话请求 消息。
上述实现方式一可以基于上述图3A所示的第一种传输路径实现，第一通信装置可以视为UE(读写器)。
示例性地，UE向AMF网元发送PDU会话建立请求消息(相当于第一会话请求消息)，该第一会话请求消息中包含用于指示第一标签归属企业信息的第一指示信息，AMF网元接收该PDU会话建立请求消息后，选择合适的SMF网元，并向该SMF网元发送PDU会话创建会话上下文请求消息，然后，AMF网元从SMF网元接收PDU会话创建会话上下文响应消息，并从SMF网元接收N1N2消息，该N1N2消息中携带目标PIOT服务器地址(相当于第一目标地址信息)和端口号信息(相当于第一端口号信息)，SMF网元向RAN发送N2 PDU会话请求消息(携带目标PIOT服务器地址和端口号信息)，RAN与UE建立空口资源并向UE发送NAS消息(相当于第一响应消息)，该NAS消息中携带目标PIOT服务器地址和端口号信息。最后，UE可以根据NAS消息中的目标PIOT服务器地址和端口号信息，与目标PIOT服务器建立连接(相当于建立第一通信会话)。
实现方式二：第一通信装置建立第一通信会话，包括：第一通信装置发送第二会话请求消息，该第二会话请求消息包含第二指示信息，该第二指示信息指示该第一标签的归属企业信息；该第一通信装置接收第二响应消息，该第二响应消息用于响应该第二会话请求消息，该第二响应消息中包含第二目标地址信息，和/或第二端口号信息；其中，该第二目标地址信息，和/或该第二端口号信息是根据该第二指示信息确定的；该第一通信装置根据该第二目标地址信息，和/或该第二端口号信息，建立第一通信会话；该第二目标地址信息，和/或该第二端口号信息用于确定第一用户面功能网元，该第一用户面功能网元是为该归属企业提供服务的用户面网元。
上述实现方式二可以基于上述图3B所示的第二种传输路径实现，第一通信装置可以视为UE(读写器)，第一用户面功能网元可以为UPF网元。
在该实现方式二中，还可能包括以下两种情况：
第一种情况：用于传输标签的信息的用户面功能网元仅为一个，即该第一用户面功能网元为公用的用户面功能网元。第一通信装置建立至少一个通信会话中任一个通信会话过程中，该第一通信装置接收的第二目标地址信息，和/或第二端口号信息均相同，且该第二目标地址信息，和/或第二端口号信息均用于指示该第一用户面功能网元。
在第一用户面功能网元侧，可以从会话管理功能网元接收不同的目标地址信息和/或端口号信息，每个目标地址信息和/或端口号信息是根据对应的标签归属企业信息(或用于指示对应的标签归属企业信息的指示信息)确定的，每个目标地址信息和/或端口号信息用于指示对应的一个服务器。
可选地，该标签归属企业信息或者是指示该标签归属企业信息的指示信息可以为企业的数据网络名称DNN。
例如，UE1获取UPF1网元(相当于第一用户面功能网元)的地址信息(相当于第二目标地址信息)和/或对应的端口号信息(相当于第二端口号信息)，该UPF1网元的地址信息和/或对应的端口号信息是根据第一标签归属企业的DNN确定的或者是根据指示第一标签归属企业的DNN的指示信息确定的。进一步的，该UE1根据该UPF1网元的地址信息和/或对应的端口号信息，与该UPF1网元建立第一PDU会话连接(相当于建立了第一通信会话)。UE1针对其它标签归属企业，建立PDU会话均可以参考该UE1针对第一标签归属企业建立 第一PDU会话的方式实现，即均为UE1与该UPF1网元之间的PDU会话。
需要注意的是，基于上述第一种情况，第一通信装置建立至少一个通信会话时，该第一通信装置每次接收的第二目标地址信息均相同，且用于指示该第一用户面功能网元，但接收的第一用户面功能网元上的第二端口号信息可能不相同，因此，该第一通信装置还可以根据每个第二端口号信息建立对应的一个通信会话。
第二种情况：用于传输标签的信息的用户面功能网元为多个，每个标签归属企业的信息对应一个用户面功能网元，例如第一标签归属企业的信息对应第一用户面功能网元。
第一通信装置建立至少一个通信会话的过程中，该第一通信装置每次接收的第二目标地址信息，和/或第二端口号信息均不相同，每个第二目标地址信息，和/或第二端口号信息用于指示对应的一个用户面功能网元。
因此，在该第二种情况中，第一通信装置在建立至少一个通信会话连接后，可以基于增强的URSP策略，确定第一标签对应的第二目标地址信息，和/或第二端口号信息，从而确定第一通信会话。
例如，UE1获取UPF1网元的地址信息和/或对应的端口号信息、UPF2网元的地址信息和/或对应的端口号信息，其中，该UPF1网元的地址信息和/或对应的端口号信息是根据标签1归属企业的DNN_(1)确定的，该UPF2网元的地址信息和/或对应的端口号信息是根据标签2归属企业的DNN_(1)确定的。UE1可以根据UPF1网元的地址信息和/或对应的端口号信息与UPF1网元建立连接(即建立了第一通信会话)，UE1可以根据UPF2网元的地址信息和/或对应的端口号信息与UPF2网元建立连接。
第三种情况：用于传输标签的信息的用户面功能网元为多个，其中至少包括：一个用户面功能网元对应一个标签归属企业的信息，以及一个用户面功能网元对应多个标签归属企业的信息。
一个用户面功能网元对应多个标签归属企业的信息可以参考上述第一种情况的方式，一个用户面功能网元对应一个标签归属企业的信息可以参考上述第二种情况的方式，此处不再具体赘述。
通过以上两种实现方式，该第一通信装置确定的该第一通信会话可以用于该第一通信装置与目标服务器之间传输该第一标签的信息，或者该第一通信会话用于该第一通信装置与第一用户面功能网元之间传输该第一标签的信息。
因此，该第一通信装置通过第一通信会话发送该第一标签的信息包括两种传输路径为：第一传输路径(即图3A所示的传输路径)参考下述步骤S504A，第二传输路径(即图3B所示的传输路径)参考下述步骤S505A-S508A。
S504A：第一通信装置通过第一通信会话，向目标服务器发送第一标签的信息。
其中，该第一标签的信息可以为该第一标识的数据。该第一标签的信息也可以仅包含该第一标签的标识，本申请对此不做限定。
基于上述步骤S503A中的实现方式一，该第一通信装置通过第一通信会话，向目标服务器发送该第一标签的信息。其中，该第一标签的信息可以包含该第一标签的标识。
因此，通过上述实现方式一，该第一通信装置可以直接通过第一通信会话，准确地向目标服务器发送该第一标签的信息。针对第一通信装置传输其它的标签的信息，均可以参考第一通信装置向目标服务器发送第一标签的信息方式实现，此处不再具体赘述。
S505A：第一通信装置通过第一通信会话，向第一用户面功能网元发送第一标签的信 息。
基于上述步骤S503A中的实现方式二，该第一通信装置通过第一通信会话，向第一用户面功能网元发送该第一标签的信息。
S506A：第一用户面功能网元接收该第一标签的信息和第一信息，该第一信息用于确定第一标签的目标服务器。
S507A：第一用户面功能网元根据该第一信息，确定该第一标签的目标服务器。
在执行步骤S506A-507A时，具体可以包括但不限于以下几种实施方式：
实施方式一中，第一用户面功能网元接收第一信息，包括：该第一用户面功能网元接收N4会话请求消息，该N4会话请求消息中包括第一信息，该第一信息指示第一标签过滤器，该第一标签过滤器用于根据标签的标识匹配对应的服务器。
其中，该第一信息可以指示第一标签过滤器，该第一信息也可以为该第一标签过滤器，本申请对此不做具体限定。
进一步的，该第一用户面功能网元根据该第一信息，确定该第一标签的目标服务器，包括：该第一用户面功能网元根据该第一信息，确定该第一标签过滤器；该第一用户面功能网元基于该第一标签的标识，使用该第一标签过滤器匹配到该第一标签的目标服务器。
实施方式二中，若第一用户面功能网元从第一通信装置接收该第一标签的信息；该第一用户面功能网元接收第一信息，包括：第一用户面功能网元接收N4会话请求消息，该N4会话请求消息中包括第一信息，该第一信息指示该第一通信装置的地址信息和/或该第一通信装置发送该第一标签的信息的第三端口号信息。
其中，该第一信息可以用于指示该第一通信装置的地址信息和/或该第一通信装置发送该第一标签的信息的第三端口号信息，该第一信息也可以为该第一通信装置的地址信息和/或该第一通信装置发送该第一标签的信息的第三端口号信息，本申请对此不做具体限定。
进一步的，该第一用户面功能网元根据该第一信息，确定该第一标签的目标服务器，包括：第一用户面功能网元根据该第一信息，确定该第一通信装置的地址信息和/或该第三端口号信息；该第一用户面功能网元根据该第一通信装置的地址信息和该第三端口号信息，以及第一映射信息，确定该第一标签的目标服务器；其中，该第一映射信息中包括该第一通信装置的地址信息和/或端口号信息与服务器的标识的对应关系。
实施方式三中，第一用户面功能网元接收第一信息，包括：该第一用户面功能网元接收N4会话请求消息，该N4会话请求消息中包括第一信息，该第一信息指示该第一用户面功能网元上接收该第一标签的信息的第四端口号信息。
其中，该第一信息可以用于指示该第一用户面功能网元上接收该第一标签的信息的第四端口号信息，该第一信息也可以为该第一用户面功能网元上接收该第一标签的信息的第四端口号信息，本申请对此不做具体限定。
进一步的，该第一用户面功能网元根据该第一信息，确定该第一标签的目标服务器，包括：该第一用户面功能网元根据该第一信息，确定该第一用户面功能网元上接收该第一标签的信息的第四端口号信息；该第一用户面功能网元根据该第四端口号信息和第二映射信息，确定该第一标签的目标服务器；其中，该第二映射信息中包括该第一用户面功能网元上的端口号信息和服务器的标识的对应关系。
实施方式四中，第一用户面功能网元接收第一信息，包括：该第一用户面功能网元接收N4会话请求消息，所述N4会话请求消息中包括第一信息，该第一信息指示该目标服务器的地址信息和/或该目标服务器上用于接收该第一标签的信息的第五端口号信息；其中，该目标服务器的地址信息和/或该第五端口号信息是根据第二指示信息确定的，该第二指示信息指示该第一标签的归属企业信息，该第二指示信息携带在第一通信装置发送的第二会话请求消息中。
其中，该第一信息可以用于指示该目标服务器的地址信息和/或该目标服务器上用于接收该第一标签的信息的第五端口号信息，该第一信息也可以为该目标服务器的地址信息和/或该目标服务器上用于接收该第一标签的信息的第五端口号信息。
进一步的，该第一用户面功能网元根据该第一信息，确定该第一标签的目标服务器，包括：该第一用户面功能网元根据该第一信息，确定该目标服务器的地址信息和/或该第五端口号信息；该第一用户面功能网元根据该目标服务器的地址信息和/或该第五端口号信息，确定该目标服务器。
S508A：第一用户面功能网元向目标服务器发送第一标签的信息。
基于上述步骤S503A实现方式二中的第二种情况，第一通信装置在建立至少一个通信会话连接之后，各用户面功能网元均配置有第一通信装置的地址信息和/或第三端口号信息和/或第四端口号信息与对应目标服务器的映射关系。因此，该第一通信装置在获取第一标签的信息后，可以更根据路由规则确定该第一标签对应的第一通信会话，进而第一通信装置将该第一标签的信息通过第一通信会话发送给对应的第一用户面功能网元。该第一用户面功能网元根据第一通信装置的地址信息和/或第三端口号，从该第一通信装置获取的第一标签的信息，并可直接确定该第一标签对应的目标服务器，进而将该第一标签的信息发送给目标服务器。
本申请实施例中，上述的“地址信息”可理解为用于确定地址的信息，“端口号信息”可理解为用于确定端口号的信息，该“地址信息”可以简称为“地址”，两者意思可相同，该“端口号信息”也可简称为“端口号”，两者意思也可相同。
通过上述本申请提供的一种通信方法，第一通信装置可以基于标签归属企业的信息，建立与对应的服务器之间的通信会话，以使得该第一通信装置在接收第一标签的信息后，可以根据包含标签的标识的第一路由策略信息，准确地确定传输该第一标签的信息的第一通信会话，进而该第一通信装置可以通过该第一通信会话，有效且准确地将该第一标签的信息传输给目标服务器。此外，该第一通信装置还可以根据该第一路由策略信息，确定第一标签的第一通信会话，该第一通信会话为该第一通信装置与对应用户面功能网元之间的通信会话，因此，该第一通信装置可以通过该第一通信会话将该第一标签的信息发送给对应的用户面功能网元，再由该用户面功能网元将该第一标签的信息，有效且准确地发送给目标服务器。
参阅图5B所示，该图示出了本申请实施例提供的另一种通信方法的流程图，具体可以包括如下步骤：
S501B：第一网元向第二网元发送第一消息，该第一消息中包括第一操作指令和第二标签过滤器，以及第一标识。
其中，该第一操作指令用于指示该第二网元根据该第一标识从至少一个标签的标识中 获取该第一标签的标识，该第二标签过滤器用于根据标签的标识确定对应的标签的信息，该第一标识用于确定第一标签的目标服务器。
在一种实施方式中，第一网元向第二网元发送该第一消息。相应的，该第二网元从该第一网元接收该第一消息。
示例性的，该第一网元为网络能力开放功能网元(NEF网元)，该第二网元为移动性管理功能网元(AMF网元)，即该NEF网元向AMF网元发送第一消息，该AMF网元从NEF网元直接地接收该第一消息。
在另一种实施方式中，该第一网元向第二网元发送第一消息，包括：该第一网元向移动性管理功能网元发送该第一消息。相应的，该第二网元从移动性管理功能网元接收该第一消息中的内容。其中，该第一消息中的内容可以包括第一操作指令和第二标签过滤器。
示例性的，上述第一消息可以是AMF通信服务消息，或者是AMF事件开放服务消息，或者是AMF非IP数据传输服务消息，或者是其他AMF通过服务化接口提供的消息，本申请对此不做具体限定。
需要注意的是，上述第一消息中的内容可以通过移动性管理功能网元向第二网元转发上述第一消息从而获得，也可以通过移动性管理功能网元向第二网元发送第三消息，如下行NAS传输消息，并在第三消息中携带上述第一消息中的内容，如第一操作指令和第二标签过滤器。
例如，该第一网元为网络能力开放功能网元(NEF网元)，该第二网元为第一通信装置(如具有读写器功能的UE)，即NEF网元先向AMF网元发送第一消息，该第一消息中包括第一操作指令和第二标签过滤器以及第一标识，该AMF网元再向UE发送第三消息，该第三消息中包括该第一操作指令和该第二标签过滤器。
S502B：第二网元根据第一操作指令和第一标识，获取第一标签的标识，并基于第一标签的标识匹配第二标签过滤器，得到第一标签的信息。
示例性的，第二网元根据该第一操作指令，执行标签操作，例如上述的标签盘存的过程，以获得至少一个标签的标识，并根据该第一标识从至少一个标签的标识中获取第一标签的标识。该第二网元基于第一标签的标识，通过该第二标签过滤器匹配得到该第一标签的信息。
示例性的，第二网元还可以先基于第二标签过滤器确定第一标签的范围并根据该第一操作指令，执行标签操作，以获得第一标签的信息(包括第一标签的标识)。
若该第二网元为具备读写器功能的第一通信装置时，则由该第一通信装置执行该步骤S502B。若第二网元为移动性管理功能网元，则由该移动性管理功能网元执行该步骤S502B。
若该第二网元为移动性管理功能网元时，该移动性管理功能网元执行该步骤S502B之前，还包括：该第二网元从具备读写器功能的第一通信装置获取第一标签的信息，或者该第二网元从具备读写器功能的第一通信装置获取所有标签的信息，该所有标签的信息中包括第一标签的信息。
S503B：第二网元向第一网元发送第二消息，该第二消息中包括该第一标签的信息和第一标识。
其中，该第一标识用于确定该第一标签的目标服务器。
相应的，该第一网元接收该第二消息。
在一种实施方式中，基于上述第二网元从该第一网元接收第一消息的情况，该第二网 元向该第一网元发送该第二消息。
在另一种实施方式中，基于上述第二网元从移动性管理功能网元接收第一消息的情况，该第二网元向第一网元发送第二消息，包括：该第二网元向该移动性管理功能网元发送该第二消息；该移动性管理功能网元再向第一网元发送该二消息。
需要注意的是，该第二网元向移动性管理功能网元发送第四消息，该第四消息中包括第一标签的信息，该移动性管理功能网元再向第一网元发送第二消息，该第二消息中包括该第一标签的信息和第一标识。
示例性的，该第二网元为UE，第一网元为NEF网元，UE网元向AMF网元发送NAS消息(相当于第四消息)，该NAS消息包含第一标签的信息，AMF网元向NEF网元发送数据传输消息(相当于第二消息)，该数据传输消息包括第一标签的信息和第一标识。
S504B：第一网元根据该第一标识，确定该第一标签的目标服务器。
在一种实施方式中，第一网元根据所述第一标识，确定该第一标签的目标服务器，包括：该第一网元根据该第一标识和第一对应关系，确定该第一标签的目标服务器，其中，所述第一对应关系包括该第一标识与所述目标服务器的对应关系。
需要注意的是，该第一对应关系可以通过以下方式得到：
第一网元接收至少一个服务器接收控制信息，每个控制信息中包括第一操作标识和第二标签过滤器。该第一网元可以基于至少一个目标服务器的控制信息，生成第一标识，并建立该第一标识与服务器之间的对应关系，即第一对应关系，该第一对应关系可以存储于第一网元的本地，或者存储于其它可通信的网元或设备中，本申请对此不做具体限定。
需要注意的是，该第一标识可以为用于标识目标服务器的信息，如目标服务器地址、目标服务器标识等。示例性地，该第一标识可以为该第一消息的标识，或者该第一标识可以为第一操作指令的标识，该第一消息的标识或第一操作指令的标识与该目标服务器存在一一对应的关系，本申请对该第一标识不做具体限定。
S505B：第一网元将该第一标签的信息发送给该目标服务器。
该实施方式主要基于上述图3C所示的第三种传输路径，该实施方式中的第二网元既可以为具备读写器功能的第一通信装置(如UE)，也可以为移动性管理功能网元(即AMF网元)。当该第二网元为第一通信装置时，该第二网元先通过移动性管理功能网元接收来自第一网元(即网络能力开放功能网元)的第一消息，然后，该第二网元可以基于该第一消息中的第一操作指令、第二标签过滤器确定第一标签，进而通过该移动性管理功能网元向第一网元发送包含该第一标签的信息和第一标识的第二消息，最后，该第一网元将该第一标签的信息发送给目标服务器。当该第二网元为移动性管理功能网元时，可以直接接收来自第一网元(即网络能力开放功能网元)的第一消息，并基于该第一消息中的第一操作指令、第二标签过滤器确定第一标签，然后将由第一通信装置读写的第一标签的信息和第一标识携带在第二消息中发送给第一网元，最后，该第一网元根据该第一标识将该第一标签的信息准确地发送给目标服务器。
下面通过几个具体实施例，以进一步的详细阐述上述本申请方案提出的通信方法。
下述实施例一、实施例二、实施例三属于上述图5A所示的一种通信方法的具体示例，其中，实施例一属于图5A所示方法中一种实施方式的具体示例，实施例二属于图5A所示方法中另一种实施方式的具体示例(上述步骤S502A中的第一种情况)，实施例二是基于图 5A所示方法中的另一种实施方式的具体示例(上述步骤S502A中的第二种情况)。下述实施例四、实施例五属于上述图5B所示的另一种通信方法的具体示例。
实施例一
在该实施例一中，以终端设备UE作为读写器为例，基于上述图3A所示的第一种传输路径，由UE(读写器)执行标签的管理，并由UE(读写器)建立用户面会话并传输标签的信息，参考图6所示，具体流程如下：
S600：UE(读写器)完成注册过程。
UE(读写器)具体执行注册的流程可以参考现有的技术实现，此处不再描述。
S601：UE(即读写器)向AMF网元发送PDU会话建立请求消息。
相应的，该AMF网元接收PDU会话建立请求消息(相当于上述本申请的第一会话请求消息)。
一种可能的示例，UE(读写器)还可以向RAN(如基站)发送该PDU会话建立请求消息，并由该RAN设备(如基站)转发给AMF网元，AMF网元从该RAN(如基站)接收该PDU会话建立请求消息。
一种可能的示例，该PDU会话建立请求消息中可包括第一指示信息，该第一指示信息用于指示该UE的接入标签归属企业的信息，该UE的接入标签归属企业的信息可以为但不限于DNN和/或NSSAI；或者该第一指示信息为DNN和/或NSSAI。该DNN和/或NSSAI指示该UE请求建立的目标企业的网络信息。
若UE(即读写器)由多个企业共享，则针对不同接入的标签归属企业，依次发起步骤S601-S608的PDU会话建立的流程。步骤S601-S608是针对一个企业建立对应的PDU会话(即通信会话)为例，进行详细介绍。
S602：AMF网元选择合适的SMF网元。
除了现有技术中涉及的AMF网元如何选择合适的SMF网元外，所述AMF网元还可以根据上述的PDU会话建立请求消息(相当于上述本申请的第一会话请求消息)中的第一指示信息来辅助选择SMF网元。
一种可能的实现方法，AMF网元选择满足上述第一指示信息中的DNN，和/或NSSAI的SMF网元。
S603：AMF网元向SMF网元发送PDU会话创建会话上下文请求消息。
相应的，SMF网元接收该PDU会话创建会话上下文请求消息。
一种可能的实现方式，该PDU会话创建会话上下文请求消息中携带接入标签归属企业的DNN和/或NSSAI。上述DNN和/或NSSAI指示UE请求建立的目标企业的网络信息。
可选的，该PDU会话创建会话上下文请求消息中还携带SUPI(即UE的标识)、UE请求的DNN、PDU Session ID等参数。
S604：SMF网元向AMF网元发送PDU会话创建会话上下文响应消息。
相应的，该AMF网元接收该PDU会话创建会话上下文响应消息。
S605：SMF网元根据接收到的PDU会话建立请求消息中的DNN和/或NSSAI，确定UE的目标PIOT服务器信息，向AMF网元发送N1N2消息。
在一种可能的示例中，该SMF网元也可以向PCF网元请求获取上述UE的目标服务器的信息。其中，UE的目标PIOT服务器信息可以包括目标服务器的IP地址和/或端口号。
相应的，AMF网元接收该N1N2消息，其中，该N1N2消息中携带UPF网元的隧道 端点标识等信息(该信息给RAN设备)。该N1N2消息中还携带PIOT服务器地址和端口号信息(封装在N1 SM消息中，并将发送给读写器UE)。示例性的，该N1N2消息可以是AMF通信N1N2消息转发消息。
S606：AMF网元向RAN发送N2 PDU会话请求消息。
相应的，该RAN接收该N2 PDU会话请求消息，其中，该N2 PDU会话请求消息中携带NAS消息，该NAS消息中携带PIOT服务器地址和端口号信息。示例性的，该NAS消息可以是PDU会话建立响应消息。该NAS消息同时也来自于上述N1 SM消息。
S607：RAN与UE(读写器)建立空口资源，并向UE发送NAS消息。
相应的，UE接收该NAS消息(相当于上述本申请的第一响应消息)，该NAS消息中携带PIOT服务器地址(相当于上述本申请的第一目标地址信息)和端口号信息(相当于上述本申请的第一端口号信息)。
S608：RAN向AMF网元发送N2 PDU会话响应消息。
相应的，AMF网元接收该N2 PDU会话响应消息。
通过上述步骤S601-S608，UE(读写器)建立了一个企业的PDU会话(PDU Session)，针对其它不同的企业，UE(读写器)均可参考上述步骤S601-S608建立对应的PDU会话，此处不再具体赘述。
例如，UE(读写器)针对标签1归属企业1，通过上述步骤S601-S608，建立了对应的PDU1会话；UE(读写器)针对标签2归属企业2，通过上述步骤S601-S608，建立了对应的PDU2会话；UE(读写器)针对标签3归属企业3，通过上述步骤S601-S608，建立了对应的PDU3会话。
此外，通过上述步骤，UE(读写器)针对不同的企业，建立不同的PDU会话后，UE分别获得不同的PIOT服务器地址信息和端口号信息，即建立一个PDU会话获得一个对应的PIOT服务器地址信息和端口号信息。
S609：UE(读写器)基于PIOT服务器地址信息和端口号信息，与对应的PIOT服务器建立连接。
例如，UE(读写器)通过建立PDU1会话，获得一个PIOT1服务器地址信息和对应的端口号信息，读写器UE根据PIOT1服务器地址信息和对应的端口号信息，与PIOT1服务器建立连接。UE(读写器)通过建立PDU2会话，获得一个PIOT2服务器地址信息和对应的端口号信息，UE(读写器)根据PIOT2服务器地址信息和对应的端口号信息，与PIOT2服务器建立连接。UE(读写器)通过建立PDU3会话，获得一个PIOT3服务器地址信息和对应的端口号信息，UE(读写器)根据PIOT3服务器地址信息和对应的端口号信息，与PIOT3服务器建立连接。
下面为应用层向UE(读写器)发送标签盘存或读写的过程，具体流程如下：
S610：PIOT服务器通过已建立的PDU会话向UE(读写器)发送第一请求消息。
相应的，UE(读写器)接收第一请求消息(相当于上述本申请的第一请求)。其中，该第一请求消息中包含标签盘存或读写的命令，此外，该第一请求消息中还可以包含目标标签的范围以及过滤规则。
S611：UE(读写器)根据上述第一请求消息，与目标标签建立连接，并执行上述标签盘存或读写的命令。
具体的，UE(读写器)可以根据该标签盘存命令，先执行目标标签((相当于上述本 申请的第一标签)盘存，执行标签盘存过程可以参考上述图2中的步骤执行，此处不再具体赘述。
进一步的，在该步骤S611中，UE(读写器)可读取接入的标签的信息。UE(读写器)具体如何读取接入的标签的信息，可以参考现有的技术实现，此处不再具体描述。
其中，标签的信息包括但不限于标签的标识，如电子产品代码EPC、标签识别号TID等。
例如，接入的标签包括标签1、标签2、标签3，UE(读写器)读取标签1的信息、标签2的信息、标签3的信息。
S612：UE(读写器)根据增强的URSP策略，选择合适的PDU会话。
应理解的是，UE(读写器)根据增强的URSP策略，选择合适的PDU会话可以视为上述的第一通信会话。
UE(读写器)根据获取的接入的标签的信息，结合表1所示的增强的用户设备路由选择策略(URSP策略)(相当于上述本申请的第一路由策略)，为接入的标签确定对应的合适的PDU会话(相当于上述本申请的通信会话)。
如表1所示，增强的URSP策略在流量描述内容中添加了额外关于Passive IoT的描述，其由企业的ID和标签的ID共同构成，用于匹配和识别不同的标签。Passive IoT的描述与对应的PIOT服务器地址和端口号绑定，并通过对应的PDU会话传输(即本申请的第一通信会话)，即一个Passive IoT分别与PIOT服务器地址和端口号，以及PDU会话存在对应关系。因此，UE(读写器)可以根据标签的信息(标签的ID以及标签归属企业的ID)，确定表1中的Passive IoT的描述，进而可以确定Passive IoT的描述对应的PIOT服务器地址和端口号，以及对应的PDU会话。
表1

应理解的是，上述的表1仅作为一个示例，该增强的URSP策略还可以包括但不限于表1中的描述内容。
例如，UE(读写器)根据标签1的ID以及标签1归属企业的ID，可以确定对应的服务器地址和端口号(或者通过上述会话建立过程获得服务器的地址和端口号)，以及PDU1会话。UE(读写器)根据标签2的ID以及标签2归属企业的ID，确定对应的服务器地址和端口号(或者通过上述会话建立过程获得服务器的地址和端口号)，以及PDU2会话。UE(读写器)根据标签3的ID以及标签3归属企业的ID，确定对应的服务器地址和端口号(或者通过上述会话建立过程获得服务器的地址和端口号)，以及PDU3会话。
S613：UE(读写器)通过PDU会话，将标签的信息发送给对应的PIOT服务器。
具体的，该标签的信息可以为标签的数据，或者该标签的信息可以仅包含该标签的标识。
UE(读写器)根据PIOT服务器地址信息和端口号，将标签的信息使用对应的PDU会话，通过相应端口号，发送给对应的PIOT服务器。
例如，UE(读写器)根据PIOT1服务器地址信息和端口号1，将标签1的数据使用对应的PDU1会话，通过相应端口号1，发送给对应的PIOT1服务器。
UE(读写器)根据PIOT2服务器地址信息和端口号2，将标签2的数据使用对应的PDU2会话，通过相应端口号2，发送给对应的PIOT2服务器。
UE(读写器)根据PIOT3服务器地址信息和端口号3，将标签3的数据使用对应的 PDU3会话，通过相应端口号3，发送给对应的PIOT3服务器。
通过该实施例一，在建立PDU会话时，通过UE(读写器)发送携带接入标签(Passive IoT)归属企业对应的DNN和/或NSSAI，以辅助核心网识别和分配不同的服务器地址信息和端口号信息，进而使得UE(读写器)可以与Passive IoT服务器建立用户面连接。此外，该实施例一中，还根据增强的URSP策略，使得UE(读写器)可以针对不同的标签的信息，选择对应的合适的PDU会话，进而路由并传输不同的标签的信息。
实施例二
在该实施例二中，以终端设备UE作为读写器为例，基于上述图3B所示的第二种传输路径，由UPF网元执行标签的管理，并通过UPF网元建立用户面会话并传输标签的信息，参考图7所示，具体流程如下：
S700：UE(读写器)完成注册的过程。
UE(读写器)具体执行注册的流程可以参考现有的技术实现，此处不再描述。
S701：UE(读写器)向AMF网元发送PDU会话建立请求消息。
相应的，该AMF网元接收该PDU会话建立请求信息(相当于上述本申请的第一会话请求消息)，该PDU会话建立请求消息中携带接入的标签归属企业的数据网络名称DNN和/或NSSAI。
具体的，该步骤S701可以参考上述步骤S601，此处不再具体赘述。
若UE(读写器)由多个企业共享，则针对接入的不同标签归属企业，依次发起步骤S701-S708的PDU会话建立的流程。该步骤S701-S708是针对一个企业建立对应的PDU会话(即通信会话)为例，进行详细介绍。
S702：AMF网元选择合适的SMF网元。
具体的，该步骤S702可以参考上述步骤S602，此处不再具体赘述。
S703：AMF网元向SMF网元发送PDU会话创建会话上下文请求消息。
相应的，SMF网元接收该PDU会话创建会话上下文请求消息。
一种可能的实现方式，该PDU会话创建会话上下文请求消息中携带接入标签归属企业的DNN和/或NSSAI。上述DNN和/或NSSAI指示UE请求建立的目标企业的网络信息。
可选的，该PDU会话创建会话上下文请求消息中还携带UE的标识(如SUPI)、UE请求的数据网络名称DNN、PDU会话标识PDU Session ID等参数。
具体的，该步骤S702可以参考上述步骤S602，此处不再具体赘述。
S704：SMF网元向AMF网元发送PDU会话创建会话上下文响应消息。
相应的，该AMF网元接收该PDU会话创建会话上下文响应消息。
S705：SMF网元向UPF网元发起N4会话建立/修改请求。
相应的，UPF网元接收该N4会话建立/修改请求(相当于上述本申请的N4会话请求消息)。其中，该N4会话建立/修改请求中携带UE的IP地址(相当于本申请的第三目标地址信息)和对应的端口号信息(相当于本申请的第三目标地址信息)、PIOT服务器的IP地址(包括完全限定域名)(相当于本申请的第二目标地址信息)和对应的端口号信息(相当于本申请的第二端口号信息)，以及第一标签过滤器。
示例性的，SMF网元可以根据接收到的DNN和/或IP地址，确定UPF网元的目标PIOT服务器信息，该目标PIOT服务器信息可以包括目标服务器的IP地址和/或端口号。SMF 网元也可以向PCF网元请求获取上述目标PIOT服务器信息。
上述的第一标签过滤器用于识别标签，UPF网元可以通过识别标签的标识或者标签携带的企业标识选择相应的PIOT服务器，以发送标签的信息。在本实施例中，UPF网元可以基于第一标签过滤器来识别标签并为该标签确定目标PIOT服务器。
S706：UPF网元向SMF网元发送N4会话建立/修改响应消息。
该UPF网元向SMF网元发送N4会话建立/修改响应消息，用于向该SMF网元反馈其自身的IP地址和端口号。
S707：SMF网元向AMF网元发送N1N2消息。
相应的，AMF网元接收N1N2消息，其中，该N1N2消息中携带上述UPF网元的IP地址和端口号信息。示例性的，上述N1N2消息可以是AMF网元通过N1N2消息转发消息。
需要注意的是，该UPF网元的IP地址和端口号信息封装在N1 SM消息中，且该信息会发送给UE(读写器)。
S708：AMF网元向RAN发送N2 PDU会话请求消息。
相应的，RAN接收N2 PDU会话请求消息，该消息中携带NAS消息，该NAS消息为上述N1 SM消息，该NAS消息中携带UPF网元的IP地址和端口号信息。
示例性的，该NAS消息可以是PDU会话建立响应消息。
S709：RAN分配空口资源，并与UE(读写器)建立无线连接，并将上述接收到的NAS消息发给UE(读写器)。
相应的，UE(读写器)接收该NAS消息(相当于上述本申请的第二响应消息)，该NAS消息中携带UPF网元的IP地址(相当于上述本申请的第二目标地址信息)和端口号信息(相当于上述本申请的第二端口号信息)。
S710：RAN向AMF网元发送N2 PDU会话响应消息。
具体的，RAN成功建立与UE(读写器)的连接，并在UE(读写器)成功接收NAS消息后，向AMF网元发送N2 PDU会话响应消息。
S711：UE(读写器)基于UPF网元的IP地址和端口号，与UPF网元建立连接。
通过该步骤S711，可以建立UE(读写器)与UPF网元的第一通信会话。
S712：UPF网元基于PIOT服务器的地址信息和端口号信息，与对应的PIOT服务器建立连接。
示例性的，在上述步骤S701-S705，UPF网元可以接收到PIOT服务器的IP地址和对应的端口号信息，进而，UPF网元可以根据PIOT服务器的IP地址和对应的端口号信息，与该PIOT服务器建立连接。具体的，该UPF网元与PIOT服务器建立连接，可以参考上述步骤S609中UE(读写器)与PIOT服务器建立连接的过程，此处不再具体赘述。
因此，UPF网元可以依次针对UE(即读写器)接入的不同标签归属企业，均可参考上述步骤S701-S705执行，获得对应的PIOT服务器的IP地址和对应的端口号信息，进而与对应的PIOT服务器建立连接。最终，UPF网元针对不同标签归属企业，创建了不同的PIOT服务器的连接，以便后续使用。
下面为应用层向UE(读写器)发送标签盘存或读写的过程，具体流程如下：
S713：PIOT服务器通过已建立的PDU会话向UE(即读写器)发送第一请求消息。
相应的，UE(即读写器)接收该第一请求消息(相当于上述本申请的第一请求)。该 第一请求消息中包含标签盘存或读写的命令，此外，该第一请求消息中还可以包含目标标签的范围以及过滤规则。
该步骤S713可以与上述步骤S610相互参考。
S714：UE(读写器)根据上述第一请求消息，与目标标签建立连接，并执行上述标签盘存或读写的命令。
具体的，UE(读写器)可以根据该标签盘存命令，先执行目标标签(相当于上述本申请的第一标签)盘存，执行标签盘存过程可以参考上述图2中的步骤执行，此处不再具体赘述。
进一步的，在该步骤S714中，UE(读写器)读取接入的标签的信息。UE(读写器)具体如何读取接入的标签的信息，可以参考现有的技术实现，此处不再具体描述。
其中，标签的信息包括但不限于标签的标识，如电子产品代码EPC、标签识别号TID等。
例如，接入的标签包括标签1、标签2、标签3，UE(读写器)读取标签1的信息、标签2的信息、标签3的信息。
该步骤S714可以与上述步骤S611相互参考。
S715：UE(读写器)根据增强的URSP策略，选择合适的PDU会话。
应理解的是，UE(读写器)根据增强的URSP策略，选择合适的PDU会话可以视为上述的第一通信会话。
UE(读写器)根据获取的接入的标签的信息，结合上述表1所示的增强的URSP策略(路由策略)，为每个接入的标签确定对应的合适的PDU会话。值得注意的是，与实施例一不同的是该实施例中的增强的URSP策略中的IP描述符为UE收到的UPF的IP地址和端口号，以及相应的协议ID。
例如，UE(读写器)可以根据获取的接入的标签1的信息，结合上述表1所示的增强的URSP策略，确定PDU1会话。UE(读写器)可以根据获取的接入的标签2的信息，结合上述表1所示的增强的URSP策略，确定PDU2会话。UE(读写器)可以根据获取的接入的标签3的信息，结合上述表1所示的增强的URSP策略，确定PDU3会话。
该步骤S715与上述步骤S612相同，可以互相参考，此处不再具体赘述。
S716：UE(读写器)通过PDU会话，将标签的信息发送给UPF网元。
相应的，UPF网元接收标签的信息。
例如，UE(读写器)将标签1的信息，通过PDU1会话传输给UPF网元。UE(读写器)将标签2的信息，通过PDU2会话传输给UPF网元。UE(读写器)将标签3的信息，通过PDU3会话传输给UPF网元。
S717：UPF网元基于第一标签过滤器，选择对应的PIOT服务器的连接。
第一标签过滤器包含标签标识或标签携带的企业标识的过滤规则，以及相应过滤规则对应的目标PIOT服务器的信息，即目标PIOT的IP地址和端口号。例如，UPF网元接收到的3份标签的信息，UPF网元可以通过第一标签过滤器对接收的3份标签的信息进行识别，确定分别为标签1的数据、标签2的数据、标签3的数据；进一步的，UPF网元可以为不同的标签的信息，确定对应的PIOT服务器的连接，即UPF网元为标签1的数据确定PIOT1服务器的连接，UPF网元为标签2的数据确定PIOT2服务器的连接，UPF网元为标签3的数据确定PIOT3服务器的连接。
S718：UPF网元将标签的信息传输给对应的PIOT服务器。
具体的，该标签的信息可以为标签的数据，或者该标签的信息可以仅包含该标签的标识。
例如，UPF网元通过PIOT1服务器的连接，将标签1的数据传输给PIOT1服务器。该UPF网元通过PIOT2服务器的连接，将标签2的数据传输给PIOT2服务器。该UPF网元通过PIOT3服务器的连接，将标签3的数据传输给PIOT3服务器。
通过该实施例二，当UE不能获知PIOT服务器的地址信息和对应的端口号信息，UE可以与UPF网元建立连接，并将标签的信息发送给UPF网元，进一步由该UPF网元对接收的标签的信息进行识别，并为标签的信息确定对应的PIOT服务器的连接(即路由数据)，最后，该UPF网元通过对应的PIOT服务器的连接，将标签的信息准确地传输给对应的PIOT服务器。
实施例三
在该实施例三中，以终端设备UE作为读写器为例，基于上述图3B所示的第二种传输路径，由UPF网元执行标签的管理，并通过UPF网元建立用户面会话并传输标签的信息。然而，在该实施例三中可能包括多个UPF网元，UE(读写器)在创建通信会话(Passive IoT会话)过程中，每个通信会话可能对应不同的UPF网元，并且每个通信会话最终对应不同企业的目标PIOT服务器，其中，不同的通信会话与不同目标PIOT服务器的对应关系储存在UPF网元上，由UPF网元执行标签的路由管理。参考图8所示，具体流程如下：
S800：UE(读写器)完成注册的过程。
UE(读写器)具体执行注册的流程可以参考现有的技术实现，此处不再描述。
S801：UE(即读写器)向AMF网元发送PDU会话建立请求信息。
相应的，该AMF网元接收该PDU会话建立请求消息。
一种可能的示例，UE(读写器)还可以向RAN设备(如基站)发送该PDU会话建立请求消息，并由该RAN设备(如基站)转发给AMF网元，AMF网元从该RAN设备(如基站)接收该PDU会话建立请求消息。
一种可能的示例，该PDU会话建立请求消息中可包括第一指示信息，该第一指示信息用于指示该UE的接入标签归属企业的信息，该UE的接入标签归属企业的信息可以为但不限于DNN和/或NSSAI；或者该第一指示信息为DNN和/或NSSAI。该DNN和/或NSSAI指示该UE请求建立的目标企业的网络信息。
该步骤S801可以参考上述步骤S601和S701。
若UE(即读写器)由多个企业共享，则针对接入的不同标签归属企业，依次发起步骤S801-S808的PDU会话建立的流程。该步骤S801-S808可以认为是针对一个企业建立对应的PDU会话(即通信会话)为例，进行详细介绍。
S802：AMF网元选择合适的SMF网元。
除了现有技术中涉及的AMF网元如何选择合适的SMF网元外，所述AMF网元还可以根据上述的PDU会话建立请求消息(相当于上述本申请的第一会话请求消息)中的第一指示信息来辅助选择SMF网元。
一种可能的实现方法，AMF网元选择满足上述第一指示信息中的DNN，和/或NSSAI的SMF网元。
该步骤S802可以参考上述步骤S602和S702。
S803：AMF网元向SMF网元发送PDU会话创建会话上下文请求消息。
相应的，SMF网元接收该PDU会话创建会话上下文请求消息。
一种可能的实现方式，该PDU会话创建会话上下文请求消息中携带接入标签归属企业的DNN和/或NSSAI。上述DNN和/或NSSAI指示UE请求建立的目标企业的网络信息。
可选的，该PDU会话创建会话上下文请求消息中还携带UE的标识(如SUPI)、UE请求的数据网络名称DNN、PDU会话标识PDU Session ID等参数。
该步骤S804可以参考上述步骤S604和S704。
S804：SMF网元向AMF网元发送PDU会话创建会话上下文响应消息。
相应的，该AMF网元接收该PDU会话创建会话上下文响应消息。
S805：SMF网元根据接收到的DNN，向对应的UPF网元发送N4会话建立/修改请求。
相应的，对应的UPF网元接收该N4会话建立/修改请求(相当于上述本申请的N4会话请求消息)。其中，该N4会话建立/修改请求中携带UE的IP地址和/或端口号信息、PIOT服务器的IP地址(包括完全限定域名)和对应的端口号信息。
示例性的，SMF网元根据接收的标签1归属企业的DNN，确定合适的PIOT服务器的IP地址(包括完全限定域名)以及对应的端口号信息，若SMF网元确定为PIOT1服务器的IP地址(包括完全限定域名)以及对应的端口号信息，SMF网元向对应的UPF(1)网元发送N4会话建立/修改请求，该N4会话建立/修改请求中携带PIOT1服务器的IP地址(包括完全限定域名)以及对应的端口号信息。
需要注意的是，SMF网元在上述步骤S805仅针对一个标签归属企业的DNN和/或NSSAI，向对应的UPF网元反馈了对应的PIOT服务器的IP地址和对应的端口号信息。因此，SMF网元针对UE所接入的其它的标签归属企业的DNN和/或NSSAI，均可以参考该方式，向对应的UPF网元反馈对应的PIOT服务器的IP地址和对应的端口号信息。
针对不同的标签，其对应的UPF网元可以相同或者不同，若上述不同的通信会话对应的UPF网元相同(即UPF网元的IP地址均相同)，则其对应的端口号不相同，若上述不同的通信会话对应的UPF网元不同(即UPF网元的IP地址不同)，则其对应的端口号则有可能相同。总的来说，由UPF网元的IP地址和端口号可以识别不同的通信会话。
例如，SMF网元可以针对UE所接入的标签1、2、3归属企业的DNN和/或NSSAI，分别向对应的UPF(1)网元、UPF(2)网元、UPF(3)网元反馈对应的PIOT1服务器的IP地址和对应的端口号信息。即SMF网元针对该UE所接入的不同标签，确定了不同的UFP网元(即UFP网元的IP地址均不同)，且不同的UPF网元对应的端口号也不同，该不同的UFP网元对应的通信会话也不同。
或者SMF网元可以针对UE所接入的标签1、2、3归属企业的DNN和/或NSSAI，均确定向同一个UPF(1)网元反馈对应的PIOT1服务器的IP地址和对应的端口号信息，但SMF网元针对该UE所接入的标签1、2、3，确定对应的UPF(1)网元的端口号可以不同，即标签1对应UPF(1)网元的端口号1，标签2对应UPF(1)网元的端口号2，标签3对应UPF(1)网元的端口号3，且该端口号1、端口号2、端口号3均对应不同的通信会话。
S806：UPF网元向SMF网元发送N4会话建立/修改响应消息。
例如，UPF(1)网元接收N4会话建立/修改请求后，向SMF网元发送N4会话建立/ 修改响应消息，用于向该SMF网元反馈其自身的IP地址和端口号，即该UPF(1)网元的IPF地址和对应的端口号。
S807：SMF网元向AMF网元发送N1N2消息。
相应的，AMF网元接收N1N2消息，其中，该N1N2消息中携带上述UPF网元的IP地址和端口号信息。示例性的，上述N1N2消息可以是AMF网元通信N1N2消息转发消息。
例如，SMF网元根据接收到的标签1归属企业的DNN和/或NSSAI，向AMF网元发送N1N2消息，该N1N2消息中携带UPF(1)网元的IP地址和端口号1信息。SMF网元根据接收到的标签2归属企业的DNN和/或NSSAI，向AMF网元发送N1N2消息，该N1N2消息中携带UPF(2)网元的IP地址和端口号2信息。SMF网元根据接收到的标签3归属企业的DNN和/或NSSAI，向AMF网元发送N1N2消息，该N1N2消息中携带UPF(3)网元的IP地址和端口号3信息。或者SMF网元根据接收到的标签1归属企业的DNN和/或NSSAI，向AMF网元发送N1N2消息，该N1N2消息中携带UPF(1)网元的IP地址和端口号1信息。SMF网元根据接收到的标签2归属企业的DNN和/或NSSAI，向AMF网元发送N1N2消息，该N1N2消息中携带UPF(1)网元的IP地址和端口号2信息。SMF网元根据接收到的标签3归属企业的DNN和/或NSSAI，向AMF网元发送N1N2消息，该N1N2消息中携带UPF(1)网元的IP地址和端口号3信息。
S808：AMF网元向RAN发送N2 PDU会话请求消息。
相应的，RAN接收该N2 PDU会话请求消息，该N2 PDU会话请求消息中携带NAS消息，该NAS消息为上述N1 SM消息，该NAS消息中携带上述AMF网元接收到的UPF网元的IP地址和端口号信息。
示例性的，该NAS消息可以是PDU会话建立响应消息。
S809：RAN分配空口资源，并与UE(读写器)建立无线连接，并将上述接收到的NAS消息发给UE(读写器)。
相应的，UE(读写器)接收该NAS消息(可相当于上述本申请的第二响应消息)，该NAS消息中携带UPF网元的IP地址((相当于上述本申请的第二目标地址信息))和端口号信息(相当于上述本申请的第二端口号信息)。
S810：RAN向AMF网元发送N2 PDU会话响应消息。
具体的，RAN成功建立与UE(读写器)的连接，并在UE(读写器)成功接收NAS消息后，向AMF网元发送N2 PDU会话响应消息。
S811：UE(读写器)基于UPF网元的IP地址和端口号，与对应的UPF网元建立连接。
参考该步骤S811执行，可以建立多个UE(读写器)到UPF网元的连接。
例如，UE(即读写器)基于UPF(1)网元的IP地址和端口号1，与对应的UPF(1)网元建立连接。UE(即读写器)基于UPF(2)网元的IP地址和端口号2，与对应的UPF(2)网元建立连接。UE(即读写器)基于UPF(3)网元的IP地址和端口号3，与对应的UPF(3)网元建立连接。或者UE(即读写器)基于UPF(1)网元的IP地址和端口号1，与对应的UPF(1)网元建立连接。UE(即读写器)基于UPF(1)网元的IP地址和端口号2，与对应的UPF(1)网元建立连接。UE(即读写器)基于UPF(1)网元的IP地址和端口号3，与对应的UPF(1)网元建立连接。
S812：UPF网元基于PIOT服务器的地址信息和端口号信息，与对应的PIOT服务器 建立连接。
通过上述步骤S805，不同的UPF网元可以针对对应接入的标签归属企业，获取到相应的PIOT服务器的地址信息和端口号信息，并根据获取到的相应的PIOT服务器的地址信息和端口号信息，与对应的PIOT服务器建立连接。
例如，UPF(1)网元基于UPF(1)网元的IP地址和UPF(1)网元的端口号1，以及PIOT1服务器的IP地址和对应的端口号1，与PIOT1服务器建立连接。UPF(2)网元基于UPF(2)网元的IP地址和UPF(2)网元的端口号2，以及PIOT2服务器的IP地址和对应的端口号2，与PIOT2服务器建立连接。UPF(3)网元基于UPF(3)网元的IP地址和UPF(3)网元的端口号3，以及PIOT3服务器的IP地址和对应的端口号3信息，与PIOT3服务器建立连接。
或者UPF(1)网元基于UPF(1)网元的IP地址和UPF(1)网元的端口号1，以及PIOT1服务器的IP地址信息和对应的端口号1，与PIOT1服务器建立连接。UPF(1)网元基于UPF(1)网元的IP地址和UPF(1)网元的端口号2，以及PIOT2服务器的IP地址和对应的端口号2，与PIOT2服务器建立连接。UPF(1)网元还基于UPF(1)网元的IP地址和UPF(1)网元的端口号3，PIOT3服务器的IP地址信息和对应的端口号3，与PIOT3服务器建立连接。
因此，参考该步骤S812，可以建立多个UPF网元对应到多个PIOT服务器的连接，或可以建立一个UPF网元对应到多个PIOT服务器的连接。
同时，可以建立UE(读写器)到多个UPF网元的连接与该多个UPF网元到多个PIOT服务器的连接之间的关联关系(或对应关系)，即包括多个UFP网元时，UE(读写器)与该多个UPF网元中的一个UPF网元之间的连接对应一个该UPF网元与多个PIOT服务器中一个PIOT服务器之间的连接，例如，一个UE与UPF(x)网元之间的连接对应一个该UPF(x)网元与PIOT(x)服务器之间的连接，x为可变的正整数。
或者可以建立UE(读写器)到一个UPF网元的连接与该UPF网元到多个PIOT服务器的连接之间的关联关系(或对应关系)，即仅包括一个UFP网元时，UE(读写器)与该UPF网元之间的连接对应一个该UPF网元与多个PIOT服务器中一个PIOT服务器之间的连接，例如，UE与UPF(1)之间的连接对应一个该UPF(1)与PIOT(x)服务器之间的连接，x为可变的正整数。
下面为应用层向UE(读写器)发送标签盘存或读写的过程，具体流程如下：
S813：PIOT服务器通过已建立的PDU会话向UE(即读写器)发送第一请求消息。
相应的，UE(即读写器)接收该第一请求消息(相当于上述本申请的第一请求)。该第一请求消息中包含标签盘存或读写的命令，此外，该第一请求消息中还可以包含目标标签的范围以及过滤规则。
该步骤S813可以与上述步骤S610和步骤S713相互参考。
S814：UE(读写器)根据上述第一请求消息，与目标标签建立连接，并执行上述标签盘存或读写的命令。
具体的，UE(读写器)可以根据该标签盘存命令，先执行目标标签(相当于上述本申请的第一标签)盘存，执行标签盘存过程可以参考上述图2中的步骤执行，此处不再具体赘述。
进一步的，在该步骤S814中，UE(读写器)读取接入的标签的信息。
其中，标签的信息包括但不限于标签的标识，如电子产品代码EPC、标签识别号TID等。
例如，接入的标签包括标签1、标签2、标签3，UE(读写器)读取标签1的信息、标签2的信息、标签3的信息。
该步骤S814可以与上述步骤S611和步骤S714相互参考。
S815：UE(读写器)根据增强的URSP策略，选择合适的PDU会话。
UE(读写器)根据获取的接入的标签的信息，结合上述表1所示的增强的URSP策略(路由策略)，为每个接入的标签确定对应的合适的PDU会话。与上述实施例一不同的是，上述URSP策略的IP描述符为UPF的IP地址和端口号，以及协议ID。
例如，UE(读写器)根据接入的标签1的信息结合上述表1所示的增强的URSP策略，确定PDU1会话。UE(读写器)根据接入的标2的信息结合上述表1所示的增强的URSP策略，确定PDU2会话，UE(读写器)根据接入的标签3的信息结合上述表1所示的增强的URSP策略，确定PDU3会话。
需要注意的是，该步骤S815与上述步骤S715相同，可以互相参考，此处不再具体赘述。
S816：UE(读写器)通过PDU会话，将标签的信息发送给对应的UPF网元。
相应的，UPF网元接收标签的信息。
例如，UE(读写器)通过PDU1会话，将标签1的信息发送给UPF(1)网元；UE(读写器)通过PDU2会话，将标签2的信息发送给UPF(2)网元；UE(读写器)通过PDU3会话，将标签3的信息发送给UPF(3)网元。
或者UE(读写器)通过PDU1会话，将标签1的信息发送给UPF(1)网元；UE(读写器)通过PDU2会话，将标签2的信息发送给UPF(1)网元；UE(读写器)通过PDU3会话，将标签3的信息发送给UPF(1)网元。
S817：UPF网元基于从不同的IP地址和/或端口号获取的标签信息，确定标签的目标企业服务器，并选择UPF网元到PIOT服务器的连接。
具体的，UPF网元可以基于上述步骤S812中所建立的关联关系，确定该UPF网元到PIOT服务器的连接。
例如，在上述步骤S816中，UE(读写器)将标签1的信息发送给UPF(1)网元，则在该步骤S817中，由UPF(1)网元基于关联关系，选择UPF网元(1)到PIOT1服务器的连接。在上述步骤S816中，UE(读写器)将标签2的信息发送给UPF(2)网元，则在该步骤S817中，由UPF(2)网元基于关联关系，选择UPF网元(2)到PIOT2服务器的连接。在上述步骤S816中，UE(读写器)将标签3的信息发送给UPF(3)网元，则在该步骤S817中，由UPF(3)网元基于关联关系，选择UPF网元(3)到PIOT3服务器的连接。
或者在上述步骤S816中，UE(读写器)将标签1的信息发送给UPF(1)网元，则在该步骤S817中，由UPF(1)网元基于关联关系，选择UPF网元(1)到PIOT1服务器的连接。在上述步骤S816中，UE(读写器)将标签2的信息也发送给UPF(1)网元，则在该步骤S817中，由UPF(1)网元基于关联关系，选择UPF网元(1)到PIOT2服务器的连接。在上述步骤S816中，UE(读写器)将标签3的信息发送给UPF(1)网元，则在该步骤S817中，由UPF(1)网元基于关联关系，选择UPF网元(1)到PIOT3服务器的连 接。
S818：UPF网元将标签的信息发送给对应的PIOT服务器。
其中，该标签的信息可以为标签的数据，或者该标签的信息可以仅包含该标签的标识。
例如，包括多个UPF网元的情况：UPF(1)网元通过上述步骤S817，选择UPF网元(1)到PIOT1服务器的连接，则在步骤S818中，通过UPF网元(1)到PIOT1服务器的连接，将标签1的信息传输给PIOT1服务器。UPF(2)网元通过上述步骤S817，选择UPF网元(2)到PIOT2服务器的连接，则在该步骤S818中，通过UPF网元(2)到PIOT2服务器的连接，将标签2的信息传输给PIOT2服务器。UPF(3)网元通过上述步骤S817，选择UPF网元(3)到PIOT3服务器的连接，则在该步骤S818中，通过UPF网元(3)到PIOT3服务器的连接，将标签3的信息传输给PIOT3服务器。
仅包括1个UPF网元，即UPF(1)网元的情况：UPF(1)网元通过上述步骤S817，选择UPF网元(1)到PIOT1服务器的连接，则在步骤S818中，通过UPF网元(1)到PIOT1服务器的连接，将标签1的信息传输给PIOT1服务器。UPF(1)网元通过上述步骤S817，选择UPF网元(1)到PIOT2服务器的连接，则在该步骤S818中，通过UPF网元(1)到PIOT2服务器的连接，将标签2的信息传输给PIOT2服务器。UPF(1)网元通过上述步骤S817，选择UPF网元(1)到PIOT3服务器的连接，则在该步骤S818中，通过UPF网元(1)到PIOT3服务器的连接，将标签3的信息传输给PIOT3服务器。
通过该实施例三，当UE不能获知PIOT服务器的地址信息和对应的端口号信息，UE可以请求不同标签归属企业的DNN/NSSAI，并通过UPF建立不同的通信会话，然后，UE基于增强的URSP策略选择第一通信会话，将目标标签的信息发送给对应的UPF网元，进一步由对应的UPF网元基于IP地址和端口号为该标签确定对应的PIOT服务器并将该标签的信息准确地传输给PIOT服务器。
实施例四
在该实施例四中，以终端设备UE作为读写器为例，基于上述图3C所示的第三种传输路径，主要由UE(读写器)执行标签的管理，通过控制面通道传输，即PIOT服务器通过NEF网元向AMF网元发送指令。参考图9所示，具体流程如下：
S900：UE(读写器)完成注册流程。
UE(读写器)具体执行注册的流程可以参考现有的技术实现，此处不再描述。
S901：PIOT服务器向NEF网元发送盘存请求消息。
相应的，NEF网元(相当于上述本申请的第一网元)接收该盘存请求消息，其中，该盘存请求消息中携带标签操作命令、第二标签过滤器(如盘存区域，盘存类型，盘存规则等)以及上报触发事件(如盘点周期、新标签接入事件、标签离开)等信息。
S902：NEF网元记录发送盘存请求消息的PIOT服务器的地址。
具体的，NEF网元针对每次接收的盘存请求消息，分别记录该盘存请求消息来源的PIOT服务器(即企业的应用服务器)的地址。
S903：NEF网元生成一个操作标识并向AMF网元发送第一信令。
示例性的，该第一信令可以为第一消息。
具体的，该操作标识(相对于上述本申请的第一标识)可以用于NEF网元唯一确定该第一信令。NEF网元可以通过确定第一信令，来进一步确定触发该第一信令的盘存请求消 息，从而确定记录的PIOT服务器的地址信息。
相应的，AMF网元接收该第一信令，其中，该第一信令中携带操作标识，以及上述盘存请求消息包括的信息，即标签操作命令、第二标签过滤器(盘点区域)以及上报触发事件等信息。由于第一信令由上述盘存请求消息触发，因此上述操作标识还可以用来标识该第一消息。
S904：AMF网元向UE(读写器)发送第一消息。
示例性的，该第一消息可以为NAS消息。
相应的，该UE(相当于上述本申请的第二网元)接收该第一消息，该第一消息中包含上述第一信令，因此该第一消息中也包含上述的操作标识(第一消息标识)、标签操作命令、第二标签过滤器(盘点区域)以及上报触发事件等信息。
S905：UE(读写器)基于第二标签过滤器，识别和确定第一标签。
其中，该第一标签可以是一组满足标签过滤器规则的标签，也可以是特定标签标识的一个标签，本申请实施例对此不做限定。
例如，UE(读写器)侧接入的标签，基于第二标签过滤器，为该标签匹配到标签ID为(1)，并根据标签(1)识别对应的操作标识(1)。
应理解的是，上述的第二标签过滤器可以用于为接入的标签匹配对应的ID，而且该第二标签过滤器还可以用于根据标签ID确定对应的操作标识。例如，该第二标签过滤器中可以包括标签ID与操作标识之间的对应关系，即一个标签ID对应一个操作标识，或者多个标签ID对应一个操作标识。此外，一个操作标识可以用于确定唯一的目标服务器，但一个目标服务器可能对应多个操作标识，即相同的目标服务器可在多次的标签盘存请求中，将在NEF网元上生成不同的操作标识。
S906：UE(读写器)根据标签操作命令，执行标签操作。
S907：UE(读写器)向AMF网元发送第二消息。
示例性的，该第二消息可以为上行NAS传输消息。
相应的，AMF网元接收该第二消息，该第二消息中携带接入的标签的信息以及相应的操作标识。
例如，该上行NAS传输消息中携带标签(1)的数据(或信息)，以及标签(1)对应的操作标识(1)。
S908：AMF网元向NEF网元发送数据传输消息。
示例性的，该数据传输消息也可以为第二消息。
相应的，NEF网元接收该数据传输消息，该数据传输消息中携带接入的标签的信息以及相应的操作标识(即第一消息标识)。
其中，该标签的信息可以为标签的数据，或者该标签的信息可以仅包含该标签的标识。
S909：NEF网元识别数据传输消息中的操作标识，并确定对应的PIOT服务器的地址。
由于在步骤S903中，NEF网元已预先记录了第一消息，并为其生成了唯一的操作标识，即记录了操作标识与第一消息之间的对应关系。当NEF网元确定该数据传输消息与第一消息关联时，可以进一步基于该第一消息与触发第一消息的盘存请求消息来确定PIOT服务器的地址信息。因此，当NEF网元通过AMF网元接收到UE(读写器)反馈的操作标识时，可以确定对应的PIOT服务器的地址。
S910：NEF网元将数据传输消息中携带的标签的信息，发送给对应的PIOT服务器。
NEF网元根据PIOT服务器的地址，将标签的信息发送给对应的该PIOT服务器。
通过该实施例四，基于控制面建立标签与PIOT服务器(即企业的应用服务器)的连接，且由读写器进行标签识别和管理。此外，由于该实施例四的方案是通过控制面传输标签的信息，因此，不需要建立会话的流程，从而可节省信令流程，也可减少传输标签的信息所需的时延。
实施例五
在该实施例五中，以终端设备UE作为读写器为例，基于上述图3C所示的第三种传输路径，主要由UE(读写器)执行标签的管理，通过控制面通道传输，即PIOT服务器通过NEF网元向AMF网元发送指令。然而，该实施例五中，UE(读写器)可以将接入的所有标签的信息(信息)发送给AMF网元(相当于上述本申请的第二网元)，由AMF网元替代UE(读写器)执行标签的管理和识别。参考图10所示，传输标签的信息具体流程如下：
S1000：UE(读写器)完成注册流程。
UE(读写器)具体执行注册的流程可以参考现有的技术实现，此处不再描述。
S1001：PIOT服务器向NEF网元发送盘存请求消息。
相应的，该NEF网元(相当于上述本申请的第一网元)接收该盘存请求消息，其中，该盘存请求消息中携带标签操作命令、第二标签过滤器(如盘存区域，盘存类型，盘存规则等)以及上报触发事件(如盘点周期、新标签接入事件、标签离开)等信息。
该步骤S1001可以与上述步骤S901相互参考。
S1002：NEF网元记录发送盘存请求消息的PIOT服务器的地址。
具体的，NEF网元可以针对每次接收的盘存请求消息，分别记录该盘存请求消息来源的PIOT服务器(即企业的应用服务器)的地址。
该步骤S1002可以与上述步骤S902相互参考。
S1003：NEF网元生成一个操作标识并向AMF网元发送第一消息。
具体的，该操作标识(相当于上述本申请的第一标识)可以用于NEF网元唯一确定该第一消息。NEF网元可以通过确定第一消息，来进一步确定触发该第一消息的盘存请求消息，从而确定记录的PIOT服务器的地址信息。
相应的，AMF网元(相当于上述本申请的第二网元)接收该第一消息，其中，该第一消息中携带操作标识，以及上述盘存请求消息包括的信息，即标签操作命令、第二标签过滤器(盘点区域)以及上报触发事件等信息。由于第一消息由上述盘存请求消息触发，因此上述操作标识还可以用来标识该第一消息。
该步骤S1003可以与上述步骤S903相互参考。
S1004：AMF网元向UE(读写器)发送第三消息。
示例性的，该第三消息可以是NAS消息。
相应的，UE(读写器)接收该第三消息，该第三消息中携带上述第一消息中的标签操作命令，以及上报触发事件等信息。
S1005：UE(读写器)根据标签操作命令，对所有信号范围内的标签执行标签操作。
S1006：UE(读写器)向AMF网元发送第四消息。
示例性的，该第四消息可以是上行NAS消息。
UE(读写器)根据标签操作命令，对所有信号范围内的标签执行标签操作，将操作结果(即收集的标签的信息)携带在第四消息(如上行NAS消息)中，并发送给AMF网元。
S1007：AMF网元基于对应的第二标签过滤器，识别和确定第一标签。
其中，该第一标签可以是一组满足标签过滤器规则的标签，也可以是特定标签标识的一个标签。
AMF网元识别和确定第一标签之后，AMF网元还可以将该第一标签的信息添加上对应的操作标识。
S1008：AMF网元向NEF网元发送第二消息。
示例性的，该第二消息可以是数据传输消息。
相应的，NEF网元接收该第二消息，该第二消息中携带接入的标签的信息以及相应的操作标识。
S1009：NEF网元识别第二消息中的操作标识，并确定对应的PIOT服务器的地址。
由于在步骤S1003中，NEF网元已预先记录了第一消息，并为其生成了唯一的操作标识，即记录了操作标识与第一消息之间的对应关系。当NEF网元确定该第二消息与第一消息关联时，可以进一步基于该第一消息与触发第一消息的盘存请求消息来确定对应的PIOT服务器的地址信息。因此，当NEF网元通过AMF网元接收到UE(读写器)反馈的操作标识时，可以确定对应的PIOT服务器的地址。
S1010：NEF网元将第二消息中携带的标签的信息，发送给对应的PIOT服务器。
其中，该标签的信息可以为标签的数据，或者该标签的信息可以仅包含该标签的标识。
NEF网元根据PIOT服务器的地址，将标签的信息发送给对应的PIOT服务器。
通过该实施例五，基于控制面建立UE(读写器)与PIOT服务器(即企业的应用服务器)的连接，即通过控制面传输标签的信息，因此，不需要建立会话的流程，从而可节省信令流程，也可减少传输标签的信息所需的时延。此外，UE(读写器)可以将基于操作命令所收集的标签的信息发送给AMF网元，由AMF网元替代UE(读写器)执行标签的管理和识别，以降低读写器的能力要求(即无需读写器存储和处理第二标签过滤器相关的信息)。
基于同一技术构思，本申请实施例提供一种通信装置，该通信装置可以包括执行上述第一种方法实施例中第一通信装置所描述的方法/操作/步骤/动作所一一对应的模块或单元，该模块或单元可以是硬件电路，也可是软件，也可以是硬件电路结合软件实现。该装置可以具有如图11所示的结构。
如图11所示，该通信装置1100可包括接收单元1101、处理单元1102、发送单元1103，下面对各单元进行具体的介绍。其中，所述接收单元1101，用于接收第一请求，所述第一请求指示所述第一通信装置获取第一标签的信息；所述接收单元1101，还用于根据所述第一请求，获取所述第一标签的信息，所述第一标签的信息包含所述第一标签的标识；所述处理单元1102，用于根据所述第一标签的标识，确定第一通信会话，所述第一通信会话用于传输所述第一标签的信息；所述发送单元1103，用于通过所述第一通信会话，发送所述第一标签的信息。
可选地，该通信装置1100还可包括存储单元(图11中未画出)，所述存储单元可以用于存储执行该通信装置所描述的方法/操作/步骤/动作的计算机程序和/或指令和/或信息等。
在一种可能的实施方式中，所述处理单元1102在根据所述第一标签的标识，确定第一通信会话时，具体用于：根据所述第一标签的标识和第一路由策略信息，从至少一个通信会话中确定所述第一通信会话，所述第一路由策略信息包含所述第一标签的标识和所述第一通信会话的标识的对应关系。
在一种可能的实施方式中，所述处理单元1102，还用于：在所述接收单元1101接收第一请求之前，建立至少一个通信会话，所述至少一个通信会话中包括所述第一通信会话；建立至少一个路由策略信息，每个所述路由策略信息包括对应的标签和通信会话的标识的对应关系。
在一种可能的实施方式中，所述处理单元1102在建立所述第一通信会话时，具体用于：
通过所述发送单元1103发送第一会话请求消息，所述第一会话请求消息包含第一指示信息，所述第一指示信息指示所述第一标签的归属企业信息；通过所述接收单元1101接收第一响应消息，所述第一响应消息用于响应所述第一会话请求消息，所述第一响应消息中包含第一目标地址信息，和/或第一端口号信息，其中，所述第一目标地址信息，和/或所述第一端口号信息是根据所述第一指示信息确定的；根据所述第一目标地址信息，和/或所述第一端口号信息，建立所述第一通信会话；所述第一目标地址信息，和/或所述第一端口号信息用于确定目标服务器，所述目标服务器为所述归属企业的服务器。
在一种可能的实施方式中，所述发送单元1103在通过所述第一通信会话，发送所述第一标签的信息时，具体用于：通过所述第一通信会话，向所述目标服务器发送所述第一标签的信息。
在一种可能的实施方式中，所述处理单元1102在建立所述第一通信会话时，具体用于：
通过所述发送单元1103发送第二会话请求消息，所述第二会话请求消息包含第二指示信息，所述第二指示信息指示所述第一标签的归属企业信息；通过所述接收单元1101接收第二响应消息，所述第二响应消息用于响应所述第二会话请求消息，所述第二响应消息中包含第二目标地址信息，和/或第二端口号信息；其中，所述第二目标地址信息，和/或所述第二端口号信息是根据所述第二指示信息确定的；根据所述第二目标地址信息，和/或所述第二端口号信息，建立所述第一通信会话；所述第二目标地址信息，和/或所述第二端口号信息用于确定第一用户面功能网元，所述第一用户面功能网元是为所述归属企业提供服务的用户面网元。
在一种可能的实施方式中，所述发送单元1103在通过所述第一通信会话，发送所述第一标签的信息时，具体用于：通过所述第一通信会话，向所述第一用户面功能网元发送所述第一标签的信息。
基于同一技术构思，本申请实施例提供一种通信装置，该通信装置可以包括执行上述第一种方法实施例中第一用户面功能网元所描述的方法/操作/步骤/动作所一一对应的模块或单元，该模块或单元可以是硬件电路，也可是软件，也可以是硬件电路结合软件实现。该装置也可以具有如图11所示的结构，该通信装置1100可以包括接收单元1101、处理单元1102、发送单元1103。其中，所述接收单元1101，用于接收第一标签的信息和第一信息，所述第一信息用于确定所述第一标签的目标服务器；所述处理单元1102，用于根据所述第一信息，确定所述第一标签的目标服务器；所述发送单元1103，用于将所述第一标签的信息发送给所述目标服务器。
可选地，该通信装置1100还可包括存储单元(图11中未画出)，所述存储单元可以用于存储执行该第一用户面功能网元所描述的方法/操作/步骤/动作的计算机程序和/或指令和/或信息等。
在一种可能的实施方式中，所述接收单元1101在接收第一信息时，具体用于：接收N4会话请求消息，所述N4会话请求消息中包括所述第一信息，所述第一信息指示第一标签过滤器，所述第一标签过滤器用于根据标签的标识匹配对应的服务器；
所述处理单元1102在根据所述第一信息，确定所述第一标签的目标服务器时，具体可用于：根据所述第一信息，确定所述第一标签过滤器；基于所述第一标签的标识，使用所述第一标签过滤器匹配到所述第一标签的目标服务器。
在一种可能的实施方式中，所述接收单元1101在接收第一标签的信息时，具体可用于：从第一通信装置接收所述第一标签的信息；
所述接收单元1101在接收第一信息时，具体用于：接收N4会话请求消息，所述N4会话请求消息中包括所述第一信息，所述第一信息指示所述第一通信装置的地址信息和/或所述第一通信装置发送所述第一标签的信息的第三端口号信息；
所述处理单元1102在根据所述第一信息，确定所述第一标签的目标服务器时，具体可用于：根据所述第一信息，确定所述第一通信装置的地址信息和/或所述第三端口号信息；根据所述第一通信装置的地址信息和所述第三端口号信息，以及第一映射信息，确定所述第一标签的目标服务器；其中，所述第一映射信息中包括所述第一通信装置的地址信息和/或端口号信息与服务器的标识的对应关系。
在一种可能的实施方式中，所述接收单元1101在接收第一信息时，具体可用于：接收N4会话请求消息，所述N4会话请求消息中包括所述第一信息，所述第一信息指示所述第一用户面功能网元上接收所述第一标签的信息的第四端口号信息；
所述处理单元1102在根据所述第一信息，确定所述第一标签的目标服务器时，具体可用于：根据所述第一信息，确定所述第一用户面功能网元上接收所述第一标签的信息的第四端口号信息；根据所述第四端口号信息和第二映射信息，确定所述第一标签的目标服务器；其中，所述第二映射信息中包括所述第一用户面功能网元上的端口号信息和服务器的标识的对应关系。
在一种可能的实施方式中，所述接收单元1101在接收第一信息时，具体可用于：接收N4会话请求消息，所述N4会话请求消息中包括所述第一信息，所述第一信息指示所述目标服务器的地址信息和/或所述目标服务器上用于接收所述第一标签的信息的第五端口号信息；其中，所述目标服务器的地址信息和/或所述第五端口号信息是根据第二指示信息确定的，所述第二指示信息指示所述第一标签的归属企业信息，所述第二指示信息携带在第一通信装置发送的第二会话请求消息中；
所述处理单元1102在根据所述第一信息，确定所述第一标签的目标服务器时，具体可用于：根据所述第一信息，确定所述目标服务器的地址信息和/或所述第五端口号信息；根据所述目标服务器的地址信息和/或所述第五端口号信息，确定所述目标服务器。
基于同一技术构思，本申请实施例提供一种通信装置，该通信装置可以包括执行上述第二种方法实施例中第一网元(如网络能力开放功能网元)所描述的方法/操作/步骤/动作所一一对应的模块或单元，该模块或单元可以是硬件电路，也可是软件，也可以是硬件电 路结合软件实现。
该装置也可以具有如图11所示的结构，该通信装置1100可以包括接收单元1101、处理单元1102、发送单元1103。其中，所述接收单元1101，用于接收第二消息，所述第二消息中包括第一标签的信息和第一标识，所述第一标识用于确定所述第一标签的目标服务器；所述处理单元1102用于根据所述第一标识，确定所述第一标签的目标服务器；所述发送单元1103，用于将所述第一标签的信息发送给所述目标服务器。
可选地，该通信装置1100还可包括存储单元(图11中未画出)，所述存储单元可以用于存储执行该第一网元所描述的方法/操作/步骤/动作的计算机程序和/或指令和/或信息等。
在一种可能的实施方式中，所述处理单元1102在根据所述第一标识，确定所述第一标签的目标服务器时，具体用于：根据所述第一标识和第一对应关系，确定所述第一标签的目标服务器，其中，所述第一对应关系包括所述第一标识与所述目标服务器的对应关系。
在一种可能的实施方式中，所述发送单元1103，还用于：在所述接收单元1101接收第二消息之前，向第二网元发送第一消息，所述第一消息中包括第一操作指令和第二标签过滤器，以及所述第一标识，所述第一操作指令用于指示所述第二网元获取至少一个标签的标识，所述第二标签过滤器用于根据不同标签的标识确定对应的标签。
基于同一技术构思，本申请实施例提供一种通信装置，该通信装置可以包括执行上述第二种方法实施例中第二网元所描述的方法/操作/步骤/动作所一一对应的模块或单元，该模块或单元可以是硬件电路，也可是软件，也可以是硬件电路结合软件实现。
该装置也可以具有如图11所示的结构，该通信装置1100可以包括接收单元1101、处理单元1102、发送单元1103。其中，所述接收单元1101，用于接收第一消息，所述第一消息中包括第一操作指令和第二标签过滤器，以及第一标识；其中，所述第一操作指令用于指示所述第二网元获取至少一个标签的标识，所述第二标签过滤器用于根据不同标签的标识确定对应的标签，所述第一标识用于确定第一标签的目标服务器；所述处理单元1102，用于根据所述第一操作指令，基于第一标签的标识匹配所述第二标签过滤器，得到所述第一标签；所述发送单元1103，用于发送第二消息，所述第二消息中包括所述第一标签的信息和所述第一标识。
可选地，该通信装置1100还可包括存储单元(图11中未画出)，所述存储单元可以用于存储执行该第二网元所描述的方法/操作/步骤/动作的计算机程序和/或指令和/或信息等。
在一种可能的实施方式中，所述接收单元1101在接收第一消息时，具体可用于：从移动性管理网元接收所述第一消息；所述发送单元1103在发送第二消息时，具体可用于：向所述移动性管理网元发送所述第二消息。
在一种可能的实施方式中，所述接收单元1101在接收第一消息时，具体可用于：从第一网元接收所述第一消息；所述发送单元1103在发送第二消息时，具体可用于：向所述第一网元发送所述第二消息。
基于同一发明构思，本申请实施例还提供了一种通信设备，该通信设备采用图5A，以及图6-图8对应的实施例提供的方法中第一通信装置执行的步骤，可以是与图11所示的通信装置1100相同的设备。参阅图12所示，通信设备1200包括：收发器1201、处理器1202和存储器1203。其中，收发器1201、处理器1202和存储器1203通过通信总线1204连接，以便实现数据交换。
其中，通信总线1204可以是外设部件互连标准(peripheral component interconnect，简称PCI)总线或扩展工业标准结构(extended industry standard architecture，简称EISA)总线等。所述通信总线1204可以分为地址总线、数据总线、控制总线等。为便于表示，图12中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
应理解，其中，该通信设备1200中收发器1201包括上述通信装置1100中的接收单元1101和发送单元1103的功能。该收发器1201用于支持通信装置1100与上述实施例中的第一用户面功能网元之间收发信息、数据等。存储器1203用于通信设备1200的程序代码和数据。处理器1202用于调用存储器1203中存储的程序代码和数据，执行图5A，以及图6-图8所示方法中涉及第一通信装置的处理过程和/或用于本申请所描述的技术的其他过程。
此外，通信设备1200还可以包括其他接口，例如光纤链路接口、以太网接口、微波链路接口、铜线接口等，用以实现通信设备1200与其他设备(例如，接入网设备、策略控制网元)的交互。
可选的，处理器1202可以是中央处理器、ASIC、FPGA或CPLD。
需要说明的是，图12示出的通信设备1200中仅包含一个收发器1201、一个处理器1202和一个存储器1203。实际实现时，收发器1201、处理器1202和存储器1203的数量可以为一个，也可以为多个。
同样说明的是，图12示出的通信设备1200也可以实现图5A以及图6-图8对应的实施例提供的方法中第一用户面功能网元执行的方法，或者可以实现图5B以及图9-图10对应的实施例提供的方法中第一网元执行的方法，或者可以实现图5B以及图9-图10对应的实施例提供的方法中第二网元执行的方法。图12示出的通信设备1200也可以是与上述图11所示的通信装置1100相同的设备。因此，通信设备1200未详细描述的实现方式可以参照图5A-5B，以及图6-图10对应的实施例提供的方法中的相关描述或者参考上述图12所示的通信设备1200中的相关描述。此处不再具体赘述。
图13为本申请实施例提供的一种芯片的装置结构示意图。该芯片1300包括接口电路1301和一个或多个处理器1302。可选的，所述芯片1300还可以包含总线。其中：
处理器1302可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述眼球跟踪方法的各步骤可以通过处理器1302中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器1302可以是通用处理器、数字通信器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)或者其它可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
接口电路1301可以用于数据、指令或者信息的发送或者接收，处理器1302可以利用接口电路1301接收的数据、指令或者其它信息，进行加工，可以将加工完成信息通过接口电路1301发送出去。
可选的，芯片还包括存储器1303，存储器1303可以包括只读存储器和随机存取存储器，并向处理器提供操作指令和数据。存储器1303的一部分还可以包括非易失性随机存取存储器(NVRAM)。
可选的，存储器存储了可执行软件模块或者数据结构，处理器可以通过调用存储器存储的操作指令(该操作指令可存储在操作系统中)，执行相应的操作。
可选的，芯片可以使用在本申请实施例涉及的第一通信装置中。可选的，接口电路1301可用于输出处理器1302的执行结果。关于本申请的一个或多个实施例提供的通信方法可参考前述各个实施例，这里不再赘述。
需要说明的，接口电路1301、处理器1302各自对应的功能既可以通过硬件设计实现，也可以通过软件设计来实现，还可以通过软硬件结合的方式来实现，这里不作限制。
基于与上述方法实施例相同构思，本申请实施例还提供了一种计算机可读存储介质，其上存储有一些指令，这些指令被计算机调用执行时，可以使得计算机完成上述方法实施例、方法实施例的任意一种可能的设计中所涉及的方法。本申请实施例中，对计算机可读存储介质不做限定，例如，可以是RAM(r网络设备dom-access memory，随机存取存储器)、ROM(read-only memory，只读存储器)等。
基于与上述方法实施例相同构思，本申请还提供一种计算机程序产品，该计算机程序产品在被计算机调用执行时可以完成方法实施例以及上述方法实施例任意可能的设计中所涉及的方法。
基于与上述方法实施例相同构思，本申请还提供一种芯片，该芯片可以包括处理器以及接口电路，用于完成上述方法实施例、方法实施例的任意一种可能的实现方式中所涉及的方法，其中，“耦合”是指两个部件彼此直接或间接地结合，这种结合可以是固定的或可移动性的，这种结合可以允许流动液、电、电信号或其它类型信号在两个部件之间进行通信。
需要注意的是，本申请实施例涉及的至少一个，包括一个或者多个；其中，多个是指大于或者等于两个。另外，需要理解的是，在本申请的描述中，“第一”、“第二”等词汇，仅用于区分描述的目的，而不能理解为指示或暗示相对重要性，也不能理解为指示或暗示顺序。
以下实施例中所使用的术语只是为了描述特定实施例的目的，而并非旨在作为对本申请的限制。如在本申请的说明书和所附权利要求书中所使用的那样，单数表达形式“一种”、“所述”、“上述”、“该”和“这一”旨在也包括例如“一个或多个”这种表达形式，除非其上下文中明确地有相反指示。还应当理解，在本申请实施例中，“一个或多个”是指一个或两个以上(包含两个)；“和/或”，描述关联对象的关联关系，表示可以存在三种关系；例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B的情况，其中A、B可以是单数或者复数。字符“/”一般表示前后关联对象是一种“或”的关系。
在本说明书中描述的参考“一个实施例”或“一些实施例”等意味着在本申请的一个或多个实施例中包括结合该实施例描述的特定特征、结构或特点。由此，在本说明书中的不同之处出现的语句“在一个实施例中”、“在一些实施例中”、“在其他一些实施例中”、“在另外一些实施例中”等不是必然都参考相同的实施例，而是意味着“一个或多个但不是所有的实施例”，除非是以其他方式另外特别强调。术语“包括”、“包含”、“具有”及它们的变形都意味着“包括但不限于”，除非是以其他方式另外特别强调。
本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，另外，在本申请各个实施例中的各功能模块可以集成在一个处理器中，也可以是单独物理存在，也可以两个或两个以上模块集成在一个模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。
本申请实施例提供了一种计算机可读存储介质，存储有计算机程序，该计算机程序包 括用于执行上述方法实施例的指令。
本申请实施例提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述方法实施例。
本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，另外，在本申请各个实施例中的各功能模块可以集成在一个处理器中，也可以是单独物理存在，也可以两个或两个以上模块集成在一个模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。
通过以上的实施方式的描述，所属领域的技术人员可以清楚地了解到本申请实施例可以用硬件实现，或固件实现，或它们的组合方式来实现。当使用软件实现时，可以将上述功能存储在计算机可读介质中或作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是计算机能够存取的任何可用介质。以此为例但不限于：计算机可读介质可以包括RAM、ROM、电可擦可编程只读存储器(electrically erasable programmable read only memory，EEPROM)、只读光盘(compact disc read-Only memory，CD-ROM)或其他光盘存储、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质。此外。任何连接可以适当的成为计算机可读介质。例如，如果软件是使用同轴电缆、光纤光缆、双绞线、数字用户线(digital subscriber line，DSL)或者诸如红外线、无线电和微波之类的无线技术从网站、服务器或者其他远程源传输的，那么同轴电缆、光纤光缆、双绞线、DSL或者诸如红外线、无线和微波之类的无线技术包括在所属介质的定影中。如本申请实施例所使用的，盘(disk)和碟(disc)包括压缩光碟(compact disc，CD)、激光碟、光碟、数字通用光碟(digital video disc，DVD)、软盘和蓝光光碟，其中盘通常磁性的复制数据，而碟则用激光来光学的复制数据。上面的组合也应当包括在计算机可读介质的保护范围之内。
总之，以上所述仅为本申请的实施例而已，并非用于限定本申请的保护范围。凡根据本申请的揭露，所作的任何修改、等同替换、改进等，均应包含在本申请的保护范围之内。

Claims (26)

  1. 一种通信方法，其特征在于，包括：
    第一通信装置接收第一请求，所述第一请求指示所述第一通信装置获取第一标签的信息；
    所述第一通信装置根据所述第一请求，获取所述第一标签的信息，所述第一标签的信息包含所述第一标签的标识；
    所述第一通信装置根据所述第一标签的标识，确定第一通信会话，所述第一通信会话用于传输所述第一标签的信息；
    所述第一通信装置通过所述第一通信会话，发送所述第一标签的信息。
  2. 根据权利要求1所述的方法，其特征在于，所述第一通信装置根据所述第一标签的标识，确定第一通信会话，包括：
    所述第一通信装置根据所述第一标签的标识和第一路由策略信息，从至少一个通信会话中确定所述第一通信会话，所述第一路由策略信息包含所述第一标签的标识和所述第一通信会话的标识的对应关系。
  3. 根据权利要求1或2所述的方法，其特征在于，所述第一通信装置接收第一请求之前，还包括：
    所述第一通信装置建立至少一个通信会话，所述至少一个通信会话中包括所述第一通信会话；
    所述第一通信装置建立至少一个路由策略信息，每个所述路由策略信息包括对应的标签和通信会话的标识的对应关系。
  4. 根据权利要求3所述的方法，其特征在于，所述第一通信装置建立所述第一通信会话，包括：
    所述第一通信装置发送第一会话请求消息，所述第一会话请求消息包含第一指示信息，所述第一指示信息指示所述第一标签的归属企业信息；
    所述第一通信装置接收第一响应消息，所述第一响应消息用于响应所述第一会话请求消息，所述第一响应消息中包含第一目标地址信息，和/或第一端口号信息，其中，所述第一目标地址信息，和/或所述第一端口号信息是根据所述第一指示信息确定的；
    所述第一通信装置根据所述第一目标地址信息，和/或所述第一端口号信息，建立所述第一通信会话；所述第一目标地址信息，和/或所述第一端口号信息用于确定目标服务器，所述目标服务器为所述归属企业的服务器。
  5. 根据权利要求4所述的方法，其特征在于，所述第一通信装置通过所述第一通信会话，发送所述第一标签的信息，包括：
    所述第一通信装置通过所述第一通信会话，向所述目标服务器发送所述第一标签的信息。
  6. 根据权利要求3所述的方法，其特征在于，所述第一通信装置建立所述第一通信会话，包括：
    所述第一通信装置发送第二会话请求消息，所述第二会话请求消息包含第二指示信息，所述第二指示信息指示所述第一标签的归属企业信息；
    所述第一通信装置接收第二响应消息，所述第二响应消息用于响应所述第二会话请求 消息，所述第二响应消息中包含第二目标地址信息，和/或第二端口号信息；其中，所述第二目标地址信息，和/或所述第二端口号信息是根据所述第二指示信息确定的；
    所述第一通信装置根据所述第二目标地址信息，和/或所述第二端口号信息，建立所述第一通信会话；所述第二目标地址信息，和/或所述第二端口号信息用于确定第一用户面功能网元，所述第一用户面功能网元是为所述归属企业提供服务的用户面网元。
  7. 根据权利要求6所述的方法，其特征在于，所述第一通信装置通过所述第一通信会话，发送所述第一标签的信息，包括：
    所述第一通信装置通过所述第一通信会话，向所述第一用户面功能网元发送所述第一标签的信息。
  8. 一种通信方法，其特征在于，包括：
    第一用户面功能网元接收第一标签的信息和第一信息，所述第一信息用于确定所述第一标签的目标服务器；
    所述第一用户面功能网元根据所述第一信息，确定所述第一标签的目标服务器；
    所述第一用户面功能网元将所述第一标签的信息发送给所述目标服务器。
  9. 根据权利要求8所述的方法，其特征在于，所述第一用户面功能网元接收第一信息，包括：
    所述第一用户面功能网元接收N4会话请求消息，所述N4会话请求消息中包括所述第一信息，所述第一信息指示第一标签过滤器，所述第一标签过滤器用于根据标签的标识匹配对应的服务器；
    所述第一用户面功能网元根据所述第一信息，确定所述第一标签的目标服务器，包括：
    所述第一用户面功能网元根据所述第一信息，确定所述第一标签过滤器；
    所述第一用户面功能网元基于所述第一标签的标识，使用所述第一标签过滤器匹配到所述第一标签的目标服务器。
  10. 根据权利要求8所述的方法，其特征在于，所述第一用户面功能网元接收第一标签的信息，包括：
    所述第一用户面功能网元从第一通信装置接收所述第一标签的信息；
    所述第一用户面功能网元接收第一信息，包括：
    所述第一用户面功能网元接收N4会话请求消息，所述N4会话请求消息中包括所述第一信息，所述第一信息指示所述第一通信装置的地址信息和/或所述第一通信装置发送所述第一标签的信息的第三端口号信息；
    所述第一用户面功能网元根据所述第一信息，确定所述第一标签的目标服务器，包括：
    所述第一用户面功能网元根据所述第一信息，确定所述第一通信装置的地址信息和/或所述第三端口号信息；
    所述第一用户面功能网元根据所述第一通信装置的地址信息和所述第三端口号信息，以及第一映射信息，确定所述第一标签的目标服务器；其中，所述第一映射信息中包括所述第一通信装置的地址信息和/或端口号信息与服务器的标识的对应关系。
  11. 根据权利要求8所述的方法，其特征在于，所述第一用户面功能网元接收第一信息，包括：
    所述第一用户面功能网元接收N4会话请求消息，所述N4会话请求消息中包括所述第一信息，所述第一信息指示所述第一用户面功能网元上接收所述第一标签的信息的第四端 口号信息；
    所述第一用户面功能网元根据所述第一信息，确定所述第一标签的目标服务器，包括：
    所述第一用户面功能网元根据所述第一信息，确定所述第一用户面功能网元上接收所述第一标签的信息的第四端口号信息；
    所述第一用户面功能网元根据所述第四端口号信息和第二映射信息，确定所述第一标签的目标服务器；其中，所述第二映射信息中包括所述第一用户面功能网元上的端口号信息和服务器的标识的对应关系。
  12. 根据权利要求8所述的方法，其特征在于，所述第一用户面功能网元接收第一信息，包括：
    所述第一用户面功能网元接收N4会话请求消息，所述N4会话请求消息中包括所述第一信息，所述第一信息指示所述目标服务器的地址信息和/或所述目标服务器上用于接收所述第一标签的信息的第五端口号信息；其中，所述目标服务器的地址信息和/或所述第五端口号信息是根据第二指示信息确定的，所述第二指示信息指示所述第一标签的归属企业信息，所述第二指示信息携带在第一通信装置发送的第二会话请求消息中；
    所述第一用户面功能网元根据所述第一信息，确定所述第一标签的目标服务器，包括：
    所述第一用户面功能网元根据所述第一信息，确定所述目标服务器的地址信息和/或所述第五端口号信息；
    所述第一用户面功能网元根据所述目标服务器的地址信息和/或所述第五端口号信息，确定所述目标服务器。
  13. 一种通信方法，其特征在于，包括：
    第一网元接收第二消息，所述第二消息中包括第一标签的信息和第一标识，所述第一标识用于确定所述第一标签的目标服务器；
    所述第一网元根据所述第一标识，确定所述第一标签的目标服务器；
    所述第一网元将所述第一标签的信息发送给所述目标服务器。
  14. 根据权利要求13所述的方法，其特征在于，所述第一网元根据所述第一标识，确定所述第一标签的目标服务器，包括：
    所述第一网元根据所述第一标识和第一对应关系，确定所述第一标签的目标服务器，其中，所述第一对应关系包括所述第一标识与所述目标服务器的对应关系。
  15. 根据权利要求13所述的方法，其特征在于，所述第一网元接收第二消息之前，还包括：
    所述第一网元向第二网元发送第一消息，所述第一消息中包括第一操作指令和第二标签过滤器，以及所述第一标识，所述第一操作指令用于指示所述第二网元根据所述第一标识从至少一个标签的标识中获取所述第一标签的标识，所述第二标签过滤器用于根据不同标签的标识确定对应的标签的信息。
  16. 一种通信方法，其特征在于，包括：
    第二网元接收第一消息，所述第一消息中包括第一操作指令和第二标签过滤器，以及第一标识；其中，所述第一操作指令用于指示所述第二网元获取至少一个标签的标识，所述第二标签过滤器用于根据不同标签的标识确定对应的标签的信息，所述第一标识用于确定第一标签的目标服务器；
    所述第二网元根据所述第一操作指令和所述第一标识，获取所述第一标签的标识，并 基于所述第一标签的标识匹配所述第二标签过滤器，得到所述第一标签的信息；
    所述第二网元发送第二消息，所述第二消息中包括所述第一标签的信息和所述第一标识。
  17. 根据权利要求16所述的方法，其特征在于，所述第二网元接收第一消息，包括：
    所述第二网元从移动性管理功能网元接收所述第一消息；
    所述第二网元发送第二消息，包括：
    所述第二网元向所述移动性管理功能网元发送所述第二消息。
  18. 根据权利要求16所述的方法，其特征在于，所述第二网元接收第一消息，包括：
    所述第二网元从第一网元接收所述第一消息；
    所述第二网元发送第二消息，包括：
    所述第二网元向所述第一网元发送所述第二消息。
  19. 一种通信装置，其特征在于，包括用于执行如权利要求1至7中任一项所述方法的单元或模块，或者包括用于执行如权利要求8至12中任一项所述方法的单元或模块。
  20. 一种通信装置，其特征在于，包括用于执行如权利要求13至15中任一项所述方法的单元或模块，或者包括用于执行如权利要求16至18中任一项所述方法的单元或模块。
  21. 一种通信装置，其特征在于，包括：处理器；所述处理器用于从存储器中读取并运行程序，以实现如权利要求1至7，或者8至12中任一项所述的方法。
  22. 一种通信装置，其特征在于，包括：处理器；所述处理器用于从存储器中读取并运行程序，以实现如权利要求13至15，或者16至18中任一项所述的方法。
  23. 一种通信系统，其特征在于，包括：用于执行权利要求1至7中任一项所述方法的第一通信装置，以及用于执行权利要求8至12中任一项所述方法的第一用户面功能网元。
  24. 一种通信系统，其特征在于，包括：用于执行权利要求13至15中任一项所述方法的第一网元，以及用于执行权利要求16至18中任一项所述方法的第二网元。
  25. 一种计算机程序产品，其特征在于，包括计算机程序，当所述计算机程序被通信装置执行时，实现如权利要求1至18中任一项所述的方法。
  26. 一种计算机可读存储介质，其特征在于，所述存储介质中存储有计算机可读程序或指令，当所述计算机程序或指令被通信装置执行时，实现如权利要求1至18中任一项所述的方法。
PCT/CN2023/096809 2022-06-22 2023-05-29 一种通信方法和装置 WO2023246431A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210714032.2 2022-06-22
CN202210714032.2A CN117319972A (zh) 2022-06-22 2022-06-22 一种通信方法和装置

Publications (1)

Publication Number Publication Date
WO2023246431A1 true WO2023246431A1 (zh) 2023-12-28

Family

ID=89272511

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/096809 WO2023246431A1 (zh) 2022-06-22 2023-05-29 一种通信方法和装置

Country Status (3)

Country Link
CN (1) CN117319972A (zh)
TW (1) TW202408259A (zh)
WO (1) WO2023246431A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102318436A (zh) * 2010-09-29 2012-01-11 华为技术有限公司 数据的传输方法、装置及系统
CN109996346A (zh) * 2017-12-29 2019-07-09 华为技术有限公司 会话建立方法、设备及系统
US20220060416A1 (en) * 2019-05-06 2022-02-24 Huawei Technologies Co., Ltd. Routing Rule Management Method and Communications Apparatus
WO2022110184A1 (zh) * 2020-11-30 2022-06-02 华为技术有限公司 一种通信方法、装置及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102318436A (zh) * 2010-09-29 2012-01-11 华为技术有限公司 数据的传输方法、装置及系统
CN109996346A (zh) * 2017-12-29 2019-07-09 华为技术有限公司 会话建立方法、设备及系统
US20220060416A1 (en) * 2019-05-06 2022-02-24 Huawei Technologies Co., Ltd. Routing Rule Management Method and Communications Apparatus
WO2022110184A1 (zh) * 2020-11-30 2022-06-02 华为技术有限公司 一种通信方法、装置及系统

Also Published As

Publication number Publication date
CN117319972A (zh) 2023-12-29
TW202408259A (zh) 2024-02-16

Similar Documents

Publication Publication Date Title
EP3557894B1 (en) Device triggering
US11770444B2 (en) Edge computing for internet of things security with blockchain authentication
WO2022227098A1 (zh) 一种信息传输方法、系统及装置
KR20200039529A (ko) 무선 통신 시스템에서 모바일 엣지 컴퓨팅의 이전을 지원하는 방법 및 장치
US11792884B2 (en) System and method for dynamic group data protection
WO2022176426A1 (ja) サーバ、要求エンティティ、及びこれらの方法
US20240040005A1 (en) Context transfer method and communication apparatus
WO2019136925A1 (zh) 一种数据传输方法及装置、计算机存储介质
EP3934174A1 (en) Terminal management and control method, apparatus and system
WO2021056448A1 (zh) 通信处理方法和通信处理装置
WO2023246431A1 (zh) 一种通信方法和装置
JP7428265B2 (ja) 通信端末及びその方法
EP4066518B1 (en) Method and apparatus for group management for group event monitoring
CN113613248B (zh) 认证事件处理方法及装置、系统
CN114830760A (zh) 无线通信系统中的寻呼方法和装置
WO2024109931A1 (zh) 一种通信方法和装置
WO2023071979A1 (zh) 一种寻呼方法及装置
WO2024066436A1 (zh) 一种通信方法及装置
WO2022104740A1 (zh) 一种非公共网络签约信息更新方法及装置
WO2024217183A1 (zh) 一种通信方法及装置
WO2024179300A1 (zh) 一种通信方法及装置
US20220322462A1 (en) Method and apparatus for configuring edge computing service information
US11950133B2 (en) Method and apparatus for performing header compression in a wireless system
WO2023241503A1 (zh) 隐私保护方法、装置、终端、节点及存储介质
WO2024021935A1 (zh) 一种通信方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23826080

Country of ref document: EP

Kind code of ref document: A1