WO2022252076A1 - 一种报文传输方法以及相关装置 - Google Patents

一种报文传输方法以及相关装置 Download PDF

Info

Publication number
WO2022252076A1
WO2022252076A1 PCT/CN2021/097471 CN2021097471W WO2022252076A1 WO 2022252076 A1 WO2022252076 A1 WO 2022252076A1 CN 2021097471 W CN2021097471 W CN 2021097471W WO 2022252076 A1 WO2022252076 A1 WO 2022252076A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
session
things
internet
passive
Prior art date
Application number
PCT/CN2021/097471
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 华为技术有限公司
Priority to EP21943452.9A priority Critical patent/EP4329420A1/en
Priority to PCT/CN2021/097471 priority patent/WO2022252076A1/zh
Priority to CN202180098430.XA priority patent/CN117337614A/zh
Publication of WO2022252076A1 publication Critical patent/WO2022252076A1/zh
Priority to US18/521,252 priority patent/US20240098145A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/564—Enhancement of application control based on intercepted application data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • 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
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/08—Upper layer protocols

Definitions

  • the present application relates to the technical field of communications, and in particular to a message transmission method and related devices.
  • Passive or semi-active IoT technology is a type of automatic identification technology.
  • the reader performs non-contact two-way data communication through radio frequency, and uses radio frequency to read and write electronic tags or radio frequency cards (Tag), so as to achieve the purpose of identifying targets and data exchange.
  • RFID radio frequency cards
  • Passive or semi-active IoT systems contain passive or semi-active IoT tags and passive or semi-active IoT readers (readers); optional, passive or semi-active IoT systems can also Including middleware (Filtering&Collection) and server. Passive or semi-active IoT readers and middleware use low level reader protocol (LLRP). The protocol between the middleware and the server is application level event (ALE).
  • LLRP low level reader protocol
  • ALE application level event
  • cellular networks can be used to support passive or semi-active IoT applications.
  • cellular networks need to incorporate passive or semi-active IoT technologies (or passive or semi-active IoT network architectures).
  • Embodiments of the present application provide a message transmission method and a related device, so that the cellular network can support the processing of application messages of the passive or semi-active Internet of Things.
  • a message transmission method including: an access network device receives a first message from an Internet of Things functional network element; the access network device obtains first information, and the first information indicates that the first message includes passive or a semi-active Internet of Things instruction; the access network device performs a passive or semi-active Internet of Things operation according to the first message.
  • the first information may be sent by the Internet of Things functional network element to the access network device, and the first information may also be obtained by the access network device from the Internet of Things functional network element, or the first information may be obtained by the access network device from Obtained from the context information, there is no limitation here.
  • the first message may include the first information, or the first message may be independent of the first information, which is not limited here.
  • the message in this embodiment of the present application may also be called a data packet, signaling, or instruction, etc., which is not limited here.
  • the access network device obtains (or the access network device obtains from the context information) first information from the Internet of Things functional network element, and the first information indicates that the first message includes a passive or semi-active Internet of Things instruction.
  • the access network device learns that the message from the Internet of Things functional network element is related to the passive or semi-active Internet of Things, and the access network device performs passive or semi-active Internet of Things operations according to the first message. It solves the problem of message transmission in the scenario where the passive or semi-active IoT system is integrated with the cellular network. It enables the cellular network to analyze the application message of the passive or semi-active Internet of Things and perform related operations according to the application message.
  • the first information includes one or more of the following: the message type of the first message, the container type in the first message, the first message
  • the tunnel identification information in the first information, or the first information is the information type of the first packet, the session type of the first session, or the session identifier of the first session, wherein the first session is used to transmit the first session A message, the session type of the first session is the passive or semi-active Internet of Things, and the session identifier of the first session indicates that the first session is related to the passive or semi-active Internet of Things.
  • the message type of the first message may be the message type field in the message header of the first message; the container type of the first message may be a newly added container type in the first message; the first message
  • the tunnel identification information refers to the tunnel identification information of the access network device RAN about the first session, that is, the endpoint identification of the N3 tunnel when the RAN establishes the first session, and the IoT function network element determines the session of the first session through the tunnel identification information Type; the information type of the first packet refers to the newly added information type field in the first packet indicating the first packet.
  • the embodiment of the present application provides multiple implementation solutions of the first information, which improves the implementation flexibility of the solutions.
  • the access network device uses the second protocol to process the first message according to the first information, and acquires passive or semi-active IoT instructions.
  • the second protocol is a low level reader protocol (low level reader protocol, LLRP).
  • the passive or semi-active IoT instructions include: event cycle specification (event cycle specification, ECSpecs) or command cycle specification (command cycle specification, CCSpecs), wherein the event cycle specification instruction or command cycle specification instruction includes the required The range of tags to be inventoried, or the range of tags that need to perform read or write operations.
  • the access network device obtains the response of the passive or semi-active Internet of Things command; the access network device uses the second protocol to process the passive or semi-active In response to the Internet of Things command, a third message is generated; the access network device sends the third message to the Internet of Things functional network element.
  • the RAN executes a passive or semi-active IoT operation according to the passive or semi-active IoT command included in the first intermediate data, and obtains a response to the passive or semi-active IoT command.
  • the passive or semi-active Internet of Things operations include, but are not limited to: tag read and write operations, tag inventory operations, and the like.
  • the response of the passive or semi-active Internet of Things command includes, but is not limited to: the read data of the tag, or the inventory operation result of the tag, and the like.
  • the RAN uses the second protocol to process the response to the passive or semi-active Internet of Things command to obtain the third message.
  • the RAN processes the response to the passive or semi-active Internet of Things command to obtain a message message including the response to the passive or semi-active Internet of Things command.
  • the RAN further encapsulates the message packet to obtain a third packet.
  • the third message includes a response to the passive or semi-active Internet of Things command.
  • the access network device notifies the Internet of Things functional network element that the third message is related to the passive or semi-active Internet of Things, and the Internet of Things functional network element obtains passive information based on the third message. Or a response to semi-active IoT commands. It solves the problem of message transmission in the scenario where the passive or semi-active IoT system is integrated with the cellular network.
  • the access network device sends the second information to the Internet of Things functional network element, and the second information indicates that the third message is related to the passive or semi-active Internet of Things related, or the third packet needs to be processed using the second protocol.
  • the third message includes information related to the passive or semi-active Internet of Things, or that the third message needs to be processed using the second protocol.
  • the second information may be sent by the access network device to the Internet of Things functional network element, and the second information may also be obtained by the Internet of Things functional network element from the access network device, which is not limited here.
  • the third message may include the second information, or the third message may be independent of the second information, which is not limited here.
  • the second information includes one or more of the following: the message type of the third message, the container type of the third message, the tunnel identification information of the third message, or the second information is the information of the third message type.
  • the access network device notifies the Internet of Things functional network element through the second information that the third message is related to the passive or semi-active Internet of Things, so that the Internet of Things functional network element can efficiently process the third message .
  • the embodiment of the present application provides multiple implementation solutions of the second information, which improves the implementation flexibility of the solutions.
  • the second information includes one or more of the following: the message type of the third message, the container type in the third message, the third message Tunnel identification information in the tunnel, the second information is the information type of the third message, or the information type of the third message, the session type of the first session, or the session identifier of the first session, wherein the first session A session is used to transmit the first message, the session type of the first session is the passive or semi-active Internet of Things, and the session identifier of the first session indicates that the first session is related to the passive or semi-active Source IoT related.
  • the message type of the third message may be the message type field in the message header of the third message; the container type of the third message may be a newly added container type in the third message; the third message
  • the tunnel identification information refers to the tunnel identification information of the RAN on the first session, that is, the endpoint identification of the N3 tunnel when the RAN establishes the first session, and the Internet of Things function network element determines the session type of the first session through the tunnel identification information; the third The information type of the message refers to the newly added information type field in the third message indicating the third message.
  • the embodiment of the present application provides multiple implementation solutions of the second information, which improves the implementation flexibility of the solutions.
  • the access network device receives the first message from the Internet of Things functional network element, including: the access network device sends a request message, and the request message is used to establish the first packet.
  • the request message is a protocol data unit (Protocol Data Unit, PDU) session establishment request message (PDU session establishment request) sent by the RAN to the AMF.
  • PDU session establishment request message is used to establish the first session.
  • the session type of the first session is the passive or semi-active Internet of Things, or the session identifier of the first session indicates that the first session is related to the passive or semi-active Internet of Things.
  • the PDU session establishment request message includes PDU session type information, and the PDU session type information indicates that the session type of the first session is passive or semi-active Internet of Things, or the PDU session type information indicates the first Sessions transmit passive or semi-active IoT-related data.
  • the RAN sends the session type of the first session to the AMF during the establishment of the PDU session.
  • the session type of the first session is also referred to as PDU session type information.
  • the AMF obtains the PDU session type information in various ways. For example, the RAN sends the PDU session type information to the AMF through a non-access stratum NAS message, or the RAN sends the PDU session type information to the AMF through an N2 message. Or, the AMF acquires the PDU session type information from the subscription data of the RAN. Alternatively, the AMF acquires the PDU session type information from the data stored by the AMF itself. There is no limitation here.
  • the first session can be used to transmit the first message sent by the network element of the Internet of Things function to the RAN, which improves the implementation flexibility of the solution.
  • the access network device sends the third packet to the Internet of Things functional network element through the first session.
  • the first session can also be used to transmit the third message sent by the RAN to the functional network element of the Internet of Things, which improves the implementation flexibility of the solution.
  • the first information further includes a session type of the first session, or a session identifier of the first session.
  • the access network device may determine, according to the session type of the first session, or the session identifier of the first session, that the first packet transmitted in the first session includes a passive or semi-active Internet of Things instruction.
  • the second information further includes a session type of the first session, or a session identifier of the first session.
  • the access network device may determine that the third packet transmitted in the first session is related to the passive or semi-active Internet of Things according to the session type of the first session, or the session identifier of the first session.
  • the Internet of Things functional network element includes: a user plane function UPF, an access and mobility management function AMF, a session management function SMF, a network warehouse function NRF, or a third A network element.
  • the embodiment of the present application proposes a message transmission method, including: the Internet of Things functional network element sends a first message to the access network device, the first message includes passive or semi-active Internet of Things instructions;
  • the networking function network element sends the first information to the access network device, and the first information indicates that the first message includes a passive or semi-active Internet of Things command, enabling the access network device to perform passive or semi-active Internet of Things operations.
  • the first information may be sent by the Internet of Things functional network element to the access network device, and the first information may also be obtained by the access network device from the Internet of Things functional network element, or the first information may be obtained by the access network device from Obtained from the context information, there is no limitation here.
  • the first message may include the first information, or the first message may be independent of the first information, which is not limited here.
  • the access network device receives the first message sent by the Internet of Things function network element. Secondly, the access network device acquires the first information. Specifically, the access network device obtains the first information from the first packet, that is, the first packet includes the first information; or, the access network device obtains the first information from the Internet of Things function network element or other network elements. Information, for example: the access network device obtains (or the access network device obtains from the context information) relevant information about the first session that transmits the first packet (including the session identifier of the first session or the second session type of a session), and the first information is related information of the first session.
  • the access network device learns that the message from the Internet of Things functional network element is related to the passive or semi-active Internet of Things, and the access network device performs passive or semi-active Internet of Things operations according to the first message. It solves the problem of message transmission in the scenario where the passive or semi-active IoT system is integrated with the cellular network. It enables the cellular network to analyze the application message of the passive or semi-active Internet of Things, and perform related operations according to the application message.
  • the Internet of Things functional network element includes: a user plane function UPF, an access and mobility management function AMF, a session management function SMF, a network storage function NRF, or a third A network element.
  • the Internet of Things functional network element receives the second message from the passive or semi-active Internet of Things server; the Internet of Things functional network element based on the second message, Generate a first message, the first message includes the passive or semi-active Internet of Things command included in the second message; the Internet of Things functional network element sends the first message to the access network device. Specifically, the Internet of Things functional network element determines that the second message is from the passive or semi-active Internet of Things server according to the message header of the second message. Alternatively, the Internet of Things functional network element transmits the relevant identification of the session of the second message, and determines whether the second message comes from the passive or semi-active Internet of Things server.
  • the Internet of Things functional network element After determining that the second message is from the passive or semi-active Internet of Things server, the Internet of Things functional network element determines that the second message includes a passive or semi-active Internet of Things instruction. Therefore, the Internet of Things functional network element generates the first message based on the second message, so as to ensure that the access network device obtains the passive or semi-active Internet of Things instruction.
  • the Internet of Things functional network element uses the first protocol to process the second message to generate the first intermediate data; the Internet of Things functional network element uses the second protocol to process the second message.
  • the intermediate data is used to generate a first packet.
  • the Internet of Things functional network element processes (or is called: parses) the second packet by using the first protocol, and the processed data is called first intermediate data.
  • the Internet of Things functional network element uses the second protocol to process the first intermediate data to generate the first message.
  • the first protocol is an Application Level Event (Application Level Event, ALE) protocol.
  • the second protocol is a Low Level Reader Protocol (Low Level Reader Protocol, LLRP).
  • the Internet of Things functional network element itself can process the second message and generate the first message, which improves the implementation flexibility of the solution.
  • the Internet of Things functional network element sends the second message to the first network element; the Internet of Things functional network element receives the second intermediate data sent by the first network element , the second intermediate data is the data obtained by the first network element processing the second message by using the first protocol and the second protocol; the Internet of Things function network element processes the second intermediate data to generate the first message.
  • the Internet of Things function network element can cooperate with other network elements (for example, the first network element) to process the second message and generate the first message, which improves the implementation flexibility of the solution.
  • the Internet of Things functional network element receives the third message from the access network device; the Internet of Things functional network element obtains the second information, and the second information indicates that the first The third message is related to the passive or semi-active Internet of Things, or the third message needs to be processed using the second protocol; the Internet of Things functional network element uses the second protocol to process the third message according to the second information, and generates the fourth message message; the third message and the fourth message include the response to the passive or semi-active Internet of Things command obtained by the access network device.
  • the third packet is a response to the first packet.
  • the Internet of Things functional network element determines that the third message needs to be processed using the second protocol according to the second information (such as the message type of the third message, or the message header of the third message) .
  • the Internet of Things functional network element determines the session identifier of the first session according to the identification information of the first session, or the session type of the first session, to determine the The third message transmitted includes the response to the passive or semi-active IoT command.
  • the Internet of Things functional network element determines that the third message needs to be processed by using the second protocol.
  • the second protocol is the LLRP protocol as an example.
  • the Internet of Things functional network element uses the LLRP protocol to process (also referred to as parsing) the third message, and obtain the response of the passive or semi-active Internet of Things command.
  • the Internet of Things functional network element uses the first protocol (for example, ALE protocol) to process the response of the passive or semi-active Internet of Things command, and generates a fourth message.
  • the Internet of Things functional network element may send the fourth packet to the passive or semi-active Internet of Things server.
  • the fourth packet carries a response including a passive or semi-active Internet of Things command.
  • the Internet of Things functional network element can efficiently identify the response carrying the passive or semi-active Internet of Things command in the third message, and process the third message using the second protocol to generate a fourth message.
  • the Internet of Things functional network element sends the fourth message to the passive or semi-active Internet of Things server, so as to improve the working efficiency of the passive or semi-active Internet of Things system.
  • the Internet of Things functional network element is a user plane function
  • the user plane function generates the first message based on the second message, including: the user plane function according to the first message A rule and/or a second rule generates a first message based on the second message; the first rule and/or the second rule are configured by the session management function SMF or the first rule and/or the second rule are preconfigured on the user plane Function.
  • the user plane function generates the first message based on the first rule and/or the second rule based on the second message, including: the user plane function determines the source of the second message according to the first rule; The second rule processes the second message from the passive or semi-active IoT server to generate the first message.
  • the first rule instructs the Internet of Things functional network element how to determine whether the received packet comes from a passive or semi-active Internet of Things server.
  • the second rule instructs the Internet of Things functional network element how to process the message from the passive or semi-active Internet of Things server. That is, it indicates the type of protocol that needs to be used by the Internet of Things functional network element to process the second message.
  • the second rule includes: a packet forwarding rule (Forwarding Action Rule, FAR), and the first rule includes: a flow matching rule (Packet Detection Rule, PDR).
  • the first rule and/or the second rule may be an enhanced N4 rule. This enhanced N4 rule is relevant to passive or semi-active IoT services.
  • the first rule may include: an enhanced FAR rule
  • the second rule may include: an enhanced PDR rule.
  • the user plane function can determine the source of the second message, process the second message and generate the first message according to the first rule and/or the second rule, which improves the solution scope of application.
  • the Internet of Things functional network element sends the first message to the access network device through the first session, and the session type of the first session is passive or semi-active.
  • the source Internet of Things, or, the session identification of the first session indicates that the first session is related to the passive or semi-active Internet of Things.
  • the first session can be used to transmit the first message sent by the network element of the Internet of Things function to the RAN, which improves the implementation flexibility of the solution.
  • the second information further includes a session type of the first session, or a session identifier of the first session.
  • the Internet of Things functional network element may determine according to the session type of the first session, or the session identifier of the first session, that the first packet transmitted in the first session includes a passive or semi-active Internet of Things instruction.
  • the Internet of Things functional network element sends a subscription request to the second network element, and the subscription request is used to obtain access network device information;
  • the access network device information includes the following One or more of the information: the permanent identification of the access network equipment, the information of the core network element serving the access network equipment, and the reader identification information of the access network equipment;
  • the second network element includes the following one or Multiple: access and mobility management function AMF, session management function SMF, unified data management function UDM or network storage function NRF.
  • the Internet of Things functional network element can obtain which RAN agent is established through the event reported by the second network element (referred to as agent) the control plane channel, and the SUPI information of the RAN agent.
  • agent the second network element
  • SUPI information of the RAN agent the event reported by the second network element (referred to as agent) the control plane channel, and the SUPI information of the RAN agent.
  • the subsequent passive or semi-active IoT server sends passive or semi-active IoT commands (or information, or data) to the IoT functional network element, so that the network element (or network function, such as NEF) responsible for forwarding the message , AMF, UDM or SMF) to know the destination of the message, that is, to which RAN the message needs to be sent.
  • the network element or network function, such as NEF
  • the first information includes one or more of the following: the message type of the first message, the container type in the first message, the first message The tunnel identification information in , or the first information is the information type of the first packet.
  • the message type of the first message may be the message type field in the message header of the first message; the container type of the first message may be a newly added container type in the first message; the first message
  • the tunnel identification information refers to the tunnel identification information of the RAN on the first session, that is, the endpoint identification of the N3 tunnel when the RAN establishes the first session, and the Internet of Things functional network element determines the session type of the first session through the tunnel identification information; the first The information type of the message refers to the newly added information type field in the first message indicating the first message.
  • the second information includes one or more of the following: the message type of the third message, the container type in the third message, the third message Tunnel identification information in , or the information type of the third packet.
  • the message type of the third message may be the message type field in the message header of the third message;
  • the container type of the third message may be a newly added container type in the third message;
  • the tunnel identification information refers to the tunnel identification information of the RAN on the first session, that is, the endpoint identification of the N3 tunnel when the RAN establishes the first session, and the Internet of Things function network element determines the session type of the first session through the tunnel identification information;
  • the third The information type of the message refers to the newly added information type field in the third message indicating the third message.
  • the embodiment of the present application proposes a communication device, including:
  • a transceiver module configured to receive the first message from the functional network element of the Internet of Things
  • the transceiver module is also used to obtain first information, the first information indicates that the first message includes passive or semi-active Internet of Things instructions;
  • a processing module configured to perform passive or semi-active Internet of Things operations according to the first message.
  • the communication device is a network device
  • the processing module may be a processor
  • the transceiver module may be a transceiver.
  • the network device is a chip, a chip system or a circuit configured in the network device.
  • the processing module may be a processor, a processing circuit, or a logic circuit.
  • the transceiver module may be an input and/or output interface, interface circuit, output circuit, input circuit, pin or related circuit on the chip, chip system or circuit.
  • the above “receiving” can also be understood as "input”.
  • the first information includes one or more of the following: the message type of the first packet, the container type of the first packet, the tunnel identification information of the first packet, or the first information is Information type of the first packet.
  • the processing module is further configured to process the first message by using the second protocol according to the first information, and acquire the passive or semi-active Internet of Things instruction.
  • the transceiver module is also used to obtain the response of passive or semi-active Internet of Things commands
  • the processing module is also used to process the response of the passive or semi-active Internet of Things command by using the second protocol, and generate a third message;
  • the transceiver module is also used to send the third message to the functional network element of the Internet of Things.
  • the transceiver module is further configured to send second information to the Internet of Things functional network element, and the second information indicates that the third message is related to the passive or semi-active Internet of Things, or the third message Need to use the second protocol for processing.
  • the second information includes one or more of the following: the message type of the third packet, the container type of the third packet, the tunnel identification information of the third packet, or the second information is The information type of the third packet.
  • the transceiver module is further configured to send a request message, and the request message is used to establish the first session;
  • the session type of the first session is the passive or semi-active Internet of Things, or, the session identifier of the first session indicates that the first session is related to the passive or semi-active Internet of Things;
  • the transceiver module is further configured to receive the first message sent by the Internet of Things functional network element through the first session.
  • the transceiver module is further configured to send a third message to the Internet of Things functional network element through the first session.
  • the first information further includes a session type of the first session, or a session identifier of the first session.
  • the second information further includes a session type of the first session, or a session identifier of the first session.
  • the Internet of Things functional network element includes: a user plane function UPF, an access and mobility management function AMF, a session management function SMF, a network warehouse function NRF, or a first network element.
  • the embodiment of the present application proposes a communication device, including:
  • a transceiver module configured to send a first message to the access network device, where the first message includes a passive or semi-active Internet of Things instruction;
  • the transceiver module is also used to send the first information to the access network device, the first information indicates that the first message includes a passive or semi-active Internet of Things command, enabling the access network device to perform passive or semi-active Internet of Things operate.
  • the transceiver module is further configured to receive the second message from the passive or semi-active IoT server;
  • a processing module configured to generate a first message based on the second message, where the first message includes the passive or semi-active Internet of Things instruction included in the second message;
  • the transceiver module is further configured to send the first packet to the access network device.
  • the communication device is a network device
  • the processing module may be a processor
  • the transceiver module may be a transceiver.
  • the network device is a chip, a chip system or a circuit configured in the network device.
  • the processing module may be a processor, a processing circuit, or a logic circuit.
  • the transceiver module may be an input and/or output interface, interface circuit, output circuit, input circuit, pin or related circuit on the chip, chip system or circuit.
  • the above “receiving” can also be understood as "input”.
  • the processing module is specifically configured to process the second message by using the first protocol to generate the first intermediate data
  • the processing module is specifically configured to use the second protocol to process the first intermediate data and generate the first message.
  • the transceiver module is specifically configured to send the second message to the first network element
  • the transceiver module is specifically used to receive the second intermediate data sent by the first network element, and the second intermediate data is the data obtained by the first network element processing the second message by using the first protocol and the second protocol;
  • the processing module is specifically configured to process the second intermediate data and generate the first message.
  • the transceiver module is further configured to receive a third message from the access network device;
  • the transceiver module is also used to obtain second information, the second information indicates that the third message is related to the passive or semi-active Internet of Things, or the third message needs to be processed using the second protocol;
  • the processing module is further configured to determine, according to the second information, to use the second protocol to process the third message, and generate a fourth message;
  • the third message and the fourth message include responses to passive or semi-active Internet of Things commands acquired by the access network device.
  • the processing module is further configured to generate the first message based on the first rule and/or the second rule based on the second message;
  • the first rule and/or the second rule are configured by the session management function SMF, or the first rule and/or the second rule are preconfigured in the user plane function.
  • the second rule includes: a packet forwarding rule
  • the first rule includes: a flow matching rule
  • the transceiver module is further configured to send the first message to the access network device through the first session, where the session type of the first session is passive or semi-active Internet of Things;
  • the session identifier of the first session indicates that the first session is related to the passive or semi-active Internet of Things.
  • the second information further includes a session type of the first session, or a session identifier of the first session.
  • the transceiver module is further configured to send a subscription request to the second network element, where the subscription request is used to obtain access network device information;
  • the access network device information includes one or more of the following information: the permanent identification of the access network device, the information of the core network element serving the access network device, and the reader identification information of the access network device;
  • the second network element includes one or more of the following: access and mobility management function AMF, session management function SMF, unified data management function UDM or network storage function NRF.
  • the Internet of Things functional network element includes: a user plane function UPF, an access and mobility management function AMF, a session management function SMF, a network warehouse function NRF, or a first network element.
  • the first information includes one or more of the following: the message type of the first packet, the container type of the first packet, the tunnel identification information of the first packet, or type of information.
  • the second information includes one or more of the following: the message type of the third packet, the container type of the third packet, the tunnel identification information of the third packet, or type of information.
  • a communication device for implementing the above various methods.
  • the communication device may be the communication device in the first aspect or any possible implementation of the first aspect, or the communication device in the second aspect or any possible implementation of the second aspect, or a device contained in the above communication device , such as a system chip.
  • the communication device provided in the fifth aspect includes corresponding modules, units, or means for implementing the above method, and the modules, units, or means may be implemented by hardware, software, or by executing corresponding software on hardware.
  • the hardware or software includes one or more modules or units corresponding to the above functions.
  • a communication device including: a processor and a memory; the memory is used to store computer instructions, and when the processor executes the instructions, the communication device executes the method of any aspect above.
  • the communication device may be the communication device in the above-mentioned first aspect or any possible implementation of the first aspect, or the second aspect or any possible implementation of the second aspect, or a device including the above-mentioned communication device , or a device included in the communication device, such as a system chip.
  • a communication device including: a processor; the processor is configured to be coupled with a memory, and after reading instructions in the memory, execute the method according to any one of the above-mentioned aspects according to the instructions, and the memory and the communication device communicate with each other independent.
  • the communication device may be the communication device in the above-mentioned first aspect or any possible implementation of the first aspect, or the second aspect or any possible implementation of the second aspect, or a device including the above-mentioned communication device , or a device included in the communication device, such as a system chip.
  • a computer-readable storage medium is provided. Instructions are stored in the computer-readable storage medium. When the instructions are run on a communication device, the communication device can execute the method in any aspect above.
  • the communication device may be the communication device in the above-mentioned first aspect or any possible implementation of the first aspect, or the second aspect or any possible implementation of the second aspect, or a device including the above-mentioned communication device , or a device included in the communication device, such as a system chip.
  • a computer program product including instructions is provided, and when the instructions are run on the communication device, the communication device can execute the method in any aspect above.
  • the communication device may be the communication device in the above-mentioned first aspect or any possible implementation of the first aspect, or the second aspect or any possible implementation of the second aspect, or a device including the above-mentioned communication device , or a device included in the communication device, such as a system chip.
  • a communication device for example, the communication device may be a chip or a chip system
  • the communication device includes a processor configured to implement the functions involved in any one of the above aspects.
  • the communication device further includes a memory, and the memory is used for storing necessary program instructions and data.
  • the communication device is a system-on-a-chip, it may consist of chips, or may include chips and other discrete devices.
  • a chip in an eleventh aspect, includes a processor and a communication interface, the communication interface is used to communicate with modules other than the shown chip, the processor is used to run computer programs or instructions, so that the chip installed
  • the device can execute the method of any one of the above aspects.
  • the technical effect brought by any one of the design methods in the third aspect to the eleventh aspect can refer to the technical effects brought by the different design methods in the first aspect or the second aspect above, and will not be repeated here.
  • a communication system in a twelfth aspect, includes the communication device of the above aspect.
  • Figure 1a is a schematic diagram of a passive or semi-active Internet of Things system involved in an embodiment of the present application
  • FIG. 1b is a schematic diagram of the RFID system in the embodiment of the present application.
  • FIG. 1c is a schematic diagram of a network architecture of a communication system
  • FIG. 2 is a schematic diagram of the hardware structure of the communication device in the embodiment of the present application.
  • Fig. 3 is a schematic flow chart of label inventory in the embodiment of the present application.
  • FIG. 4 is a schematic flow chart of tag reading and writing in the embodiment of the present application.
  • FIG. 5 is a schematic diagram of a passive or semi-active Internet of Things architecture in an embodiment of the present application.
  • FIG. 6 is a schematic diagram of another passive or semi-active Internet of Things architecture in the embodiment of the present application.
  • FIGS. 7a-7b are schematic diagrams of another passive or semi-active Internet of Things architecture in the embodiment of the present application.
  • FIG. 8 is a schematic flow diagram of establishing a control plane channel by the RAN agent in the embodiment of the present application.
  • FIG. 9a is a schematic flow diagram of the process of establishing a session by the RAN agent in the embodiment of the present application.
  • FIG. 9b is a schematic flowchart of an embodiment of a message transmission method proposed in the embodiment of the present application.
  • FIG. 10a is a schematic flowchart of an embodiment of a message transmission method proposed in the embodiment of the present application.
  • FIG. 10b is a schematic flowchart of a message transmission method in an application scenario proposed by an embodiment of the present application.
  • FIG. 10c is a schematic flowchart of a message transmission method in an application scenario proposed by an embodiment of the present application.
  • FIG. 11 is a schematic flowchart of an embodiment of a message transmission method proposed in the embodiment of the present application.
  • FIG. 12 is a schematic flowchart of another embodiment of a message transmission method proposed in the embodiment of the present application.
  • FIG. 13 is a schematic flowchart of another embodiment of a message transmission method proposed in the embodiment of the present application.
  • FIG. 14 is a schematic diagram of an embodiment of a communication device in the embodiment of the present application.
  • Fig. 15 is a schematic diagram of an embodiment of a communication device in an embodiment of the present application.
  • At least one item (piece) of a, b, or c can represent: a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, c can be single or multiple .
  • WCDMA Wideband Code Division Multiple Access
  • general packet radio service general packet radio service, GPRS
  • long term evolution Long Term Evolution
  • LTE long term evolution
  • LTE frequency division duplex frequency division duplex, FDD
  • LTE time division duplex time division duplex
  • TDD time division duplex
  • UMTS universal mobile telecommunications system
  • WiMAX global interconnected microwave access Access
  • the communication network can be a public land mobile network (PLMN) network, which is a network established and operated by the government or an operator approved by the government for the purpose of providing land mobile communication services to the public, mainly mobile network operators
  • PLMN public land mobile network
  • MNO mobile network operator
  • a mobile network operator (MNO) provides users with a public network with mobile broadband access services; it can also be an enterprise network, that is, a network built by the enterprise, controlled by the enterprise, or managed by the enterprise.
  • the communication network described in the embodiment of the present application may be a network conforming to the standard requirements of the 3rd generation partnership project (3GPP), referred to as 3GPP network, including but not limited to the fifth generation mobile communication (5th-generation , 5G) network (referred to as 5G network), fourth-generation mobile communication (4th-generation, 4G) network (referred to as 4G network) or third-generation mobile communication technology (3rd-generation, 3G) network (referred to as 3G network). 6G network is also included.
  • 3GPP 3rd generation partnership project
  • Fig. 1a is a schematic diagram of a passive or semi-active Internet of Things system involved in the embodiment of the present application.
  • the passive or semi-active Internet of Things system in the embodiment of the present application can be regarded as a radio frequency identification system, or a radio frequency identification technology (Radio Frequency Identification, RFID) system.
  • RFID Radio Frequency Identification
  • the RFID system in the embodiment of the present application is only an example of the passive or semi-active Internet of Things system in the embodiment of the present application, and the passive or semi-active Internet of Things system in the embodiment of the present application is not Not limited to RFID systems.
  • the name of “passive or semi-active Internet of Things” may also change.
  • the "passive or semi-active Internet of Things” involved in the embodiment of this application may also be the above-mentioned Internet of Things in future communication systems.
  • "Passive or semi-active IoT” systems (or communication technologies) that structure or function.
  • RFID is a kind of automatic identification technology.
  • the reader performs non-contact two-way data communication through radio frequency, and uses radio frequency to read and write electronic tags or radio frequency cards (Tag), so as to achieve the purpose of identifying targets and data exchange. It works in two ways, one is when the RFID tag enters the effective identification range of the reader, it receives the radio frequency signal sent by the reader, and sends out the information stored in the chip by virtue of the energy obtained by the induced current (corresponding to Passive Tag); the other is that the RFID tag actively sends a signal of a certain frequency (corresponding to the active Tag), and after the reader receives and decodes the information, the relevant data is processed by the RFID information service system or the back-end application system .
  • This technology is widely used in various industries. The following briefly introduces two application scenarios.
  • Items are embedded with RFID tags.
  • the relevant information of the goods is automatically collected by the reader, and the management personnel can quickly query the information of the goods in the system, reducing the risk of discarding or being stolen, which can improve the delivery speed of goods, improve the accuracy rate, and realize anti-counterfeiting and Prevent cross-selling.
  • FIG. 1b is a schematic diagram of the RFID system in the embodiment of the present application.
  • RFID system includes: tags, readers, middleware and servers.
  • the tag (Gen 2RFID Tag) and the reader (RFID Reader) use the air interface protocol (for example: Gen 2Air Interface protocol) to communicate; the reader and the middleware (Filtering&Collection) use the low-level reader protocol ( Low Level Reader Protocol, LLRP).
  • the protocol between the middleware and the server is Application Level Event (ALE).
  • ALE Application Level Event
  • the Internet of Things functional network element in the cellular network implements some or all functions of the middleware in the passive or semi-active Internet of Things.
  • the IoT functional network element can be a control plane network element or a user plane network element; the IoT functional network element can be a newly added network element, or it can be integrated into other defined network elements.
  • the network element having the Internet of Things function is referred to as the first network element.
  • the Internet of Things functional network element in the embodiment of the present application may also be referred to as an application layer event proxy function (ALE proxy).
  • ALE proxy application layer event proxy function
  • FIG. 1c is a schematic diagram of a network architecture of a communication system, which may include: a terminal device (also referred to as a user equipment part), a communication network part and a data network 104 (data network, DN) part.
  • a terminal device also referred to as a user equipment part
  • a communication network part and a data network 104 (data network, DN) part.
  • DN data network
  • the terminal equipment part includes a terminal equipment 101, and the terminal equipment 101 may also be called user equipment (user equipment, UE).
  • the terminal device 101 involved in the embodiment of the present application can communicate with an access network device in a (wireless) access network 102 ((radio) access network, (R)AN) or multiple core networks (core network, CN) for communication.
  • Terminal device 101 may also be called an access terminal, terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, wireless network device, user agent, or user device, among others.
  • the terminal device 101 can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; it can also be deployed on water (such as ships, etc.); it can also be deployed in the air (such as aircraft, balloons and satellites, etc.).
  • the terminal device 101 can be a cellular phone (cellular phone), a cordless phone, a session initiation protocol (session initiation protocol, SIP) phone, a smart phone (smart phone), a mobile phone (mobile phone), a wireless local loop (wireless local loop, WLL ) station, a personal digital assistant (PDA), which can be a handheld device with wireless communication capabilities, a computing device or other device connected to a wireless modem, an in-vehicle device, a wearable device, a drone device or the Internet of Things, Terminals in the Internet of Vehicles, terminals of any form in the fifth generation (fifth generation, 5G) network and future networks, relay user equipment or future evolution of public land mobile network (PLMN) terminal, etc., where the relay user equipment may
  • the terminal device 101 may be a virtual reality (virtual reality, VR) terminal, an augmented reality (augmented reality, AR) terminal, a wireless terminal in industrial control (industrial control), a wireless terminal in unmanned (self driving), a remote Wireless terminals in remote medical, wireless terminals in smart grid, wireless terminals in transportation safety, wireless terminals in smart city, smart home wireless terminals, etc.
  • VR virtual reality
  • AR augmented reality
  • the embodiment of the present application does not limit this.
  • the communication network may include unified data management 108 (unified data management, UDM), access and mobility management function 105 (access and mobility management function, AMF), session management function 106 (session management function, SMF), policy control network element 107 (policy control function, PCF), user plane function 103 (user plane function, UPF) and (R)AN102, etc.
  • unified data management 108 unified data management, UDM
  • access and mobility management function 105 access and mobility management function, AMF
  • session management function 106 session management function, SMF
  • policy control network element 107 policy control function, PCF
  • user plane function 103 user plane function, UPF
  • (R)AN102 etc.
  • core network core network
  • CN core network
  • the (R)AN is taken as an example for description.
  • the data network DN104 may also be called a protocol data network (protocol data network, PDN), which may be a data network of an operator or an enterprise, or a third-party data network.
  • the communication network can be connected to multiple data networks DN104, and various services can be deployed on the data network DN104, which can provide data and/or voice services for terminal equipment.
  • the data network DN104 can be a private network of a smart factory, and the sensors installed in the workshop of the smart factory can be terminal devices.
  • the control server of the sensors is deployed in the data network DN104, and the control server can provide services for the sensors.
  • the sensor can communicate with the control server, obtain instructions from the control server, and transmit the collected sensor data to the control server based on the instructions.
  • the data network DN104 may be an internal office network of a certain company, and the mobile phones or computers of the employees of the company may be terminal devices, and the mobile phones or computers of the employees may access information and data resources on the internal office network of the company.
  • the terminal device can establish a connection with the communication network through an interface provided by the communication network (such as N1, etc.), and use services such as data and/or voice provided by the communication network.
  • the terminal device can also access the data network DN104 through the communication network, and use the operator services deployed on the data network DN104, and/or services provided by a third party.
  • the above-mentioned third party may be a service provider other than the communication network and the terminal device, and may provide other data and/or voice services for the terminal device.
  • the specific form of expression of the above-mentioned third party can be determined based on actual application scenarios, and is not limited here.
  • (R)AN102 is a device that provides wireless communication functions for terminal devices. To access the communication network, the terminal equipment first passes through the (R)AN102, and then can be connected to the service node of the communication network through the (R)AN102.
  • the access network device 102 (RAN device) in the embodiment of the present application, (R)AN includes but is not limited to: the next generation base station node (next generation node base station, gNB) in the 5G system, long term evolution (long term evolution, LTE) in evolved node B (evolved node B, eNB), radio network controller (radio network controller, RNC), node B (node B, NB), base station controller (base station controller, BSC), base transceiver station Station (base transceiver station, BTS), home base station (for example, home evolved nodeB, or home node B, HNB), base band unit (base band unit, BBU), transmission point (transmitting and receiving point, TRP), transmission point ( transmitting point, TP),
  • access network devices In systems using different wireless access technologies, the names of devices that function as access network devices may be different.
  • access network equipment RAN102 or AN102 for short.
  • the access network device integrates some or all functions of the reader in the passive or semi-active Internet of Things.
  • the access and mobility management function AMF105 also called AMF network element, AMF network function or AMF network function entity
  • AMF105 is a control plane network function provided by the communication network, responsible for the access control and mobility of tags accessing the communication network Management, for example, includes mobility status management, assigning user temporary identities, authenticating and authorizing users, and other functions.
  • the session management function SMF106 (also referred to as SMF network element, SMF network function or SMF network function entity) is a control plane network function provided by the communication network, and is responsible for managing label protocol data unit (protocol data unit, PDU) sessions.
  • the PDU session is a channel for transmitting PDUs, and the label needs to transmit PDUs with the data network DN104 through the PDU session.
  • the PDU session is established, maintained and deleted by the SMF106 network function.
  • SMF106 network functions include session management (such as session establishment, modification and release, including tunnel maintenance between user plane functions UPF103 and (R)AN102), selection and control of UPF103 network functions, service and session continuity (service and session continuity) , SSC) mode selection, roaming and other session-related functions.
  • the user plane function UPF103 (also called UPF network element, UPF network function or UPF network function entity) is a gateway provided by the operator, and is a gateway for communication between the communication network and the data network DN104.
  • UPF103 network functions include data packet routing and transmission, data packet detection, service usage reporting, quality of service (QoS) processing, legal interception, uplink data packet detection, downlink data packet storage and other user-plane-related functions.
  • QoS quality of service
  • the unified data management network element UDM108 (also called UDM network element, UDM network function or UDM network function entity) is a control plane function provided by an operator, and is responsible for storing the permanent identity (subscriber permanent identifier, SUPI), the subscriber's public subscription identifier (generic public subscription identifier, GPSI), credential (credential) and other information. Among them, SUPI will be encrypted first during transmission, and the encrypted SUPI is called a hidden user subscription identifier (subscription concealed identifier, SUCI). The information stored by UDM 108 can be used for authentication and authorization of tags accessing the communication network.
  • the subscribers of the above-mentioned communication network may specifically be users who use services provided by the communication network, for example, users who use a mobile phone chip card of operator A.
  • the credential of the above-mentioned contracted user may be: a long-term key stored in the mobile phone chip card or a small file stored in encrypted information related to the mobile phone chip card, for authentication and/or authorization.
  • permanent identifiers, credentials, security contexts, authentication data (cookies), and information related to token equivalent verification/authentication and authorization are not distinguished and limited in this embodiment of the application for the convenience of description.
  • PCF Policy control entity
  • the PCF 107 can interact with the AF to obtain Quality of Service (Qos) parameters, or provide QoS parameters to the AF, thereby realizing a function that can affect application data transmission.
  • Qos Quality of Service
  • the application function AF interacts with the 3rd Generation Partnership Project (3rd Generation Partnership Project, 3GPP) core network to provide application layer services.
  • the application function AF may be located in a data network (data network, DN). For example: provide data routing on the application layer and provide access to the network capability.
  • AF can interact with PCF107.
  • the location of AF can be inside the 5G core network or outside the 5G core network. If the AF is inside the 5G core network, it can directly interact with the PCF107. If the AF is outside the 5G core network, the Network Exposure Function (NEF) acts as an intermediate node to forward the interaction content between the AF and the PCF107. For example, forwarding through NEF.
  • NEF Network Exposure Function
  • the authentication server function (authentication server function, AUSF) (also called AUSF network element, AUSF network function or AUSF network function entity) is a control plane function provided by the operator, usually used for primary authentication, that is, label 101 (subscription user) and the authentication between the communication network.
  • the AUSF may authenticate and/or authorize the subscriber through the authentication information and/or authorization information stored in the UDM 108, or generate the authentication and/or authorization information of the subscriber through the UDM 108.
  • AUSF can feed back authentication information and/or authorization information to the subscriber.
  • the AUSF can also be co-located with the UDM.
  • network elements in the core network can be co-located.
  • the access and mobility management function can be co-located with the session management function; the session management function can be co-located with the user plane function.
  • the interaction between the two network elements provided by the embodiment of the present application becomes an internal operation of the co-located network element or can be omitted.
  • the tag can communicate with the data network (Date network, DN) to communicate with passive or semi-active IoT servers.
  • the (R)AN also has some functions of the terminal equipment, that is, it requests the core network to establish the control plane channel and the user plane channel.
  • the tags in this embodiment of the application may specifically be electronic price tags for supermarkets, medical bracelets for mothers and babies, asset tags for smart parks, etc.
  • the access and mobility management network function is taken as an example for description. It can also be other network functions having the above-mentioned AMF network function in the future communication system.
  • the access and mobility management network function 105 in this application may also be a mobility management entity (mobility management entity, MME) in LTE and the like.
  • MME mobility management entity
  • the AMF network function is referred to as AMF for short, that is, the AMF described later in the embodiments of the present application can be replaced by the access and mobility management network function.
  • the session management function is SMF106 as an example for illustration. It can also be other network functions having the above-mentioned SMF network function in the future communication system. Further, the SMF network function is referred to as SMF for short, that is, the SMF described later in the embodiments of the present application can be replaced with a session management function.
  • the unified data management UDM108 is taken as an example for description. It can also be other network functions having the above-mentioned UDM network functions in the future communication system. Further, the UDM network function is referred to as UDM for short, that is, the UDM described later in the embodiments of the present application can be replaced with unified data management.
  • the user plane function UPF103 in the embodiment of the present application may also be other network functions having the above-mentioned UPF network function in the future communication system. There is no limitation here.
  • a message transmission method provided by this application can be applied to various communication systems, for example, it can be Internet of Things (Internet of Things, IoT), Narrow Band Internet of Things (NB-IoT), Long Term Evolution (long term evolution, LTE), it can also be the fifth generation (5G) communication system, it can also be a hybrid architecture of LTE and 5G, it can also be a 5G new radio (new radio, NR) system, and new technologies emerging in future communication development. communication system, etc.
  • the 5G communication system of the present application may include at least one of a non-standalone (NSA) 5G communication system and a standalone (standalone, SA) 5G communication system.
  • NSA non-standalone
  • SA standalone
  • the communication system may also be a public land mobile network (public land mobile network, PLMN) network, a device-to-device (device-to-device, D2D) network, a machine-to-machine (machine to machine, M2M) network or other networks.
  • PLMN public land mobile network
  • D2D device-to-device
  • M2M machine to machine
  • the "message” involved in the embodiment of the present application may also be replaced with "data packet”, “data”, “instruction” or “signaling”, etc., which is not limited here.
  • the embodiments of the present application may also be applicable to other future-oriented communication technologies, such as 6G and the like.
  • the network architecture and business scenarios described in this application are to illustrate the technical solution of this application more clearly, and do not constitute a limitation to the technical solution provided by this application.
  • Those of ordinary skill in the art know that with the evolution of network architecture and new business scenarios The various network functions involved in this application may change, and the technical solution provided by this application is also applicable to similar technical problems.
  • FIG. 2 is a schematic diagram of a hardware structure of a communication device in an embodiment of the present application.
  • the communication device may be a possible implementation manner of the access network device or the Internet of Things functional network element in the embodiment of the present application. It should be noted that the Internet of Things function network element proposed in the embodiment of the present application may also be co-located with other core network elements, such as a UPF, which is not limited here.
  • the communication device includes at least a processor 204 and a memory 203 .
  • the memory 203 is further used to store instructions 2031 and data 2032 .
  • the communication device includes an I/O (Input/Output, Input/Output) interface 210 and a bus 212 .
  • I/O Input/Output, Input/Output
  • the communication device may further include a transceiver 202 and an antenna 206 .
  • the transceiver 202 further includes a transmitter 2021 and a receiver 2022 .
  • the processor 204 , the transceiver 202 , the memory 203 and the I/O interface 210 are communicatively connected to each other through the bus 212 , and the antenna 206 is connected to the transceiver 202 .
  • the processor 204 can be a general processor, such as but not limited to, a central processing unit (central processing unit, CPU), and can also be a special purpose processor, such as but not limited to, a digital signal processor (digital signal processor, DSP), application application specific integrated circuit (asic) and field programmable gate array (field programmable gate array, FPGA), etc.
  • the processor 204 may also be a neural network processing unit (neural processing unit, NPU).
  • the processor 204 may also be a combination of multiple processors.
  • the processor 204 may be used to execute the relevant steps of the packet transmission method in the subsequent method embodiments.
  • the processor 204 may be a processor specially designed to perform the above steps and/or operations, or may be a processor that performs the above steps and/or operations by reading and executing the instructions 2031 stored in the memory 203.
  • the processor 204 The data 2032 may be needed during the execution of the above steps and/or operations.
  • the transceiver 202 includes a transmitter 2021 and a receiver 2022.
  • the transmitter 2021 is used to send signals through the antenna 206.
  • the receiver 2022 is used for receiving signals through at least one antenna among the antennas 206 .
  • the transmitter 2021 can be used to implement at least one of the antennas 206, for example, a message transmission method applied to network equipment in the subsequent method embodiments , the operations performed by the receiving module or sending module in the network device.
  • the transceiver 202 is used to support the communication device to perform the aforementioned receiving function and sending function.
  • a processor having a processing function is considered to be the processor 204 .
  • the receiver 2022 may also be called an input port, a receiving circuit, etc., and the transmitter 2021 may be called a transmitter or a transmitting circuit, etc.
  • the processor 204 can be used to execute the instructions stored in the memory 203 to control the transceiver 202 to receive messages and/or send messages, so as to complete the functions of the communication device in the method embodiments of the present application.
  • the function of the transceiver 202 may be considered to be realized by a transceiver circuit or a dedicated chip for transceiver.
  • receiving a message by the transceiver 202 may be understood as an input message by the transceiver 202
  • sending a message by the transceiver 202 may be understood as an output message by the transceiver 202.
  • Memory 203 can be various types of storage media, such as random access memory (random access memory, RAM), read only memory (read only memory, ROM), non-volatile RAM (non-volatile ram, NVRAM), can Programmable ROM (programmable rom, PROM), erasable PROM (erasable PROM, EPROM), electrically erasable PROM (electrically erasable PROM, EEPROM), flash memory, optical memory and registers, etc.
  • the memory 203 is specifically used to store instructions 2031 and data 2032.
  • the processor 204 can read and execute the instructions 2031 stored in the memory 203 to perform the steps and/or operations described in the method embodiments of the present application.
  • the data 2032 may be required during operations and/or steps in the method embodiments.
  • the label inventory process is used to take stock of existing labels.
  • Each label has its identifying information.
  • the identification information may be an electronic product code (electronic product code, EPC).
  • EPC electronic product code
  • the tag will send the EPC code to the reader, so that the reader can know which tags are within its coverage. This information will eventually be reported by the reader to the middleware and server. Please refer to FIG. 3 .
  • FIG. 3 is a schematic flowchart of label inventory in the embodiment of the present application.
  • the reader sends a selection command to the tag.
  • the reader/writer receives an inventory command from the functional network element of the Internet of Things.
  • the inventory command can be sent to the Internet of Things functional network element by the passive or semi-active Internet of Things server, and then issued to the reader by the Internet of Things functional network element.
  • the reader/writer After receiving the inventory command, the reader/writer generates a select command.
  • the command includes the label range, for example: EPC code within a specific range.
  • the tag After the tag listens to the selection command, it judges whether it belongs to the tag range in the selection command. If it does, the tag listens to the Query command in the subsequent process and feeds back information; if it does not belong, the tag is in the subsequent process. No action is performed.
  • the reader sends an inquiry command to the tag.
  • step A2 the reader/writer continues to send the inquiry command.
  • the tag sends a random number to the reader.
  • step A3 when the tag confirms that it belongs to the range of tags in the selection command, the tag sends a random number, such as RN16, to the reader through competition.
  • the reader sends a confirmation command to the tag.
  • step A4 after the reader/writer receives the random number from the tag, the reader/writer sends an acknowledgment (ACK) command, and the acknowledgment command includes the random number (RN16) received in step A3.
  • ACK acknowledgment
  • R16 random number
  • the tag sends the EPC code to the reader.
  • step A5 after the tag receives the confirmation command sent by the reader, the tag verifies the random number in the confirmation command. When the verification is successful, the tag feeds back its own EPC code to the reader to complete the inventory process.
  • Tag read and write process that is, to write or read tags. If it is a write operation, the data will be written into the storage area of the tag; if it is a read operation, the data in the tag storage area will be read.
  • the reader In the process of reading and writing, the reader will set the label range in the Select command to the label range to be read and written (for example, if the range in the Select command is a certain EPC code, it will tags for read and write operations). Please refer to FIG. 4 .
  • FIG. 4 is a schematic flow chart of tag reading and writing in the embodiment of the present application.
  • the reader sends a selection command to the tag.
  • the reader sends an inquiry command to the tag.
  • the tag sends a random number to the reader.
  • the reader/writer sends a confirmation command to the tag.
  • the tag sends the EPC code to the reader.
  • Steps B1-B5 are consistent with the aforementioned steps A1-A5, and will not be repeated here.
  • the reader/writer sends a random number request (Req_RN) command to the tag.
  • step B6 the reader sends a Req_RN command to the tag, and the Req_RN command includes the random number RN16 received in step B3.
  • the tag sends a handle to the reader.
  • step B7 after the tag verifies that the random number received in step B6 is correct, the tag sends a handle to the reader. In the subsequent read and write processes, the handle needs to be included.
  • the reader/writer sends a read or write command to the tag.
  • step B8 the reader-writer sends a read command or a write command to the tag, and the handle needs to be included in the read command or write command.
  • the write command it is also necessary to include the data written into the tag memory area.
  • the tag sends data to the reader.
  • step B8 is a read command, then execute step B9.
  • step B9 the tag sends the data in its storage area to the reader-writer, including the handle.
  • Passive or semi-active Internet of Things (passive IoT) architecture.
  • the passive or semi-active IoT architecture involved in the embodiments of the present application includes various implementation solutions, which will be described below with reference to the accompanying drawings.
  • the user plane network element is integrated with the function network element of the Internet of Things.
  • FIG. 5 is a schematic diagram of a passive or semi-active Internet of Things architecture in an embodiment of the present application.
  • the Internet of Things functional network element is integrated into the user plane network element, that is, the user plane network element has the function of the Internet of Things functional network element, or the user plane network element is co-located with the Internet of Things functional network element.
  • Passive or semi-active IoT data is communicated through user plane channels.
  • the downlink data is sent from the passive or semi-active IoT server to the user plane network element (that is, the IoT functional network element among them), and then the user plane network element sends it to the label through the access network device.
  • the label is sent to the access network device, and then the access network device sends it to the user plane network element (the Internet of Things functional network element) through the user plane channel, and then the user plane network element (the Internet of Things functional network element) Send to passive or semi-active IoT server.
  • FIG. 6 is a schematic diagram of another passive or semi-active Internet of Things architecture in an embodiment of the present application.
  • the Internet of Things functional network element is connected to the user plane network element, and the Internet of Things functional network element and the user plane network element are independent of each other.
  • the Internet of Things function network element is used as the control plane network element.
  • FIG. 7a-7b is a schematic diagram of another passive or semi-active IoT architecture in the embodiment of the present application.
  • IoT functional network elements are deployed in the core network as control plane network elements.
  • passive or semi-active IoT data is communicated through the control plane channel.
  • the passive or semi-active IoT server sends downlink data to the IoT functional network element, and then the IoT functional network element sends it to the access network device through SMF (optional) and AMF, and then sends it to the label .
  • the label is directly sent to the access network device, and then the access network device sends it to the IoT functional network element through the control plane channel (via AMF, SMF (optional)), and then the IoT functional network element sends For passive or semi-active IoT servers.
  • the network element of the Internet of Things function is not co-located with the network element of the user plane.
  • the Internet of Things functional network element When the Internet of Things functional network element is not co-located with the user plane network element, the Internet of Things functional network element establishes a communication connection with the user plane network element as a network element of the local communication network.
  • the network element of the user plane communicates with the functional network element of the Internet of Things through a dedicated interface (such as an N4 interface).
  • the user plane network element communicates with the Internet of Things functional network element through a service interface.
  • the RAN agent establishes a control plane channel.
  • Agent establishment may also be referred to simply as “agent establishment” in this embodiment of the application.
  • the control plane (or user plane) channel with granularity as RAN refers to the RAN establishing a control plane (or user plane) channel for passive or semi-active IoT data communication), and each RAN has a corresponding The ID of the terminal (also referred to as the SUPI established by the RAN for the label agent), the RAN supports the function of the terminal, and uses the ID of the terminal to establish a control plane (or user plane) channel for the terminal with the core network.
  • the control plane (or user plane) channel of the terminal is used to transmit control signaling or user plane data of labels within the coverage of the RAN.
  • the control plane (or user plane) channel whose granularity is a label means that the RAN establishes a control plane (or user plane) channel for each label agent.
  • the RAN constructs a terminal identity (also referred to as SUPI established by the RAN for the label proxy) using the identity of the corresponding label, and uses the constructed terminal identity to establish a control plane (or user plane) channel for the label.
  • the control plane (or user plane) channel is a channel between the RAN and the core network, and is used to transmit control plane signaling or user plane data of a corresponding label.
  • agent establishment refers to the RAN constructing non-access stratum (non-access stratum, NAS) signaling for the label, and completing the establishment process of the control plane channel based on the signaling . Please refer to FIG. 8 for a specific process of "creating a control plane channel by an agent”.
  • the RAN selects the AMF.
  • step C1 the RAN selects the AMF.
  • RAN sends N2 UE initial message to AMF.
  • the RAN sends an N2 UE initial message (N2 UE initial message) to the AMF.
  • the N2 UE initial message includes non-access stratum (non-access stratum, NAS) signaling, and the NAS signaling is a registration request message, and the registration request message includes the terminal identifier.
  • the terminal identifier is a terminal identifier constructed according to the label identifier.
  • the terminal identifier is the identifier of the terminal corresponding to the RAN.
  • the terminal identifier may be in the form of a subscription concealed identifier (SUCI).
  • SUCI subscription concealed identifier
  • AMF chooses AUSF.
  • the network authenticates the tag.
  • step C4 the network authenticates the tag.
  • the NAS security mode command process is performed between C5, RAN and AMF.
  • step C5 after the authentication is successful, the AMF initializes the NAS security mode command procedure (NAS Security Mode Command procedure).
  • the RAN responds to the AMF with a N2 uplink NAS message (NAS Security Mode Complete message).
  • NAS security context NAS security context
  • step C6 when the AMF receives the NAS security mode completion message of the RAN, it will send an initial context request (N2Initial Ctx Request) to the RAN; when the RAN completes the context establishment, it will send a response message (N2Initial Ctx Response) to the AMF.
  • the RAN establishes the context instead of the label.
  • the AMF sends a NAS registration acceptance message.
  • the RAN sends a NAS registration completion message.
  • Steps C7-C8 indicate that the process of establishing a control plane channel for the tag agent by the RAN is completed, and the tag is successfully registered to the core network.
  • RAN completes the protocol data unit (Protocol Data Unit, PDU) session establishment process for the label.
  • PDU Protocol Data Unit
  • Fig. 9a is a schematic flow diagram of the RAN completing the PDU session establishment process for the label in the embodiment of the present application. Before the RAN sends the PDU session establishment request, it needs to help the tag to complete the registration process shown in Figure 9a.
  • the RAN builds the control plane channel on behalf of the RAN and completes the registration process.
  • Step D1 is similar to the aforementioned steps shown in FIG. 8 , and will not be repeated here.
  • the RAN sends an N2 message to the AMF.
  • step D2 the RAN sends an N2 message to the AMF, the N2 message includes a PDU session establishment request message (PDU Session Establishment Request), and the PDU session establishment request message is a NAS message.
  • PDU Session Establishment Request PDU Session Establishment Request
  • the PDU session establishment request message includes a session identifier (PDU Session ID); optionally, it also includes one or more of the following parameters: request type (Request Type), UE requested data network name (UE Requested DNN) or slice information (S-NSSAI) and other parameters.
  • request type can include one or more of the following:
  • Initial request (Initial request), indicating that the session establishment request message is used to request the establishment of a new session.
  • the session identifier in the message should be the session identifier newly generated by the UE, that is, it should be the same as the currently established session.
  • the session ID is different.
  • the currently existing PDU session (Existing PDU Session), indicating that the session establishment request message is used to request a currently established session to be switched from 3GPP access to non-3GPP access, or from non-3GPP access to 3GPP access. Alternatively, it is used to request to switch a currently established 4G packet data network (Packet Data Network, PDN) connection to 5G.
  • PDN Packet Data Network
  • the session identifier should be the session identifier of a currently established session, indicating that the session is to be switched.
  • Emergency Request (Emergency Request), indicating that the session establishment request message is used to request establishment of a PDU session for emergency services.
  • Each network element executes a session establishment process.
  • step D3 the main steps of session establishment are as follows:
  • AMF selects SMF.
  • AMF sends a session creation session context request message to SMF, which includes parameters such as SUPI (UE identification), DNN requested by UE, PDU Session ID;
  • SUPI UE identification
  • DNN requested by UE
  • PDU Session ID PDU Session ID
  • Step D3.3 The SMF obtains the session management subscription data from the UDM.
  • Step D3.3 is an optional step.
  • the SMF feeds back the session creation session context response message to the AMF.
  • step D3.5 is an optional step.
  • the SMF selects a PCF and establishes a session policy association with the PCF.
  • the SMF initiates session policy association modification to the PCF.
  • the SMF sends the IP address allocated to the UE to the PCF.
  • the SMF establishes the N4 connection with the UPF.
  • SMF sends N1N2 message to AMF.
  • This message includes information such as session identifier, N2 interface session management information (N2 SM information) and N1 interface session management container (N1 SM Container); among them, N2 SM information is SMF sends to RAN through AMF, and the information in N1 SM Container is sent to RAN by SMF through AMF (subsequent AMF sends to RAN through NAS message); N2 SM information contains UPF tunnel endpoint identification and other information, the information It will be sent to RAN to tell RAN where the uplink data should be sent.
  • the N1 SM Container contains the session establishment acceptance message (an optional method, PDU Session Establishment Accept) and other session-related parameter information.
  • the AMF sends the N2 session request message to the RAN, which includes the N2 SM information, and the NAS message to be sent to the UE, where the NAS message includes the session identifier and the N1 SM Container.
  • the RAN establishes air interface resources with the UE, and the RAN sends a NAS message to the UE; the NAS message includes a PDU session establishment acceptance message.
  • the RAN sends the N2 session response message to the AMF, which includes the tunnel endpoint identifier on the RAN side (which will be sent to the UPF later via the AMF and SMF). This information is used to tell the UPF the destination of the downlink data.
  • the AMF sends the message sent by the RAN to the SMF through the PDU session update session context request.
  • the SMF sends the access network (AN) tunnel endpoint identification information on the RAN side to the UPF through the N4 session modification process.
  • AN access network
  • the SMF sends a session update session context response message to the AMF.
  • the AMF sends an N2 session request message to the RAN.
  • step D4 the AMF sends the N2 PDU session request message to the RAN, which includes the session establishment acceptance message, and sends the N3 tunnel information (ie CN Tunnel Info) to the RAN, so that the RAN knows how the uplink data should be sent.
  • N3 tunnel information ie CN Tunnel Info
  • the RAN sends an N2 session response message to the AMF.
  • step D5 the RAN sends the N2 session response message to the AMF, which includes the tunnel information of the RAN, and the tunnel information of the RAN includes: the Internet Protocol (IP) address of the RAN and the tunnel endpoint identification information of the RAN.
  • IP Internet Protocol
  • the AMF notifies the UPF how to forward the downlink data.
  • step D6 the tunnel information of the RAN is sent to the UPF through the AMF and the SMF, so that the UPF knows how to forward the downlink data.
  • the AMF sends the tunnel information of the RAN to the SMF
  • the SMF sends the tunnel information of the RAN to the UPF.
  • each network element (or network function) appearing in the following embodiments may be other network elements that have the function of the network element.
  • the Internet of Things function network element may be Other network elements (or network functions) that have the function of the Internet of Things function network element in the future communication system are not limited here.
  • the IoT functional network element in the embodiment of the present application includes but not limited to: user plane function UPF, access and mobility management function AMF, session management function SMF, network storage function NRF or the first network element.
  • FIG. 9b is a schematic flow chart of an embodiment of a message transmission method proposed in the embodiment of the present application.
  • a message transmission method proposed in the embodiment of the present application includes:
  • the access network device receives the first packet from the Internet of Things functional network element.
  • step E1 the Internet of Things functional network element generates the first message according to the passive or semi-active Internet of Things instruction from the passive or semi-active Internet of Things server.
  • the first message includes passive or semi-active Internet of Things instructions.
  • the passive or semi-active IoT server sends passive or Semi-active IoT instructions.
  • the passive or semi-active IoT instructions include: event cycle specification (event cycle specification, ECSpecs) or command cycle specification (command cycle specification, CCSpecs), wherein the event cycle specification instruction or command cycle specification instruction includes the required The range of tags to be inventoried, or the range of tags that need to perform read or write operations.
  • the Internet of Things functional network element sends the first packet to the access network device through the first session.
  • the session type of the first session is the passive or semi-active Internet of Things, or the session identifier of the first session indicates that the first session is related to the passive or semi-active Internet of Things.
  • steps S2-S4 for specific steps of establishing the first session, please refer to steps S2-S4 in subsequent embodiments.
  • the access network device acquires the first information.
  • the information indicating that the first packet includes the passive or semi-active Internet of Things instruction is called first information.
  • the first information may be sent by the Internet of Things functional network element to the access network device, and the first information may also be obtained by the access network device from the Internet of Things functional network element, or the first information may be obtained by the access network device from the context information Get, no limit here.
  • the first message may include the first information, and the first message and the first information may be independent of each other, and may or may not be sent together, which is not limited here.
  • the access network device determines that the first message is related to the passive or semi-active Internet of Things according to the first information, or it can also be called that the first message needs to be processed using the second protocol, or it can also be called , the first message includes a passive or semi-active Internet of Things instruction.
  • the first message when the first message satisfies the first information, the first message includes a passive or semi-active Internet of Things instruction.
  • the first information includes a session identifier of the first session, or a session type of the first session.
  • the access network device determines that the message is related to the passive or semi-active Internet of Things or the first message includes a passive or semi-active Internet of Things instruction .
  • the first information is indication information included in the first packet.
  • the first packet includes passive or Semi-active IoT commands.
  • the first information includes one or more of the following: the message type of the first packet, the container type of the first packet, the tunnel identification information of the first packet, the information type of the first packet, the first The session ID for the session.
  • the message type of the first message can be described in the message type field in the message header of the first message; when the message type field in the message header of the message received by the access network device When the message types of the first packets are the same, the access network device determines that the packets are related to the passive or semi-active Internet of Things or the first packet includes passive or semi-active Internet of Things instructions.
  • the tunnel identification information of the first packet refers to the tunnel identification information of the first session established by the access network device agent, that is, the endpoint identification of the N3 tunnel when the access network device establishes the first session (the tunnel on the access network side endpoint identifier and/or the tunnel endpoint identifier on the core network side), the access network device can use the tunnel identifier information in the first packet header and the tunnel endpoint identifier in the first information (for example, both are the same or indicate the same tunnel endpoint ID) shows that the first packet is related to the passive or semi-active Internet of Things.
  • the access network device agent that is, the endpoint identification of the N3 tunnel when the access network device establishes the first session (the tunnel on the access network side endpoint identifier and/or the tunnel endpoint identifier on the core network side)
  • the access network device can use the tunnel identifier information in the first packet header and the tunnel endpoint identifier in the first information (for example, both are the same or indicate the same tunnel endpoint ID) shows that the first
  • the message type of the first message indicates that the first message includes passive or semi-active Internet of Things instructions, or the first message needs to use the second protocol is processed.
  • the message header of the first message includes the message type of the first message, and the message type indication of the first message includes passive or semi-active Internet of Things instructions, or the first message Need to use the second protocol for processing.
  • the Internet of Things functional network element adopts General Packet Service Tunneling Protocol-User Plane (GTP-U) encapsulation to generate the first packet.
  • GTP-U General Packet Service Tunneling Protocol-User Plane
  • the packet header of the first packet refers to the GTP-U packet header
  • the GTP-U packet header includes a message type field
  • the message type field may also be called the message type of the first packet.
  • the message type field may indicate that the first message includes passive or semi-active IoT instructions, or that the first message needs to be processed using a second protocol.
  • the message type field can be "RFID", "Passive IoT", "P-IoT” or "LLRP", which is not limited here.
  • the Internet of Things functional network element may also record the message type of the first message in a reserved field or other fields in the first message.
  • the access network device performs passive or semi-active IoT operations according to the first packet.
  • step E3 the access network device determines the passive or semi-active Internet of Things instruction included in the first message according to the first information.
  • the access network device performs a passive or semi-active Internet of Things operation according to the passive or semi-active Internet of Things command, and obtains a response to the passive or semi-active Internet of Things command.
  • the access network device determines, according to the first information, that the first packet includes a passive or semi-active Internet of Things instruction.
  • the access network device processes (also referred to as: parsing) the first packet by using the second protocol to obtain the first intermediate data.
  • the first intermediate data includes passive or semi-active IoT instructions.
  • the access network device processes the first packet by using the second protocol according to the first information to obtain the first intermediate data.
  • the access network device after receiving the first message, uses the second protocol to process the first message to obtain the first intermediate data.
  • the passive or semi-active Internet of Things operations include, but are not limited to: tag read and write operations, tag inventory operations, and the like.
  • the response of the passive or semi-active Internet of Things command includes, but is not limited to: the read data of the tag, or the inventory operation result of the tag, and the like.
  • the access network device receives the first message from the functional network element of the Internet of Things.
  • the access network device acquires the first information, and determines according to the first information that the first packet includes a passive or semi-active Internet of Things instruction.
  • the access network device learns that the message from the Internet of Things functional network element is related to the passive or semi-active Internet of Things, and the access network device performs passive or semi-active Internet of Things operations according to the first message. It solves the problem of message transmission in the scenario where the passive or semi-active IoT system is integrated with the cellular network. It enables the cellular network to analyze the application message of the passive or semi-active Internet of Things and perform related operations according to the application message.
  • the following takes the Internet of Things functional network element as the user plane network element or the Internet of Things functional network element as an independent network element (that is, the Internet of Things functional network element as the first network element) to establish a communication connection with the user plane network element as an example
  • the user plane network element is UPF as an example for description.
  • FIG. 10a is a schematic flowchart of an embodiment of a message transmission method proposed in the embodiment of the present application.
  • a message transmission method proposed in the embodiment of the present application includes:
  • the SMF configures the first rule and/or the second rule to the UPF.
  • Step 1001 is an optional step.
  • the first rule indicates how the UPF determines whether the received message is from a passive or semi-active Internet of Things server; How to deal with the text.
  • the second rule instructs the UPF on how to process packets matching specific packet detection information (for example, packets from passive or semi-active IoT servers have specific packet detection information).
  • the second rule may indicate the protocol type that the UPF needs to use to process the second message, and send the second message to the first network element, or send the parsed second message to the access network device, where the second message is Messages from passive or semi-active IoT servers.
  • the method for the UPF to process the second packet is as steps 1003a-1003b or steps 1004a-1004e in this embodiment of the present application.
  • the second rule includes: a message forwarding rule (Forwarding Action Rule, FAR).
  • FAR Forwarding Action Rule
  • the first rule includes: a flow matching rule (Packet Detection Rule, PDR).
  • PDR Packet Detection Rule
  • the UPF determines whether the received message is from a passive or semi-active IoT server according to a PDR rule. UPF determines how to process packets from passive or semi-active IoT servers according to FAR rules.
  • the UPF determines according to the address information of the message that the received message comes from the passive or semi-active Internet of Things server. UPF determines how to process packets from passive or semi-active IoT servers according to FAR rules.
  • the UPF determines whether the received message is from a passive or semi-active IoT server according to a PDR rule. UPF determines how to process packets from passive or semi-active IoT servers according to other predefined rules.
  • first rule and/or the second rule may be an enhanced N4 rule.
  • This enhanced N4 rule is relevant to passive or semi-active IoT services.
  • the first rule and/or the second rule may include: an enhanced FAR rule, and/or an enhanced PDR rule.
  • the UPF determines whether the received message comes from the passive or semi-active IoT server according to the enhanced PDR rule. UPF determines how to process packets from passive or semi-active IoT servers based on enhanced FAR rules.
  • the UPF determines according to the address information of the message that the received message comes from the passive or semi-active Internet of Things server. UPF determines how to process packets from passive or semi-active IoT servers based on enhanced FAR rules.
  • the UPF determines whether the received message is from a passive or semi-active IoT server according to an enhanced PDR rule. UPF determines how to process packets from passive or semi-active IoT servers according to other predefined rules.
  • the SMF selects the UPF co-provisioned with the first network element (or the UPF having the function of the first network element) from multiple UPFs in the current network.
  • the SMF configures the first rule and/or the second rule to the UPF.
  • first rule and/or the second rule may also be pre-configured in the UPF, and step 1001 is not executed in this case.
  • the first rule may be sent to the UPF by the SMF, or may be preset on the UPF.
  • the second rule can be sent from the SMF to the UPF, or can be preset on the UPF.
  • the SMF sends the first rule and the second rule to the UPF; as another possible implementation, the SMF sends the first rule to the UPF, and the second rule is preset on the UPF; as another In a possible implementation manner, the SMF sends the second rule to the UPF, and the first rule is preset on the UPF; as yet another possible implementation manner, the first rule and the second rule are preset on the UPF.
  • the UPF receives the second message from the passive or semi-active IoT server.
  • the RAN establishes a first session, and the first session is used to transmit passive or semi-active IoT-related instructions or operation results. Please refer to the description of FIG. 9a for the process of establishing the first session on behalf of the RAN.
  • the passive or semi-active IoT server sends the second message to the UPF.
  • the UPF determines that the second packet comes from the passive or semi-active IoT server according to the first rule.
  • the UPF determines according to the first rule that the second packet includes a passive or semi-active Internet of Things instruction. For example, if the UPF determines that the second packet matches the PDR rule, then the UPF determines that the second packet includes a passive or semi-active IoT instruction, and the UPF instructs the UPF itself or other network elements to process the second packet.
  • the UPF determines whether the second message comes from the passive or semi-active IoT server according to the address information of the second message.
  • the address information of the second packet is, for example, the source IP address of the second packet.
  • the UPF determines whether the received second message comes from a passive or semi-active IoT server according to a preconfigured first rule.
  • the UPF determines whether the received second message is from a passive or semi-active IoT server according to the IP address of the second message.
  • the UPF uses the first protocol and/or the second protocol to process the second message to generate the first message.
  • the UPF uses the first protocol and/or the second protocol to process all received packets.
  • the received message comes from a passive or semi-active IoT server.
  • the UPF generates a first packet according to the received packet.
  • the UPF determines whether the received second message comes from the passive or semi-active IoT server according to the first rule configured by the SMF.
  • the second message includes a passive or semi-active Internet of Things instruction.
  • the passive or semi-active Internet of Things server sends passive or Semi-active IoT instructions.
  • the passive or semi-active IoT instructions include: event cycle specification (event cycle specification, ECSpecs) or command cycle specification (command cycle specification, CCSpecs), wherein the event cycle specification instruction or command cycle specification instruction includes the required The range of tags to be inventoried, or the range of tags that need to perform read or write operations.
  • step 1002 according to the deployment relationship between the Internet of Things functional network element and the UPF, it can be subdivided into two solutions: (1), the UPF and the Internet of Things functional network element are co-located, or the UPF realizes the function of the Internet of Things functional network element .
  • the Internet of Things functional network element is also called the first network element.
  • the architecture shown in Figure 6. Specifically, the steps corresponding to solution (1) are 1003a-1003b; the steps corresponding to solution (2) are 1004a-1004e.
  • the UPF uses the first protocol to process the second message, and generates first intermediate data.
  • the UPF uses the first protocol to process (or be referred to as: parse) the second packet, and the processed data is called first intermediate data.
  • the first protocol is an Application Level Event (Application Level Event, ALE) protocol.
  • Application Level Event Application Level Event
  • the UPF determines that the first protocol needs to be used to process the second packet according to the second rule.
  • the UPF uses the second protocol to process the first intermediate data, and generates a first message.
  • the UPF uses the second protocol to process the first intermediate data and generate the first message.
  • the second protocol is Low Level Reader Protocol (Low Level Reader Protocol, LLRP).
  • the UPF determines, according to the second rule, that the first intermediate data needs to be processed by using the second protocol.
  • the first packet generated by the UPF may include the first information.
  • the first packet generated by the UPF may not include the first information.
  • the message type of the first message indicates that the first message includes passive or semi-active Internet of Things instructions, or that the first message needs to be processed using the second protocol.
  • the message header of the first message includes a message type of the first message, and the message type of the first message indicates that the first message includes a passive or semi-active Internet of Things instruction, or Indicates that the first packet needs to be processed using the second protocol.
  • the UPF generates the first packet by encapsulating the General Packet Radio Service Tunneling Protocol-User Plane (GTP-U).
  • GTP-U General Packet Radio Service Tunneling Protocol-User Plane
  • the packet header of the first packet refers to the GTP-U packet header
  • the GTP-U packet header includes a message type field
  • the message type field may also be called the message type of the first packet.
  • the message type field may indicate that the first message includes passive or semi-active Internet of Things instructions, or that the first message needs to be processed using a second protocol.
  • the message type field can be "RFID", "Passive IoT", "P-IoT” or "LLRP", which is not limited here.
  • the UPF may also record the message type of the first packet in a reserved field or other fields in the first packet.
  • the UPF sends the second packet to the first network element.
  • the UPF sends the second message to the first network element after confirming that the second message comes from the passive or semi-active IoT server.
  • the UPF sends the second packet to the first network element according to the second rule.
  • the first network element processes the second packet by using the first protocol to generate first intermediate data.
  • the first network element processes (or is called: parses) the second message using the first protocol, and the processed data is called first intermediate data.
  • the first protocol is an Application Level Event (Application Level Event, ALE) protocol.
  • ALE Application Level Event
  • the first intermediate data is called an ALE protocol message.
  • the first network element processes the first intermediate data by using the second protocol to generate second intermediate data.
  • the first network element processes the first intermediate data by using the second protocol to generate the second intermediate data.
  • the second protocol is a Low Level Reader Protocol (Low Level Reader Protocol, LLRP).
  • LLRP Low Level Reader Protocol
  • the second intermediate data is called an LLRP protocol message.
  • the first network element sends the second intermediate data to the UPF.
  • the UPF processes the second intermediate data to generate the first packet.
  • the UPF processes the second intermediate data to obtain the first message. Specifically, the UPF encapsulates the second intermediate data to obtain the first packet.
  • the packet header of the first packet indicates that the first packet needs to be processed using the second protocol.
  • the header of the first packet includes a message type of the first packet, and the message type of the first packet indicates that the first packet needs to be processed using the second protocol.
  • the UPF adopts General Packet Service Tunneling Protocol-User Plane (GTP-U) encapsulation to generate the first message.
  • GTP-U General Packet Service Tunneling Protocol-User Plane
  • the packet header of the first packet refers to the GTP-U packet header
  • the GTP-U packet header includes a message type field
  • the message type field may also be called the message type of the first packet.
  • the message type field may indicate that the first packet needs to be processed using the second protocol.
  • the message type field can be "RFID", “Passive IoT", "P-IoT” or "LLRP", which is not limited here.
  • the UPF may also record the message type of the first packet in a reserved field or other fields in the first packet.
  • the message type of the first packet indicates that the first packet needs to be processed using the second protocol.
  • the UPF sends the first packet to the access network device.
  • the UPF after the UPF generates the first packet, it sends the first packet to the access network device.
  • the UPF sends the first packet to the access network device through the first session.
  • the flow of establishing the first session by the RAN is the flow of establishing the session by the RAN agent in FIG. 9a.
  • the session type of the first session is the passive or semi-active Internet of Things, or the session identifier of the first session indicates that the first session is related to the passive or semi-active Internet of Things.
  • steps of establishing the first session please refer to step S2 in subsequent embodiments.
  • the RAN processes the first packet by using the second protocol according to the first information, and obtains first intermediate data.
  • the RAN acquires the first information, and according to the first information, determines that the first message includes a passive or semi-active Internet of Things instruction.
  • the RAN obtains the first information and the specific content of the first information may refer to the description of E2 in FIG. 9b.
  • the RAN processes the first packet by using the second protocol. For example, the RAN determines, according to the session identifier of the first session or the session type of the first session, that the first packet transmitted in the first session includes a passive or semi-active Internet of Things instruction.
  • the RAN uses the second protocol to process (also referred to as: parse) the first message to obtain the first intermediate data.
  • the first intermediate data includes passive or semi-active IoT instructions.
  • the passive or semi-active IoT command may be an air interface command.
  • the RAN directly uses the second protocol to process the first message to obtain the passive or semi-active Internet of Things instruction.
  • the RAN determines, according to the session identifier of the first session or the session type of the first session, that the first packet transmitted in the first session includes a passive or semi-active Internet of Things instruction. Furthermore, the RAN determines that the first packet needs to be processed by using the second protocol.
  • the RAN determines, according to the source IP address included in the first message, that the first message is from the first network element or from the UPF (the UPF and The first network element is co-located or the UPF has the function of the first network element). Furthermore, the RAN determines that the first packet needs to be processed by using the second protocol.
  • the RAN performs a passive or semi-active IoT operation according to the first intermediate data, and obtains a response to a passive or semi-active IoT command.
  • the RAN performs a passive or semi-active IoT operation according to the passive or semi-active IoT command included in the first intermediate data, and obtains a response to the passive or semi-active IoT command.
  • the passive or semi-active Internet of Things operations include, but are not limited to: tag read and write operations, tag inventory operations, and the like.
  • the response of the passive or semi-active Internet of Things command includes, but is not limited to: the read data of the tag, or the inventory operation result of the tag, and the like.
  • the RAN uses the second protocol to process the response of the passive or semi-active Internet of Things command, and generates a third message.
  • the RAN uses the second protocol to process the response to the passive or semi-active Internet of Things command to obtain the third message. Specifically, first, the RAN processes the response to the passive or semi-active Internet of Things command to obtain a message message including the response to the passive or semi-active Internet of Things command. Secondly, the RAN further encapsulates the message packet to obtain a third packet. The third message includes a response to the passive or semi-active Internet of Things command.
  • the Internet of Things functional network element acquires the second information.
  • information indicating that the third message includes signaling related to the passive or semi-active Internet of Things, or indicating that the third message needs to be processed using the second protocol is called second information.
  • the second information may be sent by the access network device to the Internet of Things functional network element, and the second information may also be obtained by the Internet of Things functional network element or from the access network device, which is not limited here.
  • the third message may include the second information, and the third message may also be independent of the second information, that is, the second information may be sent together with the third message, or the second information and the first message may be sent together.
  • the three messages are sent separately, or the Internet of Things functional network element obtains the second information in other ways, which is not limited here.
  • the Internet of Things functional network element determines that the third message is related to the passive or semi-active Internet of Things according to the second information, which may also be referred to as determining that the third message needs to be processed using the second protocol.
  • the second information includes one or more of the following: the message type of the third message, the container type of the third message, the tunnel identification information of the third message, or the second information is the information of the third message type.
  • the message type of the third message indicates that the third message is related to the passive or semi-active Internet of Things, or the third message needs to be processed using the second protocol.
  • the packet header of the third packet includes a message type of the third packet, and the message type of the third packet indicates that the third packet needs to be processed using the second protocol.
  • the RAN adopts General Packet Radio Tunneling Protocol-User Plane (GTP-U) encapsulation to generate the third packet.
  • GTP-U General Packet Radio Tunneling Protocol-User Plane
  • the packet header of the third packet refers to the GTP-U packet header
  • the GTP-U packet header includes a message type field
  • the message type field is also called the message type of the third packet.
  • the message type field may indicate that the third packet needs to be processed using the second protocol.
  • the message type field can be "RFID", "Passive IoT", "P-IoT” or "LLRP", which is not limited here.
  • the RAN may also record the message type of the third message in a reserved field or other fields in the third message.
  • the message type of the third packet indicates that the third packet needs to be processed using the second protocol.
  • the RAN sends a third packet to the UPF.
  • the RAN sends the third packet to the UPF through the first session.
  • Step 1010 or steps 1011a-1011e are executed after step 1009.
  • the UPF generates a fourth packet according to the third packet.
  • the UPF uses the second protocol and the first protocol to process the third packet and generate the fourth packet.
  • the UPF after the UPF receives the third message, according to the second information (such as the message type of the third message, or the message header of the third message, the session identifier of the first session, or the session type) to determine that the third packet needs to be processed by using the second protocol.
  • the second information such as the message type of the third message, or the message header of the third message, the session identifier of the first session, or the session type
  • the UPF determines that the third message transmitted in the first session includes a passive or semi-active Internet of Things instruction according to the session identifier of the first session or the session type of the first session the response to. Furthermore, the UPF determines that the third packet needs to be processed by using the second protocol.
  • the second protocol is the LLRP protocol as an example.
  • the UPF uses the LLRP protocol to process (also referred to as parsing) the third message to obtain the response of the passive or semi-active IoT command.
  • the UPF uses the first protocol (for example, the ALE protocol) to process the response to the passive or semi-active Internet of Things command, and generates a fourth message.
  • the fourth message includes responses to passive or semi-active IoT commands.
  • Step 1012 is executed after step 1010 .
  • the UPF and the first network element cooperate to process the third message to generate the fourth message.
  • the implementation is as follows:
  • the UPF processes the third message to generate third intermediate data.
  • the UPF decapsulates the third packet to generate third intermediate data.
  • the UPF uses GTP-U to decapsulate the third packet to generate third intermediate data.
  • the third intermediate data includes responses to passive or semi-active IoT commands.
  • the UPF sends the third intermediate data to the first network element.
  • the UPF sends the third intermediate data to the first network element, and the first network element processes the third intermediate data.
  • the first network element processes the third intermediate data by using the second protocol to generate fourth intermediate data.
  • the first network element after the first network element receives the third message, according to the second information (such as the message type of the third message, or the message header of the third message, the session identifier of the first session, or The session type of the first session) determines that the third packet needs to be processed by using the second protocol.
  • the second information such as the message type of the third message, or the message header of the third message, the session identifier of the first session, or The session type of the first session
  • the second protocol may be a Low Level Reader Protocol (Low Level Reader Protocol, LLRP).
  • Low Level Reader Protocol Low Level Reader Protocol
  • the first network element first uses the second protocol to parse the third intermediate data to generate fourth intermediate data (including responses to passive or semi-active Internet of Things commands), where the fourth intermediate data may be LLRP protocol messages.
  • the first network element processes the fourth intermediate data to generate a fourth packet.
  • the first network element processes the fourth intermediate data by using the first protocol, and generates the fourth message.
  • the fourth message includes responses to passive or semi-active IoT commands.
  • the first protocol may be an application layer event (Application Level Event, ALE) protocol.
  • ALE Application Level Event
  • the first network element sends the fourth packet to the UPF.
  • Step 1012 is executed after step 1011e.
  • the UPF sends a fourth packet to the passive or semi-active IoT server.
  • steps 1008-1012 are optional steps.
  • the SMF may select a UPF that supports the function of the first network element.
  • the SMF can send the first rule and/or the second rule to the UPF, so that the UPF knows how to identify whether the packet is from a passive or semi-active IoT server, and/or how the UPF handles the packet from the passive or semi-active IoT server.
  • the second message from the server is a passive or semi-active IoT server.
  • the first message sent by the UPF to the RAN may include first information, so that the RAN can efficiently identify which protocol needs to be used for processing the first message.
  • the third message sent by the RAN to the UPF may include the second information, so that the UPF can efficiently identify which protocol needs to be used for processing the third message.
  • the UPF and the first network element are co-located, or the UPF implements the first network element function.
  • the architecture shown in FIG. 5 (2), the UPF and the first network element are independent of each other, and the UPF establishes a communication connection with the first network element.
  • the architecture shown in Figure 6. Describe respectively below in conjunction with accompanying drawing:
  • FIG. 10b is a schematic flow diagram of a message transmission method in an application scenario proposed by the embodiment of the present application, and an application scenario proposed by the embodiment of the present application includes:
  • the RAN completes the process of establishing a label or a control plane channel of the RAN.
  • step S1 the RAN agent establishes a control plane (or user plane) channel with RAN as granularity or label as granularity.
  • the specific establishment method is similar to the method corresponding to the aforementioned FIG. 8 , and will not be repeated here.
  • the RAN sends a PDU session establishment request message to the AMF.
  • step S2 after the RAN establishes the label or the RAN control plane channel, the RAN sends a request message, which is used to establish the first session.
  • the RAN sends a PDU session establishment request message (PDU session establishment request) to the AMF.
  • PDU session establishment request message is used to establish the first session.
  • the session type of the first session is the passive or semi-active Internet of Things, or the session identifier of the first session indicates that the first session is related to the passive or semi-active Internet of Things.
  • the PDU session establishment request message includes PDU session type information, and the PDU session type information indicates that the session type of the first session is passive or semi-active Internet of Things, or indicates that the first session transmits passive or Semi-active IoT-related data.
  • the RAN sends the PDU session type information to the AMF during the establishment of the PDU session.
  • the AMF obtains the PDU session type information in various ways. For example, the RAN sends the PDU session type information to the AMF through a non-access stratum NAS message, or the RAN sends the PDU session type information to the AMF through an N2 message. Or, the AMF acquires the PDU session type information from the subscription data of the label, or the subscription data of the terminal at the RAN granularity. Alternatively, the AMF acquires the PDU session type information from the data stored by the AMF itself. There is no limitation here.
  • the AMF sends a PDU session creation session context request to the SMF.
  • step S3a the AMF sends a PDU session creation session context request (for example, Nsmf_PDUSession_CreateSM Context Request) to the SMF, and the PDU session creation session context request indicates establishment of the first session.
  • the PDU session creation session context request includes PDU session type information, and the PDU session type information includes the session identifier of the first session, and/or the session type of the first session.
  • the PDU session type information indicates that the session type of the first session is passive or semi-active Internet of Things, or indicates that the first session transmits data related to passive or semi-active Internet of Things.
  • the session type of the first session is the passive or semi-active Internet of Things, or the session identifier of the first session indicates that the first session is related to the passive or semi-active Internet of Things.
  • the first information may be that the session type of the first session is passive or semi-active Internet of Things, or the session identifier of the first session.
  • the second information may be that the session type of the first session is passive or semi-active Internet of Things, or the session identifier of the first session.
  • the access network device may determine that the first packet transmitted in the first session includes the passive or semi-active Internet of Things instruction by acquiring the session type of the first session or the session identifier of the first session.
  • the Internet of Things function network element can determine that the third message transmitted in the first session is related to the passive or semi-active Internet of Things by obtaining the session type of the first session, or the session identifier of the first session, or that the third message
  • This paper includes data related to passive or semi-active IoT.
  • the SMF sends a PDU session creation session context response to the AMF.
  • step S3b the SMF sends a PDU session creation session context response (for example, Nsmf_PDUSession_CreateSM Context Response) to the AMF in response to the PDU session creation session context request.
  • a PDU session creation session context response for example, Nsmf_PDUSession_CreateSM Context Response
  • the SMF selects a suitable UPF.
  • step S4 the SMF responds to the PDU session establishment session context request received in step S3a, and the SMF selects a UPF supporting the function of the first network element, or selects a UPF co-located with the first network element.
  • Step S4 is optional.
  • the SMF After the SMF determines a suitable UPF, the SMF sends a session establishment acceptance message to the RAN through the AMF, so as to complete the establishment process of the first session.
  • FIG. 10c is a schematic flowchart of a message transmission method in an application scenario proposed by the embodiment of the present application.
  • Another application scenario proposed by the embodiment of the present application includes:
  • the RAN completes the establishment process of the label or the RAN control plane channel.
  • the RAN sends a PDU session establishment request message to the AMF.
  • the AMF sends a PDU session creation session context request to the SMF.
  • the SMF sends a PDU session creation session context response to the AMF.
  • Steps Q1-Q3b are similar to the aforementioned steps S1-S3b, and will not be repeated here.
  • step Q4 the SMF responds to the PDU session creation session context request received in step Q3a, and the SMF selects a UPF that has a communication connection with the first network element.
  • Step Q4 is optional. For example, all UPFs in the network have communication connections with the first network element.
  • the SMF After the SMF determines a suitable UPF, the SMF sends a session establishment acceptance message to the RAN through the AMF, so as to complete the establishment process of the first session.
  • FIG. 11 is a schematic flowchart of an embodiment of a message transmission method proposed in an embodiment of the present application.
  • a message transmission method proposed in the embodiment of the present application includes:
  • the RAN establishes a first session for the tag agent.
  • the session type of the first session is the passive or semi-active Internet of Things, or the session identifier of the first session indicates that the first session is related to the passive or semi-active Internet of Things.
  • the first session is used to transmit passive or semi-active IoT related data.
  • the first session is a "non-IP data delivery (Non-IP Data Delivery, NIDD)" session.
  • the SMF sends a session management context establishment request message to the NEF.
  • the SMF in order to establish a control plane channel between the RAN and the passive or semi-active IoT server, the SMF sends a session management context establishment request message (for example, Nnef_SMContext_Create Request) to the NEF.
  • the session management context establishment request message includes one or more parameters such as label identification information, session identification of the first session, session type of the first session, SMF identification, and NIDD information.
  • NIDD information indicates the maximum packet size.
  • the SMF obtains the NIDD information from the NEF.
  • the NIDD information is included in the PDU session establishment reception message sent by the SMF to the tag.
  • the NEF sends a session management context establishment response message to the SMF.
  • the NEF creates session context information, which is associated with tag identification information, session identification of the first session, session type of the first session and other related information.
  • the NEF sends a session management context establishment response message (for example, Nnef_SMContext_Create Response) to the SMF, and the session management context establishment response message includes NIDD information for notifying the SMF that the session context information of the label has been created.
  • a session management context establishment response message for example, Nnef_SMContext_Create Response
  • the communication network establishes a NIDD session for the tag.
  • the downlink data sent by the passive or semi-active IoT server is transmitted in the NIDD session, it will be sent to the RAN through the NEF, SMF, and AMF, and then sent to the tag through the RAN.
  • the uplink data of the tag is sent to the passive or semi-active IoT server through RAN, AMF, SMF, and NEF.
  • the AMF receives the second message from the passive or semi-active IoT server.
  • step 1104 specifically, it can be divided into the following steps:
  • step 1104.1 after the passive or semi-active IoT server sends the second message to the first network element, the first network element uses the first protocol to analyze and process it using the second protocol to generate the first message.
  • the second message includes passive or semi-active Internet of Things instructions.
  • the first message includes passive or semi-active Internet of Things instructions.
  • the passive or semi-active IoT server sends the second message to the first network element through the NEF; the passive or semi-active IoT server sends a message to the NEF, wherein the message includes passive Or semi-active Internet of Things instructions and the external identification of the tag (the external identification of the tag can be understood as identification information recognizable by the external network).
  • the tag's external identifier corresponds to the tag's Subscription Permanent Identifier (SUPI).
  • the external identifier is a Generic Public Subscription Identifier (Generic Public Subscription Identifier, GPSI), and NEF will assign a corresponding GPSI identifier to SUPI for use when interacting with external third parties, preventing third parties from obtaining SUPI and avoiding privacy risks .
  • the NEF identifies the corresponding SUPI according to the external identifier of the label, and sends a message to the first network element, where the message includes the second message and the SUPI.
  • the first network element sends the first packet to the SMF.
  • the first network element also sends the SUPI established by the RAN for the label agent to the SMF.
  • the first network element sends the first message to the SMF through the service interface, where the first message includes the SUPI established by the RAN for the label agent.
  • the first network element sends the SUPI and the first message to the SMF through the service interface.
  • step 1104.3 the SMF sends the first message to the AMF.
  • the SMF sends a Namf_Communication_N1N2MessageTransfer message to the AMF, and the Namf_Communication_N1N2MessageTransfer message includes the SUPI, the session identifier of the first session, the session type of the first session, and the first message.
  • the AMF sends the first packet to the RAN through the first session.
  • the AMF sends the first packet to the RAN through the first session.
  • the first message is a downlink non-access stratum transport (DL NAS Transport) message.
  • DL NAS Transport downlink non-access stratum transport
  • the first information is a session identifier of the first session, and/or a session type of the first session.
  • the access network device determines that the first packet needs to be processed by using the second protocol.
  • the RAN determines, according to the session type of the first session or the session identifier of the first session, that the first packet transmitted in the first session needs to be processed by using the second protocol.
  • the specific processing method is similar to the aforementioned step 1006, and will not be repeated here.
  • step 1106 is an optional step, and the access network device may directly use the second protocol to process the first message, that is, directly enter step 1107 after step 1005 .
  • the access network device processes the first packet by using the second protocol to obtain the first intermediate data.
  • Step 1107 is similar to the aforementioned step 1006, and will not be repeated here.
  • the RAN executes a passive or semi-active Internet of Things operation according to the first intermediate data, and obtains a response to a passive or semi-active Internet of Things command.
  • Step 1108 is similar to the aforementioned step 1007, and will not be repeated here.
  • the RAN sends a response to the passive or semi-active IoT command to the passive or semi-active IoT server.
  • step 1109 specifically, it can be divided into the following steps:
  • the RAN sends the response of the passive or semi-active IoT command to the AMF through an uplink NAS transmission message or N2 message.
  • the uplink NAS transmission message or the N2 message includes a third message, and the second message includes a response to a passive or semi-active Internet of Things command.
  • the uplink NAS transmission message or the N2 message further includes the session identifier of the first session, and/or the session type of the first session.
  • the AMF sends the Nsmf_PDUSession_SendMOData request message to the SMF through the service interface, which includes the SUPI created by the RAN agent, the session identifier of the first session, the session type of the first session, and the third message (passive or semi-active responses to IoT commands).
  • step 1109.3 the SMF sends the Nnef_SMContext_Delivery request message to the NEF through the service interface, which includes the SUPI and the third message (the response to the passive or semi-active IoT command).
  • step 1109.4 the NEF sends the Nnef_NIDD_DeliveryNotify request message to the first network element through the service interface, wherein the Nnef_NIDD_DeliveryNotify request message includes the third message (response to the passive or semi-active IoT command).
  • the first network element uses the second protocol to parse the third message included in the Nnef_NIDD_DeliveryNotify request message, and obtains the response of the passive or semi-active Internet of Things command.
  • the first network element uses the first protocol to process the response of the passive or semi-active Internet of Things command, and generates a fourth message. Again, the first network element will send the fourth message to the passive or semi-active Internet of Things server, and the fourth message includes a response to the passive or semi-active Internet of Things command.
  • the first protocol is an Application Level Event (Application Level Event, ALE) protocol.
  • Application Level Event Application Level Event
  • the second protocol is a Low Level Reader Protocol (Low Level Reader Protocol, LLRP).
  • LLRP Low Level Reader Protocol
  • the passive or semi-active Internet of Things command and the response to the passive or semi-active Internet of Things command are transmitted through the control plane channel.
  • the RAN uses the second protocol to analyze the data (or message) transmitted in the first session according to the first information (the session type of the first session or the session identifier of the first session).
  • RAN performs passive or semi-active IoT operations according to the parsing results (passive or semi-active IoT commands).
  • FIG. 12 is a schematic flowchart of another embodiment of a message transmission method proposed in the embodiment of the present application.
  • a message transmission method proposed in the embodiment of the present application includes:
  • the first network element subscribes to the AMF for the events of the RAN generation control plane.
  • the first network element sends a subscription request to the second network element, where the subscription request is used to acquire access network device information.
  • the access network device information includes but is not limited to: the permanent identification of the access network device (such as SUPI), the information of the core network element serving the access network device, the access network device information includes but is not limited to the core network Address information and/or identification information of the cell, identification information of the reader/writer of the access network device, and the like.
  • the second network element is an AMF for illustration. It can be understood that the Internet of Things function network element can also send a subscription request to other second network elements to subscribe to the events of the RAN agent construction control plane.
  • the core network element includes, but is not limited to: AMF, SMF, UPF, NRF, UDM, AUSF, or PCF.
  • the second network element includes, but is not limited to: AMF, SMF, UPF, NRF, UDM, AUSF, or PCF.
  • the first network element subscribes to the AMF to establish the control plane event of the RAN agent, so that the first network element obtains the SUPI established by the RAN agent and the RAN (for example: RAN identification information (which may be the RAN reader-writer identification)) relation.
  • the SUPI for example: you can subscribe to all AMFs in the network, or you can subscribe to some AMFs.
  • the first network element can obtain which RAN agent has established a control plane channel and the SUPI information established by the RAN agent through the event reported by the AMF.
  • the subsequent passive or semi-active IoT server sends passive or semi-active IoT commands (or information, or data) to the first network element, so that the network element (or network function, such as NEF, AMF, UDM or SMF) learns the destination peer of the message, that is, the target RAN to which the message needs to be sent.
  • the network element or network function, such as NEF, AMF, UDM or SMF
  • pre-configuration enables the NEF to know that all messages from the passive or semi-active IoT server are forwarded to the first network element; similarly, all messages from the first network element are forwarded to Passive or semi-active IoT servers.
  • step 1202 is an optional step.
  • the passive or semi-active IoT server may directly interact with the first network element.
  • the RAN agent builds a control plane (and/or user plane) channel.
  • the RAN establishes a control plane (and/or user plane) channel with the RAN as the granularity or with the label as the granularity.
  • the specific establishment method is similar to the method corresponding to the aforementioned FIG. 8 (and/or FIG. 9a ), and will not be described in detail here.
  • the first network element receives a passive or semi-active IoT instruction from a passive or semi-active IoT server.
  • the passive or semi-active Internet of Things server sends a passive or semi-active Internet of Things instruction to the first network element.
  • the passive or semi-active Internet of Things server sends a passive or semi-active Internet of Things command to the first network element through the NEF.
  • the first network element parses the passive or semi-active Internet of Things instruction by using the first protocol, and processes it by using the second protocol to generate the first message.
  • the first message includes passive or semi-active Internet of Things instructions.
  • the first protocol is an Application Level Event (Application Level Event, ALE) protocol.
  • Application Level Event Application Level Event
  • the second protocol is a Low Level Reader Protocol (Low Level Reader Protocol, LLRP).
  • LLRP Low Level Reader Protocol
  • the AMF receives the first message from the first network element.
  • the first network element may send the first message to the AMF through a service interface message (for example: Namf_Communication_N1N2MessageTransfer).
  • the first message includes the SUPI created by the RAN, and a payload container (Payload container) or information type.
  • the payload container is also called the container type of the first packet, or the container type included in the first packet, and the information type is also called the information type of the first packet. That is, the first information includes: the container type of the first packet, or the information type of the first packet.
  • the container type included in the first message is N1 P-IoT (or N1 Passive IoT) transmission.
  • the container type included in the first packet is N2 P-IoT (or N2 Passive IoT) transmission.
  • the information type of the first message can be "Passive IoT Information", "P-IoT Information” or "LLRP Information” and so on.
  • the above container type or information type indicates that the first packet is related to the passive or semi-active Internet of Things. It should be noted that the above-mentioned container types or information types are only illustrative, and do not limit the names of the container types or information types.
  • the container includes passive or semi-active Internet of Things instructions, that is, the second protocol encapsulates passive or semi-active Internet of Things instructions into the first message.
  • the AMF sends the first packet to the RAN.
  • the AMF when the container type included in the first message is N1 P-IoT (or N1 Passive IoT) transmission, the AMF sends the first message through the Non-Access Stratum (NAS) protocol stack, The first message is N1 P-IoT (or N1 Passive IoT) transmission message (also called downlink NAS transmission message, DL NAS Transport); or,
  • AMF sends the first message through the next generation application protocol (Next Generation Application Protocol, NGAP) protocol stack, and the first message is N2 P-IoT (or N1 Passive IoT) transmits messages.
  • NAP Next Generation Application Protocol
  • the first packet includes the first information.
  • the first information includes: the container type of the first packet, or the information type of the second packet.
  • the container type of the first message is: N1 P-IoT (or N1 Passive IoT) transmission.
  • the container type of the first message is N2 P-IoT (or N2 Passive IoT) transmission.
  • the information type of the first message may be "Passive IoT Information", "P-IoT Information", or "LLRP Information” and so on.
  • the above container type or information type indicates that the first packet is related to the passive or semi-active Internet of Things. It should be noted that the above-mentioned container types or information types are only illustrative, and do not limit the names of the container types or information types.
  • the container (“N1 P-IoT (or N1 Passive IoT) transmission” container, or “N2 P-IoT (or N2 Passive IoT) transmission” container) includes passive or semi-active IoT instructions, that is, the second
  • the protocol encapsulates passive or semi-active IoT commands into the first message.
  • the first message includes the passive or semi-active Internet of Things instruction.
  • the access network device determines that the first packet needs to be processed by using the second protocol.
  • the access network device determines, according to the first information, that the first packet needs to be processed by using the second protocol.
  • the specific processing method is similar to the aforementioned step 1006, and will not be repeated here.
  • step 1207 is an optional step, and when step 1207 is not performed, step 1208 is performed after step 1206 .
  • the access network device processes the first packet by using the second protocol to obtain the first intermediate data.
  • Step 1208 is similar to the aforementioned step 1006, and will not be repeated here.
  • the RAN performs a passive or semi-active IoT operation according to the first intermediate data, and obtains a response to a passive or semi-active IoT command.
  • Step 1209 is similar to the aforementioned step 1007, and will not be repeated here.
  • the RAN sends a third packet to the AMF, where the third packet includes a response to the passive or semi-active Internet of Things command.
  • the response to the passive or semi-active Internet of Things command is passed through the third report
  • the text is sent to AMF.
  • the third message can be N1 P-IoT (or N1 Passive IoT) transmission message (also called uplink NAS transmission message, UL NAS Transport), and the third message can also be N2 P-IoT (or N2 Passive IoT IoT) to transmit messages.
  • the RAN sends the message to the AMF through the N1 P-IoT (or N1 Passive IoT)
  • the container type of the N1 P-IoT (or N1 Passive IoT) transport message is the second protocol transmission, which is used to indicate to the AMF that the message is related to the non- source or semi-active IoT, the message needs to be sent to the first network element.
  • the RAN can also transmit a message to the AMF through the N2 P-IoT (or N2 Passive IoT), instructing the AMF that the N2 message is related to the passive or semi-active Internet of Things and needs to be forwarded to the first network element.
  • N2 P-IoT or N2 Passive IoT
  • the third message includes the second information.
  • the second information includes: the container type of the third packet, or the information type of the third packet.
  • the container type of the third message is: N1 P-IoT (or N1 Passive IoT) transmission.
  • the container type of the third message is N2 P-IoT (or N2 Passive IoT) transmission.
  • the information type of the third message may be "Passive IoT Information", "P-IoT Information", or "LLRP Information” and so on.
  • the above container type or information type indicates that the third packet is related to the passive or semi-active Internet of Things, or that the third packet needs to be processed using the second protocol. It should be noted that the above-mentioned container types or information types are only illustrative, and do not limit the names of the container types or information types.
  • N1 P-IoT (or N1 Passive IoT) Transport container
  • N2 P-IoT (or N2 Passive IoT) Transport container
  • the second protocol encapsulates the response of the passive or semi-active Internet of Things command into the third message.
  • the third message includes a response to the passive or semi-active Internet of Things command.
  • the AMF sends the third packet to the first network element.
  • the AMF learns that the third message needs to be forwarded to the first network element, and may send the third message to the first network element through the service interface.
  • the service interface message may be a newly defined message such as "Nx_PIoT_Delivery", where the x represents the name of the newly defined service interface, which is not limited in this application.
  • the service interface message includes the SUPI created by the RAN and the third message.
  • the first network element sends a response to the passive or semi-active IoT command to the passive or semi-active IoT server.
  • the first network element determines to use the second protocol to parse the message according to the second information included in the third message, such as "Nx_PIoT_Delivery" (the third message), and then obtains passive or semi- Response to Active IoT commands.
  • the first network element uses the first protocol to process the response of the passive or semi-active Internet of Things command, and generates a fourth message. Again, the first network element will send the fourth message to the passive or semi-active Internet of Things server, and the fourth message includes a response to the passive or semi-active Internet of Things command.
  • the passive or semi-active Internet of Things command and the response to the passive or semi-active Internet of Things command are transmitted through the control plane channel.
  • the message is related to passive or semi-active IoT operation, and the message needs to be processed using the second protocol.
  • the control plane network element (or network function) needs to forward the message to the first network element after learning the message from the RAN.
  • FIG. 13 is a schematic flowchart of another embodiment of a message transmission method proposed in the embodiment of the present application.
  • a message transmission method proposed in the embodiment of the present application includes:
  • the first network element subscribes to the AMF for a RAN generation control plane event.
  • the RAN completes the process of establishing a label or a control plane channel of the RAN.
  • the first network element receives an instruction from the passive or semi-active Internet of Things.
  • Steps 1301-1304 are similar to the foregoing steps 1201-1204, and will not be repeated here.
  • the SMF receives the first message from the first network element.
  • the first message includes the SUPI generated by the RAN, and the passive or semi-active Internet of Things instruction.
  • the second message is a service interface message, for example, the service interface message is "Nsmf_PIoT_Command".
  • the AMF receives the first packet from the SMF.
  • the SMF after receiving the first message, the SMF determines that the first message is related to the passive or semi-active Internet of Things. Therefore, the SMF needs to forward the passive or semi-active IoT instruction included in the first message to the AMF.
  • the SMF sends the first message to the AMF through the message Namf_Communication_N1N2MessageTransfer through the service interface.
  • the first message includes the SUPI created by the RAN, and a payload container (Payload container) or information type.
  • the container type included in the first message is N1 P-IoT (or N1 Passive IoT) transmission.
  • the container type included in the first packet is N2 P-IoT (or N2 Passive IoT) transmission.
  • the information type of the first packet can be "Passive IoT Information", “PIoT Information”, or "LLRP Information” and so on.
  • the above container type or information type indicates that the first packet is related to the passive or semi-active Internet of Things. It should be noted that the above-mentioned container types or information types are only illustrative, and do not limit the names of the container types or information types.
  • the container includes passive or semi-active Internet of Things instructions, that is, the second protocol encapsulates passive or semi-active Internet of Things instructions into the first message.
  • the AMF sends the first packet to the RAN.
  • the RAN determines that the first packet needs to be processed by using the second protocol.
  • the RAN processes the first packet by using the second protocol to obtain the first intermediate data.
  • the RAN performs a passive or semi-active IoT operation according to the first intermediate data, and acquires a response to a passive or semi-active IoT command.
  • the RAN sends a third packet to the AMF, where the third packet includes a response to the passive or semi-active Internet of Things command.
  • Steps 1307-1311 are similar to the aforementioned steps 1206-1210, and will not be repeated here.
  • the AMF sends the third message to the SMF.
  • the AMF may send the third message to the SMF through a service interface message.
  • the service interface message is "Nsmf_PIoT_report".
  • the service-based interface message indicates to the SMF that the message includes a response to a passive or semi-active Internet of Things command, and needs to be processed using the second protocol.
  • the third packet includes the second information, specifically, the third packet includes the second information.
  • the second information includes: the container type of the third packet, or the information type of the third packet.
  • the container type of the third message is: N1 P-IoT (or N1 Passive IoT) transmission.
  • the container type of the third message is N2 P-IoT (or N2 Passive IoT) transmission.
  • the information type of the third message may be "Passive IoT Information", "PIoT Information", or "LLRP Information” and so on.
  • the above container type or information type indicates that the third packet is related to the passive or semi-active Internet of Things, or that the third packet needs to be processed using the second protocol. It should be noted that the above-mentioned container types or information types are only illustrative, and do not limit the names of the container types or information types.
  • N1 P-IoT (or N1 Passive IoT) Transport container
  • N2 P-IoT (or N2 Passive IoT) Transport container
  • the second protocol encapsulates the response of the passive or semi-active Internet of Things command into the third message.
  • the third message includes a response to the passive or semi-active Internet of Things command.
  • the SMF sends the third packet to the first network element.
  • the SMF may send the third message to the first network element through a service interface message.
  • the service interface message is "Nx_RFID_report".
  • the service interface message indicates to the first network element that the message includes a third message (response to a passive or semi-active Internet of Things command), and needs to be processed using the second protocol.
  • the first network element sends a response to the passive or semi-active IoT command to the passive or semi-active IoT server.
  • the first network element uses the second protocol to parse the service interface message (third message) to obtain a response to the passive or semi-active Internet of Things command.
  • the first network element uses the first protocol to process the response of the passive or semi-active Internet of Things command, and generates a fourth message.
  • the first network element will send the fourth message to the passive or semi-active Internet of Things server, and the fourth message includes a response to the passive or semi-active Internet of Things command.
  • the passive or semi-active IoT command and the response to the passive or semi-active IoT command are transmitted through the control plane channel.
  • the message is related to passive or semi-active IoT operation, and the message needs to be processed using the second protocol.
  • the control plane network element (or network function) needs to forward the message to the first network element after learning the message from the RAN.
  • the communication device includes hardware structures and/or software modules corresponding to each function.
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software drives hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the present application.
  • the functional modules of the communication device may be divided according to the above method example.
  • each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module.
  • the above-mentioned integrated modules can be implemented in the form of hardware or in the form of software function modules. It should be noted that the division of modules in the embodiment of the present application is schematic, and is only a logical function division, and there may be other division methods in actual implementation.
  • FIG. 14 is a schematic diagram of an embodiment of a communication device in an embodiment of this application.
  • the communication device can be deployed in a network device (access network device), or a chip system, and the communication device 1400 includes: a transceiver module 1401 and a processing module 1402, wherein the communication device 1400 can be used in the access network shown in Figure 9b- Figure 13
  • the steps performed by the device reference may be made to relevant descriptions in the foregoing method embodiments.
  • the transceiver module 1401 is configured to receive the first message from the Internet of Things functional network element;
  • the transceiver module 1401 is also used to obtain first information, the first information indicates that the first message includes passive or semi-active Internet of Things instructions;
  • a processing module 1402 configured to perform passive or semi-active Internet of Things operations according to the first message.
  • the communication apparatus is a network device
  • the processing module 1402 may be a processor
  • the transceiver module 1401 may be a transceiver.
  • the network device is a chip, a chip system or a circuit configured in the network device.
  • the processing module 1402 may be a processor, a processing circuit, or a logic circuit.
  • the transceiver module 1401 may be an input and/or output interface, an interface circuit, an output circuit, an input circuit, a pin or a related circuit on the chip, a chip system or a circuit.
  • the above “receiving” can also be understood as "input”.
  • the first information includes one or more of the following: the message type of the first packet, the container type of the first packet, the tunnel identification information of the first packet, or the first information is Information type of the first packet.
  • the processing module 1402 is further configured to process the first message by using the second protocol according to the first information, and acquire passive or semi-active Internet of Things instructions.
  • the transceiver module 1401 is also used to obtain the response of the passive or semi-active Internet of Things command;
  • the processing module 1402 is further configured to use the second protocol to process the response of the passive or semi-active Internet of Things command, and generate a third message;
  • the transceiver module 1401 is further configured to send the third message to the Internet of Things functional network element.
  • the transceiver module 1401 is further configured to send second information to the Internet of Things functional network element, the second information indicates that the third message is related to the passive or semi-active Internet of Things, or the third message The text needs to be processed using the second protocol.
  • the second information includes one or more of the following: the message type of the third packet, the container type of the third packet, the tunnel identification information of the third packet, or the second information is The information type of the third message.
  • the transceiver module 1401 is further configured to send a request message, where the request message is used to establish the first session;
  • the session type of the first session is the passive or semi-active Internet of Things, or, the session identifier of the first session indicates that the first session is related to the passive or semi-active Internet of Things;
  • the transceiver module 1401 is further configured to receive the first message sent by the Internet of Things functional network element through the first session.
  • the transceiver module 1401 is further configured to send a third message to the Internet of Things functional network element through the first session.
  • the first information further includes a session type of the first session, or a session identifier of the first session.
  • the second information further includes a session type of the first session, or a session identifier of the first session.
  • the Internet of Things functional network element includes: a user plane function UPF, an access and mobility management function AMF, a session management function SMF, a network warehouse function NRF, or a first network element.
  • FIG. 15 is a schematic diagram of an embodiment of a communication device in an embodiment of this application.
  • the communication device 1500 can be deployed in a chip system, and the communication device 1500 includes: a transceiver module 1501 and a processing module 1502, wherein the communication device 1500 can be used for the steps performed by the Internet of Things functional units in Figure 9b- Figure 13, and can refer to the above method Related descriptions in the examples.
  • a transceiver module 1501 configured to send a first message to an access network device, where the first message includes a passive or semi-active Internet of Things instruction;
  • the transceiver module 1501 is also configured to send first information to the access network device, the first information indicates that the first message includes passive or semi-active IoT commands, enabling the access network device to execute passive or semi-active IoT commands. Network operation.
  • the transceiver module 1501 is also configured to receive the second message from the passive or semi-active IoT server;
  • the processing module 1502 is configured to generate a first message based on the second message, where the first message includes the passive or semi-active Internet of Things instruction included in the second message;
  • the transceiver module 1501 is further configured to send the first packet to the access network device.
  • the communication device is a network device
  • the processing module 1502 may be a processor
  • the transceiver module 1501 may be a transceiver.
  • the network device is a chip, a chip system or a circuit configured in the network device.
  • the processing module 1502 may be a processor, a processing circuit, or a logic circuit.
  • the transceiver module 1501 may be an input and/or output interface, an interface circuit, an output circuit, an input circuit, a pin or a related circuit on the chip, a chip system or a circuit.
  • the above “receiving” can also be understood as "input”.
  • the processing module 1502 is specifically configured to process the second packet by using the first protocol to generate the first intermediate data
  • the processing module 1502 is specifically configured to process the first intermediate data by using the second protocol, and generate the first message.
  • the transceiver module 1501 is specifically configured to send the second message to the first network element
  • the transceiver module 1501 is specifically configured to receive the second intermediate data sent by the first network element, where the second intermediate data is the data obtained by the first network element processing the second message by using the first protocol and the second protocol;
  • the processing module 1502 is specifically configured to process the second intermediate data and generate the first message.
  • the transceiver module 1501 is further configured to receive a third message from the access network device;
  • the transceiver module 1501 is further configured to obtain second information, the second information indicates that the third message is related to the passive or semi-active Internet of Things, or the third message needs to be processed using the second protocol;
  • the processing module 1502 is further configured to determine, according to the second information, to use the second protocol to process the third message, and generate a fourth message;
  • the third message and the fourth message include responses to passive or semi-active Internet of Things commands acquired by the access network device.
  • the processing module 1502 is further configured to generate the first message based on the first rule and/or the second rule based on the second message;
  • the first rule and/or the second rule are configured by the session management function SMF, or the first rule and/or the second rule are preconfigured in the user plane function.
  • the second rule includes: a packet forwarding rule
  • the first rule includes: a flow matching rule
  • the transceiver module 1501 is further configured to send a first message to the access network device through a first session, where the session type of the first session is passive or semi-active Internet of Things;
  • the session identifier of the first session indicates that the first session is related to the passive or semi-active Internet of Things.
  • the second information further includes a session type of the first session, or a session identifier of the first session.
  • the transceiver module 1501 is further configured to send a subscription request to the second network element, where the subscription request is used to obtain access network device information;
  • the access network device information includes one or more of the following information: the permanent identification of the access network device, the information of the core network element serving the access network device, and the reader identification information of the access network device;
  • the second network element includes one or more of the following: access and mobility management function AMF, session management function SMF, unified data management function UDM or network storage function NRF.
  • the Internet of Things functional network element includes: a user plane function UPF, an access and mobility management function AMF, a session management function SMF, a network warehouse function NRF, or a first network element.
  • the first information includes one or more of the following: the message type of the first packet, the container type of the first packet, the tunnel identification information of the first packet, or type of information.
  • the second information includes one or more of the following: the message type of the third packet, the container type of the third packet, the tunnel identification information of the third packet, or type of information.
  • An embodiment of the present application further provides a processing device, the processing device includes a processor and an interface; the processor is configured to execute a message transmission method in any one of the above method embodiments.
  • the above-mentioned processing device may be a chip, and the processor may be implemented by hardware or by software.
  • the processor When implemented by hardware, the processor may be a logic circuit, an integrated circuit, etc.; when implemented by software, the processor may be a general-purpose processor, and may be implemented by reading software codes stored in a memory.
  • the memory may be integrated in the processor, or may be located outside the processor and exist independently.
  • the hardware processing circuit can include ASIC (application-specific integrated circuit, application-specific integrated circuit), or PLD (programmable logic device, programmable logic device); wherein, PLD can include FPGA (field programmable gate array, field programmable gate array) , CPLD (complex programmable logic device, complex programmable logic device) and so on.
  • ASIC application-specific integrated circuit, application-specific integrated circuit
  • PLD programmable logic device, programmable logic device
  • FPGA field programmable gate array
  • CPLD complex programmable logic device, complex programmable logic device
  • These hardware processing circuits can be a semiconductor chip packaged separately (such as packaged into an ASIC); they can also be integrated with other circuits (such as CPU, DSP) and packaged into a semiconductor chip, for example, can be formed on a silicon base.
  • a variety of hardware circuits and CPUs are packaged separately into a chip.
  • This chip is also called SoC, or circuits and CPUs for realizing FPGA functions can also be formed on a silicon base, and separately sealed into a chip.
  • SoPC system on a programmable chip, programmable system on a chip.
  • the present application also provides a communication system, which includes at least one or more of the above communication devices.
  • An embodiment of the present application further provides a computer-readable storage medium, including instructions, which, when run on a computer, enable the computer to control the communication device to execute any implementation manner as shown in the foregoing method embodiments.
  • the embodiment of the present application also provides a computer program product, the computer program product includes computer program code, and when the computer program code is run on the computer, the computer is made to execute any one of the implementation manners shown in the foregoing method embodiments.
  • the embodiment of the present application also provides a chip system, including a memory and a processor, the memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that the chip performs any implementation as shown in the foregoing method embodiments Way.
  • the embodiment of the present application also provides a chip system, including a processor, and the processor is configured to call and run a computer program, so that the chip executes any one of the implementation manners shown in the foregoing method embodiments.
  • the device embodiments described above are only illustrative, and the units described as separate components may or may not be physically separated, and the components shown as units may or may not be A physical unit can be located in one place, or it can be distributed to multiple network units. Part or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • the connection relationship between modules indicates that they have communication connections, which can be implemented as one or more communication buses or signal lines.
  • the essence of the technical solution of this application or the part that contributes to the prior art can be embodied in the form of a software product, and the computer software product is stored in a readable storage medium, such as a floppy disk of a computer , U disk, mobile hard disk, ROM, RAM, magnetic disk or optical disk, etc., including several instructions to make a computer device execute the method described in each embodiment of the present application.
  • a readable storage medium such as a floppy disk of a computer , U disk, mobile hard disk, ROM, RAM, magnetic disk or optical disk, etc.
  • all or part of them may be implemented by software, hardware, firmware or any combination thereof.
  • software When implemented using software, it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website, computer, communication device, computing equipment or data center to another website site, computer, communication device, computing device or data center by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) transmission.
  • wired such as coaxial cable, optical fiber, digital subscriber line (DSL)
  • wireless such as infrared, wireless, microwave, etc.
  • the computer-readable storage medium may be any available medium that can be stored by a computer, or a data storage device such as a communication device or a data center integrated with one or more available media.
  • the available medium may be a magnetic medium (such as a floppy disk, a hard disk, or a magnetic tape), an optical medium (such as a DVD), or a semiconductor medium (such as a solid state disk (Solid State Disk, SSD)), etc.
  • the disclosed system, device and method can be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components can be combined or integrated. to another system, or some features may be ignored, or not implemented.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.
  • a unit described as a separate component may or may not be physically separated, and a component displayed as a unit may or may not be a physical unit, that is, it may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit.
  • the above-mentioned integrated units can be implemented in the form of hardware or in the form of software functional units.
  • the integrated unit is realized in the form of a software function unit and sold or used as an independent product, it can be stored in a computer-readable storage medium.
  • the technical solution of the present application is essentially or part of the contribution to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , including several instructions to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods in various embodiments of the present application.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Health & Medical Sciences (AREA)
  • Computing Systems (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Telephonic Communication Services (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请实施例公开一种报文传输方法以及相关装置，该方法包括：接入网设备从物联网功能网元接收第一报文；接入网设备获取第一信息，第一信息指示第一报文包括无源或半有源物联网指令；接入网设备根据第一报文执行无源或半有源物联网操作。通过上述方法，接入网设备获知来自物联网功能网元的报文与无源或半有源物联网有关，接入网设备根据该第一报文执行无源或半有源物联网操作。解决了无源或半有源物联网系统与蜂窝网络融合的场景中报文传输的问题。

Description

一种报文传输方法以及相关装置 技术领域
本申请涉及通信技术领域，尤其涉及一种报文传输方法以及相关装置。
背景技术
无源或半有源物联网技术是自动识别技术的一种。读写器(Reader)通过无线射频方式进行非接触双向数据通信，利用无线射频方式对电子标签或射频卡(Tag)进行读写，从而达到识别目标和数据交换的目的。
无源或半有源物联网系统包含无源或半有源物联网标签和无源或半有源物联网读写器(reader)；可选的，无源或半有源物联网系统还可以包括中间件(Filtering&Collection)和服务器。无源或半有源物联网读写器与中间件是采用低级别读写器协议(low level reader protocol，LLRP)。而中间件与服务器之间的协议为应用层事件(application level event，ALE)。
为了节约成本，可以使用蜂窝网络支持无源或半有源物联网的应用。在这种情况下，蜂窝网络需要融合无源或半有源物联网技术(或无源或半有源物联网网络架构)。
发明内容
本申请实施例提供一种报文传输方法以及相关装置，使得蜂窝网络能够支持无源或半有源物联网的应用报文的处理。
第一方面，提供一种报文传输方法，包括：接入网设备从物联网功能网元接收第一报文；接入网设备获取第一信息，第一信息指示第一报文包括无源或半有源物联网指令；接入网设备根据第一报文执行无源或半有源物联网操作。
具体的，第一信息可以由物联网功能网元向接入网设备发送，该第一信息还可以由接入网设备从物联网功能网元获取或者该第一信息可以由接入网设备从上下文信息中获取，此处不做限制。可选的，第一报文中可以包括该第一信息，第一报文也可以与该第一信息相互独立，此处不作限制。
需要说明的是，本申请实施例中的报文也可以称为数据包、信令、或指令等，此处不作限制。
本申请实施例中，接入网设备从物联网功能网元获取(或者接入网设备从上下文信息中获取)第一信息，第一信息指示第一报文包括无源或半有源物联网指令。通过上述方法，接入网设备获知来自物联网功能网元的报文与无源或半有源物联网有关，接入网设备根据该第一报文执行无源或半有源物联网操作。解决了无源或半有源物联网系统与蜂窝网络融合的场景中报文传输的问题。使得蜂窝网络可以解析无源或半有源物联网的应用报文并根据该应用报文执行相关操作。
结合第一方面，在第一方面的一种可能的实现方式中，第一信息包括以下一项或多项：第一报文的消息类型，第一报文中的容器类型，第一报文中的隧道标识信息，或者第一信息为第一报文的信息类型，第一会话的会话类型，或者，所述第一会话的会话标识，其中，所述第一会话用于传输所述第一报文，所述第一会话的会话类型为无源或半有源物联网， 所述第一会话的会话标识指示所述第一会话与无源或半有源物联网有关。
具体的，第一报文的消息类型可以是第一报文的报文头中的消息类型字段；第一报文的容器类型可以是第一报文中新增的容器类型；第一报文的隧道标识信息指的是接入网设备RAN关于第一会话的隧道标识信息，即RAN建立第一会话时N3隧道的端点标识，物联网功能网元通过该隧道标识信息确定第一会话的会话类型；第一报文的信息类型指的是第一报文中新增的指示该第一报文的信息类型字段。本申请实施例提供了第一信息的多种实现方案，提升了方案的实现灵活性。
结合第一方面，在第一方面的一种可能的实现方式中，接入网设备根据第一信息，采用第二协议处理第一报文，获取无源或半有源物联网指令。一种可能的实现方式中，该第二协议为低级别读写器协议(low level reader protocol，LLRP)。该无源或半有源物联网指令包括：事件周期规格指令(event cycle specification，ECSpecs)或命令周期规格(command cycle specification，CCSpecs)，其中，该事件周期规格指令或命令周期规格指令包括了需要盘点的标签范围，或者需要执行读操作或写操作的标签范围。
结合第一方面，在第一方面的一种可能的实现方式中，接入网设备获取无源或半有源物联网指令的响应；接入网设备采用第二协议处理无源或半有源物联网指令的响应，生成第三报文；接入网设备向物联网功能网元发送第三报文。
具体的，RAN根据第一中间数据中包括的无源或半有源物联网指令，执行无源或半有源物联网操作，并获取无源或半有源物联网指令的响应。示例性的，该无源或半有源物联网操作包括但不限于：标签读写操作，标签盘点操作等。该无源或半有源物联网指令的响应包括但不限于：标签的读数据，或者标签的盘点操作结果等。RAN采用第二协议对无源或半有源物联网指令的响应进行处理，得到第三报文。具体的，首先，RAN对该无源或半有源物联网指令的响应进行处理，得到包括该无源或半有源物联网指令的响应的消息报文。其次，RAN对该消息报文进行进一步封装处理，得到第三报文。该第三报文包括该无源或半有源物联网指令的响应。
本申请实施例中，通过上述方法，接入网设通知物联网功能网元该第三报文与无源或半有源物联网有关，物联网功能网元根据该第三报文获取无源或半有源物联网指令的响应。解决了无源或半有源物联网系统与蜂窝网络融合的场景中，报文传输的问题。
结合第一方面，在第一方面的一种可能的实现方式中，接入网设备向物联网功能网元发送第二信息，第二信息指示第三报文与无源或半有源物联网有关，或者第三报文需要使用第二协议进行处理。
具体的，本申请实施例中，将指示第三报文包括与无源或半有源物联网有关，或者第三报文需要使用第二协议进行处理的信息称为第二信息。第二信息可以由接入网设备向物联网功能网元发送，该第二信息还可以由物联网功能网元从接入网设备获取，此处不做限制。可选的，第三报文中可以包括该第二信息，第三报文也可以与该第二信息相互独立，此处不作限制。进一步的，第二信息包括以下一项或多项：第三报文的消息类型，第三报文的容器类型，第三报文的隧道标识信息，或者第二信息为第三报文的信息类型。
本申请实施例中，接入网设备通过第二信息通知物联网功能网元，该第三报文与无源 或半有源物联网有关，以便物联网功能网元高效处理该第三报文。本申请实施例提供了第二信息的多种实现方案，提升了方案的实现灵活性。
结合第一方面，在第一方面的一种可能的实现方式中，第二信息包括以下一项或多项：第三报文的消息类型，第三报文中的容器类型，第三报文中的隧道标识信息，第二信息为第三报文的信息类型，或者第三报文的信息类型，第一会话的会话类型，或者，所述第一会话的会话标识，其中，所述第一会话用于传输所述第一报文，所述第一会话的会话类型为无源或半有源物联网，所述第一会话的会话标识指示所述第一会话与无源或半有源物联网有关。
具体的，第三报文的消息类型可以是第三报文的报文头中的消息类型字段；第三报文的容器类型可以是第三报文中新增的容器类型；第三报文的隧道标识信息指的是RAN关于第一会话的隧道标识信息，即RAN建立第一会话时N3隧道的端点标识，物联网功能网元通过该隧道标识信息确定第一会话的会话类型；第三报文的信息类型指的是第三报文中新增的指示该第三报文的信息类型字段。本申请实施例提供了第二信息的多种实现方案，提升了方案的实现灵活性。
结合第一方面，在第一方面的一种可能的实现方式中，接入网设备从物联网功能网元接收第一报文，包括：接入网设备发送请求消息，请求消息用于建立第一会话；第一会话的会话类型为无源或半有源物联网，或者，第一会话的会话标识指示第一会话与无源或半有源物联网有关；接入网设备通过第一会话接收物联网功能网元发送的第一报文。
示例性的，该请求消息为RAN向AMF发送协议数据单元(Protocol Data Unit，PDU)会话建立请求消息(PDU session establishment request)。该PDU会话建立请求消息用于建立第一会话。第一会话的会话类型为无源或半有源物联网，或者，第一会话的会话标识指示第一会话与无源或半有源物联网有关。
可选的，该PDU会话建立请求消息中包括PDU会话类型信息，该PDU会话类型信息指示该第一会话的会话类型为无源或半有源物联网，或者，该PDU会话类型信息指示第一会话传输无源或半有源物联网相关的数据。
可选的，RAN在该PDU会话建立的过程中，向AMF发送该第一会话的会话类型。具体的，该第一会话的会话类型也称为PDU会话类型信息。AMF通过多种方式获取该PDU会话类型信息，示例性的，RAN通过非接入层NAS消息向AMF发送该PDU会话类型信息，或者RAN通过N2消息向AMF发送该PDU会话类型信息。或者，AMF从该RAN的签约数据中获取该PDU会话类型信息。或者，AMF从AMF自身存储的数据中获取该PDU会话类型信息。此处不作限制。第一会话可以用于传输物联网功能网元向RAN发送的第一报文，提升了方案的实现灵活性。
结合第一方面，在第一方面的一种可能的实现方式中，接入网设备通过第一会话向物联网功能网元发送第三报文。第一会话还可以用于传输RAN向物联网功能网元发送的第三报文，提升了方案的实现灵活性。
结合第一方面，在第一方面的一种可能的实现方式中，第一信息还包括第一会话的会话类型，或者，第一会话的会话标识。本申请实施例中，接入网设备可以根据第一会话的 会话类型，或者，第一会话的会话标识确定第一会话中传输的第一报文包括无源或半有源物联网指令。
结合第一方面，在第一方面的一种可能的实现方式中，第二信息还包括第一会话的会话类型，或者，第一会话的会话标识。本申请实施例中，接入网设备可以根据第一会话的会话类型，或者，第一会话的会话标识确定第一会话中传输的第三报文与无源或半有源物联网有关。
结合第一方面，在第一方面的一种可能的实现方式中，物联网功能网元包括：用户面功能UPF、接入和移动性管理功能AMF、会话管理功能SMF、网络仓储功能NRF或者第一网元。
第二方面，本申请实施例提出一种报文传输方法，包括：物联网功能网元向接入网设备发送第一报文，第一报文包括无源或半有源物联网指令；物联网功能网元向接入网设备发送第一信息，第一信息指示第一报文包括无源或半有源物联网指令，使能接入网设备执行无源或半有源物联网操作。
具体的，第一信息可以由物联网功能网元向接入网设备发送，该第一信息还可以由接入网设备从物联网功能网元获取或者该第一信息可以由接入网设备从上下文信息中获取，此处不做限制。可选的，第一报文中可以包括该第一信息，第一报文也可以与该第一信息相互独立，此处不作限制。
本申请实施例中，首先，接入网设备接收物联网功能网元发送的第一报文。其次，接入网设备获取第一信息。具体的，接入网设备从第一报文中获取该第一信息，即第一报文包括第一信息；或者，接入网设备从物联网功能网元或者其它网元中获取该第一信息，例如：接入网设备从物联网功能网元获取(或者接入网设备从上下文信息中获取)传输该第一报文的第一会话的相关信息(包括第一会话的会话标识或者第一会话的会话类型)，第一信息为该第一会话的相关信息。通过上述方法，接入网设备获知来自物联网功能网元的报文与无源或半有源物联网有关，接入网设备根据该第一报文执行无源或半有源物联网操作。解决了无源或半有源物联网系统与蜂窝网络融合的场景中，报文传输的问题。使得蜂窝网络可以解析无源或半有源物联网的应用报文，并可以根据该应用报文执行相关操作。
结合第二方面，在第二方面的一种可能的实现方式中，物联网功能网元包括：用户面功能UPF、接入和移动性管理功能AMF、会话管理功能SMF、网络仓储功能NRF或者第一网元。
结合第二方面，在第二方面的一种可能的实现方式中，物联网功能网元从无源或半有源物联网服务器接收第二报文；物联网功能网元基于第二报文，生成第一报文，第一报文包括第二报文包括的无源或半有源物联网指令；物联网功能网元向接入网设备发送第一报文。具体的，物联网功能网元根据该第二报文的报文头确定该第二报文来自无源或半有源物联网服务器。或者，物联网功能网元传输第二报文的会话的相关标识，确定第二报文是否来自无源或半有源物联网服务器。物联网功能网元在确定第二报文来自无源或半有源物联网服务器后，确定该第二报文中包括无源或半有源物联网指令。因此，物联网功能网元基于该第二报文生成第一报文，以保证接入网设备获取该无源或半有源物联网指令。
结合第二方面，在第二方面的一种可能的实现方式中，物联网功能网元采用第一协议处理第二报文，生成第一中间数据；物联网功能网元采用第二协议处理第一中间数据，生成第一报文。具体的，物联网功能网元采用第一协议处理(或者称为：解析)第二报文，处理得到的数据称为第一中间数据。其次，物联网功能网元采用第二协议处理第一中间数据，生成第一报文。一种可能的实现方式中，该第一协议为应用层事件(Application Level Event，ALE)协议。一种可能的实现方式中，该第二协议为低级别读写器协议(Low Level Reader Protocol，LLRP)。物联网功能网元自身可以处理该第二报文，并生成第一报文，提升了方案的实现灵活性。
结合第二方面，在第二方面的一种可能的实现方式中，物联网功能网元向第一网元发送第二报文；物联网功能网元接收第一网元发送的第二中间数据，第二中间数据为第一网元采用第一协议和第二协议处理第二报文得到的数据；物联网功能网元处理第二中间数据，生成第一报文。物联网功能网元可以与其它的网元(例如第一网元)协同处理该第二报文，并生成第一报文，提升了方案的实现灵活性。
结合第二方面，在第二方面的一种可能的实现方式中，物联网功能网元接收来自接入网设备的第三报文；物联网功能网元获取第二信息，第二信息指示第三报文与无源或半有源物联网有关，或者第三报文需要使用第二协议进行处理；物联网功能网元根据第二信息，采用第二协议处理第三报文，生成第四报文；第三报文和第四报文包括接入网设备获取的无源或半有源物联网指令的响应。
本实施例中，该第三报文为第一报文的响应。物联网功能网元接收该第三报文后，根据第二信息(例如该第三报文的消息类型，或者第三报文的报文头)确定第三报文需要采用第二协议进行处理。在又一种可能的实现方式中，物联网功能网元接收该第三报文后，根据第一会话的标识信息第一会话的会话标识，或者第一会话的会话类型，确定第一会话中传输的第三报文包括无源或半有源物联网指令的响应。进而物联网功能网元确定该第三报文需要采用第二协议进行处理。示例性的，以第二协议为LLRP协议为例。首先，物联网功能网元使用LLRP协议处理(又称为解析)该第三报文，获取无源或半有源物联网指令的响应。其次，物联网功能网元使用第一协议(例如ALE协议)处理该无源或半有源物联网指令的响应，生成第四报文。物联网功能网元可以向无源或半有源物联网服务器发送该第四报文。该第四报文携带包括无源或半有源物联网指令的响应。物联网功能网元根据第二信息，可以高效识别第三报文中携带无源或半有源物联网指令的响应，并采用第二协议处理第三报文，生成第四报文。物联网功能网元向无源或半有源物联网服务器发送该第四报文，提高无源或半有源物联网系统的工作效率。
结合第二方面，在第二方面的一种可能的实现方式中，物联网功能网元为用户面功能，用户面功能基于第二报文，生成第一报文，包括：用户面功能根据第一规则和/或第二规则基于第二报文，生成第一报文；第一规则和/或第二规则由会话管理功能SMF配置或者第一规则和/或第二规则预配置于用户面功能。具体的，用户面功能根据第一规则和/或第二规则基于第二报文，生成第一报文，包括：用户面功能根据第一规则确定第二报文的来源；用户面功能根据第二规则对来自无源或半有源物联网服务器的该第二报文进行处理，生成 第一报文。
第一规则指示物联网功能网元如何确定接收的报文是否来自无源或半有源物联网服务器。该第二规则指示物联网功能网元对来自无源或半有源物联网服务器的报文如何处理。即指示物联网功能网元处理该第二报文需要使用的协议类型。可选的，第二规则包括：报文转发规则(Forwarding Action Rule，FAR)，第一规则包括：流匹配规则(Packet Detection Rule，PDR)。进一步的，该第一规则和/或第二规则可以是增强的N4规则。该增强的N4规则与无源或半有源物联网服务相关。该第一规则可以包括：增强的FAR规则，该第二规则包括：增强的PDR规则。通过配置第一规则和/或第二规则，使得用户面功能可以根据第一规则和/或第二规则确定第二报文的来源、处理第二报文并生成第一报文，提升了方案的适用范围。
结合第二方面，在第二方面的一种可能的实现方式中，物联网功能网元通过第一会话向接入网设备发送第一报文，第一会话的会话类型为无源或半有源物联网，或者，第一会话的会话标识指示第一会话与无源或半有源物联网有关。第一会话可以用于传输物联网功能网元向RAN发送的第一报文，提升了方案的实现灵活性。
结合第二方面，在第二方面的一种可能的实现方式中，第二信息还包括第一会话的会话类型，或者，第一会话的会话标识。本申请实施例中，物联网功能网元可以根据第一会话的会话类型，或者，第一会话的会话标识确定第一会话中传输的第一报文包括无源或半有源物联网指令。
结合第二方面，在第二方面的一种可能的实现方式中，物联网功能网元向第二网元发送订阅请求，订阅请求用于获取接入网设备信息；接入网设备信息包括以下信息中的一项或多项：接入网设备的永久标识，服务接入网设备的核心网网元的信息，和接入网设备的读写器标识信息；第二网元包括以下一个或多个：接入与移动管理功能AMF、会话管理功能SMF、统一数据管理功能UDM或者网络仓储功能NRF。通过该步骤，每当有RAN代理标签建立以RAN为粒度或者以标签为粒度的控制面通道后，物联网功能网元就可以通过第二网元上报的事件来获取哪个RAN代理建立(简称为代建)了控制面通道，以及该RAN代建的SUPI信息等。后续无源或半有源物联网服务器向物联网功能网元发送无源或半有源物联网指令(或者信息，或者数据)时，以便负责转发报文的网元(或网络功能，例如NEF、AMF、UDM或SMF)获知报文的目的地，即该报文需要发送至什么RAN。
结合第二方面，在第二方面的一种可能的实现方式中，第一信息包括以下一项或多项：第一报文的消息类型，第一报文中的容器类型，第一报文中的隧道标识信息，或者第一信息为第一报文的信息类型。
具体的，第一报文的消息类型可以是第一报文的报文头中的消息类型字段；第一报文的容器类型可以是第一报文中新增的容器类型；第一报文的隧道标识信息指的是RAN关于第一会话的隧道标识信息，即RAN建立第一会话时N3隧道的端点标识，物联网功能网元通过该隧道标识信息确定第一会话的会话类型；第一报文的信息类型指的是第一报文中新增的指示该第一报文的信息类型字段。本申请实施例提供了第一信息的多种实现方案，提升了方案的实现灵活性。
结合第二方面，在第二方面的一种可能的实现方式中，第二信息包括以下一项或多项：第三报文的消息类型，第三报文中的容器类型，第三报文中的隧道标识信息，或者第三报文的信息类型。具体的，第三报文的消息类型可以是第三报文的报文头中的消息类型字段；第三报文的容器类型可以是第三报文中新增的容器类型；第三报文的隧道标识信息指的是RAN关于第一会话的隧道标识信息，即RAN建立第一会话时N3隧道的端点标识，物联网功能网元通过该隧道标识信息确定第一会话的会话类型；第三报文的信息类型指的是第三报文中新增的指示该第三报文的信息类型字段。本申请实施例提供了第二信息的多种实现方案，提升了方案的实现灵活性。
第三方面，本申请实施例提出一种通信装置，包括：
收发模块，用于从物联网功能网元接收第一报文；
收发模块，还用于获取第一信息，第一信息指示第一报文包括无源或半有源物联网指令；
处理模块，用于根据第一报文执行无源或半有源物联网操作。
在一种实现方式中，该通信装置为网络设备，在一种实现方式中，所述处理模块可以是处理器，所述收发模块可以是收发器。
在另一种实现方式中，该网络设备为配置于网络设备中的芯片、芯片系统或电路。所述处理模块可以是处理器、处理电路或逻辑电路等。所述收发模块可以是该芯片、芯片系统或电路上的输入和/或输出接口、接口电路、输出电路、输入电路、管脚或相关电路等。可选的，上述“接收”还可以理解为“输入”。
在一种可能的实现方式中，第一信息包括以下一项或多项：第一报文的消息类型，第一报文的容器类型，第一报文的隧道标识信息，或者第一信息为第一报文的信息类型。
在一种可能的实现方式中，处理模块，还用于根据第一信息，采用第二协议处理第一报文，获取无源或半有源物联网指令。
在一种可能的实现方式中，收发模块，还用于获取无源或半有源物联网指令的响应；
处理模块，还用于采用第二协议处理无源或半有源物联网指令的响应，生成第三报文；
收发模块，还用于向物联网功能网元发送第三报文。
在一种可能的实现方式中，收发模块，还用于向物联网功能网元发送第二信息，第二信息指示第三报文与无源或半有源物联网有关，或者第三报文需要使用第二协议进行处理。
在一种可能的实现方式中，第二信息包括以下一项或多项：第三报文的消息类型，第三报文的容器类型，第三报文的隧道标识信息，或者第二信息为第三报文的信息类型。
在一种可能的实现方式中，收发模块，还用于发送请求消息，请求消息用于建立第一会话；
第一会话的会话类型为无源或半有源物联网，或者，第一会话的会话标识指示第一会话与无源或半有源物联网有关；
收发模块，还用于通过第一会话接收物联网功能网元发送的第一报文。
在一种可能的实现方式中，收发模块，还用于通过第一会话向物联网功能网元发送第三报文。
在一种可能的实现方式中，第一信息还包括第一会话的会话类型，或者，第一会话的会话标识。
在一种可能的实现方式中，第二信息还包括第一会话的会话类型，或者，第一会话的会话标识。
在一种可能的实现方式中，物联网功能网元包括：用户面功能UPF、接入和移动性管理功能AMF、会话管理功能SMF、网络仓储功能NRF或者第一网元。
第四方面，本申请实施例提出一种通信装置，包括：
收发模块，用于向接入网设备发送第一报文，第一报文包括无源或半有源物联网指令；
收发模块，还用于向接入网设备发送第一信息，第一信息指示第一报文包括无源或半有源物联网指令，使能接入网设备执行无源或半有源物联网操作。
在一种可能的实现方式中，收发模块，还用于从无源或半有源物联网服务器接收第二报文；
处理模块，用于基于第二报文，生成第一报文，第一报文包括第二报文包括的无源或半有源物联网指令；
收发模块，还用于向接入网设备发送第一报文。
在一种实现方式中，该通信装置为网络设备，在一种实现方式中，所述处理模块可以是处理器，所述收发模块可以是收发器。
在另一种实现方式中，该网络设备为配置于网络设备中的芯片、芯片系统或电路。所述处理模块可以是处理器、处理电路或逻辑电路等。所述收发模块可以是该芯片、芯片系统或电路上的输入和/或输出接口、接口电路、输出电路、输入电路、管脚或相关电路等。可选的，上述“接收”还可以理解为“输入”。
在一种可能的实现方式中，处理模块，具体用于采用第一协议处理第二报文，生成第一中间数据；
处理模块，具体用于采用第二协议处理第一中间数据，生成第一报文。
在一种可能的实现方式中，收发模块，具体用于向第一网元发送第二报文；
收发模块，具体用于接收第一网元发送的第二中间数据，第二中间数据为第一网元采用第一协议和第二协议处理第二报文得到的数据；
处理模块，具体用于处理第二中间数据，生成第一报文。
在一种可能的实现方式中，收发模块，还用于接收来自接入网设备的第三报文；
收发模块，还用于获取第二信息，第二信息指示第三报文与无源或半有源物联网有关，或者第三报文需要使用第二协议进行处理；
处理模块，还用于根据第二信息，确定采用第二协议处理第三报文，生成第四报文；
第三报文和第四报文包括接入网设备获取的无源或半有源物联网指令的响应。
在一种可能的实现方式中，处理模块，还用于根据第一规则和/或第二规则基于第二报文，生成第一报文；
第一规则和/或第二规则由会话管理功能SMF配置，或者第一规则和/或第二规则预配置于用户面功能。
在一种可能的实现方式中，第二规则包括：报文转发规则，第一规则包括：流匹配规则。
在一种可能的实现方式中，收发模块，还用于通过第一会话向接入网设备发送第一报文，第一会话的会话类型为无源或半有源物联网；
或者，第一会话的会话标识指示第一会话与无源或半有源物联网有关。
在一种可能的实现方式中，第二信息还包括第一会话的会话类型，或者，第一会话的会话标识。
在一种可能的实现方式中，收发模块，还用于向第二网元发送订阅请求，订阅请求用于获取接入网设备信息；
接入网设备信息包括以下信息中的一项或多项：接入网设备的永久标识，服务接入网设备的核心网网元的信息，和接入网设备的读写器标识信息；
第二网元包括以下一个或多个：接入与移动管理功能AMF、会话管理功能SMF、统一数据管理功能UDM或者网络仓储功能NRF。
在一种可能的实现方式中，物联网功能网元包括：用户面功能UPF、接入和移动性管理功能AMF、会话管理功能SMF、网络仓储功能NRF或者第一网元。
在一种可能的实现方式中，第一信息包括以下一项或多项：第一报文的消息类型，第一报文的容器类型，第一报文的隧道标识信息，或者第一报文的信息类型。
在一种可能的实现方式中，第二信息包括以下一项或多项：第三报文的消息类型，第三报文的容器类型，第三报文的隧道标识信息，或者第三报文的信息类型。
第五方面，提供了一种通信装置用于实现上述各种方法。该通信装置可以为上述第一方面或第一方面的任一种可能的实现方式第二方面或第二方面的任一种可能的实现方式中的通信装置，或者是上述通信装置中包含的装置，比如系统芯片。该第五方面提供的通信装置包括实现上述方法相应的模块、单元、或手段(means)，该模块、单元、或means可以通过硬件实现，软件实现，或者通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块或单元。
第六方面，提供了一种通信装置，包括：处理器和存储器；该存储器用于存储计算机指令，当该处理器执行该指令时，以使该通信装置执行上述任一方面的方法。该通信装置可以为上述第一方面或第一方面的任一种可能的实现方式、或者第二方面或第二方面的任一种可能的实现方式中的通信装置，或者包含上述通信装置的装置，或者上述通信装置中包含的装置，比如系统芯片。
第七方面，提供了一种通信装置，包括：处理器；处理器用于与存储器耦合，并读取存储器中的指令之后，根据指令执行如上述任一方面的方法，该存储器与该通信装置相互独立。该通信装置可以为上述第一方面或第一方面的任一种可能的实现方式、或者第二方面或第二方面的任一种可能的实现方式中的通信装置，或者包含上述通信装置的装置，或者上述通信装置中包含的装置，比如系统芯片。
第八方面，提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当指令在通信装置上运行时，使得通信装置可以执行上述任一方面的方法。该通信装置可 以为上述第一方面或第一方面的任一种可能的实现方式、或者第二方面或第二方面的任一种可能的实现方式中的通信装置，或者包含上述通信装置的装置，或者上述通信装置中包含的装置，比如系统芯片。
第九方面，提供了一种包含指令的计算机程序产品，当指令在通信装置上运行时，使得通信装置可以执行上述任一方面的方法。该通信装置可以为上述第一方面或第一方面的任一种可能的实现方式、或者第二方面或第二方面的任一种可能的实现方式中的通信装置，或者包含上述通信装置的装置，或者上述通信装置中包含的装置，比如系统芯片。
第十方面，提供了一种通信装置(例如，该通信装置可以是芯片或芯片系统)，该通信装置包括处理器，用于实现上述任一方面中所涉及的功能。在一种可能的设计中，该通信装置还包括存储器，该存储器，用于保存必要的程序指令和数据。该通信装置是芯片系统时，可以由芯片构成，也可以包含芯片和其他分立器件。
第十一方面，提供了一种芯片，该芯片包括处理器和通信接口，该通信接口用于与所示芯片之外的模块通信，该处理器用于运行计算机程序或指令，使得安装该芯片的装置可以执行上述任一方面的方法。
其中，第三方面至第十一方面中任一种设计方式所带来的技术效果可参见上述第一方面或第二方面中不同设计方式所带来的技术效果，此处不再赘述。
第十二方面，提供一种通信系统，该通信系统包括上述方面的通信装置。
附图说明
图1a为本申请实施例涉及的一种无源或半有源物联网系统示意图；
图1b为本申请实施例中RFID系统的一种示意图；
图1c为一种通信系统的网络架构示意图；
图2为本申请实施例中通信装置的硬件结构示意图；
图3为本申请实施例中标签盘点的流程示意图；
图4为本申请实施例中标签读写的流程示意图；
图5为本申请实施例中一种无源或半有源物联网架构示意图；
图6为本申请实施例中又一种无源或半有源物联网架构示意图；
图7a-7b为本申请实施例中又一种无源或半有源物联网架构示意图；
图8为本申请实施例中RAN代理建立控制面通道的流程示意图；
图9a为本申请实施例中RAN代理建立会话流程的流程示意图；
图9b为本申请实施例提出的一种报文传输方法的实施例流程示意图；
图10a为本申请实施例提出的一种报文传输方法的实施例流程示意图；
图10b为本申请实施例提出的一种应用场景中的报文传输方法的流程示意图；
图10c为本申请实施例提出的一种应用场景中的报文传输方法的流程示意图；
图11为本申请实施例提出的一种报文传输方法的实施例流程示意图；
图12为本申请实施例提出的一种报文传输方法的又一种实施例流程示意图；
图13为本申请实施例提出的一种报文传输方法的又一种实施例流程示意图；
图14为本申请实施例中通信装置的一种实施例示意图；
图15为本申请实施例中通信装置的一种实施例示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述。显然，所描述的实施例仅仅是本申请一部分实施例，而不是全部的实施例。
本申请的说明书和权利要求书及上述附图中的术语“第一”、第二”以及相应术语标号等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的术语在适当情况下可以互换，这仅仅是描述本申请的实施例中对相同属性的对象在描述时所采用的区分方式。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，以便包含一系列单元的过程、方法、系统、产品或设备不必限于那些单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它单元。
在本申请的描述中，除非另有说明，“/”表示或的意思，例如，A/B可以表示A或B；本申请中的“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，在本申请的描述中，“至少一项”是指一项或者多项，“多项”是指两项或两项以上。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a,b,或c中的至少一项(个)，可以表示：a,b,c,a-b,a-c,b-c,或a-b-c，其中a,b,c可以是单个，也可以是多个。
本申请实施例的技术方案可以应用于各种通信系统，例如：宽带码分多址(Wideband Code Division Multiple Access，WCDMA)系统，通用分组无线业务(general packet radio service，GPRS)，长期演进(Long Term Evolution，LTE)系统，LTE频分双工(frequency division duplex，FDD)系统，LTE时分双工(time division duplex，TDD)，通用移动通信系统(universal mobile telecommunication system，UMTS)，全球互联微波接入(worldwide interoperability for microwave access，WiMAX)通信系统，第五代(5th generation，5G)系统或NR以及第六代通信系统等。
通信网络可以为公用陆地移动网(public land mobile network，PLMN)网络，是由政府或政府所批准的经营者，以为公众提供陆地移动通信业务为目的而建立和经营的网络，主要是移动网络运营商(mobile network operator，MNO)为用户提供移动宽带接入服务的公共网络；也可以为企业网络，即为企业自建、企业控制或企业管理的网络。本申请实施例中所描述的通信网络，可以为符合第三代合作伙伴项目(3rd generation partnership project，3GPP)标准要求的网络，简称3GPP网络，包括但不限于第五代移动通信(5th-generation，5G)网络(简称5G网络)，第四代移动通信(4th-generation，4G)网络(简称4G网络)或第三代移动通信技术(3rd-generation，3G)网络(简称3G网络)。还包括6G网络。
为了便于理解本申请实施例，首先介绍图1a所示的无源或半有源物联网系统，图1a为本申请实施例涉及的一种无源或半有源物联网系统示意图。本申请实施例中的无源或半 有源物联网系统可以看做无线射频识别系统，或者射频识别技术(Radio Frequency Identification，RFID)系统。需要说明的是，本申请实施例中的RFID系统仅是本申请实施例中无源或半有源物联网系统的一种示例，本申请实施例中的无源或半有源物联网系统并不局限于RFID系统。随着技术的发展，“无源或半有源物联网”的名称也可能发生变化，本申请实施例中涉及的“无源或半有源物联网”，也可以是未来通信系统中具有上述“无源或半有源物联网”结构或功能的系统(或通信技术)。
RFID是自动识别技术的一种。读写器(Reader)通过无线射频方式进行非接触双向数据通信，利用无线射频方式对电子标签或射频卡(Tag)进行读写，从而达到识别目标和数据交换的目的。它的工作方式有两种情况，一种就是当RFID标签进入读写器有效识别范围内时，接收读写器发出的射频信号，凭借感应电流所获得能量发出存储在芯片中的信息(对应于无源Tag)；另一种就是由RFID标签主动发送某一频率的信号(对应于有源Tag)，读写器接收信息并解码后，由RFID信息服务系统或后端应用系统进行有关数据处理。该技术广泛应用于各行业领域，下面简单介绍两种应用场景。
(1)、物流应用场景。
货品嵌入RFID标签。当货品在物流过程中，货品相关信息被读写器自动采集，管理人员就可以在系统迅速查询货品信息，降低丢弃或者被盗的风险，可以提高货品交接速度，提高准确率，并且实现防伪和防止窜货。
(2)、固定资产管理。
在储存有贵重物品的场所，例如：图书馆、艺术馆与博物馆等地点。在这些贵重物品上设置RFID标签。管理人员可以通过对RFID标签的监测，第一时间获知这些贵重物品的存放位置信息是否发生异常变动。
产品电子代码(Electronic Product Code，EPC)标准组织定义了RFID系统架构，具体的，请参阅图1b，图1b为本申请实施例中RFID系统的一种示意图。RFID系统包括：标签、读写器、中间件和服务器。标签(Gen 2RFID Tag)与读写器(RFID Reader)之间是采用空口协议(例如：Gen 2Air Interface协议)进行通信；而读写器与中间件(Filtering&Collection)是采用低级别读写器协议(Low Level Reader Protocol，LLRP)。而中间件与服务器之间的协议为应用层事件(Application Level Event，ALE)。
蜂窝网络为了支持无源或半有源物联网的应用，蜂窝网络需要融合无源或半有源物联网技术(或无源或半有源物联网网络架构)。可选的，一种可行的实施方式中，蜂窝网络中的物联网功能网元实现无源或半有源物联网中的中间件部分或全部功能。物联网功能网元可以是控制面网元，也可以是用户面网元；物联网功能网元可以是新增设的网元，也可以是集成于其他已定义的网元中。为了便于叙述，本申请实施例中，将具有物联网功能的网元称为第一网元。按照物联网功能网元的部署方式，存在多种融合的网络架构方案。在后续实施例中再做详细说明，此处不作赘述。本申请实施例中，需要说明的是，本申请实施例中的物联网功能网元还可以称为应用层事件代理功能(ALE proxy)。
接下来，介绍本申请实施例涉及的蜂窝网络，图1c所示的5G网络架构为例对本申请涉及的蜂窝网络进行说明。请参阅图1c，图1c为一种通信系统的网络架构示意图，所述 网络架构中可以包括：终端设备(也可以称为用户设备部分)，通信网络部分和数据网络104(data network，DN)部分。
终端设备部分包括终端设备101，终端设备101也可以称为用户设备(user equipment，UE)。本申请实施例中所涉及的终端设备101作为一种具有无线收发功能的设备，可以经(无线)接入网102((radio)access network，(R)AN)中的接入网设备与一个或多个核心网(core network，CN)进行通信。终端设备101也可称为接入终端，终端，用户单元，用户站，移动站，移动台，远方站，远程终端，移动设备，用户终端，无线网络设备，用户代理或用户装置等。终端设备101可以部署在陆地上，包括室内或室外，手持或车载；也可以部署在水面上(如轮船等)；还可以部署在空中(例如飞机，气球和卫星上等)。终端设备101可以是蜂窝电话(cellular phone)，无绳电话，会话启动协议(session initiation protocol，SIP)电话，智能电话(smart phone)，手机(mobile phone)，无线本地环路(wireless local loop，WLL)站，个人数字处理(personal digital assistant，PDA)，可以是具有无线通信功能的手持设备，计算设备或连接到无线调制解调器的其它设备，车载设备，可穿戴设备，无人机设备或物联网，车联网中的终端，第五代移动通信(fifth generation，5G)网络以及未来网络中的任意形态的终端，中继用户设备或者未来演进的公用陆地移动通信网络(public land mobile network，PLMN)中的终端等，其中，中继用户设备例如可以是5G家庭网关(residential gateway，RG)。例如终端设备101可以是虚拟现实(virtual reality，VR)终端，增强现实(augmented reality，AR)终端，工业控制(industrial control)中的无线终端，无人驾驶(self driving)中的无线终端，远程医疗(remote medical)中的无线终端，智能电网(smart grid)中的无线终端，运输安全(transportation safety)中的无线终端，智慧城市(smart city)中的无线终端，智慧家庭(smart home)中的无线终端等。本申请实施例对此并不限定。
通信网络可以包括统一数据管理108(unified data management，UDM)，接入和移动性管理功能105(access and mobility management function，AMF)，会话管理功能106(session management function，SMF)，策略控制网元107(policy control function，PCF)，用户面功能103(user plane function，UPF)以及(R)AN102等。上述通信网络中，除(R)AN部分之外的其他部分可以称为核心网络(core network，CN)部分或核心网部分。为方便说明，本申请实施例中以(R)AN为RAN为例进行说明。
数据网络DN104，也可以称为协议数据网络(protocol data network，PDN)，可以为运营商或企业的数据网络，也可以为第三方数据网络。通信网络可以接入多个数据网络DN104，数据网络DN104上可部署多种业务，可为终端设备提供数据和/或语音等服务。例如，数据网络DN104可以是某智能工厂的私有网络，智能工厂安装在车间的传感器可以是终端设备，数据网络DN104中部署了传感器的控制服务器，控制服务器可为传感器提供服务。传感器可与控制服务器通信，获取控制服务器的指令，基于指令将采集的传感器数据传送给控制服务器等。又例如，数据网络DN104可以是某公司的内部办公网络，该公司员工的手机或者电脑可为终端设备，员工的手机或者电脑可以访问公司内部办公网络上的信息，数据资源等。
终端设备可通过通信网络提供的接口(例如N1等)与通信网络建立连接，使用通信网络提供的数据和/或语音等服务。终端设备还可通过通信网络访问数据网络DN104，使用数据网络DN104上部署的运营商业务，和/或第三方提供的业务。其中，上述第三方可为通信网络和终端设备之外的服务方，可为终端设备提供其他数据和/或语音等服务。其中，上述第三方的具体表现形式，具体可基于实际应用场景确定，在此不做限制。
下面对通信网络中的网络功能进行简要介绍。
(R)AN102是一种为终端设备提供无线通信功能的设备。终端设备要接入通信网络，首先是经过(R)AN102，进而可通过(R)AN102与通信网络的业务节点连接。本申请实施例中的接入网设备102(RAN设备)，(R)AN包括但不限于：5G系统中的下一代基站节点(next generation node base station，gNB)，长期演进(long term evolution，LTE)中的演进型节点B(evolved node B，eNB)，无线网络控制器(radio network controller，RNC)，节点B(node B，NB)，基站控制器(base station controller，BSC)，基站收发台(base transceiver station，BTS)，家庭基站(例如，home evolved nodeB，或home node B，HNB)，基带单元(base band unit，BBU)，传输点(transmitting and receiving point，TRP)，发射点(transmitting point，TP)，小基站设备(pico)，移动交换中心，非3GPP(如wireless local area network，WLAN或蓝牙Bluetooth)网络的接入点，或者未来网络中的网络设备等。采用不同无线接入技术的系统中，具备接入网设备功能的设备的名称可能会有所不同。为方便描述，本申请所有实施例中，上述为终端设备提供无线通信功能的装置统称为接入网设备或简称为RAN102或AN102。
应理解，本文对接入网设备的具体类型不作限定。该接入网设备融合了无源或半有源物联网中读写器的部分或全部功能。该接入网设备与标签之间的通信流程，如标签盘点流程与标签读写流程可以参考图3和图4的描述。接入与移动性管理功能AMF105(也可以称为AMF网元，AMF网络功能或AMF网络功能实体)是由通信网络提供的控制面网络功能，负责标签接入通信网络的接入控制和移动性管理，例如包括移动状态管理，分配用户临时身份标识，认证和授权用户等功能。
会话管理功能SMF106(也可以称为SMF网元，SMF网络功能或SMF网络功能实体)是由通信网络提供的控制面网络功能，负责管理标签的协议数据单元(protocol data unit，PDU)会话。PDU会话是一个用于传输PDU的通道，标签需要通过PDU会话与数据网络DN104互相传送PDU。PDU会话由SMF106网络功能负责建立，维护和删除等。SMF106网络功能包括会话管理(如会话建立，修改和释放，包含用户面功能UPF103和(R)AN102之间的隧道维护)，UPF103网络功能的选择和控制，业务和会话连续性(service and session continuity，SSC)模式选择，漫游等会话相关的功能。
用户面功能UPF103(也可以称为UPF网元，UPF网络功能或UPF网络功能实体)是由运营商提供的网关，是通信网络与数据网络DN104通信的网关。UPF103网络功能包括数据包路由和传输，数据包检测，业务用量上报，服务质量(quality of service，QoS)处理，合法监听，上行数据包检测，下行数据包存储等用户面相关的功能。
统一数据管理网元UDM108(也可以称为UDM网元，UDM网络功能或UDM网络功能实体) 是由运营商提供的控制面功能，负责存储通信网络中签约用户的永久身份标识(subscriber permanent identifier，SUPI)，签约用户的公开使用的签约标识(generic public subscription identifier，GPSI)，信任状(credential)等信息。其中SUPI在传输过程中会先进行加密，加密后的SUPI被称为隐藏的用户签约标识符(subscription concealed identifier，SUCI)。UDM108所存储的这些信息可用于标签接入通信网络的认证和授权。其中，上述通信网络的签约用户具体可为使用通信网络提供的业务的用户，例如使用运营商A的手机芯卡的用户。上述签约用户的信任状可以是：该手机芯卡存储的长期密钥或者跟该手机芯卡加密相关的信息等存储的小文件，用于认证和/或授权。需要说明的是，永久标识符，信任状，安全上下文，认证数据(cookie)，以及令牌等同验证/认证，授权相关的信息，在本申请实施例中，为了描述方便起见不做区分限制。
策略控制实体(policy control function，PCF),负责策略控制、计费策略控制、服务质量(quality of service，QoS)控制等。PCF107可以与AF交互获得服务质量(Quality of Service，Qos)参数，或者提供QoS参数给AF，进而实现一种可以影响应用程序数据传输的作用。
应用功能AF，AF与第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)核心网交互用于提供应用层服务。该应用功能AF可以位于数据网络(data network，DN)中。比如：提供关于应用层数据路由，提供接入网络能力。AF可以与PCF107交互。AF的位置可以在5G核心网内部，也可以在5G核心网外部。如果AF在5G核心网内部，那么他可以直接与PCF107交互。如果AF在5G核心网外部，则网络开放功能(Network Exposure Function，NEF)作为中间节点转发AF与PCF107的交互内容。比如通过NEF转发。
鉴权管理功能(authentication server function，AUSF)(也可以称为AUSF网元、AUSF网络功能或AUSF网络功能实体)是由运营商提供的控制面功能，通常用于主认证，即标签101(签约用户)与通信网络之间的认证。AUSF接收到签约用户发起的认证请求之后，可通过UDM 108中存储的认证信息和/或授权信息对签约用户进行认证和/或授权，或者通过UDM 108生成签约用户的认证和/或授权信息。AUSF可向签约用户反馈认证信息和/或授权信息。在一种实现方式中，AUSF也可以与UDM合设。
在实际部署中，核心网中的网元可以合设。例如，接入与移动性管理功能可以与会话管理功能合设；会话管理功能可以与用户面功能合设。当两个网元合设的时候，本申请实施例提供的这两个网元之间的交互就成为该合设网元的内部操作或者可以省略。
值得说明的是，在本申请实施例所基于的通信网络架构中，标签可以通过具有无源或半有源物联网中读写器的部分或全部功能的通信网络，与数据网络(Date network，DN)中的无源或半有源物联网服务器进行通信。其中，(R)AN还具有终端设备的部分功能，即向核心网请求建立控制面通道和用户面通道，也可以称为(R)AN为标签代建控制面通道和用户面通道。具体可以参考本申请图8和图9a的描述。需要说明的是，本申请实施例中的标签具体可以是商超的电子价签、医疗的母婴手环，智慧园区的资产标签等。
为方便说明，本申请实施例中以接入和移动性管理网络功能为AMF105为例进行说明。 它也可以是未来通信系统中的具有上述AMF网络功能的其他网络功能。或者，本申请中的接入和移动性管理网络功能105还可以是LTE中的移动管理网元(mobility management entity，MME)等。进一步地，将AMF网络功能简称为AMF，将即本申请实施例中后文所描述的AMF均可替换为接入和移动性管理网络功能。
本申请实施例中以会话管理功能为SMF106为例进行说明。它也可以是未来通信系统中的具有上述SMF网络功能的其他网络功能。进一步地，将SMF网络功能简称为SMF，将即本申请实施例中后文所描述的SMF均可替换为会话管理功能。
本申请实施例中以统一数据管理UDM108为例进行说明。它也可以是未来通信系统中的具有上述UDM网络功能的其他网络功能。进一步地，将UDM网络功能简称为UDM，将即本申请实施例中后文所描述的UDM均可替换为统一数据管理。
本申请实施例中的用户面功能UPF103，它也可以是未来通信系统中的具有上述UPF网络功能的其他网络功能。此处不作限制。
本申请提供的一种报文传输方法可以应用于各类通信系统中，例如，可以是物联网(internet of things，IoT)、窄带物联网(narrow band internet of things，NB-IoT)、长期演进(long term evolution，LTE)，也可以是第五代(5G)通信系统，还可以是LTE与5G混合架构、也可以是5G新无线(new radio，NR)系统以及未来通信发展中出现的新的通信系统等。本申请的5G通信系统可以包括非独立组网(non-standalone，NSA)的5G通信系统、独立组网(standalone，SA)的5G通信系统中的至少一种。通信系统还可以是公共陆地移动网络(public land mobile network，PLMN)网络、设备到设备(device-to-device，D2D)网络、机器到机器(machine to machine，M2M)网络或者其他网络。
本申请实施例中涉及的“报文”，还可以替换为“数据包”、“数据”、“指令”或“信令”等，此处不作限制。
此外，本申请实施例还可以适用于面向未来的其他通信技术，例如6G等。本申请描述的网络架构以及业务场景是为了更加清楚的说明本申请的技术方案，并不构成对本申请提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请涉及的各个网络功能可能发生变更，本申请提供的技术方案对于类似的技术问题，同样适用。
图2为本申请实施例中通信装置的硬件结构示意图。该通信装置可以是本申请实施例中接入网设备或者物联网功能网元的一种可能的实现方式。需要说明的是，本申请实施例中提出的物联网功能网元还可能与其它核心网网元合设，例如与UPF合设，此处不作限制。如图2所示，通信装置至少包括处理器204和存储器203。存储器203进一步用于存储指令2031和数据2032。可选的，通信装置包括I/O(输入/输出，Input/Output)接口210和总线212。可选的，该通信装置还可以包括收发器202和天线206。收发器202进一步包括发射器2021和接收器2022。此外，处理器204，收发器202，存储器203和I/O接口210通过总线212彼此通信连接，天线206与收发器202相连。
处理器204可以是通用处理器，例如但不限于，中央处理器(central processing unit， CPU)，也可以是专用处理器，例如但不限于，数字信号处理器(digital signal processor，DSP)，应用专用集成电路(application specific integrated circuit，asic)和现场可编程门阵列(field programmable gate array，FPGA)等。该处理器204还可以是神经网络处理单元(neural processing unit，NPU)。此外，处理器204还可以是多个处理器的组合。特别的，在本申请实施例提供的技术方案中，处理器204可以用于执行，后续方法实施例中报文传输方法的相关步骤。处理器204可以是专门设计用于执行上述步骤和/或操作的处理器，也可以是通过读取并执行存储器203中存储的指令2031来执行上述步骤和/或操作的处理器，处理器204在执行上述步骤和/或操作的过程中可能需要用到数据2032。
收发器202包括发射器2021和接收器2022，在一种可选的实现方式中，发射器2021用于通过天线206发送信号。接收器2022用于通过天线206之中的至少一根天线接收信号。特别的，在本申请实施例提供的技术方案中，发射器2021具体可以用于通过天线206之中的至少一根天线执行，例如，后续方法实施例中一种报文传输方法应用于网络设备时，网络设备中接收模块或发送模块所执行的操作。
在本申请实施例中，收发器202用于支持通信装置执行前述的接收功能和发送功能。将具有处理功能的处理器视为处理器204。接收器2022也可以称为输入口、接收电路等，发射器2021可以称为发射器或者发射电路等。
处理器204可用于执行该存储器203存储的指令，以控制收发器202接收消息和/或发送消息，完成本申请方法实施例中通信装置的功能。作为一种实现方式，收发器202的功能可以考虑通过收发电路或者收发的专用芯片实现。本申请实施例中，收发器202接收消息可以理解为收发器202输入消息，收发器202发送消息可以理解为收发器202输出消息。
存储器203可以是各种类型的存储介质，例如随机存取存储器(random access memory，RAM)，只读存储器(read only memory，ROM)，非易失性RAM(non-volatile ram，NVRAM)，可编程ROM(programmable rom，PROM)，可擦除PROM(erasable PROM，EPROM)，电可擦除PROM(electrically erasable PROM，EEPROM)，闪存，光存储器和寄存器等。存储器203具体用于存储指令2031和数据2032，处理器204可以通过读取并执行存储器203中存储的指令2031，来执行本申请方法实施例中所述的步骤和/或操作，在执行本申请方法实施例中操作和/或步骤的过程中可能需要用到数据2032。
在介绍本申请实施例之前，首先介绍本申请实施例涉及的技术内容。
(1)、标签盘点流程。
标签盘点流程用于盘点存在的标签情况。每个标签都有其标识信息。可选的，一种可能的实现方式，该标识信息可以是电子产品代码(electronic product code，EPC)。以下以该标识信息为EPC码为例进行阐述，但本申请实施例中，标签的标识信息不限于EPC码。在盘点流程中，标签会将该EPC码发送给读写器，从而读写器可获知有哪些标签在其覆盖范围内。该信息会最终由读写器上报给中间件和服务器。请参阅图3，图3为本申请实施例中标签盘点的流程示意图。
A1、读写器向标签发送选择命令。
步骤A1中，读写器接收来自物联网功能网元的盘点命令。该盘点命令可以由无源或半 有源物联网服务器下发给物联网功能网元，再由物联网功能网元下发给读写器。读写器接收该盘点命令后，生成选择(select)命令。该命令中包括标签的范围，例如：特定范围内EPC码。
标签在监听该选择命令后，判断自身是否属于该选择命令中的标签范围，若属于，则标签在后续流程中监听到询问(Query)命令后反馈信息；若不属于，则标签在后续流程中不执行动作。
A2、读写器向标签发送询问命令。
步骤A2中，读写器继续发送询问命令。
A3、标签向读写器发送随机数。
步骤A3中，当标签确认自身属于选择命令中的标签范围内，标签通过竞争的方式向读写器发送随机数，例如：RN16。
A4、读写器向标签发送确认命令。
步骤A4中，当读写器接收到来自标签的随机数后，读写器发送确认(ACK)命令，该确认命令中包括步骤A3中收到的随机数(RN16)。
A5、标签向读写器发送EPC码。
步骤A5中，当标签收到读写器发送的确认命令后，标签校验该确认命令中的随机数。当校验成功后，标签反馈自身的EPC码给读写器，完成盘点流程。
(2)、标签读写流程。
标签读写流程，即对标签进行写或读操作。若为写操作，则会将数据写入标签的存储区中；若为读操作，则会读取标签存储区中的数据。在读写流程中，读写器会通过将选择(Select)命令中的标签范围设置为需读写的标签范围(比如Select命令中的范围为某一EPC码，则会对该EPC码对应的标签进行读写操作)。请参阅图4，图4为本申请实施例中标签读写的流程示意图。
B1、读写器向标签发送选择命令。
B2、读写器向标签发送询问命令。
B3、标签向读写器发送随机数。
B4、读写器向标签发送确认命令。
B5、标签向读写器发送EPC码。
步骤B1-B5与前述步骤A1-A5一致，此处不再赘述。
B6、读写器向标签发送随机数请求(Req_RN)命令。
步骤B6中，读写器向标签发送Req_RN命令，Req_RN命令中包括了步骤B3中收到的随机数RN16。
B7、标签向读写器发送句柄(handle)。
步骤B7中，当标签校验步骤B6中接收的随机数正确后，标签向读写器发送句柄。在后续的读写流程中，都需要包括该句柄。
B8、读写器向标签发送读或写命令。
步骤B8中，读写器向该标签发送读命令或写命令，该读命令或写命令中都需要包括该 句柄。在写命令中，还需要包括写进标签存储区的数据。
B9、标签向读写器发送数据。
若步骤B8为读命令，则执行步骤B9。
步骤B9中，标签向读写器发送自己存储区中的数据，并且包括句柄。
(3)、无源或半有源物联网(passive IoT)架构。
本申请实施例中涉及的无源或半有源物联网架构包括多种实现方案，下面分别结合附图进行说明。
(3.1)、用户面网元融合物联网功能网元。
一种可能的实现方式中，如图5所示，图5为本申请实施例中一种无源或半有源物联网架构示意图。物联网功能网元融合至用户面网元中，即用户面网元具有物联网功能网元的功能，或者，该用户面网元与该物联网功能网元合设。
无源或半有源物联网数据则通过用户面通道进行通信。在该架构下，下行数据从无源或半有源物联网服务器发给用户面网元(即其中的物联网功能网元)，再由用户面网元通过接入网设备发给标签。而上行数据侧是标签发给接入网设备，再由接入网设备通过用户面通道发给用户面网元(物联网功能网元)，再由用户面网元(物联网功能网元)发给无源或半有源物联网服务器。
在另一种可能的实现方式中，如图6所示，图6为本申请实施例中又一种无源或半有源物联网架构示意图。物联网功能网元与用户面网元连接，该物联网功能网元与用户面网元相互独立。
(3.2)、物联网功能网元作为控制面网元。
请参阅图7a和图7b，图7a-7b为本申请实施例中又一种无源或半有源物联网架构示意图。物联网功能网元作为控制面网元部署在核心网中。此时，无源或半有源物联网数据则通过控制面通道进行通信。在该架构下，无源或半有源物联网服务器向物联网功能网元发送下行数据，再由物联网功能网元通过SMF(可选)、AMF发给接入网设备，进而发给标签。而上行数据侧是标签直接发给接入网设备，再由接入网设备通过控制面通道(通过AMF、SMF(可选))发给物联网功能网元，再由物联网功能网元发给无源或半有源物联网服务器。
(3.3)、物联网功能网元不与用户面网元合设。
当物联网功能网元不与用户面网元合设时，物联网功能网元作为本地通信网络的网元与用户面网元建立通信连接。作为一种可能的实现方式，用户面网元通过专有接口(例如N4接口)与物联网功能网元通信。作为另一种可能的实现方式，用户面网元通过服务化接口与物联网功能网元通信。
(4)、RAN代理建立控制面通道。
上述(3.1)-(3.3)所示的架构中，RAN为了实现传输无源或半有源物联网指令，需要RAN代理建立以RAN为粒度或者以标签为粒度的控制面(或用户面)通道，“代理建立”本申请实施例中还可以简称为“代建”。以颗粒度为RAN的控制面(或用户面)通道指的是RAN为无源或半有源物联网数据的通信建立一个控制面(或用户面)通道)，此时每个RAN有一个对应的终端的标识(也可以称为RAN为标签代理建立的SUPI)，RAN支持终端的功能， 使用该终端的标识与核心网之间建立该终端的控制面(或用户面)通道。该终端的控制面(或用户面)通道用于传输该RAN覆盖范围内标签的控制信令或用户面数据。颗粒度为标签的控制面(或用户面)通道指的是RAN为每个标签代理建立一个控制面(或用户面)通道。示例性的，RAN使用对应标签的标识构造终端标识(也可以称为RAN为标签代理建立的SUPI)，并使用构造的终端标识为该标签建立控制面(或用户面)通道。该控制面(或用户面)通道为RAN与核心网之间的通道，用于传输对应的标签的控制面信令或用户面数据。以RAN为标签代理建立控制面通道为例，“代理建立”指的是RAN为标签构建非接入层(non-access stratum，NAS)信令，并基于该信令完成控制面通道的建立流程。具体“代理建立”控制面通道的流程，请参阅图8，图8为本申请实施例中RAN代理建立控制面通道的流程示意图。
C1、RAN选择AMF。
步骤C1中，RAN选择AMF。
C2、RAN向AMF发送N2 UE初始消息。
步骤C2中，RAN向AMF发送N2 UE初始消息(N2 UE initial message)。N2 UE初始消息中包括非接入层(non-access stratum，NAS)信令，NAS信令是一个注册请求消息，该注册请求消息中包含了终端标识。当RAN代建颗粒度为标签的控制面通道时，该终端标识为根据该标签的标识构造的终端标识。当RAN代建颗粒度为RAN的控制面通道时，该终端标识为RAN对应的终端的标识。终端标识可以为用户隐藏标识(subscription concealed identifier，SUCI)的形式。
C3、AMF选择AUSF。
C4、网络对标签进行鉴权。
步骤C4中，网络对标签进行鉴权。
C5、RAN和AMF之间进行NAS安全模式命令流程。
步骤C5中，当鉴权成功后，AMF初始化NAS安全模式命令流程(NAS Security Mode Command procedure)。RAN向AMF通过N2上行NAS消息响应一个NAS安全模式完成消息(NAS Security Mode Complete message)。这时，RAN代替标签与AMF之间建立了一个NAS安全上下文(NAS security context)。
C6、RAN与AMF建立上下文。
步骤C6中，当AMF收到RAN的NAS安全模式完成消息后，会向RAN发送初始上下文请求(N2Initial Ctx Request)；当RAN完成上下文建立后，会发送响应消息(N2Initial Ctx Response)给AMF。此时，RAN代替标签建立了上下文。
C7、AMF发送NAS注册接受消息。
C8、RAN发送NAS注册完成消息。
步骤C7-C8示意RAN为标签代理建立控制面通道的流程完成，该标签成功注册至核心网。
(5)、RAN为标签完成协议数据单元(Protocol Data Unit，PDU)会话建立流程。
在图8的基础上，介绍RAN为标签代建用户面通道。请参阅图9a，图9a为本申请实 施例中RAN为标签完成协议数据单元PDU会话建立流程的流程示意图。RAN在发送PDU会话建立请求之前，需要帮助标签完成图9a所示的注册流程。
D1、RAN代建控制面通道，完成注册流程。
步骤D1与前述图8所示步骤类似，此处不再赘述。
D2、RAN向AMF发送N2消息。
步骤D2中，RAN向AMF发送N2消息，该N2消息中包括了PDU会话建立请求消息(PDU Session Establishment Request)，该PDU会话建立请求消息为NAS消息。
该PDU会话建立请求消息包括会话标识(PDU Session ID)；可选的，还包括以下一项或多项参数：请求类型(Request Type)、UE请求的数据网络名称(UE Requested DNN)或者切片信息(S-NSSAI)等参数。其中，请求类型可以包括以下一种或多种：
A、初始请求(Initial request)，表明该会话建立请求消息是用于请求建立一个新的会话，此时消息中的会话标识应为UE新生成的会话标识，即应与当前已建立的会话的会话标识不一样。
B、当前存在的PDU会话(Existing PDU Session)，表明该会话建立请求消息是用于请求将一个当前已建立的会话从3GPP接入切换至非3GPP接入，或者从非3GPP接入切换至3GPP接入。亦或者，用于请求将一个当前已建立的4G分组数据网(Packet Data Network，PDN)连接切换至5G。在这种情况下，会话标识应为一个当前已建立的会话的会话标识，表明要将该会话进行切换。
C、紧急请求(Emergency Request)，表明该会话建立请求消息是用于请求建立一个用于紧急业务的PDU会话。
D3、各个网元执行会话建立流程。
步骤D3中，会话建立的主要步骤如下：
D3.1、AMF选择SMF。
D3.2、AMF向SMF发送会话创建会话上下文请求消息，其中包括了SUPI(UE标识)、UE请求的DNN、PDU Session ID等参数；
D3.3、SMF向UDM获取会话管理签约数据，步骤D3.3为可选步骤。
D3.4、SMF向AMF反馈会话创建会话上下文响应消息。
D3.5、执行会话鉴权或授权流程，步骤D3.5为可选步骤。
D3.6、若需要动态PCC规则，则SMF选择PCF，并与该PCF建立会话策略关联。
D3.7、SMF选择UPF。
D3.8、SMF向PCF发起会话策略关联修改，在该步骤中，SMF会将为UE分配的IP地址发给PCF。
D3.9、SMF与UPF建立N4连接。
D3.10、SMF向AMF发送N1N2消息，此消息中，包含了会话标识、N2接口会话管理信息(N2 SM information)以及N1接口会话管理容器(N1 SM Container)等信息；其中，N2 SM information是SMF通过AMF发给RAN的，而N1 SM Container中的信息是SMF通过AMF发给RAN(后续AMF通过NAS消息发给RAN)的；N2 SM information中包含了UPF 的隧道端点标识等信息，该信息会发给RAN，用于告诉RAN，上行数据应该发到哪。而N1 SM Container中包含了会话建立接受消息(一种可选的方式，PDU Session Establishment Accept)以及其他与会话相关的参数信息。
D3.11、AMF向RAN发送N2会话请求消息，其中包括了N2 SM information，以及需要发给UE的NAS消息，其中NAS消息中包括了会话标识以及N1 SM Container。
D3.12、RAN与UE建立空口资源，RAN将NAS消息发给UE；NAS消息中，包括了PDU会话建立接受消息。
D3.13、RAN向AMF发送N2会话响应消息，其中包括了RAN侧的隧道端点标识(后续会经过AMF、SMF发给UPF)。该信息用于告诉UPF，下行数据的目的地。
D3.14、AMF将RAN发送的消息通过PDU会话更新会话上下文请求发给SMF。
D3.15、SMF通过N4会话修改流程向UPF发送RAN侧的接入网(AN)隧道端点标识信息。
D3.16、SMF向AMF发送会话更新会话上下文响应消息。
D4、AMF向RAN发送N2会话请求消息。
步骤D4中，AMF向RAN发送N2 PDU会话请求消息，当中包括会话建立接受消息，并将N3隧道信息(即CN Tunnel Info)发给RAN，从而让RAN获知上行数据应如何发送。
D5、RAN向AMF发送N2会话响应消息。
步骤D5中，RAN向AMF发送N2会话响应消息，当中包括RAN的隧道信息，RAN的隧道信息包括：RAN的互联网协议(IP)地址与RAN的隧道端点标识信息等。
D6、AMF通知UPF如何转发下行数据。
步骤D6中，RAN的隧道信息通过AMF、SMF发给UPF，从而使UPF获知下行数据该如何转发。具体的，AMF向SMF发送该RAN的隧道信息，SMF向UPF发送该RAN的隧道信息。
下面结合附图介绍本申请实施例，需要说明的是，以下实施例中出现的各个网元(或者网络功能)可以是具有该网元功能的其它网元，例如：物联网功能网元可以是未来通信系统中具有该物联网功能网元功能的其它网元(或网络功能)，此处不作限定。本申请实施例中的物联网功能网元包括但不限于：用户面功能UPF、接入和移动性管理功能AMF、会话管理功能SMF、网络仓储功能NRF或者第一网元。
首先，请参阅图9b，图9b为本申请实施例提出的一种报文传输方法的实施例流程示意图。本申请实施例提出的一种报文传输方法包括：
E1、接入网设备从物联网功能网元接收第一报文。
步骤E1中，物联网功能网元根据来自无源或半有源物联网服务器的无源或半有源物联网指令，生成第一报文。该第一报文中包括无源或半有源物联网指令。
示例性的，无源或半有源物联网服务器通过是通过应用层事件(application level event，ALE)协议中的读应用程序接口(Reading API)或写应用程序接口(Writing API)发送无源或半有源物联网指令。该无源或半有源物联网指令包括：事件周期规格指令(event cycle specification，ECSpecs)或命令周期规格(command cycle specification，CCSpecs)，其中，该事件周期规格指令或命令周期规格指令包括了需要盘点的标签范围，或者需要执 行读操作或写操作的标签范围。
可选的，物联网功能网元通过第一会话向接入网设备发送第一报文。该第一会话的会话类型为无源或半有源物联网，或者第一会话的会话标识指示第一会话与无源或半有源物联网有关。具体建立第一会话的步骤，请参阅后续实施例中步骤S2-S4。
E2、接入网设备获取第一信息。
本实施例中，将指示第一报文包括无源或半有源物联网指令的信息称为第一信息。第一信息可以由物联网功能网元向接入网设备发送，该第一信息还可以由接入网设备从物联网功能网元获取或者该第一信息可以由接入网设备从上下文信息中获取，此处不做限制。可选的，第一报文中可以包括该第一信息，第一报文也可以与该第一信息相互独立，可以一起发送，也可以不一起发送，此处不作限制。
接入网设备根据第一信息，确定该第一报文与无源或半有源物联网有关，或者也可以称为，该第一报文需要使用第二协议进行处理，或者也可以称为，该第一报文包括无源或半有源物联网指令。
作为一种可能的实施方式，当第一报文满足第一信息时，则第一报文包括无源或半有源物联网指令。示例性的，第一信息包括第一会话的会话标识，或者第一会话的会话类型。当接入网设备接收到第一会话的报文时，则接入网设备确定该报文与无源或半有源物联网有关或该第一报文包括无源或半有源物联网指令。
作为另一种可能的实施方式，第一信息是包括在第一报文中的指示信息，当接入网设备接收到的报文中包括这个指示信息，就该第一报文包括无源或半有源物联网指令。示例性的，第一信息包括以下一项或多项：第一报文的消息类型，第一报文的容器类型，第一报文的隧道标识信息，第一报文的信息类型，第一会话的会话标识。例如，第一报文的消息类型可以在第一报文的报文头中的消息类型字段描述；当接入网设备接收到的报文的报文头中的消息类型字段与第一信息的第一报文的消息类型相同时，接入网设备确定该报文与无源或半有源物联网有关或该第一报文包括无源或半有源物联网指令。又例如，第一报文的隧道标识信息指的是接入网设备代理建立第一会话的隧道标识信息，即接入网设备建立第一会话时N3隧道的端点标识(接入网侧的隧道端点标识和/或核心网侧的隧道端点标识)，接入网设备可以通过第一报文头中的隧道标识信息和第一信息中的隧道端点标识(例如两者相同或指示相同的隧道端点标识)可知第一报文与无源或半有源物联网有关。具体说明请参阅后续实施例。
示例性的，物联网功能网元生成的第一报文中，第一报文的消息类型指示第一报文包括无源或半有源物联网指令，或者该第一报文需要使用第二协议进行处理。一种可能的实现方式中，第一报文的报文头中包括第一报文的消息类型，第一报文的消息类型指示包括无源或半有源物联网指令，或者第一报文需要使用第二协议进行处理。
示例性的，物联网功能网元采用通用无线分组业务隧道传输协议-用户平面(GTP-U)封装生成第一报文。具体的，该第一报文的报文头指的是GTP-U报文头，该GTP-U报文头包括消息类型字段，该消息类型字段也可以称为第一报文的消息类型。该消息类型字段可以指示该第一报文包括无源或半有源物联网指令，或者该第一报文需要使用第二协议进行 处理。该消息类型字段可以是“RFID”、“Passive IoT”、“P-IoT”或者“LLRP”此处不作限制。
在又一种可能的实现方式中，物联网功能网元还可以在第一报文中的保留字段或者其它字段，记录该第一报文的消息类型。
E3、接入网设备根据第一报文执行无源或半有源物联网操作。
步骤E3中，接入网设备根据第一信息确定第一报文包括的无源或半有源物联网指令。接入网设备根据该无源或半有源物联网指令执行无源或半有源物联网操作，并获取无源或半有源物联网指令的响应。
一种可能的实现方式中，接入网设备根据第一信息，确定第一报文包括无源或半有源物联网指令。接入网设备采用第二协议对该第一报文进行处理(又称为：解析)，得到第一中间数据。该第一中间数据包括无源或半有源物联网指令。
另一种可能的实现方式中，接入网设备根据第一信息，采用第二协议对该第一报文进行处理，得到第一中间数据。
另一种可能的实现方式中，接入网设备接收到第一报文后，采用第二协议对该第一报文进行处理，得到第一中间数据。
示例性的，该无源或半有源物联网操作包括但不限于：标签读写操作，标签盘点操作等。该无源或半有源物联网指令的响应包括但不限于：标签的读数据，或者标签的盘点操作结果等。
本申请实施例中，接入网设备接收来自物联网功能网元的第一报文。接入网设备获取第一信息，根据第一信息确定第一报文包括无源或半有源物联网指令。通过上述方法，接入网设备获知来自物联网功能网元的报文与无源或半有源物联网有关，接入网设备根据该第一报文执行无源或半有源物联网操作。解决了无源或半有源物联网系统与蜂窝网络融合的场景中报文传输的问题。使得蜂窝网络可以解析无源或半有源物联网的应用报文并根据该应用报文执行相关操作。
结合前述实施例，下面以物联网功能网元为用户面网元或者物联网功能网元作为独立网元(即物联网功能网元为第一网元)与用户面网元建立通信连接为例进行说明，在本实施例中以用户面网元是UPF为例进行说明。具体的，请参阅图10a，图10a为本申请实施例提出的一种报文传输方法的实施例流程示意图。本申请实施例提出的一种报文传输方法包括：
1001、SMF向UPF配置第一规则和/或第二规则。
步骤1001为可选步骤。
本实施例中，第一规则指示UPF如何确定接收的报文是否来自无源或半有源物联网服务器；该第二规则还用于指示UPF对来自无源或半有源物联网服务器的报文如何处理。或者，该第二规则指示UPF对匹配上特定包检测信息(例如，来自无源或半有源物联网服务器的报文有特定的包检测信息)的报文如何处理。
第二规则可以指示UPF处理第二报文需要使用的协议类型，向第一网元发送该第二报文，或者向接入网设备发送解析后的第二报文，该第二报文为来自无源或半有源物联网服 务器的报文。示例性的，UPF处理第二报文的方法如本申请实施例中步骤1003a-1003b或者步骤1004a-1004e。
可选的，第二规则包括：报文转发规则(Forwarding Action Rule，FAR)。
第一规则包括：流匹配规则(Packet Detection Rule，PDR)。
示例性的，UPF根据PDR规则确定接收的报文是否来自无源或半有源物联网服务器。UPF根据FAR规则确定来自无源或半有源物联网服务器的报文如何处理。
又一种示例中，UPF根据报文的地址信息确定接收的报文来自无源或半有源物联网服务器。UPF根据FAR规则确定来自无源或半有源物联网服务器的报文如何处理。
又一种示例中，UPF根据PDR规则确定接收的报文是否来自无源或半有源物联网服务器。UPF根据其它预定义的规则确定来自无源或半有源物联网服务器的报文如何处理。
进一步的，该第一规则和/或第二规则可以是增强的N4规则。该增强的N4规则与无源或半有源物联网服务相关。该第一规则和/或第二规则可以包括：增强的FAR规则，和/或增强的PDR规则。
示例性的，UPF根据增强的PDR规则确定接收的报文是否来自无源或半有源物联网服务器。UPF根据增强的FAR规则确定来自无源或半有源物联网服务器的报文如何处理。
又一种示例中，UPF根据报文的地址信息确定接收的报文来自无源或半有源物联网服务器。UPF根据增强的FAR规则确定来自无源或半有源物联网服务器的报文如何处理。
又一种示例中，UPF根据增强的PDR规则确定接收的报文是否来自无源或半有源物联网服务器。UPF根据其它预定义的规则确定来自无源或半有源物联网服务器的报文如何处理。
可选的，当UPF与第一网元合设时，SMF从当前网络中的多个UPF中选取与第一网元合设的UPF(或者具有该第一网元的功能的UPF)。SMF向该UPF配置第一规则和/或第二规则。
需要说明的是，该第一规则和/或第二规则也可以预先配置在UPF中，此时步骤1001不执行。第一规则可以由SMF发给UPF，也可以预置在UPF上。第二规则可以由SMF发给UPF，也可以预置在UPF上。作为一种可能的实现方式，SMF向UPF发送第一规则和第二规则；作为另一种可能的实现方式，SMF向UPF发送第一规则，第二规则预置在UPF上；作为再一种可能的实现方式，SMF向UPF发送第二规则，第一规则预置在UPF上；作为再一种可能的实现方式，第一规则和第二规则预置在UPF上。
1002、UPF从无源或半有源物联网服务器接收第二报文。
可选的，步骤1002之前，RAN代建第一会话，该第一会话用于传输无源或半有源物联网相关的指令或者操作结果。RAN代建第一会话的流程请参阅图9a的描述。
相应的，无源或半有源物联网服务器向UPF发送第二报文。
可选的，UPF根据第一规则确定该第二报文来自无源或半有源物联网服务器。
可选的，UPF根据第一规则确定该第二报文包括无源或半有源物联网指令。例如：UPF确定第二报文与PDR规则匹配，则UPF确定第二报文包括无源或半有源物联网指令，UPF指示UPF自身或者其它网元对该第二报文进行处理。
示例性的，UPF根据第二报文的地址信息，确定第二报文是否来自无源或半有源物联网服务器。该第二报文的地址信息例如是第二报文的源IP地址。
可选的，当不执行步骤1001时，UPF根据预配置的第一规则，确定接收的第二报文是否来自无源或半有源物联网服务器。
可选的，当不执行步骤1001时，UPF根据该第二报文的IP地址，确定接收的第二报文是否来自无源或半有源物联网服务器。当第二报文来自无源或半有源物联网服务器，则UPF采用第一协议和/或第二协议对该第二报文进行处理，生成第一报文。
可选的，当不执行步骤1001时，UPF对所有接收的报文采用第一协议和/或第二协议进行处理。当解析成功，则该接收的报文来自无源或半有源物联网服务器。UPF根据该接收的报文生成第一报文。
可选的，当执行步骤1001时，UPF根据SMF配置的第一规则，确定接收的第二报文是否来自无源或半有源物联网服务器。
一种可能的实现方式中，该第二报文中包括无源或半有源物联网指令。示例性的，无源或半有源物联网服务器通过是通过应用层事件(Application Level Event，ALE)协议中的读应用程序接口(Reading API)或写应用程序接口(Writing API)发送无源或半有源物联网指令。该无源或半有源物联网指令包括：事件周期规格指令(event cycle specification，ECSpecs)或命令周期规格(command cycle specification，CCSpecs)，其中，该事件周期规格指令或命令周期规格指令包括了需要盘点的标签范围，或者需要执行读操作或写操作的标签范围。
步骤1002后，根据物联网功能网元与UPF的部署关系，具体可以细分为两种方案：(1)、UPF与物联网功能网元合设，或者UPF实现该物联网功能网元的功能。例如图5所示的架构；(2)、UPF与物联网功能网元相互独立，UPF与该物联网功能网元建立通信连接，此时该物联网功能网元也称为第一网元。例如图6所示的架构。具体的，方案(1)对应的步骤为1003a-1003b；方案(2)对应的步骤为1004a-1004e。
1003a、UPF采用第一协议处理第二报文，生成第一中间数据。
本实施例中，UPF采用第一协议处理(或者称为：解析)第二报文，处理得到的数据称为第一中间数据。
一种可能的实现方式中，该第一协议为应用层事件(Application Level Event，ALE)协议。
可选的，UPF根据第二规则，确定需要采用第一协议处理第二报文。
1003b、UPF采用第二协议处理第一中间数据，生成第一报文。
本实施例中，UPF采用第二协议处理第一中间数据，生成第一报文。
示例性的，该第二协议为低级别读写器协议(Low Level Reader Protocol，LLRP)。
可选的，UPF根据第二规则，确定需要采用第二协议处理第一中间数据。
下面对UPF生成第一报文的步骤进行描述：
本实施例中，UPF生成的第一报文可以包括第一信息。UPF生成的第一报文也可以不包括该第一信息。
示例性的，UPF生成的第一报文中，第一报文的消息类型指示第一报文包括无源或半有源物联网指令，或者该第一报文需要使用第二协议进行处理。一种可能的实现方式中，第一报文的报文头中包括第一报文的消息类型，第一报文的消息类型指示第一报文包括无源或半有源物联网指令，或者指示第一报文需要使用第二协议进行处理。
又一种示例中，UPF采用通用无线分组业务隧道传输协议-用户平面(GTP-U)封装生成第一报文。具体的，该第一报文的报文头指的是GTP-U报文头，该GTP-U报文头包括消息类型字段，该消息类型字段也可以称为第一报文的消息类型。该消息类型字段可以指示该第一报文包括无源或半有源物联网指令，或者该第一报文需要使用第二协议进行处理。该消息类型字段可以是“RFID”、“Passive IoT”、“P-IoT”或者“LLRP”此处不作限制。
在又一种可能的实现方式中，UPF还可以在第一报文中的保留字段或者其它字段，记录该第一报文的消息类型。
1004a、UPF向第一网元发送第二报文。
可选的，UPF确认第二报文来自无源或半有源物联网服务器后，向第一网元发送第二报文。
可选的，UPF根据第二规则，向第一网元发送该第二报文。
1004b、第一网元采用第一协议处理第二报文，生成第一中间数据。
本实施例中，第一网元接收第二报文后，第一网元采用第一协议处理(或者称为：解析)第二报文，处理得到的数据称为第一中间数据。
一种可能的实现方式中，该第一协议为应用层事件(Application Level Event，ALE)协议。则该第一中间数据称为ALE协议消息。
1004c、第一网元采用第二协议处理第一中间数据，生成第二中间数据。
本实施例中，第一网元采用第二协议处理第一中间数据，生成第二中间数据。
一种可能的实现方式中，该第二协议为低级别读写器协议(Low Level Reader Protocol，LLRP)。则该第二中间数据称为LLRP协议消息。
1004d、第一网元向UPF发送第二中间数据。
1004e、UPF处理第二中间数据，生成第一报文。
本实施例中，第一网元向UPF发送第二中间数据后，UPF对该第二中间数据进行处理，得到第一报文。具体的，UPF对该第二中间数据进行封装，得到第一报文。
进一步的，一种可能的实现方式中，UPF生成的第一报文中，第一报文的报文头指示第一报文需要使用第二协议进行处理。一种可能的实现方式中，第一报文的报文头中包括第一报文的消息类型，第一报文的消息类型指示第一报文需要使用第二协议进行处理。
示例性的，UPF采用通用无线分组业务隧道传输协议-用户平面(GTP-U)封装生成第一报文。具体的，该第一报文的报文头指的是GTP-U报文头，该GTP-U报文头包括消息类型字段，该消息类型字段也可以称为第一报文的消息类型。该消息类型字段可以指示该第一报文需要使用第二协议进行处理。该消息类型字段可以是“RFID”、“Passive IoT”、“P-IoT”或者“LLRP”此处不作限制。
在又一种可能的实现方式中，UPF还可以在第一报文中的保留字段或者其它字段，记 录该第一报文的消息类型。该第一报文的消息类型指示该第一报文需要使用第二协议进行处理。
1005、UPF向接入网设备发送第一报文。
本实施例中，UPF生成第一报文后，向接入网设备发送第一报文。
可选的，UPF通过第一会话向接入网设备发送第一报文。RAN建立该第一会话的流程为图9a中RAN代理建立会话流程。该第一会话的会话类型为无源或半有源物联网，或者第一会话的会话标识指示第一会话与无源或半有源物联网有关。具体建立第一会话的步骤，请参阅后续实施例中步骤S2。
1006、RAN根据第一信息，采用第二协议处理第一报文，得到第一中间数据。
本实施例中，RAN获取第一信息，根据第一信息，确定第一报文包括无源或半有源物联网指令。RAN获取第一信息以及第一信息的具体内容可以参考图9b中E2的描述。RAN采用第二协议对第一报文进行处理。例如：RAN根据第一会话的会话标识，或者第一会话的会话类型，确定第一会话中传输的第一报文包括无源或半有源物联网指令。
RAN采用第二协议处理(又称为：解析)第一报文，得到第一中间数据。该第一中间数据中包括无源或半有源物联网指令。该无源或半有源物联网指令可以是一种空口指令。
一种可能的实现方式中，RAN直接采用第二协议处理第一报文，得到无源或半有源物联网指令。
在另一种可能的实现方式中，RAN根据第一会话的会话标识，或者第一会话的会话类型，确定第一会话中传输的第一报文包括无源或半有源物联网指令。进而，RAN确定该第一报文需要采用第二协议进行处理。
作为步骤1006的一种可能的替换，在另一种可能的实现方式中，RAN根据第一报文中包括的源IP地址，确定第一报文来自第一网元或者来自UPF(该UPF与第一网元合设或者该UPF具有第一网元的功能)。进而，RAN确定该第一报文需要采用第二协议进行处理。
1007、RAN根据第一中间数据，执行无源或半有源物联网操作，并获取无源或半有源物联网指令的响应。
本实施例中，RAN根据第一中间数据中包括的无源或半有源物联网指令，执行无源或半有源物联网操作，并获取无源或半有源物联网指令的响应。示例性的，该无源或半有源物联网操作包括但不限于：标签读写操作，标签盘点操作等。该无源或半有源物联网指令的响应包括但不限于：标签的读数据，或者标签的盘点操作结果等。
1008、RAN采用第二协议处理无源或半有源物联网指令的响应，生成第三报文。
本实施例中，RAN采用第二协议对无源或半有源物联网指令的响应进行处理，得到第三报文。具体的，首先，RAN对该无源或半有源物联网指令的响应进行处理，得到包括该无源或半有源物联网指令的响应的消息报文。其次，RAN对该消息报文进行进一步封装处理，得到第三报文。该第三报文包括该无源或半有源物联网指令的响应。
可选的，物联网功能网元获取第二信息。本申请实施例中，将指示第三报文包括与无源或半有源物联网有关的信令，或者指示第三报文需要使用第二协议进行处理的信息称为第二信息。第二信息可以由接入网设备向物联网功能网元发送，该第二信息还可以由物联 网功能网元获取或者从接入网设备获取，此处不做限制。可选的，第三报文中可以包括该第二信息，第三报文也可以与该第二信息相互独立，即第二信息可以与第三报文一起发送，或者，第二信息与第三报文分开发送，或者，物联网功能网元通过其它方式获取该第二信息，此处不作限制。物联网功能网元根据第二信息，确定该第三报文与无源或半有源物联网有关，也可以称为，确定该第三报文需要使用第二协议进行处理。
进一步的，第二信息包括以下一项或多项：第三报文的消息类型，第三报文的容器类型，第三报文的隧道标识信息，或者第二信息为第三报文的信息类型。
示例性的，RAN生成的第三报文中，第三报文的消息类型指示第三报文与无源或半有源物联网有关，或者第三报文需要使用第二协议进行处理。一种可能的实现方式中，第三报文的报文头中包括第三报文的消息类型，第三报文的消息类型指示第三报文需要使用第二协议进行处理。
示例性的，RAN采用通用无线分组业务隧道传输协议-用户平面(GTP-U)封装生成第三报文。具体的，该第三报文的报文头指的是GTP-U报文头，该GTP-U报文头包括消息类型字段，该消息类型字段也称为第三报文的消息类型。该消息类型字段可以指示该第三报文需要使用第二协议进行处理。该消息类型字段可以是“RFID”、“Passive IoT”、“P-IoT”或者“LLRP”此处不作限制。
在又一种可能的实现方式中，RAN还可以在第三报文中的保留字段或者其它字段，记录该第三报文的消息类型。该第三报文的消息类型指示该第三报文需要使用第二协议进行处理。
1009、RAN向UPF发送第三报文。
本实施例中，可选的，RAN通过第一会话向UPF发送第三报文。
步骤1009后执行步骤1010或者步骤1011a-1011e。
1010、UPF根据第三报文生成第四报文。
示例性的，UPF采用第二协议和第一协议处理第三报文，生成第四报文。
可选的，UPF接收该第三报文后，根据第二信息(例如该第三报文的消息类型，或者第三报文的报文头，第一会话的会话标识，或者第一会话的会话类型)确定第三报文需要采用第二协议进行处理。
示例性的，UPF接收该第三报文后，根据第一会话的会话标识，或者第一会话的会话类型，确定第一会话中传输的第三报文包括无源或半有源物联网指令的响应。进而UPF确定该第三报文需要采用第二协议进行处理。
示例性的，以第二协议为LLRP协议为例。首先，UPF使用LLRP协议处理(又称为解析)该第三报文，获取无源或半有源物联网指令的响应。其次，UPF使用第一协议(例如ALE协议)处理该无源或半有源物联网指令的响应，生成第四报文。该第四报文包括无源或半有源物联网指令的响应。
步骤1010之后执行步骤1012。
可以理解的是，又一种可能的实现方式中，UPF与第一网元之间协同处理第三报文，生成第四报文。示例性的，实现方式如下：
1011a、UPF处理第三报文，生成第三中间数据。
本实施例中，UPF解封装第三报文，生成第三中间数据。示例性的，UPF采用GTP-U解封装第三报文，生成第三中间数据。第三中间数据包括无源或半有源物联网指令的响应。
1011b、UPF向第一网元发送第三中间数据。
本实施例中，UPF向第一网元发送该第三中间数据，由第一网元处理该第三中间数据。
1011c、第一网元采用第二协议处理第三中间数据，生成第四中间数据。
本实施例中，第一网元接收该第三报文后，根据第二信息(例如该第三报文的消息类型，或者第三报文的报文头，第一会话的会话标识，或者第一会话的会话类型)确定第三报文需要采用第二协议进行处理。
一种可能的实现方式中，该第二协议可以为低级别读写器协议(Low Level Reader Protocol，LLRP)。
具体的，第一网元首先采用第二协议解析第三中间数据，生成第四中间数据(包括无源或半有源物联网指令的响应)，该第四中间数据可以是LLRP协议消息。
1011d、第一网元处理第四中间数据，生成第四报文。
本实施例中，第一网元采用第一协议处理第四中间数据，生成第四报文。第四报文包括无源或半有源物联网指令的响应。该第一协议可以为应用层事件(Application Level Event，ALE)协议。
1011e、第一网元向UPF发送第四报文。
步骤1011e后执行步骤1012。
1012、UPF向无源或半有源物联网服务器发送第四报文。
需要说明的是，步骤1008-1012为可选步骤。
本申请实施例中，首先RAN代理建立第一会话，第一会话的会话类型为无源或半有源物联网，或者第一会话的会话标识指示第一会话与无源或半有源物联网有关。在RAN代理建立第一会话的过程中，SMF可以选择支持第一网元功能的UPF。SMF可以向该UPF发送第一规则和/或第二规则，以便UPF获知如何识别报文是否来自无源或半有源物联网服务器，和/或UPF如何处理来自无源或半有源物联网服务器的第二报文。UPF向RAN发送的第一报文中可以包括第一信息，以便RAN高效的识别该第一报文需要采用什么协议进行处理。RAN向UPF发送的第三报文可以包括第二信息，以便UPF高效的识别该第三报文需要采用什么协议进行处理。通过上述方案，解决了无源或半有源物联网系统与蜂窝网络融合的场景中，报文传输的问题。使得蜂窝网络可以解析无源或半有源物联网的应用报文，蜂窝网络中部署的网络功能(或者网元)可以根据该应用报文执行相关操作。
在图10a所示的实施例中，根据第一网元与UPF的关系，具体可以细分为两种方案：(1)、UPF与第一网元合设，或者UPF实现该第一网元的功能。例如图5所示的架构；(2)、UPF与第一网元相互独立，UPF与该第一网元建立通信连接。例如图6所示的架构。下面结合附图分别进行说明：
(1)UPF与第一网元合设，或者UPF实现该第一网元的功能。请参阅图10b，图10b为本申请实施例提出的一种应用场景中的报文传输方法的流程示意图，本申请实施例提出 的一种应用场景包括：
S1、RAN完成标签或RAN的控制面通道的建立流程。
步骤S1中，RAN代理建立以RAN为粒度或者以标签为粒度的控制面(或用户面)通道。具体建立的方法，与前述图8对应的方法类似，此处不作赘述。
S2、RAN向AMF发送PDU会话建立请求消息。
步骤S2中，当RAN建立了标签或RAN的控制面通道后，RAN发送请求消息，该请求消息用于建立第一会话。示例性的，RAN向AMF发送PDU会话建立请求消息(PDU session establishment request)。该PDU会话建立请求消息用于建立第一会话。第一会话的会话类型为无源或半有源物联网，或者，第一会话的会话标识指示第一会话与无源或半有源物联网有关。
可选的，该PDU会话建立请求消息中包括PDU会话类型信息，该PDU会话类型信息指示该第一会话的会话类型为无源或半有源物联网，或者，指示第一会话传输无源或半有源物联网相关的数据。
可选的，RAN在该PDU会话建立的过程中，向AMF发送该PDU会话类型信息。
AMF通过多种方式获取该PDU会话类型信息，示例性的，RAN通过非接入层NAS消息向AMF发送该PDU会话类型信息，或者RAN通过N2消息向AMF发送该PDU会话类型信息。或者，AMF从该标签的签约数据，或者RAN粒度的终端的签约数据中获取该PDU会话类型信息。或者，AMF从AMF自身存储的数据中获取该PDU会话类型信息。此处不作限制。
RAN向AMF发送请求建立第一会话的PDU会话建立请求消息后，后续动作与前述步骤D3-D6类似。值得说明的是，在执行D3时，本实施例有以下不同之处，具体可以参考以下S3a、S3b和S4的描述。
S3a、AMF向SMF发送PDU会话创建会话上下文请求。
步骤S3a中，AMF向SMF发送PDU会话创建会话上下文请求(例如，Nsmf_PDUSession_CreateSM Context Request)，该PDU会话创建会话上下文请求指示建立第一会话。该PDU会话创建会话上下文请求中包括PDU会话类型信息，该PDU会话类型信息包括第一会话的会话标识，和/或第一会话的会话类型。该PDU会话类型信息指示该第一会话的会话类型为无源或半有源物联网，或者，指示第一会话传输无源或半有源物联网相关的数据。
第一会话的会话类型为无源或半有源物联网，或者，第一会话的会话标识指示第一会话与无源或半有源物联网有关。本申请实施例中，第一信息可以是第一会话的会话类型为无源或半有源物联网，或者，第一会话的会话标识。第二信息可以是第一会话的会话类型为无源或半有源物联网，或者，第一会话的会话标识。接入网设备可以通过获取第一会话的会话类型，或者第一会话的会话标识，确定第一会话中传输的第一报文包括无源或半有源物联网指令。物联网功能网元可以通过获取第一会话的会话类型，或者第一会话的会话标识，确定第一会话中传输的第三报文与无源或半有源物联网有关，或者该第三报文包括无源或半有源物联网相关的数据。
S3b、SMF向AMF发送PDU会话创建会话上下文响应。
步骤S3b中，SMF响应于该PDU会话创建会话上下文请求，向AMF发送PDU会话创建会话上下文响应(例如，Nsmf_PDUSession_CreateSM Context Response)。
S4、SMF选择合适的UPF。
步骤S4中，SMF响应于步骤S3a中接收的PDU会话创建会话上下文请求，SMF选择支持第一网元功能的UPF，或者SMF选择与第一网元合设的UPF。步骤S4可选。
当SMF确定合适的UPF后，SMF通过AMF向RAN发送会话建立接受消息，以完成第一会话的建立流程。
S5、执行前述步骤1001-1002，1003a-1003b，1005-1012。
(2)、UPF与第一网元相互独立，UPF与该第一网元建立通信连接。请参阅图10c，图10c为本申请实施例提出的一种应用场景中的报文传输方法的流程示意图，本申请实施例提出的又一种应用场景包括：
Q1、RAN完成标签或RAN的控制面通道的建立流程。
Q2、RAN向AMF发送PDU会话建立请求消息。
RAN向AMF发送请求建立第一会话的PDU会话建立请求消息后，后续动作与前述步骤D3-D6类似。值得说明的是，在执行D3时，本实施例有以下不同之处，具体可以参考以下Q3a、Q3b和Q4的描述。
Q3a、AMF向SMF发送PDU会话创建会话上下文请求。
Q3b、SMF向AMF发送PDU会话创建会话上下文响应。
步骤Q1-Q3b与前述步骤S1-S3b类似，此处不作赘述。
Q4、SMF选择合适的UPF。
步骤Q4中，SMF响应于步骤Q3a中接收的PDU会话创建会话上下文请求，SMF选择与第一网元有通信连接的UPF。步骤Q4可选。例如，该网络中所有UPF均与第一网元有通信连接。
当SMF确定合适的UPF后，SMF通过AMF向RAN发送会话建立接受消息，以完成第一会话的建立流程。
Q5、步骤1001-1002，1004a-1004e，1005-1012。
接下来，介绍物联网功能网元部署于核心网的应用场景，例如前述图7a和图7b所示架构。一种可能的实现方式中，即该物联网功能网元为第一网元。该应用场景中，第一报文通过控制面通道传输。具体的，请参阅图11，图11为本申请实施例提出的一种报文传输方法的实施例流程示意图。本申请实施例提出的一种报文传输方法包括：
1101、RAN为标签代建第一会话。
1101可以参考图9a中D2和D3的描述。其中，第一会话的会话类型为无源或半有源物联网，或者第一会话的会话标识指示第一会话与无源或半有源物联网有关。第一会话用于传输无源或半有源物联网相关的数据。
可选的，第一会话无需建立RAN与UPF之间的用户面通道，该第一会话的用户面数据都通过控制面通道进行传输。示例性的，第一会话为“非IP数据传输(Non-IP Data Delivery，NIDD)”会话。
1102、SMF向NEF发送会话管理上下文建立请求消息。
步骤1102中，为了建立RAN与无源或半有源物联网服务器之间的控制面通道，SMF向NEF发送会话管理上下文建立请求消息(例如，Nnef_SMContext_Create Request)。该会话管理上下文建立请求消息中包括标签的标识信息、第一会话的会话标识、第一会话的会话类型、SMF标识、NIDD信息等参数中的一项或多项。NIDD信息指示最大的报文大小。在SMF与NEF建立连接时，SMF从NEF获取该NIDD信息。SMF向标签发送的PDU会话建立接收消息中包括该NIDD信息。
1103、NEF向SMF发送会话管理上下文建立响应消息。
步骤1103中，NEF创建了会话上下文信息，该上下文信息与标签的标识信息，第一会话的会话标识、第一会话的会话类型等相关信息关联。NEF向SMF发送会话管理上下文建立响应消息(例如，Nnef_SMContext_Create Response)，该会话管理上下文建立响应消息包括NIDD信息，用于通知SMF已创建该标签的会话上下文信息。
通过步骤1101-1103，通信网络为标签建立了NIDD会话。无源或半有源物联网服务器发送的下行数据在NIDD会话中传输时，将通过NEF、SMF、AMF发送到RAN，再通过RAN发送到标签。标签的上行数据通过RAN、AMF、SMF、NEF向无源或半有源物联网服务器发送。
1104、AMF接收来自无源或半有源物联网服务器的第二报文。
步骤1104中，具体可以分为以下步骤：
步骤1104.1中，无源或半有源物联网服务器向第一网元发送第二报文后，第一网元采用第一协议进行解析，并采用第二协议进行处理，生成第一报文。第二报文中包括无源或半有源物联网指令。第一报文中包括无源或半有源物联网指令。
一种可能的实现方式，无源或半有源物联网服务器通过NEF向第一网元发送第二报文；无源或半有源物联网服务器向NEF发送消息，其中该消息包括了无源或半有源物联网指令以及标签的外部标识(该标签的外部标识可以理解为外部网络可识别的标识信息)。该标签的外部标识与标签的订阅永久标识符(Subscription Permanent Identifier，SUPI)相对应的。具体的，该外部标识是一般公共订阅标识符(Generic Public Subscription Identifier，GPSI)，NEF会为SUPI分配对应的GPSI标识，用于与外部第三方交互时使用，防止第三方获取SUPI，避免隐私隐患。NEF根据标签的外部标识，识别相对应的SUPI，向第一网元发送消息，其中该消息包括第二报文和SUPI。
步骤1104.2中，第一网元向SMF发送第一报文。可选的，第一网元还向SMF发送RAN为标签代理建立的SUPI。
在一种可能的实现方式中，第一网元通过服务化接口向SMF发送该第一报文，该第一报文包括该RAN为标签代理建立的SUPI。
在另一种可能的实现方式中，第一网元通过服务化接口向SMF发送该SUPI和第一报文。
步骤1104.3中，SMF向AMF发送第一报文。
示例性的，SMF向AMF发送Namf_Communication_N1N2MessageTransfer消息，Namf_Communication_N1N2MessageTransfer消息包括了SUPI、第一会话的会话标识、第一会话的会话类型，以及第一报文。
1105、AMF通过第一会话向RAN发送第一报文。
步骤1105中，AMF通过第一会话向RAN发送第一报文。具体的，该第一报文为下行非接入层传输(DL NAS Transport)消息。
具体的，第一信息为第一会话的会话标识，和/或第一会话的会话类型。
1106、接入网设备确定第一报文需要采用第二协议进行处理。
步骤1106中，RAN根据第一会话的会话类型，或者第一会话的会话标识，确定第一会话中传输的第一报文需要采用第二协议进行处理。
具体处理方式与前述步骤1006类似，此处不作赘述。
需要说明的是，步骤1106为可选步骤，接入网设备可以直接采用第二协议处理第一报文，即步骤1005后直接进入步骤1107。
1107、接入网设备采用第二协议处理第一报文，得到第一中间数据。
步骤1107与前述步骤1006类似，此处不作赘述。
1108、RAN根据第一中间数据，执行无源或半有源物联网操作，并获取无源或半有源物联网指令的响应。
步骤1108与前述步骤1007类似，此处不作赘述。
1109、RAN向无源或半有源物联网服务器发送无源或半有源物联网指令的响应。
步骤1109中，具体可以分为以下步骤：
1109.1中，完成无源或半有源物联网操作后，RAN将无源或半有源物联网指令的响应通过上行NAS传输消息或N2消息发给AMF。具体的，该上行NAS传输消息或N2消息中包括第三报文，该第二报文包括无源或半有源物联网指令的响应。该上行NAS传输消息或N2消息中还包括第一会话的会话标识，和/或第一会话的会话类型。
1109.2中，AMF通过服务化接口向SMF发送Nsmf_PDUSession_SendMOData请求消息，其中包括了该RAN代建的SUPI、第一会话的会话标识、第一会话的会话类型以及第三报文(无源或半有源物联网指令的响应)。
步骤1109.3中，SMF通过服务化接口向NEF发送Nnef_SMContext_Delivery请求消息，其中包括了SUPI以及第三报文(无源或半有源物联网指令的响应)。
步骤1109.4中，NEF通过服务化接口向第一网元发送Nnef_NIDD_DeliveryNotify请求消息，其中，该Nnef_NIDD_DeliveryNotify请求消息包括第三报文(无源或半有源物联网指令的响应)。
步骤1109.5中，第一网元采用第二协议解析Nnef_NIDD_DeliveryNotify请求消息中包括的第三报文，获取无源或半有源物联网指令的响应。其次，第一网元采用第一协议处理该无源或半有源物联网指令的响应，生成第四报文。再次，第一网元将向无源或半有源物联网服务器发送该第四报文，该第四报文中包括该无源或半有源物联网指令的响应。
一种可能的实现方式中，该第一协议为应用层事件(Application Level Event，ALE)协议。
一种可能的实现方式中，该第二协议为低级别读写器协议(Low Level Reader Protocol，LLRP)。
本申请实施例中，通过控制面通道传输无源或半有源物联网指令与无源或半有源物联网指令的响应。RAN根据第一信息(第一会话的会话类型或者第一会话的会话标识)，使用第二协议对第一会话中传输的数据(或者报文)进行解析。RAN根据解析结果(无源或半有源物联网指令)执行无源或半有源物联网操作。通过上述方案，解决了无源或半有源物联网系统与蜂窝网络融合的场景中，报文传输的问题。使得蜂窝网络可以解析无源或半有源物联网的应用报文，蜂窝网络中部署的网络功能(或者网元)可以根据该应用报文执行相关操作。
接下来，以图7a所示的架构为例，介绍本申请提出的又一种实施例，物联网功能网元为第一网元，第一网元部署于核心网。具体的，请参阅图12，图12为本申请实施例提出的一种报文传输方法的又一种实施例流程示意图。本申请实施例提出的一种报文传输方法包括：
1201、第一网元向AMF订阅RAN代建控制面的事件。
本实施例中，以物联网功能网元是第一网元为例进行说明。第一网元向第二网元发送订阅请求，该订阅请求用于获取接入网设备信息。该接入网设备信息包括但不限于：接入网设备的永久标识(例如SUPI)，服务该接入网设备的核心网网元的信息，该接入网设备信息包括但不限于核心网网元的地址信息和/或标识信息，该接入网设备的读写器标识信息等。步骤1201中仅以第二网元是AMF为例进行说明，可以理解的是物联网功能网元还可以向其它的第二网元发送订阅请求，以订阅RAN代建控制面的事件。
该核心网网元包括但不限于：AMF、SMF、UPF、NRF、UDM、AUSF或者PCF等。
该第二网元包括但不限于：AMF、SMF、UPF、NRF、UDM、AUSF或者PCF等。
示例性的，第一网元向AMF订阅RAN代理建立控制面事件，以便第一网元获取RAN代理建立的SUPI与RAN(例如：RAN的标识信息(可以是RAN的读写器标识))的关系。例如：可以向网络内所有的AMF订阅，也可以向部分AMF订阅。通过该步骤，每当有RAN代理建立了控制面通道后，第一网元就可以通过AMF上报的事件来获取哪个RAN代理建立了控制面通道，以及该RAN代理建立的SUPI信息等。后续无源或半有源物联网服务器向第一网元发送无源或半有源物联网指令(或者信息，或者数据)时，以便负责转发报文的网元(或网络功能，例如NEF、AMF、UDM或SMF)获知报文的目的对端，即该报文需要发送的目标RAN。
1202、预配置NEF。
可选的，本实施例中，通过预配置使得NEF获知来自无源或半有源物联网服务器的所有消息都转发给第一网元；同理，来自第一网元的所有消息都转发给无源或半有源物联网服务器。
需要说明的是，步骤1202为可选步骤。当不执行步骤1202时，无源或半有源物联网服务器可以与第一网元直接进行交互。
1203、RAN代建控制面(和/或用户面)通道。
本实施例中，RAN建立以RAN为粒度或者以标签为粒度的控制面(和/或用户面)通道。具体建立的方法，与前述图8(和/或图9a)对应的方法类似，此处不作赘述。
1204、第一网元接收来自无源或半有源物联网服务器的无源或半有源物联网指令。
本实施例中，无源或半有源物联网服务器向第一网元发送无源或半有源物联网指令。
可选的，无源或半有源物联网服务器通过NEF向第一网元发送无源或半有源物联网指令。
第一网元采用第一协议解析该无源或半有源物联网指令，并采用第二协议处理，生成第一报文。第一报文中包括无源或半有源物联网指令。
一种可能的实现方式中，该第一协议为应用层事件(Application Level Event，ALE)协议。
一种可能的实现方式中，该第二协议为低级别读写器协议(Low Level Reader Protocol，LLRP)。
1205、AMF接收来自第一网元的第一报文。
示例性的，第一网元可以通过服务化接口的消息(例如：Namf_Communication_N1N2MessageTransfer)向AMF发送该第一报文。该第一报文中包括RAN代建的SUPI，以及负载容器(Payload container)或者信息类型。该负载容器也称为第一报文的容器类型，或者称为第一报文包括的容器类型，该信息类型也称为第一报文的信息类型。即第一信息包括：第一报文的容器类型，或者，第一报文的信息类型。
具体如下：第一报文包括的容器类型为N1 P-IoT(或者N1 Passive IoT)传输。或者，第一报文包括的容器类型为N2 P-IoT(或者N2 Passive IoT)传输。
第一报文的信息类型可以是“Passive IoT Information”，“P-IoT Information”或“LLRP Information”等等。
上述容器类型或者信息类型，指示第一报文与无源或半有源物联网有关。需要说明的是，上述容器类型或者信息类型仅做示例性说明，并不限定容器类型或者信息类型的名称。
该容器中包括了无源或半有源物联网指令，即第二协议封装无源或半有源物联网指令至该第一报文中。
1206、AMF向RAN发送第一报文。
本实施例中，当第一报文包括的容器类型为N1 P-IoT(或者N1 Passive IoT)传输时，AMF通过非接入层(Non-Access Stratum，NAS)协议栈发送第一报文，第一报文为N1 P-IoT(或者N1 Passive IoT)传输消息(也称为下行NAS传输消息，DL NAS Transport)；或者，
当第一报文包括的容器类型为N2 P-IoT(或者N2 Passive IoT)传输时，AMF通过下一代应用协议(Next Generation Application Protocol，NGAP)协议栈发送第一报文，第一报文为N2 P-IoT(或者N1 Passive IoT)传输消息。
具体的，第一报文中包括第一信息。第一信息包括：第一报文的容器类型，或者，第二报文的信息类型。
具体如下：第一报文的容器类型为：N1 P-IoT(或者N1 Passive IoT)传输。或者，第一报文的容器类型为N2 P-IoT(或者N2 Passive IoT)传输。第一报文的信息类型可以是“Passive IoT Information”，“P-IoT Information”，或“LLRP Information”等等。
上述容器类型或者信息类型，指示第一报文与无源或半有源物联网有关。需要说明的是，上述容器类型或者信息类型仅做示例性说明，并不限定容器类型或者信息类型的名称。
该容器(“N1 P-IoT(或者N1 Passive IoT)传输”容器，或者“N2 P-IoT(或者N2 Passive IoT)传输”容器)中包括了无源或半有源物联网指令，即第二协议封装无源或半有源物联网指令至该第一报文中。第一报文中包括该无源或半有源物联网指令。
1207、接入网设备确定第一报文需要采用第二协议进行处理。
本实施例中，接入网设备根据第一信息，确定第一报文需要采用第二协议进行处理。
具体处理方法与前述步骤1006类似，此处不作赘述。
需要说明的是，步骤1207为可选步骤，当步骤1207不执行时，步骤1206后执行步骤1208。
1208、接入网设备采用第二协议处理第一报文，得到第一中间数据。
步骤1208与前述步骤1006类似，此处不作赘述。
1209、RAN根据第一中间数据，执行无源或半有源物联网操作，并获取无源或半有源物联网指令的响应。
步骤1209与前述步骤1007类似，此处不作赘述。
1210、RAN向AMF发送第三报文，第三报文包括无源或半有源物联网指令的响应。
本实施例中，当RAN执行完无源或半有源物联网操作，获取无源或半有源物联网指令的响应后，将该无源或半有源物联网指令的响应通过第三报文发送至AMF。
具体的，第三报文可以是N1 P-IoT(或者N1 Passive IoT)传输消息(也称为上行NAS传输消息，UL NAS Transport)，第三报文也可以是N2 P-IoT(或者N2 Passive IoT)传输消息。若RAN通过N1 P-IoT(或者N1 Passive IoT)传输消息发给AMF，则该N1 P-IoT(或者N1 Passive IoT)传输消息的容器类型为第二协议传输，用以指示AMF该消息与无源或半有源物联网有关，需要将该消息发给第一网元。同理，RAN也可以通过N2 P-IoT(或者N2 Passive IoT)传输消息发给AMF，指示AMF该N2消息与无源或半有源物联网有关，需要转发给第一网元。
第三报文中包括第二信息。第二信息包括：第三报文的容器类型，或者，第三报文的信息类型。
具体如下：第三报文的容器类型为：N1 P-IoT(或者N1 Passive IoT)传输。或者，第三报文的容器类型为N2 P-IoT(或者N2 Passive IoT)传输。第三报文的信息类型可以是“Passive IoT Information”，“P-IoT Information”，或“LLRP Information”等等。
上述容器类型或者信息类型，指示第三报文与无源或半有源物联网有关，或者，第三报文需要使用第二协议进行处理。需要说明的是，上述容器类型或者信息类型仅做示例性说明，并不限定容器类型或者信息类型的名称。
该容器(“N1 P-IoT(或者N1 Passive IoT)传输”容器，或者“N2 P-IoT(或者N2 Passive IoT)传输”容器)中包括了无源或半有源物联网指令的响应，即第二协议封装无源或半有源物联网指令的响应至该第三报文中。第三报文中包括该无源或半有源物联网指令的响应。
1211、AMF通过向第一网元发送第三报文。
本实施例中，AMF收到RAN发送的第三报文后，获知该第三报文需要转发给第一网元，可以通过服务化接口将该第三报文发给第一网元。该服务化接口消息可以是新定义的消息例如：“Nx_PIoT_Delivery”，其中该x表示该新定义的服务化接口的名称，本申请不做限定。该服务化接口消息中包括了RAN代建的SUPI以及第三报文。
1212、第一网元向无源或半有源物联网服务器发送无源或半有源物联网指令的响应。
本实施例中，第一网元根据第三报文中包括的第二信息，确定采用第二协议解析该消息，该消息例如：“Nx_PIoT_Delivery”(第三报文)，进而获取无源或半有源物联网指令的响应。其次，第一网元采用第一协议处理该无源或半有源物联网指令的响应，生成第四报文。再次，第一网元将向无源或半有源物联网服务器发送该第四报文，该第四报文中包括该无源或半有源物联网指令的响应。
本申请实施例中，通过控制面通道传输无源或半有源物联网指令与无源或半有源物联网指令的响应。控制面网元(或者网络功能)根据消息类型、信息类型、容器类型或者服务化接口，该消息与无源或半有源物联网操作相关，该消息需要使用第二协议进行处理。控制面网元(或者网络功能)获知来自RAN的该消息，需要转发至第一网元。通过上述方案，解决了无源或半有源物联网系统与蜂窝网络融合的场景中，报文传输的问题。使得蜂窝网络可以解析无源或半有源物联网的应用报文，蜂窝网络中部署的网络功能(或者网元)可以根据该应用报文执行相关操作。
接下来，以图7b所示的架构为例，介绍本申请提出的又一种实施例。具体的，请参阅图13，图13为本申请实施例提出的一种报文传输方法的又一种实施例流程示意图。本申请实施例提出的一种报文传输方法包括：
1301、第一网元向AMF订阅RAN代建控制面事件。
1302、预配置NEF。
1303、RAN完成标签或RAN的控制面通道的建立流程。
1304、第一网元接收来自无源或半有源物联网指令。
步骤1301-1304与前述步骤1201-1204类似，此处不作赘述。
1305、SMF接收来自第一网元的第一报文。
本实施例中，该第一报文中包括RAN代建的SUPI，以及无源或半有源物联网指令。该第二报文为服务化接口消息，示例性的，该服务化接口消息为“Nsmf_PIoT_Command”。
1306、AMF接收来自SMF的第一报文。
本实施例中，SMF接收第一报文后，确定该第一报文与无源或半有源物联网有关。因此，SMF需要向AMF转发该第一报文中包括的无源或半有源物联网指令转发至AMF。
SMF以通过服务化接口的消息Namf_Communication_N1N2MessageTransfer向AMF发送该第一报文。该第一报文中包括RAN代建的SUPI，以及负载容器(Payload container)或者信息类型。
具体如下：第一报文包括的容器类型为N1 P-IoT(或者N1 Passive IoT)传输。或者，第一报文包括的容器类型为N2 P-IoT(或者N2 Passive IoT)传输。
第一报文的信息类型可以是“Passive IoT Information”，“PIoT Information”，或 “LLRP Information”等等。
上述容器类型或者信息类型，指示第一报文与无源或半有源物联网有关。需要说明的是，上述容器类型或者信息类型仅做示例性说明，并不限定容器类型或者信息类型的名称。
该容器中包括了无源或半有源物联网指令，即第二协议封装无源或半有源物联网指令至该第一报文中。
1307、AMF向RAN发送第一报文。
1308、RAN确定第一报文需要采用第二协议进行处理。
1309、RAN采用第二协议处理第一报文，得到第一中间数据。
1310、RAN根据第一中间数据，执行无源或半有源物联网操作，并获取无源或半有源物联网指令的响应。
1311、RAN向AMF发送第三报文，第三报文包括无源或半有源物联网指令的响应。
步骤1307-1311与前述步骤1206-1210类似，此处不作赘述。
1312、AMF向SMF发送第三报文。
本实施例中，AMF可以通过服务化接口消息向SMF发送第三报文。示例性的，该服务化接口消息为“Nsmf_PIoT_report”。该服务化接口消息指示SMF该消息包括无源或半有源物联网指令的响应，并且需要使用第二协议进行处理。
第三报文中包括第二信息，具体的，第三报文中包括第二信息。第二信息包括：第三报文的容器类型，或者，第三报文的信息类型。
具体如下：第三报文的容器类型为：N1 P-IoT(或者N1 Passive IoT)传输。或者，第三报文的容器类型为N2 P-IoT(或者N2 Passive IoT)传输。第三报文的信息类型可以是“Passive IoT Information”，“PIoT Information”，或“LLRP Information”等等。
上述容器类型或者信息类型，指示第三报文与无源或半有源物联网有关，或者，第三报文需要使用第二协议进行处理。需要说明的是，上述容器类型或者信息类型仅做示例性说明，并不限定容器类型或者信息类型的名称。
该容器(“N1 P-IoT(或者N1 Passive IoT)传输”容器，或者“N2 P-IoT(或者N2 Passive IoT)传输”容器)中包括了无源或半有源物联网指令的响应，即第二协议封装无源或半有源物联网指令的响应至该第三报文中。第三报文中包括该无源或半有源物联网指令的响应。
1313、SMF向第一网元发送第三报文。
本实施例中，SMF可以通过服务化接口消息向第一网元发送第三报文。示例性的，该服务化接口消息为“Nx_RFID_report”。该服务化接口消息指示第一网元该消息包括第三报文(无源或半有源物联网指令的响应)，并且需要使用第二协议进行处理。
1314、第一网元向无源或半有源物联网服务器发送无源或半有源物联网指令的响应。
本实施例中，第一网元采用第二协议解析该服务化接口消息(第三报文)，获取无源或半有源物联网指令的响应。其次，第一网元采用第一协议处理该无源或半有源物联网指令的响应，生成第四报文。再次，第一网元将向无源或半有源物联网服务器发送该第四报文，该第四报文中包括该无源或半有源物联网指令的响应。
本申请实施例中，通过控制面通道传输无源或半有源物联网指令与无源或半有源物联 网指令的响应。控制面网元(或者网络功能)根据消息类型、信息类型、容器类型或者服务化接口，该消息与无源或半有源物联网操作相关，该消息需要使用第二协议进行处理。控制面网元(或者网络功能)获知来自RAN的该消息，需要转发至第一网元。通过上述方案，解决了无源或半有源物联网系统与蜂窝网络融合的场景中报文传输的问题。使得蜂窝网络可以解析无源或半有源物联网的应用报文，蜂窝网络中部署的网络功能(或者网元)可以根据该应用报文执行相关操作。
上述主要以方法的角度对本申请实施例提供的方案进行了介绍。可以理解的是，通信装置为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的模块及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对通信装置进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
下面对本申请中的通信装置进行详细描述，请参阅图14，图14为本申请实施例中通信装置的一种实施例示意图。通信装置可以部署于网络设备(接入网设备)，或芯片系统中，通信装置1400包括：收发模块1401和处理模块1402，其中，该通信装置1400可以用于图9b-图13中接入网设备执行的步骤，可以参考上述方法实施例中的相关描述。
具体的，收发模块1401，用于从物联网功能网元接收第一报文；
收发模块1401，还用于获取第一信息，第一信息指示第一报文包括无源或半有源物联网指令；
处理模块1402，用于根据第一报文执行无源或半有源物联网操作。
在一种实现方式中，该通信装置为网络设备，在一种实现方式中，所述处理模块1402可以是处理器，所述收发模块1401可以是收发器。
在另一种实现方式中，该网络设备为配置于网络设备中的芯片、芯片系统或电路。所述处理模块1402可以是处理器、处理电路或逻辑电路等。所述收发模块1401可以是该芯片、芯片系统或电路上的输入和/或输出接口、接口电路、输出电路、输入电路、管脚或相关电路等。可选的，上述“接收”还可以理解为“输入”。
在一种可能的实现方式中，第一信息包括以下一项或多项：第一报文的消息类型，第一报文的容器类型，第一报文的隧道标识信息，或者第一信息为第一报文的信息类型。
在一种可能的实现方式中，处理模块1402，还用于根据第一信息，采用第二协议处理第一报文，获取无源或半有源物联网指令。
在一种可能的实现方式中，收发模块1401，还用于获取无源或半有源物联网指令的响 应；
处理模块1402，还用于采用第二协议处理无源或半有源物联网指令的响应，生成第三报文；
收发模块1401，还用于向物联网功能网元发送第三报文。
在一种可能的实现方式中，收发模块1401，还用于向物联网功能网元发送第二信息，第二信息指示第三报文与无源或半有源物联网有关，或者第三报文需要使用第二协议进行处理。
在一种可能的实现方式中，第二信息包括以下一项或多项：第三报文的消息类型，第三报文的容器类型，第三报文的隧道标识信息，或者第二信息为第三报文的信息类型。
在一种可能的实现方式中，收发模块1401，还用于发送请求消息，请求消息用于建立第一会话；
第一会话的会话类型为无源或半有源物联网，或者，第一会话的会话标识指示第一会话与无源或半有源物联网有关；
收发模块1401，还用于通过第一会话接收物联网功能网元发送的第一报文。
在一种可能的实现方式中，收发模块1401，还用于通过第一会话向物联网功能网元发送第三报文。
在一种可能的实现方式中，第一信息还包括第一会话的会话类型，或者，第一会话的会话标识。
在一种可能的实现方式中，第二信息还包括第一会话的会话类型，或者，第一会话的会话标识。
在一种可能的实现方式中，物联网功能网元包括：用户面功能UPF、接入和移动性管理功能AMF、会话管理功能SMF、网络仓储功能NRF或者第一网元。
下面对本申请中的又一种通信装置进行详细描述，请参阅图15，图15为本申请实施例中通信装置的一种实施例示意图。通信装置1500可以部署于芯片系统中，通信装置1500包括：收发模块1501和处理模块1502，其中，该通信装置1500可以用于图9b-图13中物联网功能单元执行的步骤，可以参考上述方法实施例中的相关描述。
收发模块1501，用于向接入网设备发送第一报文，第一报文包括无源或半有源物联网指令；
收发模块1501，还用于向接入网设备发送第一信息，第一信息指示第一报文包括无源或半有源物联网指令，使能接入网设备执行无源或半有源物联网操作。
在一种可能的实现方式中，收发模块1501，还用于从无源或半有源物联网服务器接收第二报文；
处理模块1502，用于基于第二报文，生成第一报文，第一报文包括第二报文包括的无源或半有源物联网指令；
收发模块1501，还用于向接入网设备发送第一报文。
在一种实现方式中，该通信装置为网络设备，在一种实现方式中，所述处理模块1502可以是处理器，所述收发模块1501可以是收发器。
在另一种实现方式中，该网络设备为配置于网络设备中的芯片、芯片系统或电路。所述处理模块1502可以是处理器、处理电路或逻辑电路等。所述收发模块1501可以是该芯片、芯片系统或电路上的输入和/或输出接口、接口电路、输出电路、输入电路、管脚或相关电路等。可选的，上述“接收”还可以理解为“输入”。
在一种可能的实现方式中，处理模块1502，具体用于采用第一协议处理第二报文，生成第一中间数据；
处理模块1502，具体用于采用第二协议处理第一中间数据，生成第一报文。
在一种可能的实现方式中，收发模块1501，具体用于向第一网元发送第二报文；
收发模块1501，具体用于接收第一网元发送的第二中间数据，第二中间数据为第一网元采用第一协议和第二协议处理第二报文得到的数据；
处理模块1502，具体用于处理第二中间数据，生成第一报文。
在一种可能的实现方式中，收发模块1501，还用于接收来自接入网设备的第三报文；
收发模块1501，还用于获取第二信息，第二信息指示第三报文与无源或半有源物联网有关，或者第三报文需要使用第二协议进行处理；
处理模块1502，还用于根据第二信息，确定采用第二协议处理第三报文，生成第四报文；
第三报文和第四报文包括接入网设备获取的无源或半有源物联网指令的响应。
在一种可能的实现方式中，处理模块1502，还用于根据第一规则和/或第二规则基于第二报文，生成第一报文；
第一规则和/或第二规则由会话管理功能SMF配置，或者第一规则和/或第二规则预配置于用户面功能。
在一种可能的实现方式中，第二规则包括：报文转发规则，第一规则包括：流匹配规则。
在一种可能的实现方式中，收发模块1501，还用于通过第一会话向接入网设备发送第一报文，第一会话的会话类型为无源或半有源物联网；
或者，第一会话的会话标识指示第一会话与无源或半有源物联网有关。
在一种可能的实现方式中，第二信息还包括第一会话的会话类型，或者，第一会话的会话标识。
在一种可能的实现方式中，收发模块1501，还用于向第二网元发送订阅请求，订阅请求用于获取接入网设备信息；
接入网设备信息包括以下信息中的一项或多项：接入网设备的永久标识，服务接入网设备的核心网网元的信息，和接入网设备的读写器标识信息；
第二网元包括以下一个或多个：接入与移动管理功能AMF、会话管理功能SMF、统一数据管理功能UDM或者网络仓储功能NRF。
在一种可能的实现方式中，物联网功能网元包括：用户面功能UPF、接入和移动性管理功能AMF、会话管理功能SMF、网络仓储功能NRF或者第一网元。
在一种可能的实现方式中，第一信息包括以下一项或多项：第一报文的消息类型，第 一报文的容器类型，第一报文的隧道标识信息，或者第一报文的信息类型。
在一种可能的实现方式中，第二信息包括以下一项或多项：第三报文的消息类型，第三报文的容器类型，第三报文的隧道标识信息，或者第三报文的信息类型。
需要说明的是，对于通信装置的具体实现方式以及带来的有益效果，均可以参考图10a-图13对应的各个方法实施例中的叙述，此处不再一一赘述。
本申请实施例还提供了一种处理装置，处理装置包括处理器和接口；该处理器，用于执行上述任一方法实施例的一种报文传输方法。
应理解，上述处理装置可以是一个芯片，该处理器可以通过硬件实现也可以通过软件来实现，当通过硬件实现时，该处理器可以是逻辑电路、集成电路等；当通过软件来实现时，该处理器可以是一个通用处理器，通过读取存储器中存储的软件代码来实现，该存储器可以集成在处理器中，可以位于该处理器之外，独立存在。
其中，“通过硬件实现”是指通过不具有程序指令处理功能的硬件处理电路来实现上述模块或者单元的功能，该硬件处理电路可以通过分立的硬件元器件组成，也可以是集成电路。为了减少功耗、降低尺寸，通常会采用集成电路的形式来实现。硬件处理电路可以包括ASIC(application-specific integrated circuit，专用集成电路)，或者PLD(programmable logic device，可编程逻辑器件)；其中，PLD又可包括FPGA(field programmable gate array，现场可编程门阵列)、CPLD(complex programmable logic device，复杂可编程逻辑器件)等等。这些硬件处理电路可以是单独封装的一块半导体芯片(如封装成一个ASIC)；也可以跟其他电路(如CPU、DSP)集成在一起后封装成一个半导体芯片，例如，可以在一个硅基上形成多种硬件电路以及CPU，并单独封装成一个芯片，这种芯片也称为SoC，或者也可以在硅基上形成用于实现FPGA功能的电路以及CPU，并单独封闭成一个芯片，这种芯片也称为SoPC(system on a programmable chip，可编程片上系统)。
本申请还提供一种通信系统，其包括上述通信装置中的至少一种或多种。
本申请实施例还提供的一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得计算机控制通信装置执行如前述方法实施例所示任一项实现方式。
本申请实施例还提供的一种计算机程序产品，计算机程序产品包括计算机程序代码，当计算机程序代码在计算机上运行时，使得计算机执行如前述方法实施例所示任一项实现方式。
本申请实施例还提供一种芯片系统，包括存储器和处理器，存储器用于存储计算机程序，处理器用于从存储器中调用并运行计算机程序，使得芯片执行如前述方法实施例所示任一项实现方式。
本申请实施例还提供一种芯片系统，包括处理器，处理器用于调用并运行计算机程序，使得芯片执行如前述方法实施例所示任一项实现方式。
另外需说明的是，以上所描述的装置实施例仅仅是示意性的，其中所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。另外，本申请提供的装 置实施例附图中，模块之间的连接关系表示它们之间具有通信连接，具体可以实现为一条或多条通信总线或信号线。
通过以上的实施方式的描述，所属领域的技术人员可以清楚地了解到本申请可借助软件加必需的通用硬件的方式来实现，当然也可以通过专用硬件包括专用集成电路、专用CPU、专用存储器、专用元器件等来实现。一般情况下，凡由计算机程序完成的功能都可以很容易地用相应的硬件来实现，而且，用来实现同一功能的具体硬件结构也可以是多种多样的，例如模拟电路、数字电路或专用电路等。但是，对本申请而言更多情况下软件程序实现是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在可读取的存储介质中，如计算机的软盘、U盘、移动硬盘、ROM、RAM、磁碟或者光盘等，包括若干指令用以使得一台计算机设备执行本申请各个实施例所述的方法。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。
所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、通信装置、计算设备或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、通信装置、计算设备或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存储的任何可用介质或者是包含一个或多个可用介质集成的通信装置、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘(Solid State Disk，SSD))等。
应理解，说明书通篇中提到的“一个实施例”或“一实施例”意味着与实施例有关的特定特征、结构或特性包括在本申请的至少一个实施例中。因此，在整个说明书各处出现的“在一个实施例中”或“在一实施例中”未必一定指相同的实施例。此外，这些特定的特征、结构或特性可以任意适合的方式结合在一个或多个实施例中。应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、计算机软件或者二者的结合来实现，为了清楚地说明硬件和软件的可互换性，在上述说明中已经按照功能一般性地描述了各示例的组成及步骤。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为了描述的方便和简洁，上述描述的系统、 装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统，装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例方法的全部或部分步骤。

Claims (56)

  1. 一种报文传输方法，其特征在于，包括：
    接入网设备从物联网功能网元接收第一报文；
    所述接入网设备获取第一信息，所述第一信息指示所述第一报文包括无源或半有源物联网指令；
    所述接入网设备根据所述第一报文执行无源或半有源物联网操作。
  2. 根据权利要求1所述的方法，其特征在于，所述第一信息包括以下一项或多项：
    所述第一报文的消息类型，
    所述第一报文的容器类型，
    所述第一报文的隧道标识信息，或者，
    所述第一报文的信息类型。
  3. 根据权利要求1-2中任一项所述的方法，其特征在于，所述第一信息还包括以下一项或多项：用于传输所述第一报文的第一会话的会话类型，或者，所述第一会话的会话标识；
    其中，所述第一会话的会话类型为无源或半有源物联网，所述第一会话的会话标识指示所述第一会话与无源或半有源物联网有关。
  4. 根据权利要求1-3中任一项所述的方法，其特征在于，所述接入网设备根据所述第一报文执行所述无源或半有源物联网操作，包括：
    所述接入网设备根据所述第一信息，采用第二协议处理所述第一报文，获取无源或半有源物联网指令。
  5. 根据权利要求1-4中任一项所述的方法，其特征在于，所述方法还包括：
    所述接入网设备获取无源或半有源物联网指令的响应；
    所述接入网设备采用第二协议处理所述无源或半有源物联网指令的响应，生成第三报文；
    所述接入网设备向所述物联网功能网元发送所述第三报文。
  6. 根据权利要求5所述的方法，其特征在于，所述方法还包括：
    所述接入网设备向所述物联网功能网元发送第二信息；所述第二信息指示所述第三报文与无源或半有源物联网有关，或者所述第三报文需要使用所述第二协议进行处理。
  7. 根据权利要求6所述的方法，其特征在于，所述第二信息包括以下一项或多项：所述第三报文的消息类型，所述第三报文的容器类型，所述第三报文的隧道标识信息，所述第三报文的信息类型。
  8. 根据权利要求5-7中任一项所述的方法，其特征在于，所述第二信息包括以下一项或多项：
    第一会话的会话类型，或者，所述第一会话的会话标识，其中，所述第一会话用于传输所述第三报文，所述第一会话的会话类型为无源或半有源物联网，所述第一会话的会话标识指示所述第一会话与无源或半有源物联网有关。
  9. 根据权利要求1-8中任一项所述的方法，其特征在于，所述方法还包括：
    所述接入网设备发送请求消息，所述请求消息用于建立第一会话；
    所述第一会话的会话类型为无源或半有源物联网，或者，所述第一会话的会话标识指示所述第一会话与所述无源或半有源物联网有关；
    所述接入网设备从所述物联网功能网元接收所述第一报文，包括：
    所述接入网设备通过所述第一会话接收所述物联网功能网元发送的所述第一报文。
  10. 根据权利要求9所述的方法，其特征在于，所述接入网设备向所述物联网功能网元发送所述第三报文，包括：
    所述接入网设备通过所述第一会话向所述物联网功能网元发送所述第三报文。
  11. 根据权利要求1-10中任一项所述的方法，其特征在于，所述物联网功能网元包括：用户面功能UPF、接入和移动性管理功能AMF、会话管理功能SMF、网络仓储功能NRF或者第一网元。
  12. 一种报文传输方法，其特征在于，包括：
    物联网功能网元向接入网设备发送第一报文，所述第一报文包括无源或半有源物联网指令；
    所述物联网功能网元向所述接入网设备发送第一信息，所述第一信息指示所述第一报文包括所述无源或半有源物联网指令，使能所述接入网设备执行无源或半有源物联网操作。
  13. 根据权利要求12所述的方法，其特征在于，所述物联网功能网元向所述接入网设备发送所述第一报文，包括：
    所述物联网功能网元从无源或半有源物联网服务器接收第二报文；
    所述物联网功能网元基于所述第二报文，生成所述第一报文，所述第一报文包括所述第二报文包括的所述无源或半有源物联网指令；
    所述物联网功能网元向所述接入网设备发送所述第一报文。
  14. 根据权利要求13所述的方法，其特征在于，所述物联网功能网元基于所述第二报文，生成所述第一报文，包括：
    所述物联网功能网元采用第一协议处理所述第二报文，生成第一中间数据；
    所述物联网功能网元采用第二协议处理所述第一中间数据，生成所述第一报文。
  15. 根据权利要求14所述的方法，其特征在于，所述物联网功能网元基于所述第二报文，生成所述第一报文，包括：
    所述物联网功能网元向第一网元发送所述第二报文；
    所述物联网功能网元接收所述第一网元发送的第二中间数据，所述第二中间数据为所述第一网元采用第一协议和第二协议处理所述第二报文得到的数据；
    所述物联网功能网元处理所述第二中间数据，生成所述第一报文。
  16. 根据权利要求12-15中任一项所述的方法，其特征在于，所述方法还包括：
    所述物联网功能网元接收来自所述接入网设备的第三报文；
    所述物联网功能网元获取第二信息，所述第二信息指示所述第三报文与无源或半有源物联网有关，或者所述第三报文需要使用第二协议进行处理；
    所述物联网功能网元根据所述第二信息，采用所述第二协议处理所述第三报文，生成 第四报文；
    所述第三报文和所述第四报文包括所述无源或半有源物联网指令的响应。
  17. 根据权利要求12-16中任一项所述的方法，其特征在于，所述物联网功能网元为所述用户面功能，所述用户面功能基于所述第二报文，生成所述第一报文，包括：
    所述用户面功能根据第一规则和/或第二规则基于所述第二报文，生成所述第一报文；
    所述第一规则和/或所述第二规则由会话管理功能SMF配置，或者所述第一规则和/或所述第二规则预配置于所述用户面功能。
  18. 根据权利要求17所述的方法，其特征在于，所述第二规则包括：报文转发规则、所述第一规则包括流匹配规则。
  19. 根据权利要求12-18中任一项所述的方法，其特征在于，所述物联网功能网元向所述接入网设备发送所述第一报文，所述方法包括：
    所述物联网功能网元通过第一会话向所述接入网设备发送所述第一报文，所述第一会话的会话类型为无源或半有源物联网，或者，所述第一会话的会话标识指示所述第一会话与无源或半有源物联网有关。
  20. 根据权利要求12-19中任一项所述的方法，其特征在于，所述方法还包括：
    所述物联网功能网元向第二网元发送订阅请求，所述订阅请求用于获取所述接入网设备信息；
    所述接入网设备信息包括以下信息中的一项或多项：所述接入网设备的永久标识，服务所述接入网设备的核心网网元的信息，和所述接入网设备的读写器标识信息；
    所述第二网元包括以下一个或多个：接入与移动管理功能AMF、会话管理功能SMF、统一数据管理功能UDM或者网络仓储功能NRF。
  21. 根据权利要求12-20中任一项所述的方法，其特征在于，
    所述物联网功能网元包括：用户面功能UPF、接入和移动性管理功能AMF、会话管理功能SMF、网络仓储功能NRF或者第一网元。
  22. 根据权利要求12-21中任一项所述的方法，其特征在于，所述第一信息包括以下一项或多项：所述第一报文的消息类型，所述第一报文的容器类型，所述第一报文的隧道标识信息，或者所述第一报文的信息类型。
  23. 根据权利要求12-22中任一项所述的方法，其特征在于，所述第一信息包括以下一项或多项：
    第一会话的会话类型，或者，所述第一会话的会话标识，其中，所述第一会话用于传输所述第一报文，所述第一会话的会话类型为无源或半有源物联网，所述第一会话的会话标识指示所述第一会话与无源或半有源物联网有关。
  24. 根据权利要求16-23中任一项所述的方法，其特征在于，所述第二信息包括以下一项或多项：所述第三报文的消息类型，所述第三报文的容器类型，所述第三报文的隧道标识信息，或者所述第三报文的信息类型。
  25. 根据权利要求16-24中任一项所述的方法，其特征在于，所述第二信息还包括以下一项或多项：第一会话的会话类型，或者，所述第一会话的会话标识，其中，所述第一会 话用于传输所述第三报文，所述第一会话的会话类型为无源或半有源物联网，所述第一会话的会话标识指示所述第一会话与无源或半有源物联网有关。
  26. 一种通信装置，其特征在于，包括：
    收发模块，用于从物联网功能网元接收第一报文；
    所述收发模块，还用于获取第一信息，所述第一信息指示所述第一报文包括无源或半有源物联网指令；
    处理模块，用于根据所述第一报文执行无源或半有源物联网操作。
  27. 根据权利要求26所述的装置，其特征在于，所述第一信息包括以下一项或多项：
    所述第一报文的消息类型，
    所述第一报文的容器类型，
    所述第一报文的隧道标识信息，或者，
    所述第一报文的信息类型。
  28. 根据权利要求26-27中任一项所述的装置，其特征在于，所述第一信息还包括以下一项或多项：用于传输所述第一报文的第一会话的会话类型，或者，所述第一会话的会话标识；
    其中，所述第一会话的会话类型为无源或半有源物联网，所述第一会话的会话标识指示所述第一会话与无源或半有源物联网有关。
  29. 根据权利要求26-28中任一项所述的装置，其特征在于，
    所述处理模块，还用于根据所述第一信息，采用第二协议处理所述第一报文，获取无源或半有源物联网指令。
  30. 根据权利要求26-29中任一项所述的装置，其特征在于，
    所述收发模块，还用于获取无源或半有源物联网指令的响应；
    所述处理模块，还用于采用第二协议处理所述无源或半有源物联网指令的响应，生成第三报文；
    所述收发模块，还用于向所述物联网功能网元发送所述第三报文。
  31. 根据权利要求30所述的装置，其特征在于，
    所述收发模块，还用于向所述物联网功能网元发送第二信息；
    所述第二信息指示所述第三报文与无源或半有源物联网有关，或者所述第三报文需要使用所述第二协议进行处理。
  32. 根据权利要求31所述的装置，其特征在于，所述第二信息包括以下一项或多项：所述第三报文的消息类型，所述第三报文的容器类型，所述第三报文的隧道标识信息，所述第三报文的信息类型，
  33. 根据权利要求30-32中任一项所述的装置，其特征在于，所述第二信息包括以下一项或多项：
    第一会话的会话类型，或者，所述第一会话的会话标识，其中，所述第一会话用于传输所述第三报文，所述第一会话的会话类型为无源或半有源物联网，所述第一会话的会话标识指示所述第一会话与无源或半有源物联网有关。
  34. 根据权利要求26-33中任一项所述的装置，其特征在于，
    所述收发模块，还用于发送请求消息，所述请求消息用于建立第一会话；
    所述第一会话的会话类型为无源或半有源物联网，或者，所述第一会话的会话标识指示所述第一会话与所述无源或半有源物联网有关；
    所述收发模块，还用于通过所述第一会话接收所述物联网功能网元发送的所述第一报文。
  35. 根据权利要求34所述的装置，其特征在于，
    所述收发模块，还用于通过所述第一会话向所述物联网功能网元发送所述第三报文。
  36. 根据权利要求26-35中任一项所述的装置，其特征在于，所述物联网功能网元包括：用户面功能UPF、接入和移动性管理功能AMF、会话管理功能SMF、网络仓储功能NRF或者第一网元。
  37. 一种通信装置，其特征在于，包括：
    收发模块，用于向接入网设备发送第一报文，所述第一报文包括无源或半有源物联网指令；
    所述收发模块，还用于向所述接入网设备发送第一信息，所述第一信息指示所述第一报文包括所述无源或半有源物联网指令，使能所述接入网设备执行无源或半有源物联网操作。
  38. 根据权利要求37所述的装置，其特征在于，
    所述收发模块，还用于从无源或半有源物联网服务器接收第二报文；
    处理模块，用于根据所述第二报文，生成所述第一报文，所述第一报文包括所述第二报文包括的所述无源或半有源物联网指令；
    所述收发模块，还用于向所述接入网设备发送所述第一报文。
  39. 根据权利要求38所述的装置，其特征在于，
    所述处理模块，还用于采用第一协议处理所述第二报文，生成第一中间数据；
    所述处理模块，还用于采用第二协议处理所述第一中间数据，生成所述第一报文。
  40. 根据权利要求39所述的装置，其特征在于，
    所述收发模块，还用于向第一网元发送所述第二报文；
    所述收发模块，还用于接收所述第一网元发送的第二中间数据，所述第二中间数据为所述第一网元采用第一协议和第二协议处理所述第二报文得到的数据；
    所述处理模块，还用于处理所述第二中间数据，生成所述第一报文。
  41. 根据权利要求37-40中任一项所述的装置，其特征在于，
    所述收发模块，还用于接收来自所述接入网设备的第三报文；
    所述收发模块，还用于获取第二信息，所述第二信息指示所述第三报文与无源或半有源物联网有关，或者所述第三报文需要使用第二协议进行处理；
    所述处理模块，还用于根据所述第二信息，采用所述第二协议处理所述第三报文，生成第四报文；
    所述第三报文和所述第四报文包括所述无源或半有源物联网指令的响应。
  42. 根据权利要求37-41中任一项所述的装置，其特征在于，
    所述处理模块，还用于根据第一规则和/或第二规则基于所述第二报文，生成所述第一报文；
    所述第一规则和/或所述第二规则由会话管理功能SMF配置，或者所述第一规则和/或所述第二规则预配置于所述用户面功能。
  43. 根据权利要求42所述的装置，其特征在于，所述第二规则包括：报文转发规则、所述第一规则包括流匹配规则。
  44. 根据权利要求37-43中任一项所述的装置，其特征在于，
    所述收发模块，还用于通过第一会话向所述接入网设备发送所述第一报文，所述第一会话的会话类型为无源或半有源物联网，或者，所述第一会话的会话标识指示所述第一会话与无源或半有源物联网有关。
  45. 根据权利要求37-44中任一项所述的装置，其特征在于，
    所述收发模块，还用于向第二网元发送订阅请求，所述订阅请求用于获取所述接入网设备信息；
    所述接入网设备信息包括以下信息中的一项或多项：所述接入网设备的永久标识，服务所述接入网设备的核心网网元的信息，和所述接入网设备的读写器标识信息；
    所述第二网元包括以下一个或多个：接入与移动管理功能AMF、会话管理功能SMF、统一数据管理功能UDM或者网络仓储功能NRF。
  46. 根据权利要求37-45中任一项所述的装置，其特征在于，
    所述物联网功能网元包括：用户面功能UPF、接入和移动性管理功能AMF、会话管理功能SMF、网络仓储功能NRF或者第一网元。
  47. 根据权利要求37-46中任一项所述的装置，其特征在于，所述第一信息包括以下一项或多项：所述第一报文的消息类型，所述第一报文的容器类型，所述第一报文的隧道标识信息，或者所述第一报文的信息类型。
  48. 根据权利要求37-47中任一项所述的装置，其特征在于，所述第一信息包括以下一项或多项：
    第一会话的会话类型，或者，所述第一会话的会话标识，其中，所述第一会话用于传输所述第一报文，所述第一会话的会话类型为无源或半有源物联网，所述第一会话的会话标识指示所述第一会话与无源或半有源物联网有关。
  49. 根据权利要求41-48中任一项所述的装置，其特征在于，所述第二信息包括以下一项或多项：所述第三报文的消息类型，所述第三报文的容器类型，所述第三报文的隧道标识信息，或者所述第三报文的信息类型。
  50. 根据权利要求41-49中任一项所述的装置，其特征在于，所述第二信息还包括以下一项或多项：第一会话的会话类型，或者，所述第一会话的会话标识，其中，所述第一会话用于传输所述第三报文，所述第一会话的会话类型为无源或半有源物联网，所述第一会话的会话标识指示所述第一会话与无源或半有源物联网有关。
  51. 一种通信装置，其特征在于，所述通信装置包括：至少一个处理器；
    所述至少一个处理器，用于执行存储器中存储的计算机程序或指令，以使所述通信装置执行如权利要求1-25中任一项所述的方法。
  52. 一种通信装置，其特征在于，所述通信装置包括：至少一个处理器和存储器；
    所述存储器，用于存储计算机程序或指令；
    所述至少一个处理器，用于执行存储器中存储的计算机程序或指令，以使所述通信装置执行如权利要求1-25中任一项所述的方法。
  53. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质具有程序指令，当所述程序指令被直接或者间接执行时，使得如权利要求1-25中任一所述的方法被实现。
  54. 一种计算机程序产品，其特征在于，包括指令，当所述指令在计算机上运行时，使得计算机执行权利要求1-25中任一项所述的方法。
  55. 一种芯片系统，其特征在于，所述芯片系统包括至少一个处理器，所述处理器用于执行存储器中存储的计算机程序或指令，当所述计算机程序或所述指令在所述至少一个处理器中执行时，使得如权利要求1-25中任一所述的方法被实现。
  56. 一种通信系统，其特征在于，所述通信系统包括接入网设备和物联网功能网元，
    所述接入网设备用于实现权利要求1-11中任一项所述的方法；
    所述物联网功能网元用于实现权利要求12-25中任一项所述的方法。
PCT/CN2021/097471 2021-05-31 2021-05-31 一种报文传输方法以及相关装置 WO2022252076A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP21943452.9A EP4329420A1 (en) 2021-05-31 2021-05-31 Packet transmission method and related apparatus
PCT/CN2021/097471 WO2022252076A1 (zh) 2021-05-31 2021-05-31 一种报文传输方法以及相关装置
CN202180098430.XA CN117337614A (zh) 2021-05-31 2021-05-31 一种报文传输方法以及相关装置
US18/521,252 US20240098145A1 (en) 2021-05-31 2023-11-28 Packet transmission method and related apparatus

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/097471 WO2022252076A1 (zh) 2021-05-31 2021-05-31 一种报文传输方法以及相关装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/521,252 Continuation US20240098145A1 (en) 2021-05-31 2023-11-28 Packet transmission method and related apparatus

Publications (1)

Publication Number Publication Date
WO2022252076A1 true WO2022252076A1 (zh) 2022-12-08

Family

ID=84322660

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/097471 WO2022252076A1 (zh) 2021-05-31 2021-05-31 一种报文传输方法以及相关装置

Country Status (4)

Country Link
US (1) US20240098145A1 (zh)
EP (1) EP4329420A1 (zh)
CN (1) CN117337614A (zh)
WO (1) WO2022252076A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116308066A (zh) * 2023-05-10 2023-06-23 青岛创新奇智科技集团股份有限公司 基于物联网的仓储管理方法及装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104036303A (zh) * 2013-03-04 2014-09-10 中国移动通信集团广东有限公司 一种rfid中间件及其实现通信的方法
WO2017063427A1 (zh) * 2015-10-13 2017-04-20 中兴通讯股份有限公司 一种通信方法、装置及终端
US20190306251A1 (en) * 2018-03-30 2019-10-03 Peyman TALEBI FARD Data Transmission over User Plane for Cellular IoT
CN110808830A (zh) * 2019-10-21 2020-02-18 边缘智能研究院南京有限公司 一种基于5G网络切片的IoT安全验证框架及其服务方法
CN111758246A (zh) * 2018-02-20 2020-10-09 瑞典爱立信有限公司 用于蜂窝物联网（CIoT）的小数据用户平面传输

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104036303A (zh) * 2013-03-04 2014-09-10 中国移动通信集团广东有限公司 一种rfid中间件及其实现通信的方法
WO2017063427A1 (zh) * 2015-10-13 2017-04-20 中兴通讯股份有限公司 一种通信方法、装置及终端
CN111758246A (zh) * 2018-02-20 2020-10-09 瑞典爱立信有限公司 用于蜂窝物联网（CIoT）的小数据用户平面传输
US20190306251A1 (en) * 2018-03-30 2019-10-03 Peyman TALEBI FARD Data Transmission over User Plane for Cellular IoT
CN110808830A (zh) * 2019-10-21 2020-02-18 边缘智能研究院南京有限公司 一种基于5G网络切片的IoT安全验证框架及其服务方法

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on Cellular Internet of Things (CIoT) support and evolution for the 5G System (5GS) (Release 16)", 3GPP STANDARD; TECHNICAL REPORT; 3GPP TR 23.724, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. V16.1.0, 11 June 2019 (2019-06-11), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , pages 1 - 274, XP051753964 *
CORREIA RICARDO; CARVALHO NUNO BORGES: "Design of high order modulation backscatter wireless sensor for passive IoT solutions", 2016 IEEE WIRELESS POWER TRANSFER CONFERENCE (WPTC), IEEE, 5 May 2016 (2016-05-05), pages 1 - 3, XP032916219, DOI: 10.1109/WPT.2016.7498833 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116308066A (zh) * 2023-05-10 2023-06-23 青岛创新奇智科技集团股份有限公司 基于物联网的仓储管理方法及装置
CN116308066B (zh) * 2023-05-10 2023-08-18 青岛创新奇智科技集团股份有限公司 基于物联网的仓储管理方法及装置

Also Published As

Publication number Publication date
US20240098145A1 (en) 2024-03-21
EP4329420A1 (en) 2024-02-28
CN117337614A (zh) 2024-01-02

Similar Documents

Publication Publication Date Title
US20200296574A1 (en) Method and apparatus for accessing cellular network for sim profile
US20200322884A1 (en) Managing network enrollment and redirection for internet-of-things and like devices
US8634393B2 (en) Channel scanning in a network having one or more access points
WO2022110184A1 (zh) 一种通信方法、装置及系统
CN113748697A (zh) 用于提供非接入层(nas)消息保护的方法和系统
US20230345243A1 (en) Authentication method and communication apparatus
US20230362636A1 (en) Key identifier generation method and related apparatus
US20240098145A1 (en) Packet transmission method and related apparatus
CN114071510A (zh) 一种通信方法及装置
US20220225463A1 (en) Communications method, apparatus, and system
CN117204085A (zh) 一种信息传输方法、系统及装置
US10299310B2 (en) Wireless device including first platform for local area and second platform for remote area and method for wireless device
WO2023138198A1 (zh) 一种通信方法、装置和系统
WO2024067047A1 (zh) 一种通信方法及装置
WO2022251993A1 (zh) 一种标签的管理方法以及相关装置
JP7428265B2 (ja) 通信端末及びその方法
WO2024119498A1 (zh) 电子标签信息的传输方法、装置、设备及存储介质
WO2024067046A1 (zh) 一种通信方法及装置
WO2023142569A1 (zh) 一种通信方法、装置、可读存储介质和芯片系统
WO2024066436A1 (zh) 一种通信方法及装置
WO2022070546A1 (ja) コアネットワークノード、Ｕｓｅｒ Ｅｑｕｉｐｍｅｎｔ、及びこれらの方法
WO2024104246A1 (zh) 通信方法和通信装置
WO2023054194A1 (ja) 第１のノード、第２のノード、第１のノードによる方法、及び第２のノードによる方法
CN118075681A (zh) 一种通信方法和装置
WO2023147051A1 (en) Personal internet-of-things networks

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: 21943452

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 202180098430.X

Country of ref document: CN

WWE Wipo information: entry into national phase

Ref document number: 2021943452

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2021943452

Country of ref document: EP

Effective date: 20231124

NENP Non-entry into the national phase

Ref country code: DE