WO2021184783A1 - 实现网络能力开放的方法、装置、电子设备和存储介质 - Google Patents

实现网络能力开放的方法、装置、电子设备和存储介质 Download PDF

Info

Publication number
WO2021184783A1
WO2021184783A1 PCT/CN2020/128209 CN2020128209W WO2021184783A1 WO 2021184783 A1 WO2021184783 A1 WO 2021184783A1 CN 2020128209 W CN2020128209 W CN 2020128209W WO 2021184783 A1 WO2021184783 A1 WO 2021184783A1
Authority
WO
WIPO (PCT)
Prior art keywords
network information
network
packet
option
information
Prior art date
Application number
PCT/CN2020/128209
Other languages
English (en)
French (fr)
Inventor
熊春山
Original Assignee
腾讯科技（深圳）有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 腾讯科技（深圳）有限公司 filed Critical 腾讯科技（深圳）有限公司
Priority to EP20925912.6A priority Critical patent/EP4017073A4/en
Publication of WO2021184783A1 publication Critical patent/WO2021184783A1/zh
Priority to US17/674,349 priority patent/US20220174477A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/75—Media network packet handling
    • H04L65/752—Media network packet handling adapting media to network capabilities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/80—Responding to QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H04W28/065—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information using assembly or disassembly of packets
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters

Definitions

  • This application relates to communication technology, and relates to a method and device for realizing network capability opening, electronic equipment, and computer-readable storage medium.
  • the opening of network capabilities in related technologies is all based on the control plane.
  • the opening of network capabilities based on the control plane cannot be applied to the opening of real-time changes and low-latency network capabilities.
  • the embodiments of the present application provide a method and device, electronic equipment, and computer-readable storage medium for realizing network capability opening, which realizes the opening of network capabilities through the user plane, and can support real-time change and low-latency network capability opening.
  • the embodiment of the present application provides a method for achieving network capability opening.
  • the method includes: obtaining a downlink data packet, where the downlink data packet includes a network information acquisition request; sending the downlink data packet to a target user plane node; receiving a return from the target user plane node The response information in response to the network information acquisition request, where the response information includes the network information requested by the network information acquisition request.
  • the embodiment of the present application provides a method for realizing network capability opening.
  • the method includes: receiving a downlink data packet sent by an application server, wherein the downlink data packet includes a network information acquisition request; in response to the network information acquisition request, generating response information, wherein, The response information includes the network information requested by the network information acquisition request; the response information is sent to the application server.
  • An embodiment of the present application provides a device for implementing network capability opening.
  • the device includes: a downlink data acquisition unit configured to acquire a downlink data packet, wherein the downlink data packet includes a network information acquisition request; a downlink data sending unit configured to transmit the downlink data The packet is sent to the target user plane node; the response information receiving unit is configured to receive response information returned by the target user plane node in response to the network information acquisition request, wherein the response information includes the network information requested by the network information acquisition request.
  • An embodiment of the present application provides a device for implementing network capability opening.
  • the device includes: a downlink data receiving unit configured to receive a downlink data packet sent by an application server, wherein the downlink data packet includes a network information acquisition request; a response information generating unit, configured In order to generate response information in response to the network information acquisition request, the response information includes the network information requested by the network information acquisition request; the response information sending unit is configured to send the response information to the application server.
  • the embodiment of the present application provides a computer-readable storage medium on which a computer program is stored.
  • the program is executed by a processor, the method for implementing network capability opening in the above-mentioned embodiment is implemented.
  • An embodiment of the present application provides an electronic device, including: one or more processors; a storage device, configured to store one or more programs, and when one or more programs are executed by one or more processors, one Or multiple processors implement the method for implementing network capability opening as in the foregoing embodiment.
  • network information is obtained through user plane nodes.
  • the network information since the network information only adds a small portion of user plane data, the impact on the entire system is very small; on the other hand, on the one hand, since the time delay of user plane data transmission is very small, it can support real-time change and low-latency network capability opening.
  • Figure 1 shows a schematic diagram of the architecture of network capability opening defined by 4G in related technologies
  • Figure 2 shows a schematic diagram of the architecture of 5G network capability opening in related technologies
  • Figure 3 shows a schematic diagram of a service-based architecture in related technologies
  • Figure 4 shows a schematic diagram of the CAPIF architecture in related technologies
  • Figure 5 shows a schematic diagram of an EC architecture and network capability opening requirements in related technologies
  • Figure 6 shows a schematic diagram of an EC architecture and network capability opening requirements in related technologies
  • Fig. 7 schematically shows a flowchart of a method for implementing network capability opening according to an embodiment of the present application
  • FIG. 8 shows a schematic diagram of the processing process of step S710 shown in FIG. 7 in an embodiment
  • FIG. 9 shows a schematic diagram of the processing process of step S710 shown in FIG. 7 in an embodiment
  • FIG. 10 shows a schematic diagram of the processing process of step S710 shown in FIG. 7 in an embodiment
  • FIG. 11 schematically shows a schematic diagram of an architecture of user plane-based in-band network capability opening according to an embodiment of the present application
  • FIG. 12 schematically shows a schematic flowchart of an application server obtaining network information based on UPF according to an embodiment of the present application
  • FIG. 13 schematically shows a schematic flow chart of obtaining network information through UPF according to an embodiment of the present application
  • FIG. 14 schematically shows a schematic flow chart of an application server obtaining network information based on RAN according to an embodiment of the present application
  • FIG. 15 schematically shows a schematic flow chart of obtaining network information through RAN according to an embodiment of the present application
  • FIG. 16 schematically shows a schematic flowchart of an application server obtaining network information based on a UE according to an embodiment of the present application
  • FIG. 17 schematically shows a schematic flow chart of obtaining network information through a UE according to an embodiment of the present application
  • FIG. 18 schematically shows a flowchart of a method for implementing network capability opening according to an embodiment of the present application
  • FIG. 19 shows a schematic diagram of the processing process of step S182 shown in FIG. 18 in an embodiment
  • FIG. 20 shows a schematic diagram of the processing procedure of step S182 shown in FIG. 18 in an embodiment
  • FIG. 21 shows a schematic diagram of the processing process of step S182 shown in FIG. 18 in an embodiment
  • FIG. 22 shows a schematic diagram of the processing process of step S182 shown in FIG. 18 in an embodiment
  • FIG. 23 shows a schematic diagram of the processing process of step S182 shown in FIG. 18 in an embodiment
  • FIG. 24 schematically shows a block diagram of an apparatus for implementing network capability opening according to an embodiment of the present application
  • Fig. 25 schematically shows a block diagram of an apparatus for implementing network capability opening according to an embodiment of the present application.
  • the process described below with reference to the flowchart can be implemented as a computer software program.
  • the embodiments of the present application include a computer program product, which includes a computer program carried on a computer-readable storage medium, and the computer program contains program code for executing the method shown in the flowchart.
  • the computer-readable storage medium shown in the embodiments of the present application may be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two.
  • the embodiments of the present application also provide a computer-readable storage medium.
  • the computer-readable storage medium may be included in the electronic device described in the above embodiment; or it may exist alone without being assembled into the electronic device .
  • the foregoing computer-readable storage medium carries one or more programs, and when the foregoing one or more programs are executed by an electronic device, the electronic device is caused to implement the method in the following embodiments. For example, the electronic device can implement the steps shown in FIGS. 6-9 and 17-22.
  • Figure 1 shows a schematic diagram of the architecture of network capability opening defined by 4G (the 4th generation mobile communication technology).
  • Inter-communication architecture enhancements Architecture enhancements to facilitate communications with packet data networks and applications
  • Figure 1 shows 3GPP's architecture for Service Capability Exposure, so that the 3GPP network can safely open its services and capabilities to hosting an Application(s) through 3GPP network interfaces (interfaces) ) External third-party service provider service capability server/application server (Services Capability Server/Application Server, SCS/AS).
  • SCS/AS Service Capability Server/Application Server
  • the 3GPP protocol TS23.682 also defines the network capability open architecture and interfaces in roaming situations.
  • the 3GPP protocol TS23.682 defines many network capability openings that support M2M communication, such as: device trigger, group message delivery, and monitoring ), high latency communications (HLC), etc., are almost in all M2M functions and processes defined in the 3GPP protocol TS23.682.
  • the SDO in Figure 1 is the abbreviation of Service Data Objects, that is, the service data object.
  • API is the abbreviation of Application Program Interface, that is, application program interface.
  • n is a positive integer greater than or equal to 1.
  • the full English name of Service Capability Exposure Function is Service Capability Exposure Function, abbreviated as SCEF.
  • SCEF Service Capability Exposure Function
  • HSS is the abbreviation of Home Subscriber Server, that is, home subscriber server.
  • PCRF is the abbreviation of Policy and Charging Rules Function, which is the function of policy and charging rules.
  • PFDF is the abbreviation of Packet Flow Description Function, that is, the packet flow description function.
  • MME Mobility Management Entity
  • SGSN is the abbreviation of Serving GPRS (General Packet Radio Service, General Packet Radio Service) Support Node, that is, Serving GPRS Support Node.
  • BM-SC is a node that controls MBMS (Multimedia Broadcast/Multicast Service, Multimedia Broadcast/Multicast Service) sessions.
  • S-CSCF is the abbreviation of Service-Call Session Control Function, that is, service-call session control function.
  • RCAF is the abbreviation of RAN (Radio Access Network) Congestion Awareness Function, and it is the wireless congestion awareness function.
  • the English corresponding to the network entity is Network Entity.
  • T6a refers to the reference point used between SCEF and the serving MME.
  • T6b refers to the reference point used between the SCEF and the serving SGSN.
  • T8 refers to the reference point used between SCEF and SCS/AS.
  • S6t refers to the reference point used between SCEF and HSS.
  • Rx refers to the reference point used by SCEF and PCRF. The function of the Rx reference point can be found in TS23.203.
  • Ns refers to the reference point used between SCEF and RCAF.
  • Nt refers to the reference point used by SCEF and PCRF.
  • Nu refers to the reference point used by SCEF to interact with PFDF.
  • Figure 2 shows a schematic diagram of the architecture of 5G network capability opening.
  • the 3GPP protocol TS23.501 defines the capability opening architecture as shown in Figure 2 (Non-roaming architecture for Network Exposure Function in reference point representation).
  • the open architecture of 5G network capabilities has evolved from 4G.
  • NEF Network Exposure Function
  • AF Application Function
  • N33 interface is based on the service-based interface defined by 5G.
  • the external exposure of network capability in the 3GPP protocol TS23.501 provides some basic network capability openings.
  • the network exposure of TS23.502 provides some basic use cases and procedures for network capability exposure.
  • NF in Figure 2 is the abbreviation of Network Function, that is, network function.
  • Figure 3 shows a schematic diagram of a service-based architecture.
  • the 5G architecture introduces a service-based interface (service-based interface) architecture.
  • service-based interface service-based interface
  • the advantage of service-based architecture (SBA) is that a network function entity only pays attention to the service it provides, and this service can be used by any other network function.
  • NF entity is used, so that the service can be atomized, and the scalability of the 5G system is improved.
  • NWDAF Network Data Analytics Function
  • UE User Equipment
  • UE communication information UE communication information
  • Expected UE behavioral parameters UE abnormal behavior information
  • User data congestion information User data congestion information
  • Quality of Service (QoS) sustainability etc. 10
  • NWDAF can open the features analyzed above to AF or any other NF (such as access and mobility management function (Access and Mobility Management Function, AMF), session management function (Session Management Function, SMF).
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • 3GPP protocol TS23.288 standardizes the signaling interaction and opening process of NWDAF's network data analysis.
  • the NSSF in Figure 3 is the abbreviation of Network Slice Selection Function, that is, the network slice selection function, and Nnssf refers to the Nnssf message sent to the NSSF.
  • Nnef refers to the Nnef message sent to NEF.
  • NRF is the abbreviation of Network Respository Function, that is, network storage function.
  • Nnrf refers to the Nnrf message sent to NRF.
  • PCF is the abbreviation of Policy Control Function, that is, policy control function.
  • Npcf refers to the Npcf message sent to the PCF.
  • UDM is the abbreviation of Unified Data Management, that is, unified data management.
  • Nudm refers to the Nudm message sent to UDM.
  • Naf refers to the Naf message sent to AF.
  • Namf refers to the Namf message sent to AMF.
  • Nsmf refers to the Nsmf message sent to SMF.
  • Nnwdaf refers to the Nnwdaf message sent to NWDAF.
  • AUSF is the abbreviation of Authentication Server Function, that is, the authentication server function.
  • Nausf refers to the Nausf message sent to AUSF.
  • SCP is the abbreviation of Service Communication Proxy, that is, service communication proxy.
  • UPF is the abbreviation of User Plane Function, that is, the user plane function.
  • DN is the abbreviation of Data Network, that is, data network.
  • the UE and AMF interact through the N1 interface, between AMF and RAN through the N2 interface, between SMF and UPF through the N4 interface, between RAN and UPF through the N3 interface, and between UPF and DN through the N6 interface.
  • the UPF interacts through the N9 interface.
  • FIG 4 shows a schematic diagram of the architecture of a common API framework (CAPIF).
  • CAPIF common API framework
  • the general framework technology CAPIF for network capability opening is defined in the 3GPP protocol TS23.222.
  • API is used to indicate the network capability opening, but the original language in communication is used to represent it, as shown in Figure 4.
  • CAPIF defines the following general functions for network capability opening: release and implementation of service API; security; OAM; onboarding; configuration; interconnection; identification; routing; registration and other functions.
  • service API release and implementation of service API
  • OAM onboarding
  • configuration configuration
  • interconnection identification
  • routing registration and other functions.
  • 3GPP Protocol TS23.222 3GPP Protocol TS23.222.
  • the public land mobile network (Public Land Mobile Network, PLMN) trust zone refers to an entity that is controlled by a PLMN operator or a trusted third party of the PLMN and is protected by adequate security.
  • CAPIF is hosted in the PLMN operator network.
  • the API invoker is usually provided by a third-party application provider that has a service agreement with the PLMN operator.
  • the API invoker can be located in the same trust zone as the PLMN operator network.
  • the API invoker in the PLMN trust zone interacts with CAPIF through CAPIF-1 and CAPIF-2.
  • the API invoker from outside the PLMN trust zone interacts with CAPIF through CAPIF-1e and CAPIF-2e.
  • API exposure function API exposure function
  • API publishing function APIpulishing function
  • API management function API management function
  • edge computing The basic definition of edge computing (EC) is given in the 3GPP protocol TS23.501.
  • EAS Edge Application Server
  • PSA Packet Data Unit
  • UPF User Plane Data Unit
  • the 3GPP protocol TR23.748 defines the architecture of the two EC implementations shown in Figure 5 and Figure 6. Among them, the EC architecture of the application layer is defined in the 3GPP protocol TR23.758.
  • the 3GPP agreements TR23.748 and TR23.758 define EC from different dimensions and complement each other.
  • the EC architecture of the 3GPP protocol TR23.748 is used as an example of the solution baseline, but this application is not limited to this. In other embodiments, it can also be extended to adapt to the 3GPP protocol TR23. 758 EC architecture.
  • Figure 5 shows the use of Uplink Classifier/Branching Point (UL CL/BP) to access EAS.
  • Figure 6 shows that UL CL/BP is not used to access EAS.
  • UL CL/BP Uplink Classifier/Branching Point
  • the network capability openings used are all based on the control plane.
  • the control plane is used to carry signaling or control messages.
  • the opposite is the user plane.
  • the user plane is also called the data plane or the forwarding plane, which carries data traffic.
  • control plane-based solution is an out-of-band solution, that is, when EAS/AS communicates with UE, EAS/AS generally needs to interact with NEF or SCEF through AF to obtain 5G or 4G network some information.
  • This method has the following disadvantages:
  • EAS/AS either has an AF function by itself or has an interface to interact with AF, requiring AF to interact with 4G or 5G networks.
  • EAS/AS does not have this function. Therefore, the scope of application of this method is greatly reduced.
  • the 4G or 5G network cannot transfer the function of this AF.
  • the request is associated with the Internet Protocol (IP) data of the UE currently being applied on the wireless network.
  • IP Internet Protocol
  • the 4G or 5G network cannot perceive which QoS flow (QoS flow) or evolved packet system of the UE is related to the request of this AF.
  • EPS Evolved Packet System
  • IP flow information due to the existence of Network Address Translation (NAT) in the network; and due to the short lifetime of some IP flows, EAS/AS can continuously release the old ones. IP flow and the establishment of a new IP flow to realize the transmission of some small files (such as various small object files on the web page). Therefore, it is difficult for AF to keep up with the dynamic changes of this IP flow. If the life cycle of an IP flow is long, the above AF method may be effective.
  • NAT Network Address Translation
  • the wireless base station Since the network status of wireless communication changes rapidly, if the wireless base station is allowed to report the change of its transmission rate, it may cause a lot of control plane signaling. In this case, the out-of-band solution is also not suitable for this kind of real-time change, low-latency (low-latency) network capability opening.
  • EAS/AS can adjust the real-time downlink rate according to the bandwidth of the wireless network (such as in games, video, ultra-high-definition voice, etc.), thereby reducing the freeze time and number of freezes applied on the UE, and improving the quality of user experience ( Quality of Experience, QoE).
  • QoE Quality of Experience
  • Fig. 7 schematically shows a flowchart of a method for implementing network capability opening according to an embodiment of the present application.
  • the method provided in the embodiments of the present application can be executed by any electronic device with computing and processing capabilities, such as the application server AS or the edge application server EAS.
  • the capability abstracts the complex implementation of the underlying layer and provides a development and execution environment externally.
  • Capability opening can be regarded as a novel network open mode in essence.
  • the network capability opening platform adopts a unified multi-level open interface to open telecommunications capabilities, gathers potential and creative developers on the Internet, and allows developers to continuously use these capabilities. To create better commercial applications and services, and form a large number of new mobile Internet applications and services.
  • the method for implementing network capability opening may include the following steps.
  • step S710 a downlink data packet is acquired, where the downlink data packet includes a network information acquisition request.
  • the network information acquisition request refers to EAS/AS (also expressed as (E)AS, that is, EAS or AS) sent, and is used to obtain the requested request from the target user plane node Network information request.
  • EAS/AS also expressed as (E)AS, that is, EAS or AS
  • step S720 the downlink data packet is sent to the target user plane node.
  • the EAS/AS can determine which user plane node is the current target user plane node according to the network information currently requested.
  • the user plane node here refers to a node used to carry data traffic, and its corresponding is a control plane node, which refers to a node used to carry signaling or control messages.
  • control plane nodes can be different.
  • control plane nodes can include MME, HSS, PCRF, and can also include SGW-C and PGW-C, where SGW stands for Service Gateway, and SGW-C stands for SGW-Control, which means control Plane service gateway; PGW is PDN (Public Data Network) GateWay, PDN gateway or packet gateway, PGW-C refers to PGW-Control, that is, control plane packet gateway; the user plane node part is included in SGW and PGW, It can also be SGW-U and PGW-U.
  • SGW Service Gateway
  • SGW-C stands for SGW-Control, which means control Plane service gateway
  • PGW is PDN (Public Data Network) GateWay, PDN gateway or packet gateway
  • PGW-C refers to PGW-Control, that is, control plane packet gateway
  • the user plane node part is included in SGW and PGW, It can also be SGW-U and PGW-U.
  • the user plane node may include a terminal (UE), a radio access network (RAN, referred to as a base station here), and a user plane gateway (UPF (User Plane Function) is taken as an example for illustration here.
  • UE terminal
  • RAN radio access network
  • UPF User Plane Function
  • the embodiment of the present application is not limited to this
  • the UPF here can be an I-UPF, or a PSA UPF, and a suitable UPF can be used according to different situations.
  • the target user plane node is any one of UE, RAN, and UPF for illustration, but the embodiment of the present application is not limited to this.
  • UPF is responsible for forwarding traffic between the wireless access network and the Internet, reporting traffic usage, QoS policy implementation, etc., corresponding to the user plane of SGW/PGW in 4G.
  • Control plane nodes can include AMF, SMF, PCF, UDM, AUSF, NEF, NRF, NSSF, etc.
  • step S730 receive response information returned by the target user plane node in response to the network information acquisition request, where the response information includes the network information requested by the network information acquisition request.
  • the method may further include: If it is detected that the length of the network information in the response information returned by the terminal exceeds the preset threshold, it switches to using the user plane gateway or the base station to return the network information requested by the network information acquisition request.
  • ICMP Internet Control Message Protocol
  • the method for implementing network capability opening obtained by the embodiments of the present application obtains network information through user plane nodes.
  • network information since network information only adds a small portion of user plane data, the impact on the entire system is very small; on the other hand, , Since the time delay of user plane data transmission is very small, it can support real-time change and low-latency network capability opening.
  • IP protocol The Internet Protocol
  • IP version 4 Internet Protocol version 4
  • RRC Request For Comments
  • IPv4 IP header (Header, can also be called frame header), the options (Options) included in the IP header are as follows.
  • the options may appear or not in datagrams. They must be implemented by all IP modules(host and gateways). What is optional is their transmission in any particular datagram, not their implementation. // These options may appear in the datagram, also May not appear in the datagram. They must be implemented by all IP modules (host and gateway). What is optional is their transmission in any particular datagram, not their implementation.
  • the security option may be required in all datagrams. //In some environments, all datagrams may require security options.
  • the option field is variable in length. There may be zero or more options. There are two cases for the format of an option://The length of the option field is variable. There may be zero or more options. There are two cases for the format of the option:
  • Case 1 A single octet of option-type. // Case 1: A single 8-bit byte of option type.
  • Case 2 An option-type octet, an option-length octet, and the actual option-data octets. // Case 2: Option type 8 bytes, option length 8 bytes, and actual option data 8 bytes.
  • the option-length octet counts the option-type octet and the option-length octet as well as the option-data octets.//The option length is 8 bits and the option type is 8 bits and the option length is 8 bits and the options are The data is 8-bit bytes.
  • option-type octet is viewed as having 3fields://option-type 8-bit bytes are considered to have 3 fields:
  • the copied flag indicators that this option is copied into all fragments on fragmentation.//The copied flag indicates that this option is copied to all fragments of the fragment.
  • the option classes are: The option classes are:
  • IP Options is a total length of one byte, or option type (Option-Type, 1 byte) + option length (Option-Length, 1 byte) + option data (Option Data, 1-38 bytes), that is Option type + option length + option data.
  • option-Type 1 byte
  • option length Option-Length, 1 byte
  • option data Option Data, 1-38 bytes
  • the 8 bits (8 bits, 1 byte) of Option-Type are divided into 3 parts: copied flag (1 bit), option class (2 bits), option number (5 bits).
  • IPv4 Option-Type used for experimental is listed, as shown below.
  • IPv4 Option Numbers (in-parameters initial section) (Section 2.5)//IPv4 option number (in the parameter initial section) (Section 2.5)
  • 3GPP can apply for a dedicated Option-Type from IANA (The Internet Assigned Numbers Authority) (when the method provided in this application embodiment enters the standard). Or 3GPP can continue to use the experimental value defined by RFC 4727 (but there may be conflicts when other IP applications use this experimental value).
  • IANA The Internet Assigned Numbers Authority
  • IPv6 two Option-Types 253 and 254 are defined in RFC 3296 as experimental use. I won't do a detailed explanation here. The following embodiments are described using IPv4, and the same method can also be applied to IPv6.
  • FIG. 8 shows a schematic diagram of the processing process of step S710 shown in FIG. 7 in an embodiment. As shown in FIG. 8, the above step S710 in the embodiment of the present application may further include the following steps.
  • step S711 first downlink data to be sent is acquired, where the first downlink data to be sent includes an Internet Protocol header (Internet Protocol Header, IP frame header or IP header).
  • Internet Protocol header Internet Protocol Header, IP frame header or IP header.
  • the first downlink data to be sent may be any data currently prepared by the EAS/AS or that needs to be sent to the UE.
  • the IP packet includes an IP Header.
  • step S712 an internetwork protocol option is added to the first internetwork protocol frame header of the downlink data to be sent.
  • the IP Option is added to the IP Header of the first IP packet of downlink data to be sent.
  • step S713 a network information acquisition request is written in the data area of the Internet Protocol option of the first downlink data to be sent, so as to generate a downlink data packet.
  • the Data area or part of the IP Option of the IP Header of the first IP packet to be sent downstream data is written in the above-mentioned network information acquisition request to be sent to the target user plane node to generate and send to the target user plane.
  • Downlink data packet of the node is written in the above-mentioned network information acquisition request to be sent to the target user plane node to generate and send to the target user plane.
  • IPv4 Header is shown in Table 1 below:
  • DF is the abbreviation of Don't Fragment label, that is, do not split the label, which means that the data packet is not allowed to be split. If the length of the packet exceeds the processing capacity of the network device and the DF label is added, then The network device will discard the packet.
  • MF is the More Fragments tag, which is used to indicate whether the packet is fragmented. If it is fragmented, the bit is 1, and if it is not fragmented, the bit is 0.
  • the length of the downlink data packet includes the first downlink data to be sent after the encryption and integrity protection processing + Integrity protection message authentication code (message authentication code, MAC).
  • the byte length provided by an IP Option is sufficient for the EAS or AS to send a control command (for example, the downlink data packet including the network information acquisition request) to the target user plane node. If EAS or AS sends a downlink data packet including the above network information acquisition request to the target user plane node, the length of 40 bytes provided by an IP Option is not enough.
  • the first one or two words in the IP Option data is defined as the current location of the data, that is, as a data pointer of the network information acquisition request data, which divides the provided network information acquisition request into the IP Option of multiple IP packets .
  • the receiver can implement data reorganization through the data pointer. However, if one IP packet in the middle is lost, the entire data may not be reorganized successfully. In this case, EAS or AS will need to resend the downlink data packet including the network information acquisition request.
  • EAS or AS can also use the Data part or area of the ICMP ECHO packet to send the above network information acquisition request.
  • Transmission control protocol is the most widely used transport layer protocol.
  • RFC 793 note that TCP does not distinguish between IPv4 or IPv6, there is only one
  • the Options included in the TCP header are defined as follows.
  • Options mayoccupy space at the end of the TCP header and are a multiple of 8 bits in length.All options are included in the checksum.An option may begin on any octet of boundary.There are two options for the format: The / option may occupy the space at the beginning and end of the TCP frame, and the length is a multiple of 8 bits. All options are included in the checksum. Options can start at any octal boundary. There are two cases for the format of the option:
  • Case 1 a single octet of option-kind. // Case 1: A single 8-bit byte of option type.
  • Case 2 an octet of option-kind, an octet of option-length, and the actual option-data octets. // Case 2: An 8-bit byte of option type, an 8-bit byte of option length and actual option Multiple 8-bit bytes of data.
  • the option-length counts the two octets of option-kind and option-length as well as the option-data octets. // Option length counts two 8-bit bytes of option type and option length and multiple 8-bits of option data byte.
  • the list of options may be shorter than the data offset field might imply.
  • the content of the header beyond the End-of-option option must be header padding(ie,zero).//Please note that the option list may be shorter than possible
  • the implied data offset field should be short.
  • the content of the frame beginning of the option beyond the end of the option must be frame beginning padding (for example, zero).
  • a TCP must implement all options. //TCP must implement all options.
  • TCP Option is a total length of one byte, or option-kind+option-length+option data, that is, option type + option length + option data, which is very similar to the above-mentioned IPv4 Option.
  • 3GPP can apply to IANA for a dedicated option-kind (when the method provided in the embodiments of this application enters the standard). 3GPP can continue to use the experimental values defined in RFC 4727 (at this time, the RFC 6994 protocol needs to be used, see the following content).
  • ExID experiment identifier
  • the ExID is used to differentiate, first as and after Lol: //This document uses the experiment identifier (ExID) to extend the option structure of the experiment code point (253, 254), and the length of the identifier is 2 or 4 bytes. ExID is used to distinguish experiments and is the first field after type and length, as shown below:
  • RFC 6994 introduces an ExID at the beginning of option-data (length can be 2 bytes or 4 Byte), so that the probability of conflict between two applications is greatly reduced.
  • the application can declare the ExID used to IANA, so that other IP applications can no longer use the ExID of this application, which further reduces the possibility of conflicts.
  • 3GPP can continue to use the experimental values defined in RFC 4727, or apply for a dedicated ExID from IANA (when the method provided in the embodiments of this application enters the standard).
  • a TCP header option can transmit up to 38 bytes of content.
  • FIG. 9 shows a schematic diagram of the processing process of step S710 shown in FIG. 7 in an embodiment.
  • step S710 in the embodiment of the present application may further include the following steps.
  • step S714 the second downlink data to be sent is acquired, and the second downlink data to be sent includes the transmission control protocol frame header.
  • the second downlink data to be sent may be any data currently prepared by the EAS/AS or that needs to be sent to the UE.
  • the TCP packet includes a TCP Header.
  • step S715 a transmission control protocol option is added to the first transmission control protocol frame of the second downlink data to be sent.
  • TCP Option is added to the TCP Header of the TCP packet of the second downlink data to be sent.
  • step S716 a network information acquisition request is written in the data area of the transmission control protocol option of the second downlink data to be sent, so as to generate a downlink data packet.
  • the data area or part of the TCP Option of the TCP Header of the TCP packet of the second downlink data to be sent is written into the network information acquisition request to be sent to the target user plane node to generate and send to the target user plane.
  • Downlink data packet of the node is written into the network information acquisition request to be sent to the target user plane node to generate and send to the target user plane.
  • TCP Header is shown in Table 2 below:
  • URG is the abbreviation of urgent, emergency bit
  • ACK is the abbreviation of acknowledgement, confirmation bit
  • PSH is the abbreviation of push, push bit
  • RST is the abbreviation of reset, reset bit
  • SYN is the abbreviation of synchronization, request bit
  • FIN is the abbreviation of finish, the end bit.
  • the length of the downlink data packet includes the second downlink data to be sent after the encryption and integrity protection processing + Integrity protection MAC.
  • MAC can take 8 bytes or 4 bytes.
  • the byte length provided by a TCP Option is sufficient for the EAS or AS to send a control command (for example, the downlink data packet including the network information acquisition request) to the target user plane node. If EAS or AS sends a downlink data packet including the above network information acquisition request to the target user plane node, the length of 40 bytes provided by a TCP Option is not enough.
  • the first one or two words in the TCP Option data is defined as the current location of the data, that is, as a data pointer of the network information acquisition request data, which divides the provided network information acquisition request into the TCP Option of multiple TCP packets .
  • the TCP protocol can finally realize the reordering of TCP packets, it can indirectly ensure that the receiver sequentially receives the network capability opening data (including the downlink data packets of the network information acquisition request mentioned above, including the TCP during transmission. Packet loss, which is better than IP option).
  • EAS or AS can also use the Data part or area of the ICMP ECHO packet to send the above network information acquisition request.
  • this method may still have the above multiple transmission problem for a long downlink network information acquisition request. For this reason, for the case where the length of the network information acquisition request is> 38 bytes, instead of waiting for the available first or second downlink data to be sent, the method of directly adopting the Data part or area of the ICMP ECHO packet mentioned above is not used. , Data is used to transmit network information acquisition requests.
  • TCP empty packets that send one or more ACKs (that is, packets that do not transmit actual user data), and transmit part of the data with open network capabilities in each TCP empty packet, so that no TCP connection will be caused.
  • some TCP protocol stacks will repeat the TCP empty packet (that is, the ACK number of the TCP packet) unchanged for three times, and EAS/AS will reduce the rate at which the actual TCP data packet is sent to the UE, which will affect the user experience.
  • IPv4 ICMP see RFC792
  • ICMPv4 ECHO and ECHO reply to transmit data with open network capabilities
  • the transmission efficiency can be greatly increased, and the functions of sorting and reorganization can be realized.
  • Echo or Echo Reply Message Message:// Echo or echo response message
  • the identifier and sequence number may be used by the echo sender to aid in matching the replies with the ECHOs.
  • the identifier might be used like a port in TCP or UDP to be identified a session, and the number be identified in the right sequence each ECHO sent.
  • the echoer returns these same values in the echo reply.
  • the echo sender can use the identifier and sequence number to help match the echo response with the echo request.
  • the identifier can be used to identify the session like a port in TCP or UDP, and the sequence number can be incremented on each echo request sent. The echoer returns these same values in the echo response.
  • the embodiment of this application also proposes to use the option in the IP header of ICMP ECHO to transmit data (only 38 bytes can be transmitted).
  • the IP packet (including ECHO with ICMP) is called IP Dummy (IP simulation) package, but not to be confused with the method of using the Data in ICMP ECHO to transmit network information acquisition requests or network information data.
  • the specification does not arbitrarily limit the identifier and sequence number (SN) of ECHO. However, the identifier and SN of ECHO reply must take the same values of identifier and SN as the corresponding ECHO.
  • the embodiment in FIG. 10 describes the use of dummy IP packets and ICMP to realize data transmission for opening network capabilities.
  • FIG. 10 shows a schematic diagram of the processing process of step S710 shown in FIG. 7 in an embodiment. As shown in FIG. 10, the above step S710 in the embodiment of the present application may further include the following steps.
  • step S717 a downlink dummy data packet is generated, and the downlink dummy data packet includes an Internet Protocol frame header.
  • the IP header is 20 bytes and the ICMP 8-byte header (including the above Type, Code, Checksum, Identifier, Sequence Number).
  • ICMP 8-byte header including the above Type, Code, Checksum, Identifier, Sequence Number.
  • Extended Header extended header
  • step S718 an internet protocol option is added to the internet protocol frame header of the downlink analog data packet.
  • EAS or AS sends a downlink data packet including the above network information acquisition request to a target user plane node such as UE/RAN/UPF
  • a target user plane node such as UE/RAN/UPF
  • One solution is to wait until there is first downlink data to be sent or second downlink data to be sent, but there may be no first downlink data to be sent or second downlink data to be sent for a long time.
  • the method of generating a DL dummy IP packet is adopted, and the DL dummy IP option is used to transmit the data related to the network information acquisition request.
  • step S719 a network information acquisition request is written in the data area of the Internet Protocol option of the downlink simulated data packet for generating the downlink data packet.
  • a DL dummy IP packet is generated (for example, in the following embodiment, the DL dummy IP packet is an ICMP ECHO packet as an example for illustration, but the embodiment of this application is not limited to this): use (one or more times) to send The ECHO of ICMP, and the identifier in the ECHO sent each time is set to a port number of UDP or TCP, and the SN is set to an increasing sequence number.
  • the UE/RAN/UPF can reply to EAS/AS a corresponding ECHO reply indicating that the receipt is confirmed.
  • EAS /AS can compare the SN of the received ECHO Reply with the identifier and the SN of the ECHO with the identifier. If both are the same, it indicates that the UE/RAN/UPF has received the ICMP ECHO packet. In this way, the IP header of the ICMP ECHO packet.
  • the above option data (including the aforementioned network information acquisition request) is received by the target user plane node such as UE/RAN/UPF. If the ECHO Reply from the target user plane node is not received within the predetermined time, EAS/AS will resend this ECHO again and include the corresponding network information acquisition request in the option of the IP header. The retransmitted ECHO is the same as the previous one.
  • the SN is consistent with the identifier.
  • the method of the foregoing embodiment is still inefficient, because each DL dummy IP option, IP option, or TCP option can only transmit 38 bytes of content. Therefore, in some embodiments, another method can also be used.
  • the network information acquisition request data can be sent out as the Data part of the ECHO, and the transmission efficiency at this time is much greater than only transmitting 38 words each time Section DL dummy IP option or IP option or TCP option method, and at the same time, ID + SN, and the method of adding 1 to SN can be used to achieve multiple ECHO transmissions: no ECHO Reply( is received within a certain period of time By comparing ID+SN to confirm whether it has been received), the ECHO is retransmitted again (in the retransmission, the ID+SN value is the ID+SN value of the retransmitted ECHO packet), so as to achieve the reliability and reliability of the network acquisition request. Transfer in order. Because the SN of a
  • the data length of the network capability opening does not exceed 38 bytes (note that if the encryption and integrity protection processing is performed, the MAC after encryption and integrity processing is also included.
  • the following embodiment is the same as this)
  • the data length of the network capability opening exceeds 38 bytes and is less than 1472 bytes, you can run the ICMP ECHO and ECHO reply methods once.
  • the method of ICMP ECHO and ECHO reply with increasing SN number can be run multiple times to achieve reliable and orderly transmission of network information acquisition requests.
  • UE radio base station (RAN, radio access network) or PSA
  • SGW user plane service gateway
  • SGW-User user plane service gateway
  • GGSN intermediate UPF (intermediate-UPF, I-UPF), UPF, PGW, user All PDN gateways (PGW-User, PGW-U)
  • a constant user plane node such as UE and PSA (ie, UPF) or PGW-U is given as an example here.
  • the base station (RAN) is taken as an example to show how the mobile node continues to provide network capabilities to EAS or AS.
  • FIG. 11 schematically shows an architecture diagram of in-band network capability opening based on a user plane according to an embodiment of the present application.
  • EAS1/2/3 is an application server deployed in an edge computing environment. EAS1/2/3 respectively communicate with UE, RAN and UPF for open network capabilities.
  • edge computing environment only represents a platform for AS that implements edge computing. During the standardization phase, this name may change.
  • AS4 here refers to Internet applications. It can be the operator’s own business or a third-party AS (such as a search engine company’s server, a certain Internet company’s game game server). In Figure 11, only AS4 and UPF are shown. The interaction of network capability opening, but the embodiment of this application is not limited to this. AS4 can also interact with UE, RAN, and UPF just like EAS1/2/3.
  • AS or EAS can interact with UE, RAN, and UPF for network capabilities.
  • the UE/RAN/UPF can interact with these NFs (such as AMF, SMF) interact and obtain from these NFs. If there is no direct interaction interface between the UE/RAN/UPF and these NFs, the UE and the RAN can use AMF, and the UPF can be obtained from other NFs through SMF.
  • NFs such as AMF, SMF
  • other non-user plane nodes of the network open some key network capabilities to EAS or AS through network nodes such as UE, base station, PSA (PGW/PGW-U, GGSN), etc.
  • network nodes such as UE, base station, PSA (PGW/PGW-U, GGSN), etc.
  • PGW/PGW-U, GGSN PSA
  • GGSN GGSN
  • other NFs can provide network information to EAS or AS through SMF or AMF.
  • EAS or AS Since the uplink data of IP and TCP data reach EAS or AS directly, and the downlink data of EAS or AS reach PSA, base station and UE directly, EAS or AS can directly interact with them to realize the in-Band capability. It is open and the data of the network capability only adds a small part of the user-plane data, which has a very small impact on the entire system, and the transmission delay of the user-plane data is very small.
  • Fig. 12 schematically shows a flow chart of an application server obtaining network information based on UPF according to an embodiment of the present application.
  • Figure 12 illustrates that UPF uses ICMP/IP option/TCP option to realize the transmission of requested network information.
  • Figure 12 may include the following steps.
  • step S1 the UE establishes a PDU session (session) and is assigned an IP address.
  • An IP connection is established with the (E)AS through this IP address, and the transmitted IP stream can reach the (E)AS through the RAN and UPF.
  • Step S2 It is assumed here that the (E)AS decides to request network information from the UPF and sends a network information acquisition request to the UPF.
  • the (E)AS decides who is requested to provide network information, which is determined according to the currently requested network information. For example, if the requested network information is related to an application or a terminal, the UE may be requested to provide network information. If the requested network information is wireless-related information, the RAN can be requested to provide network information. If the requested network information does not fall into the above two cases, you can request the UPF to provide network information.
  • Step S3 this step is optional.
  • E Mutual authentication is performed between AS and UPF, and the security algorithm (shared algorithm) and the use of a common security key (shared key) are negotiated.
  • the secure interactive transmission mode of encryption and integrity protection processing between (E)AS and UPF is taken as an example for illustration.
  • Step S4 Generate a DL dummy IP packet or add an option to the IP header or TCP header of the DL data.
  • the data area of the option contains request information.
  • Request Information refers to information related to the network information acquisition request, for example It can include who is currently requesting network information (Target ID, Request Type, Request parameters).
  • Request Type refers to which type of network information is currently requested, and Request parameters refers to some other parameters for requesting network information. According to The requested network information is determined.
  • the (E)AS can add option to the downstream IP header, or if the downstream IP packet is still a TCP packet, it can add Option to the TCP header instead .
  • (E)AS can generate a DL dummy IP packet (such as ICMP ECHO, note that there is no specific content in the DATA part of ICMP ECHO at this time) or TCP null Packet (only TCP header without any user data).
  • a DL dummy IP packet such as ICMP ECHO, note that there is no specific content in the DATA part of ICMP ECHO at this time
  • TCP null Packet only TCP header without any user data
  • the (E)AS can also wait until there are downlink data packets, and then continue to perform the following steps.
  • Step S5a if the above step S4 adopts adding Option to the IP header of the DL to transmit the network information acquisition request, the (E)AS can send a DL IP data packet to the UPF.
  • the DL IP data packet carries the Option option and is in the IP
  • the data part of the Option includes (Option-Type, Target ID, Request Type, Request parameters, MAC).
  • Option-Type can adopt the 30/94/158/222 mentioned above or use a specific value applied for by 3GPP on IANA.
  • Target ID ( UPF).
  • the above step S3 determines that the network capability opening interaction requires encryption and integrity protection.
  • Step S5b if the IP packet is a TCP packet, the (E)AS decides to use TCP option to transmit the network information acquisition request, that is, the above step S4 uses the option to add Option to the TCP header of the DL to transmit the network information acquisition request, then (E) The AS may send a DL TCP data packet to the UPF.
  • the DL TCP data packet has Option options, and the data part of the TCP Option includes (Option-kind, Target ID, Request Type, Request parameters, MAC). For Option-kind, see 253/254 in the example above or use a specific value applied by 3GPP on IANA, and an ExID (RFC 6994, the same below) can be used.
  • the data processing in TCP Option is the same as step S5a.
  • Step S6 After receiving the DL IP packet or DL TCP packet sent by the (E)AS, the UPF checks the DL IP packet or DL TCP packet as follows:
  • IPv4 Option-type
  • TCP Option-kind
  • the MAC in the DL IP packet or DL TCP packet is used for security verification. If the security verification is passed, continue with the following steps; if the security verification is not passed, then stop performing the steps.
  • Step S7 the UPF deletes the corresponding options in the DL IP or TCP packets, and then sends them in the downlink direction, that is, the UPF sends the DL IP data packets (not including the preceding Option) to the UE through the RAN.
  • UPF can record the IP quintuple information of the DL IP packet or DL TCP packet and the identification field in the IP header. Later, when UPF provides network information to the (E)AS, the IP quintuple that needs to be recorded Group information and the identification field in the IP header.
  • Step S8 if the UPF can and needs to provide network information immediately, the UPF judges the size of the network information provided.
  • Step S8a if the UPF determines that the length of the network information (including the MAC after integrity processing, the same hereinafter)> the first length (here assumed to be 38 bytes), use UPF to generate an ICMP ECHO packet, for example, generate an ICMP echo packet (ECHO Package) and the data (Data) part contains response information (Response Information), and may also include Target ID.
  • the UPF determines that the length of the network information (including the MAC after integrity processing, the same hereinafter)> the first length (here assumed to be 38 bytes)
  • use UPF to generate an ICMP ECHO packet, for example, generate an ICMP echo packet (ECHO Package) and the data (Data) part contains response information (Response Information), and may also include Target ID.
  • the source address (for example, source IP address) of the generated ICMP ECHO packet can be set to the destination address (for example, destination IP address) and destination address (for example, destination IP address) in the IP quintuple information recorded in step S7. It can be set as the source address (for example, the source IP address) of the IP quintuple information recorded in step S7.
  • the Type/code in the ICMP ECHO packet is 8/0, and the identifier takes a specific value, such as the destination port number of the UDP or TCP packet in the IP quintuple information recorded in step S7. If the IP quintuple information recorded in step S7 is neither a UDP nor a TCP packet, the identifier of the ICMP ECHO packet can be the identification in the IP quintuple information recorded in step S7. For the sequence number of the ICMP ECHO packet, if the UPF has not been used, the UPF takes a specific value, such as generating a random value.
  • the UPF in order to prevent different IP streams from using the same random value, the UPF can generate a random value based on the IP quintuple information recorded in step S7. Then UPF sends a response message containing the network information it has obtained to (E)AS.
  • the UPF determines that the length of the network information (including the MAC after integrity processing, the same hereinafter)> the second length (here assumed to be 1472 bytes), the UPF needs to transmit the remaining network information.
  • ICMP ECHO The Type/Code and identifier in the packet can be consistent with the above embodiment, except that the SN is incremented by 1 until the transmission of the obtained network information is completed.
  • UPF can determine which ICMP ECHO packets are correctly received by (E)AS through ECHO reply within a predetermined time. If UPF does not receive the corresponding ECHO reply returned by (E)AS, it can resend the previous ICMP ECHO packet. At this time, the ICMP ECHO packet remains the same as the ECHO message header to be retransmitted.
  • the options may include (Option-Type, Target ID, Response Information).
  • the source IP address of the UL dummy IP packet can be set to the destination IP address in the IP quintuple information recorded in step S7, and the destination IP address of the UL dummy IP packet can be set to the IP quintuple recorded in step S7.
  • Option-Type can take the 30/94/158/222 exemplified above or use a specific value applied for by 3GPP on IANA.
  • Response Information contains the network information provided by UPF. If encryption and integrity protection are activated, Response Information also includes MAC.
  • UPF can also choose to generate a UL TCP empty packet, where the source IP address of the UL TCP empty packet can be set as the destination in the IP quintuple information recorded in step S7 above IP address, the destination IP address of the UL TCP empty packet can be set as the source IP address in the IP quintuple information recorded in step S7.
  • the destination port of the UL TCP empty packet can be set to the TCP source port in the IP quintuple information recorded in step S7, and the source port of the UL TCP empty packet can be set to the IP quintuple information recorded in step S7.
  • Response information contains the provided network information. If encryption and integrity protection are activated, Response Information also includes MAC.
  • step S8 and the following step S10 are not implement.
  • step S9 the UPF receives the uplink (UL) IP data packet sent by the UE via the RAN.
  • Step S10 When the UPF receives the UL IP packet, it may include (Option-Type, Target ID, Response Information) in the data data of the option of the UL IP packet. That is, UPF adds the network information to be provided to the IP option of the upstream IP packet. Or, if the UL IP packet is also a UL TCP packet, the network information to be provided by the UPF can be added to the TCP option of the uplink TCP packet. At this time, the content of the transmission is the same as the above step 8b.
  • step S8a if adding option causes IP fragmentation, UPF can continue to wait for subsequent upstream IP/TCP packets. Generally speaking, most upstream TCP packets are only TCP ACK packets, and option will not cause IP fragmentation. If there is no available upstream IP/TCP packet, after UPF waits for a certain period of time, if there is no suitable upstream IP/TCP packet to add option to transmit network information, you can use the method of step S8a above to generate an ICMP Packet or use the method of step S8b to generate a UL IP dummy packet or TCP null packet to transmit network information.
  • UPF may not perform any special processing on the uplink data received in step S9 above (such as continuing to upload to (E)AS) At this time, the above step S10 is not executed.
  • the UPF may receive multiple uplink data of the above step S9. In this case, no special processing is done (such as continuing to upload to (E)AS).
  • Step S11 UPF interacts with SMF to obtain network information from other NFs.
  • the UPF receives the network information provided by the SMF itself or other NFs, it continues to perform the following steps.
  • step S12a if UPF decides to provide the obtained network information to the (E)AS immediately or the network information length is greater than 38 bytes, the method defined in step S8a or step S8b can be used to generate an ICMP ECHO packet or UL dummy packet or TCP empty packets carry options.
  • Options include response information.
  • options may include (Option-Type, Target ID, Response Information), where Response Information includes network information obtained by UPF from SMF itself or other NFs.
  • step S12b when the UPF determines to carry the obtained network information to the (E)AS through the uplink data packet, the method of the above step S9 and step S10 can be adopted, that is, the UPF receives the UL IP data packet from the UE via the RAN. Then, step S12c is executed to make the received UL IP or TCP data packet carry options.
  • the data of the options includes response information, for example (Option-Type, Target ID, Response Information), where Response Information includes UPF slave Network information obtained by SMF itself or other NFs.
  • step S13 the UE and the (E)AS can continue the uplink and downlink transmission of the IP packet.
  • EAS in the Request information in the downlink data packet sent by the (E)AS to the UPF, EAS can specify whose network information (for example, UPF or SMF, or other NF) is obtained; it can also specify that the network information is obtained directly from the UPF. Return to EAS or send to EAS after processing; and you can also specify whether to return one time or multiple times.
  • the content included in the request information can refer to the related content in the control plane.
  • Step S14 When the time interval required by (E)AS arrives or the network information status changes, UPF needs to upload and update the network information again.
  • step S15 Geneate ICMP echo packet or UL Dummy IP packet or TCP empty packet with Options, options include response information (Option-Type, Target ID, Response Information)
  • step S16 UPF receives UL IP packets sent from UE via RAN
  • step S17 UL IP or TCP packets with options
  • the processing of options including response information (Option-Type, Target ID, Response Information)) is the same as the previous step S12a, step S12b and step S12c.
  • the network information length includes the processed network information + the integrity protection MAC.
  • MAC can take 8 bytes or 4 bytes.
  • Fig. 13 schematically shows a flow chart of obtaining network information through UPF according to an embodiment of the present application.
  • Figure 13 shows the process of obtaining network information through UPF to provide to the (E)AS.
  • Figure 13 is just an example of UPF obtaining network information from an NF through SMF.
  • UPF may need to obtain network information from different NFs through SMF, and then collectively report to the (E)AS, that is, steps S2-S5 in FIG. 13 can be performed multiple times, but the NFs are different.
  • Figure 13 may include the following steps.
  • Step S1 the (E)AS sends a downlink IP data packet to the UPF as an example for illustration.
  • the downlink IP data packet carries options (Option-Type, Target ID, Request Type, Request Parameters, MAC).
  • options Option-Type, Target ID, Request Type, Request Parameters, MAC.
  • the embodiment of the present application is not limited to this, and the specific implementation can refer to steps S1-S10 in FIG. 12 above.
  • Steps S2-S5 correspond to step S11 in FIG. 12 described above. It will be described in detail below.
  • Step S2 UPF sends an N4 message to SMF to send a network data request.
  • the N4 message requests SMF to obtain network information currently required by (E)AS.
  • This N4 message may include the network information acquisition request sent by (E)AS to UPF.
  • the request type that is, the type of network information currently requested, the above-mentioned Request Type
  • the request parameters the above-mentioned Request Parameters. That is, N4: Network Data Request (Request Type, Request Parameters), and Request Parameters may include, for example, valid time (valid time), Times (number of times), and so on.
  • this N4 message is a new message name proposed in the embodiment of this application, the name and, for example, parameters of the message name of this N4 message can be defined by 3GPP standards, but the corresponding function is to request SMF to obtain network information.
  • Step S3a corresponds to the SMF sending the Nnf_Network Data Get Request (Request Type, Request Parameters) to other NFs (the target NF, that is, the other NF from which the current SMF requests network information), that is, Nnf_NetworkData Get Request (Request Type, Request Parameters), that is, Nnf_NetworkData
  • the GetRequest message contains the type of network information currently requested (request type) and request parameters.
  • step S4a the target NF responds to the Nnf_network data acquisition request sent by the SMF, and returns the Nnf_network data acquisition response to the SMF, that is, Nnf_NetworkData Get Response (network data information), and network data information represents the network information returned by other NFs to the SMF .
  • the Nnf_NetworkData Get Request/Nnf_NetworkData Get Response in step S3a and step S4a is a one-time interactive process, that is, the Request Parameters currently sent by the (E)AS to the UPF does not specify that the UPF needs to return network information to it at regular intervals. It is not specified that when the network information changes, the UPF will automatically return to it to update the network information. For example, it can be specified by the above valid time and/or Times (number of times).
  • Step S3b corresponds to the SMF sending the Nnf_Network Data Subscription Request message to the target NF, that is, Nnf_NetworkData Subscribe Request (Request Type, Request Parameters).
  • Step S4b In response to the Nnf_NetworkData Subscribe Request message sent by the SMF, the target NF returns an Nnf_Network Data notification, that is, Nnf_NetworkData notify(network data information) to the SMF.
  • step S3b and step S4b in FIG. 13 the current network information status will be reviewed.
  • the target NF can continuously provide updated network information to the SMF.
  • Nnf_NetworkDataSubscribeRequest and Nnf_NetworkDatanotify are similar to steps S3a and S4a in FIG. 13.
  • the target NF When the target NF receives the Nnf_NetworkData Subscribe Request message, it will immediately report a current network information state to the SMF.
  • SMF can request relevant network analysis information from NWDAF. Refer to the 10 network information listed in Figure 3 above. For this request and response message and its name and detailed parameters, refer to 3GPP protocol TS23.288.
  • Nnf_NetworkData Subscribe Request and Nnf_NetworkData notify are not a one-time interaction process.
  • the target NF finds that the network information has changed, it will continue to report to the SMF to update the network information. This process can continue until the SMF is located. Set the number of times (Times) and/or time (valid time).
  • Step S5 When the SMF receives the network information replies from the target NF, it passes the network information to the UPF through the N4 message, that is, sends the N4 message to the UPF.
  • the N4 message includes the network data response, that is, N4: Network Data Response (network data information) ).
  • step SMF adopts steps S3b and S4b in Figure 13, and steps S3a and S4a in Figure 13 can generally be used to obtain network information.
  • Some static data or configuration are examples of
  • steps S3 and S4 in FIG. 13 are not executed.
  • Option Option-Type, Target ID, Response Information
  • TCP empty packet with Option Option-kind, Target ID, Response Information
  • Response Information includes network data information.
  • steps S6a and S6b in FIG. 13 can refer to steps S12a, S12b, and S12c in FIG. 12 described above.
  • Steps S7-S9 in FIG. 13 refer to step S14 in FIG. 12 described above. Next, steps S7-S9 in FIG. 13 will be described.
  • Step S7 When the target NF detects that the network information has changed, it sends the new network information data, that is, the updated network information, to the SMF by sending a Nnf_network data notification to the SMF, that is, sending Nnf_NetworkDataNotify(network datainformation), where the Network data information refers to updating network information.
  • Nnf_NetworkDataNotify Network datainformation
  • the Network data information refers to updating network information.
  • step S7 in FIG. 13 is not executed.
  • Step S8 When the SMF receives new network information data, it is sent to the UPF through an N4 message transfer, that is, the SMF sends an N4 message to the UPF, and the N4 message includes a network data response, that is, N4: Network Data Response (network data information),
  • N4 Network Data Response
  • the network data information here refers to updating network information.
  • Step 9 UPF confirms receipt of the network information, that is, after UPF receives the network information sent by the SMF or updates the network information, it sends an N4 message to the SMF: Network data notification to notify the SMF that it has received the network information sent by the SMF.
  • N4 Network Data Notify acknowledge.
  • Steps S10a and S10b in FIG. 13 refer to steps S15-S17 in FIG. 12 described above.
  • Fig. 14 schematically shows a schematic flow chart of an application server acquiring network information based on the RAN according to an embodiment of the present application.
  • Figure 14 illustrates that the RAN uses ICMP/IP option/TCP option to realize the transmission of the requested network information.
  • the embodiments of the present application may include the following steps.
  • step S1 the UE establishes a PDU session and is assigned an IP address.
  • An IP connection is established with the (E)AS through this IP address, and the transmitted IP stream can reach the (E)AS through the RAN and UPF.
  • Step S2 It is assumed here that the (E)AS decides to request network information from the RAN, and sends a network information acquisition request to the RAN via the UPF.
  • Step S3 this step is optional.
  • (E) AS and RAN conduct mutual authentication, and negotiate a security algorithm (shared algorithm) and use a common security key (shared key).
  • a security algorithm shared algorithm
  • shared key shared key
  • Step S4 Generate a DL dummy IP packet or add an option to the IP header or TCP header of the DL data.
  • the data area of the option contains request information.
  • Request Information refers to information related to the network information acquisition request, for example It can include (Target ID, Request Type, Request parameters), where Target ID refers to who is currently requesting network information, Request Type refers to the type of network information currently requested, and Request parameters refers to requesting network information Some other parameters are determined according to the requested network information.
  • the (E)AS can add option to the downstream IP header, or if the downstream IP packet is still a TCP packet, it can add Option to the TCP header instead .
  • (E)AS can generate a DL dummy IP packet (such as ICMP ECHO, note that there is no specific content in the DATA part of ICMP ECHO at this time) or TCP null Bag.
  • a DL dummy IP packet such as ICMP ECHO, note that there is no specific content in the DATA part of ICMP ECHO at this time
  • TCP null Bag TCP null Bag
  • the (E)AS can also wait until there are downlink data packets, and then continue to perform the following steps.
  • Step S5a if the above step S4 adopts adding Option to the IP header of the DL to transmit the network information acquisition request, the (E)AS can send a DL IP data packet to the RAN.
  • the DL IP data packet carries the Option option and is in the IP
  • the data part of the Option includes (Option-Type, Target ID, Request Type, Request parameters, MAC).
  • Option-Type can adopt the 30/94/158/222 mentioned above or use a specific value applied for by 3GPP on IANA.
  • Target ID ( RAN).
  • the above step S3 determines that the network capability opening interaction requires encryption and integrity protection.
  • Step S5b if the IP packet is a TCP packet, the (E)AS decides to use TCP option to transmit the network information acquisition request, that is, the above step S4 uses the option to add Option to the TCP header of the DL to transmit the network information acquisition request, then (E) The AS can send a DL TCP data packet to the RAN.
  • the DL TCP data packet has Option options, and the data part of the TCP Option includes (Option-kind, Target ID, Request Type, Request parameters, MAC). For Option-kind, see 253/254 in the example above or use a specific value applied by 3GPP on IANA, and an ExID (RFC 6994, the same below) can be used.
  • the data processing in TCP Option is the same as step S5a.
  • Step S6 After receiving the DL IP packet or DL TCP packet sent by the (E)AS, the RAN checks the DL IP packet or DL TCP packet as follows:
  • IPv4 Option-type
  • TCP Option-kind
  • the MAC in the DL IP packet or DL TCP packet is used for security verification. If the security verification is passed, continue with the following steps; if the security verification is not passed, then stop performing the steps.
  • the RAN determines whether the RAN supports the Request Type. If the RAN supports the Request Type, continue the following process. Otherwise, the RAN will not perform any special processing, and the following steps will not be executed.
  • the DL IP packet or DL TCP packet sent by the (E)AS received by the RAN is forwarded by UPF. Therefore, the UPF will also check the DL IP packet or DL TCP packet after it is received. When the Target ID points to the RAN, the UPF does not perform any special processing on it and continues to send it to the RAN.
  • Step S7 the RAN deletes the corresponding option in the DL IP or TCP packet, and then sends them in the downlink direction, that is, the RAN sends the DL IP data packet (excluding the preceding Option) to the UE.
  • the RAN can record the IP quintuple information of the DL IP packet or DL TCP packet and the identification field in the IP header. Later, when the RAN provides network information to the (E)AS, the IP quintuple that needs to be recorded Group information and the identification field in the IP header.
  • Step S8 if the RAN can and needs to provide the network information immediately, the RAN judges the size of the provided network information.
  • step S8a if the RAN determines that the length of the network information (including the MAC after integrity processing, the same hereinafter)> the first length (here assumed to be 38 bytes), use the RAN to generate an ICMP ECHO packet, for example, generate an ICMP echo packet (ECHO Package) and the data (Data) part contains response information (Response Information), and may also include Target ID.
  • the source address (for example, the source IP address) of the generated ICMP ECHO packet can be set to the destination address (for example, the destination IP address) in the IP quintuple information recorded in step S7, and the destination address (for example, the destination IP address) can be Set to the source address (for example, source IP address) of the IP quintuple information recorded in step S7.
  • the Type/code in the ICMP ECHO packet is 8/0, and the identifier takes a specific value, such as the destination port number of the UDP or TCP packet in the IP quintuple information recorded in step S7. If the IP quintuple information recorded in step S7 is neither a UDP nor a TCP packet, the identifier of the ICMP ECHO packet can be the identification in the IP quintuple information recorded in step S7. For the sequence number of the ICMP ECHO packet, if the RAN has not used it, the RAN takes a specific value, such as generating a random value.
  • the RAN may generate a random value based on the IP quintuple information recorded in step S7. Then the RAN sends a response message containing the obtained network information to the (E)AS.
  • the RAN can determine which ICMP ECHO packets are correctly received by the (E)AS through the ECHO reply within a predetermined time. If the RAN does not receive the corresponding ECHO reply returned by the (E)AS, it can resend the previous ICMP ECHO packet. At this time, the ICMP ECHO packet remains the same as the ECHO message header to be retransmitted.
  • the options may include (Option-Type, Target ID, Response Information).
  • the source IP address of the UL dummy IP packet can be set to the destination IP address in the IP quintuple information recorded in step S7, and the destination IP address of the UL dummy IP packet can be set to the IP quintuple recorded in step S7.
  • Option-Type can take the 30/94/158/222 exemplified above or use a specific value applied for by 3GPP on IANA.
  • Response Information includes the network information provided by the RAN. If encryption and integrity protection are activated, Response Information also includes MAC.
  • the RAN can also choose to generate a UL TCP empty packet, where the source IP address of the UL TCP empty packet can be set as the destination in the IP quintuple information recorded in step S7.
  • IP address the destination IP address of the UL TCP empty packet can be set as the source IP address in the IP quintuple information recorded in step S7.
  • the destination port of the UL TCP empty packet can be set to the TCP source port in the IP quintuple information recorded in step S7, and the source port of the UL TCP empty packet can be set to the IP quintuple information recorded in step S7.
  • step S8 and the following step S10 are not implement.
  • Step S9 the RAN receives the UL IP data packet sent by the UE.
  • Step S10 When the RAN receives the UL IP packet, it may include (Option-Type, Target ID, Response Information) in the data data of the option of the UL IP packet. That is, the RAN adds the network information to be provided to the IP option of the upstream IP packet. Or, if the UL IP packet is also a UL TCP packet, the network information to be provided by the RAN can be added to the TCP option of the uplink TCP packet. At this time, the content of the transmission is the same as the above step S8b.
  • step S8a can be used to generate an ICMP Packet or use the method of step S8b to generate a UL IP dummy packet or TCP null packet to transmit network information.
  • the RAN may not perform any special processing on the uplink data received in step S9 (such as continuing to upload to (E)AS) At this time, the above step S10 is not executed.
  • the RAN may receive multiple uplink data of the above step S9. In this case, no special processing is done (such as continuing to upload to (E)AS).
  • Step S11 the RAN interacts with the AMF to obtain network information from other NFs.
  • the RAN receives the network information provided by the AMF itself or other NFs, it continues to perform the following steps.
  • Step S12a if the RAN decides to immediately provide the obtained network information to the (E)AS or the network information length is greater than 38 bytes, the method defined in the above step S8a or step S8b can be used to generate an ICMP ECHO packet or UL dummy packet or TCP empty packets carry options, and options include response information.
  • options may include (Option-Type, Target ID, Response Information), where Response Information includes network information obtained by RAN from AMF itself or other NFs.
  • step S12b when the RAN determines to carry the obtained network information to the (E)AS through an uplink data packet, the above-mentioned methods of step S9 and step S10 can be adopted, that is, the RAN receives the UL IP data packet from the UE. Then, step S12c is executed to make the received UL IP or TCP data packet carry options.
  • the data of the options contains response information, for example (Option-Type, Target ID, Response Information), where Response Information includes RAN slave Network information obtained by AMF itself or other NFs.
  • step S13 the UE and the (E)AS can continue the uplink and downlink transmission of the IP packet.
  • the (E)AS sends a command to the RAN (a request for obtaining network information for downlink data packets), it includes a request for the RAN to report network information at regular intervals (for example, a time interval can be set) or when network information occurs.
  • a time interval for example, a time interval can be set
  • the (E)AS in the Request information in the downlink data packet sent by the (E)AS to the RAN, the (E)AS can specify whose network information (for example, RAN or AMF, or other NF) is obtained; it can also specify that after obtaining the network information, Whether the RAN returns directly to the (E)AS or sends it to the (E)AS after processing; and it can also be specified whether to return once or multiple times.
  • the content included in the request information can refer to the related content in the control plane.
  • Step S14 When the time interval required by the (E)AS arrives or the network information status changes, the RAN needs to upload and update the network information again.
  • step S15 in Figure 14 generatorate ICMP echo packet or UL Dummy IP packet or TCP empty Packet band options, options include response information (Option-Type, Target ID, Response Information)), step S16 (RAN receives UL IP data packets sent from the UE), step S17 (UL IP or TCP data packets with options, The processing of the option containing response information (Option-Type, Target ID, Response Information)) is the same as step S12a, step S12b, and step S12c in FIG. 14.
  • UPF has Option-Type or Option-kind in the upstream IP packet or TCP packet (defined as obtaining network information or network information). Capability open packets) will continue to be sent to (E)AS without any special processing.
  • FIG. 15 schematically shows a flow chart of obtaining network information through the RAN according to an embodiment of the present application.
  • Figure 15 shows the process of obtaining network information through the RAN to provide it to the (E)AS.
  • the RAN when the RAN itself can provide the network information required by the (E)AS (for example, the RAN itself can measure the current radio air interface transmission rate, and whether it can get the information of the UE connected to the current base station. Quantity, etc.), in this case, the RAN does not need to interact with the AMF.
  • the RAN In addition, many network capability openings are related to the air interface on the RAN. Therefore, the RAN generally directly provides its own measurement data as network information to the (E)AS without requesting network information from the AMF.
  • Figure 15 is just an example of RAN obtaining network information from an NF through AMF.
  • the RAN may need to obtain network information from different NFs through AMF, and then collectively report to the (E)AS, that is, steps S2-S5 in FIG. 15 can be performed multiple times, but the NFs are different.
  • Figure 15 may include the following steps.
  • Step S1 here is an example where the (E)AS sends a downlink IP data packet to the RAN as an example.
  • the downlink IP data packet carries options (Option-Type, Target ID, Request Type, Request Parameters, MAC).
  • options Option-Type, Target ID, Request Type, Request Parameters, MAC.
  • the present application is not limited to this, and the specific implementation can refer to steps S1-S10 in FIG. 14 described above.
  • Steps S2-S5 correspond to step S11 in FIG. 14 described above. It will be described in detail below.
  • Step S2 the RAN sends an N2 message to the AMF to send a network data request.
  • the N2 message requests the AMF to obtain the network information currently required by the (E)AS.
  • the N2 message may include the network information acquisition request sent by the (E)AS to the RAN.
  • the request type that is, the type of network information currently requested, the above-mentioned Request Type
  • the request parameters the above-mentioned Request Parameters. That is, N2: Network Data Request (Request Type, Request Parameters), and Request Parameters may include, for example, valid time (valid time), Times (number of times), and so on.
  • this N2 message is a new message name proposed in the embodiment of this application
  • the name and specific parameters of the message name of this N2 message can be defined by 3GPP standards, but the corresponding function is to request AMF to obtain network information.
  • Step S3a corresponds to the AMF sending Nnf_Network Data Get Request (Request Type, Request Parameters) to other NFs (target NF, that is, other NFs from which the current AMF requests to obtain network information), that is, Nnf_NetworkData Get Request (Request Type, Request Parameters), that is, Nnf_NetworkData
  • the GetRequest message contains the type of network information currently requested (request type) and request parameters.
  • step S4a the target NF responds to the Nnf_network data acquisition request sent by the AMF, and returns the Nnf_network data acquisition response to the AMF, that is, Nnf_NetworkData Get Response (network data information), and network data information represents the network information returned by other NFs to the AMF .
  • the Nnf_NetworkData Get Request/Nnf_NetworkData Get Response in step S3a and step S4a is a one-time interaction process, that is, the Request Parameters currently sent by the (E)AS to the RAN does not specify that the RAN needs to return network information to it at regular intervals. It is not specified that the RAN needs to automatically return the updated network information to it when the network information changes. For example, it can be specified by the above valid time and/or Times (number of times).
  • Step S3b corresponds to the Nnf_Network Data Subscription Request message sent by the AMF to the target NF, that is, Nnf_NetworkData Subscribe Request (Request Type, Request Parameters).
  • Step S4b In response to the Nnf_NetworkData Subscribe Request message sent by the AMF, the target NF returns an Nnf_Network Data notification, that is, Nnf_NetworkData notify(network data information) to the AMF.
  • step S3b and step S4b in FIG. 15 the current network information status will be reviewed.
  • the target NF can continuously provide the AMF with updated network information.
  • Nnf_NetworkDataSubscribeRequest and Nnf_NetworkDatanotify are similar to steps S3a and S4a in FIG. 15.
  • the target NF When the target NF receives the Nnf_NetworkData Subscribe Request message, it will immediately report a current network information state to the AMF.
  • AMF can request relevant network analysis information from NWDAF. See the 10 network information listed in Figure 3 above. For this request and response message and its name and detailed parameters, see 3GPP protocol TS23.288.
  • Nnf_NetworkData Subscribe Request and Nnf_NetworkData notify are not a one-time interaction process.
  • the target NF finds that the network information has changed, it will continue to report to the AMF to update the network information. This process can continue until the AMF. Set the number of times (Times) and/or time (valid time).
  • Step S5 When the AMF receives the network information replies from the target NF, it transmits the network information to the RAN through the N2 message, that is, sends an N2 message to the RAN.
  • the N2 message includes the network data response, namely N2: Network Data Response (network data information) ).
  • AMF adopts steps S3b and S4b in Figure 15, and steps S3a and S4a in Figure 15 can generally be used to obtain Some static data or configuration.
  • steps S3 and S4 in FIG. 15 are not executed.
  • Option Option-Type, Target ID, Response Information
  • TCP empty packet with Option Option-kind, Target ID, Response Information
  • Response Information includes network data information.
  • Option Option-Type, Target ID, Response Information
  • TCP data packets with Option Option-kind, Target ID, Response Information
  • Response Information includes network data information.
  • steps S6a and S6b in FIG. 15 can refer to steps S12a, S12b, and S12c in FIG. 14 described above.
  • Steps S7-S9 in FIG. 15 refer to step S14 in FIG. 14 described above. Next, steps S7-S9 in FIG. 15 will be described.
  • Step S7 When the target NF detects that the network information has changed, it sends the Nnf_network data notification to the AMF to provide the new network information data, that is, the updated network information, to the AMF, that is, to send Nnf_NetworkDataNotify(network datainformation), where the Network data information refers to updating network information.
  • the target NF detects that the network information has changed, it sends the Nnf_network data notification to the AMF to provide the new network information data, that is, the updated network information, to the AMF, that is, to send Nnf_NetworkDataNotify(network datainformation), where the Network data information refers to updating network information.
  • step S7 in FIG. 15 is not executed.
  • Step S8 When the AMF receives new network information data, it is sent to the RAN through an N2 message transfer, that is, the AMF sends an N2 message to the RAN, and the N2 message includes a network data response, that is, N2: Network Data Response (network data information),
  • N2 Network Data Response
  • the network data information here refers to updating network information.
  • Step 9 RAN confirms the receipt of network information, that is, after RAN receives the network information sent by AMF or updates the network information, it sends an N2 message to AMF: Network Data Notification to notify AMF that it has received the network information sent by AMF.
  • N2 Network Data Notify acknowledge.
  • Steps S10a and S10b in FIG. 15 refer to steps S15-S17 in FIG. 14 described above.
  • FIG. 16 schematically shows a flow chart of an application server acquiring network information based on a UE according to an embodiment of the present application.
  • Figure 16 illustrates that the UE uses ICMP/IP option/TCP option to realize the transmission of the requested network information.
  • Figure 16 may include the following steps.
  • step S1 the UE establishes a PDU session and is assigned an IP address.
  • An IP connection is established with the (E)AS through this IP address, and the transmitted IP stream can reach the (E)AS through the RAN and UPF.
  • Step S2 It is assumed here that the (E)AS decides to request network information from the UE, and sends a network information acquisition request to the UE via UPF and RAN.
  • Step S3 this step is optional.
  • the AS and the UE perform mutual authentication, and negotiate a security algorithm (shared algorithm) and use a common security key (shared key).
  • a security algorithm shared algorithm
  • shared key shared key
  • Step S4 Generate a DL dummy IP packet or add an option to the IP header or TCP header of the DL data.
  • the data area of the option contains request information.
  • Request Information refers to information related to the network information acquisition request, for example It can include (Target ID, Request Type, Request parameters).
  • the (E)AS can add option to the downstream IP header, or if the downstream IP packet is still a TCP packet, it can add Option to the TCP header instead .
  • (E)AS can generate a DL dummy IP packet (such as ICMP ECHO, note that there is no specific content in the DATA part of ICMP ECHO at this time) or TCP empty Bag.
  • a DL dummy IP packet such as ICMP ECHO, note that there is no specific content in the DATA part of ICMP ECHO at this time
  • the (E)AS can also wait until there are downlink data packets, and then continue to perform the following steps.
  • Step S5a if the step S4 in Figure 16 adds Option to the IP header of the DL to transmit the network information acquisition request, then the (E)AS can send a DL IP data packet to the UE.
  • the DL IP data packet carries the Option option and is in The data part of the IP Option includes (Option-Type, Target ID, Request Type, Request parameters, MAC).
  • Option-Type can adopt the 30/94/158/222 mentioned above or use a specific value applied for by 3GPP on IANA.
  • Target ID ( UE).
  • the above step S3 determines that the network capability opening interaction requires encryption and integrity protection.
  • Step S5b if the IP packet is a TCP packet, the (E)AS decides to use TCP option to transmit the network information acquisition request, that is, the above step S4 uses the option to add Option to the TCP header of the DL to transmit the network information acquisition request, then (E) The AS can send a DL TCP data packet to the UE.
  • the DL TCP data packet has Option options, and the data part of the TCP Option includes (Option-kind, Target ID, Request Type, Request parameters, MAC). For Option-kind, see 253/254 in the example above or use a specific value applied by 3GPP on IANA, and an ExID (RFC 6994, the same below) can be used.
  • the data processing in TCP Option is the same as step S5a.
  • Step S6 After receiving the DL IP packet or DL TCP packet sent by the (E)AS, the UE performs the following checks on the DL IP packet or DL TCP packet:
  • IPv4 Option-type
  • TCP Option-kind
  • the MAC in the DL IP packet or DL TCP packet is used for security verification. If the security verification is passed, continue with the following steps; if the security verification is not passed, then stop performing the steps.
  • the UE determines whether the UE supports the Request Type. If the UE supports the Request Type, continue the following process. Otherwise, the UE will not perform any special processing, and the following steps will not be executed.
  • the DL IP packet or DL TCP packet sent by the (E)AS received by the UE is forwarded by the UPF and RAN. Therefore, the UPF and RAN will also receive the DL IP packet or DL TCP packet after receiving it. Check, if the Target ID points to the UE, UPF and RAN will not perform any special processing on it.
  • Step S7 the UE deletes the corresponding option in the DL IP or TCP packet, and then passes them to the upper layer.
  • the UE can record the IP quintuple information of the DL IP packet or DL TCP packet and the identification field in the IP header. Later, when the UE provides network information to the (E)AS, the IP quintuple that needs to be recorded Group information and the identification field in the IP header.
  • Step S8 If the UE can and needs to provide network information immediately, the UE judges the size of the provided network information.
  • Step S8a If the UE determines that the length of the network information (including the MAC after integrity processing, the same hereinafter)> the first length (here assumed to be 38 bytes), the UE generates an ICMP ECHO packet, for example, an ICMP echo packet (ECHO packet) ) And the data (Data) part contains response information (Response Information), and may also include Target ID.
  • the UE determines that the length of the network information (including the MAC after integrity processing, the same hereinafter)> the first length (here assumed to be 38 bytes)
  • the UE generates an ICMP ECHO packet, for example, an ICMP echo packet (ECHO packet)
  • the data (Data) part contains response information (Response Information), and may also include Target ID.
  • the source address (for example, the source IP address) of the generated ICMP ECHO packet can be set to the destination address (for example, the destination IP address) in the IP quintuple information recorded in step S7, and the destination address (for example, the destination IP address) can be Set to the source address (for example, source IP address) of the IP quintuple information recorded in step S7.
  • the Type/code in the ICMP ECHO packet is 8/0, and the identifier takes a specific value, such as the destination port number of the UDP or TCP packet in the IP quintuple information recorded in step S7. If the IP quintuple information recorded in step S7 is neither a UDP nor a TCP packet, the identifier of the ICMP ECHO packet can be the identification in the IP quintuple information recorded in step S7. For the sequence number of the ICMP ECHO packet, if the UE has not used it, the UE takes a specific value, such as generating a random value.
  • the UE may generate a random value based on the IP quintuple information recorded in step S7. Then the UE sends a response message containing the obtained network information to the (E)AS.
  • the UE can determine which ICMP ECHO packets are correctly received by the (E)AS through the ECHO reply within a predetermined time. If the UE does not receive the corresponding ECHO reply returned by the (E)AS, it can resend the previous ICMP ECHO packet. At this time, the ICMP ECHO packet remains the same as the ECHO message header to be retransmitted.
  • the options may include (Option-Type, Target ID, Response Information).
  • the source IP address of the UL dummy IP packet can be set to the destination IP address in the IP quintuple information recorded in step S7, and the destination IP address of the UL dummy IP packet can be set to the IP quintuple recorded in step S7.
  • Option-Type can take the 30/94/158/222 exemplified above or use a specific value applied for by 3GPP on IANA.
  • Response Information includes the network information provided by the RAN. If encryption and integrity protection are activated, Response Information also includes MAC.
  • the UE can also choose to generate a UL TCP empty packet, where the source IP address of the UL TCP empty packet can be set as the destination in the IP quintuple information recorded in step S7.
  • IP address the destination IP address of the UL TCP empty packet can be set as the source IP address in the IP quintuple information recorded in step S7.
  • the destination port of the UL TCP empty packet can be set to the TCP source port in the IP quintuple information recorded in step S7, and the source port of the UL TCP empty packet can be set to the IP quintuple information recorded in step S7.
  • step S8 if the UE cannot provide network information immediately, if the UE needs to interact with AMF and obtain network information provided by AMF or other NFs from AMF, then the UE can initiate interaction with AMF, then step S8 and the following step S10 are not implement.
  • Step S9 the UE receives the UL IP data packet.
  • Step S10 When the UE receives the UL IP packet, it may include (Option-Type, Target ID, Response Information) in the data data of the option of the UL IP packet. That is, the UE adds the network information to be provided to the IP option of the uplink IP packet. Or, if the UL IP packet is also a UL TCP packet, the network information to be provided by the RAN can be added to the TCP option of the uplink TCP packet. At this time, the content of the transmission is the same as the above step S8b.
  • step S8a if adding option causes IP fragmentation, the UE can continue to wait for subsequent uplink IP/TCP packets. Generally speaking, most uplink TCP packets are only TCP ACK packets, and option will not cause IP fragmentation. If there is no available uplink IP/TCP packet, after the UE waits for a certain period of time, if there is no suitable uplink IP/TCP packet for adding option to transmit network information, it can use the method of step S8a above to generate an ICMP Packet or use the method of step S8b to generate a UL IP dummy packet or TCP null packet to transmit network information.
  • step S9 the uplink data received in step S9 above (such as continuing to upload to (E)AS)
  • step S10 the above step S10 is not executed.
  • step S11 there may be multiple uplink data received by the UE in the above step S9. In this case, no special processing is done (such as continuing to upload to (E)AS).
  • Step S11 the UE interacts with the AMF to obtain network information from other NFs.
  • the UE receives the network information provided by the AMF itself or other NFs, it continues to perform the following steps.
  • Step S12a if the UE decides to immediately provide the obtained network information to the (E)AS or the network information length is greater than 38 bytes, the method defined in the above step S8a or step S8b can be used to generate an ICMP ECHO packet or UL dummy packet or TCP empty packets carry options, options include response information, for example, options may include (Option-Type, Target ID, Response Information), where Response Information includes network information obtained by the UE from the AMF itself or other NFs.
  • step S12b when the UE determines to carry the obtained network information to the (E)AS through an uplink data packet, the above-mentioned method of step S9 and step S10 can be adopted, that is, the UE receives the UL IP data packet. Then, step S12c is performed to make the received UL IP or TCP data packet carry options, and the data of the options contains response information, for example (Option-Type, Target ID, Response Information), where Response Information includes UE slave Network information obtained by AMF itself or other NFs.
  • response information for example (Option-Type, Target ID, Response Information)
  • step S13 the UE and the (E)AS can continue the uplink and downlink transmission of the IP packet.
  • the (E)AS sends a command to the UE (a request for obtaining network information of a downlink data packet), it includes a request for the UE to report network information or network information at regular intervals (for example, a time interval can be set).
  • a time interval can be set.
  • the information changes send the updated network information to the (E)AS again.
  • the IP communication between the UE and the (E)AS continues, and at this time, the UE does not perform any specific processing.
  • the (E)AS in the Request information in the downlink data packet sent by the (E)AS to the UE, the (E)AS can specify whose network information (for example, UE or AMF, or other NF) is obtained; it can also specify that after obtaining the network information, Whether the UE directly returns to the (E)AS or sends it to the (E)AS after processing; and it can also be specified whether to return once or multiple times.
  • the content included in the request information can refer to the related content in the control plane.
  • Step S14 when the time interval required by (E)AS arrives or the network information status changes, the UE needs to upload and update the network information again.
  • step S15 in Figure 16 generatorate ICMP echo packet or UL Dummy IP packet or TCP empty Packet with options, options include response information (Option-Type, Target ID, Response Information)
  • step S16 UE receives UL IP data packets
  • step S17 UL IP or TCP packets with options, options include response information
  • the processing of (Option-Type, Target ID, Response Information)) is the same as step S12a, step S12b, and step S12c in FIG. 16.
  • the UPF and RAN also need to check whether the Target ID points to themselves, and when they find that they are not pointing to themselves, they do not perform any special processing and continue to send to the UE.
  • UPF and RAN respond to upstream IP packets or TCP packets with Option-Type or Option-kind (defined as obtaining network information or opening network capabilities). Packet) without any special processing, continue to be sent to (E)AS.
  • steps S9, S12 (including S12a, S12b, and S12c) and the UL IP packet in S16 in FIG. 16 mean that the UE receives an uplink data packet to be sent to the (E)AS.
  • FIG. 17 schematically shows a schematic flow chart of obtaining network information through a UE according to an embodiment of the present application.
  • Figure 17 shows the process of obtaining network information through the UE to provide it to the (E)AS.
  • the UE when the UE itself can provide the network information required by (E)AS (for example, when the UE interacts with AMF, SMF, PCF, RAN before, the UE already has some network information
  • the network information may include, for example, the transmission delay between the UE and the RAN, the total transmission rate of the UE, etc.). In this case, the UE does not need to interact with the AMF. If the UE only needs to obtain the network information on the AMF and provide it to the (E)AS, the following steps S3 (including steps S3a and S3b), S4 (including steps S4a and S4b), and S7 in FIG. 17 will not be executed.
  • Fig. 17 only shows an example in which the UE obtains network information from an NF through AMF. In actual situations, the UE may need to obtain network information from different NFs through AMF, and then collectively report to the (E)AS, that is, steps S2-S5 in FIG. 17 can be performed multiple times, but the NFs are different respectively.
  • Figure 17 may include the following steps.
  • Step S1 the (E)AS sends a downlink IP data packet to the UE through UPF and RAN as an example for illustration.
  • the downlink IP data packet carries options (Option-Type, Target ID, Request Type, Request Parameters, MAC).
  • options Option-Type, Target ID, Request Type, Request Parameters, MAC.
  • the embodiment of the present application is not limited to this, and the specific implementation can refer to steps S1-S10 in FIG. 16 described above.
  • Steps S2-S5 correspond to step S11 in FIG. 16 described above. It will be described in detail below.
  • Step S2 The UE sends a NAS (Non-Access Stratum, non-access stratum) message to the AMF to send a network data request.
  • the NAS message requests the AMF to obtain the network information currently required by the (E)AS.
  • the NAS message may contain ( E) The request type (that is, the type of network information currently requested, the aforementioned Request Type) and the request parameters (the aforementioned Request Parameters) in the network information acquisition request sent by the AS to the UE. That is, NAS: Network Data Request (Request Type, Request Parameters), and Request Parameters may include, for example, valid time (valid time), Times (number of times), and so on.
  • this NAS message is a new message name proposed in the embodiment of this application, the name and, for example, parameters of the message name of this NAS message can be defined by 3GPP standards, but the corresponding function is to request AMF to obtain network information.
  • Step S3a corresponds to the AMF sending Nnf_Network Data Get Request (Request Type, Request Parameters) to other NFs (target NF, that is, other NFs from which the current AMF requests to obtain network information), that is, Nnf_NetworkData Get Request (Request Type, Request Parameters), that is, Nnf_NetworkData
  • the GetRequest message contains the type of network information currently requested (request type) and request parameters.
  • step S4a the target NF responds to the Nnf_network data acquisition request sent by the AMF, and returns the Nnf_network data acquisition response to the AMF, that is, Nnf_NetworkData Get Response (network data information), and network data information represents the network information returned by other NFs to the AMF .
  • the AMF may obtain some user subscription data from the UDM, and provide part of the subscription data to the UE, and then to the (E)AS.
  • the Nnf_NetworkData Get Request/Nnf_NetworkData Get Response in step S3a and step S4a is a one-time interaction process, that is, the Request Parameters currently sent by the (E)AS to the UE does not specify that the UE should return network information to it at regular intervals. It is not specified that when the network information changes, the UE will automatically return to it to update the network information. For example, it can be specified by the above valid time and/or Times (number of times).
  • Step S3b corresponds to the Nnf_Network Data Subscription Request message sent by the AMF to the target NF, that is, Nnf_NetworkData Subscribe Request (Request Type, Request Parameters).
  • Step S4b In response to the Nnf_NetworkData Subscribe Request message sent by the AMF, the target NF returns an Nnf_Network Data notification, that is, Nnf_NetworkData notify(network data information) to the AMF.
  • step S3b and step S4b in FIG. 17 the current network information status will be reviewed.
  • the target NF can continuously provide the AMF with updated network information.
  • Nnf_NetworkDataSubscribeRequest and Nnf_NetworkDatanotify are similar to steps S3a and S4a in FIG. 17.
  • the target NF When the target NF receives the Nnf_NetworkData Subscribe Request message, it will immediately report a current network information state to the AMF.
  • AMF can request relevant network analysis information from NWDAF. See the 10 network information listed in Figure 3 above. For this request and response message and its name and detailed parameters, see 3GPP protocol TS23.288.
  • Nnf_NetworkData Subscribe Request and Nnf_NetworkData notify are not a one-time interaction process.
  • the target NF finds that the network information has changed, it will continuously report to the AMF to update the network information. This process can continue until the AMF Set the number of times (Times) and/or time (valid time).
  • Step S5 When the AMF receives the network information replies from the target NF, it passes the network information to the UE through a NAS message, that is, sends a NAS message to the UE.
  • the NAS message includes a network data response, namely NAS: Network Data Response (network data information) ).
  • AMF adopts steps S3b and S4b in Figure 17, and steps S3a and S4a in Figure 17 can generally be used to obtain network information. Some static data or configuration.
  • steps S3 and S4 in FIG. 17 are not executed.
  • Option Option-Type, Target ID, Response Information
  • TCP empty packet with Option Option-kind, Target ID, Response Information
  • Response Information includes network data information.
  • Option Option-Type, Target ID, Response Information
  • TCP data packets with Option Option-kind, Target ID, Response Information
  • Response Information includes network data information.
  • steps S6a and S6b in FIG. 17 can refer to steps S12a, S12b, and S12c in FIG. 16 described above.
  • Steps S7-S9 in FIG. 17 refer to step S14 in FIG. 16 described above. Next, steps S7-S9 in FIG. 17 will be described.
  • Step S7 When the target NF detects that the network information has changed, it sends the Nnf_network data notification to the AMF to provide the new network information data, that is, the updated network information, to the AMF, that is, to send Nnf_NetworkDataNotify(network datainformation), where the Network data information refers to updating network information.
  • the target NF detects that the network information has changed, it sends the Nnf_network data notification to the AMF to provide the new network information data, that is, the updated network information, to the AMF, that is, to send Nnf_NetworkDataNotify(network datainformation), where the Network data information refers to updating network information.
  • step S7 in FIG. 17 is not executed.
  • Step S8 When the AMF receives new network information data, it is sent to the UE through a NAS message, that is, the AMF sends a NAS message to the UE.
  • the NAS message includes a network data response, namely NAS: Network Data Response (network data information),
  • the network data information here refers to updating network information.
  • the AMF may initiate a Network triggered service request (network Trigger the service request) process (see section 4.2.3.3 of the 3GPP protocol TS23.502). After the UE establishes a signaling connection with the AMF, the AMF performs step S8 again.
  • CM-IDLE connection management-IDLE, connection management-idle, when the UE is in the CM-IDLE state, there is no N2 and N3 connection of the terminal
  • the AMF may initiate a Network triggered service request (network Trigger the service request) process (see section 4.2.3.3 of the 3GPP protocol TS23.502).
  • the AMF performs step S8 again.
  • Step 9 The UE confirms the receipt of the network information, that is, after the UE receives the network information sent by the AMF or updates the network information, it sends a NAS message to the AMF: Network Data Notification to notify the AMF that it has received the network information sent by the AMF.
  • NAS Network Data Notify acknowledge.
  • steps S8 and S9 in Figure 17 can be executed multiple times (see 3GPP protocol for similar processing Section 4.2.4.3 of TS23.502).
  • the signaling interaction manner similar to steps S8 and S9 in Figure 17 can be used. , Transmit the remaining network information data to the UE.
  • Steps S10a and S10b in FIG. 17 refer to steps 15-S17 in FIG. 16 described above.
  • Fig. 18 schematically shows a flowchart of a method for implementing network capability opening according to an embodiment of the present application.
  • the method in FIG. 18 may be executed by a target user plane node, such as any one of UE/RAN/UPF.
  • the method provided by the embodiment of the present application may include the following steps.
  • step S181 a downlink data packet sent by the application server is received, where the downlink data packet includes a network information acquisition request.
  • the method may further include: recording the Internetwork Protocol quintuple information of the downlink data packet and the identification field of the Internetwork Protocol frame header.
  • step S182 in response to the network information acquisition request, response information is generated, where the response information includes the network information requested by the network information acquisition request.
  • step S183 the response information is sent to the application server.
  • FIG. 19 shows a schematic diagram of the processing process of step S182 shown in FIG. 18 in an embodiment. As shown in FIG. 19, the above step S182 in the embodiment of the present application may further include the following steps.
  • step S1821 the requested network information is acquired according to the network information acquisition request.
  • obtaining the requested network information according to the network information obtaining request includes: sending the network information obtaining request to the first target non-user plane node; receiving the first target non-user plane node to return in response to the network information obtaining request The network information of the first target non-user plane node.
  • the first target non-user plane node in FIG. 19 may be, for example, AMF or SMF, where when the target user plane node is UE or RAN, the first target non-user plane node may be AMF, and when the target user plane node is UPF At this time, the first target non-user plane node may be SMF. That is, the user plane node UE or RAN obtains the network information provided by the AMF itself. At this time, the AMF does not need to interact with other NFs to obtain the network information. There is also a situation where the target user plane node can obtain the network information provided by itself. At this time, the UE/RAN does not need to interact with the AMF to obtain the network information, and the UPF does not need to interact with the SMF to obtain the network information.
  • obtaining the requested network information according to the network information obtaining request includes: sending the network information obtaining request to the first target non-user plane node, so that the first target non-user plane node can send the network information obtaining request To the second target non-user plane node, and receive the network information of the second target non-user plane node returned by the second target non-user plane node in response to the network information request; receive the second target non-user plane node returned by the first target non-user plane node Network information of the user plane node.
  • the second target non-user plane node may be other non-user plane nodes other than AMF and SMF, such as a control plane node, or may be the target NF in the foregoing embodiment. That is, the AMF can interact with the target NF to obtain network information, or the SMF can interact with the target NF to obtain network information, and then provide it to the UE, RAN or UPF.
  • AMF can interact with the target NF to obtain network information
  • the SMF can interact with the target NF to obtain network information, and then provide it to the UE, RAN or UPF.
  • acquiring the requested network information according to the network information acquisition request may further include: receiving updated network information of the second target non-user plane node returned by the first target non-user plane node; wherein, the second target non-user plane node The updated network information of the user plane node is sent by the second target non-user plane node to the first target non-user plane node when the network information of the second target non-user plane node changes or reaches a predetermined time interval.
  • (E)AS When (E)AS requests the target user plane node at regular intervals or when network information changes, it will automatically return the changed network information to (E)AS (that is, update network information), then the set time interval will be reached Later, or when the network information changes, the target NF will automatically send updated network information to the AMF or SMF, so that the target user plane node can provide it to the (E)AS.
  • step S1822 if the length of the network information is greater than the first length, at least one Internet Control Message Protocol echo request packet is generated, where the first length is related to the length of the data area of the Internet Protocol option.
  • the method may further include: setting the source address and the destination address of the at least one Internet Control Message Protocol echo request packet to be the destination address and the source address in the Internet Protocol quintuple information of the downlink data packet; If the internetwork protocol quintuple information of the data packet includes the destination port number of the user datagram protocol or transmission control protocol, set the identifier of at least one internet control message protocol echo request packet as the internetwork protocol quintuple of the downlink data packet The destination port number of the user datagram protocol or transmission control protocol in the information; if the Internet protocol quintuple information of the downlink data packet does not include the destination port number of the user datagram protocol or transmission control protocol, at least one Internet control protocol is set The identifier of the message protocol echo request packet is the identifier field of the Internet Protocol frame header.
  • the at least one Internet Control Message Protocol return request packet includes multiple Internet Control Message Protocol return request packets, and the sequence numbers of the multiple Internet Control Message Protocol return request packets Starting from a random value and increasing sequentially; wherein, the second length is related to the length of the data area of the Internet Control Message Protocol echo request packet, and the second length is greater than the first length.
  • the method may further include: generating a random value according to the internetwork protocol quintuple information of the downlink data packet.
  • step S1823 write network information in the data area of at least one Internet Control Message Protocol echo request packet for generating response information.
  • FIG. 20 shows a schematic diagram of the processing process of step S182 shown in FIG. 18 in an embodiment. As shown in FIG. 20, the above step S182 in the embodiment of the present application may further include the following steps.
  • step S1824 the requested network information is acquired according to the network information acquisition request.
  • obtaining the requested network information according to the network information obtaining request includes: sending the network information obtaining request to the first target non-user plane node; receiving the first target non-user plane node to return in response to the network information obtaining request The network information of the first target non-user plane node.
  • obtaining the requested network information according to the network information obtaining request includes: sending the network information obtaining request to the first target non-user plane node, so that the first target non-user plane node can send the network information obtaining request To the second target non-user plane node, and receive the network information of the second target non-user plane node returned by the second target non-user plane node in response to the network information request; receive the second target non-user plane node returned by the first target non-user plane node Network information of the user plane node.
  • acquiring the requested network information according to the network information acquisition request may further include: receiving updated network information of the second target non-user plane node returned by the first target non-user plane node; wherein, the second target non-user plane node The updated network information of the user plane node is sent by the second target non-user plane node to the first target non-user plane node when the network information of the second target non-user plane node changes or reaches a predetermined time interval.
  • step S1825 if the length of the network information is less than or equal to the first length, an uplink analog data packet is generated.
  • the uplink analog data packet includes the Internet Protocol frame header, wherein the source address and the destination address of the uplink analog data packet are respectively set as the downlink data The destination address and source address of the packet.
  • step S1826 an internet protocol option is added to the internet protocol frame header of the uplink analog data packet.
  • step S1827 write network information in the data area of the Internet protocol option of the uplink simulated data packet for generating response information.
  • FIG. 21 shows a schematic diagram of the processing process of step S182 shown in FIG. 18 in an embodiment. As shown in FIG. 21, the above step S182 in the embodiment of the present application may further include the following steps.
  • step S1828 the requested network information is acquired according to the network information acquisition request.
  • obtaining the requested network information according to the network information obtaining request includes: sending the network information obtaining request to the first target non-user plane node; receiving the first target non-user plane node to return in response to the network information obtaining request The network information of the first target non-user plane node.
  • obtaining the requested network information according to the network information obtaining request includes: sending the network information obtaining request to the first target non-user plane node, so that the first target non-user plane node can send the network information obtaining request To the second target non-user plane node, and receive the network information of the second target non-user plane node returned by the second target non-user plane node in response to the network information request; receive the second target non-user plane node returned by the first target non-user plane node Network information of the user plane node.
  • acquiring the requested network information according to the network information acquisition request may further include: receiving updated network information of the second target non-user plane node returned by the first target non-user plane node; wherein, the second target non-user plane node The updated network information of the user plane node is sent by the second target non-user plane node to the first target non-user plane node when the network information of the second target non-user plane node changes or reaches a predetermined time interval.
  • step S1829 if the length of the network information is less than or equal to the first length, an uplink transmission control protocol null packet is generated, wherein the source address and destination address of the uplink transmission control protocol null packet are set as the destination address and source address of the downlink data packet, respectively The address, the source port number and the destination port number of the empty uplink transmission control protocol packet are respectively set as the transmission control protocol destination port number and the transmission control protocol source port number in the Internetwork protocol quintuple information of the downlink data packet.
  • step S18210 write network information in the data area of the uplink transmission control protocol empty packet for generating response information.
  • FIG. 22 shows a schematic diagram of the processing process of step S182 shown in FIG. 18 in an embodiment. As shown in FIG. 22, the above step S182 in the embodiment of the present application may further include the following steps.
  • step S18211 the requested network information is acquired according to the network information acquisition request.
  • obtaining the requested network information according to the network information obtaining request includes: sending the network information obtaining request to the first target non-user plane node; receiving the first target non-user plane node to return in response to the network information obtaining request The network information of the first target non-user plane node.
  • obtaining the requested network information according to the network information obtaining request includes: sending the network information obtaining request to the first target non-user plane node, so that the first target non-user plane node can send the network information obtaining request To the second target non-user plane node, and receive the network information of the second target non-user plane node returned by the second target non-user plane node in response to the network information request; receive the second target non-user plane node returned by the first target non-user plane node Network information of the user plane node.
  • acquiring the requested network information according to the network information acquisition request may further include: receiving updated network information of the second target non-user plane node returned by the first target non-user plane node; wherein, the second target non-user plane node The updated network information of the user plane node is sent by the second target non-user plane node to the first target non-user plane node when the network information of the second target non-user plane node changes or reaches a predetermined time interval.
  • step S18212 if the length of the network information is less than or equal to the first length and the uplink Internet Protocol data packet is received, the network information is written into the data area of the Internet Protocol option of the uplink Internet Protocol data packet for generating response information .
  • FIG. 23 shows a schematic diagram of the processing process of step S182 shown in FIG. 18 in an embodiment. As shown in FIG. 23, the above step S182 in the embodiment of the present application may further include the following steps.
  • step S18213 the requested network information is acquired according to the network information acquisition request.
  • obtaining the requested network information according to the network information obtaining request includes: sending the network information obtaining request to the first target non-user plane node; receiving the first target non-user plane node to return in response to the network information obtaining request The network information of the first target non-user plane node.
  • obtaining the requested network information according to the network information obtaining request includes: sending the network information obtaining request to the first target non-user plane node, so that the first target non-user plane node can send the network information obtaining request To the second target non-user plane node, and receive the network information of the second target non-user plane node returned by the second target non-user plane node in response to the network information request; receive the second target non-user plane node returned by the first target non-user plane node Network information of the user plane node.
  • acquiring the requested network information according to the network information acquisition request may further include: receiving updated network information of the second target non-user plane node returned by the first target non-user plane node; wherein, the second target non-user plane node The updated network information of the user plane node is sent by the second target non-user plane node to the first target non-user plane node when the network information of the second target non-user plane node changes or reaches a predetermined time interval.
  • step S18214 if the length of the network information is less than or equal to the first length and the uplink transmission control protocol data packet is received, the network information is written into the transmission control protocol option data area of the uplink transmission control protocol data packet for use Generate response information.
  • IP Option the maximum length of IP Option is 40 bytes, and EAS or AS is generally sufficient for sending control commands to the target user plane node. If the UE/RAN/UPF provides network information to EAS or AS, the length of 40 bytes may be insufficient.
  • the receiver can implement data reorganization through Network Data Pointer. However, if one IP packet in the middle is lost, the entire Network Data may not be reorganized successfully. In this case, EAS or AS needs to resend the network information acquisition request command.
  • EAS or AS sends control commands to UE/RAN/UPF or UE/RAN/UPF sends response information to EAS/AS, if there is no downlink data or uplink data that can be sent at this time, wait until there is downlink data or uplink data .
  • this method still has the problem of requiring multiple transmissions for longer uplink network data.
  • the maximum length of TCP Option is 40 bytes, and EAS or AS is generally sufficient for sending control commands to the target user plane node. If UE/RAN/UPF provides network information to EAS or AS, the length of 40 bytes may be insufficient.
  • the TCP protocol can realize the sequential reassembly of TCP packets Therefore, it can indirectly ensure that the receiver sequentially receives the network capability opening data (including the loss of TCP packets during transmission, which is better than IP Option). But this is only based on each existing TCP An option is added to the package. When the network capability is opened for a long time, a lot of TCP packets may be needed, and it may last for a long time.
  • TCP empty packets that send an ACK multiple times, and transmit a part of the network capacity open data in each TCP empty packet, which will not cause any problems with TCP connections, but some TCP protocol stacks will repeat TCP empty packets.
  • the packet the ACK Number of the TCP packet
  • the packet arrives unchanged for three times, it starts to reduce the transmission rate sent to the other party (that is, when the UE/RAN/UPF continuously sends data with open network capabilities to the EAS or AS through the empty ACK packet of TCP. )
  • EAS/AS will reduce the rate of sending TCP actual data packets to the UE, which will affect the user experience.
  • EAS or AS sends control commands to UE/RAN/UPF or UE/RAN/UPF sends response information to EAS/AS, if there is no downlink data or uplink data that can be sent at this time, wait until there is downlink data or uplink data . However, there may be no uplink or downlink data for a long period of time. At this time, a dummy IP packet is generated, and the dummy IP option is used to transmit data related to network information.
  • the Dummy IP packet is actually an ICMP ECHO packet, and the ECHO of ICMP is sent (multiple times), and the identifier in the ECHO sent each time is set to a port number of UDP or TCP, and the SN is set to an incremental serial number.
  • the UE/RAN/UPF receives the corresponding ECHO Reply, it compares the SN and identifier of the received ECHO Reply to whether the SN and identifier of the ECHO are the same. If they are the same, it means that EAS/AS has received the ICMP message. In this way, Dummy IP The Option data on the header is received. If the UE/RAN/UPF does not receive an ECHO Reply within a predetermined time, it will resend the ECHO again and include the corresponding Option data in the IP header.
  • the embodiment of this application proposes to send the Network Data data as the Data part of the ECHO.
  • the transmission efficiency at this time is much greater than that of Option which only transmits 38 bytes each time.
  • the IP Option and TCP Option methods are used.
  • the data length of the network information exceeds 38 bytes and is less than 1472 bytes, run the ICMP ECHO and Reply methods once.
  • the reliable and sequential transmission of network information data can be realized by repeatedly running the ICMP Request and Reply methods of increasing the SN number.
  • the method provided in the embodiment of the present application uses the user plane to realize network capability opening.
  • Internet applications and various applications basically use IP and TCP protocols. Therefore, the option extension header on the IP or TCP protocol header is used to transmit the request and response of network capability opening, contract and report data. For example, make full use of TCP's ACK empty packet or generate an IP dummy packet to send the option extension header, thereby avoiding fragmentation caused by the increase in the length of the IP data packet caused by the introduction of the option header.
  • the length of the uplink data packet is smaller and the length of the downlink data packet is longer, so as to realize more uploading of network capability open data to EAS or AS.
  • the packets sent by the UE are called uplink data packets.
  • there are fewer uplink data packets than downlink data packets and most of the uplink data packets are ACK empty packets, and only a small part carries actual data.
  • the UE user requests EAS or AS.
  • EAS or AS needs to send 1GB of downlink data packets, then the corresponding uplink data packets are assumed to be 200,000, of which only 1,000 are with actual data, and the others are ACK packets.
  • the option part of the UL data packet is used to transmit network information, if you encounter a UL data packet with actual data, you can skip this UL data packet, and the transmission of network information will not be affected as a whole.
  • the downlink data packet is generally long, and the downlink data packet is sent to the UE by EAS or AS, if option data is added and some bytes of the downlink data packet are occupied, EAS or AS can automatically pack a few more bytes.
  • UPF or RAN After UPF or RAN receives the downlink data packet sent by EAS or AS, it can only encapsulate a small amount of data outside, and cannot lose the downlink data packet sent by EAS or AS itself, nor can it decide how many A packet to send to the UE.
  • the method for realizing network capability opening proposed by the embodiments of this application uses the user plane to realize the function of network capability opening, which has strong real-time performance, large amount of network data transmitted, and does not cause a large amount of network signaling; on the other hand, , Network capability opening is realized based on IP, TCP and ICMP, which are the basic protocols supported by all current applications and networks, especially the use of ICMP to achieve reliable and orderly large network information data transmission.
  • network capability opening does not require a dedicated control plane interface between EAS or AS and the network (the interface between AF and NEF and (E)AS and AF).
  • the IP transmission path during communication is used to achieve network capability opening.
  • the method provided in the embodiments of this application is an in-band technology, which reduces the difficulty and difficulty of how network information is associated with (E)AS, especially with UE when out-of-band capabilities are opened. challenge.
  • the method for implementing network capability opening proposed in the implementation of this application can be applied to MEC, and can also be applied to 2G, 3G, 4G, and 5G networks, and multiple implementation methods are proposed: IP, TCP, ICMP, and each method is given How to choose the method. Provides a way to achieve network capability opening through UE, RAN, and UPF to support network capability opening in different situations.
  • Fig. 24 schematically shows a block diagram of an apparatus for implementing network capability opening according to an embodiment of the present application.
  • the apparatus 2400 for implementing network capability opening provided by the embodiment of the present application includes: a downlink data obtaining unit 2410, a downlink data sending unit 2420, and a response information receiving unit 2430.
  • the downlink data obtaining unit 2410 is configured to obtain a downlink data packet, where the downlink data packet includes a network information obtaining request.
  • the downlink data sending unit 2420 is configured to send the downlink data packet to the target user plane node.
  • the response information receiving unit 2430 is configured to receive response information returned by the target user plane node in response to the network information acquisition request, where the response information includes the network information requested by the network information acquisition request.
  • the downlink data obtaining unit 2410 includes: a first to-be-sent downlink data obtaining unit configured to obtain the first to-be-sent downlink data, where the first to-be-sent downlink data includes the Internet Protocol frame header;
  • the interconnection protocol option adding unit is configured to add an internetwork protocol option to the first internetwork protocol frame header of the first to be sent downlink data;
  • the first internetwork protocol data writing unit is configured to add the internetwork protocol option to the first internetwork of the first downlink data to be sent The data area of the protocol option is written into the network information acquisition request for generating downlink data packets.
  • the downlink data obtaining unit 2410 includes: a second to-be-sent downlink data obtaining unit, configured to obtain the second to-be-sent downlink data, the second to-be-sent downlink data including the transmission control protocol frame header; the second transmission control protocol The option adding unit is configured to add a transmission control protocol option to the first transmission control protocol frame of the second downlink data to be sent; the second transmission control protocol data writing unit is configured to add a transmission control protocol option to the second downlink data to be sent The data area of is written into the network information acquisition request to be used to generate the downlink data packet.
  • the downlink data acquisition unit 2410 includes: a downlink analog data packet generating unit, configured to generate a downlink analog data packet, the downlink analog data packet includes an Internet Protocol frame header; a downlink analog data packet Internet Protocol option adding unit, configured to The Internet Protocol option is added to the Internet Protocol frame header of the downstream analog data packet; the downstream analog data packet option data writing unit is configured to write a network information acquisition request in the data area of the Internet Protocol option of the downstream analog data packet for use Generate downstream data packets.
  • the target user plane node may include any one of a user plane gateway, a base station, and a terminal.
  • the apparatus 2400 for enabling network capability opening further includes: a target user plane node switching unit configured to When it is detected that the length of the network information in the response information returned by the terminal exceeds the preset threshold, it switches to using the user plane gateway or the base station to return the network information requested by the network information acquisition request.
  • Fig. 25 schematically shows a block diagram of an apparatus for implementing network capability opening according to an embodiment of the present application.
  • the apparatus 2500 for implementing network capability opening provided by the embodiment of the present application includes: a downlink data receiving unit 2510, a response information generating unit 2520, and a response information sending unit 2530.
  • the downlink data receiving unit 2510 is configured to receive a downlink data packet sent by an application server, where the downlink data packet includes a network information acquisition request.
  • the response information generating unit 2520 is configured to generate response information in response to the network information acquisition request, wherein the response information includes the network information requested by the network information acquisition request.
  • the response information sending unit 2530 is configured to send the response information to the application server.
  • the device 2500 for implementing network capability opening further includes: a quintuple information recording unit configured to record the internetwork protocol quintuple information of the downlink data packet and the identification field of the internetwork protocol frame header.
  • the response information generating unit 2520 includes: a network information obtaining unit configured to obtain the requested network information according to a network information obtaining request; an Internet Control Message Protocol echo request packet generating unit configured to be configured when the length of the network information is greater than At the first length, at least one Internet Control Message Protocol echo request packet is generated, where the first length is related to the length of the data area of the Internet Protocol option; the Internet Control Message Protocol echo request packet data writing unit is configured to be at least An Internet Control Message Protocol sends back the data area of the request packet to write network information to generate response information.
  • the device 2500 for implementing network capability opening includes: an Internet Control Message Protocol echo request packet address setting unit, configured to set the source address and destination address of at least one Internet Control Message Protocol echo request packet to be those of a downlink data packet.
  • the first identifier setting unit is configured to include the destination port number of the user datagram protocol or transmission control protocol in the internetwork protocol quintuple information of the downlink data packet
  • the second identifier setting unit It is configured to set the identifier of at least one Internet Control Message Protocol echo request packet to the Internet Protocol frame when the Internet Protocol quintuple information of the downlink data packet does not include the destination port number of the User Datagram Protocol or the Transmission Control Protocol The first identification field.
  • the at least one Internet Control Message Protocol echo request packet when the length of the network information is greater than the second length, includes multiple Internet Control Message Protocol echo request packets, and a sequence of multiple Internet Control Message Protocol echo request packets The number starts from a random value and increases in sequence.
  • the second length is related to the length of the data area of the request packet sent back by the Internet Control Message Protocol, and the second length is greater than the first length.
  • the apparatus 2500 for implementing network capability opening includes: a random value generating unit configured to generate a random value according to the Internetwork Protocol quintuple information of the downlink data packet.
  • the response information generating unit 2520 includes: a network information obtaining unit configured to obtain the requested network information according to a network information obtaining request; an uplink analog data packet generating unit configured to when the length of the network information is less than or equal to the first When the length is longer, the upstream analog data packet is generated.
  • the upstream analog data packet includes the Internet Protocol frame header.
  • the source address and destination address of the upstream analog data packet are respectively set as the destination address and source address of the downstream data packet;
  • the upstream analog data packet Internet The protocol option adding unit is configured to add Internet protocol options to the Internet Protocol frame header of the uplink analog data packet;
  • the uplink analog data packet Internet Protocol option data writing unit is configured to write in the data area of the Internet protocol option of the uplink analog data packet Enter network information to be used to generate response information.
  • the response information generating unit 2520 includes: a network information obtaining unit, configured to obtain the requested network information according to a network information obtaining request; an uplink transmission control protocol empty packet generating unit, configured to be configured when the length of the network information is less than or equal to At the first length, an uplink transmission control protocol empty packet is generated, where the source address and destination address of the uplink transmission control protocol empty packet are set to the destination address and source address of the downlink data packet, and the source port of the uplink transmission control protocol empty packet Set the destination port number and destination port number as the transmission control protocol destination port number and transmission control protocol source port number in the Internetwork Protocol quintuple information of the downstream data packet; the upstream transmission control protocol empty packet data writing unit is configured to be in the upstream The data area of the transmission control protocol empty packet is written into the network information for generating response information.
  • the response information generating unit 2520 includes: a network information obtaining unit configured to obtain the requested network information according to a network information obtaining request; an uplink internet protocol packet option data writing unit configured to be the length of the network information When the length is less than or equal to the first length and the uplink Internet Protocol data packet is received, the network information is written into the data area of the Internet Protocol option of the uplink Internet Protocol data packet for generating response information.
  • the response information generating unit 2520 includes: a network information obtaining unit, configured to obtain the requested network information according to a network information obtaining request; an uplink transmission control protocol packet option data writing unit, configured to be a network information When the length is less than or equal to the first length and the uplink transmission control protocol data packet is received, the network information is written into the data area of the transmission control protocol option of the uplink transmission control protocol data packet for generating response information.
  • the network information obtaining unit includes: a first network information obtaining request forwarding unit configured to send the network information obtaining request to the first target non-user plane node; and the first network information response receiving unit configured to receive the first network information The network information of the first target non-user plane node returned by a target non-user plane node in response to the network information acquisition request.
  • the network information acquisition unit includes: a second network information acquisition request forwarding unit configured to send the network information acquisition request to the first target non-user plane node, so that the first target non-user plane node can transfer the network information
  • the acquisition request is sent to the second target non-user plane node, and receives the network information of the second target non-user plane node returned by the second target non-user plane node in response to the network information request;
  • the second network information response receiving unit is configured to receive The network information of the second target non-user plane node returned by the first target non-user plane node.
  • the network information acquiring unit includes: an updated network information receiving unit configured to receive updated network information of the second target non-user plane node returned by the first target non-user plane node.
  • the updated network information of the second target non-user plane node is sent by the second target non-user plane node to the first target non-user plane node when the network information of the second target non-user plane node changes or reaches a predetermined time interval.
  • each unit in the device for implementing network capability opening may refer to the content in the above method for implementing network capability opening, and details are not described herein again.
  • the example embodiments described here can be implemented by software, or can be implemented by combining software with necessary hardware. Therefore, the technical solution according to the embodiments of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, U disk, mobile hard disk, etc.) or on the network , Including several instructions to make a computing device (which can be a personal computer, a server, a touch terminal, or a network device, etc.) execute the method according to the embodiment of the present application.
  • a non-volatile storage medium which can be a CD-ROM, U disk, mobile hard disk, etc.
  • Including several instructions to make a computing device which can be a personal computer, a server, a touch terminal, or a network device, etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请提供了一种实现网络能力开放的方法及装置、电子设备和计算机可读存储介质，属于通信技术。该方法包括：获取下行数据包，其中，下行数据包中包括网络信息获取请求；将下行数据包发送至目标用户面节点；接收目标用户面节点返回的响应于网络信息获取请求的响应信息，其中，响应信息中包括网络信息获取请求所请求的网络信息。

Description

实现网络能力开放的方法、装置、电子设备和存储介质
相关申请的交叉引用
本申请基于申请号为202010179045.5、申请日为2020年03月15日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本申请涉及通信技术，涉及一种实现网络能力开放的方法及装置、电子设备和计算机可读存储介质。
背景技术
相关技术中的网络能力开放都是基于控制面来实现的。但是，基于控制面的网络能力开放，不能适用于实时变化、低时延的网络能力开放。
如何实现一种可以支持实时变化、低时延的网络能力开放是一个当前亟待解决的问题。
因此，需要一种新的实现网络能力开放的方法及装置、电子设备和计算机可读存储介质。
发明内容
本申请实施例提供一种实现网络能力开放的方法及装置、电子设备和计算机可读存储介质，通过用户面实现网络能力的开放，能够支持实时变化、低时延的网络能力开放。
本申请实施例提供一种实现网络能力开放的方法，方法包括：获取下行数据包，其中下行数据包中包括网络信息获取请求；将下行数据包发送至目标用户面节点；接收目标用户面节点返回的响应于网络信息获取请求的响应信息，其中，响应信息中包括网络信息获取请求所请求的网络信息。
本申请实施例提供一种实现网络能力开放的方法，方法包括：接收应用服务器发送的下行数据包，其中下行数据包中包括网络信息获取请求；响应于网络信息获取请求，生成响应信息，其中，响应信息中包括网络信息获取请求所请求的网络信息；将响应信息发送至应用服务器。
本申请实施例提供一种实现网络能力开放的装置，装置包括：下行数据获取单元，配置为获取下行数据包，其中下行数据包中包括网络信息获取请求；下行数据发送单元，配置为将下行数据包发送至目标用户面节点；响应信息接收单元，配置为接收目标用户面节点返回的响应于网络信息获取请求的响应信息，其中响应信息中包括网络信息获取请求所请求的网络信息。
本申请实施例提供一种实现网络能力开放的装置，装置包括：下行数据接收单元，配置为接收应用服务器发送的下行数据包，其中下行数据包中包括网络信息获取请求；响应信息生成单元，配置为响应于网络信息获取请求，生成响应信息，其中响应信息中包括网络信息获取请求所请求的网络信息；响应信息发送单元，配置为将响应信息发送至应用服务器。
本申请实施例提供了一种计算机可读存储介质，其上存储有计算机程序，程序被处理器执行时实现如上述实施例中的实现网络能力开放的方法。
本申请实施例提供了一种电子设备，包括：一个或多个处理器；存储装置，配置为存储一个或多个程序，当一个或多个程序被一个或多个处理器执行时，使得一个或多个处理器实现如上述实施例中的实现网络能力开放的方法。
在本申请的一些实施例所提供的技术方案中，通过用户面节点获取网络信息，一方面，由于网络信息只是增加一小部分用户面的数据，因此，对整个系统的影响非常小；另一方面，由于用户面数据传输的时延都非常小，因此，能够支持实时变化、低时延的网络能力开放。
附图说明
图1示出了相关技术中4G所定义的网络能力开放的架构示意图；
图2示出了相关技术中5G网络能力开放的架构示意图；
图3示出了相关技术中基于服务的架构示意图；
图4示出了相关技术中CAPIF的架构示意图；
图5示出了相关技术中一种EC架构与网络能力开放需求的示意图；
图6示出了相关技术中一种EC架构与网络能力开放需求的示意图；
图7示意性示出了根据本申请实施例的实现网络能力开放的方法的流程图；
图8示出了图7中所示的步骤S710在一实施例中的处理过程示意图；
图9示出了图7中所示的步骤S710在一实施例中的处理过程示意图；
图10示出了图7中所示的步骤S710在一实施例中的处理过程示意图；
图11示意性示出了根据本申请实施例的基于用户面的带内网络能力开放的架构示意图；
图12示意性示出了根据本申请实施例的应用服务器基于UPF获取网络信息的流程示意图；
图13示意性示出了根据本申请实施例的通过UPF获取网络信息的流程示意图；
图14示意性示出了根据本申请实施例的应用服务器基于RAN获取网络信息的流程示意图；
图15示意性示出了根据本申请实施例的通过RAN获取网络信息的流程示意图；
图16示意性示出了根据本申请实施例的应用服务器基于UE获取网络信息的流程示意图；
图17示意性示出了根据本申请实施例的通过UE获取网络信息的流程示意图；
图18示意性示出了根据本申请实施例的实现网络能力开放的方法的流程图；
图19示出了图18中所示的步骤S182在一实施例中的处理过程示意图；
图20示出了图18中所示的步骤S182在一实施例中的处理过程示意图；
图21示出了图18中所示的步骤S182在一实施例中的处理过程示意图；
图22示出了图18中所示的步骤S182在一实施例中的处理过程示意图；
图23示出了图18中所示的步骤S182在一实施例中的处理过程示意图；
图24示意性示出了根据本申请实施例的实现网络能力开放的装置的框图；
图25示意性示出了根据本申请实施例的实现网络能力开放的装置的框图。
具体实施方式
附图中所示的方框图仅仅是功能实体，不一定必须与物理上独立的实体相对应。即，采用软件形式来实现这些功能实体，或在一个或多个硬件模块或集成电路中实现这些功能实体，或在不同网络和/或处理器装置和/或微控制器装置中实现这些功能实体。
附图中所示的流程图仅是示例性说明，不是必须包括所有的内容和操作/步骤，也不是必须按所描述的顺序执行。例如，有的操作/步骤还可以分解，而有的操作/步骤可以合并或部分合并，因此实际执行的顺序有可能根据实际情况改变。
特别地，根据本申请的实施例，下文参考流程图描述的过程可以被实现为计算机软件程序。例如，本申请的实施例包括一种计算机程序产品，其包括承载在计算机可读存储介质上的计算机程序，该计算机程序包含用于执行流程图所示的方法的程序代码。
需要说明的是，本申请实施例所示的计算机可读存储介质可以是计算机可读信号介质或者计算机可读存储介质或者是上述两者的任意组合。
本申请实施例还提供了一种计算机可读存储介质，该计算机可读存储介质可以是上述实施例中描述的电子设备中所包含的；也可以是单独存在，而未装配入该电子设备中。上述计算机可读存储介质承载有一个或者多个程序，当上述一个或者多个程序被一个该电子设备执行时，使得该电子设备实现如下述实施例中的方法。例如，的电子设备可以实现如图6-图9、图17-图22所示的各个步骤。
图1示出了4G(the 4th generation mobile communication technology，第四代移动通信技术)所定义的网络能力开放的架构示意图。
在4G为机器对机器(Machine to Machine，M2M)(物联网应用的一种主要方式)所定义的第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)协议TS23.682促进分组数据网络和应用间的通信架构增强(Architecture enhancements to facilitate communications with packet data networks and applications)中，定义了如图1所示的4G网络能力开放架构。
图1为3GPP针对服务能力开放的架构(Architecture for Service Capability Exposure)，以使得3GPP网络通过3GPP网络接口(interfaces)，能够安全地开放它的服务和能力给托管应用程序(hosting an Application(s))的外部第三方服务提供者服务能力服务器/应用服务器(Services Capability Server/Application Server，SCS/AS)。
在3GPP协议TS23.682中还定义了在漫游情形下的网络能力开放架构与接口。
基于图1所示的网络能力开放架构，3GPP协议TS23.682中定义了很多支持M2M通信的网络能力开放，如：设备触发器(Device trigger)，分组消息传输(group message delivery)，监控(monitoring)，高延迟通信(High latency communications，HLC)等，几乎在3GPP协议TS23.682所定义的所有M2M功能与过程中。
其中，图1中的SDO是Service Data Objects的简称，即服务数据对象。API是Application Program Interface的简称，即应用程序接口，假设有n个API，n为大于或等于1的正整数。服务能力开放功能的英文全称是Service Capability Exposure Function，简称为SCEF。信任区域的英文是TRUST DOMAIN。HSS是Home Subscriber Server的简称，即归属订户服务器。PCRF是Policy and Charging Rules Function的简称，即策略与计费规则功能。PFDF是Packet Flow Description Function的简称，即数据包流量描述功能。MME是Mobility Management Entity的简称，即移动性管理实体。SGSN是Serving GPRS(General Packet Radio Service，通用分组无线业务)Support Node的简称，即服务GPRS支持节点。BM-SC是控制MBMS(Multimedia Broadcast/Multicast Service，多媒体广播/组播业务)会话的节点。S-CSCF是Service-Call Session Control Function的简称，即服务-呼叫会话控制功能。RCAF是RAN(Radio Access Network，无线接入网)Congestion Awareness Function的简称，无线拥塞感知功能。网络实体对应的英文是Network Entity。
图1中，T6a是指SCEF和服务MME之间使用的参考点。T6b是指SCEF与服务SGSN之间使用的参考点。T8是指SCEF和SCS/AS之间使用的参考点。S6t是指SCEF和HSS之间使用的参考点。Rx是指被SCEF和PCRF使用的参考点。Rx参考点的功能可以参见规范TS23.203。Ns是指SCEF和RCAF之间使用的参考点。Nt是指Reference point used被SCEF和PCRF使用的参考点。Nt参考点的功能可以参见3GPP协议TS 23.203。Nu是指被SCEF用于与PFDF交互的参考点。
图2示出了5G网络能力开放的架构示意图。
在3GPP协议TS23.501中定义了如图2所示的能力开放架构(Non-roaming architecture for Network Exposure Function in reference point representation，参考点表示中的网络开放功能的非漫游体系结构)。5G网络能力开放架构，是从4G演进过来的。
如图2所示，NEF(Network Exposure Function，网络开放功能)通过N33接口开放网络能力给AF(Application Function，应用功能)。具体的开放的网络能力分散在各个规范中，没有一个规范来收集所有的网络能力开放的功能与用例说明。
不过，N33接口是基于5G所定义的基于service(服务)的接口，在3GPP协议TS23.501的网络能力的对外开放(external exposure of network capability)给出了一些基本的网络能力开放，并在3GPP协议TS23.502的网络开放(network exposure)给出了一些基本的网络能力开放用例与流程。图2中的NF是Network Function的简称，即网络功能。
图3示出了基于服务的架构示意图。
5G架构引入了service based interface(基于服务接口)的架构。如图3所示，与4G架构相比，service based architecture(基于服务的架构，SBA)的好处是一个网络功能实体只关注其提供的服务(service)，而这个服务可以被任何其它的网络功能NF实体所使用，从而使得服务可以原子化，提升了5G系统的可扩展性。
在3GPP协议TS23.501和3GPP协议TS23.502对service based的NF的交互过程进行了详细的说明。
其中，NWDAF(Network Data Analytics Function)是一个网络数据分析功能实体，它能够从各个NF与操作维护管理(Operation Administration and Maintenance，OAM)中提取一些用户与网络的数据(利用大数据，机器学习，人工智能等技术)，并分析出网络的一些特定的特征出来，如在3GPP协议TS23.288中定义的：分片加载等级信息(Slice load level information)；观察到的服务体验信息(Observed service experience information)；NF加载信息(NF load information)；网络性能信息(Network performance information)；用户终端(User Equipment，UE，以下称之为终端)移动信息(mobility information)；UE通信信息(UE communication information)；预期UE行为参数(Expected UE behavioural parameters)；UE异常行为信息(UE abnormal behaviour information)；用户数据拥塞信息(User data congestion information)；服务质量(Quality of Service，QoS)持续性(sustainability)等10个网络信息。
且NWDAF可以将上面分析出的特征开放给AF或其它任何的NF(如接入和移动性管理功能(Access and Mobility Management Function，AMF)、会话管理功能(Session Management Function，SMF)。在3GPP协议TS23.288中对NWDAF的网络数据分析的信令交互与开放过程进行了标准化。
其中，图3中的NSSF是Network Slice Selection Function的简称，即网络切片选择功能，Nnssf是指发送给NSSF的Nnssf消息。Nnef是指发送给NEF的Nnef消息。NRF是Network Respository Function的简称，即网络存储功能，Nnrf是指发送给NRF的Nnrf消息。PCF是Policy Control Function的简称，即策略控制功能，Npcf是指发送给PCF的Npcf消息。UDM是Unified Data Management的简称，即统一数据管理，Nudm是指发送给UDM的Nudm消息。Naf是指发送给AF的Naf消息。Namf是指发送给AMF的Namf消息。Nsmf是指发送给SMF的Nsmf消息。Nnwdaf是指发送给NWDAF的Nnwdaf消息。AUSF是Authentication Server Function的简称，即鉴权服务器功能，Nausf是指发送给AUSF的Nausf消息。SCP是Service Communication Proxy的简称，即服务通信代理。UPF是User Plane Function的简称，即用户面功能。DN是Data Network的简称，即数据网络。UE与AMF之间通过N1接口交互，AMF与RAN之间通过N2接口交互，SMF与UPF之间通过N4接口交互，RAN与UPF之间通过N3接口交互，UPF与DN之间通过N6接口交互，UPF之间通过N9接口交互。
图4示出了通用API框架(common API framework，CAPIF)的架构示意图。在3GPP协议TS23.222中定义了网络能力开放的通用框架技术CAPIF，这里使用了API来表示网络能力开放，只是采用了通信中的原话来表示，如图4所示。
CAPIF定义了以下网络能力开放的通用功能：服务API的发布与实现；安全；OAM；上线(onboarding)；配置；互联互通；标识；路由；注册等各个功能，详细功能的说明与过程可参见3GPP协议TS23.222。
在图4中，公共陆地移动网络(Public Land Mobile Network，PLMN)信任区域是指由PLMN运营商或PLMN的可信第三方控制的受到足够安全保护的实体。CAPIF托管在PLMN运营商网络中。API调用器(API invoker)通常由与PLMN运营商有服务协议的第三方应用程序提供商提供。API invoker可以与PLMN运营商网络位于同一信任区域中。在基于参考点的模型中，PLMN信任区域中的API invoker通过CAPIF-1和CAPIF-2与CAPIF交互。来自PLMN信任区域外部的API invoker通过CAPIF-1e和CAPIF-2e与CAPIF交互。PLMN信任区域内的API提供者区域(API provider domain)的API开放功能(API exposing function)、API发布功能(API pulishing function)和API管理功能(API management function)分别通过CAPIF-3、CAPIF-4、CAPIF-5 与CAPIF核心功能(core function)交互。
在3GPP协议TS23.501中给出了边缘计算(edge computing，EC)的基本定义。通过将边缘应用服务器(Edge Application server，EAS)及分组数据单元(PSA(PDU(Protocol Data Unit，UPF)会话锚点(Session Anchor)))部署到离用户近的位置，减少UE与EAS之间的交互时延，从而提升用户的使用体验。
3GPP协议TR23.748中定义了如图5和图6所示的两个EC实现的架构。其中，3GPP协议TR23.758中定义了application层的EC的架构。3GPP协议TR23.748与TR23.758是从不同的维度来定义EC，互为补充。
本申请实施例中是以3GPP协议TR23.748的EC架构作为其解决方案的基线进行举例说明，但本申请并不限定于此，在其他实施例中，也可以扩展到适应于3GPP协议TR23.758的EC架构。
图5是利用上行分类器/分支点(Uplink classifier/Branching Point，UL CL/BP)访问EAS。图6是没有利用UL CL/BP访问EAS。
在上述图1-6相关技术中，所采用的网络能力开放都是基于控制面来实现的。其中控制面用于承载信令或控制消息，与之相对的是用户面，用户面也叫数据面或转发面，承载数据流量。
其中，基于控制面的方案是一种带外(out of band)的方案，即EAS/AS与UE通信时，EAS/AS一般需要通过AF与NEF或SCEF进行交互，才能得到5G或4G网络的一些信息。这种方法有以下缺点：
一方面，EAS/AS此时要么自身是具有AF功能的，要么与AF之间有一个接口进行交互，要求AF与4G或5G网络进行交互。而目前很多的互联网公司的EAS/AS不具有此功能。因此，这种方法的应用范围就大大地缩小了。
另一方面，即使EAS/AS具有AF的功能或具有与AF交互的功能，AF将EAS/AS的请求网络能力开放的请求发送到4G或5G网络时，4G或5G网络却不能将这个AF的请求与UE的当前正在无线网络的应用的网际互联协议(Internet Protocol，IP)数据关联起来，如4G或5G网络不能感知到这个AF的请求与UE的哪个QoS流(QoS flow)或演进分组系统(Evolved Packet System，EPS)承载(Bearer)关联起来。这是这种out of band的通知缺点。
此外，即使AF提供了UE的IP流的信息，但由于网络存在着网络地址转换(Network Address Translation，NAT)；以及由于一些IP流的生命期较短，EAS/AS可以不停地释放旧的IP流与建立新的IP流来实现一些小文件的传输(如网页上的各种小的目标object文件)。因此，AF很难跟上这种IP流的动态的变化。若一个IP流的生命周期较长，上面的AF的方法才可能有效。
由于无线通信的网络状态变化很快，若让无线基站来上报其传输速率的变化可能引起很多的控制面信令。在这种情形下，out of band的方案也不适用于这种实时变化、低延时(low latency)的网络能力开放。
因此，如何实现一种可以支持实时变化、low latency的网络能力开放就是一个非常大的挑战。特别是EC对这种要求支持实时、low latency的网络能力开放具有很大的需求，否则EC的优势不能很好地体现出来。
例如EAS/AS可以根据无线网络的带宽进行实时的下行速率的调整(如在游戏，视频，超高清语音等)，从而减少UE上应用的卡顿时间与卡顿次数，提升用户的体验质量(Quality of Experience，QoE)。
图7示意性示出了根据本申请实施例的实现网络能力开放的方法的流程图。本申请实施例提供的方法可以由任意具备计算处理能力的电子设备执行，例如应用服务器AS或者边缘应用服务器EAS。
本申请实施例中，能力是对底层复杂的实现进行了抽象，对外提供一个开发和执行环境。能力开放，实质上可以将其看成是一种新颖的网络开放模式。网络能力开放平台在整合和利用电信核心网资源的基础上，采用统一的多层级的开放接口来开放电信能力，聚集互联网上有潜力、有创造力的开发者，让开发者能利用这些能力不断地创造出更好的商业应用和服务，形成一大批新的移动互联网应用及服务。
如图7所示，本申请实施例提供的实现网络能力开放的方法可以包括以下步骤。
在步骤S710中，获取下行数据包，其中，下行数据包中包括网络信息获取请求。
本申请实施例中，网络信息获取请求是指EAS/AS(也可以表示为(E)AS，即可以是EAS，也可以是AS)发送的，且用于从目标用户面节点获得所请求的网络信息的请求。具体获取下行数据包的方式可以参照下述图8-10。
在步骤S720中，将下行数据包发送至目标用户面节点。
本申请实施例中，EAS/AS可以根据当前所要请求的网络信息来确定哪个用户面节点作为当前的目标用户面节点。这里的用户面节点是指用于承载数据流量的节点，与其相对应的是控制面节点，控制面节点是指用于承载信令或控制消息的节点。在不同的通信网络中，用户面节点和控制面节点可以是不同的。
例如，在4G网络中，控制面节点可以包括MME、HSS、PCRF，也可以包括SGW-C和PGW-C，其中SGW即Service Gateway，服务网关)，SGW-C是指SGW-Control，即控制面服务网关；PGW即PDN(Public Data Network，公用数据网)GateWay，PDN网关或者分组网关，PGW-C是指PGW-Control，即控制面分组网关；用户面节点部分包含于SGW和PGW中，也可以是SGW-U和PGW-U。
再例如，在5G网络中，用户面节点可以包括终端(UE)、无线接入网(RAN，这里称之为基站)和用户面网关(这里以UPF(用户面功能)为例进行举例说明，但本申请实施例并不限定于此)，这里的UPF可以是I-UPF，也可以是PSA UPF，根据不同的情况可以采用相适应的UPF。在下面的举例说明中，以目标用户面节点为UE、RAN、UPF中的任意一种进行举例说明，但本申请实施例并不限定于此。其中，UPF负责在无线接入网和Internet之间转发流量、报告流量使用情况、QoS策略实施等，对应4G中的SGW/PGW的用户面。控制面节点可以包括AMF、SMF、PCF、UDM、AUSF、NEF、NRF、NSSF等。
在步骤S730中，接收目标用户面节点返回的响应于网络信息获取请求的响应信息，其中，响应信息中包括网络信息获取请求所请求的网络信息。
在一些实施例中，当目标用户节点为终端，且终端使用互联网控制消息协议回送请求(ICMP(Internet Control Message Protocol)ECHO)包的数据(Data)区域返回响应信息时，方法还可以包括：若检测到终端返回的响应信息中的网络信息的长度超过预设阈值，则切换到使用用户面网关或者基站来返回网络信息获取请求所请求的网络信息。
本申请实施例中，在使用ICMP ECHO包的Data来传输数据时，因为UE的用户面是要经过空口(空中接口的简称)的，会消耗无线空口的资源，在这种情形下，若EAS/AS确定UE返回的响应信息中的网络信息的长度较大，则EAS/AS停止使用UE来提供网络能力开放，而切换到使用UPF或RAN来进行网络能力开放，将目标标识(Target identification，Target ID)修改为UPF或RAN，从而避免影响空口的资源，具体可以参见下文实施例的内容。
本申请实施方式提供的实现网络能力开放的方法，通过用户面节点获取网络信息，一方面，由于网络信息只是增加一小部分用户面的数据，因此，对整个系统的影响非常小；另一方面，由于用户面数据传输的时延都非常小，因此，能够支持实时变化、低时延的网络能力开放。
网际互联协议(Internet Protocol，IP协议)是使用最为广泛的通信协议，在请求注解(Request For Comments，RFC)791(IP协议的说明规范)中定义了网际互联协议版本4(Internet Protocol version 4，IPv4)的IP头(Header，也可以称之为帧首)，IP头包含的选项(Options)如下所示。
RFC 791:
Options:variable                       //选项：变量
The options may appear or not in datagrams.They must be implemented by all IP modules(host and gateways).What is optional is their transmission in any particular datagram,not their implementation.//这些选项可能出现在数据报中，也可能不出现在数据报中。它们必须由所有IP模块(主机和网关)实现。可选的是它们在任何特定数据报中的传输，而不是它们的实现。
In some environments the security option may be required in all datagrams.//在某些环境中，所有数据报中都可能需要安全选项。
The option field is variable in length.There may be zero or more options.There are two cases for the format of an option://选项字段的长度是可变的。可能有零个或多个选项。选项的格式有两种情况：
Case 1:A single octet of option-type.//情况1：选项类型的单个8比特字节。
Case 2:An option-type octet,an option-length octet,and the actual option-data octets.//情况2：选项类型8比特字节、选项长度8比特字节和实际选项数据8比特字节。
The option-length octet counts the option-type octet and the option-length octet as well as the option-data octets.//选项长度8比特字节统计选项类型8比特字节和选项长度8比特字节以及选项数据8比特字节。
The option-type octet is viewed as having 3fields://选项类型8比特字节被视为具有3个字段：
1 bit copied flag,                        //1比特复制标志，
2 bits option class,                      //2比特选项类别，
5 bits option number.                    //5比特选项号。
The copied flag indicates that this option is copied into all fragments on fragmentation.//复制的标志表示此选项复制到片段的所有片段中。
0＝not copied                                //0＝未复制
1＝copied                                    //1＝复制
The option classes are:                        //选项类别包括：
0＝control                                    //0＝控制
1＝reserved for future use                 //1＝保留以备将来使用
2＝debugging and measurements              //2＝调试和测量
3＝reserved for future use                 //3＝保留以备将来使用
即，IP Options为一个字节总长，或者为选项类型(Option-Type，1字节)+选项长度(Option-Length，1字节)+选项数据(Option Data，1-38字节)，即选项类型+选项长度+选项数据。而Option-Type的8比特(8bits，1字节)分为3部分：copied flag(1bit)，option class(2bits)，option number(5bits)。
而RFC 4727(experimental values In IPv4，IPv6，ICMPv4，ICMPv6，UDP(User Datagram Protocol，用户数据报协议)，and TCP headers，即IPv4、IPv6、ICMPv4、ICMPv6、UDP和TCP头中的实验值)给出了IPv4 Option-Type用于experimental的值，如下所示。
RFC 4727：
IPv4 Option Numbers(in-parameters initial section)(Section 2.5)//IPv4选项号(在参数初始部分)(第2.5章节)
Figure PCTCN2020128209-appb-000001
对于3GPP而言，3GPP可以向IANA(The Internet Assigned Numbers Authority，互联网 数字分配机构)申请一个专用的Option-Type(当本申请实施例提供的方法进入标准)。或3GPP可以继续使用RFC 4727所定义的实验值(但有可能出现其它的IP应用使用此实验值而出现冲突)。
见下面实施例的说明，一个IPv4Header Options最多可以传输38个字节的内容(40-2＝38)。
需要说明的是，对于IPv6，在RFC 3296中定义了253，254两个Option-Type作为experimental使用。这里就不再做详细的说明了。后面实施例是以IPv4来作说明的，同样的方法也可以应用于IPv6。
下面结合图8实施例来说明本申请实施例可以利用IP Option进行网络能力开放的数据传输。
图8示出了图7中所示的步骤S710在一实施例中的处理过程示意图。如图8所示，本申请实施例中上述步骤S710可以进一步包括以下步骤。
在步骤S711中，获取第一待发送下行数据，其中，第一待发送下行数据包括网际互联协议帧首(Internet Protocol Header，IP帧首或者IP头)。
本申请实施例中，第一待发送下行数据可以是EAS/AS当前准备或者需要发送给UE的任意的数据，当该第一待发送下行数据是IP包时，该IP包包括IP Header。
在步骤S712中，在第一待发送下行数据的网际互联协议帧首上增加网际互联协议选项。
本申请实施例中，在第一待发送下行数据的IP包的IP Header上增加IP Option。
在步骤S713中，在第一待发送下行数据的网际互联协议选项的数据区域写入网络信息获取请求，以用于生成下行数据包。
本申请实施例中，在第一待发送下行数据的IP包的IP Header的IP Option的Data区域或者部分写入上述待发送给目标用户面节点的网络信息获取请求，以生成发送给目标用户面节点的下行数据包。
例如，IPv4 Header如下表1所示：
表1 IPv4 Header
Figure PCTCN2020128209-appb-000002
表1中，DF是Don’t Fragment标签的简称，即不要切分标签，表示数据包不允许切分，如果该包的长度超出了网络设备的处理能力，并且又打上了DF标签，那么该网络设备会丢弃掉该数据包。MF是More Fragments标签，用于表示数据包是否被分片了，如果被分片了该位为1，如果没有被分片那么该位为0。
由上表1可知，IP头最小20字节。因IP header中的Head Length最大取值为0x0F(16进制)，也就是15，因此IP头的总长度为15*4＝60字节，这样，IP Option的最大长度为60-20＝40字节。
需要说明的是，若对写入网络信息获取请求的第一待发送下行数据启动加密与完整性保护处理，则下行数据包的长度包含加密与完整性保护处理后的第一待发送下行数据+完整性保护消 息验证码(message authentication code，MAC)。这里的MAC是指在网络能力开放交互时，用于消息完整性保护的消息验证码。一般MAC可以取8字节或者4字节。这种情况下，IP Option只能传输38-8＝30或者38-4＝34字节的网络信息获取请求。
一般情况下，一个IP Option所能提供的字节长度用于EAS或AS向目标用户面节点发送控制命令(例如包括上述网络信息获取请求的下行数据包)是足够的。若EAS或AS向目标用户面节点发送包括上述网络信息获取请求的下行数据包时，一个IP Option提供的40字节的长度不足，这时，将IP Option的数据中的前一个或两个字节(本申请实施例并不限定于此)定义为数据的当前位置，即作为网络信息获取请求数据的指针(data pointer)，将提供的网络信息获取请求分割到多个IP包的IP Option中。一个IP Option的Data区域能够提供40-1(Option-Type)-1(Option-Length)-0/1/2(data pointer)＝38/37/36字节。
另外，由于IP协议不能保证IP包的到达次序与发送次序一致，因此，接收方可以通过data pointer来实现数据的重组。但若中间的一个IP包丢失，则可能整个data不能重组成功，在这种情形下，EAS或AS就需要重新发送包括上述网络信息获取请求的下行数据包。
因此，在一些实施例中，当上述网络信息获取请求的长度(注意，若进行了加密与完整性保护处理，则还要包含加密与完整性保护处理后的MAC，下面实施例与此相同)>38字节时，EAS或AS也可以采用ICMP ECHO包的Data部分或区域来发送上述网络信息获取请求。ICMP ECHO包的Data部分或区域可传输1500(整个以太网帧可以提供的数据包大小)-20(IP头大小)-8(ICMP头大小)＝1472字节的网络信息获取请求，即使在采用启动与完整性保护处理后，MAC占用8字节或者4字节，仍然可以传输1472-8/4＝1464/1468字节的网络信息获取请求，传输效率相比于IP option有1468/34＝43或者1464/30＝49倍的提升。
传输控制协议(transmission control protocol，TCP)是使用最为广泛的传输层协议。在RFC 793(注意TCP不区分IPv4或IPv6，只有一个)中定义了TCP头包含的Options如下所示。
RFC 793:
Options:variable
Options may occupy space at the end of the TCP header and are a multiple of 8 bits in length.All options are included in the checksum.An option may begin on any octet boundary.There are two cases for the format of an option://选项可能会占用TCP帧首末尾的空间，长度是8比特的倍数。所有选项都包含在校验和中。选项可以从任何八进制边界开始。选项的格式有两种情况：
Case 1:a single octet of option-kind.//情况1：选项类型的单个8比特字节。
Case 2:an octet of option-kind,an octet of option-length,and the actual option-data octets.//情况2：选项类型的一个8比特字节，选项长度的一个8比特字节和实际选项数据的多个8比特字节。
The option-length counts the two octets of option-kind and option-length as well as the option-data octets.//选项长度统计选项类型和选项长度的两个8比特字节以及选项数据的多个8比特字节。
Note that the list of options may be shorter than the data offset field might imply.The content of the header beyond the End-of-option option must be header padding(i.e.,zero).//请注意，选项列表可能比可能隐含的数据偏移字段要短。超出选项结尾的选项的帧首的内容必须是帧首填充(例如，零)。
A TCP must implement all options.  //TCP必须实现所有选项。
Currently defined options include(kind indicated in octal)://当前定义的选项包括(以八进制表示类型)：
Figure PCTCN2020128209-appb-000003
Figure PCTCN2020128209-appb-000004
即TCP Option为一个字节总长，或者为option-kind+option-length+option data即选项类型+选项长度+选项数据，与上述IPv4的Option非常类似。
而RFC 4727(experimental values In IPv4,IPv6，ICMPv4，ICMPv6,UDP,and TCP headers)中给出了TCP option-kind用于experimental的值，如下所示。
Figure PCTCN2020128209-appb-000005
对于3GPP而言，3GPP可以向IANA申请一个专用的option-kind(当本申请实施例提供的方法进入标准)。3GPP可以继续使用RFC 4727所定义的实验值(这时需要使用RFC 6994协议，见下面的内容)。
RFC 6994:
This document extends the option structure for experimental codepoints(253,254)with an experiment identifier(ExID),which is either 2 or 4 bytes in length.The ExID is used to differentiate experiments and is the first field after Kind and Length,as follows://本文档使用实验标识符(ExID)扩展了实验代码点(253，254)的选项结构，该标识符的长度为2或4字节。ExID用于区分实验，是继类型和长度之后的第一个字段，如下所示：
Figure PCTCN2020128209-appb-000006
Figure 2.TCP Experimental Option with a 16-bit ExID//图2.16比特ExID的TCP实验选项
Figure PCTCN2020128209-appb-000007
Figure 3.TCP Experimental Option with a 32-bit ExID//图3.32比特ExID的TCP实验选项
当两个应用都使用RFC 4727所定义的使用TCP的option-kind的253或254时，就可能出现相互冲突，而RFC 6994在option-data的开始引入一个ExID(长度可以是2字节或4字节)，这样两个应用出现冲突的几率就大大地降低了。另外，应用可以向IANA申报所使用的ExID，这样其它的IP应用就不能再使用这个申请的ExID，这样就更加降低了出现冲突的可能性。
3GPP可以继续使用RFC 4727所定义的实验值，也可以向IANA申请一个专用的ExID(当本申请实施例提供的方法进入标准时)。
见下面实施例的说明，类似于IPv4 header option，一个TCP header option最多可以传输38个字节的内容。
下面结合图9来说明本申请实施例可以利用TCP option来实现网络能力开放的数据传输。
图9示出了图7中所示的步骤S710在一实施例中的处理过程示意图。
如图9所示，本申请实施例中上述步骤S710可以进一步包括以下步骤。
在步骤S714中，获取第二待发送下行数据，第二待发送下行数据包括传输控制协议帧首。
本申请实施例中，第二待发送下行数据可以是EAS/AS当前准备或者需要发送给UE的任意的数据，当该第二待发送下行数据是TCP包时，该TCP包包括TCP Header。
在步骤S715中，在第二待发送下行数据的传输控制协议帧首上增加传输控制协议选项。
本申请实施例中，在第二待发送下行数据的TCP包的TCP Header上增加TCP Option。
在步骤S716中，在第二待发送下行数据的传输控制协议选项的数据区域写入网络信息获取请求，以用于生成下行数据包。
本申请实施例中，在第二待发送下行数据的TCP包的TCP Header的TCP Option的Data区域或者部分写入上述待发送给目标用户面节点的网络信息获取请求，以生成发送给目标用户面节点的下行数据包。
例如，TCP Header如下表2所示：
表2 TCP Header
Figure PCTCN2020128209-appb-000008
上述表2中，URG是urgent的缩写，紧急位；ACK是acknowledgement的缩写，确认位；PSH是push的缩写，推送位；RST是reset的缩写，重置位；SYN是synchronization的缩写，请求位；FIN是finish的缩写，结束位。
由此可知，TCP头最小20字节。类似于IP header，TCP因head length最大取值为0x0F(16进制)，也就是15，因此TCP头的总长度为15*4＝60字节，这样，TCP option的最大长度为60-20＝40字节。
需要说明的是，若对写入网络信息获取请求的第二待发送下行数据启动加密与完整性保护处理，则下行数据包的长度包含加密与完整性保护处理后的第二待发送下行数据+完整性保护MAC。一般MAC可以取8字节或者4字节。这种情况下，TCP Option与IP Option类似，只能传输38-8＝30或者38-4＝34字节的网络信息获取请求。
一般情况下，一个TCP Option所能提供的字节长度用于EAS或AS向目标用户面节点发送控制命令(例如包括上述网络信息获取请求的下行数据包)是足够的。若EAS或AS向目标用户面节点发送包括上述网络信息获取请求的下行数据包时，一个TCP Option提供的40字节的长度不足，这时，将TCP Option的数据中的前一个或两个字节(本申请实施例并不限定于此)定义为数据的当前位置，即作为网络信息获取请求数据的指针(data pointer)，将提供的网络信息获取请求分割到多个TCP包的TCP Option中。一个TCP Option的Data区域能够提供40-1(Option-Type)-1(Option-Length)-1/2(data pointer)＝37/36字节。
但是这只是基于在每个现有的TCP包上增加一个option。当网络能力开放的数据较长时，可能需要很多的TCP包，并且有可能持续较长的时间。此时，在这种情况下还是采用下述实施例中的ICMP ECHO包的Data的方法好。
另外，由于TCP协议能最终实现TCP包的按顺序重新，因此也就可以间接地保证接收方顺序地接收到网络能力开放数据(包括上述网络信息获取请求的下行数据包，其中包括传输过程中TCP包的丢失，这是比IP option好的方面)。
因此，在一些实施例中，当上述网络信息获取请求的长度(注意，若进行了加密与完整性保护处理，则还要包含加密与完整性保护处理后的MAC，下面实施例与此相同)>38字节时，EAS或AS也可以采用ICMP ECHO包的Data部分或区域来发送上述网络信息获取请求。ICMP ECHO包的Data部分或区域可传输1472-8/4＝1464/1468字节的网络信息获取请求，传输效率相比于TCP option有1468/34＝43或者1464/30＝49倍的提升。
上述图8和9实施例中，当EAS或AS向目标用户面节点(例如，UE/RAN/UPF)发送包括上述网络信息获取请求的下行数据包时，若此时没有可以发送的第一待发送下行数据或第二待发送下行数据，其中一种解决方法是一直等到有可以发送的第一待发送下行数据或第二待发送下行数据为止。
但这种方法对较长的下行的网络信息获取请求而言，这种方法仍然可能出现上面的多次传输的问题。为此，对于网络信息获取请求长度>38字节的情况，不采用等待可用的第一待发送下行数据或第二待发送下行数据，而直接采用上述的ICMP ECHO包的Data部分或区域的方法，Data用于传输网络信息获取请求。
另外，还可利用发送一个或者多个ACK的TCP空包(即不传输实际用户数据的包)，且在每个TCP空包中传输一部分网络能力开放的数据，这样不会造成TCP连接的任何问题。但有些TCP协议栈将重复TCP空包(即TCP包的ACK number)不变到达三次后，EAS/AS会降低向UE发送TCP实际数据包的速率，从而给用户的体验造成影响。
此外，还可利用下行(downlink，DL)模拟(dummy)IP包的option来传输上述网络信息获取请求。下面结合图10实施例进行说明。
在下面的实施例中，提出使用IPv4的ICMP(见RFC792)，例如ICMPv4的ECHO与ECHO reply来传输网络能力开放的数据，则传输的效率可以大大地增加，并可以实现排序与重组的功能。
Echo or Echo Reply Message://回送或者回送响应消息
Figure PCTCN2020128209-appb-000009
The identifier and sequence number may be used by the echo sender to aid in matching the  replies with the ECHOs.For example,the identifier might be used like a port in TCP or UDP to identify a session,and the sequence number might be incremented on each ECHO sent.The echoer returns these same values in the echo reply.//回送发送者可以使用标识符和序列号来帮助将回送响应与回送请求相匹配。例如，标识符可以像TCP或UDP中的端口一样用于标识会话，并且序列号可以在发送的每个回送请求上递增。回送器在回送响应中返回这些相同的值。
需要说明的是，本申请实施例中也提出利用ICMP ECHO的IP头中的option来传输数据(只能传输38个字节)，此时的IP包(包含有ICMP的ECHO)称为IP Dummy(IP模拟)包，但不要与使用ICMP ECHO中的Data来传输网络信息获取请求或者网络信息数据的方法混淆。
参见下文的实施例可知，ICMP的ECHO/ECHO reply的消息头只有8个字节，一般加上IP头(ICMP是在IP之上传输的)，所以可传输的数据一般为1500-20-8＝1472字节，比IPoption与TCP option能够传输的数据(38字节)大得多，效率是TCP包或IP包(包括IP dummy包)option的1472/38＝39倍。
其中，Type/Code＝8/0表示ECHO(回送请求)，Type/Code＝0/0表示ECHO reply(回送响应)。规范对ECHO的identifier(标识器)与sequence number(序列号，简称为SN)没有作任意的限定，但是，ECHO reply的identifier与SN必须取与对应的ECHO相同的identifier与SN的值。
图10实施例描述了利用dummy IP包与ICMP实现网络能力开放的数据传输。
图10示出了图7中所示的步骤S710在一实施例中的处理过程示意图。如图10所示，本申请实施例中上述步骤S710可以进一步包括以下步骤。
在步骤S717中，生成下行模拟(dummy)数据包，下行模拟数据包包括网际协议帧首。
RFC 792：
Figure PCTCN2020128209-appb-000010
由此可知，IP头20字节，ICMP 8字节头(包括上述Type，Code，Checksum，Identifier，Sequence Number)。依据RFC 792：对于ICMP的ECHO：Type/Coder＝8/0，ECHO Reply:Type/Coder＝0/0。且Extended Header(扩展头)可以是一个变化的ID(SN)。
在步骤S718中，在下行模拟数据包的网际协议帧首上增加网际协议选项。
当EAS或AS向目标用户面节点例如UE/RAN/UPF发送包括上述网络信息获取请求的下行数据包时，若此时没有可以发送的第一待发送下行数据或第二待发送下行数据，如前，一种解决方法是一直等到有第一待发送下行数据或第二待发送下行数据为止，但可能在较长的时间内仍没有第一待发送下行数据或第二待发送下行数据。此时，采用产生DL dummy IP包的方法，并利用此DL dummy IP的option来传输网络信息获取请求相关的数据。
在步骤S719中，在下行模拟数据包的网际协议选项的数据区域写入网络信息获取请求，以用于生成下行数据包。
例如，产生一个DL dummy IP包(例如下面实施例中以该DL dummy IP包为ICMP ECHO包为例进行举例说明，但本申请实施例并不限定于此)：采用(一次或多次)发送ICMP的ECHO，并且每次发送的ECHO中的identifier设置为UDP或TCP的一个端口号，SN设置为一个递增的序列号。当UE/RAN/UPF收到EAS/AS发送的在IP option部分包含上述网络信息获取请求的ECHO后，UE/RAN/UPF可以向EAS/AS回复一个表示确认收到的对应的ECHO  reply，EAS/AS可以将接收到的ECHO Reply的SN与identifier和ECHO的SN与identifier进行比较，若两者均相同，表明UE/RAN/UPF收到了这个ICMP ECHO包，这样，这个ICMP ECHO包的IP头上的option数据(包含上述网络信息获取请求)就被目标用户面节点例如UE/RAN/UPF接收到了。若在预定的时间内未收到目标用户面节点返回的ECHO Reply，则EAS/AS再次重发这个ECHO，并在IP头的option中包含对应的网络信息获取请求，被重发的ECHO与之前的SN与identifier保持一致。
但是，上述实施例的方法仍然是低效率的，因为每次DL dummy IP option或IP option或TCP option只能传输38字节的内容，因此，在一些实施例中，也可以采用另一种方法，由于ICMP的ECHO可以包含1500-20-8＝1472个字节的数据，因此可以将网络信息获取请求数据作为ECHO中的Data部分发送出去，此时的传送效率远大于每次只传输38字节的DL dummy IP option或IP option或TCP option的方法，且同时可以应用ID+SN，及SN每次加1的方法来实现多次的ECHO传输：在一定的时间内未收到ECHO Reply(通过对比ID+SN来确认是否收到)，则再次重发这个ECHO(在重发时，ID+SN值是重发的ECHO包的ID+SN值)的，从而实现网络获取请求的可靠与按序传输。因为每次新的ECHO包的SN都加1，所以接收方可以根据SN号进行接收数据的排序。
因此，当网络能力开放的数据长度不超过38字节(注意，若进行了加密与完整性保护处理，则还要包含加密与完整性处理后的MAC，下面的实施例与此相同)时，则可以选择使用DL dummy IP option或IP option或TCP option的方法。当网络能力开放的数据长度超过38字节小于1472字节时，则可以运行一次ICMP ECHO与ECHO reply的方法。当网络能力开放的数据超过1472字节时，则可通过多次运行递增SN号的ICMP ECHO与ECHO reply的方法，实现网络信息获取请求的可靠与按序传输。
下面以EC为参考架构对本申请实施例提供的方法进行举例说明，实际上本申请实施例提供的方法可以应用于任何的2G，3G，4G，5G与其它任何的无线网络。
UE、无线基站(RAN，无线接入网络)或PSA，SGW，用户面服务网关(SGW-User，SGW-U)，GGSN，中间UPF(intermediate-UPF，I-UPF)，UPF，PGW，用户面PDN网关(PGW-User，PGW-U)等都可以上传数据给EAS或AS。但由于UE的移动性，会引起基站、SGW，I-UPF的变化。因此，这里以不变的用户面节点例如UE和PSA(即UPF)或PGW-U来给出举例说明。但由基站所提供的无线网络的信息非常重要，因此以基站(RAN)为例来给出移动后的节点如何继续提供网络能力开放给EAS或AS。
图11示意性示出了根据本申请实施例的基于用户面的带内(in-band)网络能力开放的架构示意图。
如图11所示，这里假设EAS1/2/3是部署在边缘计算环境(edge computing environment)上的application server。EAS1/2/3分别向UE，RAN与UPF进行网络能力开放的通信。
需要说明的是，edge computing environment只是表示实现edge computing的AS的一个平台，在标准化阶段，这个名字可能会发生改变。
AS4这里指互联网应用，它可以是运营商自己的业务，也可以是第三方的AS(如某搜索引擎公司的server，某互联网公司的游戏game server)，在图11中只显示AS4与UPF进行网络能力开放的交互，但本申请实施例并不限定于此，AS4也可以如同EAS1/2/3一样，与UE、RAN，UPF进行交互。
后面为了说明简单，这里都假定AS或EAS都是可以与UE、RAN、UPF进行网络能力交互的。
继续参考图11，当AS或EAS向UE/RAN/UPF所请求的网络信息不能由UE/RAN/UPF自己得到，但可以由其它NF获得时，则UE/RAN/UPF可以与这些NF(如AMF，SMF)进行交互，从这些NF获取。若UE/RAN/UPF与这些NF之间没有直接交互的接口时，则UE和RAN可通过AMF，UPF可通过SMF向其它NF获取。后面的实施例给出相关的实现方式。
本申请实施例中，网络的其它非用户面节点(如控制面节点)，通过UE，基站，PSA (PGW/PGW-U，GGSN)等网络节点将一些关键的网络能力开放给EAS或AS，从而可以实现全网络的网络能力开放。例如其它NF可以通过SMF或者AMF将网络信息提供给EAS或AS。
由于IP与TCP数据的上行数据是直接到达EAS或AS的，EAS或AS的下行数据是直接到达PSA、基站和UE的，因此EAS或AS可以直接与他们进行交互，从而实现in-Band的能力开放，并且网络能力的数据只是增加一小部分用户面的数据，对整个系统的影响非常小，且用户面数据的传输时延都非常小。
图12示意性示出了根据本申请实施例的应用服务器基于UPF获取网络信息的流程示意图。图12对UPF利用ICMP/IP option/TCP option实现所请求的网络信息的传输进行说明。图12可以包括以下步骤。
步骤S1，UE建立一个PDU会话(session)，分配到一个IP地址，通过这个IP地址与(E)AS建立了IP连接，传输的IP流可以经过RAN与UPF到达(E)AS。
步骤S2：这里假设(E)AS决定向UPF请求网络信息，向UPF发送网络信息获取请求。
本申请实施例中，(E)AS决定请求谁来提供网络信息，根据当前所请求的网络信息来决定。例如，若所请求的网络信息是与应用或终端相关的，则可以向UE请求提供网络信息。若所请求的网络信息是与无线相关的信息，则可以向RAN请求提供网络信息。若所请求的网络信息不属于以上两种情况，则可以向UPF请求提供网络信息。
步骤S3，这个步骤是可选的。(E)AS与UPF之间进行相互认证，并协商安全算法(共用算法)与采用共同的安全密钥(共用密钥)。在下面的实施例中，均以(E)AS与UPF之间进行加密与完整性保护处理的安全交互传输方式为例进行举例说明。
步骤S4，产生DL dummy IP包或在DL数据的IP头或TCP头上增加选项，在选项的数据区域包含请求信息，这里的请求信息(Request Information)是指网络信息获取请求相关的信息，例如可以包括当前向谁请求获取网络信息(Target ID，Request Type，Request parameters)，Request Type即请求类型是指当前请求哪种类型的网络信息，Request parameters是指请求获取网络信息的一些其它参数，根据所请求的网络信息进行确定。
在这里又可以分为以下几种情况：
若(E)AS有待发送的DL数据，则(E)AS可以在下行的IP包头上加上option，或者，若该下行的IP包还是TCP包，则可以改为在TCP包头上加上Option。在IP option或者TCP option的data部分包含有Target ID(这里＝UPF)，Request Type和Request parameters。
若(E)AS没有待发送的下行的任何数据，则(E)AS可以产生一个DL dummy IP包(如ICMP ECHO，注意此时的ICMP ECHO中的DATA部分无任何特定的内容)或TCP空包(只有TCP头没有任何的用户数据)。
另外，(E)AS也可以等到有下行的数据包后，再继续执行下述步骤。
步骤S5a，若上述步骤S4采用了在DL的IP头上增加Option来传输网络信息获取请求，则(E)AS可以向UPF发送DL IP数据包，该DL IP数据包带Option选项，且在IP Option的data部分包括(Option-Type，Target ID，Request Type，Request parameters，MAC)。其中Option-Type可以采用上文中所例举的30/94/158/222或使用3GPP在IANA上申请的一个特定值。这里的Target ID(＝UPF)。且这里假设上述步骤S3确定网络能力开放交互要进行加密与完整性保护。
步骤S5b，若IP包是TCP包，(E)AS决定采用TCP option来传输网络信息获取请求，即上述步骤S4采用了在DL的TCP头上增加Option来传输网络信息获取请求，则(E)AS可以向UPF发送DL TCP数据包，该DL TCP数据包带Option选项，且在TCP Option的data部分包括(Option-kind，Target ID，Request Type，Request parameters，MAC)。其中Option-kind见上文中所例举中的253/254或使用3GPP在IANA上申请的一个特定值，且可以使用一个ExID(RFC 6994，下文与此相同)。TCP Option中的数据处理同步骤S5a。
步骤S6，UPF接收到(E)AS发送的DL IP包或者DL TCP包之后，对该DL IP包或者DL  TCP包进行如下检查：
第一，判断该DL IP包或者DL TCP包中是否有option存在，若有option，则检查Option-type(IPv4)或Option-kind(TCP)是否是规范所指定的。
第二，检查该DL IP包或者DL TCP包中的Target ID是否是UPF。若是，则UPF进行下述步骤；若不是，则UPF不对其进行本申请实施例所指出的特定处理，将该DL IP包或者DL TCP包继续往RAN方向发送。
第三，若进行了安全加密与完整性保护，则利用该DL IP包或者DL TCP包中的MAC进行安全验证。若通过了安全验证，则继续下述步骤；若未通过安全验证，则停止执行步骤步骤。
第四，根据该DL IP包或者DL TCP包中的Request Type，判断UPF是否支持该Request Type。若UPF支持Request Type，则继续后面的过程。否则，UPF不作任何特殊的处理，后面的步骤不再执行。
步骤S7，UPF删除DL IP或TCP包中的对应的option，然后将他们往下行方向发送，即UPF将DL IP数据包(不包含前面的Option)通过RAN发送至UE。
图12中，UPF可以记录该DL IP包或者DL TCP包的IP五元组信息及IP头中的标识(identification)字段，后面UPF提供网络信息给(E)AS时，需要记录的IP五元组信息及IP头中的identification字段。
步骤S8，若UPF可以并且需要立即提供网络信息，UPF判断提供的网络信息的大小。
步骤S8a，若UPF判定网络信息长度(包含完整性处理后的MAC，后同)>第一长度(这里假设为38字节)，则用UPF产生一个ICMP ECHO包，例如产生ICMP回送包(ECHO包)且数据(Data)部分包含响应信息(Response Information)，还可以包括Target ID。
其中，所生成的ICMP ECHO包的源地址(例如源IP地址)可以设置为上述步骤S7中记录的IP五元组信息中的目的地址(例如目的IP地址)，目的地址(例如目的IP地址)可以设置为上述步骤S7中记录的IP五元组信息的源地址(例如源IP地址)。
ICMP ECHO包中的Type/code＝8/0，identifier取一特定值，如上述步骤S7中记录的IP五元组信息中的UDP或TCP包的目的端口号。若上述步骤S7中记录的IP五元组信息既不是UDP也不是TCP包，则ICMP ECHO包的identifier可以取上述步骤S7中记录的IP五元组信息中的identification。对于ICMP ECHO包的sequence number，若UPF没有使用过，则UPF取一特定值，如产生一个随机值。
图12中，为了防止不同的IP流采用相同的随机值，UPF可以以上述步骤S7中记录的IP五元组信息来产生一个随机值。然后UPF向(E)AS发送包含其所获得的网络信息的响应信息。
图12中，若UPF判定网络信息长度(包含完整性处理后的MAC，后同)>第二长度(这里假设为1472字节)，则UPF需要传输剩下的网络信息，此时，ICMP ECHO包中的Type/Code，identifier可以与上述实施例保持一致，只是SN依次递增1，直到将获得的网络信息传输完成。
其中，UPF可以在预定的时间内通过ECHO reply来判断哪些ICMP ECHO包被(E)AS正确地接收，若UPF没有收到(E)AS返回的对应的ECHO reply，则可以重新发送之前的ICMP ECHO包，此时ICMP ECHO包还是与要重发的ECHO消息头保持相同。
步骤S8b，若UPF判定网络信息长度(包含完整性处理后的MAC，后同)<＝38字节，则UPF可以产生一个UL dummy IP包或者TCP空包，该UL dummy IP包或者TCP空包带选项，选项包含响应信息。
例如若为UL dummy IP包，则选项中可以包括(Option-Type，Target ID，Response Information)。其中，该UL dummy IP包的源IP地址可以设置为上述步骤S7记录的IP五元组信息中的目的IP地址，该UL dummy IP包的目的IP地址可以设置为上述步骤S7记录的IP五元组信息中的源IP地址。然后加上IP Option。Option-Type可以取上文中例举的30/94/158/222或使用3GPP在IANA上申请的一个特定值。然后设置Target ID(＝UPF)表明是从UPF回复的。Response Information包含UPF所提供的网络信息。若激活了加密与完整性 保护，则Response Information还包含MAC。
另外，若网络信息长度<＝38字节，则UPF也可以选择产生一个UL TCP空包，其中该UL TCP空包的源IP地址可以设置为上述步骤S7记录的IP五元组信息中的目的IP地址，该UL TCP空包的目的IP地址可以设置为上述步骤S7记录的IP五元组信息中的源IP地址。该UL TCP空包的目的端口可以设置为上述步骤S7记录的IP五元组信息中的TCP源端口，该UL TCP空包的源端口可以设置为上述步骤S7记录的IP五元组信息中的TCP目的端口，然后加上TCP Option，option-kind可以取上文中例举的253/254或使用3GPP在IANA上申请的一个特定值。且可以使用一个ExID。然后设置target ID(＝UPF)表明是从UPF回复的。Response information包含提供的网络信息。若激活了加密与完整性保护，则Response information还包含MAC。
图12中，若UPF判定网络信息长度(包含完整性处理后的MAC，后同)<＝38字节，且UPF决定等待后续的上行数据时携带该网络信息，则上述步骤S8不执行。
图12中，若UPF不能立即提供网络信息，如UPF需要与SMF进行交互，从SMF获取SMF或其它NF提供的网络信息，则UPF可以发起与SMF的交互，则步骤S8和下面的步骤S10不执行。
步骤S9，UPF收到UE经RAN发送的上行(uplink，UL)的IP数据包。
步骤S10，当UPF收到UL IP包时，则可以在该UL的IP包的option的数据data中包含(Option-Type，Target ID，Response Information)。即UPF将要提供的网络信息加到上行IP包的IP option。或者，若该UL IP包同时还是UL TCP包，则可以在该上行TCP包的TCP option上加上UPF所要提供的网络信息，此时，传输的内容同上述步骤8b。
需要注意的是，这里只是加上一个IP option，且要重新计算IP头中的checksum，其它信息均不改变；或者，只是加上一个TCP option，且要重新计算TCP头中的checksum，其它信息均不改变。
图12中，若加上option后，引起IP分片，则UPF可以继续等待后续的上行IP/TCP包，一般而言大部分的上行的TCP包都只是TCP ACK包，加上option不会引起IP分片。若没有可用的上行IP/TCP包，UPF在等待一定的时间后，若还没有合适的上行IP/TCP包用于加上option以传输网络信息，则可以使用上述步骤S8a的方法，产生一个ICMP包或使用步骤S8b的方法产生一个UL IP dummy包或TCP空包来传输网络信息。
图12中，若UPF当前没有可以提供的网络信息(如还在等待SMF的响应)，则UPF可以将上述步骤S9收到的上行数据不作任何的特殊处理(如继续上传给(E)AS)，此时上述步骤S10不执行。同样的，要注意的是，在下述步骤S11之前，UPF收到的上述步骤S9的上行数据，可能有多个。在这种情形下，都是不作任何的特殊处理(如继续上传给(E)AS)。
步骤S11，UPF与SMF交互，从其它NF获取网络信息。当UPF收到了SMF自身或其它NF提供的网络信息时，继续执行下述步骤。
步骤S12a，若UPF决定立即将得到的网络信息提供给(E)AS或网络信息长度>38字节，则可采用上述步骤S8a或步骤S8b所定义的方法，产生ICMP ECHO包或UL dummy包或TCP空包带选项，选项包含响应信息，例如选项中可以包括(Option-Type，Target ID，Response Information)，这里的Response Information包括UPF从SMF自身或其它NF获取的网络信息。
步骤S12b，当UPF确定将得到的网络信息通过上行的数据包携带给(E)AS时，则可以采用上述步骤S9和步骤S10的方法，即UPF从UE经过RAN接收UL的IP数据包。然后，执行步骤S12c，使得该接收的UL的IP或TCP数据包带选项，选项的data中包含响应信息，例如可以包括(Option-Type，Target ID，Response Information)，这里的Response Information包括UPF从SMF自身或其它NF获取的网络信息。
步骤S13，UE与(E)AS可以继续IP包的上下行传输。
图12中，若(E)AS在发送给UPF的命令(下行数据包的网络信息获取请求)中，包含请求UPF每隔一段时间(例如可以设定时间间隔)报告网络信息或当网络信息发生改变时，再 次向(E)AS发送更新网络信息。则在时间未到达或网络信息状态没有改变时，UE与(E)AS的IP通信继续，此时，UPF不作任何特定的处理。
其中，(E)AS发送给UPF的下行数据包中的Request information中，EAS可以指定获取谁的网络信息(例如是UPF还是SMF，或者其它NF)；还可以指定获取网络信息后，是UPF直接返回给EAS还是经过处理后再发送给EAS；以及还可以指定是一次性返回，还是多次返回。Request information中包括的内容可以参照控制面中的相关内容。
步骤S14，在(E)AS要求的时间间隔到达或网络信息状态发生改变时，UPF就需要再次上传更新网络信息，此时的步骤S15(产生ICMP回送包或UL Dummy IP包或TCP空包带选项，选项包含响应信息(Option-Type，Target ID，Response Information))，步骤S16(UPF接收从UE经RAN发送的UL的IP数据包),步骤S 17(UL的IP或TCP数据包带选项，选项包含响应信息(Option-Type，Target ID，Response Information))的处理同前面的步骤S12a，步骤S12b与步骤S12c。
需要说明的是，若启动加密与完整性保护处理，则网络信息长度包含处理后的网络信息+完整性保护MAC。一般MAC可以取8字节或者4字节。这样UL IP option、UL dummy IP option或者UL TCP option只能传输38-8/4＝30/34字节的网络信息。而ICMP ECHO的Data可传输1472-8/4＝1464/1468字节的网络信息，网络信息的传输效率得到1468/34＝43或者1464/30＝49倍的提升。
在3GPP规范中没有定义通过UE，RAN或UPF来获取网络信息的方法，在下面的图13，15和17中分别给出方法。其中的基本思想是类似的，即可以通过AMF或SMF来获取网络信息。详细的步骤参见下面的实施例。
图13示意性示出了根据本申请实施例的通过UPF获取网络信息的流程示意图。图13给出了通过UPF获取网络信息以提供给(E)AS的过程。
这里需要说明的是，在图13中，当UPF自身可以提供(E)AS所需的网络信息时(例如，测量UPF与UE之间通信的时延，UE的总传输速率等)，则这种情况下UPF无需与SMF进行交互。若UPF只需获取SMF上的网络信息提供给(E)AS时，则图13中的下述步骤S3(包括步骤S3a和S3b)，S4(包括步骤S4a和S4b)，S7都不会执行。
图13只是给出UPF通过SMF向一个NF获取网络信息的实例。在实际的情形中，UPF可能需要通过SMF向不同的NF获取网络信息，然后集中起来向(E)AS报告，即图13中的步骤S2-S5可执行多次，只是NF分别不同。
图13可以包括以下步骤。
步骤S1，这里以(E)AS向UPF发送下行IP数据包为例进行举例说明，该下行IP数据包带option(Option-Type，Target ID，Request Type，Request Parameters，MAC)。但本申请实施例并不限定于此，具体实现可以参照上述图12中的步骤S1-S10。
步骤S2-S5，对应于上述图12中的步骤S11。下面对其进行具体阐述。
步骤S2，UPF向SMF发送N4消息以发送网络数据请求，该N4消息是请求SMF获取(E)AS当前所需的网络信息，此N4消息可以包含(E)AS发送给UPF的网络信息获取请求中的请求类型(即当前所请求的网络信息的类型，上述的Request Type)、请求参数(上述的Request Parameters)。即N4:Network Data Request(Request Type,Request Parameters)，Request Parameters例如可以包括valid time(有效时间)，Times(次数)等。
因为此N4消息是本申请实施例提出的新的消息名，因此，此N4消息的消息名的名称及例如参数可以由3GPP标准来定义，但对应的功能是请求SMF来获取网络信息。
步骤S3a是对应于SMF向其它的NF(目标NF，即当前SMF向其请求获取网络信息的其它的NF)发送Nnf_网络数据获取请求，即Nnf_NetworkData Get Request(Request Type,Request Parameters)，即Nnf_NetworkData Get Request消息中包含当前所请求的网络信息的类型(请求类型)及请求参数。
步骤S4a是目标NF响应于SMF发送的Nnf_网络数据获取请求，返回给SMF的Nnf_网络 数据获取响应，即Nnf_NetworkData Get Response(network data information)，network data information表示其它NF返回给SMF的网络信息。
步骤S3a和步骤S4a中的Nnf_NetworkData Get Request/Nnf_NetworkData Get Response是一次性的交互过程，即(E)AS当前发送给UPF的Request Parameters中并没有指定需要UPF每隔一段时间向其返回网络信息，也没有指定需要UPF在网络信息变化时，自动向其返回更新网络信息，例如可以通过上述valid time和/或Times(次数)等来指定。
步骤S3b，对应于SMF向目标NF发送Nnf_网络数据订阅请求消息，即Nnf_NetworkData Subscribe Request(Request Type,Request Parameters)。
步骤S4b，目标NF响应于SMF发送的Nnf_NetworkData Subscribe Request消息，向SMF返回Nnf_网络数据通知，即Nnf_NetworkData notify(network data information)。
在图13中的步骤S3b和步骤S4b中，会评阅当前的网络信息状态，当网络信息状态发生变化时，目标NF可以持续的给SMF提供更新网络信息。
Nnf_NetworkData Subscribe Request和Nnf_NetworkData notify中的参数的含义和处理类似于图13中的步骤S3a，步骤S4a。
当目标NF收到Nnf_NetworkData Subscribe Request消息时，会立即向SMF报告一个当前的网络信息状态。SMF可以向NWDAF请求相关的网络分析信息，可参见上述图3中所列出的10个网络信息，这个请求与响应消息及其名称与详细参数，参见3GPP协议TS23.288。
Nnf_NetworkData Subscribe Request和Nnf_NetworkData notify不是一次性的交互过程，在图13的下述步骤S7中，当目标NF发现网络信息发生改变时，会持续地向SMF报告更新网络信息，这个过程可以持续到SMF所设置的次数(Times)与/或时间(valid time)。
步骤S5，当SMF收到目标NF回复的网络信息时，通过N4消息将网络信息传递给UPF，即向UPF发送N4消息，该N4消息包括网络数据响应，即N4：Network Data Response(network data information)。
当图13中的步骤S2中的Network Data Request显示出需要持续获取网络信息时，SMF采用图13中的步骤S3b和步骤S4b的方式，而图13中的步骤S3a和步骤S4a一般可以用于取一些静态的数据或配置。
若网络信息数据可以直接由SMF来提供，则图13中的步骤S3和S4不执行。
图13中的步骤S6a，UPF通过产生ICMP ECHO包的Data部分或UL dummy IP包带Option(Option-Type，Target ID，Response Information)或TCP空包带Option(Option-kind，Target ID，Response Information)，返回给(E)AS，Target ID(＝UPF)，这里的Response Information包括network data information。
图13中的步骤S6b，UPF也可以通过UL的IP数据包带Option(Option-Type，Target ID，Response Information)或TCP数据包带Option(Option-kind，Target ID，Response Information)，返回给(E)AS，Target ID(＝UPF)，这里的Response Information包括network data information。
图13中的步骤S6a和S6b的具体实现可以参照上述图12中的步骤S12a，S12b，S12c。
图13中的步骤S7-S9，参照上述图12中的步骤S14。下面对图13的步骤S7-S9进行说明。
步骤S7，当目标NF检测到网络信息发生改变时，通过向SMF发送Nnf_网络数据通知将新的网络信息数据即更新网络信息提供给SMF，即发送Nnf_NetworkData Notify(network data information)，此处的network data information是指更新网络信息。(很多的例子可参见3GPP协议TS23.288)。
若网络信息数据直接由SMF来提供时，则图13中的步骤S7不执行。
步骤S8，SMF收到新的网络信息数据时，通过一个N4消息传递发送给UPF，即SMF向UPF发送N4消息，该N4消息包括网络数据响应，即N4：Network Data Response(network data information)，此处的network data information是指更新网络信息。
步骤Step9，UPF确认收到网络信息，即UPF收到SMF发送的网络信息或者更新网络信息后，向SMF发送一个N4消息：网络数据告知，以通知SMF其已经收到了SMF所发送的网络 信息，例如N4:Network Data Notify acknowledge。
需要说明的是，当SMF发送给UPF的网络信息数据较大时，由于N4接口可以一次性传输很大的数据，因此不需要重复执行图13中的步骤S8与S9。
图13中的步骤S10a和S10b，参照上述图12中的步骤S15-S17。
图14示意性示出了根据本申请实施例的应用服务器基于RAN获取网络信息的流程示意图。图14对RAN利用ICMP/IP option/TCP option实现所请求的网络信息的传输进行说明。本申请实施例可以包括以下步骤。
步骤S1，UE建立一个PDU session(会话)，分配到一个IP地址，通过这个IP地址与(E)AS建立了IP连接，传输的IP流可以经过RAN与UPF到达(E)AS。
步骤S2：这里假设(E)AS决定向RAN请求网络信息，经过UPF向RAN发送网络信息获取请求。
步骤S3，这个步骤是可选的。(E)AS与RAN之间进行相互认证，并协商安全算法(共用算法)与采用共同的安全密钥(共用密钥)。在下面的实施例中，均以(E)AS与RAN之间进行加密与完整性保护处理的安全交互传输方式为例进行举例说明。
步骤S4，产生DL dummy IP包或在DL数据的IP头或TCP头上增加选项，在选项的数据区域包含请求信息，这里的请求信息(Request Information)是指网络信息获取请求相关的信息，例如可以包括(Target ID，Request Type，Request parameters)，其中Target ID是指当前向谁请求获取网络信息，Request Type即请求类型是指当前请求哪种类型的网络信息，Request parameters是指请求获取网络信息的一些其它参数，根据所请求的网络信息进行确定。
在这里又可以分为以下几种情况：
若(E)AS有待发送的DL数据，则(E)AS可以在下行的IP包头上加上option，或者，若该下行的IP包还是TCP包，则可以改为在TCP包头上加上Option。在IP option或者TCP option的data部分包含有Target ID(这里＝RAN)，Request Type和Request parameters。
若(E)AS没有待发送的下行的任何数据，则(E)AS可以产生一个DL dummy IP包(如ICMP ECHO，注意此时的ICMP ECHO中的DATA部分无任何特定的内容)或TCP空包。
另外，(E)AS也可以等到有下行的数据包后，再继续执行下述步骤。
步骤S5a，若上述步骤S4采用了在DL的IP头上增加Option来传输网络信息获取请求，则(E)AS可以向RAN发送DL IP数据包，该DL IP数据包带Option选项，且在IP Option的data部分包括(Option-Type，Target ID，Request Type，Request parameters，MAC)。其中Option-Type可以采用上文中所例举的30/94/158/222或使用3GPP在IANA上申请的一个特定值。这里的Target ID(＝RAN)。且这里假设上述步骤S3确定网络能力开放交互要进行加密与完整性保护。
步骤S5b，若IP包是TCP包，(E)AS决定采用TCP option来传输网络信息获取请求，即上述步骤S4采用了在DL的TCP头上增加Option来传输网络信息获取请求，则(E)AS可以向RAN发送DL TCP数据包，该DL TCP数据包带Option选项，且在TCP Option的data部分包括(Option-kind，Target ID，Request Type，Request parameters，MAC)。其中Option-kind见上文中所例举中的253/254或使用3GPP在IANA上申请的一个特定值，且可以使用一个ExID(RFC 6994，下文与此相同)。TCP Option中的数据处理同步骤S5a。
步骤S6，RAN接收到(E)AS发送的DL IP包或者DL TCP包之后，对该DL IP包或者DL TCP包进行如下检查：
第一，判断该DL IP包或者DL TCP包中是否有option存在，若有option，则检查Option-type(IPv4)或Option-kind(TCP)是否是规范所指定的。
第二，检查该DL IP包或者DL TCP包中的Target ID是否是RAN。若是，则RAN进行下述步骤，若不是，则RAN不对其进行本申请实施例所指出的特定处理，将该DL IP包或者DL TCP包继续往UE方向发送。
第三，若进行了安全加密与完整性保护，则利用该DL IP包或者DL TCP包中的MAC进 行安全验证。若通过了安全验证，则继续下述步骤；若未通过安全验证，则停止执行步骤步骤。
第四，根据该DL IP包或者DL TCP包中的Request Type，判断RAN是否支持该Request Type。若RAN支持Request Type，则继续后面的过程。否则，RAN不作任何特殊的处理，后面的步骤不再执行。
需要说明的是，RAN接收到的(E)AS发送的DL IP包或者DL TCP包，是经过UPF转发的，因此，UPF接收到后也会对该DL IP包或者DL TCP包进行检查，此时Target ID指向的是RAN，则UPF不对其进行任何特殊的处理，继续发送给RAN。
步骤S7，RAN删除DL IP或TCP包中的对应的option，然后将他们往下行方向发送，即RAN将DL IP数据包(不包含前面的Option)发送至UE。
图14中，RAN可以记录该DL IP包或者DL TCP包的IP五元组信息及IP头中的identification(标识)字段，后面RAN提供网络信息给(E)AS时，需要记录的IP五元组信息及IP头中的identification字段。
步骤S8，若RAN可以并且需要立即提供网络信息，RAN判断提供的网络信息的大小。
步骤S8a，若RAN判定网络信息长度(包含完整性处理后的MAC，后同)>第一长度(这里假设为38字节)，则用RAN产生一个ICMP ECHO包，例如产生ICMP回送包(ECHO包)且数据(Data)部分包含响应信息(Response Information)，还可以包括Target ID。
其中所生成的ICMP ECHO包的源地址(例如源IP地址)可以设置为上述步骤S7中记录的IP五元组信息中的目的地址(例如目的IP地址)，目的地址(例如目的IP地址)可以设置为上述步骤S7中记录的IP五元组信息的源地址(例如源IP地址)。
ICMP ECHO包中的Type/code＝8/0，identifier取一特定值，如上述步骤S7中记录的IP五元组信息中的UDP或TCP包的目的端口号。若上述步骤S7中记录的IP五元组信息既不是UDP也不是TCP包，则ICMP ECHO包的identifier可以取上述步骤S7中记录的IP五元组信息中的identification。对于ICMP ECHO包的sequence number，若RAN没有使用过，则RAN取一特定值，如产生一个随机值。
图14中，为了防止不同的IP流采用相同的随机值，RAN可以以上述步骤S7中记录的IP五元组信息来产生一个随机值。然后RAN向(E)AS发送包含其所获得的网络信息的响应信息。
图14中，若RAN判定网络信息长度(包含完整性处理后的MAC，后同)>第二长度(这里假设为1472字节)，则RAN需要传输剩下的网络信息，此时，ICMP ECHO包中的Type/Code，identifier可以与上述实施例保持一致，只是SN依次递增1，直到将获得的网络信息传输完成。
其中，RAN可以在预定的时间内通过ECHO reply来判断哪些ICMP ECHO包被(E)AS正确地接收，若RAN没有收到(E)AS返回的对应的ECHO reply，则可以重新发送之前的ICMP ECHO包，此时ICMP ECHO包还是与要重发的ECHO消息头保持相同。
步骤S8b，若RAN判定网络信息长度(包含完整性处理后的MAC，后同)<＝38字节，则RAN可以产生一个UL dummy IP包或者TCP空包，该UL dummy IP包或者TCP空包带选项，选项包含响应信息。
例如若为UL dummy IP包，则选项中可以包括(Option-Type，Target ID，Response Information)。其中，该UL dummy IP包的源IP地址可以设置为上述步骤S7记录的IP五元组信息中的目的IP地址，该UL dummy IP包的目的IP地址可以设置为上述步骤S7记录的IP五元组信息中的源IP地址。然后加上IP Option。Option-Type可以取上文中例举的30/94/158/222或使用3GPP在IANA上申请的一个特定值。然后设置Target ID(＝RAN)表明是从RAN回复的。Response Information包含RAN所提供的网络信息。若激活了加密与完整性保护，则Response Information还包含MAC。
另外，若网络信息长度<＝38字节，则RAN也可以选择产生一个UL TCP空包，其中该UL TCP空包的源IP地址可以设置为上述步骤S7记录的IP五元组信息中的目的IP地址，该UL TCP空包的目的IP地址可以设置为上述步骤S7记录的IP五元组信息中的源IP地址。该 UL TCP空包的目的端口可以设置为上述步骤S7记录的IP五元组信息中的TCP源端口，该UL TCP空包的源端口可以设置为上述步骤S7记录的IP五元组信息中的TCP目的端口，然后加上TCP Option，option-kind可以取上文中例举的253/254或使用3GPP在IANA上申请的一个特定值。且可以使用一个ExID。然后设置target ID(＝RAN)表明是从RAN回复的。Response information包含提供的网络信息。若激活了加密与完整性保护，则Response information还包含MAC。
图14中，若RAN判定网络信息长度(包含完整性处理后的MAC，后同)<＝38字节，且RAN决定等待后续的上行数据时携带该网络信息，则上述步骤S8不执行。
图14中，若RAN不能立即提供网络信息，如RAN需要与AMF进行交互，从AMF获取AMF或其它NF提供的网络信息，则RAN可以发起与AMF的交互，则步骤S8和下面的步骤S10不执行。
步骤S9，RAN收到UE发送的UL的IP数据包。
步骤S10，当RAN收到UL IP包时，则可以在该UL的IP包的option的数据data中包含(Option-Type，Target ID，Response Information)。即RAN将要提供的网络信息加到上行IP包的IP option。或者，若该UL IP包同时还是UL TCP包，则可以在该上行TCP包的TCP option上加上RAN所要提供的网络信息，此时，传输的内容同上述步骤S8b。
需要注意的是，这里只是加上一个IP option，且要重新计算IP头中的checksum，其它信息均不改变；或者，只是加上一个TCP option，且要重新计算TCP头中的checksum，其它信息均不改变。
图14中，若加上option后，引起IP分片，则RAN可以继续等待后续的上行IP/TCP包，一般而言大部分的上行的TCP包都只是TCP ACK包，加上option不会引起IP分片。若没有可用的上行IP/TCP包，RAN在等待一定的时间后，若还没有合适的上行IP/TCP包用于加上option以传输网络信息，则可以使用上述步骤S8a的方法，产生一个ICMP包或使用步骤S8b的方法产生一个UL IP dummy包或TCP空包来传输网络信息。
图14中，若RAN当前没有可以提供的网络信息(如还在等待AMF的响应)，则RAN可以将上述步骤S9收到的上行数据不作任何的特殊处理(如继续上传给(E)AS)，此时上述步骤S10不执行。同样的，要注意的是，在下述步骤S11之前，RAN收到的上述步骤S9的上行数据，可能有多个。在这种情形下，都是不作任何的特殊处理(如继续上传给(E)AS)。
步骤S11，RAN与AMF交互，从其它NF获取网络信息。当RAN收到了AMF自身或其它NF提供的网络信息时，继续执行下述步骤。
步骤S12a，若RAN决定立即将得到的网络信息提供给(E)AS或网络信息长度>38字节，则可采用上述步骤S8a或步骤S8b所定义的方法，产生ICMP ECHO包或UL dummy包或TCP空包带选项，选项包含响应信息，例如选项中可以包括(Option-Type，Target ID，Response Information)，这里的Response Information包括RAN从AMF自身或其它NF获取的网络信息。
步骤S12b，当RAN确定将得到的网络信息通过上行的数据包携带给(E)AS时，则可以采用上述步骤S9和步骤S10的方法，即RAN从UE接收UL的IP数据包。然后，执行步骤S12c，使得该接收的UL的IP或TCP数据包带选项，选项的data中包含响应信息，例如可以包括(Option-Type，Target ID，Response Information)，这里的Response Information包括RAN从AMF自身或其它NF获取的网络信息。
步骤S13，UE与(E)AS可以继续IP包的上下行传输。
图14中，若(E)AS在发送给RAN的命令(下行数据包的网络信息获取请求)中，包含请求RAN每隔一段时间(例如可以设定时间间隔)报告网络信息或当网络信息发生改变时，再次向(E)AS发送更新网络信息。则在时间未到达或网络信息状态没有改变时，UE与(E)AS的IP通信继续，此时，RAN不作任何特定的处理。
其中，(E)AS发送给RAN的下行数据包中的Request information中，(E)AS可以指定获 取谁的网络信息(例如是RAN还是AMF，或者其它NF)；还可以指定获取网络信息后，是RAN直接返回给(E)AS还是经过处理后再发送给(E)AS；以及还可以指定是一次性返回，还是多次返回。Request information中包括的内容可以参照控制面中的相关内容。
步骤S14，在(E)AS要求的时间间隔到达或网络信息状态发生改变时，RAN就需要再次上传更新网络信息，此时图14的步骤S15(产生ICMP回送包或UL Dummy IP包或TCP空包带选项，选项包含响应信息(Option-Type，Target ID，Response Information))，步骤S16(RAN接收从UE发送的UL的IP数据包)，步骤S17(UL的IP或TCP数据包带选项，选项包含响应信息(Option-Type，Target ID，Response Information))的处理同图14的步骤S12a，步骤S12b与步骤S12c。
需要说明的是，图14的上述步骤8b、S10、S12a、S12c、S15和S17中，UPF对上行IP包或TCP包中有Option-Type或者Option-kind的包(定义为获取网络信息或者网络能力开放的包)不作任何特殊的处理，继续发送给(E)AS。
图15示意性示出了根据本申请实施例的通过RAN获取网络信息的流程示意图。图15给出了通过RAN获取网络信息以提供给(E)AS的过程。
这里需要说明的是，在图15中，当RAN自身可以提供(E)AS所需的网络信息时(例如，RAN自身可以测量当前的无线空口传输速率，能否得到当前基站下连接的UE的数量等)，则这种情况下RAN无需与AMF进行交互。并且，很多的网络能力开放是与RAN上的空口相关的，因此RAN一般都是直接提供自身的测量数据作为网络信息提供给(E)AS，而无需向AMF请求网络信息。
若RAN只需获取AMF上的网络信息提供给(E)AS时，则图15中的下述步骤S3(包括步骤S3a和S3b)，S4(包括步骤S4a和S4b)，S7都不会执行。
图15只是给出RAN通过AMF向一个NF获取网络信息的实例。在实际的情形中，RAN可能需要通过AMF向不同的NF获取网络信息，然后集中起来向(E)AS报告，即图15中的步骤S2-S5可执行多次，只是NF分别不同。
图15可以包括以下步骤。
步骤S1，这里以(E)AS向RAN发送下行IP数据包为例进行举例说明，该下行IP数据包带option(Option-Type，Target ID，Request Type，Request Parameters，MAC)。但本申请并不限定于此，具体实现可以参照上述图14中的步骤S1-S10。
步骤S2-S5，对应于上述图14中的步骤S11。下面对其进行具体阐述。
步骤S2，RAN向AMF发送N2消息以发送网络数据请求，该N2消息是请求AMF获取(E)AS当前所需的网络信息，此N2消息可以包含(E)AS发送给RAN的网络信息获取请求中的请求类型(即当前所请求的网络信息的类型，上述的Request Type)、请求参数(上述的Request Parameters)。即N2:Network Data Request(Request Type,Request Parameters)，Request Parameters例如可以包括valid time(有效时间)，Times(次数)等。
因为此N2消息是本申请实施例提出的新的消息名，因此，此N2消息的消息名的名称及具体的参数可以由3GPP标准来定义，但对应的功能是请求AMF来获取网络信息。
步骤S3a是对应于AMF向其它的NF(目标NF，即当前AMF向其请求获取网络信息的其它的NF)发送Nnf_网络数据获取请求，即Nnf_NetworkData Get Request(Request Type,Request Parameters)，即Nnf_NetworkData Get Request消息中包含当前所请求的网络信息的类型(请求类型)及请求参数。
步骤S4a是目标NF响应于AMF发送的Nnf_网络数据获取请求，返回给AMF的Nnf_网络数据获取响应，即Nnf_NetworkData Get Response(network data information)，network data information表示其它NF返回给AMF的网络信息。
步骤S3a和步骤S4a中的Nnf_NetworkData Get Request/Nnf_NetworkData Get Response是一次性的交互过程，即(E)AS当前发送给RAN的Request Parameters中并没有指定需要RAN每隔一段时间向其返回网络信息，也没有指定需要RAN在网络信息变化时，自动向其返回更新网络 信息，例如可以通过上述valid time和/或Times(次数)等来指定。
步骤S3b，对应于AMF向目标NF发送Nnf_网络数据订阅请求消息，即Nnf_NetworkData Subscribe Request(Request Type,Request Parameters)。
步骤S4b，目标NF响应于AMF发送的Nnf_NetworkData Subscribe Request消息，向AMF返回Nnf_网络数据通知，即Nnf_NetworkData notify(network data information)。
在图15中的步骤S3b和步骤S4b中，会评阅当前的网络信息状态，当网络信息状态发生变化时，目标NF可以持续的给AMF提供更新网络信息。
Nnf_NetworkData Subscribe Request和Nnf_NetworkData notify中的参数的含义和处理类似于图15中的步骤S3a，步骤S4a。
当目标NF收到Nnf_NetworkData Subscribe Request消息时，会立即向AMF报告一个当前的网络信息状态。AMF可以向NWDAF请求相关的网络分析信息，可参见上述图3中所列出的10个网络信息，这个请求与响应消息及其名称与详细参数，参见3GPP协议TS23.288。
Nnf_NetworkData Subscribe Request和Nnf_NetworkData notify不是一次性的交互过程，在图15的下述步骤S7中，当目标NF发现网络信息发生改变时，会持续地向AMF报告更新网络信息，这个过程可以持续到AMF所设置的次数(Times)与/或时间(valid time)。
步骤S5，当AMF收到目标NF回复的网络信息时，通过N2消息将网络信息传递给RAN，即向RAN发送N2消息，该N2消息包括网络数据响应，即N2：Network Data Response(network data information)。
当图15中的步骤S2中的Network Data Request显示出需要持续获取网络信息时，AMF采用图15中的步骤S3b和步骤S4b的方式，而图15中的步骤S3a和步骤S4a一般可以用于取一些静态的数据或配置。
若网络信息数据可以直接由AMF来提供，则图15中的步骤S3和S4不执行。
图15中的步骤S6a，RAN通过产生ICMP ECHO包的Data部分或UL dummy IP包带Option(Option-Type，Target ID，Response Information)或TCP空包带Option(Option-kind，Target ID，Response Information)，返回给(E)AS，Target ID(＝RAN)，这里的Response Information包括network data information。
图15中的步骤S6b，RAN也可以通过UL的IP数据包带Option(Option-Type，Target ID，Response Information)或TCP数据包带Option(Option-kind，Target ID，Response Information)，返回给(E)AS，Target ID(＝RAN)，这里的Response Information包括network data information。
图15中的步骤S6a和S6b的具体实现可以参照上述图14中的步骤S12a，S12b，S12c。
图15中的步骤S7-S9，参照上述图14中的步骤S14。下面对图15的步骤S7-S9进行说明。
步骤S7，当目标NF检测到网络信息发生改变时，通过向AMF发送Nnf_网络数据通知将新的网络信息数据即更新网络信息提供给AMF，即发送Nnf_NetworkData Notify(network data information)，此处的network data information是指更新网络信息。(很多的例子可参见3GPP协议TS23.288)。
若网络信息数据直接由AMF来提供时，则图15中的步骤S7不执行。
步骤S8，AMF收到新的网络信息数据时，通过一个N2消息传递发送给RAN，即AMF向RAN发送N2消息，该N2消息包括网络数据响应，即N2：Network Data Response(network data information)，此处的network data information是指更新网络信息。
步骤Step9，RAN确认收到网络信息，即RAN收到AMF发送的网络信息或者更新网络信息后，向AMF发送一个N2消息：网络数据告知，以通知AMF其已经收到了AMF所发送的网络信息，例如N2:Network Data Notify acknowledge。
需要说明的是，当AMF发送给RAN的网络信息数据较大时，由于N2接口可以一次性传输很大的数据，因此不需要重复执行图15中的步骤S8与S9。
图15中的步骤S10a和S10b，参照上述图14中的步骤S15-S17。
图16示意性示出了根据本申请实施例的应用服务器基于UE获取网络信息的流程示意图。 图16对UE利用ICMP/IP option/TCP option实现所请求的网络信息的传输进行说明。图16可以包括以下步骤。
步骤S1，UE建立一个PDU session(会话)，分配到一个IP地址，通过这个IP地址与(E)AS建立了IP连接，传输的IP流可以经过RAN与UPF到达(E)AS。
步骤S2：这里假设(E)AS决定向UE请求网络信息，经过UPF和RAN向UE发送网络信息获取请求。
步骤S3，这个步骤是可选的。(E)AS与UE之间进行相互认证，并协商安全算法(共用算法)与采用共同的安全密钥(共用密钥)。在下面的实施例中，均以(E)AS与UE之间进行加密与完整性保护处理的安全交互传输方式为例进行举例说明。
步骤S4，产生DL dummy IP包或在DL数据的IP头或TCP头上增加选项，在选项的数据区域包含请求信息，这里的请求信息(Request Information)是指网络信息获取请求相关的信息，例如可以包括(Target ID，Request Type，Request parameters)。
在这里又可以分为以下几种情况：
若(E)AS有待发送的DL数据，则(E)AS可以在下行的IP包头上加上option，或者，若该下行的IP包还是TCP包，则可以改为在TCP包头上加上Option。在IP option或者TCP option的data部分包含有Target ID(这里＝RAN)，Request Type和Request parameters。
若(E)AS没有待发送的下行的任何数据，则(E)AS可以产生一个DL dummy IP包(如ICMP ECHO，注意此时的ICMP ECHO中的DATA部分无任何特定的内容)或TCP空包。
另外，(E)AS也可以等到有下行的数据包后，再继续执行下述步骤。
步骤S5a，若图16步骤S4采用了在DL的IP头上增加Option来传输网络信息获取请求，则(E)AS可以向UE发送DL IP数据包，该DL IP数据包带Option选项，且在IP Option的data部分包括(Option-Type，Target ID，Request Type，Request parameters，MAC)。其中Option-Type可以采用上文中所例举的30/94/158/222或使用3GPP在IANA上申请的一个特定值。这里的Target ID(＝UE)。且这里假设上述步骤S3确定网络能力开放交互要进行加密与完整性保护。
步骤S5b，若IP包是TCP包，(E)AS决定采用TCP option来传输网络信息获取请求，即上述步骤S4采用了在DL的TCP头上增加Option来传输网络信息获取请求，则(E)AS可以向UE发送DL TCP数据包，该DL TCP数据包带Option选项，且在TCP Option的data部分包括(Option-kind，Target ID，Request Type，Request parameters，MAC)。其中Option-kind见上文中所例举中的253/254或使用3GPP在IANA上申请的一个特定值，且可以使用一个ExID(RFC 6994，下文与此相同)。TCP Option中的数据处理同步骤S5a。
步骤S6，UE接收到(E)AS发送的DL IP包或者DL TCP包之后，对该DL IP包或者DL TCP包进行如下检查：
第一，判断该DL IP包或者DL TCP包中是否有option存在，若有option，则检查Option-type(IPv4)或Option-kind(TCP)是否是规范所指定的。
第二，检查该DL IP包或者DL TCP包中的Target ID是否是UE。若是，则UE进行下述步骤，若不是，则UE不对其进行本申请实施例所指出的特定处理，将该DL IP包或者DL TCP包删除Option后继续往传递给上层。
第三，若进行了安全加密与完整性保护，则利用该DL IP包或者DL TCP包中的MAC进行安全验证。若通过了安全验证，则继续下述步骤；若未通过安全验证，则停止执行步骤步骤。
第四，根据该DL IP包或者DL TCP包中的Request Type，判断UE是否支持该Request Type。若UE支持Request Type，则继续后面的过程。否则，UE不作任何特殊的处理，后面的步骤不再执行。
需要说明的是，UE接收到的(E)AS发送的DL IP包或者DL TCP包，是经过UPF和RAN转发的，因此，UPF和RAN接收到后也会对该DL IP包或者DL TCP包进行检查，此时Target  ID指向的是UE，则UPF和RAN不对其进行任何特殊的处理。
步骤S7，UE删除DL IP或TCP包中的对应的option，然后将他们往传递给上层。
图16中，UE可以记录该DL IP包或者DL TCP包的IP五元组信息及IP头中的identification(标识)字段，后面UE提供网络信息给(E)AS时，需要记录的IP五元组信息及IP头中的identification字段。
步骤S8，若UE可以并且需要立即提供网络信息，UE判断提供的网络信息的大小。
步骤S8a，若UE判定网络信息长度(包含完整性处理后的MAC，后同)>第一长度(这里假设为38字节)，则UE产生一个ICMP ECHO包，例如产生ICMP回送包(ECHO包)且数据(Data)部分包含响应信息(Response Information)，还可以包括Target ID。
其中所生成的ICMP ECHO包的源地址(例如源IP地址)可以设置为上述步骤S7中记录的IP五元组信息中的目的地址(例如目的IP地址)，目的地址(例如目的IP地址)可以设置为上述步骤S7中记录的IP五元组信息的源地址(例如源IP地址)。
ICMP ECHO包中的Type/code＝8/0，identifier取一特定值，如上述步骤S7中记录的IP五元组信息中的UDP或TCP包的目的端口号。若上述步骤S7中记录的IP五元组信息既不是UDP也不是TCP包，则ICMP ECHO包的identifier可以取上述步骤S7中记录的IP五元组信息中的identification。对于ICMP ECHO包的sequence number，若UE没有使用过，则UE取一特定值，如产生一个随机值。
图16中，为了防止不同的IP流采用相同的随机值，UE可以以上述步骤S7中记录的IP五元组信息来产生一个随机值。然后UE向(E)AS发送包含其所获得的网络信息的响应信息。
图16中，若UE判定网络信息长度(包含完整性处理后的MAC，后同)>第二长度(这里假设为1472字节)，则UE需要传输剩下的网络信息，此时，ICMP ECHO包中的Type/Code，identifier可以与上述实施例保持一致，只是SN依次递增1，直到将获得的网络信息传输完成。
其中，UE可以在预定的时间内通过ECHO reply来判断哪些ICMP ECHO包被(E)AS正确地接收，若UE没有收到(E)AS返回的对应的ECHO reply，则可以重新发送之前的ICMP ECHO包，此时ICMP ECHO包还是与要重发的ECHO消息头保持相同。
步骤S8b，若UE判定网络信息长度(包含完整性处理后的MAC，后同)<＝38字节，则UE可以产生一个UL dummy IP包或者TCP空包，该UL dummy IP包或者TCP空包带选项，选项包含响应信息。
例如若为UL dummy IP包，则选项中可以包括(Option-Type，Target ID，Response Information)。其中，该UL dummy IP包的源IP地址可以设置为上述步骤S7记录的IP五元组信息中的目的IP地址，该UL dummy IP包的目的IP地址可以设置为上述步骤S7记录的IP五元组信息中的源IP地址。然后加上IP Option。Option-Type可以取上文中例举的30/94/158/222或使用3GPP在IANA上申请的一个特定值。然后设置Target ID(＝UE)表明是从UE回复的。Response Information包含RAN所提供的网络信息。若激活了加密与完整性保护，则Response Information还包含MAC。
另外，若网络信息长度<＝38字节，则UE也可以选择产生一个UL TCP空包，其中该UL TCP空包的源IP地址可以设置为上述步骤S7记录的IP五元组信息中的目的IP地址，该UL TCP空包的目的IP地址可以设置为上述步骤S7记录的IP五元组信息中的源IP地址。该UL TCP空包的目的端口可以设置为上述步骤S7记录的IP五元组信息中的TCP源端口，该UL TCP空包的源端口可以设置为上述步骤S7记录的IP五元组信息中的TCP目的端口，然后加上TCP Option，option-kind可以取上文中例举的253/254或使用3GPP在IANA上申请的一个特定值。且可以使用一个ExID。然后设置target ID(＝UE)表明是从UE回复的。Response information包含提供的网络信息。若激活了加密与完整性保护，则Response information还包含MAC。
图16中，若UE判定网络信息长度(包含完整性处理后的MAC，后同)<＝38字节，且UE决定等待后续的上行数据时携带该网络信息，则上述步骤S8不执行。
图16中，若UE不能立即提供网络信息，如UE需要与AMF进行交互，从AMF获取AMF或其它NF提供的网络信息，则UE可以发起与AMF的交互，则步骤S8和下面的步骤S10不执行。
步骤S9，UE收到UL的IP数据包。
步骤S10，当UE收到UL IP包时，则可以在该UL的IP包的option的数据data中包含(Option-Type，Target ID，Response Information)。即UE将要提供的网络信息加到上行IP包的IP option。或者，若该UL IP包同时还是UL TCP包，则可以在该上行TCP包的TCP option上加上RAN所要提供的网络信息，此时，传输的内容同上述步骤S8b。
需要注意的是，这里只是加上一个IP option，且要重新计算IP头中的checksum，其它信息均不改变；或者，只是加上一个TCP option，且要重新计算TCP头中的checksum，其它信息均不改变。
图16中，若加上option后，引起IP分片，则UE可以继续等待后续的上行IP/TCP包，一般而言大部分的上行的TCP包都只是TCP ACK包，加上option不会引起IP分片。若没有可用的上行IP/TCP包，UE在等待一定的时间后，若还没有合适的上行IP/TCP包用于加上option以传输网络信息，则可以使用上述步骤S8a的方法，产生一个ICMP包或使用步骤S8b的方法产生一个UL IP dummy包或TCP空包来传输网络信息。
图16中，若UE当前没有可以提供的网络信息(如还在等待AMF的响应)，则UE可以将上述步骤S9收到的上行数据不作任何的特殊处理(如继续上传给(E)AS)，此时上述步骤S10不执行。同样的，要注意的是，在下述步骤S11之前，UE收到的上述步骤S9的上行数据，可能有多个。在这种情形下，都是不作任何的特殊处理(如继续上传给(E)AS)。
步骤S11，UE与AMF交互，从其它NF获取网络信息。当UE收到了AMF自身或其它NF提供的网络信息时，继续执行下述步骤。
步骤S12a，若UE决定立即将得到的网络信息提供给(E)AS或网络信息长度>38字节，则可采用上述步骤S8a或步骤S8b所定义的方法，产生ICMP ECHO包或UL dummy包或TCP空包带选项，选项包含响应信息，例如选项中可以包括(Option-Type，Target ID，Response Information)，这里的Response Information包括UE从AMF自身或其它NF获取的网络信息。
步骤S12b，当UE确定将得到的网络信息通过上行的数据包携带给(E)AS时，则可以采用上述步骤S9和步骤S10的方法，即UE接收UL的IP数据包。然后，执行步骤S12c，使得该接收的UL的IP或TCP数据包带选项，选项的data中包含响应信息，例如可以包括(Option-Type，Target ID，Response Information)，这里的Response Information包括UE从AMF自身或其它NF获取的网络信息。
步骤S13，UE与(E)AS可以继续IP包的上下行传输。
本申请实施例中，若(E)AS在发送给UE的命令(下行数据包的网络信息获取请求)中，包含请求UE每隔一段时间(例如可以设定时间间隔)报告网络信息或当网络信息发生改变时，再次向(E)AS发送更新网络信息。则在时间未到达或网络信息状态没有改变时，UE与(E)AS的IP通信继续，此时，UE不作任何特定的处理。
其中，(E)AS发送给UE的下行数据包中的Request information中，(E)AS可以指定获取谁的网络信息(例如是UE还是AMF，或者其它NF)；还可以指定获取网络信息后，是UE直接返回给(E)AS还是经过处理后再发送给(E)AS；以及还可以指定是一次性返回，还是多次返回。Request information中包括的内容可以参照控制面中的相关内容。
步骤S14，在(E)AS要求的时间间隔到达或网络信息状态发生改变时，UE就需要再次上传更新网络信息，此时图16的步骤S15(产生ICMP回送包或UL Dummy IP包或TCP空包带选项，选项包含响应信息(Option-Type，Target ID，Response Information))，步骤S16(UE接收UL的IP数据包)，步骤S17(UL的IP或TCP数据包带选项，选项包含响应信息(Option-Type，Target ID，Response Information))的处理同图16的步骤S12a，步骤S12b与步骤S12c。
需要说明的是，图16的上述步骤S5a和S5b中，UPF和RAN也需要检查Target ID是否指向自己，当发现不是指向自己的时，则不作任何特殊的处理，继续发送给UE。图16的上述步骤S8b、S10、S12a、S12c、S15和S17中，UPF和RAN对上行IP包或TCP包中有Option-Type或者Option-kind的包(定义为获取网络信息或者网络能力开放的包)不作任何特殊的处理，继续发送给(E)AS。
另外，图16的上述步骤S9，S12(包括S12a、S12b和S12c)和S16中的UL IP包是指UE收到要发送给(E)AS的上行数据包。
图17示意性示出了根据本申请实施例的通过UE获取网络信息的流程示意图。图17给出了通过UE获取网络信息以提供给(E)AS的过程。
这里需要说明的是，在图17中，当UE自身可以提供(E)AS所需的网络信息时(例如，在UE之前与AMF，SMF，PCF，RAN进行交互时，UE已经有一些网络信息，这些网络信息例如可以包括UE与RAN之间的传输时延，UE的总传输速率等)，则这种情况下UE无需与AMF进行交互。若UE只需获取AMF上的网络信息提供给(E)AS时，则图17中的下述步骤S3(包括步骤S3a和S3b)，S4(包括步骤S4a和S4b)，S7都不会执行。
图17只是给出UE通过AMF向一个NF获取网络信息的实例。在实际的情形中，UE可能需要通过AMF向不同的NF获取网络信息，然后集中起来向(E)AS报告，即图17中的步骤S2-S5可执行多次，只是NF分别不同。
图17可以包括以下步骤。
步骤S1，这里以(E)AS通过UPF和RAN向UE发送下行IP数据包为例进行举例说明，该下行IP数据包带option(Option-Type，Target ID，Request Type，Request Parameters，MAC)。但本申请实施例并不限定于此，具体实现可以参照上述图16中的步骤S1-S10。
步骤S2-S5，对应于上述图16中的步骤S11。下面对其进行具体阐述。
步骤S2，UE向AMF发送NAS(Non-Access Stratum，非接入层)消息以发送网络数据请求，该NAS消息是请求AMF获取(E)AS当前所需的网络信息，此NAS消息可以包含(E)AS发送给UE的网络信息获取请求中的请求类型(即当前所请求的网络信息的类型，上述的Request Type)、请求参数(上述的Request Parameters)。即NAS:Network Data Request(Request Type,Request Parameters)，Request Parameters例如可以包括valid time(有效时间)，Times(次数)等。
因为此NAS消息是本申请实施例提出的新的消息名，因此，此NAS消息的消息名的名称及例如参数可以由3GPP标准来定义，但对应的功能是请求AMF来获取网络信息。
步骤S3a是对应于AMF向其它的NF(目标NF，即当前AMF向其请求获取网络信息的其它的NF)发送Nnf_网络数据获取请求，即Nnf_NetworkData Get Request(Request Type,Request Parameters)，即Nnf_NetworkData Get Request消息中包含当前所请求的网络信息的类型(请求类型)及请求参数。
步骤S4a是目标NF响应于AMF发送的Nnf_网络数据获取请求，返回给AMF的Nnf_网络数据获取响应，即Nnf_NetworkData Get Response(network data information)，network data information表示其它NF返回给AMF的网络信息。
例如，假设该目标NF为UDM，则AMF可以向UDM获取用户一些签约数据，并将部分签约数据提供给UE，然后再提供给(E)AS。
步骤S3a和步骤S4a中的Nnf_NetworkData Get Request/Nnf_NetworkData Get Response是一次性的交互过程，即(E)AS当前发送给UE的Request Parameters中并没有指定需要UE每隔一段时间向其返回网络信息，也没有指定需要UE在网络信息变化时，自动向其返回更新网络信息，例如可以通过上述valid time和/或Times(次数)等来指定。
步骤S3b，对应于AMF向目标NF发送Nnf_网络数据订阅请求消息，即Nnf_NetworkData Subscribe Request(Request Type,Request Parameters)。
步骤S4b，目标NF响应于AMF发送的Nnf_NetworkData Subscribe Request消息，向AMF返回Nnf_网络数据通知，即Nnf_NetworkData notify(network data information)。
在图17中的步骤S3b和步骤S4b中，会评阅当前的网络信息状态，当网络信息状态发生变化时，目标NF可以持续的给AMF提供更新网络信息。
Nnf_NetworkData Subscribe Request和Nnf_NetworkData notify中的参数的含义和处理类似于图17中的步骤S3a，步骤S4a。
当目标NF收到Nnf_NetworkData Subscribe Request消息时，会立即向AMF报告一个当前的网络信息状态。AMF可以向NWDAF请求相关的网络分析信息，可参见上述图3中所列出的10个网络信息，这个请求与响应消息及其名称与详细参数，参见3GPP协议TS23.288。
Nnf_NetworkData Subscribe Request和Nnf_NetworkData notify不是一次性的交互过程，在图17的下述步骤S7中，当目标NF发现网络信息发生改变时，会持续地向AMF报告更新网络信息，这个过程可以持续到AMF所设置的次数(Times)与/或时间(valid time)。
步骤S5，当AMF收到目标NF回复的网络信息时，通过NAS消息将网络信息传递给UE，即向UE发送NAS消息，该NAS消息包括网络数据响应，即NAS：Network Data Response(network data information)。
当图17中的步骤S2中的Network Data Request显示出需要持续获取网络信息时，AMF采用图17中的步骤S3b和步骤S4b的方式，而图17中的步骤S3a和步骤S4a一般可以用于取一些静态的数据或配置。
若网络信息数据可以直接由AMF来提供，则图17中的步骤S3和S4不执行。
图17中的步骤S6a，UE通过产生ICMP ECHO包的Data部分或UL dummy IP包带Option(Option-Type，Target ID，Response Information)或TCP空包带Option(Option-kind，Target ID，Response Information)，返回给(E)AS，Target ID(＝UE)，这里的Response Information包括network data information。
图17中的步骤S6b，UE也可以通过UL的IP数据包带Option(Option-Type，Target ID，Response Information)或TCP数据包带Option(Option-kind，Target ID，Response Information)，返回给(E)AS，Target ID(＝UE)，这里的Response Information包括network data information。
图17中的步骤S6a和S6b的具体实现可以参照上述图16中的步骤S12a，S12b，S12c。
图17中的步骤S7-S9，参照上述图16中的步骤S14。下面对图17的步骤S7-S9进行说明。
步骤S7，当目标NF检测到网络信息发生改变时，通过向AMF发送Nnf_网络数据通知将新的网络信息数据即更新网络信息提供给AMF，即发送Nnf_NetworkData Notify(network data information)，此处的network data information是指更新网络信息。(很多的例子可参见3GPP协议TS23.288)。
若网络信息数据直接由AMF来提供时，则图17中的步骤S7不执行。
步骤S8，AMF收到新的网络信息数据时，通过一个NAS消息传递发送给UE，即AMF向UE发送NAS消息，该NAS消息包括网络数据响应，即NAS：Network Data Response(network data information)，此处的network data information是指更新网络信息。
此时，若UE处于CM-IDLE(connection management-IDLE，连接管理-空闲，当UE处于CM-IDLE态时，没有该终端的N2和N3连接)状态，AMF可能要发起Network triggered service request(网络触发服务请求)过程(见3GPP协议TS23.502的章节4.2.3.3)，当UE与AMF建立起信令连接后，AMF再执行步骤S8。
步骤Step9，UE确认收到网络信息，即UE收到AMF发送的网络信息或者更新网络信息后，向AMF发送一个NAS消息：网络数据告知，以通知AMF其已经收到了AMF所发送的网络信息，例如NAS:Network Data Notify acknowledge。
需要说明的是，当AMF发送给UE的网络信息数据较大时，不能在步骤S8中一次性传递给UE时，则图17中的步骤S8与S9可以执行多次(类似的处理见3GPP协议TS23.502的章节4.2.4.3)。
类似地，当AMF发送给UE的网络信息数据较大时，不能在图17中的步骤S5中一次性传递给UE时，则可以采用类似于图17中的步骤S8与S9的信令交互方式，将余下的网络信 息数据传送给UE。
图17中的步骤S10a和S10b，参照上述图16中的步骤15-S17。
图18示意性示出了根据本申请实施例的实现网络能力开放的方法的流程图。图18的方法可以由目标用户面节点执行，例如UE/RAN/UPF中的任意一者。如图18所示，本申请实施例提供的方法可以包括以下步骤。
在步骤S181中，接收应用服务器发送的下行数据包，其中，下行数据包中包括网络信息获取请求。
在一些实施例中，方法还可以包括：记录下行数据包的网际互联协议五元组信息及其网际互联协议帧首的标识字段。
在步骤S182中，响应于网络信息获取请求，生成响应信息，其中，响应信息中包括网络信息获取请求所请求的网络信息。
在步骤S183中，将响应信息发送至应用服务器。
图19示出了图18中所示的步骤S182在一实施例中的处理过程示意图。如图19所示，本申请实施例中上述步骤S182可以进一步包括以下步骤。
在步骤S1821中，根据网络信息获取请求获取所请求的网络信息。
在一些实施例中，根据网络信息获取请求获取所请求的网络信息，包括：将网络信息获取请求发送至第一目标非用户面节点；接收第一目标非用户面节点响应于网络信息获取请求返回的第一目标非用户面节点的网络信息。
图19中的第一目标非用户面节点例如可以是AMF或SMF，其中，当目标用户面节点为UE或者RAN时，该第一目标非用户面节点可以为AMF，当目标用户面节点为UPF时，该第一目标非用户面节点可以为SMF。即用户面节点UE或者RAN，获取AMF自身提供网络信息，此时AMF不需要与其它NF进行交互获取网络信息。还存在一种情况，目标用户面节点可以获取自身提供的网络信息，此时UE/RAN不需要和AMF交互获取网络信息，UPF不需要和SMF交互获取网络信息。
在一些实施例中，根据网络信息获取请求获取所请求的网络信息，包括：将网络信息获取请求发送至第一目标非用户面节点，以便于第一目标非用户面节点将网络信息获取请求发送至第二目标非用户面节点，并接收第二目标非用户面节点响应于网络信息请求返回的第二目标非用户面节点的网络信息；接收第一目标非用户面节点返回的第二目标非用户面节点的网络信息。
图19中，第二目标非用户面节点可以是除了AMF和SMF以外的其他非用户面节点，例如控制面节点，也可以为上述实施例中的目标NF。即AMF可以与目标NF交互获取网络信息，或者SMF可以与目标NF交互获取网络信息，然后再提供给UE，RAN或者UPF。
在一些实施例中，根据网络信息获取请求获取所请求的网络信息，还可以包括：接收第一目标非用户面节点返回的第二目标非用户面节点的更新网络信息；其中，第二目标非用户面节点的更新网络信息是第二目标非用户面节点的网络信息发生变化或者达到预定时间间隔时，第二目标非用户面节点发送给第一目标非用户面节点的。
当(E)AS请求目标用户面节点每隔一定时间或者在网络信息发生变化时，自动向(E)AS返回变化后的网络信息(即更新网络信息)，则在到达所设定的时间间隔后，或者在网络信息发生变化时，目标NF会自动向AMF或者SMF发送更新网络信息，以便于目标用户面节点提供给(E)AS。
在步骤S1822中，若网络信息的长度大于第一长度，则生成至少一个互联网控制消息协议回送请求包，其中，第一长度相关于网际互联协议选项的数据区域的长度。
在一些实施例中，方法还可以包括：设置至少一个互联网控制消息协议回送请求包的源地址和目的地址分别为下行数据包的网际互联协议五元组信息中的目的地址和源地址；若下行数据包的网际互联协议五元组信息中包括用户数据报协议或者传输控制协议的目的端口号，则设置至少一个互联网控制消息协议回送请求包的标识器为下行数据包的网际互联协议五元组信息中的用户数据报协议或者传输控制协议的目的端口号；若下行数据包的网际互联协议五元组信 息中不包括用户数据报协议或者传输控制协议的目的端口号，则设置至少一个互联网控制消息协议回送请求包的标识器为网际互联协议帧首的标识字段。
在一些实施例中，若网络信息的长度大于第二长度，则至少一个互联网控制消息协议回送请求包包括多个互联网控制消息协议回送请求包，且多个互联网控制消息协议回送请求包的序列号从随机值开始依次递增；其中，第二长度相关于互联网控制消息协议回送请求包的数据区域的长度，第二长度大于第一长度。
在一些实施例中，方法还可以包括：根据下行数据包的网际互联协议五元组信息生成随机值。
在步骤S1823中，在至少一个互联网控制消息协议回送请求包的数据区域写入网络信息，以用于生成响应信息。
图20示出了图18中所示的步骤S182在一实施例中的处理过程示意图。如图20所示，本申请实施例中上述步骤S182可以进一步包括以下步骤。
在步骤S1824中，根据网络信息获取请求获取所请求的网络信息。
在一些实施例中，根据网络信息获取请求获取所请求的网络信息，包括：将网络信息获取请求发送至第一目标非用户面节点；接收第一目标非用户面节点响应于网络信息获取请求返回的第一目标非用户面节点的网络信息。
在一些实施例中，根据网络信息获取请求获取所请求的网络信息，包括：将网络信息获取请求发送至第一目标非用户面节点，以便于第一目标非用户面节点将网络信息获取请求发送至第二目标非用户面节点，并接收第二目标非用户面节点响应于网络信息请求返回的第二目标非用户面节点的网络信息；接收第一目标非用户面节点返回的第二目标非用户面节点的网络信息。
在一些实施例中，根据网络信息获取请求获取所请求的网络信息，还可以包括：接收第一目标非用户面节点返回的第二目标非用户面节点的更新网络信息；其中，第二目标非用户面节点的更新网络信息是第二目标非用户面节点的网络信息发生变化或者达到预定时间间隔时，第二目标非用户面节点发送给第一目标非用户面节点的。
在步骤S1825中，若网络信息的长度小于等于第一长度，则生成上行模拟数据包，上行模拟数据包包括网际协议帧首，其中，上行模拟数据包的源地址和目的地址分别设置为下行数据包的目的地址和源地址。
在步骤S1826中，在上行模拟数据包的网际协议帧首上增加网际协议选项。
在步骤S1827中，在上行模拟数据包的网际协议选项的数据区域写入网络信息，以用于生成响应信息。
图21示出了图18中所示的步骤S182在一实施例中的处理过程示意图。如图21所示，本申请实施例中上述步骤S182可以进一步包括以下步骤。
在步骤S1828中，根据网络信息获取请求获取所请求的网络信息。
在一些实施例中，根据网络信息获取请求获取所请求的网络信息，包括：将网络信息获取请求发送至第一目标非用户面节点；接收第一目标非用户面节点响应于网络信息获取请求返回的第一目标非用户面节点的网络信息。
在一些实施例中，根据网络信息获取请求获取所请求的网络信息，包括：将网络信息获取请求发送至第一目标非用户面节点，以便于第一目标非用户面节点将网络信息获取请求发送至第二目标非用户面节点，并接收第二目标非用户面节点响应于网络信息请求返回的第二目标非用户面节点的网络信息；接收第一目标非用户面节点返回的第二目标非用户面节点的网络信息。
在一些实施例中，根据网络信息获取请求获取所请求的网络信息，还可以包括：接收第一目标非用户面节点返回的第二目标非用户面节点的更新网络信息；其中，第二目标非用户面节点的更新网络信息是第二目标非用户面节点的网络信息发生变化或者达到预定时间间隔时，第二目标非用户面节点发送给第一目标非用户面节点的。
在步骤S1829中，若网络信息的长度小于等于第一长度，则生成上行传输控制协议空包，其中，上行传输控制协议空包的源地址和目的地址分别设置为下行数据包的目标地址和源地址， 上行传输控制协议空包的源端口号和目的端口号分别设置为下行数据包的网际互联协议五元组信息中的传输控制协议目的端口号和传输控制协议源端口号。
在步骤S18210中，在上行传输控制协议空包的数据区域写入网络信息，以用于生成响应信息。
图22示出了图18中所示的步骤S182在一实施例中的处理过程示意图。如图22所示，本申请实施例中上述步骤S182可以进一步包括以下步骤。
在步骤S18211中，根据网络信息获取请求获取所请求的网络信息。
在一些实施例中，根据网络信息获取请求获取所请求的网络信息，包括：将网络信息获取请求发送至第一目标非用户面节点；接收第一目标非用户面节点响应于网络信息获取请求返回的第一目标非用户面节点的网络信息。
在一些实施例中，根据网络信息获取请求获取所请求的网络信息，包括：将网络信息获取请求发送至第一目标非用户面节点，以便于第一目标非用户面节点将网络信息获取请求发送至第二目标非用户面节点，并接收第二目标非用户面节点响应于网络信息请求返回的第二目标非用户面节点的网络信息；接收第一目标非用户面节点返回的第二目标非用户面节点的网络信息。
在一些实施例中，根据网络信息获取请求获取所请求的网络信息，还可以包括：接收第一目标非用户面节点返回的第二目标非用户面节点的更新网络信息；其中，第二目标非用户面节点的更新网络信息是第二目标非用户面节点的网络信息发生变化或者达到预定时间间隔时，第二目标非用户面节点发送给第一目标非用户面节点的。
在步骤S18212中，若网络信息的长度小于等于第一长度，且接收到上行网际协议数据包，则将网络信息写入上行网际协议数据包的网际协议选项的数据区域，以用于生成响应信息。
图23示出了图18中所示的步骤S182在一实施例中的处理过程示意图。如图23所示，本申请实施例中上述步骤S182可以进一步包括以下步骤。
在步骤S18213中，根据网络信息获取请求获取所请求的网络信息。
在一些实施例中，根据网络信息获取请求获取所请求的网络信息，包括：将网络信息获取请求发送至第一目标非用户面节点；接收第一目标非用户面节点响应于网络信息获取请求返回的第一目标非用户面节点的网络信息。
在一些实施例中，根据网络信息获取请求获取所请求的网络信息，包括：将网络信息获取请求发送至第一目标非用户面节点，以便于第一目标非用户面节点将网络信息获取请求发送至第二目标非用户面节点，并接收第二目标非用户面节点响应于网络信息请求返回的第二目标非用户面节点的网络信息；接收第一目标非用户面节点返回的第二目标非用户面节点的网络信息。
在一些实施例中，根据网络信息获取请求获取所请求的网络信息，还可以包括：接收第一目标非用户面节点返回的第二目标非用户面节点的更新网络信息；其中，第二目标非用户面节点的更新网络信息是第二目标非用户面节点的网络信息发生变化或者达到预定时间间隔时，第二目标非用户面节点发送给第一目标非用户面节点的。
在步骤S18214中，若网络信息的长度小于等于第一长度，且接收到上行传输控制协议数据包，则将网络信息写入上行传输控制协议数据包的传输控制协议选项的数据区域，以用于生成响应信息。
上述图18-23的具体实现可以参照上述图7-17的内容。
需要说明的是，IP Option的最大长度为40字节，EAS或AS用于向目标用户面节点发送控制命令一般是足够了。若是UE/RAN/UPF向EAS或AS提供网络信息时，40字节的长度可能不足，这时，在IP Option的数据中的前一个或两个字节定义为数据的当前位置，将提供的网络信息数据分割到多个IP Options包中(这样，一个IP Option实际上最多只能传输36/37/38个字节，即(40-1(Option-type)-1(Option-length)-0/1/2(Network Data Pointer)＝38/37/36)。另外，由于IP协议不能保证IP包的到达次序与发送次序一致，因此，接收方可以通过Network Data Pointer来实现数据的重组。但若中间的一个IP包丢失，则可能整个Network Data不能重组成功，在这种情形下，EAS或AS就需要重新发送网络信息获取请求命令。
当EAS或AS向UE/RAN/UPF发送控制命令或UE/RAN/UPF向EAS/AS发送响应信息时，此时若没有可以发送的下行数据或上行数据，一直等到有下行数据或上行数据为止。但这种方法对较长的上行Network Data而言，仍然会出现需要多次传输的问题。
类似于IP Header，TCP Option的最大长度为40字节，EAS或AS用于向目标用户面节点发送控制命令一般是足够了。若是UE/RAN/UPF向EAS或AS提供网络信息时，40字节的长度可能不足。这时，在TCP Option的数据中的前一个或两个字节定义为数据的当前位置，将提供的网络信息数据分割到多个TCP Options包中(这样，一个TCP Option实际上最多只能传输36或37个字节(40-1(Option-type)-1(Option-length)-1/2(network data Pointer)＝37/36)。另外，由于TCP协议能实现TCP包的按顺序重组，因此也就可以间接地保证了接收方顺序地接收到网络能力开放数据(包括传输过程中TCP包的丢失，这是比IP Option好的方面)。但是这只是基于在每个现有的TCP包上增加一个Option。当网络能力开放的数据较长时，可能需要很多的TCP包，并且有可能持续较长的时间。
另外，可利用多次发送一个ACK的TCP空包，且在每个TCP空包中传输一部分网络能力开放的数据，这样不会造成TCP连接的任何问题，但有些TCP协议栈将重复的TCP空包(即TCP包的ACK Number)不变到达三次后，就开始降低向对方发送的传输速率(即UE/RAN/UPF通过TCP的空ACK包连续地向EAS或AS发送网络能力开放的数据时)，EAS/AS会降低向UE发送TCP实际数据包的速率，从而给用户的体验造成影响。
当EAS或AS向UE/RAN/UPF发送控制命令或UE/RAN/UPF向EAS/AS发送响应信息时，此时若没有可以发送的下行数据或上行数据，一直等到有下行数据或上行数据为止。但可能在较长的时间内仍没有上行或下行数据，此时，产生Dummy IP包，并利用此Dummy IP的Option来传输网络信息相关的数据。为此，假设Dummy IP包实际上为一个ICMP ECHO包，采用(多次)发送ICMP的ECHO，并且每次发送的ECHO中的identifier设置为UDP或TCP的一个端口号，SN设置为一个递增的序列号。当UE/RAN/UPF收到对应的ECHO Reply后，比较收到的ECHO Reply的SN与identifier与ECHO的SN与identifier是否相同，若相同，表明EAS/AS收到了这个ICMP消息，这样，Dummy IP头上的Option数据就收到。在预定的时间内UE/RAN/UPF未收到ECHO Reply，则再次重发这个ECHO并在IP头中包含对应的Option数据。
但是上面的方法仍然是低效率的，因为每次IP Option只能传输38字节的内容。由于ICMP的ECHO可以包含1472个字节的数据，因此，本申请实施例提出将Network Data数据作为ECHO中的Data部分发送出来，此时的传送效率则远大于每次只传输38字节的Option的方法，同时应用ID+SN，及SN每次加1的方法来实现多次的ECHO传输：在一定的时间内未收到ECHO Reply(通过对比ID+SN来确认是否收到)，则再次重发这个ECHO(在重发时，ID+SN值是重发的ECHO包的ID+SN值)，从而实现了网络信息数据的可靠与按序传输。因为每次新的ECHO包的SN都加1，所以接收方可以根据SN号进行接收数据的排序。
总之，当网络信息的长度(注意，还要包含完整性保护处理后的MAC)不超过38字节时，则选用IP Option与TCP Option的方法。当网络信息的数据长度超过38字节小于1472字节时，则运行一次ICMP ECHO与Reply方法。当网络信息的数据长度超过1472字节时，则可通过多次运行递增SN号的ICMP Request与Reply的方法，实现网络信息数据的可靠与按序传输。
本申请实施例中所提供的方法，是利用用户面实现网络能力开放。目前互联网应用及各种应用基本上都是使用IP与TCP协议。因此，利用IP或TCP协议头上的option扩展头来传输网络能力开放的请求与响应，签约与报告数据。例如，充分利用TCP的ACK空包或产生一个IP dummy包来发送option扩展头，从而可以避免由于引入option头导致的IP数据包长度增加而引起的分片。
例如，充分利用实际数据传输过程中，上行数据包的长度较小而下行数据包的长度较长的特点，来实现更多地上传网络能力开放数据给EAS或AS。其中，UE发出的包叫上行数据包，一般情况下上行数据包比下行数据包要少，且上行数据包中大部分是ACK空包，只有少 部分携带实际数据，例如UE用户请求EAS或AS某部电影资源，EAS或AS需要下发下行数据包1GB，则对应的上行数据包假设为20万个，其中只有1000个是带实际数据的，其它的均为ACK包，这时，在利用UL数据包的option部分来传输网络信息时，若碰到某个UL数据包带有实际数据，则跳过这个UL数据包即可，网络信息的传输整体上不会受到影响。此外，由于下行数据包一般本身较长，且下行数据包是EAS或AS发送给UE的，若加了option数据后占据了下行数据包的部分字节，EAS或AS可以自动将其多打包几个下行数据包，但UPF或者RAN收到EAS或AS下发的下行数据包后，只能在外面封装少量的数据，不能丢失EAS或AS本身下发的下行数据包，也不能重新决定分成几个包来发送给UE。
本申请实施方式提出的实现网络能力开放的方法，一方面，利用用户面实现网络能力开放的功能，实时性强，传输的网络数据量大，且不会引起大量的网络信令；另一方面，网络能力开放是基于IP、TCP及ICMP来实现的，这都是目前所有的应用与网络都支持的基本协议，特别是利用ICMP可实现可靠有序的大的网络信息数据的传输。同时，网络能力开放无需EAS或AS与网络之间有专用的控制面接口(AF与NEF及(E)AS与AF之间的接口)，天然地利用通信时的IP传输通路来实现网络能力开放数据(网络信息)的交互与传输。本申请实施例提供的方法是一种in-band的技术，减少了out-of-band能力开放时，网络能力开放数据即网络信息如何与(E)AS，特别是与UE关联起来的困难与挑战。
本申请实施方式提出的实现网络能力开放的方法，可应用于MEC，也可以应用2G，3G，4G，5G网络，并提出了多种实现方式：IP，TCP，ICMP，对于每种方式给出了如何选择的方法。提供了通过UE，RAN，UPF来实现网络能力开放的方式，以支持不同情形下的网络能力开放。
图24示意性示出了根据本申请实施例的实现网络能力开放的装置的框图。如图24所示，本申请实施方式提供的实现网络能力开放的装置2400包括：下行数据获取单元2410、下行数据发送单元2420以及响应信息接收单元2430。
其中，下行数据获取单元2410配置为获取下行数据包，其中，下行数据包中包括网络信息获取请求。下行数据发送单元2420配置为将下行数据包发送至目标用户面节点。响应信息接收单元2430配置为接收目标用户面节点返回的响应于网络信息获取请求的响应信息，其中，响应信息中包括网络信息获取请求所请求的网络信息。
在一些实施例中，下行数据获取单元2410包括：第一待发送下行数据获取单元，配置为获取第一待发送下行数据，其中，第一待发送下行数据包括网际互联协议帧首；第一网际互联协议选项增加单元，配置为在第一待发送下行数据的网际互联协议帧首上增加网际互联协议选项；第一网际互联协议数据写入单元，配置为在第一待发送下行数据的网际互联协议选项的数据区域写入网络信息获取请求，以用于生成下行数据包。
在一些实施例中，下行数据获取单元2410包括：第二待发送下行数据获取单元，配置为获取第二待发送下行数据，第二待发送下行数据包括传输控制协议帧首；第二传输控制协议选项增加单元，配置为在第二待发送下行数据的传输控制协议帧首上增加传输控制协议选项；第二传输控制协议数据写入单元，配置为在第二待发送下行数据的传输控制协议选项的数据区域写入网络信息获取请求，以用于生成下行数据包。
在一些实施例中，下行数据获取单元2410包括：下行模拟数据包生成单元，配置为生成下行模拟数据包，下行模拟数据包包括网际协议帧首；下行模拟数据包网际协议选项增加单元，配置为在下行模拟数据包的网际协议帧首上增加网际协议选项；下行模拟数据包选项数据写入单元，配置为在下行模拟数据包的网际协议选项的数据区域写入网络信息获取请求，以用于生成下行数据包。
在一些实施例中，目标用户面节点可以包括用户面网关、基站和终端中的任意一种。
在一些实施例中，当目标用户节点为终端，且终端使用互联网控制消息协议回送请求包的数据区域返回响应信息时，实现网络能力开放的装置2400还包括：目标用户面节点切换单元，配置为当检测到终端返回的响应信息中的网络信息的长度超过预设阈值时，则切换到使用用户 面网关或者基站来返回网络信息获取请求所请求的网络信息。
图25示意性示出了根据本申请实施例的实现网络能力开放的装置的框图。如图25所示，本申请实施方式提供的实现网络能力开放的装置2500包括：下行数据接收单元2510、响应信息生成单元2520以及响应信息发送单元2530。
其中，下行数据接收单元2510配置为接收应用服务器发送的下行数据包，其中，下行数据包中包括网络信息获取请求。响应信息生成单元2520配置为响应于网络信息获取请求，生成响应信息，其中，响应信息中包括网络信息获取请求所请求的网络信息。响应信息发送单元2530配置为将响应信息发送至应用服务器。
在一些实施例中，实现网络能力开放的装置2500还包括：五元组信息记录单元，配置为记录下行数据包的网际互联协议五元组信息及其网际互联协议帧首的标识字段。
在一些实施例中，响应信息生成单元2520包括：网络信息获取单元，配置为根据网络信息获取请求获取所请求的网络信息；互联网控制消息协议回送请求包生成单元，配置为当网络信息的长度大于第一长度时，则生成至少一个互联网控制消息协议回送请求包，其中，第一长度相关于网际互联协议选项的数据区域的长度；互联网控制消息协议回送请求包数据写入单元，配置为在至少一个互联网控制消息协议回送请求包的数据区域写入网络信息，以用于生成响应信息。
在一些实施例中，实现网络能力开放的装置2500包括：互联网控制消息协议回送请求包地址设置单元，配置为设置至少一个互联网控制消息协议回送请求包的源地址和目的地址分别为下行数据包的网际互联协议五元组信息中的目的地址和源地址；第一标识器设置单元，配置为当下行数据包的网际互联协议五元组信息中包括用户数据报协议或者传输控制协议的目的端口号时，则设置至少一个互联网控制消息协议回送请求包的标识器为下行数据包的网际互联协议五元组信息中的用户数据报协议或者传输控制协议的目的端口号；第二标识器设置单元，配置为当下行数据包的网际互联协议五元组信息中不包括用户数据报协议或者传输控制协议的目的端口号时，则设置至少一个互联网控制消息协议回送请求包的标识器为网际互联协议帧首的标识字段。
在一些实施例中，当网络信息的长度大于第二长度时，则至少一个互联网控制消息协议回送请求包包括多个互联网控制消息协议回送请求包，且多个互联网控制消息协议回送请求包的序列号从随机值开始依次递增。其中，第二长度相关于互联网控制消息协议回送请求包的数据区域的长度，第二长度大于第一长度。
在一些实施例中，实现网络能力开放的装置2500包括：随机值生成单元，配置为根据下行数据包的网际互联协议五元组信息生成随机值。
在一些实施例中，响应信息生成单元2520包括：网络信息获取单元，配置为根据网络信息获取请求获取所请求的网络信息；上行模拟数据包生成单元，配置为当网络信息的长度小于等于第一长度时，则生成上行模拟数据包，上行模拟数据包包括网际协议帧首，其中，上行模拟数据包的源地址和目的地址分别设置为下行数据包的目的地址和源地址；上行模拟数据包网际协议选项增加单元，配置为在上行模拟数据包的网际协议帧首上增加网际协议选项；上行模拟数据包网际协议选项数据写入单元，配置为在上行模拟数据包的网际协议选项的数据区域写入网络信息，以用于生成响应信息。
在一些实施例中，响应信息生成单元2520包括：网络信息获取单元，配置为根据网络信息获取请求获取所请求的网络信息；上行传输控制协议空包生成单元，配置为当网络信息的长度小于等于第一长度时，则生成上行传输控制协议空包，其中，上行传输控制协议空包的源地址和目的地址分别设置为下行数据包的目标地址和源地址，上行传输控制协议空包的源端口号和目的端口号分别设置为下行数据包的网际互联协议五元组信息中的传输控制协议目的端口号和传输控制协议源端口号；上行传输控制协议空包数据写入单元，配置为在上行传输控制协议空包的数据区域写入网络信息，以用于生成响应信息。
在一些实施例中，响应信息生成单元2520包括：网络信息获取单元，配置为根据网络信息 获取请求获取所请求的网络信息；上行网际协议数据包选项数据写入单元，配置为当网络信息的长度小于等于第一长度，且接收到上行网际协议数据包时，则将网络信息写入上行网际协议数据包的网际协议选项的数据区域，以用于生成响应信息。
在一些实施例中，响应信息生成单元2520包括：网络信息获取单元，配置为根据网络信息获取请求获取所请求的网络信息；上行传输控制协议数据包选项数据写入单元，配置为当网络信息的长度小于等于第一长度，且接收到上行传输控制协议数据包时，则将网络信息写入上行传输控制协议数据包的传输控制协议选项的数据区域，以用于生成响应信息。
在一些实施例中，网络信息获取单元包括：第一网络信息获取请求转发单元，配置为将网络信息获取请求发送至第一目标非用户面节点；第一网络信息响应接收单元，配置为接收第一目标非用户面节点响应于网络信息获取请求返回的第一目标非用户面节点的网络信息。
在一些实施例中，网络信息获取单元包括：第二网络信息获取请求转发单元，配置为将网络信息获取请求发送至第一目标非用户面节点，以便于第一目标非用户面节点将网络信息获取请求发送至第二目标非用户面节点，并接收第二目标非用户面节点响应于网络信息请求返回的第二目标非用户面节点的网络信息；第二网络信息响应接收单元，配置为接收第一目标非用户面节点返回的第二目标非用户面节点的网络信息。
在一些实施例中，网络信息获取单元包括：更新网络信息接收单元，配置为接收第一目标非用户面节点返回的第二目标非用户面节点的更新网络信息。其中，第二目标非用户面节点的更新网络信息是第二目标非用户面节点的网络信息发生变化或者达到预定时间间隔时，第二目标非用户面节点发送给第一目标非用户面节点的。
本申请实施例提供的实现网络能力开放的装置中的各个单元的具体实现可以参照上述实现网络能力开放的方法中的内容，在此不再赘述。
应当注意，尽管在上文详细描述中提及了用于动作执行的设备的若干单元，但是这种划分并非强制性的。实际上，根据本申请的实施方式，上文描述的两个或更多单元的特征和功能可以在一个单元中具体化。反之，上文描述的一个单元的特征和功能可以进一步划分为由多个单元来具体化。
通过以上的实施方式的描述，本领域的技术人员易于理解，这里描述的示例实施方式可以通过软件实现，也可以通过软件结合必要的硬件的方式来实现。因此，根据本申请实施方式的技术方案可以以软件产品的形式体现出来，该软件产品可以存储在一个非易失性存储介质(可以是CD-ROM，U盘，移动硬盘等)中或网络上，包括若干指令以使得一台计算设备(可以是个人计算机、服务器、触控终端、或者网络设备等)执行根据本申请实施方式的方法。

Claims (23)

  1. 一种实现网络能力开放的方法，包括：
    获取下行数据包，其中，所述下行数据包中包括网络信息获取请求；
    将所述下行数据包发送至目标用户面节点；
    接收所述目标用户面节点返回的响应于所述网络信息获取请求的响应信息，其中，所述响应信息中包括所述网络信息获取请求所请求的网络信息。
  2. 根据权利要求1所述的实现网络能力开放的方法，其中，所述获取下行数据包，包括：
    获取第一待发送下行数据，其中，所述第一待发送下行数据包括网际互联协议帧首；
    在所述第一待发送下行数据的网际互联协议帧首上增加网际互联协议选项；
    在所述第一待发送下行数据的网际互联协议选项的数据区域写入所述网络信息获取请求，以用于生成所述下行数据包。
  3. 根据权利要求1所述的实现网络能力开放的方法，其中，所述获取下行数据包，包括：
    获取第二待发送下行数据，其中，所述第二待发送下行数据包括传输控制协议帧首；
    在所述第二待发送下行数据的传输控制协议帧首上增加传输控制协议选项；
    在所述第二待发送下行数据的传输控制协议选项的数据区域写入所述网络信息获取请求，以用于生成所述下行数据包。
  4. 根据权利要求1所述的实现网络能力开放的方法，其中，所述获取下行数据包，包括：
    生成下行模拟数据包，其中，所述下行模拟数据包包括网际协议帧首；
    在所述下行模拟数据包的网际协议帧首上增加网际协议选项；
    在所述下行模拟数据包的网际协议选项的数据区域写入所述网络信息获取请求，以用于生成所述下行数据包。
  5. 根据权利要求1所述的实现网络能力开放的方法，其中，所述目标用户面节点包括用户面网关、基站和终端中的任意一种。
  6. 根据权利要求1所述的实现网络能力开放的方法，其中，当所述目标用户节点为终端，且所述终端使用互联网控制消息协议回送请求包的数据区域返回所述响应信息时，所述方法还包括：
    当检测到所述终端返回的响应信息中的网络信息的长度超过预设阈值时，则切换到使用用户面网关或者基站来返回所述网络信息获取请求所请求的网络信息。
  7. 一种实现网络能力开放的方法，所述方法由电子设备执行，包括：
    接收应用服务器发送的下行数据包，其中，所述下行数据包中包括网络信息获取请求；
    响应于所述网络信息获取请求，生成响应信息，其中，所述响应信息中包括所述网络信息获取请求所请求的网络信息；
    将所述响应信息发送至所述应用服务器。
  8. 根据权利要求7所述的实现网络能力开放的方法，其中，所述方法还包括：
    记录所述下行数据包的网际互联协议五元组信息及其网际互联协议帧首的标识字段。
  9. 根据权利要求8所述的实现网络能力开放的方法，其中，所述响应于所述网络信息获取请求，生成响应信息，包括：
    根据所述网络信息获取请求获取所请求的网络信息；
    当所述网络信息的长度小于等于第一长度时，则生成上行模拟数据包，其中，所述上行模拟数据包包括网际协议帧首，所述上行模拟数据包的源地址和目的地址分别设置为所述下行数据包的目的地址和源地址；
    在所述上行模拟数据包的网际协议帧首上增加网际协议选项；
    在所述上行模拟数据包的网际协议选项的数据区域写入所述网络信息，以用于生成所述响应信息。
  10. 根据权利要求8所述的实现网络能力开放的方法，其中，所述响应于所述网络信息获取请求，生成响应信息，包括：
    根据所述网络信息获取请求获取所请求的网络信息；
    当所述网络信息的长度小于等于第一长度时，则生成上行传输控制协议空包，其中，所述上行传输控制协议空包的源地址和目的地址分别设置为所述下行数据包的目标地址和源地址，所述上行传输控制协议空包的源端口号和目的端口号分别设置为下行数据包的网际互联协议五元组信息中的传输控制协议目的端口号和传输控制协议源端口号；
    在所述上行传输控制协议空包的数据区域写入所述网络信息，以用于生成所述响应信息。
  11. 根据权利要求8所述的实现网络能力开放的方法，其中，所述响应于所述网络信息获取请求，生成响应信息，包括：
    根据所述网络信息获取请求获取所请求的网络信息；
    当所述网络信息的长度小于等于第一长度，且接收到上行网际协议数据包时，则将所述网络信息写入所述上行网际协议数据包的网际协议选项的数据区域，以用于生成所述响应信息。
  12. 根据权利要求8所述的实现网络能力开放的方法，其中，响应于所述网络信息获取请求，生成响应信息，包括：
    根据所述网络信息获取请求获取所请求的网络信息；
    当所述网络信息的长度小于等于第一长度，且接收到上行传输控制协议数据包时，则将所述网络信息写入所述上行传输控制协议数据包的传输控制协议选项的数据区域，以用于生成所述响应信息。
  13. 根据权利要求8所述的实现网络能力开放的方法，其中，所述响应于所述网络信息获取请求，生成响应信息，包括：
    根据所述网络信息获取请求获取所请求的网络信息；
    当所述网络信息的长度大于第一长度时，则生成至少一个互联网控制消息协议回送请求包，其中，所述第一长度相关于网际互联协议选项的数据区域的长度；
    在所述至少一个互联网控制消息协议回送请求包的数据区域写入所述网络信息，以用于生成所述响应信息。
  14. 根据权利要求13所述的实现网络能力开放的方法，其中，所述方法还包括：
    设置所述至少一个互联网控制消息协议回送请求包的源地址和目的地址分别为所述下行数据包的网际互联协议五元组信息中的目的地址和源地址；
    当所述下行数据包的网际互联协议五元组信息中包括用户数据报协议或者传输控制协议的目的端口号时，则设置所述至少一个互联网控制消息协议回送请求包的标识器为所述下行数据包的网际互联协议五元组信息中的用户数据报协议或者传输控制协议的目的端口号；
    当所述下行数据包的网际互联协议五元组信息中不包括用户数据报协议或者传输控制协议的目的端口号时，则设置所述至少一个互联网控制消息协议回送请求包的标识器为所述网际互联协议帧首的标识字段。
  15. 根据权利要求13所述的实现网络能力开放的方法，其中，当所述网络信息的长度大于第二长度，则所述至少一个互联网控制消息协议回送请求包包括多个互联网控制消息协议回送请求包，且所述多个互联网控制消息协议回送请求包的序列号从随机值开始依次递增；
    其中，所述第二长度相关于互联网控制消息协议回送请求包的数据区域的长度，所述第二长度大于所述第一长度。
  16. 根据权利要求15所述的实现网络能力开放的方法，其中，所述方法还包括：
    根据所述下行数据包的网际互联协议五元组信息生成所述随机值。
  17. 根据权利要求9至16任一项所述的实现网络能力开放的方法，其中，所述根据所述网络信息获取请求获取所请求的网络信息，包括：
    将所述网络信息获取请求发送至第一目标非用户面节点；
    接收所述第一目标非用户面节点响应于所述网络信息获取请求返回的所述第一目标非用户面节点的网络信息。
  18. 根据权利要求9至16任一项所述的实现网络能力开放的方法，其中，所述根据所述网络信息获取请求获取所请求的网络信息，包括：
    将所述网络信息获取请求发送至第一目标非用户面节点，以便于所述第一目标非用户面节点将所述网络信息获取请求发送至第二目标非用户面节点，并接收所述第二目标非用户面节点响应于所述网络信息请求返回的所述第二目标非用户面节点的网络信息；
    接收所述第一目标非用户面节点返回的所述第二目标非用户面节点的网络信息。
  19. 根据权利要求18所述的实现网络能力开放的方法，其中，还包括：
    接收所述第一目标非用户面节点返回的所述第二目标非用户面节点的更新网络信息；
    其中，所述第二目标非用户面节点的更新网络信息是所述第二目标非用户面节点的网络信息发生变化或者达到预定时间间隔时，所述第二目标非用户面节点发送给所述第一目标非用户面节点的。
  20. 一种实现网络能力开放的装置，包括：
    下行数据获取单元，配置为获取下行数据包，其中，所述下行数据包中包括网络信息获取请求；
    下行数据发送单元，配置为将所述下行数据包发送至目标用户面节点；
    响应信息接收单元，配置为接收所述目标用户面节点返回的响应于所述网络信息获取请求的响应信息，其中所述响应信息中包括所述网络信息获取请求所请求的网络信息。
  21. 一种实现网络能力开放的装置，包括：
    下行数据接收单元，配置为接收应用服务器发送的下行数据包，其中，所述下行数据包中包括网络信息获取请求；
    响应信息生成单元，配置为响应于所述网络信息获取请求，生成响应信息，其中，所述响应信息中包括所述网络信息获取请求所请求的网络信息；
    响应信息发送单元，配置为将所述响应信息发送至所述应用服务器。
  22. 一种电子设备，包括：
    一个或多个处理器；
    存储装置，配置为存储一个或多个程序，当所述一个或多个程序被所述一个或多个处理器执行时，使得所述一个或多个处理器实现如权利要求1至19中任一项所述的方法。
  23. 一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，所述计算机程序被处理器执行时实现如权利要求1至19中任一项所述的方法。
PCT/CN2020/128209 2020-03-15 2020-11-11 实现网络能力开放的方法、装置、电子设备和存储介质 WO2021184783A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP20925912.6A EP4017073A4 (en) 2020-03-15 2020-11-11 METHOD AND APPARATUS FOR PERFORMING NETWORK CAPACITY OPENING, ELECTRONIC DEVICE AND STORAGE MEDIA
US17/674,349 US20220174477A1 (en) 2020-03-15 2022-02-17 Method and apparatus for realizing network capability opening, electronic device and storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010179045.5 2020-03-15
CN202010179045.5A CN111356157A (zh) 2020-03-15 2020-03-15 实现网络能力开放的方法及相关设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/674,349 Continuation US20220174477A1 (en) 2020-03-15 2022-02-17 Method and apparatus for realizing network capability opening, electronic device and storage medium

Publications (1)

Publication Number Publication Date
WO2021184783A1 true WO2021184783A1 (zh) 2021-09-23

Family

ID=71197550

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/128209 WO2021184783A1 (zh) 2020-03-15 2020-11-11 实现网络能力开放的方法、装置、电子设备和存储介质

Country Status (4)

Country Link
US (1) US20220174477A1 (zh)
EP (1) EP4017073A4 (zh)
CN (1) CN111356157A (zh)
WO (1) WO2021184783A1 (zh)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111356157A (zh) * 2020-03-15 2020-06-30 腾讯科技（深圳）有限公司 实现网络能力开放的方法及相关设备
WO2022032521A1 (zh) * 2020-08-12 2022-02-17 华为技术有限公司 基于用户面的控制信令获取方法、装置和系统
CN115529590A (zh) * 2021-06-24 2022-12-27 中移(成都)信息通信科技有限公司 一种能力开放信息获取方法、装置和通信设备
CN115643608A (zh) * 2021-07-19 2023-01-24 阿里巴巴达摩院(杭州)科技有限公司 服务提供方法、系统、网关、设备和存储介质
CN115734199A (zh) * 2021-09-01 2023-03-03 华为技术有限公司 通信感知业务中选择网元的方法、通信装置和通信系统
CN114845276B (zh) * 2022-04-19 2023-06-06 广州爱浦路网络技术有限公司 一种网络能力开放的实现方法及平台
CN115277556A (zh) * 2022-06-21 2022-11-01 网宿科技股份有限公司 拥塞控制方法、电子设备及可读存储介质

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104854841A (zh) * 2013-10-31 2015-08-19 华为技术有限公司 应用服务器、终端设备、网络能力调用系统及方法
CN109417534A (zh) * 2016-05-02 2019-03-01 华为技术有限公司 通信网络服务质量能力开放方法和装置
CN110418395A (zh) * 2018-04-28 2019-11-05 华为技术有限公司 能力开放方法、相关装置及系统
US20190394833A1 (en) * 2018-06-21 2019-12-26 Peyman TALEBI FARD Multi Access Packet/Protocol Data Unit Session
CN110769466A (zh) * 2018-07-26 2020-02-07 中国移动通信有限公司研究院 信息发送和接收、业务和网络质量调控方法、装置及设备
CN111356157A (zh) * 2020-03-15 2020-06-30 腾讯科技（深圳）有限公司 实现网络能力开放的方法及相关设备

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016206118A1 (zh) * 2015-06-26 2016-12-29 华为技术有限公司 网络能力信息的获取方法及装置
US10362507B2 (en) * 2016-06-10 2019-07-23 Huawei Technologies Co., Ltd. Systems and method for quality of service monitoring, policy enforcement, and charging in a communications network
US10986516B2 (en) * 2017-03-10 2021-04-20 Huawei Technologies Co., Ltd. System and method of network policy optimization
US11974218B2 (en) * 2017-03-31 2024-04-30 British Telecommunications Public Limited Company Access network selection
CN109429348B (zh) * 2017-07-19 2022-03-29 华为技术有限公司 一种数据的处理方法、移动性管理设备和终端设备

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104854841A (zh) * 2013-10-31 2015-08-19 华为技术有限公司 应用服务器、终端设备、网络能力调用系统及方法
CN109417534A (zh) * 2016-05-02 2019-03-01 华为技术有限公司 通信网络服务质量能力开放方法和装置
CN110418395A (zh) * 2018-04-28 2019-11-05 华为技术有限公司 能力开放方法、相关装置及系统
US20190394833A1 (en) * 2018-06-21 2019-12-26 Peyman TALEBI FARD Multi Access Packet/Protocol Data Unit Session
CN110769466A (zh) * 2018-07-26 2020-02-07 中国移动通信有限公司研究院 信息发送和接收、业务和网络质量调控方法、装置及设备
CN111356157A (zh) * 2020-03-15 2020-06-30 腾讯科技（深圳）有限公司 实现网络能力开放的方法及相关设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
LG ELECTRONICS, INTEL: "Correction of UE 5GSM Core Network Capability", 3GPP DRAFT; S2-1903490_TS 23.502_REL15_5GSM CAPABILITY, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Xi'an, China; 20190408 - 20190412, 2 April 2019 (2019-04-02), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051719642 *

Also Published As

Publication number Publication date
EP4017073A4 (en) 2022-11-23
CN111356157A (zh) 2020-06-30
US20220174477A1 (en) 2022-06-02
EP4017073A1 (en) 2022-06-22

Similar Documents

Publication Publication Date Title
WO2021184783A1 (zh) 实现网络能力开放的方法、装置、电子设备和存储介质
CN106716951B (zh) 用于优化隧道流量的方法和装置
JP6907444B2 (ja) データ伝送方法、通信デバイス、端末、および基地局
JP4318733B2 (ja) 処理時間情報を含む制御プロトコルデータユニットの送受信方法
US9565699B2 (en) Method of performing polling procedure in a wireless communication system
RU2543996C2 (ru) Управление перегрузкой в сети связи
US8400982B2 (en) Method for handling correctly received but header compression failed packets
US10511640B2 (en) Providing cellular-specific transport layer service by way of cell-site proxying in a network environment
US20130024523A1 (en) System and method for flow termination of a tcp session
WO2019101054A1 (zh) 聚合速率控制方法、设备以及系统
CN109120540B (zh) 传输报文的方法、代理服务器和计算机可读存储介质
WO2022206251A1 (zh) 拒绝服务攻击的解决方法、装置、设备、介质和计算机程序产品
WO2023103847A1 (zh) 一种通信方法、装置及系统
WO2022063187A1 (zh) 一种通信方法和装置
Navarro‐Ortiz et al. Removing redundant TCP functionalities in wired‐cum‐wireless networks with IEEE 802.11 e HCCA support
WO2016058424A1 (zh) 一种数据传输方法、装置、系统及存储介质
WO2013050079A1 (en) Transmission of data to or from a node of a mobile network
Kumar et al. Device‐centric data reordering and buffer management for mobile Internet using Multipath Transmission Control Protocol
WO2023184552A1 (zh) 一种数据传输方法及装置、通信设备
WO2023071946A1 (zh) 一种通信方法及装置
WO2023028950A1 (en) Radio link control cumulative mode for new radio
KR102031896B1 (ko) Udp 캡슐화에 기반한 대역폭 정보 제공 방법 및 이를 위한 장치
CN117812746A (zh) 一种协议数据单元集合传输方法及装置
WO2018072097A1 (zh) 数据传输方法及设备
Adigozalov The Intelligent Use of Multiple Interfaces

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020925912

Country of ref document: EP

Effective date: 20220315

NENP Non-entry into the national phase

Ref country code: DE