WO2022252076A1 - 一种报文传输方法以及相关装置 - Google Patents
一种报文传输方法以及相关装置 Download PDFInfo
- 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
Links
- 238000000034 method Methods 0.000 title claims abstract description 251
- 230000005540 biological transmission Effects 0.000 title claims abstract description 69
- 230000006870 function Effects 0.000 claims description 228
- 238000004891 communication Methods 0.000 claims description 152
- 230000008569 process Effects 0.000 claims description 135
- 230000004044 response Effects 0.000 claims description 96
- 238000007726 management method Methods 0.000 claims description 67
- 238000012545 processing Methods 0.000 claims description 66
- 230000015654 memory Effects 0.000 claims description 31
- 238000004590 computer program Methods 0.000 claims description 19
- 238000013523 data management Methods 0.000 claims description 10
- 230000001413 cellular effect Effects 0.000 abstract description 30
- 239000003795 chemical substances by application Substances 0.000 description 34
- 238000010586 diagram Methods 0.000 description 22
- 238000005516 engineering process Methods 0.000 description 13
- 230000011664 signaling Effects 0.000 description 9
- 101100321409 Rattus norvegicus Zdhhc23 gene Proteins 0.000 description 8
- 238000013475 authorization Methods 0.000 description 7
- 230000007774 longterm Effects 0.000 description 7
- 238000001514 detection method Methods 0.000 description 6
- 238000012384 transportation and delivery Methods 0.000 description 6
- 230000009471 action Effects 0.000 description 5
- 238000013461 design Methods 0.000 description 5
- 238000012790 confirmation Methods 0.000 description 4
- 238000010295 mobile communication Methods 0.000 description 4
- 230000005641 tunneling Effects 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000005538 encapsulation Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 239000004065 semiconductor Substances 0.000 description 3
- XUIMIQQOPSSXEZ-UHFFFAOYSA-N Silicon Chemical compound [Si] XUIMIQQOPSSXEZ-UHFFFAOYSA-N 0.000 description 2
- 230000003190 augmentative effect Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 238000001914 filtration Methods 0.000 description 2
- 230000014509 gene expression Effects 0.000 description 2
- 230000000977 initiatory effect Effects 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 238000003672 processing method Methods 0.000 description 2
- 229910052710 silicon Inorganic materials 0.000 description 2
- 239000010703 silicon Substances 0.000 description 2
- 239000007787 solid Substances 0.000 description 2
- 238000012795 verification Methods 0.000 description 2
- 101100240462 Homo sapiens RASAL2 gene Proteins 0.000 description 1
- 102100035410 Ras GTPase-activating protein nGAP Human genes 0.000 description 1
- 238000013528 artificial neural network Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 235000014510 cooky Nutrition 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 230000001537 neural effect Effects 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- XLYOFNOQVPJJNP-UHFFFAOYSA-N water Substances O XLYOFNOQVPJJNP-UHFFFAOYSA-N 0.000 description 1
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
Claims (56)
- 一种报文传输方法,其特征在于,包括:接入网设备从物联网功能网元接收第一报文;所述接入网设备获取第一信息,所述第一信息指示所述第一报文包括无源或半有源物联网指令;所述接入网设备根据所述第一报文执行无源或半有源物联网操作。
- 根据权利要求1所述的方法,其特征在于,所述第一信息包括以下一项或多项:所述第一报文的消息类型,所述第一报文的容器类型,所述第一报文的隧道标识信息,或者,所述第一报文的信息类型。
- 根据权利要求1-2中任一项所述的方法,其特征在于,所述第一信息还包括以下一项或多项:用于传输所述第一报文的第一会话的会话类型,或者,所述第一会话的会话标识;其中,所述第一会话的会话类型为无源或半有源物联网,所述第一会话的会话标识指示所述第一会话与无源或半有源物联网有关。
- 根据权利要求1-3中任一项所述的方法,其特征在于,所述接入网设备根据所述第一报文执行所述无源或半有源物联网操作,包括:所述接入网设备根据所述第一信息,采用第二协议处理所述第一报文,获取无源或半有源物联网指令。
- 根据权利要求1-4中任一项所述的方法,其特征在于,所述方法还包括:所述接入网设备获取无源或半有源物联网指令的响应;所述接入网设备采用第二协议处理所述无源或半有源物联网指令的响应,生成第三报文;所述接入网设备向所述物联网功能网元发送所述第三报文。
- 根据权利要求5所述的方法,其特征在于,所述方法还包括:所述接入网设备向所述物联网功能网元发送第二信息;所述第二信息指示所述第三报文与无源或半有源物联网有关,或者所述第三报文需要使用所述第二协议进行处理。
- 根据权利要求6所述的方法,其特征在于,所述第二信息包括以下一项或多项:所述第三报文的消息类型,所述第三报文的容器类型,所述第三报文的隧道标识信息,所述第三报文的信息类型。
- 根据权利要求5-7中任一项所述的方法,其特征在于,所述第二信息包括以下一项或多项:第一会话的会话类型,或者,所述第一会话的会话标识,其中,所述第一会话用于传输所述第三报文,所述第一会话的会话类型为无源或半有源物联网,所述第一会话的会话标识指示所述第一会话与无源或半有源物联网有关。
- 根据权利要求1-8中任一项所述的方法,其特征在于,所述方法还包括:所述接入网设备发送请求消息,所述请求消息用于建立第一会话;所述第一会话的会话类型为无源或半有源物联网,或者,所述第一会话的会话标识指示所述第一会话与所述无源或半有源物联网有关;所述接入网设备从所述物联网功能网元接收所述第一报文,包括:所述接入网设备通过所述第一会话接收所述物联网功能网元发送的所述第一报文。
- 根据权利要求9所述的方法,其特征在于,所述接入网设备向所述物联网功能网元发送所述第三报文,包括:所述接入网设备通过所述第一会话向所述物联网功能网元发送所述第三报文。
- 根据权利要求1-10中任一项所述的方法,其特征在于,所述物联网功能网元包括:用户面功能UPF、接入和移动性管理功能AMF、会话管理功能SMF、网络仓储功能NRF或者第一网元。
- 一种报文传输方法,其特征在于,包括:物联网功能网元向接入网设备发送第一报文,所述第一报文包括无源或半有源物联网指令;所述物联网功能网元向所述接入网设备发送第一信息,所述第一信息指示所述第一报文包括所述无源或半有源物联网指令,使能所述接入网设备执行无源或半有源物联网操作。
- 根据权利要求12所述的方法,其特征在于,所述物联网功能网元向所述接入网设备发送所述第一报文,包括:所述物联网功能网元从无源或半有源物联网服务器接收第二报文;所述物联网功能网元基于所述第二报文,生成所述第一报文,所述第一报文包括所述第二报文包括的所述无源或半有源物联网指令;所述物联网功能网元向所述接入网设备发送所述第一报文。
- 根据权利要求13所述的方法,其特征在于,所述物联网功能网元基于所述第二报文,生成所述第一报文,包括:所述物联网功能网元采用第一协议处理所述第二报文,生成第一中间数据;所述物联网功能网元采用第二协议处理所述第一中间数据,生成所述第一报文。
- 根据权利要求14所述的方法,其特征在于,所述物联网功能网元基于所述第二报文,生成所述第一报文,包括:所述物联网功能网元向第一网元发送所述第二报文;所述物联网功能网元接收所述第一网元发送的第二中间数据,所述第二中间数据为所述第一网元采用第一协议和第二协议处理所述第二报文得到的数据;所述物联网功能网元处理所述第二中间数据,生成所述第一报文。
- 根据权利要求12-15中任一项所述的方法,其特征在于,所述方法还包括:所述物联网功能网元接收来自所述接入网设备的第三报文;所述物联网功能网元获取第二信息,所述第二信息指示所述第三报文与无源或半有源物联网有关,或者所述第三报文需要使用第二协议进行处理;所述物联网功能网元根据所述第二信息,采用所述第二协议处理所述第三报文,生成 第四报文;所述第三报文和所述第四报文包括所述无源或半有源物联网指令的响应。
- 根据权利要求12-16中任一项所述的方法,其特征在于,所述物联网功能网元为所述用户面功能,所述用户面功能基于所述第二报文,生成所述第一报文,包括:所述用户面功能根据第一规则和/或第二规则基于所述第二报文,生成所述第一报文;所述第一规则和/或所述第二规则由会话管理功能SMF配置,或者所述第一规则和/或所述第二规则预配置于所述用户面功能。
- 根据权利要求17所述的方法,其特征在于,所述第二规则包括:报文转发规则、所述第一规则包括流匹配规则。
- 根据权利要求12-18中任一项所述的方法,其特征在于,所述物联网功能网元向所述接入网设备发送所述第一报文,所述方法包括:所述物联网功能网元通过第一会话向所述接入网设备发送所述第一报文,所述第一会话的会话类型为无源或半有源物联网,或者,所述第一会话的会话标识指示所述第一会话与无源或半有源物联网有关。
- 根据权利要求12-19中任一项所述的方法,其特征在于,所述方法还包括:所述物联网功能网元向第二网元发送订阅请求,所述订阅请求用于获取所述接入网设备信息;所述接入网设备信息包括以下信息中的一项或多项:所述接入网设备的永久标识,服务所述接入网设备的核心网网元的信息,和所述接入网设备的读写器标识信息;所述第二网元包括以下一个或多个:接入与移动管理功能AMF、会话管理功能SMF、统一数据管理功能UDM或者网络仓储功能NRF。
- 根据权利要求12-20中任一项所述的方法,其特征在于,所述物联网功能网元包括:用户面功能UPF、接入和移动性管理功能AMF、会话管理功能SMF、网络仓储功能NRF或者第一网元。
- 根据权利要求12-21中任一项所述的方法,其特征在于,所述第一信息包括以下一项或多项:所述第一报文的消息类型,所述第一报文的容器类型,所述第一报文的隧道标识信息,或者所述第一报文的信息类型。
- 根据权利要求12-22中任一项所述的方法,其特征在于,所述第一信息包括以下一项或多项:第一会话的会话类型,或者,所述第一会话的会话标识,其中,所述第一会话用于传输所述第一报文,所述第一会话的会话类型为无源或半有源物联网,所述第一会话的会话标识指示所述第一会话与无源或半有源物联网有关。
- 根据权利要求16-23中任一项所述的方法,其特征在于,所述第二信息包括以下一项或多项:所述第三报文的消息类型,所述第三报文的容器类型,所述第三报文的隧道标识信息,或者所述第三报文的信息类型。
- 根据权利要求16-24中任一项所述的方法,其特征在于,所述第二信息还包括以下一项或多项:第一会话的会话类型,或者,所述第一会话的会话标识,其中,所述第一会 话用于传输所述第三报文,所述第一会话的会话类型为无源或半有源物联网,所述第一会话的会话标识指示所述第一会话与无源或半有源物联网有关。
- 一种通信装置,其特征在于,包括:收发模块,用于从物联网功能网元接收第一报文;所述收发模块,还用于获取第一信息,所述第一信息指示所述第一报文包括无源或半有源物联网指令;处理模块,用于根据所述第一报文执行无源或半有源物联网操作。
- 根据权利要求26所述的装置,其特征在于,所述第一信息包括以下一项或多项:所述第一报文的消息类型,所述第一报文的容器类型,所述第一报文的隧道标识信息,或者,所述第一报文的信息类型。
- 根据权利要求26-27中任一项所述的装置,其特征在于,所述第一信息还包括以下一项或多项:用于传输所述第一报文的第一会话的会话类型,或者,所述第一会话的会话标识;其中,所述第一会话的会话类型为无源或半有源物联网,所述第一会话的会话标识指示所述第一会话与无源或半有源物联网有关。
- 根据权利要求26-28中任一项所述的装置,其特征在于,所述处理模块,还用于根据所述第一信息,采用第二协议处理所述第一报文,获取无源或半有源物联网指令。
- 根据权利要求26-29中任一项所述的装置,其特征在于,所述收发模块,还用于获取无源或半有源物联网指令的响应;所述处理模块,还用于采用第二协议处理所述无源或半有源物联网指令的响应,生成第三报文;所述收发模块,还用于向所述物联网功能网元发送所述第三报文。
- 根据权利要求30所述的装置,其特征在于,所述收发模块,还用于向所述物联网功能网元发送第二信息;所述第二信息指示所述第三报文与无源或半有源物联网有关,或者所述第三报文需要使用所述第二协议进行处理。
- 根据权利要求31所述的装置,其特征在于,所述第二信息包括以下一项或多项:所述第三报文的消息类型,所述第三报文的容器类型,所述第三报文的隧道标识信息,所述第三报文的信息类型,
- 根据权利要求30-32中任一项所述的装置,其特征在于,所述第二信息包括以下一项或多项:第一会话的会话类型,或者,所述第一会话的会话标识,其中,所述第一会话用于传输所述第三报文,所述第一会话的会话类型为无源或半有源物联网,所述第一会话的会话标识指示所述第一会话与无源或半有源物联网有关。
- 根据权利要求26-33中任一项所述的装置,其特征在于,所述收发模块,还用于发送请求消息,所述请求消息用于建立第一会话;所述第一会话的会话类型为无源或半有源物联网,或者,所述第一会话的会话标识指示所述第一会话与所述无源或半有源物联网有关;所述收发模块,还用于通过所述第一会话接收所述物联网功能网元发送的所述第一报文。
- 根据权利要求34所述的装置,其特征在于,所述收发模块,还用于通过所述第一会话向所述物联网功能网元发送所述第三报文。
- 根据权利要求26-35中任一项所述的装置,其特征在于,所述物联网功能网元包括:用户面功能UPF、接入和移动性管理功能AMF、会话管理功能SMF、网络仓储功能NRF或者第一网元。
- 一种通信装置,其特征在于,包括:收发模块,用于向接入网设备发送第一报文,所述第一报文包括无源或半有源物联网指令;所述收发模块,还用于向所述接入网设备发送第一信息,所述第一信息指示所述第一报文包括所述无源或半有源物联网指令,使能所述接入网设备执行无源或半有源物联网操作。
- 根据权利要求37所述的装置,其特征在于,所述收发模块,还用于从无源或半有源物联网服务器接收第二报文;处理模块,用于根据所述第二报文,生成所述第一报文,所述第一报文包括所述第二报文包括的所述无源或半有源物联网指令;所述收发模块,还用于向所述接入网设备发送所述第一报文。
- 根据权利要求38所述的装置,其特征在于,所述处理模块,还用于采用第一协议处理所述第二报文,生成第一中间数据;所述处理模块,还用于采用第二协议处理所述第一中间数据,生成所述第一报文。
- 根据权利要求39所述的装置,其特征在于,所述收发模块,还用于向第一网元发送所述第二报文;所述收发模块,还用于接收所述第一网元发送的第二中间数据,所述第二中间数据为所述第一网元采用第一协议和第二协议处理所述第二报文得到的数据;所述处理模块,还用于处理所述第二中间数据,生成所述第一报文。
- 根据权利要求37-40中任一项所述的装置,其特征在于,所述收发模块,还用于接收来自所述接入网设备的第三报文;所述收发模块,还用于获取第二信息,所述第二信息指示所述第三报文与无源或半有源物联网有关,或者所述第三报文需要使用第二协议进行处理;所述处理模块,还用于根据所述第二信息,采用所述第二协议处理所述第三报文,生成第四报文;所述第三报文和所述第四报文包括所述无源或半有源物联网指令的响应。
- 根据权利要求37-41中任一项所述的装置,其特征在于,所述处理模块,还用于根据第一规则和/或第二规则基于所述第二报文,生成所述第一报文;所述第一规则和/或所述第二规则由会话管理功能SMF配置,或者所述第一规则和/或所述第二规则预配置于所述用户面功能。
- 根据权利要求42所述的装置,其特征在于,所述第二规则包括:报文转发规则、所述第一规则包括流匹配规则。
- 根据权利要求37-43中任一项所述的装置,其特征在于,所述收发模块,还用于通过第一会话向所述接入网设备发送所述第一报文,所述第一会话的会话类型为无源或半有源物联网,或者,所述第一会话的会话标识指示所述第一会话与无源或半有源物联网有关。
- 根据权利要求37-44中任一项所述的装置,其特征在于,所述收发模块,还用于向第二网元发送订阅请求,所述订阅请求用于获取所述接入网设备信息;所述接入网设备信息包括以下信息中的一项或多项:所述接入网设备的永久标识,服务所述接入网设备的核心网网元的信息,和所述接入网设备的读写器标识信息;所述第二网元包括以下一个或多个:接入与移动管理功能AMF、会话管理功能SMF、统一数据管理功能UDM或者网络仓储功能NRF。
- 根据权利要求37-45中任一项所述的装置,其特征在于,所述物联网功能网元包括:用户面功能UPF、接入和移动性管理功能AMF、会话管理功能SMF、网络仓储功能NRF或者第一网元。
- 根据权利要求37-46中任一项所述的装置,其特征在于,所述第一信息包括以下一项或多项:所述第一报文的消息类型,所述第一报文的容器类型,所述第一报文的隧道标识信息,或者所述第一报文的信息类型。
- 根据权利要求37-47中任一项所述的装置,其特征在于,所述第一信息包括以下一项或多项:第一会话的会话类型,或者,所述第一会话的会话标识,其中,所述第一会话用于传输所述第一报文,所述第一会话的会话类型为无源或半有源物联网,所述第一会话的会话标识指示所述第一会话与无源或半有源物联网有关。
- 根据权利要求41-48中任一项所述的装置,其特征在于,所述第二信息包括以下一项或多项:所述第三报文的消息类型,所述第三报文的容器类型,所述第三报文的隧道标识信息,或者所述第三报文的信息类型。
- 根据权利要求41-49中任一项所述的装置,其特征在于,所述第二信息还包括以下一项或多项:第一会话的会话类型,或者,所述第一会话的会话标识,其中,所述第一会话用于传输所述第三报文,所述第一会话的会话类型为无源或半有源物联网,所述第一会话的会话标识指示所述第一会话与无源或半有源物联网有关。
- 一种通信装置,其特征在于,所述通信装置包括:至少一个处理器;所述至少一个处理器,用于执行存储器中存储的计算机程序或指令,以使所述通信装置执行如权利要求1-25中任一项所述的方法。
- 一种通信装置,其特征在于,所述通信装置包括:至少一个处理器和存储器;所述存储器,用于存储计算机程序或指令;所述至少一个处理器,用于执行存储器中存储的计算机程序或指令,以使所述通信装置执行如权利要求1-25中任一项所述的方法。
- 一种计算机可读存储介质,其特征在于,所述计算机可读存储介质具有程序指令,当所述程序指令被直接或者间接执行时,使得如权利要求1-25中任一所述的方法被实现。
- 一种计算机程序产品,其特征在于,包括指令,当所述指令在计算机上运行时,使得计算机执行权利要求1-25中任一项所述的方法。
- 一种芯片系统,其特征在于,所述芯片系统包括至少一个处理器,所述处理器用于执行存储器中存储的计算机程序或指令,当所述计算机程序或所述指令在所述至少一个处理器中执行时,使得如权利要求1-25中任一所述的方法被实现。
- 一种通信系统,其特征在于,所述通信系统包括接入网设备和物联网功能网元,所述接入网设备用于实现权利要求1-11中任一项所述的方法;所述物联网功能网元用于实现权利要求12-25中任一项所述的方法。
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2021/097471 WO2022252076A1 (zh) | 2021-05-31 | 2021-05-31 | 一种报文传输方法以及相关装置 |
EP21943452.9A EP4329420A4 (en) | 2021-05-31 | 2021-05-31 | PACKET TRANSMISSION METHOD AND ASSOCIATED DEVICE |
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) | EP4329420A4 (zh) |
CN (1) | CN117337614A (zh) |
WO (1) | WO2022252076A1 (zh) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN116308066A (zh) * | 2023-05-10 | 2023-06-23 | 青岛创新奇智科技集团股份有限公司 | 基于物联网的仓储管理方法及装置 |
Citations (5)
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)的小数据用户平面传输 |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CA3020155A1 (en) * | 2016-04-05 | 2017-10-12 | Wellaware Holdings, Inc. | A device for monitoring and controlling industrial equipment |
-
2021
- 2021-05-31 WO PCT/CN2021/097471 patent/WO2022252076A1/zh active Application Filing
- 2021-05-31 CN CN202180098430.XA patent/CN117337614A/zh active Pending
- 2021-05-31 EP EP21943452.9A patent/EP4329420A4/en active Pending
-
2023
- 2023-11-28 US US18/521,252 patent/US20240098145A1/en active Pending
Patent Citations (5)
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 (3)
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 * |
See also references of EP4329420A4 * |
Cited By (2)
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 |
---|---|
EP4329420A1 (en) | 2024-02-28 |
CN117337614A (zh) | 2024-01-02 |
US20240098145A1 (en) | 2024-03-21 |
EP4329420A4 (en) | 2024-06-26 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20200296574A1 (en) | Method and apparatus for accessing cellular network for sim profile | |
US11445435B2 (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 | |
CN113748697B (zh) | 用于提供非接入层(nas)消息保护的方法和系统 | |
WO2022110184A1 (zh) | 一种通信方法、装置及系统 | |
WO2022251993A1 (zh) | 一种标签的管理方法以及相关装置 | |
US20230345243A1 (en) | Authentication method and communication apparatus | |
US20230362636A1 (en) | Key identifier generation method and related apparatus | |
CN117204085A (zh) | 一种信息传输方法、系统及装置 | |
CN114071510A (zh) | 一种通信方法及装置 | |
US20240098145A1 (en) | Packet transmission method and related apparatus | |
JP7428265B2 (ja) | 通信端末及びその方法 | |
US20220225463A1 (en) | Communications method, apparatus, and system | |
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) | 一种通信方法及装置 | |
WO2024119498A1 (zh) | 电子标签信息的传输方法、装置、设备及存储介质 | |
WO2024067046A1 (zh) | 一种通信方法及装置 | |
WO2023142569A1 (zh) | 一种通信方法、装置、可读存储介质和芯片系统 | |
WO2024066436A1 (zh) | 一种通信方法及装置 | |
WO2022070546A1 (ja) | コアネットワークノード、User Equipment、及びこれらの方法 | |
US20240251239A1 (en) | Technologies for non-seamless wireless local area access offload | |
WO2024104246A1 (zh) | 通信方法和通信装置 | |
WO2023054194A1 (ja) | 第1のノード、第2のノード、第1のノードによる方法、及び第2のノードによる方法 | |
CN118075681A (zh) | 一种通信方法和装置 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 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 |