WO2023000935A1 - 一种数据处理方法、网元设备以及可读存储介质 - Google Patents

一种数据处理方法、网元设备以及可读存储介质 Download PDF

Info

Publication number
WO2023000935A1
WO2023000935A1 PCT/CN2022/102056 CN2022102056W WO2023000935A1 WO 2023000935 A1 WO2023000935 A1 WO 2023000935A1 CN 2022102056 W CN2022102056 W CN 2022102056W WO 2023000935 A1 WO2023000935 A1 WO 2023000935A1
Authority
WO
WIPO (PCT)
Prior art keywords
application server
network element
edge application
edge
address
Prior art date
Application number
PCT/CN2022/102056
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 EP22845100.1A priority Critical patent/EP4247049A1/en
Publication of WO2023000935A1 publication Critical patent/WO2023000935A1/zh
Priority to US18/327,938 priority patent/US20230308951A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/141—Setup of application sessions
    • 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/10—Flow control between communication endpoints
    • H04W28/14—Flow control between communication endpoints using intermediate storage
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/12—Avoiding congestion; Recovering from congestion
    • H04L47/125—Avoiding congestion; Recovering from congestion by balancing the load, e.g. traffic engineering
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1004—Server selection for load balancing
    • H04L67/101—Server selection for load balancing based on network conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1036—Load balancing of requests to servers for services different from user content provisioning, e.g. load balancing across domain name servers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/146—Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
    • 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/08—Load balancing or load distribution
    • H04W28/084—Load balancing or load distribution among network function virtualisation [NFV] entities; among edge computing entities, e.g. multi-access edge computing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/22—Alternate routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/28—Routing or path finding of packets in data switching networks using route fault recovery

Definitions

  • the present application relates to the technical field of communications, and in particular to a data processing method, network element equipment, and a readable storage medium.
  • Edge Computing edge computing
  • the Session Management Function (SMF) in the 5G core network will generate a distribution rule based on the IP address of the edge application server obtained from the query, and the Intermediate User Plane Function (I-UPF, Intermediate User Plane Function ) Configure a distribution path for the terminal device according to the distribution rule, and then the Edge Application Server Discovery Function (EASDF) sends the IP address to the terminal device, so that the terminal device can access the edge application through the IP address and the distribution path server.
  • EASDF Edge Application Server Discovery Function
  • SMF needs to configure distribution rules for each IP address, and configure the I-UPF associated with all IP addresses.
  • L-PSA Local Protocol Data Unit Session Anchor, Local Protocol Data Unit Session Anchor
  • UPF establishes distribution paths, and the distribution paths corresponding to IP addresses not selected by terminal devices will be idle, resulting in waste of network resources.
  • Embodiments of the present application provide a data processing method, a network element device, and a readable storage medium, which can reduce waste of network resources.
  • An embodiment of the present application provides a data processing method on the one hand, including:
  • the session management network element receives the domain name system message report sent by the edge application server discovery network element; the domain name system message report contains at least two edge application server addresses;
  • the session management network element selects the target data network access identifier, and uses the edge application server address that has a mapping relationship with the target data network access identifier among at least two edge application server addresses as the offloading edge application server address;
  • the session management network element generates the offload rule of the intermediate user plane network element according to the address of the offload edge application server.
  • An embodiment of the present application provides a data processing method on the one hand, including:
  • the edge application server discovers that the network element receives the domain name system response message sent by the domain name system server; the domain name system response message includes at least two edge application server addresses;
  • the edge application server finds that the network element selects the target data network access identifier, and uses the edge application server address that has a mapping relationship with the target data network access identifier from at least two edge application server addresses as the offloading edge application server address;
  • the edge application server discovers that the network element sends the offload edge application server address and the target data network access identifier to the session management network element, so that the session management network element generates the offload rule of the intermediate user plane network element according to the offload edge application server address, and establishes An offload path between the intermediate user plane network element and the edge anchor user plane network element corresponding to the target data network access identifier.
  • An embodiment of the present application provides a data processing method on the one hand, including:
  • the intermediate user plane network element receives the offloading rules issued by the session management network element
  • the offload rule is generated according to the address of the offload edge application server; the offload rule is used to forward the service access request of the terminal device to access the offload edge application server address to the edge anchor user plane network element corresponding to the target data network access identifier; the target data
  • the network access identifier is selected by the session management network element after receiving the domain name system message report sent by the edge application server to discover the network element; the domain name system message report contains at least two edge application server addresses, and the edge application server
  • the address refers to the edge application server address that has a mapping relationship with the target data network access identifier among the at least two edge application server addresses.
  • An embodiment of the present application provides a network element device, including:
  • the report receiving module is used for the session management network element to receive the domain name system message report sent by the edge application server to discover the network element; the domain name system message report contains at least two edge application server addresses;
  • An identifier selection module configured to select a target data network access identifier
  • the address selection module is configured to use the address of the edge application server that has a mapping relationship with the target data network access identifier among the at least two edge application server addresses as the address of the offloading edge application server;
  • the rule generating module is configured to generate a distribution rule for an intermediate user plane network element according to the address of the distribution edge application server.
  • An embodiment of the present application provides a network element device, including:
  • the receiving module is used for the edge application server to discover the network element and receive the domain name system response message sent by the domain name system server; the domain name system response message contains at least two edge application server addresses;
  • An identifier selection module configured to select a target data network access identifier
  • the address selection module is configured to use the address of the edge application server that has a mapping relationship with the target data network access identifier from at least two addresses of the edge application server as the address of the offloading edge application server;
  • the sending module is used to send the offload edge application server address and the target data network access identifier to the session management network element, so that the session management network element generates the offload rule of the intermediate user plane network element according to the offload edge application server address, and establishes an intermediate An offload path between the user plane network element and the edge anchor user plane network element corresponding to the target data network access identifier.
  • An embodiment of the present application provides a network element device, including:
  • the rule receiving module is used for the intermediate user plane network element to receive the offloading rule issued by the session management network element; the offloading rule is generated according to the address of the offloading edge application server; the offloading rule is used to offload the service access of the terminal device access to the edge application server address
  • the request is forwarded to the edge anchor user plane network element corresponding to the target data network access identifier; the target data network access identifier is sent by the session management network element after receiving the domain name system message report sent by the edge application server discovery network element, Selected; the domain name system message report contains at least two edge application server addresses, and the offload edge application server address refers to the edge application server address that has a mapping relationship with the target data network access identifier among the at least two edge application server addresses .
  • An embodiment of the present application provides a network element device, including: a processor, a memory, and a network interface;
  • the above-mentioned processor is connected to the above-mentioned memory and the above-mentioned network interface, wherein the above-mentioned network interface is used to provide data communication network elements, the above-mentioned memory is used to store computer programs, and the above-mentioned processor is used to call the above-mentioned computer programs so that the network element equipment executes the present application Methods in the examples.
  • An embodiment of the present application provides a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and the computer program is adapted to be loaded by a processor and execute the method in the embodiment of the present application.
  • An aspect of the embodiments of the present application provides a computer program product or computer program, the computer program product or computer program includes computer instructions, and the computer instructions are suitable for being loaded by a processor and executing the method in the embodiments of the present application.
  • the session management network element obtains at least two edge application server addresses, and then can further select the target data network access identifier, and combine the at least two edge application server addresses with the target data network access identifier
  • the address of the edge application server with a mapping relationship is used as the address of the offload edge application server, and then the session management network element generates the offload rule of the intermediate user plane network element according to the address of the offload edge application server.
  • the session management network element does not generate offloading rules for all edge application server addresses, but determines the offloading edge application server addresses through a selection mechanism, and the subsequent intermediate user plane network elements can be based on the offloading rules.
  • the service access request of the terminal device to access the offload edge application server address is forwarded to the corresponding offload path, where the offload path can be the edge anchor corresponding to the intermediate user plane network element established by the session management network element and the target data network access identifier Point out the offload paths between user plane network elements. It can be seen that the session management network element does not need to establish offload paths associated with all edge application server addresses, which can reduce the occurrence of offload paths being idle, thereby reducing network resources. waste.
  • FIG. 1 is a schematic diagram of a system architecture provided by an embodiment of the present application.
  • FIG. 2a-FIG. 2c are schematic diagrams of scenarios of a data processing method provided by an embodiment of the present application.
  • Fig. 3 is a schematic flow chart of a data processing method provided by an embodiment of the present application.
  • 4a-4c are schematic diagrams of scenarios for selecting a target data network access identifier provided by an embodiment of the present application.
  • FIG. 5 is a schematic flow diagram of a data processing method provided in an embodiment of the present application.
  • FIG. 6 is a schematic flow chart of a data processing method provided in an embodiment of the present application.
  • FIG. 7 is an interactive schematic diagram of edge application server discovery provided by an embodiment of the present application.
  • FIG. 8 is a schematic diagram of a network architecture of an offload path provided in an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of a network element device provided in an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of a network element device provided in an embodiment of the present application.
  • FIG. 11 is a schematic structural diagram of a network element device provided in an embodiment of the present application.
  • FIG. 12 is a schematic structural diagram of a network element device provided in an embodiment of the present application.
  • FIG. 13 is a schematic structural diagram of a network element device provided in an embodiment of the present application.
  • FIG. 14 is a schematic structural diagram of a network element device provided in an embodiment of the present application.
  • FIG. 1 is a schematic diagram of a system architecture provided by an embodiment of the present application.
  • the system architecture can be applied to business scenarios supporting edge computing.
  • Edge computing refers to a platform that integrates network, computing storage, and application core capabilities on the edge of the network close to the source of objects or data, and provides edge intelligent services nearby to meet the needs of industry digitization in agile connection, real-time business, data optimization, application intelligence, security and Key requirements in terms of privacy protection, etc.
  • Edge computing enables operators and third-party services to be hosted close to the point of access of end devices, enabling efficient service capabilities by reducing end-to-end latency and load on the transport network.
  • the fifth generation mobile communication technology is a new generation of broadband mobile communication technology featuring high speed, low delay and large connection.
  • the International Telecommunication Union (ITU) defines typical scenarios in 5G applications, including: enhanced mobile broadband (Enhanced Mobile Broadband, eMBB), ultra-reliable and low-latency communication (Ultra-relaible and Low Latency Communication, URLLC), ultra-reliable and low-latency Communication and Massive Machine Type of Communication (mMTC), Vehicle to Everything (V2X), etc.
  • eMBB enhanced mobile broadband
  • URLLC ultra-reliable and low-latency Communication
  • mMTC Massive Machine Type of Communication
  • V2X Vehicle to Everything
  • the aforementioned eMBB scenarios provide high-traffic mobile broadband services, such as high-speed downloads, high-definition video, virtual reality (Virtual Reality, VR)/augmented reality (Augmented Reality, AR), etc.
  • URLLC scenarios and V2X scenarios can provide ultra-high reliability and ultra-low latency communications, such as autonomous driving, industrial control, telemedicine, etc., which require end-to-end high reliability of 99.999% and end-to-end ultra-low latency less than 1ms Low latency. Therefore, these business requirements also need to sink services to the edge of the network to reduce network latency caused by network transmission and multi-level service forwarding.
  • edge computing has increased the demand for edge computing.
  • edge computing and 5G can help solve bandwidth, speed and security problems for networks that encounter sudden and continuous traffic surges.
  • the system architecture may include an edge data center 100 and a terminal cluster.
  • the terminal cluster may include: terminal equipment 200a, terminal equipment 200b, terminal equipment 200c, ..., terminal equipment 200n, and the edge data center 100 may include multiple Edge application server (EAS), such as edge application server 100a, edge application server 100b, . . . , edge application server 100m.
  • EAS Edge application server
  • There may be a communication connection between the terminal clusters for example, a communication connection exists between the terminal device 200a and the terminal device 200b, and a communication connection exists between the terminal device 200a and the terminal device 200n.
  • There may be a communication connection between the edge application servers for example, a communication connection between the edge application server 100a and the edge application server 100b.
  • any terminal device in the terminal cluster may have a communication connection with any edge application server in the edge data center 100, for example, there is a communication connection between the terminal device 200a and the edge application server 100a.
  • the above-mentioned communication connection is not limited to a connection method, and may be through a 4G wireless access method, or may be through a 5G wireless access method, etc., and this application does not make a limitation here.
  • the system architecture shown in Figure 1 can also include an access network, a bearer network (transmission network) and a core network, and multiple base stations (such as 5G base stations gNB) can be deployed in the access network.
  • the bearer network can be composed of a series of switching and routing equipment of operators, and is mainly used to transmit control signaling and user data between the base station and the core network
  • the core network is A series of core network elements (“network elements" can also be referred to as "network functions”) can be deployed. These network elements cooperate to perform authentication, charging, and mobility management on terminal equipment.
  • the network is expanded and described.
  • SMF Session Management Function, session management function
  • SMF Session Management Function, session management function
  • UE IP User Equipment, that is, terminal equipment or user equipment
  • IP Internet Protocol, that is, Internet Protocol
  • UPF User Plane Function, user plane function
  • UPF User Plane Function, user plane function
  • UPF is the only data processing module in the 5G core network.
  • UPF can also be called a user plane network element, and its main functions are as follows:
  • Data Network such as operator services, Internet or third-party services, etc.
  • PCF Policy Control Function, Policy Control Function
  • UDR Unified Data Repository
  • EASDF Edge Application Server Discovery Function
  • EASDF Edge Application Server Discovery Function
  • (b3) DNS message is forwarded to C-DNS server (Central DNS server, center domain name system server) or L-DNS server (Local DNS server, local domain name system server) to perform DNS query;
  • C-DNS server Central DNS server, center domain name system server
  • L-DNS server Local DNS server, local domain name system server
  • EASDF can interact with the SMF through the data plane interface.
  • EASDF can be connected with PSA (PDU Session Anchor, that is, PDU Session Anchor) UPF through the data plane interface, and can be used to transmit DNS messages exchanged with UE.
  • PSA PDU Session Anchor
  • multiple EASDF instances can be deployed in a PLMN (Public Land Mobile Network, public land mobile network), and the interaction between the network functions of the 5G core network and EASDF takes place in a PLMN.
  • PLMN Public Land Mobile Network, public land mobile network
  • a terminal device such as any one of the terminal device 200a, the terminal device 200b, the terminal device 200c, and the terminal device 200n
  • a data network Data Network, DN
  • the terminal device can initiate an access request, and the base station can forward the requested service flow to the core network element UPF in the 5G core network (5G Core, which can be referred to as 5GC for short), and then pass After the UPF is forwarded by the core network element, it is sent to the external data network, and other core network elements in the 5G core network are responsible for processing signaling and controlling the entire process.
  • 5G Core 5G Core
  • edge computing can be used to meet different business needs.
  • an edge application service may be provided by multiple edge application servers usually deployed at different sites (such as edge application server 100a, edge application server 100b, and edge application server 100m in Figure 1) Services, these multiple edge application servers hosting edge application services may use a single IP address or different IP addresses.
  • an application may be deployed in the central application server, or it may be deployed in the edge application server.
  • edge application server In order to route the business flow of the application to the edge application server (Edge Application Service), the terminal device needs to know the IP address of the edge application server that provides services for the application, and the terminal device can perform discovery to obtain a suitable edge application server (such as The IP address of the nearest edge application server) so that traffic can be routed locally to the edge application server, and service latency, traffic routing paths, and user service experience can be optimized.
  • edge application server discovery is a process in which terminal devices use the domain name system to find the IP address of a suitable edge application server.
  • the Domain Name System is a service of the Internet, which serves as a distributed database that maps domain names and IP addresses to each other, enabling users to access the Internet more conveniently.
  • the 5G core network supports the PDU connection service between the terminal device and the data network.
  • the PDU connection service is embodied in the form of a PDU session (that is, a protocol data unit session).
  • a PDU session refers to the communication process between a terminal device and the data network. , that is to say, after the PDU session is established, the data transmission channel between the terminal device and the data network is also established. It should be noted that all core network data must be forwarded by the core network element I-UPF before it can flow to the external network. In other words, the connection of the data transmission channel corresponding to a PDU session is actually the connection between the terminal device and the core network element I-UPF , the core network element I-UPF is connected to the data network at the same time.
  • the core network element I-UPF When multiple PDU sessions are established, data forwarding must be completed through the core network element I-UPF.
  • the core network element The SMF and the core network element EASDF can interact multiple times, so that the core network element EASDF can correctly process DNS requests and DNS response messages, and the core network element SMF can be inserted into the core network on the core network element I-UPF
  • the network element L-PSA UPF is used to establish distribution paths and configure distribution rules to realize local distribution of data traffic.
  • the core network element L-PSA UPF can be deployed at the edge of the network, which can reduce transmission delay and alleviate the core network. Data transmission pressure, improve network data processing efficiency.
  • the nearby deployment of mobile edge computing can process ultra-large bandwidth traffic nearby, which can greatly reduce the impact of large bandwidth on the backbone network.
  • Typical scenarios are as follows: Stadium game live broadcast, concert live broadcast, mobile content distribution, etc.
  • the offload paths configured by the core network element SMF for different edge application server IP addresses may be different, and multiple core network element L-PSA UPFs may be inserted into the core network element I-UPF for a PDU session to Perform local distribution.
  • the target data network access identifier can be selected through the core network element SMF or the core network element EASDF.
  • the data network access identifier DNAI refers to an identifier for the user plane to access one or more DNs for deploying application programs. Then, the core network element SMF only needs to generate the offloading rules of the core network element I-UPF according to the IP address of the offloading edge application server, and select the core network element L-PSA UPF and UPF corresponding to the target data network access identifier.
  • the network element I-UPF of the core network establishes an offload path associated with the IP address of the offload edge application server. It can be understood that the core network element EASDF only needs to send the IP address of the offload edge application server to the terminal device, and the terminal device can access the corresponding edge application server through the IP address of the offload edge application server to obtain edge application services.
  • the above terminal devices that can be used for edge computing may include terminal application products in civil, commercial, industrial, military and other fields, such as smart phones, tablet computers, notebook computers, palmtop computers, mobile internet devices (mobile internet devices, MID), wearable devices (such as smart watches, smart bracelets, etc.), smart computers, smart cars, smart homes, drones, ATM machines, cameras, traffic lights, generators or various types of sensors, etc.
  • the edge application server can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, and can also provide cloud database, cloud service, cloud computing, cloud function, cloud storage, network service, cloud communication , middleware services, domain name services, security services, CDN, and cloud servers for basic cloud computing services such as big data and artificial intelligence platforms.
  • the terminal device and the edge application server may be directly or indirectly connected in a wired or wireless manner, which is not limited in this embodiment of the present application.
  • a terminal device initiates a protocol data unit session to obtain an edge application service as an example.
  • a protocol data unit session establishment request 3001 i.e., the PDU session establishment request in the embodiment corresponding to FIG. 1 above
  • the session management network element 300a i.e.
  • the network element SMF can respond to the protocol data unit session establishment request 3001, and obtain the PDU session-related policy information provided by the policy control network element (that is, the core network network element PCF in the embodiment corresponding to Figure 1 above) to the edge application server deployment information, and then select the corresponding edge application server discovery network element (that is, the core network network element EASDF in the embodiment corresponding to FIG. A connection can be established between the session management network element 300a and the edge application server discovery network element 300b.
  • the terminal device 301 can initiate a domain name system query request 3002, wherein the domain name system query request 3002 is used to query
  • the address of the edge application server that provides the edge application service required by the terminal device 301 (that is, the IP address of the edge application server described in FIG. 1 above) can be obtained.
  • the edge application server discovers that the network element 300b will perform data interaction with the domain name system server 302 according to the domain name system query request 3002 , and then receives the domain name system response message 3003 sent by the domain name system server 302 .
  • the domain name system response message 3003 includes a suitable edge application server address set 3004, wherein the edge application server address set 3004 may include at least two edge application server addresses.
  • the edge application server address set 3004 may include edge application server address A1, edge application server address A2, edge application server address B1, edge application server address C1, and edge application server address C2.
  • the edge application servers corresponding to different edge application server addresses may be located on different edge computing platforms, so the data network (that is, the corresponding data network access identifier) may be different.
  • the edge application server address A1 The data network access identifier corresponding to the edge application server address A2 is A
  • the data network access identifier corresponding to the edge application server address B1 is B
  • the identifier is C.
  • the edge application server discovers that the network element 300b sends a domain name system message report 3005 carrying the edge application server address set 3004 to the session management network element 300a.
  • the session management network element 300a needs to select the edge application server addresses in the edge application server address set 3004 first, and obtain some edge application server addresses as the distribution edge application server addresses.
  • the session management network element 300a can first select the target data network access identifier, and then the session management network element 300a will select an address that has a mapping with the target data network access identifier from at least two edge application server addresses The edge application server address of the relationship is used as the offload edge application server address.
  • the distribution edge application server address set 3006 includes the distribution edge application server address C1 and the distribution edge application server address C2, and then, the session management network element 300a will use the distribution edge application server address set
  • the offloading edge application server address in 3006 generates a offloading rule, and delivers it to the intermediate user plane network element 300c (that is, the core network element I-UPF in the above-mentioned embodiment corresponding to FIG. 1 ).
  • the session management network element 300a can insert the edge anchor user plane network element 300d (that is, the core network element L-PSA UPF in the embodiment corresponding to FIG.
  • the anchor user plane network element 300d is the edge anchor user plane network element corresponding to the target data network access identifier, that is, the session management network element 300a can establish a connection between the intermediate user plane network element 300c and the edge anchor user plane network element 300d
  • the offloading path is used to offload the service flow corresponding to the offloading edge application server address C1 and offloading edge application server address C2, in other words, the terminal device accesses the Edge application servers can all be implemented through this distribution path.
  • the edge application server After the offload rule is issued and the offload path is established, the edge application server discovers that the network element 300b will transfer the offload edge application server address C1 and offload edge application server address C1 in the offload edge application server address set 3006
  • the server address C2 is sent to the terminal device 301 together, and the terminal device 301 can select a distribution edge application server address from the distribution edge application server address set 3006 as the service access address to access the edge application corresponding to the distribution edge application server address server to obtain edge application services.
  • the offload edge application server address C1 corresponds to the edge application server 303
  • the service access request is used to obtain the edge application service
  • the intermediate The user plane network element 300c recognizes that the service access request carries the offloading edge application server address C1, and then forwards the service access request to the edge anchor user plane network element 300d according to the offloading rules and offloading paths, and is finally accepted by the edge anchor user plane network element 300c.
  • the network element 300d sends it to the edge application server 303.
  • the address of the offload edge application server C2 can be used as the service access address, and a service access request carrying the address of the offload edge application server C2 can be re-initiated.
  • the service access request of the application server address C2 reaches the intermediate user plane network element 300c, the service access request will also be forwarded by the intermediate user plane network element 300c to the edge anchor user plane network element 300d, and then the service access request will be sent by the edge The anchor user plane network element 300d forwards to the edge application server corresponding to the offload edge application server address C2.
  • Fig. 2a-Fig. 2c only reflect the core network elements (including SMF, EASDF, I-UPF and L-PSA UPF) closely related to the embodiment of the present application.
  • Other core network elements such as AMF (Access and Mobility Management Function), base station, PCF, etc., will also be involved in the service scenario, which will not be expanded in this embodiment of the present application.
  • AMF Access and Mobility Management Function
  • FIG. 3 is a schematic flowchart of a data processing method provided in an embodiment of the present application.
  • the data processing method can be executed by a session management network element (SMF).
  • SMF session management network element
  • the data processing method may at least include the following steps S101-step S103:
  • Step S101 the session management network element receives the domain name system message report sent by the edge application server discovery network element; the domain name system message report includes at least two edge application server addresses.
  • a terminal device wants to start an edge application service EAS, it needs to know the edge application server address of the edge application server that provides services for the edge application service, and the domain name system query request (DNS Query) of the terminal device is sent to the edge application server to find After the network element, the edge application server finds that the network element can query the domain name system server for a suitable edge application server address. After the domain name system server responds to the domain name system query request of the edge application server to discover the network element, it may notify the edge application server of at least two addresses of the edge application server to discover the network element.
  • DNS Query domain name system query request
  • the edge application server address may be an Internet Protocol (IP) address for interconnection between networks and any other information that can be used to identify a node in the edge application server, such as an IP address. It can be understood that the edge application servers respectively corresponding to at least two edge application server addresses can provide the edge application service for the terminal device independently.
  • IP Internet Protocol
  • Step S102 the session management network element selects the target data network access identifier, and uses the edge application server address that has a mapping relationship with the target data network access identifier among the at least two edge application server addresses as the distribution edge application server address.
  • the data network access identifiers corresponding to the edge application server addresses of at least two edge application servers may be different.
  • a data network access identifier (DN Access Identifier, DNAI) refers to an identifier for a user plane to access a data network DN deployed by one or more applications.
  • One data network access identifier can correspond to one or more edge-anchor user plane network elements (L-PSA UPF), and the edge-anchor user plane network elements corresponding to different data network access identifiers can be different.
  • L-PSA UPF edge-anchor user plane network elements
  • the offloading of the edge application server address corresponding to the same data network access identifier can be realized through the edge anchor user plane network element corresponding to the data network access identifier. Therefore, from the at least two edge application server addresses, only the edge application server address corresponding to the target data network access identifier may be used as the offloading edge application server address.
  • the mapping relationship between the edge application server address and the data network access identifier can be written into the pre-configuration information table, and then the session management network element receives at least two edge
  • the server address according to the pre-configuration information table, look up the data network access identifier with a mapping relationship for each edge application server address in the pre-configuration information table as the data network access identifier to be selected, and then from the to-be-selected
  • the target data network access identifier is obtained according to a preset selection rule.
  • the selection rule may be random selection, round selection, load sharing and so on.
  • step S103 the session management network element generates a distribution rule for the intermediate user plane network element according to the address of the distribution edge application server.
  • the offloading rules may also be called offloading policies
  • the session management network element controls the intermediate user plane network element to execute service flow processing by configuring various offloading policies.
  • the session management network element after the session management network element generates the distribution rule according to the distribution edge application server address, it can establish a distribution path between the intermediate user plane network element and the edge anchor user plane network element corresponding to the target data network access identifier; and then The session management network element can issue distribution rules to the intermediate user plane network element, and the intermediate user plane network element forwards the service access request of the terminal device to access the distribution edge application server address to the edge anchor user plane network element based on the distribution rule and the distribution path; Then, the edge anchor user plane network element may forward the service access request to the edge application server corresponding to the address of the distribution edge application server. It can be understood that one target data network access identifier may correspond to one or more edge-anchor user plane network elements.
  • the session management network element can configure the UL CL (Uplink classifier, uplink classifier) corresponding to the edge anchor user plane network element on the intermediate user plane network element to provide a capability interface to support distribution rules.
  • the offloading rules include traffic detection and traffic forwarding rules.
  • the offloading rules corresponding to the offloading edge application server address can be configured to offload the traffic whose destination address is the offloading edge application server address to the edge anchor user plane network element, and finally send it to the edge application server.
  • the UL CL can forward the service flow of the terminal device to the edge anchor user plane network element according to the traffic detection and traffic forwarding rules.
  • the UL CL configuration is completed, and the offload path between the intermediate user plane network element and the edge anchor user plane network element is established.
  • the session management network element can send the offloading edge application server address to the edge application server to discover the network element, and then the edge application server will offload the edge application server address upon discovering the network element Send it to the terminal device, so that the terminal device can choose a distribution edge application server address from the distribution edge application server address as the service access address, and the service access request of the terminal device to the service access address will be sent to the service access through the above distribution path
  • the edge application server corresponding to the address.
  • edge application server address set 400 obtained by the session management network element includes edge application server address A1, edge application server address A2, edge application server address B1, edge application server address C1, and edge application server address C2.
  • the specific process for the session management network element to select the target data network access identifier may be as follows: the session management network element obtains the target edge application server address from at least two edge application server addresses; then the session management network The element uses the data network access identifier that has a mapping relationship with the address of the target edge application server as the target data network access identifier.
  • the session management network element can randomly select an edge application server address from the edge application server address set 400, for example, obtain the edge application server address A2 (ie, the target edge application server address) through a random function, and then, the session The management network element can determine that the data network access identifier that has a mapping relationship with the edge application server address A2 is the data network access identifier A, and then the session management network element can use the data network access identifier A as the target data network access identifier. Enter the identifier.
  • the specific process for the session management network element to select the target data network access identifier may be as follows: the session management network element obtains the data network access identifier that has a mapping relationship with at least two edge application server addresses respectively, Obtain one or more data network access identifiers to be selected; the session management network element queries the load conditions of the edge anchor user plane network elements respectively corresponding to the one or more data network access identifiers to be selected; the session management network element according to The load situation determines the target data network access identifier among the one or more data network access identifiers to be selected.
  • the session management network element inquires in turn the data network access identifiers with a mapping relationship between each edge application server address, and obtains a set of data network access identifiers to be selected 401, the set of data network access identifiers to be selected 401 includes a data network access identifier A to be selected, a data network access identifier B to be selected, and a data network access identifier C to be selected.
  • the session management network element can find the edge anchor user plane network element 402a corresponding to the data network access identifier A to be selected, the edge anchor user plane network element 402b corresponding to the data network access identifier B to be selected and the The edge anchor user plane network element 402c corresponding to the data network access identifier C can then determine the load situation corresponding to each edge anchor user plane network element by querying historical offload rules and current offload path connection status, etc. Then a comparison is made, and finally the data network access identifier to be selected corresponding to the edge-anchor user plane network element with the best load condition is selected as the target data network access identifier.
  • the specific process for the session management network element to select the target data network access identifier may be as follows: the session management network element obtains the data network access identifier that has a mapping relationship with at least two edge application server addresses respectively, Obtain one or more data network access identifiers to be selected; the session management network element can obtain the predicted average values of the edge-anchor user plane network elements respectively corresponding to the one or more data network access identifiers to be selected within the target time period Load condition; then determine the target data network access identifier among one or more data network access identifiers to be selected according to the predicted average load condition.
  • the session management network element can query the predicted average load situation corresponding to the edge anchor user plane network element, wherein the predicted average load situation refers to the target time period (that is, the future time period, such as the next ten minutes, the next One hour, etc.) the average load of the edge-anchor user plane network element, and then select the data network access identifier to be selected corresponding to the edge-anchor user plane network element with the best predicted average load as the target data network access identifier.
  • the target time period that is, the future time period, such as the next ten minutes, the next One hour, etc.
  • the specific process for the session management network element to select the target data network access identifier may be as follows: the session management network element obtains the data network access identifier that has a mapping relationship with at least two edge application server addresses respectively, One or more data network access identifiers to be selected are obtained; the session management network element determines a target data network access identifier from the one or more data network access identifiers to be selected according to a polling mechanism.
  • a polling table set 403 may be included in the session management network element, and the polling table set 403 includes a plurality of polling tables, such as a polling table 404, and a polling table includes a polling sequence The data network access identifier to be selected and the last selected target data network access identifier mark.
  • the session management network element queries the polling table set 403 to obtain the polling table 404 corresponding to the data network access identifier set 401 to be selected.
  • the polling sequence in the polling table 404 is A ⁇ B ⁇ C ⁇ A..., at this time, the data network access identifier to be selected marked by the target data network access identifier mark 405 is the data network access identifier to be selected B, indicating that the target data network access identifier selected last time is the data network access identifier B to be selected. Therefore, the session management network element will use the data network access identifier C to be selected next to the data network access identifier B to be selected as the target data network access identifier according to the polling sequence.
  • the session management network element can update the target data network access identifier flag 405, that is, use the target data network access identifier flag 405 to mark the data network access to be selected identifier C.
  • the session management network element can select the target data network access identifier, and then can select the target data network access identifier from the received at least two Among the edge application server addresses, the edge application server address that has a mapping relationship with the target data network access identifier is used as the distribution edge application server address, and then the distribution rule of the intermediate user plane network element is generated based on the distribution edge application server address, and the session The management NE will only create a distribution path for the distribution edge application server address on the intermediate user plane network element, and it is not necessary to establish distribution paths corresponding to all edge application server addresses, which can reduce the waste of network resources and reduce the need for the core network to support multiple distributions at the same time. path burden.
  • FIG. 5 is a schematic flowchart of a data processing method provided by an embodiment of the present application.
  • the data processing method can be executed by an edge application server discovery network element (EASDF).
  • EASDF edge application server discovery network element
  • the data processing method may at least include the following steps S201-step S203:
  • the edge application server discovers network elements and receives a DNS response message sent by the domain name system server; the domain name system response message includes at least two edge application server addresses.
  • the edge application server discovers that the network element will interact with the domain name system server after obtaining the domain name system query request sent by the terminal device, and then receive the domain name system response message sent by the domain name system server.
  • the domain name system query request is used to obtain the edge application server address of the edge application server that provides services for the edge application service to be started by the terminal device.
  • Step S202 the edge application server discovers that the network element selects the target data network access identifier, and uses the edge application server address that has a mapping relationship with the target data network access identifier from at least two edge application server addresses as the offloaded edge application server address.
  • the edge application server After the edge application server discovers that the network element receives the domain name system response message, it first selects the target data network access identifier, and then according to the target data network access identifier, at least two edge Select the address of the application server to determine the address of the offload edge application server. It can be understood that the edge application server discovers that the network element selects the target data network access identifier, and from the at least two edge application server addresses, the edge application server address that has a mapping relationship with the target data network access identifier, The specific implementation process of the address of the offloading edge application server may be the same as the specific implementation process of selecting the address of the offloading edge application server by the session management network element in the embodiment corresponding to Figure 3 above. The selection of the access identifier may occur in the network element discovered by the edge application server, which will not be repeated here.
  • Step S203 the edge application server discovers that the network element sends the offload edge application server address and the target data network access identifier to the session management network element, so that the session management network element generates an intermediate user plane according to the offload edge application server address
  • the distribution rule of the network element establishes the distribution path between the intermediate user plane network element and the edge anchor user plane network element corresponding to the target data network access identifier.
  • the edge application server discovers that the network element no longer sends all the edge application server addresses contained in the domain name system response message to the session management network element, but only sends the distribution edge application server address and the target data network access identifier to the session management network element.
  • the session management network element does not need to select the received distribution edge application server address, directly according to the target data network access identifier and the distribution edge application server address that have a mapping relationship with the distribution edge application server address, Generate an offload rule for the intermediate user plane network element, and establish an offload path between the intermediate user plane network element and the edge anchor user plane network element corresponding to the target data network access identifier.
  • the edge application server discovers that the network element sends the address of the offload edge application server to the terminal device after the offload rule is generated and the offload path is established.
  • the selection process of the target data network access identifier can be realized by the edge application server discovering the network element, and the edge application server can find the network element directly according to the target data network access identifier from the domain name system. Select the offload edge application server address from at least two edge application server addresses included in the response message, and then send the offload edge application server address and the target data network access identifier to the session management network element.
  • the session management network element only generates the distribution rule according to the distribution edge application server address, and establishes the distribution path between the intermediate user plane network element and the edge anchor user plane network element corresponding to the target data network access identifier, which can reduce the network resources. waste, and reduce the burden on the core network to support multiple distribution paths at the same time.
  • FIG. 6 is a schematic flowchart of a data processing method provided by an embodiment of the present application.
  • the data processing method can be executed by an intermediate user plane network element (I-UPF).
  • I-UPF intermediate user plane network element
  • the data processing method may at least include the following steps S301-step S303:
  • step S301 the intermediate user plane network element receives the distribution rule issued by the session management network element.
  • the offloading rule is generated according to the address of the offloading edge application server, and the offloading rule is used to forward the service access request of the terminal device to access the address of the offloading edge application server to the edge anchor user plane network corresponding to the target data network access identifier Yuan.
  • the target data network access identifier is selected by the session management network element after receiving the domain name system message report sent by the edge application server discovery network element.
  • the domain name system message report includes at least two edge application server addresses.
  • the offloading edge application server address refers to the edge application server address that has a mapping relationship with the target data network access identifier among at least two edge application server addresses.
  • Step S302 the intermediate user plane network element forwards the service access request of the terminal device to access the address of the offload edge application server to the edge anchor user plane network element corresponding to the target data network access identifier based on the offload rule and the offload path,
  • the edge anchor user plane network element forwards the service access request to the edge application server corresponding to the distribution edge application server address.
  • the offload path is an offload path between the intermediate user plane network element established by the session management network element and the edge anchor user plane network element corresponding to the target data network access identifier.
  • the process in which the intermediate user plane network element forwards the service access request of the terminal device to access the offload edge application server address to the edge anchor user plane network element corresponding to the target data network access identifier based on the offload rule and the offload path can be :
  • the intermediate user plane network element receives the target service access request sent by the terminal device, where the target service access request carries the address of the target edge application server.
  • the intermediate user plane network element finds the same edge application server address as the target edge application server address in the distribution edge application server address, it forwards the target service access request to the target data network access identifier based on the distribution rule and the distribution path The edge anchor user plane network element corresponding to the identifier, so that the edge anchor user plane network element forwards the target service access request to the edge application server corresponding to the target edge application server address.
  • the UL CL uses flow filtering rules (such as checking the destination IP address/prefix of the target service access request sent by the terminal device) to decide whether to access the target service
  • the request is forwarded to the corresponding edge-anchor user plane network element, and if it is determined that the target service access request is sent to the address of the distribution edge application server, the target service access request is forwarded to the edge-anchor user plane network element.
  • the edge application server corresponding to the offload edge application server address is used to provide edge application services for terminal devices; the number of offload edge application server addresses is at least two, and the at least two offload edge application server addresses include the first offload edge application server address and the address of the second offload edge application server.
  • the second offloading edge application server address is the edge application server address carried in the service access request initiated by the terminal device again after failing to access the edge application service through the first offloading edge application server address.
  • the terminal device receives available offload edge application server addresses including offload edge application server address E1, offload edge application server address E2, and offload edge application server address E3, the terminal device can randomly obtain a offload edge application server address, For example, if the distribution edge application server address E1 is used as the target edge application server address, a business access request is initiated to the edge application server corresponding to the distribution edge application server address E1 to obtain edge application services.
  • the terminal device can select a new target edge application server address from the received unselected distribution edge application server addresses, such as the distribution edge application server address E3, and the terminal device The device may initiate a service access request to the edge application server corresponding to the offloaded edge application server address E3 to obtain the edge application service.
  • FIG. 7 is a schematic diagram of an interaction of edge application server discovery provided by an embodiment of the present application.
  • the entire interaction process mainly involves the terminal equipment UE, the session management network element SMF, the edge application server discovery network element EASDF, the domain name system DNS server, and the user plane network element UPF that can be inserted into the uplink classifier UL CL (ie Intermediate user plane network element I-UPF), local PDU session anchor L-PSA user plane network element UPF (that is, edge anchor user plane network element L-PSA UPF).
  • the interaction process includes:
  • Step S401 EASDF sends a DNS query request (DNS Query) to the DNS server.
  • the DNS query request is a query request sent by the UE to the EASDF, and is a query request initiated by the UE to obtain an IP address of an edge application server that can provide edge application services.
  • EASDF can add ECS option in DNS Query message and send it to DNS server.
  • step S402 the DNS server sends a DNS response message (DNS Responses) to the EASDF.
  • DNS Responses DNS Responses
  • EASDF can receive DNS Responses from the DNS server, and determine that it can send DNS Responses to UE.
  • the DNS Response can contain multiple IP addresses of edge application servers that can provide the UE with the required edge application services, that is, multiple EAS IP addresses.
  • step S403 the EASDF sends a DNS message report to the SMF.
  • EASDF can call the Neasdf_DNSContext_Notify (EASDF DNS context notification service) service containing EAS information to send to SMF DNS message reporting.
  • the DNS message report contains multiple EAS IP addresses received by EASDF. It should be noted that, according to the DNS message processing rules, the EASDF will not send the DNS response message to the UE at this time, but wait for the SMF instruction (in step S406), that is, cache the DNS response message first. Unless otherwise specified, this document does not limit the names of services provided by EASDF, such as Neasdf_DNSContext_Notify, etc.
  • Step S404 the SMF responds to the DNS message report.
  • SMF calls Neasdf_DNSContext_Notify to respond.
  • step S405 the SMF determines the offload address according to the target data network access identifier (DNAI), and generates a corresponding offload rule.
  • DNAI target data network access identifier
  • the SMF After the SMF obtains the EAS IP address in the DNS message report, it will select a DNAI as the target DNAI, and then obtain the EAS IP address that has a mapping relationship with the target DNAI as the distribution edge according to the mapping relationship between the target DNAI and the EAS IP address
  • the address of the application server (that is, the address of the distribution edge application server in the above-mentioned embodiment corresponding to FIG. 3 ).
  • the selection process of the target DNAI can also be performed in step S403.
  • the DNS message report sent by the EASDF to the SMF will only include the target DNAI and the EAS IP address that has a mapping relationship with the target DNAI.
  • the DNS message report sent by the EASDF to the SMF will only include the target DNAI and the EAS IP address that has a mapping relationship with the target DNAI.
  • step S202 in the above embodiment corresponding to FIG. 5 which will not be repeated here.
  • the SMF can generate a distribution rule based on the distribution edge application server address, and then send it to the I-UPF.
  • the generation process of the distribution rule refer to the description of step S103 in the embodiment corresponding to FIG. 3 above, and will not repeat it here.
  • the SMF will determine the uplink classifier UL CL corresponding to the target DNAI that needs to be inserted into the I-UPF, and then configure the UL CL to establish a shunt path between the I-UPF and the L-PAS UPF.
  • the SMF will determine the uplink classifier UL CL corresponding to the target DNAI that needs to be inserted into the I-UPF, and then configure the UL CL to establish a shunt path between the I-UPF and the L-PAS UPF.
  • Step S407 the SMF invokes the DNS message processing rule, and sends the DNS message processing rule request to the EASDF.
  • the SMF calls the Neasdf_DNSContext_Update Request service request, and sends the DNS message processing rule request to the EASDF, wherein the DNS message processing rule is used to instruct the EASDF to send the DNS response message cached in step S403 to the UE.
  • Step S408 EASDF executes the DNS message processing rule, and sends a response message to the SMF.
  • EASDF calls Neasdf_DNSContext_Update Response to respond to SMF.
  • Step S409 The EASDF sends a DNS response message including the address of the offload edge application server to the UE.
  • the EASDF sends a DNS response message including the address of the offload edge application server to the UE.
  • the UE can access the offloading edge application server to obtain the corresponding edge application service.
  • step S303 For the process of obtaining the edge application service by the UE, refer to step S303 in the above embodiment corresponding to FIG. 6 .
  • SMF can use the EAS IP address that has a mapping relationship with the target DNAI as the address of the distribution edge application server, so that the distribution rule is generated only based on the address of the distribution edge application server, and it is no longer necessary to query the DNS server. All available EAS IP addresses to establish offload paths to avoid the offload paths associated with EAS IP addresses not selected by terminal devices from being idle, thereby reducing the waste of network resources.
  • FIG. 8 is a schematic diagram of a network architecture of an offload path provided by an embodiment of the present application.
  • the network architecture involves terminal equipment 801 (User Equipment, UE), access network 802 (Access Network, AN), multiple functional network elements of the core network, and a central data network 803 (Central DN) and Edge Data Network 804 (EAS DN).
  • terminal equipment 801 User Equipment, UE
  • access network 802 Access Network, AN
  • EAS DN Edge Data Network
  • the multiple functional network elements of the core network may include: a user plane function 805 that can be inserted into the uplink classifier (UL CL) (that is, the above-mentioned intermediate user plane network element I-UPF), a central protocol data unit session anchor Point user plane function (Central Protocol Data Unit Session Anchor UPF, C-PSA UPF) 806, local protocol data unit session anchor user plane function 807 (that is, the above-mentioned edge anchor user plane network element L-PSA UPF), access and Mobility management function 808 (Access and Mobility Management Function, AMF), session management function 809 (that is, the above-mentioned session management network element), network exposure function 810 (Network Exposure Function, NEF), edge application server discovery function 811 (that is, the above-mentioned edge Application server discovers network elements), network storage function 812 (Network Repository Function, NRF), policy control function 813 (Policy Control Function, PCF), application function 814 (Application Function, AF) and unified data management 8
  • Functional network elements of the core network can provide service interfaces, and the naming rule is to add N in front of the name of the function body.
  • the service-based interface (Service-based interface) is the interface exposed by the function body implemented by the service registration and service discovery similar to the micro-service architecture. This interface is only for a single function body, while other function bodies use this function The interface exposed by the body interacts with this function body. In fact, this mechanism provides a many-to-one access mechanism, and because of the use of service registration and service discovery, they can access each other without knowing each other's address. As shown in FIG.
  • the access and mobility management function 808 provides a service interface 8080 (which may be called Namf), the session management function 809 provides a service interface 8090 (which may be called Nsmf), and the network opening function 810 provides a service interface 8100 ( may be called Nnef), the edge application server discovery function 811 provides a service interface 8110 (which may be called Neasdf), the network storage function 812 provides a service interface 8120 (which may be called Nnrf), and the policy control function 813 provides a service interface 8130 ( It can be called Npcf), the application function 814 provides a service interface 8140 (it can be called Naf), and the unified data management 815 provides a service interface 8150 (it can be called Nudm).
  • Functional network elements interact with other functional network elements through service interfaces.
  • the network architecture can also include reference points.
  • a reference point is similar to a traditional interface, which is a mutually agreed mutual access interface between two different functional entities.
  • the reference point between two functional bodies can generally be replaced by one or more service-oriented interfaces, so as to provide exactly the same but more flexible and scalable implementation, and communication between user function blocks.
  • reference point N1 is the interface between the terminal equipment 801 and the access and mobility management function 808; reference point N2 is the interface between the access network 802 and the access and mobility management function 808; reference point N3 It is the interface between the access network 802 and the user plane function 805 that can be inserted into the uplink classifier, and the tunnel transmission of user data can be performed by using the GTP-U (a tunnel transmission protocol) protocol; the reference point N4 is the session management function 809 and The interface between the user plane function 805 that can be plugged into the uplink classifier is also the interface between the session management function 809 and the central protocol data unit session anchor user plane function 806, and is also the interface between the session management function 809 and the local protocol data unit session anchor The interface between the point user plane function 807; N6 reference point is the interface between the central PDU session anchor user plane function 806 and the central data network 803, and is also the interface between the local PDU session anchor user plane function 807 and the edge data
  • the interface between networks 804 can support dedicated lines or
  • the service-oriented interface and reference point are modeled interaction methods between two different network entities introduced by the 5G architecture.
  • the terminal device 801 can access the edge data network 804 where the edge application server EAS is located.
  • EASDF may query the DNS server for the IP addresses of edge application servers available to the UE, and after receiving multiple IP addresses, EASDF first sends the multiple IP addresses to the SMF.
  • SMF When SMF receives multiple IP addresses, it will determine the mapping relationship between each IP address and DNAI according to the pre-configured information, for example: DNAI#1:IP#1,IP#2; DNAI#2:IP#3,IP #4, IP#5, that is, DNAI#1 has a mapping relationship with IP#1 and IP#2, and DNAI#2 has a mapping relationship with IP#3, IP#4 and IP#5.
  • the SMF may further determine the selected IP address according to the mapping relationship between the IP address and the DNAI.
  • DNAI will affect the selection of I-UPF and L-PSA UPF. Different DNAIs usually correspond to different L-PSA UPFs, so when the business IP address received by SMF corresponds to multiple DNAIs, SMF will select a target DNAI, and then select the IP address corresponding to the target DNAI as the diversion address, so that When distributing the path on the user plane, you only need to select the L-PSA UPF that supports the target DNAI to establish the distributing path.
  • the SMF can select all IP addresses corresponding to the target DNAI, and use these IP addresses as the offload address of the UE (that is, the above-mentioned offload edge application server address, and these IP addresses will be associated with the established offload path), and then the SMF Send the distribution address to the EASDF, and then the EASDF sends the distribution address to the UE.
  • the UE When initiating service access subsequently, the UE will arbitrarily select one of these offload addresses for service access. When the offload address fails to be accessed, it will select one offload address from other offload addresses to initiate service access again.
  • the SMF may select only one IP address corresponding to the target DNAI and configure it as the offload address of the UE.
  • EASDF queries the DNS system for the IP address of the edge application server available to the UE. If the EASDF receives multiple IP addresses returned by the DNS system, the EASDF can, based on the pre-configured information, Determine the mapping relationship between these IP addresses and the DNAI. Then EASDF can select a target DNAI, and then select the IP address corresponding to the target DNAI, so that when establishing the user plane offload path, it will select the L-PSA UPF that supports the target DNAI to establish the offload path. EASDF will send the IP address corresponding to the target DNAI to SMF.
  • SMF will use these IP addresses as the UE's offload address (that is, the offload edge application server address in the offload rule on I-UPF).
  • EASDF will send the offload address corresponding to the target DNAI to the UE.
  • the UE When initiating service access subsequently, the UE will arbitrarily select one of these offload addresses for service access.
  • the offload address fails to be accessed, it will select one offload address from other offload addresses to initiate service access again.
  • the EASDF may select only one IP address corresponding to the target DNAI as the offload address of the UE.
  • the session management network element uses the method provided in the embodiment of the present application, at least two IP addresses are obtained, and then the target DNAI can be further selected, and the IP address that has a mapping relationship with the target DNAI among the at least two IP addresses can be used as the diversion address, and then the session The management network element generates the distribution rule of the intermediate user plane network element according to the distribution address. It can be seen that in the embodiment of the present application, the session management network element does not generate distribution rules for all IP addresses, but determines the distribution address through a selection mechanism, so that only the distribution path associated with the distribution address is established in the future, and the distribution path is not used. Then establish distribution paths associated with all available IP addresses, so as to prevent distribution paths associated with IP addresses not selected by the terminal device from being idle, thereby reducing waste of network resources.
  • FIG. 9 is a schematic structural diagram of a network element device provided in an embodiment of the present application.
  • the network element device can be a computer program (including program code) running on the network element equipment, for example, the network element device is an application software; the device can be used to execute the corresponding steps in the data processing method provided by the embodiment of the present application .
  • the network element device 1 may include: a report receiving module 11 , an identifier selection module 12 , an address selection module 13 and a rule generation module 14 .
  • the report receiving module 11 is used for the session management network element to receive the domain name system message report sent by the edge application server discovery network element; the domain name system message report contains at least two edge application server addresses;
  • An identifier selection module 12 configured to select a target data network access identifier
  • the address selection module 13 is configured to use the edge application server address having a mapping relationship with the target data network access identifier among the at least two edge application server addresses as the distribution edge application server address;
  • the rule generating module 14 is configured to generate an offloading rule for an intermediate user plane network element according to an offloading edge application server address.
  • the identifier selection module 12 may include: a first acquiring unit 121 and a first determining unit 122 .
  • the first acquiring unit 121 is configured to acquire the target edge application server address from at least two edge application server addresses;
  • the first determining unit 122 is configured to use the data network access identifier that has a mapping relationship with the address of the target edge application server as the target data network access identifier.
  • the identifier selection module 12 may include: a second acquiring unit 123 , a query unit 124 and a second determining unit 125 .
  • the second acquiring unit 123 is configured to acquire data network access identifiers respectively having a mapping relationship with at least two edge application server addresses, and obtain one or more data network access identifiers to be selected;
  • the query unit 124 is configured to query the load conditions of the edge anchor user plane network elements respectively corresponding to one or more data network access identifiers to be selected;
  • the second determining unit 125 is configured to determine a target data network access identifier among one or more data network access identifiers to be selected according to load conditions.
  • the identifier selection module 12 may include: a third acquiring unit 126 , a predicting unit 127 and a third determining unit 128 .
  • the third acquiring unit 126 is configured to acquire data network access identifiers respectively having a mapping relationship with at least two edge application server addresses, and obtain one or more data network access identifiers to be selected;
  • the prediction unit 127 is configured to obtain the predicted load average situation of the edge-anchor user plane network elements respectively corresponding to one or more data network access identifiers to be selected within the target time period;
  • the third determining unit 128 is configured to determine a target data network access identifier among one or more data network access identifiers to be selected according to the predicted load average condition.
  • the identifier selection module 12 may include: a polling unit 129 .
  • the polling unit 129 is configured to obtain data network access identifiers that have a mapping relationship with at least two edge application server addresses, and obtain one or more data network access identifiers to be selected;
  • the polling unit 129 is further configured to determine a target data network access identifier from one or more data network access identifiers to be selected according to a polling mechanism.
  • the above-mentioned network element device 1 may further include: a path establishing module 15 and a rule issuing module 16 .
  • a path establishment module 15 configured to establish an offload path between the intermediate user plane network element and the edge anchor user plane network element corresponding to the target data network access identifier
  • the rule issuing module 16 is configured to issue distribution rules to the intermediate user plane network element, so that the intermediate user plane network element forwards the service access request of the terminal device to access the distribution edge application server address to the edge anchor point based on the distribution rule and the distribution path
  • the user plane network element; the edge anchor user plane network element is used to forward the service access request to the edge application server corresponding to the distribution edge application server address.
  • step S103 for the implementation of specific functions of the path establishment module 15 and the rule delivery module 16, please refer to the description of step S103 in the above embodiment corresponding to FIG. 3 , which will not be repeated here.
  • the above-mentioned network element device 1 may further include: an address sending module 17 .
  • the address sending module 17 is configured to send the offload edge application server address to the edge application server discovery network element, so that the edge application server discovers the network element and sends the offload edge application server address to the terminal device.
  • step S103 for the specific function implementation of the address sending module 17, reference may be made to the description of step S103 in the above embodiment corresponding to FIG. 3 , which will not be repeated here.
  • FIG. 10 is a schematic structural diagram of a network element device provided in an embodiment of the present application.
  • the network element device can be a computer program (including program code) running on the network element equipment, for example, the network element device is an application software; the device can be used to execute the corresponding steps in the data processing method provided by the embodiment of the present application .
  • the network element device 2 may include: a receiving module 21 , an identifier selection module 22 , an address selection module 23 and a sending module 24 .
  • the receiving module 21 is used for the edge application server to discover the network element and receive the domain name system response message sent by the domain name system server; the domain name system response message includes at least two edge application server addresses;
  • An identifier selection module 22 configured to select a target data network access identifier
  • the address selection module 23 is configured to use the edge application server address having a mapping relationship with the target data network access identifier from at least two edge application server addresses as the offloading edge application server address;
  • the sending module 24 is configured to send the offloading edge application server address and the target data network access identifier to the session management network element, so that the session management network element generates the offloading rule of the intermediate user plane network element according to the offloading edge application server address, and establishes An offload path between the intermediate user plane network element and the edge anchor user plane network element corresponding to the target data network access identifier.
  • the network element device 2 may further include: a response sending module 25 .
  • the response sending module 25 is configured to send the address of the offloading edge application server to the terminal device after the offloading rule is generated and the offloading path is established.
  • the specific function implementation manner of the response sending module 25 can refer to the description of step S203 in the above embodiment corresponding to FIG. 5 , which will not be repeated here.
  • FIG. 11 is a schematic structural diagram of a network element device provided by an embodiment of the present application.
  • the network element device can be a computer program (including program code) running on the network element equipment, for example, the network element device is an application software; the device can be used to execute the corresponding steps in the data processing method provided by the embodiment of the present application .
  • the network element device 3 may include: a rule receiving module 31 .
  • the rule receiving module 31 is used for the intermediate user plane network element to receive the distribution rule issued by the session management network element; the distribution rule is generated according to the distribution edge application server address; The access request is forwarded to the edge anchor user plane network element corresponding to the target data network access identifier; the target data network access identifier is sent by the session management network element after receiving the domain name system message report sent by the edge application server discovery network element , selected to obtain; the domain name system message report contains at least two edge application server addresses, and the split edge application server address refers to the edge application server that has a mapping relationship with the target data network access identifier among the at least two edge application server addresses address.
  • the above-mentioned network element device 3 further includes: a request forwarding module 32 .
  • the request forwarding module 32 is configured to forward the service access request of the terminal device to access the offload edge application server address to the edge anchor user plane network element corresponding to the target data network access identifier based on the offload rule and the offload path, so that the edge anchor
  • the user plane network element forwards the service access request to the edge application server corresponding to the distribution edge application server address; the distribution path is the edge anchor user corresponding to the intermediate user plane network element established by the session management network element and the target data network access identifier Distribution path between plane NEs.
  • the specific function implementation manner of the request forwarding module 32 can refer to the description of step S302 in the above-mentioned embodiment corresponding to FIG. 6 , which will not be repeated here.
  • the request forwarding module 32 may include: a receiving unit 321 and a forwarding unit 322 .
  • the receiving unit 321 is configured to receive the target service access request sent by the terminal device; the target service access request carries the address of the target edge application server;
  • the forwarding unit 322 is configured to forward the target service access request to the target data network access identifier based on the offload rule and offload path if the edge application server address that is the same as the target edge application server address is found in the offload edge application server address.
  • the corresponding edge anchor user plane network element so that the edge anchor user plane network element forwards the target service access request to the edge application server corresponding to the address of the target edge application server.
  • the edge application servers corresponding to the above distribution edge application server addresses are all used to provide edge application services for terminal devices; the number of distribution edge application server addresses is at least two, and the at least two distribution edge application server addresses include the first distribution edge application server address.
  • the server address and the address of the second offloading edge application server; the second offloading edge application server address is the edge that is carried in the service access request initiated by the terminal device after the access to the edge application service fails through the first offloading edge application server address Application server address.
  • step S302 for specific function implementation manners of the receiving unit 321 and the forwarding unit 322, reference may be made to the description of step S302 in the above embodiment corresponding to FIG. 6 , which will not be repeated here.
  • FIG. 12 is a schematic structural diagram of a network element device provided by an embodiment of the present application.
  • the network element device 1000 may include: a processor 1001 , a network interface 1003 and a memory 1004 .
  • the network element device 1000 may further include: at least one communication bus 1002 .
  • the communication bus 1002 is used to realize connection and communication between these components.
  • the network interface 1003 may optionally include a standard wired interface and a wireless interface (such as a WI-FI interface).
  • the memory 1004 can be a high-speed RAM memory, or a non-volatile memory, such as at least one disk memory.
  • the memory 1004 may also be at least one storage device located away from the aforementioned processor 1001 .
  • the memory 1004 as a computer-readable storage medium may include an operating system, a network communication module, and a device control application program.
  • the network element device 1000 may be a session management network element.
  • the network interface 1003 can provide a network element for network communication; and the processor 1001 can be used to call the device control application program stored in the memory 1004, so that the network element device 1000 executes:
  • the domain name system message report sent by the edge application server to discover the network element; the domain name system message report includes at least two edge application server addresses;
  • network element device 1000 described in the embodiment of the present application may execute the description of the data processing method in the embodiment corresponding to FIG. 3 above, and details are not repeated here.
  • the description of the beneficial effect of adopting the same method will not be repeated here.
  • the embodiment of the present application also provides a computer-readable storage medium, and the above-mentioned computer-readable storage medium stores the computer program executed by the aforementioned network element device 1, and the above-mentioned computer
  • the program includes program instructions.
  • the above-mentioned processor executes the above-mentioned program instructions, it can execute the description of the above-mentioned data processing method in the embodiment corresponding to FIG. 3 above, so details will not be repeated here.
  • the description of the beneficial effect of adopting the same method will not be repeated here.
  • FIG. 13 is a schematic structural diagram of a network element device provided by an embodiment of the present application.
  • the network element device 2000 may include: a processor 2001 , a network interface 2003 and a memory 2004 .
  • the network element device 2000 may further include: at least one communication bus 2002 .
  • the communication bus 2002 is used to realize connection and communication between these components.
  • the network interface 2003 may optionally include a standard wired interface and a wireless interface (such as a WI-FI interface).
  • the memory 2004 can be a high-speed RAM memory, or a non-volatile memory, such as at least one disk memory.
  • the memory 2004 may also be at least one storage device located away from the aforementioned processor 2001 .
  • the memory 2004 as a computer-readable storage medium may include an operating system, a network communication module, and a device control application program. In this embodiment of the application, the network element device 2000 can discover network elements for the edge application server.
  • the network interface 2003 can provide network communication elements; and the processor 2001 can be used to call the device control application program stored in the memory 2004, so that the network element device 2000 executes:
  • the domain name system response message includes at least two edge application server addresses;
  • the session management network element Send the offload edge application server address and the target data network access identifier to the session management network element, so that the session management network element generates the offload rule of the intermediate user plane network element according to the offload edge application server address, and establishes the intermediate user plane network element and An offload path between edge anchor user plane network elements corresponding to the target data network access identifier.
  • network element device 2000 described in the embodiment of the present application may execute the description of the data processing method in the embodiment corresponding to FIG. 5 above, and details are not repeated here.
  • the description of the beneficial effect of adopting the same method will not be repeated here.
  • the embodiment of the present application also provides a computer-readable storage medium, and the above-mentioned computer-readable storage medium stores the computer program executed by the aforementioned network element device 2, and the above-mentioned computer
  • the program includes program instructions.
  • the above-mentioned processor executes the above-mentioned program instructions, it can execute the description of the above-mentioned data processing method in the embodiment corresponding to FIG. 5 above, so details will not be repeated here.
  • the description of the beneficial effect of adopting the same method will not be repeated here.
  • FIG. 14 is a schematic structural diagram of a network element device provided by an embodiment of the present application.
  • the network element device 3000 may include: a processor 3001 , a network interface 3003 and a memory 3004 .
  • the network element device 3000 may further include: at least one communication bus 3002 .
  • the communication bus 3002 is used to realize connection and communication between these components.
  • the network interface 3003 may optionally include a standard wired interface and a wireless interface (such as a WI-FI interface).
  • the memory 3004 may be a high-speed RAM memory, or a non-volatile memory, such as at least one disk memory.
  • the memory 3004 may also be at least one storage device located away from the aforementioned processor 3001 .
  • the memory 3004 as a computer-readable storage medium may include an operating system, a network communication module, and a device control application program.
  • the network element device 3000 may be an intermediate user plane network element.
  • the network interface 3003 can provide a network element for network communication; and the processor 3001 can be used to call the device control application program stored in the memory 3004, so that the network element device 3000 executes:
  • the offload rule is generated according to the address of the offload edge application server; the offload rule is used to forward the service access request of the terminal device to access the offload edge application server address to the edge anchor user plane network element corresponding to the target data network access identifier; the target data
  • the network access identifier is selected by the session management network element after receiving the domain name system message report sent by the edge application server to discover the network element; the domain name system message report contains at least two edge application server addresses, and the edge application server
  • the address refers to the edge application server address that has a mapping relationship with the target data network access identifier among the at least two edge application server addresses.
  • network element device 3000 described in the embodiment of the present application may execute the description of the data processing method in the embodiment corresponding to FIG. 6 above, and details are not repeated here.
  • the description of the beneficial effect of adopting the same method will not be repeated here.
  • the embodiment of the present application also provides a computer-readable storage medium, and the above-mentioned computer-readable storage medium stores the computer program executed by the aforementioned network element device 3, and the above-mentioned computer
  • the program includes program instructions.
  • the above-mentioned processor executes the above-mentioned program instructions, it can execute the description of the above-mentioned data processing method in the embodiment corresponding to FIG. 6 above, so details will not be repeated here.
  • the description of the beneficial effect of adopting the same method will not be repeated here.
  • the foregoing computer-readable storage medium may be the network element device provided in any of the foregoing embodiments or an internal storage unit of the foregoing network element device, for example, a hard disk or a memory of the network element device.
  • the computer-readable storage medium can also be an external storage device of the network element device, such as a plug-in hard disk equipped on the network element device, a smart memory card (smart media card, SMC), a secure digital (secure digital, SD) card, flash card, etc.
  • the computer-readable storage medium may also include both an internal storage unit of the network element device and an external storage device.
  • the computer-readable storage medium is used to store the computer program and other programs and data required by the network element device.
  • the computer-readable storage medium can also be used to temporarily store data that has been output or will be output.
  • the embodiment of the present application also provides a computer program product or computer program, where the computer program product or computer program includes computer instructions, and the computer instructions are stored in a computer-readable storage medium.
  • the processor of the network element device reads the computer instruction from the computer-readable storage medium, and the processor executes the computer instruction, so that the network element device executes the method provided by any one of the embodiments corresponding to FIG. 3 , FIG. 5 , and FIG. 6 above.
  • each flow and/or process of the method flow charts and/or structural diagrams can be implemented by computer program instructions or blocks, and combinations of processes and/or blocks in flowcharts and/or block diagrams.
  • These computer program instructions may be provided to a general purpose computer, special purpose computer, embedded processor, or processor of other programmable data processing equipment to produce a machine such that the instructions executed by the processor of the computer or other programmable data processing equipment produce a A device for realizing the functions specified in one or more steps of the flowchart and/or one or more blocks of the structural diagram.
  • These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to operate in a specific manner, such that the instructions stored in the computer-readable memory produce an article of manufacture comprising instruction means, the instructions
  • the device implements the functions specified in one or more blocks of the flowchart and/or one or more blocks of the structural schematic diagram.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby
  • the instructions provide steps for implementing the functions specified in one or more steps of the flowchart and/or one or more blocks in the structural illustration.

Abstract

提供一种数据处理方法、网元设备以及可读存储介质，该方法包括：获取至少两个边缘应用服务器地址的域名系统消息报告，然后选择目标数据网络接入标识符，将至少两个边缘应用服务器地址中，与目标数据网络接入标识符具有映射关系的边缘应用服务器地址，作为分流边缘应用服务器地址；再由会话管理网元根据分流边缘应用服务器地址生成中间用户面网元的分流规则。

Description

一种数据处理方法、网元设备以及可读存储介质
本申请基于申请号为：202110839104.1，申请日为2021年07月23日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本申请涉及通信技术领域，尤其涉及一种数据处理方法、网元设备以及可读存储介质。
背景技术
随着智能终端的普及和快速发展，网络边缘产生的数据量迅速增长，进一步推动了边缘计算(Edge Computing)的发展。
目前，在支持边缘计算的第五代移动通信技术(5th Generation Mobile Communication Technology，简称5G)中，终端设备(User Equipment，UE)可以通过边缘应用服务器(Edge Application Server，EAS)获得边缘应用服务(Edge Application Service)。在获得边缘应用服务之前，终端设备需要先发现合适的边缘应用服务器的IP(Internet Protocol)地址，现有的边缘应用服务器发现(EAS Discovery)方式是根据域名系统(Domain Name System，DNS)机制查询获得边缘应用服务器的IP地址。在这个过程中，5G核心网中的会话管理网元(Session Management Function，SMF)会根据查询获得的边缘应用服务器的IP地址生成分流规则，中间用户面网元(I-UPF，Intermediate User Plane Function)根据分流规则为终端设备配置分流路径，然后由边缘应用服务器发现网元(Edge Application Server Discovery Function，EASDF)将IP地址发送给终端设备，使得终端设备可以通过IP地址和分流路径访问到边缘应用服务器。但是，边缘应用服务可能对应有多个可用的IP地址，终端设备选择使用的IP地址是随机的，因此SMF需要为每个IP地址配置分流规则，并为I-UPF与所有IP地址相关联的L-PSA(Local Protocol Data Unit Session Anchor，本地协议数据单元会话锚点)UPF都建立分流路径，未被终端设备选择的IP地址对应的分流路径会被闲置，造成网络资源浪费。
发明内容
本申请实施例提供了一种数据处理方法、网元设备以及可读存储介质，可以减少网络资源浪费。
本申请实施例一方面提供了一种数据处理方法，包括：
会话管理网元接收边缘应用服务器发现网元发送的域名系统消息报告；域名系统消息报告包含至少两个边缘应用服务器地址；
会话管理网元选择目标数据网络接入标识符，将至少两个边缘应用服务器地址中，与目标数据网络接入标识符具有映射关系的边缘应用服务器地址，作为分流边缘应用服务器地址；
会话管理网元根据分流边缘应用服务器地址生成中间用户面网元的分流规则。
本申请实施例一方面提供了一种数据处理方法，包括：
边缘应用服务器发现网元接收域名系统服务器发送的域名系统响应消息；域名系统响应消息包含至少两个边缘应用服务器地址；
边缘应用服务器发现网元选择目标数据网络接入标识符，从至少两个边缘应用服务器地址中，将与目标数据网络接入标识符具有映射关系的边缘应用服务器地址，作为分流边缘应用服务器地址；
边缘应用服务器发现网元将分流边缘应用服务器地址和目标数据网络接入标识符发送给会话管理网元，以使会话管理网元根据分流边缘应用服务器地址生成中间用户面网元的分流规则，建立中间用户面网元与目标数据网络接入标识符对应的边缘锚点用户面网元之间的分流路径。
本申请实施例一方面提供了一种数据处理方法，包括：
中间用户面网元接收会话管理网元下发的分流规则；
分流规则是根据分流边缘应用服务器地址生成的；分流规则用于将终端设备访问分流边缘应用服务器地址的业务访问请求转发至目标数据网络接入标识符对应的边缘锚点用户面网元；目标数据网络接入标识符是由会话管理网元在接收到边缘应用服务器发现网元发送的域名系统消息报告后，所选择得到的；域名系统消息报告包含至少两个边缘应用服务器地址，分流边缘应用服务器地址是指至少两个边缘应用服务器地址中，与目标数据网络接入标识符具有映射关系的边缘应用服务器地址。
本申请实施例一方面提供了一种网元装置，包括：
报告接收模块，用于会话管理网元接收边缘应用服务器发现网元发送的域名系统消息报告；域名系统消息报告包含至少两个边缘应用服务器地址；
标识符选择模块，用于选择目标数据网络接入标识符；
地址选择模块，用于将至少两个边缘应用服务器地址中，与目标数据网络接入标识符具有映射关系的边缘应用服务器地址，作为分流边缘应用服务器地址；
规则生成模块，用于根据分流边缘应用服务器地址生成中间用户面网元的分流规则。
本申请实施例一方面提供了一种网元装置，包括：
接收模块，用于边缘应用服务器发现网元接收域名系统服务器发送的域名系统响应消息；域名系统响 应消息包含至少两个边缘应用服务器地址；
标识符选择模块，用于选择目标数据网络接入标识符；
地址选择模块，用于从至少两个边缘应用服务器地址中，将与目标数据网络接入标识符具有映射关系的边缘应用服务器地址，作为分流边缘应用服务器地址；
发送模块，用于将分流边缘应用服务器地址和目标数据网络接入标识符发送给会话管理网元，以使会话管理网元根据分流边缘应用服务器地址生成中间用户面网元的分流规则，建立中间用户面网元与目标数据网络接入标识符对应的边缘锚点用户面网元之间的分流路径。
本申请实施例一方面提供了一种网元装置，包括：
规则接收模块，用于中间用户面网元接收会话管理网元下发的分流规则；分流规则是根据分流边缘应用服务器地址生成的；分流规则用于将终端设备访问分流边缘应用服务器地址的业务访问请求转发至目标数据网络接入标识符对应的边缘锚点用户面网元；目标数据网络接入标识符是由会话管理网元在接收到边缘应用服务器发现网元发送的域名系统消息报告后，所选择得到的；域名系统消息报告包含至少两个边缘应用服务器地址，分流边缘应用服务器地址是指至少两个边缘应用服务器地址中，与目标数据网络接入标识符具有映射关系的边缘应用服务器地址。
本申请实施例一方面提供了一种网元设备，包括：处理器、存储器、网络接口；
上述处理器与上述存储器、上述网络接口相连，其中，上述网络接口用于提供数据通信网元，上述存储器用于存储计算机程序，上述处理器用于调用上述计算机程序，以使网元设备执行本申请实施例中的方法。
本申请实施例一方面提供了一种计算机可读存储介质，上述计算机可读存储介质中存储有计算机程序，上述计算机程序适于由处理器加载并执行本申请实施例中的方法。
本申请实施例一方面提供了一种计算机程序产品或计算机程序，该计算机程序产品或计算机程序包括计算机指令，该计算机指令适于由处理器加载并执行本申请实施例中的方法。
本申请实施例中，会话管理网元获取至少两个边缘应用服务器地址，然后，可以进一步选择目标数据网络接入标识符，将至少两个边缘应用服务器地址中，与目标数据网络接入标识符具有映射关系的边缘应用服务器地址，作为分流边缘应用服务器地址，再由会话管理网元根据分流边缘应用服务器地址生成中间用户面网元的分流规则。由此可见，本申请实施例中，会话管理网元不会为所有边缘应用服务器地址生成分流规则，而是通过选择机制确定出分流边缘应用服务器地址，后续中间用户面网元能够根据分流规则将终端设备访问分流边缘应用服务器地址的业务访问请求转发至对应的分流路径上，其中，该分流路径可以是会话管理网元建立的中间用户面网元与目标数据网络接入标识符对应的边缘锚点用户面网元之间的分流路径，由此可见，会话管理网元不用再建立所有边缘应用服务器地址相关联的分流路径，可以减少分流路径会被闲置的情况发生，从而可以降低网络资源的浪费。
附图说明
为了更清楚地说明本申请实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是本申请实施例提供的一种系统架构示意图；
图2a-图2c是本申请实施例提供的一种数据处理方法的场景示意图；
图3是本申请实施例提供的一种数据处理方法的流程示意图；
图4a-图4c是本申请实施例提供的一种选择目标数据网络接入标识符的场景示意图；
图5是本申请实施例提供的一种数据处理方法的流程示意图；
图6是本申请实施例提供的一种数据处理方法的流程示意图；
图7是本申请实施例提供的一种边缘应用服务器发现的交互示意图；
图8是本申请实施例提供的一种分流路径的网络架构示意图；
图9是本申请实施例提供的一种网元装置的结构示意图；
图10是本申请实施例提供的一种网元装置的结构示意图；
图11是本申请实施例提供的一种网元装置的结构示意图；
图12是本申请实施例提供的一种网元设备的结构示意图；
图13是本申请实施例提供的一种网元设备的结构示意图；
图14是本申请实施例提供的一种网元设备的结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技 术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
请参见图1，是本申请实施例提供的一种系统架构示意图。该系统架构可以应用于支持边缘计算的业务场景中。边缘计算是指在靠近物或数据源头的网络边缘侧，融合网络、计算存储、应用核心能力的平台，就近提供边缘智能服务，满足行业数字化在敏捷联接、实时业务、数据优化、应用智能安全与隐私保护等方面的关键需求。边缘计算使运营商和第三方服务能够靠近终端设备的接入点进行托管，从而通过减少传输网络上的端到端延迟和负载来实现高效的服务能力。
第五代移动通信技术(简称5G)是具有高速率、低时延和大连接特点的新一代宽带移动通信技术，是实现人机物互联的网络基础设施。国际电信联盟(ITU)定义了5G应用中较为典型的场景，包括：增强移动宽带(Enhanced Mobile Broadband，eMBB)、超可靠低延迟通信(Ultra-relaible and Low Latency Communication，URLLC)、超可靠低延迟通信和海量机器通信(massive Machine Type of Communication，mMTC)、车联网(vehicle to everything，V2X)等。一方面，上述eMBB场景提供大流量移动宽带业务，如高速下载、高清视频、虚拟现实(Virtual Reality，VR)/增强现实(Augmented Reality，AR)等，这些业务的峰值速率通常超过10Gbps，带宽的要求则高达几十Gbps，故此，会对无线中传、回传移动网络造成巨大的压力。因此，这些业务需求需要将业务尽可能下沉至网络边缘，以实现业务的本地分流。另一方面，URLLC场景及V2X场景可提供超高可靠超低时延通信，如自动驾驶、工业控制、远程医疗等，其要求端到端99.999％的高可靠性以及端到端小于1ms的超低时延，因此，这些业务需求也需要将业务下沉至网络边缘，以减少网络传输和多级业务转发带来的网络时延。
上述可知，5G的推广增加了对边缘计算的需求，此外，边缘计算与5G结合使用可以帮助遇到突发且持续的流量激增情况的网络解决带宽、速度和安全问题。
如图1所示，该系统架构可以包括边缘数据中心100以及终端集群，终端集群可以包括：终端设备200a、终端设备200b、终端设备200c、…、终端设备200n，边缘数据中心100可以包括多个边缘应用服务器(EAS)，如边缘应用服务器100a、边缘应用服务器100b、…、边缘应用服务器100m。其中，终端集群之间可以存在通信连接，例如终端设备200a与终端设备200b之间存在通信连接，终端设备200a与终端设备200n之间存在通信连接。其中，边缘应用服务器之间可以存在通信连接，例如边缘应用服务器100a和边缘应用服务器100b之间存在通信连接。同时，终端集群中的任一终端设备可以与边缘数据中心100中的任一边缘应用服务器存在通信连接，例如终端设备200a与边缘应用服务器100a之间存在通信连接。其中，上述通信连接不限定连接方式，可以通过4G无线接入方式，也可以通过5G无线接入方式等，本申请在此不做限制。
需要说明的是，在移动通信中，如图1所示的系统架构还可以包括接入网、承载网(传输网)以及核心网，接入网中可以部署多个基站(如5G基站gNB)，主要负责终端设备在无线侧的接入与管理；承载网可以由一系列运营商的交换和路由设备组成，主要用于传输基站与核心网之间的控制信令与用户数据；核心网则可以部署一系列核心网网元(“网元”也可称为“网络功能”)，这些网元协同对终端设备进行鉴权、计费和移动性管理等，此处不对接入网和承载网进行展开描述。
为便于后续实施例的理解和说明，这里先对本申请实施例涉及到的主要核心网网元进行简要介绍，具体如下：
(1)SMF(Session Management Function，会话管理功能)：是5G基于服务架构的一个功能单元，在本申请实施例中，SMF也可以称为会话管理网元，其主要功能如下：
(a)负责会话建立、删除和更新；
(b)用户面选择与控制；
(c)UE IP(UE，User Equipment，即终端设备或用户设备；IP，Internet Protocol，即互联网协议)地址分配和管理；
(d)控制和管理UPF(User Plane Function，用户面功能)，可以向UPF下发各种策略执行业务流的处理。
(2)UPF(User Plane Function，用户面功能)：UPF是5G核心网中唯一的处理数据的模块，在本申请实施例中，UPF也可以称为用户面网元，其主要功能如下：
(a)负责移动核心网用户面的数据路由和转发，并与外部数据网络(Data Network，比如运营商业务、互联网或者第三方业务等)互连；
(b)支持UE业务数据的路由和转发；
(c)接受SMF控制和管理，依据SMF下发的各种策略执行业务流的处理。
(3)PCF(Policy Control Function，策略控制功能)：主要负责使用统一的策略框架来管理网络行为，并协同UDR(Unified Data Repository)中的用户信息，来执行相关的策略。在本申请实施例中，PCF也可以称为策略控制网元。
(4)EASDF(Edge Application Server Discovery Function，边缘应用服务器发现功能)：在本申请实 施例中，EASDF也可称为边缘应用服务器发现网元，其主要功能如下：
(a)向NRF(Network Repository Function，网络仓库功能)注册以进行EASDF的发现和选择；
(b)根据SMF的指示处理DNS(Domain Name System，域名系统)消息，包括：
(b1)接收来自于SMF的DNS消息处理规则；
(b2)交换来自UE的DNS消息；
(b3)将DNS消息转发到C-DNS服务器(Central DNS server，中心域名系统服务器)或L-DNS服务器(Local DNS server，本地域名系统服务器)以进行DNS查询；
(b4)将ECS(EDNS Client Subnet，EDNS客户端子网，EDNS即Extension Mechanisms for DNS，是一种扩展DNS机制)选项添加到针对一个FQDN(Fully Qualified Domain Name，全限定域名/完全合格域名/全称域名)的DNS查询中；
(b5)将EASDF相关信息通知给SMF；
(b6)如果使用DoT(DNS over TLS，使用TLS协议来传输DNS协议)、DoH(DNS over HTTPS，使用HTTPS协议来传输DNS协议)或DNS over DTLS(使用数据包传输层安全性协议(即Datagram Transport Layer Security，DTLS)来传输DNS协议)，则终止DNS安全。
需要说明的是，UPF可以通过数据面接口与SMF进行交互。EASDF可以通过数据面接口与PSA(PDU Session Anchor，即PDU会话锚点)UPF连接，可用于传输与UE交换的DNS消息。此外，可以在一个PLMN(Public Land Mobile Network，公共陆地移动网络)内部署多个EASDF实例，且5G核心网的网络功能与EASDF之间的交互发生在一个PLMN内。
在5G网络下，假设某个终端设备(如终端设备200a、终端设备200b、终端设备200c、以及终端设备200n中的任意一个)希望访问移动通信网外部的数据网络(Data Network，DN)，例如Internet、WAP、企业内部网等，则该终端设备可以发起访问请求，基站可以将其请求的业务流转发至5G核心网(5G Core，可简称为5GC)中的核心网网元UPF，再通过核心网网元UPF转发后，发送到外部数据网络，5G核心网中的其它核心网网元则负责处理信令，控制整个流程。
进一步，为了获得更高效的服务交付，可以采用边缘计算来满足不同的业务需求。需要说明的是，在边缘计算场景下，一个边缘应用服务可能由通常部署在不同站点的多个边缘应用服务器(如图1中的边缘应用服务器100a、边缘应用服务器100b、边缘应用服务器100m)提供服务，这些承载边缘应用服务的多个边缘应用服务器可能使用单个IP地址或不同的IP地址。通常情况下，某个应用可能部署在中心的应用服务器中，也可能部署在边缘应用服务器中。要想把该应用的业务流路由到边缘应用服务器(Edge Application Service)，终端设备需要知道为该应用提供服务的边缘应用服务器的IP地址，终端设备可以进行发现以获取合适的边缘应用服务器(例如最近的一个边缘应用服务器)的IP地址，以便流量可以被本地路由到该边缘应用服务器，并且可以优化服务延迟、流量路由路径和用户服务体验。基于此，边缘应用服务器发现是终端设备使用域名系统查找合适的边缘应用服务器的IP地址的过程。其中，域名系统(DNS)是互联网的一项服务，它作为将域名和IP地址相互映射的一个分布式数据库，能够使用户更方便地访问互联网。
5G核心网支持终端设备和数据网络间的PDU连接业务，PDU连接业务通过PDU会话(即协议数据单元会话)的形式来体现，一个PDU会话是指一个终端设备与数据网络之间进行通讯的过程，也就是说，PDU会话建立后，也就建立起了该终端设备和数据网络之间的数据传输通道。需要说明的是，所有核心网数据必须经过核心网网元I-UPF转发，才可以流向外部网络，换言之，一个PDU会话对应的数据传输通道的连接实际是终端设备连接核心网网元I-UPF，核心网网元I-UPF同时连接数据网络。多个PDU会话建立时，均要通过核心网网元I-UPF来完成数据转发，为了缓解核心网的数据传输压力，当终端设备的新的PDU会话建立需要访问数据网络时，核心网网元SMF和核心网网元EASDF可以进行多次交互，使得核心网网元EASDF可以正确的处理DNS请求和DNS响应消息，并使得核心网网元SMF可以在核心网网元I-UPF上插入核心网网元L-PSA UPF来建立分流路径并配置分流规则，来实现数据流量的本地分流，核心网网元L-PSA UPF可以下沉到网络边缘部署，可以减少传输时延，从而缓解核心网的数据传输压力，提升网络数据处理效率。
可以理解，对于超大带宽的业务，通过移动边缘计算(如图1所示的边缘应用服务器)的就近部署，使超大带宽流量就近处理，可以极大减轻大带宽对骨干网络的冲击，典型场景如体育馆比赛直播、演唱会直播、移动内容分发等。
需要说明的是，核心网网元SMF对不同边缘应用服务器的IP地址配置的分流路径可能不同，核心网网元I-UPF上可能为一个PDU会话插入多个核心网网元L-PSA UPF来进行本地分流。但是终端设备获取边缘应用服务时仅需占用一个IP地址对应的分流路径，造成了网络资源的浪费。因此，在本申请实施例中，在获取到至少两个合适的边缘应用服务器的IP地址后，可以通过核心网网元SMF或者核心网网元EASDF来选择目标数据网络接入标识符(DN Access Identifier，DNAI)，然后从至少两个合适的边缘应用服务器 的IP地址中，选择与该目标数据网络接入标识符具有映射关系的边缘应用服务器的IP地址，作为分流边缘应用服务器的IP地址。其中，数据网络接入标识符DNAI是指用户面访问一个或多个部署应用程序的DN的标识符。然后，核心网网元SMF仅需根据该分流边缘应用服务器的IP地址生成核心网网元I-UPF的分流规则，并选择目标数据网络接入标识符对应的核心网网元L-PSA UPF和核心网网元I-UPF建立分流边缘应用服务器的IP地址关联的分流路径。可以理解的是，核心网网元EASDF也只需要将分流边缘应用服务器的IP地址发送给终端设备，终端设备可以通过分流边缘应用服务器的IP地址来访问对应的边缘应用服务器，获取边缘应用服务。
可以理解的是，上述可用于边缘计算的终端设备可以包括民用、商用、工业、军工等领域的终端应用产品，如智能手机、平板电脑、笔记本电脑、掌上电脑、移动互联网设备(mobile internet device，MID)、可穿戴设备(例如智能手表、智能手环等)、智能电脑、智能车载、智能家居、无人机、ATM机、摄像头、红绿灯、发电机或各类型的传感器等。边缘应用服务器可以是独立的物理服务器，也可以是多个物理服务器构成的服务器集群或者分布式系统，还可以是提供云数据库、云服务、云计算、云函数、云存储、网络服务、云通信、中间件服务、域名服务、安全服务、CDN、以及大数据和人工智能平台等基础云计算服务的云服务器。其中，终端设备和边缘应用服务器可以通过有线或无线方式进行直接或间接地连接，本申请实施例在此不做限制。
请一并参见图2a-图2c，是本申请实施例提供的一种数据处理方法的场景示意图，该数据处理方法的实现过程主要在5G核心网内进行。本申请实施例以一个终端设备发起一个协议数据单元会话以获取边缘应用服务为例进行说明，如图2a所示，假设终端设备301(可以为上述图1所示的终端集群中的任一终端设备)向核心网300发起一个协议数据单元会话建立请求3001(即上述图1所对应实施例中的PDU会话建立请求)，会话管理网元300a(即上述图1所对应实施例中的核心网网元SMF)可以响应该协议数据单元会话建立请求3001，通过策略控制网元(即上述图1所对应实施例中的核心网网元PCF)提供的PDU会话相关策略信息获取到边缘应用服务器部署信息，进而按照相关规则选择对应的边缘应用服务器发现网元(即上述图1所对应实施例中的核心网网元EASDF)，假设会话管理网元300a选择了边缘应用服务器发现网元300b，则会话管理网元300a和边缘应用服务器发现网元300b之间可以建立连接。在会话管理网元300a和边缘应用服务器发现网元300b建立连接并完成协议数据单元会话建立的相关数据交互后，终端设备301可以发起域名系统查询请求3002，其中，域名系统查询请求3002用于查询可以获取提供终端设备301所需边缘应用服务的边缘应用服务器地址(即上述图1所述的边缘应用服务器的IP地址)。边缘应用服务器发现网元300b将根据该域名系统查询请求3002和域名系统服务器302进行数据交互，然后接收域名系统服务器302发送的域名系统响应消息3003。域名系统响应消息3003中包含合适的边缘应用服务器地址集合3004，其中，边缘应用服务器地址集合3004可以包含至少两个边缘应用服务器地址。
如图2a所示，边缘应用服务器地址集合3004中可以包含边缘应用服务器地址A1、边缘应用服务器地址A2、边缘应用服务器地址B1、边缘应用服务器地址C1、边缘应用服务器地址C2。不同边缘应用服务器地址对应的边缘应用服务器可能会位于不同的边缘计算平台，因此所处的数据网络(即对应的数据网络接入标识符)可能会不同，为便于理解，假设边缘应用服务器地址A1、边缘应用服务器地址A2对应的数据网络接入标识符为A，边缘应用服务器地址B1对应的数据网络接入标识符为B，边缘应用服务器地址C1、边缘应用服务器地址C2对应的数据网络接入标识符为C。
进一步的，请一并参见图2b，边缘应用服务器发现网元300b会向会话管理网元300a发送携带该边缘应用服务器地址集合3004的域名系统消息报告3005。会话管理网元300a接收到域名系统消息报告3005后，需要先对边缘应用服务器地址集合3004中的边缘应用服务器地址进行选择，获取部分边缘应用服务器地址作为分流边缘应用服务器地址。如图2b所示，会话管理网元300a可以先选择目标数据网络接入标识符，然后会话管理网元300a会从至少两个边缘应用服务器地址中选择与该目标数据网络接入标识符具有映射关系的边缘应用服务器地址，作为分流边缘应用服务器地址。假设目标数据网络接入标识符为C，则分流边缘应用服务器地址集合3006中包含分流边缘应用服务器地址C1和分流边缘应用服务器地址C2，随后，会话管理网元300a会根据分流边缘应用服务器地址集合3006中的分流边缘应用服务器地址生成分流规则，下发给中间用户面网元300c(即上述图1所对应的实施例中的核心网网元I-UPF)。同时，会话管理网元300a可以在中间用户面网元300c上插入边缘锚点用户面网元300d(即上述图1所对应的实施例中的核心网网元L-PSA UPF)，其中，边缘锚点用户面网元300d是目标数据网络接入标识符对应的边缘锚点用户面网元，即会话管理网元300a可以建立中间用户面网元300c与边缘锚点用户面网元300d之间的分流路径，该分流路径用于对分流边缘应用服务器地址C1和分流边缘应用服务器地址C2对应的业务流进行分流，换言之，终端设备访问分流边缘应用服务器地址C1或者分流边缘应用服务器地址C2对应的边缘应用服务器，均可以通过该分流路径实现。
进一步地，请一并参见图2c，在分流规则下发以及分流路径建立完以后，边缘应用服务器发现网元300b会将分流边缘应用服务器地址集合3006中的分流边缘应用服务器地址C1和分流边缘应用服务器地 址C2一并下发给终端设备301，终端设备301可以从分流边缘应用服务器地址集合3006中任选一个分流边缘应用服务器地址作为业务访问地址，去访问该分流边缘应用服务器地址对应的边缘应用服务器，以获得边缘应用服务。假设分流边缘应用服务器地址C1对应边缘应用服务器303，则终端设备301携带分流边缘应用服务器地址C1的业务访问请求到达中间用户面网元300c后，其中，业务访问请求用于获取边缘应用服务，中间用户面网元300c识别到该业务访问请求携带分流边缘应用服务器地址C1，即可根据分流规则以及分流路径将该业务访问请求转发至边缘锚点用户面网元300d，最后被边缘锚点用户面网元300d发送至边缘应用服务器303。可以理解的是，如果终端设备301对边缘应用服务器303的访问失败后，可以将分流边缘应用服务器地址C2作为业务访问地址，重新发起携带分流边缘应用服务器地址C2的业务访问请求，该携带分流边缘应用服务器地址C2的业务访问请求到达中间用户面网元300c后，该业务访问请求同样会被中间用户面网元300c转发至边缘锚点用户面网元300d，随后，该业务访问请求会被边缘锚点用户面网元300d转发至分流边缘应用服务器地址C2对应的边缘应用服务器。
需要说明的是，图2a-图2c所示的数据处理方法中仅体现了与本申请实施例具有密切关系的核心网网元(包括SMF、EASDF、I-UPF和L-PSA UPF)，实际业务场景中还会涉及到其它的核心网网元，例如AMF(接入和移动性管理功能)、基站、PCF等，本申请实施例不进行展开。
请参见图3，图3是本申请实施例提供的一种数据处理方法的流程示意图。该数据处理方法可以由会话管理网元(SMF)执行。如图3所示，该数据处理方法至少可以包括以下步骤S101-步骤S103：
步骤S101，会话管理网元接收边缘应用服务器发现网元发送的域名系统消息报告；域名系统消息报告包含至少两个边缘应用服务器地址。
具体的，终端设备要启动一个边缘应用服务EAS，需要先知道为该边缘应用服务提供服务的边缘应用服务器的边缘应用服务器地址，终端设备的域名系统查询请求(DNS Query)发送至边缘应用服务器发现网元后，边缘应用服务器发现网元可以向域名系统服务器查询合适的边缘应用服务器地址。域名系统服务器响应边缘应用服务器发现网元的域名系统查询请求后，可以将至少两个边缘应用服务器地址告知给边缘应用服务器发现网元。其中，边缘应用服务器地址可为网络之间互联的协议(Internet Protocol，IP)地址以及其他任意一种能够用于标识边缘应用服务器中节点的信息，比如IP地址。可以理解的是，至少两个边缘应用服务器地址分别对应的边缘应用服务器可以单独为终端设备提供该边缘应用服务。
步骤S102，会话管理网元选择目标数据网络接入标识符，将至少两个边缘应用服务器地址中，与目标数据网络接入标识符具有映射关系的边缘应用服务器地址，作为分流边缘应用服务器地址。
具体的，至少两个边缘应用服务器的边缘应用服务器地址对应的数据网络接入标识符可以不同。其中，数据网络接入标识符(DN Access Identifier，DNAI)是指用户面访问一个或多个应用程序部署的数据网络DN的标识符。一个数据网络接入标识符可以对应一个或者多个边缘锚点用户面网元(L-PSA UPF)，不同数据网络接入标识符对应的边缘锚点用户面网元可以不同。同一数据网络接入标识符对应的边缘应用服务器地址的分流，可以通过该数据网络接入标识符对应的边缘锚点用户面网元实现。因此，可以从至少两个边缘应用服务器地址中，仅将目标数据网络接入标识符对应的边缘应用服务器地址，作为分流边缘应用服务器地址。
具体的，在本申请实施例的方法执行之前，可以先将边缘应用服务器地址和数据网络接入标识之间的映射关系写入预配置信息表中，然后会话管理网元接收到至少两个边缘应用服务器地址时，可以根据预配置信息表，在该预配置信息表中查找每个边缘应用服务器地址具有映射关系的数据网络接入标识符，作为待选择数据网络接入标识符，然后从待选择数据网络接入标识符中根据事先设定的选择规则获取目标数据网络接入标识符。其中，选择规则可以是随机选择、轮流选择、负荷分担等等。
步骤S103，会话管理网元根据分流边缘应用服务器地址生成中间用户面网元的分流规则。
具体的，分流规则又可以叫分流策略，会话管理网元通过配置各种分流策略来控制中间用户面网元执行业务流的处理。
可选的，会话管理网元根据分流边缘应用服务器地址生成分流规则后，可以建立中间用户面网元与目标数据网络接入标识符对应的边缘锚点用户面网元之间的分流路径；然后会话管理网元可以向中间用户面网元下发分流规则，中间用户面网元基于分流规则以及分流路径将终端设备访问分流边缘应用服务器地址的业务访问请求转发至边缘锚点用户面网元；然后，边缘锚点用户面网元可以将业务访问请求转发至分流边缘应用服务器地址对应的边缘应用服务器。可以理解的是，一个目标数据网络接入标识符可以对应一个或多个边缘锚点用户面网元。会话管理网元可以在中间用户面网元上可以配置与该边缘锚点用户面网元对应的UL CL(Uplink classifier，上行分类器)来提供能力接口支持分流规则。分流规则中包含流量检测和流量转发规则，分流边缘应用服务器地址对应的分流规则可以配置为将目的地址为分流边缘应用服务器地址的流量分流到边缘锚点用户面网元，并最终发送到边缘应用服务器。UL CL可以根据流量检测和流量转发规则向边缘锚点用户面网元转发终端设备的业务流。UL CL配置完成，中间用户面网元和边缘锚点用户面网元之间的分流路径建立完成。
可选的，会话管理网元在分流路径建立好且成功下发分流规则后，可以将分流边缘应用服务器地址发送给边缘应用服务器发现网元，然后边缘应用服务器发现网元将分流边缘应用服务器地址发送给终端设备，使得终端设备可以从分流边缘应用服务器地址中任选一个分流边缘应用服务器地址作为业务访问地址，终端设备对该业务访问地址的业务访问请求会通过上述分流路径发送至该业务访问地址对应的边缘应用服务器。
进一步地，为便于理解上述步骤S102中目标数据网络接入标识符的选择过程，请一并请参见图4a-图4c，图4a-图4c是本申请实施例提供的一种选择目标数据网络接入标识符的场景示意图。假设会话管理网元获取到的边缘应用服务器地址集合400中包含边缘应用服务器地址A1、边缘应用服务器地址A2、边缘应用服务器地址B1、边缘应用服务器地址C1、边缘应用服务器地址C2。
一个可行的实施例中，会话管理网元选择目标数据网络接入标识符的具体过程可以为：会话管理网元从至少两个边缘应用服务器地址中，获取目标边缘应用服务器地址；然后会话管理网元将与目标边缘应用服务器地址具有映射关系的数据网络接入标识符，作为目标数据网络接入标识符。如图4a所示，会话管理网元可以从边缘应用服务器地址集合400中随机选取一个边缘应用服务器地址，比如通过随机函数获取到边缘应用服务器地址A2(即目标边缘应用服务器地址)，随后，会话管理网元可以确定与边缘应用服务器地址A2具有映射关系的数据网络接入标识符为数据网络接入标识符A，然后，会话管理网元可以将数据网络接入标识符A作为目标数据网络接入标识符。
一个可行的实施例中，会话管理网元选择目标数据网络接入标识符的具体过程可以为：会话管理网元获取与至少两个边缘应用服务器地址分别具有映射关系的数据网络接入标识符，得到一个或多个待选择数据网络接入标识符；会话管理网元查询一个或多个待选择数据网络接入标识符分别对应的边缘锚点用户面网元的负载情况；会话管理网元根据负载情况在一个或多个待选择数据网络接入标识符中，确定目标数据网络接入标识符。如图4b所示，会话管理网元依次查询每个边缘应用服务器地址具有映射关系的数据网络接入标识，得到待选择数据网络接入标识符集合401，该待选择数据网络接入标识符集合401包含待选择数据网络接入标识符A、待选择数据网络接入标识符B以及待选择数据网络接入标识符C。然后，会话管理网元可以找到待选择数据网络接入标识符A对应的边缘锚点用户面网元402a，待选择数据网络接入标识符B对应的边缘锚点用户面网元402b和待选择数据网络接入标识符C对应的边缘锚点用户面网元402c，然后可以通过查询历史分流规则以及当前分流路径连接状态等方法，来确定每个边缘锚点用户面网元对应的负载情况，然后进行比较，最后选择负载情况最优的边缘锚点用户面网元对应的待选择数据网络接入标识符作为目标数据网络接入标识符。
一个可行的实施例中，会话管理网元选择目标数据网络接入标识符的具体过程可以为：会话管理网元获取与至少两个边缘应用服务器地址分别具有映射关系的数据网络接入标识符，得到一个或多个待选择数据网络接入标识符；会话管理网元可以获取一个或多个待选择数据网络接入标识符分别对应的边缘锚点用户面网元在目标时间段内的预测平均负载情况；然后根据预测平均负载情况在一个或多个待选择数据网络接入标识符中，确定目标数据网络接入标识符。即会话管理网元可以通过查询边缘锚点用户面网元对应的预测平均负载情况，其中，预测平均负载情况是指在目标时间段内(即未来时间段内，比如接下来十分钟，接下来一小时等等)边缘锚点用户面网元的平均负载情况，然后，选择预测平均负载情况最优的边缘锚点用户面网元对应的待选择数据网络接入标识符作为目标数据网络接入标识符。
一个可行的实施例中，会话管理网元选择目标数据网络接入标识符的具体过程可以为：会话管理网元获取与至少两个边缘应用服务器地址分别具有映射关系的数据网络接入标识符，得到一个或多个待选择数据网络接入标识符；会话管理网元根据轮询机制，从一个或多个待选择数据网络接入标识符中，确定目标数据网络接入标识符。如图4c所示，会话管理网元中可以包含一个轮询表集合403，该轮询表集合403中包含多个轮询表，如轮询表404，一个轮询表中包含具有轮询序列的待选择数据网络接入标识符以及上次被选择的目标数据网络接入标识符标记。如图4c所示，会话管理网元会对轮询表集合403进行查询，获取待选择数据网络接入标识符集合401对应的轮询表404。轮询表404中的轮询序列为A→B→C→A…，此时，目标数据网络接入标识符标记405标记的待选择数据网络接入标识符为待选择数据网络接入标识符B，说明上次被选择的目标数据网络接入标识符为待选择数据网络接入标识符B。因此，会话管理网元会根据轮询序列，将待选择数据网络接入标识符B的下一位待选择数据网络接入标识符C作为目标数据网络接入标识符。可以理解的是，目标数据网络接入标识符选择完成后，会话管理网元可以更新目标数据网络接入标识符标记405，即用目标数据网络接入标识符标记405标记待选择数据网络接入标识符C。
通过本申请实施例提供的方法，会话管理网元在获取到包含至少两个边缘应用服务器地址的域名系统消息报告后，可以选择出目标数据网络接入标识符，然后可以从接收到的至少两个边缘应用服务器地址中，将和目标数据网络接入标识符具有映射关系的边缘应用服务器地址，作为分流边缘应用服务器地址，随后基于分流边缘应用服务器地址生成中间用户面网元的分流规则，会话管理网元仅会在中间用户面网元上为分流边缘应用服务器地址创建分流路径，不用再建立所有边缘应用服务器地址对应的分流路径，可以降低 网络资源的浪费，减轻核心网同时支持多条分流路径的负担。
进一步的，请参见图5，图5是本申请实施例提供的一种数据处理方法的流程示意图。该数据处理方法可以由边缘应用服务器发现网元(EASDF)执行。如图5所示，该数据处理方法至少可以包括以下步骤S201-步骤S203：
步骤S201，边缘应用服务器发现网元接收域名系统服务器发送的域名系统响应消息；域名系统响应消息包含至少两个边缘应用服务器地址。
具体的，边缘应用服务器发现网元在获取到终端设备发送的域名系统查询请求后，将与域名系统服务器进行交互，然后接收域名系统服务器发送的域名系统响应消息。其中，域名系统查询请求用于获取给终端设备准备启动的边缘应用服务提供服务的边缘应用服务器的边缘应用服务器地址。
步骤S202，边缘应用服务器发现网元选择目标数据网络接入标识符，从至少两个边缘应用服务器地址中，将与目标数据网络接入标识符具有映射关系的边缘应用服务器地址，作为分流边缘应用服务器地址。
具体的，边缘应用服务器发现网元在接收到域名系统响应消息后，会先选择目标数据网络接入标识符，然后根据该目标数据网络接入标识符对域名系统响应消息中的至少两个边缘应用服务器地址进行选择，确定分流边缘应用服务器地址。可以理解的是，边缘应用服务器发现网元选择目标数据网络接入标识符，从所述至少两个边缘应用服务器地址中，将与目标数据网络接入标识符具有映射关系的边缘应用服务器地址，作为分流边缘应用服务器地址的具体实现过程，和上述图3所对应实施例中会话管理网元选择分流边缘应用服务器地址的具体实现过程可以相同，换言之，上述图4a-图4c中对目标数据网络接入标识符的选择可以发生在边缘应用服务器发现网元中，这里不再进行赘述。
步骤S203，边缘应用服务器发现网元将分流边缘应用服务器地址和所述目标数据网络接入标识符发送给会话管理网元，以使会话管理网元根据所述分流边缘应用服务器地址生成中间用户面网元的分流规则，建立中间用户面网元与目标数据网络接入标识符对应的边缘锚点用户面网元之间的分流路径。
具体的，边缘应用服务器发现网元不再将域名系统响应消息中包含的所有边缘应用服务器地址发送给会话管理网元，而是仅将分流边缘应用服务器地址和目标数据网络接入标识符发送给会话管理网元，会话管理网元不需要再对接收到的分流边缘应用服务器地址进行选择，直接根据和分流边缘应用服务器地址具有映射关系的目标数据网络接入标识符以及分流边缘应用服务器地址，生成中间用户面网元的分流规则，建立中间用户面网元与所述目标数据网络接入标识符对应的边缘锚点用户面网元之间的分流路径。然后边缘应用服务器发现网元在分流规则生成且分流路径建立后，将分流边缘应用服务器地址发送给终端设备。
采用本申请实施例提供的方法，目标数据网络接入标识符的选择过程可以由边缘应用服务器发现网元来实现，边缘应用服务器发现网元可以直接根据目标数据网络接入标识符来从域名系统响应消息包含的至少两个边缘应用服务器地址中选出分流边缘应用服务器地址，然后将该分流边缘应用服务器地址和目标数据网络接入标识符发送给会话管理网元。会话管理网元仅根据分流边缘应用服务器地址生成分流规则，并建立中间用户面网元和目标数据网络接入标识符对应的边缘锚点用户面网元之间的分流路径，可以降低网络资源的浪费，减轻核心网同时支持多条分流路径的负担。
进一步的，请参见图6，图6是本申请实施例提供的一种数据处理方法的流程示意图。该数据处理方法可以由中间用户面网元(I-UPF)执行。如图3所示，该数据处理方法至少可以包括以下步骤S301-步骤S303：
步骤S301，中间用户面网元接收会话管理网元下发的分流规则。
具体的，该分流规则是根据分流边缘应用服务器地址生成的，分流规则用于将终端设备访问分流边缘应用服务器地址的业务访问请求转发至目标数据网络接入标识符对应的边缘锚点用户面网元。其中，目标数据网络接入标识符是由会话管理网元在接收到边缘应用服务器发现网元发送的域名系统消息报告后，所选择得到的。其中，域名系统消息报告包含至少两个边缘应用服务器地址。其中，分流边缘应用服务器地址是指至少两个边缘应用服务器地址中，与目标数据网络接入标识符具有映射关系的边缘应用服务器地址。
步骤S302，中间用户面网元基于所述分流规则以及分流路径将终端设备访问分流边缘应用服务器地址的业务访问请求转发至所述目标数据网络接入标识符对应的边缘锚点用户面网元，以使边缘锚点用户面网元将业务访问请求转发至分流边缘应用服务器地址对应的边缘应用服务器。
具体的，分流路径是由会话管理网元建立的中间用户面网元与目标数据网络接入标识符对应的边缘锚点用户面网元之间的分流路径。
具体的，中间用户面网元基于分流规则以及分流路径将终端设备访问分流边缘应用服务器地址的业务访问请求转发至目标数据网络接入标识符对应的边缘锚点用户面网元的过程，可以为：中间用户面网元接收终端设备发送的目标业务访问请求，其中，目标业务访问请求中携带有目标边缘应用服务器地址。所述中间用户面网元若在分流边缘应用服务器地址中查找到和目标边缘应用服务器地址相同的边缘应用服务器地址，则基于分流规则以及分流路径将目标业务访问请求转发至目标数据网络接入标识符对应的边缘锚 点用户面网元，以使边缘锚点用户面网元将目标业务访问请求转发至目标边缘应用服务器地址对应的边缘应用服务器。换言之，中间用户面网元接收到终端设备的目标业务访问请求后，UL CL采用流过滤规则(例如检查终端设备发送的目标业务访问请求的目的IP地址/前缀)来决定是否将该目标业务访问请求转发至对应的边缘锚点用户面网元，如果确定目标业务访问请求发送至分流边缘应用服务器地址，则将该目标业务访问请求转发至边缘锚点用户面网元。
具体的，分流边缘应用服务器地址对应的边缘应用服务器用于为终端设备提供边缘应用服务；分流边缘应用服务器地址的数量为至少两个，至少两个分流边缘应用服务器地址包括第一分流边缘应用服务器地址和第二分流边缘应用服务器地址。其中，第二分流边缘应用服务器地址是在通过第一分流边缘应用服务器地址对边缘应用服务访问失败后，由终端设备再次发起的业务访问请求中所携带的边缘应用服务器地址。为便于理解，假设终端设备接收到可用的分流边缘应用服务器地址包括分流边缘应用服务器地址E1、分流边缘应用服务器地址E2和分流边缘应用服务器地址E3，终端设备可以随机获取一个分流边缘应用服务器地址，如分流边缘应用服务器地址E1作为目标边缘应用服务器地址，发起对该分流边缘应用服务器地址E1对应的边缘应用服务器的业务访问请求来获取边缘应用服务，但是由于网络等问题，该终端设备对分流边缘应用服务器地址E1对应的边缘应用服务器访问失败了，终端设备可以从接收到的未被选择的分流边缘应用服务器地址中，选择一个新的目标边缘应用服务器地址，比如分流边缘应用服务器地址E3，终端设备可以发起对该分流边缘应用服务器地址E3对应的边缘应用服务器的业务访问请求来获取边缘应用服务。
本申请实施例中，中间用户面网元上不再需要插入多个上行分类器建立多条与边缘应用服务器地址关联的分流路径，从而减少了网络资源的浪费。
进一步地，请参见图7，图7是本申请实施例提供的一种边缘应用服务器发现的交互示意图。如图7所示，整个交互过程主要涉及到终端设备UE、会话管理网元SMF、边缘应用服务器发现网元EASDF、域名系统DNS服务器、可插入上行分类器UL CL的用户面网元UPF(即中间用户面网元I-UPF)、本地PDU会话锚点L-PSA用户面网元UPF(即边缘锚点用户面网元L-PSA UPF)。如图7所示，交互过程包括：
步骤S401，EASDF向DNS服务器发送DNS查询请求(DNS Query)。
具体的，DNS查询请求是UE发送给EASDF的查询请求，是UE为获取能提供边缘应用服务的边缘应用服务器的IP地址发起的查询请求。EASDF可以在DNS Query消息中添加ECS选项，并将其发送到DNS服务器。
步骤S402，DNS服务器将DNS响应消息(DNS Responses)发送给EASDF。
具体的，EASDF可以从DNS服务器接收DNS Responses，并确定可以向UE发送DNS Response。DNS Response中可以包含多个能为UE提供所需边缘应用服务的边缘应用服务器的IP地址，即多个EAS IP地址。
步骤S403，EASDF向SMF发送DNS消息报告。
具体的，如果DNS响应消息中的EAS IP地址或FQDN(完全合格的域名)与SMF提供的报告条件匹配，则EASDF可以通过调用包含EAS信息的Neasdf_DNSContext_Notify(EASDF的DNS上下文通知服务)服务向SMF发送DNS消息报告。其中，DNS消息报告中包含了EASDF接收到的多个EAS IP地址。需要说明的是，根据DNS消息处理规则，EASDF此时不会向UE发送DNS响应消息，而是等待SMF指令(在步骤S406中)，即先缓存DNS响应消息。如无特别说明，本文件对EASDF提供的服务的名称，如Neasdf_DNSContext_Notify等，不做限定。
步骤S404，SMF响应DNS消息报告。
具体的，SMF调用Neasdf_DNSContext_Notify响应。
步骤S405，SMF根据目标数据网络接入标识符(DNAI)确定分流地址，生成对应的分流规则。
具体的，SMF获取到DNS消息报告中的EAS IP地址后，会选择一个DNAI作为目标DNAI，然后根据目标DNAI和EAS IP地址的映射关系，获取与目标DNAI具有映射关系的EAS IP地址作为分流边缘应用服务器地址(即上述图3所对应实施例中的分流边缘应用服务器地址)。目标DNAI的选择过程可以参见上述图3所对应实施例中步骤S102的具体描述，这里不再进行赘述。可选的，目标DNAI的选择过程也可以放在步骤S403中进行，此时EASDF向SMF发送DNS消息报告中只会包含目标DNAI和与目标DNAI具有映射关系的EAS IP地址。具体实现可以参见上述图5所对应实施例中的步骤S202，这里不再进行赘述。
然后，SMF可以基于分流边缘应用服务器地址生成分流规则，然后发送到I-UPF，分流规则的生成过程可以参见上述图3所对应实施例中步骤S103的描述，这里不再进行赘述。
S406，I-UPF和L-PSA UPF之间建立分流路径。
具体的，SMF会确定需要插入I-UPF的与目标DNAI对应的上行分类器UL CL，然后配置UL CL来建立I-UPF和L-PAS UPF之间的分流路径，具体可以参见上述图3所对应实施例中步骤S103的描述，这 里不再进行赘述。
步骤S407，SMF调用DNS消息处理规则，将DNS消息处理规则请求发送至EASDF。
具体的，SMF调用Neasdf_DNSContext_Update Request服务请求，将DNS消息处理规则请求发送至EASDF，其中，DNS消息处理规则用于指示EASDF向UE发送在步骤S403中缓存的DNS响应消息。
步骤S408：EASDF执行该DNS消息处理规则，并将响应消息发送给SMF。
具体的，EASDF调用Neasdf_DNSContext_Update Response响应SMF。
步骤S409：EASDF向UE发送包含分流边缘应用服务器地址的DNS响应消息。
具体的，EASDF向UE发送包含分流边缘应用服务器地址的DNS响应消息。UE可以访问分流边缘应用服务器来获取相应的边缘应用服务，UE获取边缘应用服务的过程可以参见上述图6所对应实施例中的步骤S303。
采用本申请实施例提供的方法，SMF可以将与目标DNAI具有映射关系的EAS IP地址作为分流边缘应用服务器地址，从而仅根据分流边缘应用服务器地址来生成分流规则，不再需要对DNS服务器查询到的所有可用的EAS IP地址建立分流路径，以避免未被终端设备选择的EAS IP地址相关联的分流路径会被闲置，从而可以降低网络资源的浪费。
进一步地，请参见图8，图8是本申请实施例提供的一种分流路径的网络架构示意图。如图8所示，该网络架构中涉及到终端设备801(User Equipment，UE)、接入网络802(Access Network，AN)、核心网的多个功能网元和中央数据网络803(Central DN)以及边缘数据网络804(EAS DN)。如图8所示，核心网的多个功能网元可以包括：可插入上行分类器(UL CL)的用户面功能805(即上述中间用户面网元I-UPF)、中心协议数据单元会话锚点用户面功能(Central Protocol Data Unit Session Anchor UPF，C-PSA UPF)806、本地协议数据单元会话锚点用户面功能807(即上述边缘锚点用户面网元L-PSA UPF)、接入与移动性管理功能808(Access and Mobility Management Function，AMF)、会话管理功能809(即上述会话管理网元)、网络开放功能810(Network Exposure Function，NEF)、边缘应用服务器发现功能811(即上述边缘应用服务器发现网元)、网络存储功能812(Network Repository Function，NRF)、策略控制功能813(Policy Control Function，PCF)、应用功能814(Application Function，AF)和统一数据管理815(Unified Data Management，UDM)。
核心网的功能网元可以提供服务化接口，其命名规则就是在功能体的名字前面加N。其中，服务化接口(Service-basedinterface)是类似微服务化架构的服务注册和服务发现来实现的功能体对外暴露的接口，这种接口只针对于单个功能体，而其他的功能体通过该功能体暴露的接口与此功能体进行交互，实际上这种机制提供了一种多对一访问的机制，并且由于采用服务注册和服务发现，相互之间无需相互知道对方地址即可访问。如图8所示，接入与移动管理功能808提供服务化接口8080(可称为Namf)，会话管理功能809提供服务化接口8090可称为Nsmf)，网络开放功能810提供服务化接口8100(可称为Nnef)，边缘应用服务器发现功能811提供服务化接口8110(可称为Neasdf)，网络存储功能812提供服务化接口8120(可称为Nnrf)，策略控制功能813提供服务化接口8130(可称为Npcf)，应用功能814提供服务化接口8140(可称为Naf)，统一数据管理815提供服务化接口8150(可称为Nudm)。功能网元通过服务化接口和其他功能网元进行交互。
网络架构中也可以包含参考点，参考点(reference point)类似于传统接口，就是两个不同功能体之间相互约定的互访问接口。两个功能体之间的参考点一般可以通过一个或更多的服务化接口来代替，从而提供完全相同却更灵活扩展性更好的实现，用户功能块之间的通信。如图8所示，参考点N1是终端设备801和接入与移动管理功能808之间的接口；参考点N2是接入网络802和接入与移动管理功能808之间的接口；参考点N3是接入网络802和可插入上行分类器的用户面功能805之间的接口，可以采用GTP-U(一种隧道传输协议)协议进行用户数据的隧道传输；参考点N4是会话管理功能809和可插入上行分类器的用户面功能805之间的接口，也是会话管理功能809和中心协议数据单元会话锚点用户面功能806之间的接口，且也是会话管理功能809和本地协议数据单元会话锚点用户面功能807之间的接口；N6参考点是中心协议数据单元会话锚点用户面功能806和中央数据网络803之间的接口，也是本地协议数据单元会话锚点用户面功能807和边缘数据网络804之间的接口，可支持专线或L2/L3层隧道，可基于IP地址与DN网络通信；N9参考点是中心协议数据单元会话锚点用户面功能806、本地协议数据单元会话锚点用户面功能807分别和可插入上行分类器的用户面功能805之间的接口。
可以理解的是，服务化接口和参考点是5G架构所引入的两种不同的网络实体之间的模型化交互方式，通过对网络功能块和网络实体之间的接口和连接的灵活的定义，来实现5G网络对于多样的、特定的服务类型在各个协议层的灵活的处理方法和处理流程的实现，根据上述网络架构，终端设备801可以接入边缘应用服务器EAS所在的边缘数据网络804。
一个可行的实施例中，如图8所示，EASDF可以向DNS服务器查询UE可用的边缘应用服务器的IP地址，当EASDF接收到多个IP地址后，先将多个IP地址发送给SMF。SMF接收到多个IP地址时，会根 据预配置的信息，确定每个IP地址与DNAI的映射关系，例如：DNAI#1:IP#1,IP#2；DNAI#2:IP#3,IP#4,IP#5，即DNAI#1和IP#1、IP#2具有映射关系，DNAI#2和IP#3、IP#4、IP#5具有映射关系。SMF可以根据IP地址与DNAI的映射关系来进一步确定所选择的IP地址。因为DNAI会影响I-UPF和L-PSA UPF的选择。不同的DNAI通常会对应不同的L-PSA UPF，所以当SMF接收到的业务IP地址对应多个DNAI时，SMF会选择一个目标DNAI，然后选择对应目标DNAI的IP地址作为分流地址，这样在建立用户面分流路径时，只需选择支持该目标DNAI的L-PSA UPF来建立分流路径。SMF可以选择对应于该目标DNAI的所有IP地址，将这些IP地址均作为UE的分流地址(即上述所说的分流边缘应用服务器地址，这些IP地址均会与建立的分流路径关联)，然后SMF将分流地址发送给EASDF，然后EASDF再将分流地址发送给UE。UE在后续发起业务访问时会任意选择这些分流地址中的一个分流地址进行业务访问，当该分流地址访问失败时，会从其他分流地址中选择一个分流地址再次发起业务访问。可选的，SMF可以仅选择目标DNAI对应的一个IP地址配置为UE的分流地址。
一个可行的实施例中，如图8所示，EASDF向DNS系统查询UE可用的边缘应用服务器的IP地址，如果EASDF接收到DNS系统返回的多个IP地址，则EASDF可以根据预配置的信息，确定这些IP地址与DNAI的映射关系。然后EASDF可以选择一个目标DNAI，然后选择对应目标DNAI的IP地址，这样在建立用户面分流路径时，会选择支持该目标DNAI的L-PSA UPF来建立分流路径。EASDF会将对应目标DNAI的IP地址发送给SMF。SMF会把这些IP地址均作为UE的分流地址(即I-UPF上的分流规则中的分流边缘应用服务器地址)，当SMF配置完成后，EASDF会将对应目标DNAI的分流地址发送给UE。UE在后续发起业务访问时会任意选择这些分流地址中的一个分流地址进行业务访问，当该分流地址访问失败时，会从其他分流地址中选择一个分流地址再次发起业务访问。可选的，EASDF可以仅选择目标DNAI对应的一个IP地址作为UE的分流地址。
采用本申请实施例提供的方法，获取到至少两个IP地址，然后，可以进一步选择目标DNAI，将至少两个IP地址中，与目标DNAI具有映射关系的IP地址，作为分流地址，再由会话管理网元根据分流地址生成中间用户面网元的分流规则。由此可见，本申请实施例中，会话管理网元不会为所有IP地址生成分流规则，而是通过选择机制确定出分流地址，使得后续只用建立与分流地址相关联的分流路径，而不用再建立所有可用的IP地址相关联的分流路径，以避免未被终端设备选择的IP地址相关联的分流路径会被闲置，从而可以降低网络资源的浪费。
请参见图9，图9是本申请实施例提供的一种网元装置的结构示意图。该网元装置可以是运行于网元设备的一个计算机程序(包括程序代码)，例如该网元装置为一个应用软件；该装置可以用于执行本申请实施例提供的数据处理方法中的相应步骤。如图9所示，该网元装置1可以包括：报告接收模块11、标识符选择模块12、地址选择模块13以及规则生成模块14。
报告接收模块11，用于会话管理网元接收边缘应用服务器发现网元发送的域名系统消息报告；域名系统消息报告包含至少两个边缘应用服务器地址；
标识符选择模块12，用于选择目标数据网络接入标识符；
地址选择模块13，用于将至少两个边缘应用服务器地址中，与目标数据网络接入标识符具有映射关系的边缘应用服务器地址，作为分流边缘应用服务器地址；
规则生成模块14，用于根据分流边缘应用服务器地址生成中间用户面网元的分流规则。
其中，报告接收模块11、标识符选择模块12、地址选择模块13以及规则生成模块14的具体功能实现方式可以参见上述图3所对应实施例中的步骤S101-步骤S103，这里不再进行赘述。
请参见图9，标识符选择模块12可以包括：第一获取单元121以及第一确定单元122。
第一获取单元121，用于从至少两个边缘应用服务器地址中，获取目标边缘应用服务器地址；
第一确定单元122，用于将与目标边缘应用服务器地址具有映射关系的数据网络接入标识符，作为目标数据网络接入标识符。
其中，第一获取单元121以及第一确定单元122的具体功能实现方式可以参见上述图4a所对应实施例的描述，这里不再进行赘述。
请参见图9，标识符选择模块12可以包括：第二获取单元123、查询单元124以及第二确定单元125。
第二获取单元123，用于获取与至少两个边缘应用服务器地址分别具有映射关系的数据网络接入标识符，得到一个或多个待选择数据网络接入标识符；
查询单元124，用于查询一个或多个待选择数据网络接入标识符分别对应的边缘锚点用户面网元的负载情况；
第二确定单元125，用于根据负载情况在一个或多个待选择数据网络接入标识符中，确定目标数据网络接入标识符。
其中，第二获取单元123、查询单元124以及第二确定单元125的具体功能实现方式可以参见上述图4b所对应实施例的描述，这里不再进行赘述。
请参见图9，标识符选择模块12可以包括：第三获取单元126、预测单元127以及第三确定单元128。
第三获取单元126，用于获取与至少两个边缘应用服务器地址分别具有映射关系的数据网络接入标识符，得到一个或多个待选择数据网络接入标识符；
预测单元127，用于获取一个或多个待选择数据网络接入标识符分别对应的边缘锚点用户面网元在目标时间段内的预测负载平均情况；
第三确定单元128，用于根据预测负载平均情况在一个或多个待选择数据网络接入标识符中，确定目标数据网络接入标识符。
其中，第三获取单元126、预测单元127以及第三确定单元128的具体功能实现方式可以参见上述图4b所对应实施例的描述，这里不再进行赘述。
请参见图9，标识符选择模块12可以包括：轮询单元129。
轮询单元129，用于获取与至少两个边缘应用服务器地址分别具有映射关系的数据网络接入标识符，得到一个或多个待选择数据网络接入标识符；
轮询单元129，还用于根据轮询机制，从一个或多个待选择数据网络接入标识符中，确定目标数据网络接入标识符。
其中，轮询单元129的具体功能实现方式可以参见上述图4c所对应实施例的描述，这里不再进行赘述。
请参见图9，上述网元装置1还可以包括：路径建立模块15以及规则下发模块16。
路径建立模块15，用于建立中间用户面网元与目标数据网络接入标识符对应的边缘锚点用户面网元之间的分流路径；
规则下发模块16，用于向中间用户面网元下发分流规则，以使中间用户面网元基于分流规则以及分流路径将终端设备访问分流边缘应用服务器地址的业务访问请求转发至边缘锚点用户面网元；边缘锚点用户面网元用于将业务访问请求转发至分流边缘应用服务器地址对应的边缘应用服务器。
其中，路径建立模块15以及规则下发模块16的具体功能实现方式可以参见上述图3所对应实施例中步骤S103的描述，这里不再进行赘述。
请参见图9，上述网元装置1还可以包括：地址发送模块17。
地址发送模块17，用于将分流边缘应用服务器地址发送给边缘应用服务器发现网元，以使边缘应用服务器发现网元将分流边缘应用服务器地址发送给终端设备。
其中，地址发送模块17的具体功能实现方式可以参见上述图3所对应实施例中步骤S103的描述，这里不再进行赘述。
请参见图10，图10是本申请实施例提供的一种网元装置的结构示意图。该网元装置可以是运行于网元设备的一个计算机程序(包括程序代码)，例如该网元装置为一个应用软件；该装置可以用于执行本申请实施例提供的数据处理方法中的相应步骤。如图10所示，该网元装置2可以包括：接收模块21、标识符选择模块22、地址选择模块23以及发送模块24。
接收模块21，用于边缘应用服务器发现网元接收域名系统服务器发送的域名系统响应消息；域名系统响应消息包含至少两个边缘应用服务器地址；
标识符选择模块22，用于选择目标数据网络接入标识符；
地址选择模块23，用于从至少两个边缘应用服务器地址中，将与目标数据网络接入标识符具有映射关系的边缘应用服务器地址，作为分流边缘应用服务器地址；
发送模块24，用于将分流边缘应用服务器地址和目标数据网络接入标识符发送给会话管理网元，以使会话管理网元根据分流边缘应用服务器地址生成中间用户面网元的分流规则，建立中间用户面网元与目标数据网络接入标识符对应的边缘锚点用户面网元之间的分流路径。
其中，接收模块21、标识符选择模块22、地址选择模块23以及发送模块24的具体功能实现方式可以参见上述图5所对应实施例中步骤S201-步骤S203的描述，这里不再进行赘述。
请参见图10，该网元装置2还可以包括：响应发送模块25。
响应发送模块25，用于在分流规则生成且分流路径建立后，将所述分流边缘应用服务器地址发送给终端设备。
其中，响应发送模块25的具体功能实现方式可以参见上述图5所对应实施例中步骤S203的描述，这里不再进行赘述。
请参见图11，图11是本申请实施例提供的一种网元装置的结构示意图。该网元装置可以是运行于网元设备的一个计算机程序(包括程序代码)，例如该网元装置为一个应用软件；该装置可以用于执行本申请实施例提供的数据处理方法中的相应步骤。如图11所示，该网元装置3可以包括：规则接收模块31。
规则接收模块31，用于中间用户面网元接收会话管理网元下发的分流规则；分流规则是根据分流边缘应用服务器地址生成的；分流规则用于将终端设备访问分流边缘应用服务器地址的业务访问请求转发至目 标数据网络接入标识符对应的边缘锚点用户面网元；目标数据网络接入标识符是由会话管理网元在接收到边缘应用服务器发现网元发送的域名系统消息报告后，所选择得到的；域名系统消息报告包含至少两个边缘应用服务器地址，分流边缘应用服务器地址是指至少两个边缘应用服务器地址中，与目标数据网络接入标识符具有映射关系的边缘应用服务器地址。
请参见图11，上述网元装置3还包括：请求转发模块32。
请求转发模块32，用于基于分流规则以及分流路径将终端设备访问分流边缘应用服务器地址的业务访问请求转发至目标数据网络接入标识符对应的边缘锚点用户面网元，以使边缘锚点用户面网元将业务访问请求转发至分流边缘应用服务器地址对应的边缘应用服务器；分流路径是由会话管理网元建立的中间用户面网元与目标数据网络接入标识符对应的边缘锚点用户面网元之间的分流路径。
其中，请求转发模块32的具体功能实现方式可以参见上述图6所对应实施例中步骤S302的描述，这里不再进行赘述。
请参见图11，请求转发模块32可以包括：接收单元321以及转发单元322。
接收单元321，用于接收终端设备发送的目标业务访问请求；目标业务访问请求中携带有目标边缘应用服务器地址；
转发单元322，用于若在分流边缘应用服务器地址中查找到和目标边缘应用服务器地址相同的边缘应用服务器地址，则基于分流规则以及分流路径将目标业务访问请求转发至目标数据网络接入标识符对应的边缘锚点用户面网元，以使边缘锚点用户面网元将目标业务访问请求转发至目标边缘应用服务器地址对应的边缘应用服务器。
其中，上述分流边缘应用服务器地址对应的边缘应用服务器均用于为终端设备提供边缘应用服务；分流边缘应用服务器地址的数量为至少两个，至少两个分流边缘应用服务器地址包括第一分流边缘应用服务器地址和第二分流边缘应用服务器地址；第二分流边缘应用服务器地址是在通过第一分流边缘应用服务器地址对边缘应用服务访问失败后，由终端设备再次发起的业务访问请求中所携带的边缘应用服务器地址。
其中，接收单元321以及转发单元322的具体功能实现方式可以参见上述图6所对应实施例中步骤S302的描述，这里不再进行赘述。
请参见图12，图12是本申请实施例提供的一种网元设备的结构示意图。如图12所示，该网元设备1000可以包括：处理器1001，网络接口1003和存储器1004，此外，上述网元设备1000还可以包括：至少一个通信总线1002。其中，通信总线1002用于实现这些组件之间的连接通信。其中，网络接口1003可选的可以包括标准的有线接口、无线接口(如WI-FI接口)。存储器1004可以是高速RAM存储器，也可以是非不稳定的存储器(non-volatile memory)，例如至少一个磁盘存储器。存储器1004可选的还可以是至少一个位于远离前述处理器1001的存储装置。如图12所示，作为一种计算机可读存储介质的存储器1004中可以包括操作系统、网络通信模块以及设备控制应用程序。在本申请实施例中，网元设备1000可以为会话管理网元。
在如图12所示的网元设备1000中，网络接口1003可提供网络通讯网元；而处理器1001可以用于调用存储器1004中存储的设备控制应用程序，以使网元设备1000执行：
接收边缘应用服务器发现网元发送的域名系统消息报告；域名系统消息报告包含至少两个边缘应用服务器地址；
选择目标数据网络接入标识符，将至少两个边缘应用服务器地址中，与目标数据网络接入标识符具有映射关系的边缘应用服务器地址，作为分流边缘应用服务器地址；
根据分流边缘应用服务器地址生成中间用户面网元的分流规则。
应当理解，本申请实施例中所描述的网元设备1000可执行前文图3所对应实施例中对该数据处理方法的描述，在此不再赘述。另外，对采用相同方法的有益效果描述，也不再进行赘述。
此外，这里需要指出的是：本申请实施例还提供了一种计算机可读存储介质，且上述计算机可读存储介质中存储有前文提及的网元装置1所执行的计算机程序，且上述计算机程序包括程序指令，当上述处理器执行上述程序指令时，能够执行前文图3所对应实施例中对上述数据处理方法的描述，因此，这里将不再进行赘述。另外，对采用相同方法的有益效果描述，也不再进行赘述。对于本申请所涉及的计算机可读存储介质实施例中未披露的技术细节，请参照本申请方法实施例的描述。
请参见图13，图13是本申请实施例提供的一种网元设备的结构示意图。如图13所示，该网元设备2000可以包括：处理器2001，网络接口2003和存储器2004，此外，上述网元设备2000还可以包括：至少一个通信总线2002。其中，通信总线2002用于实现这些组件之间的连接通信。其中，网络接口2003可选的可以包括标准的有线接口、无线接口(如WI-FI接口)。存储器2004可以是高速RAM存储器，也可以是非不稳定的存储器(non-volatile memory)，例如至少一个磁盘存储器。存储器2004可选的还可以是至少一个位于远离前述处理器2001的存储装置。如图13所示，作为一种计算机可读存储介质的存储器2004中可以包括操作系统、网络通信模块以及设备控制应用程序。在本申请实施例中，网元设备2000可以为 边缘应用服务器发现网元。
在如图13所示的网元设备2000中，网络接口2003可提供网络通讯网元；而处理器2001可以用于调用存储器2004中存储的设备控制应用程序，以使网元设备2000执行：
接收域名系统服务器发送的域名系统响应消息；域名系统响应消息包含至少两个边缘应用服务器地址；
选择目标数据网络接入标识符，从至少两个边缘应用服务器地址中，将与目标数据网络接入标识符具有映射关系的边缘应用服务器地址，作为分流边缘应用服务器地址；
将分流边缘应用服务器地址和目标数据网络接入标识符发送给会话管理网元，以使会话管理网元根据分流边缘应用服务器地址生成中间用户面网元的分流规则，建立中间用户面网元与目标数据网络接入标识符对应的边缘锚点用户面网元之间的分流路径。
应当理解，本申请实施例中所描述的网元设备2000可执行前文图5所对应实施例中对该数据处理方法的描述，在此不再赘述。另外，对采用相同方法的有益效果描述，也不再进行赘述。
此外，这里需要指出的是：本申请实施例还提供了一种计算机可读存储介质，且上述计算机可读存储介质中存储有前文提及的网元装置2所执行的计算机程序，且上述计算机程序包括程序指令，当上述处理器执行上述程序指令时，能够执行前文图5所对应实施例中对上述数据处理方法的描述，因此，这里将不再进行赘述。另外，对采用相同方法的有益效果描述，也不再进行赘述。对于本申请所涉及的计算机可读存储介质实施例中未披露的技术细节，请参照本申请方法实施例的描述。
请参见图14，图14是本申请实施例提供的一种网元设备的结构示意图。如图14所示，该网元设备3000可以包括：处理器3001，网络接口3003和存储器3004，此外，上述网元设备3000还可以包括：至少一个通信总线3002。其中，通信总线3002用于实现这些组件之间的连接通信。其中，网络接口3003可选的可以包括标准的有线接口、无线接口(如WI-FI接口)。存储器3004可以是高速RAM存储器，也可以是非不稳定的存储器(non-volatile memory)，例如至少一个磁盘存储器。存储器3004可选的还可以是至少一个位于远离前述处理器3001的存储装置。如图14所示，作为一种计算机可读存储介质的存储器3004中可以包括操作系统、网络通信模块以及设备控制应用程序。在本申请实施例中，网元设备3000可以为中间用户面网元。
在如图14所示的网元设备3000中，网络接口3003可提供网络通讯网元；而处理器3001可以用于调用存储器3004中存储的设备控制应用程序，以使网元设备3000执行：
接收会话管理网元下发的分流规则；
分流规则是根据分流边缘应用服务器地址生成的；分流规则用于将终端设备访问分流边缘应用服务器地址的业务访问请求转发至目标数据网络接入标识符对应的边缘锚点用户面网元；目标数据网络接入标识符是由会话管理网元在接收到边缘应用服务器发现网元发送的域名系统消息报告后，所选择得到的；域名系统消息报告包含至少两个边缘应用服务器地址，分流边缘应用服务器地址是指至少两个边缘应用服务器地址中，与目标数据网络接入标识符具有映射关系的边缘应用服务器地址。
应当理解，本申请实施例中所描述的网元设备3000可执行前文图6所对应实施例中对该数据处理方法的描述，在此不再赘述。另外，对采用相同方法的有益效果描述，也不再进行赘述。
此外，这里需要指出的是：本申请实施例还提供了一种计算机可读存储介质，且上述计算机可读存储介质中存储有前文提及的网元装置3所执行的计算机程序，且上述计算机程序包括程序指令，当上述处理器执行上述程序指令时，能够执行前文图6所对应实施例中对上述数据处理方法的描述，因此，这里将不再进行赘述。另外，对采用相同方法的有益效果描述，也不再进行赘述。对于本申请所涉及的计算机可读存储介质实施例中未披露的技术细节，请参照本申请方法实施例的描述。
上述计算机可读存储介质可以是前述任一实施例提供的网元装置或者上述网元设备的内部存储单元，例如网元设备的硬盘或内存。该计算机可读存储介质也可以是该网元设备的外部存储设备，例如该网元设备上配备的插接式硬盘，智能存储卡(smart media card，SMC)，安全数字(secure digital，SD)卡，闪存卡(flash card)等。进一步地，该计算机可读存储介质还可以既包括该网元设备的内部存储单元也包括外部存储设备。该计算机可读存储介质用于存储该计算机程序以及该网元设备所需的其他程序和数据。该计算机可读存储介质还可以用于暂时地存储已经输出或者将要输出的数据。
此外，这里需要指出的是：本申请实施例还提供了一种计算机程序产品或计算机程序，该计算机程序产品或计算机程序包括计算机指令，该计算机指令存储在计算机可读存储介质中。网元设备的处理器从计算机可读存储介质读取该计算机指令，处理器执行该计算机指令，使得该网元设备执行前文图3、图5、图6任一个所对应实施例提供的方法。
本申请实施例的说明书和权利要求书及附图中的术语“第一”、“第二”等是用于区别不同对象，而非用于描述特定顺序。此外，术语“包括”以及它们任何变形，意图在于覆盖不排他的包含。例如包含了一系列步骤或单元的过程、方法、装置、产品或设备没有限定于已列出的步骤或模块，而是可选地还包括没有列 出的步骤或模块，或可选地还包括对于这些过程、方法、装置、产品或设备固有的其他步骤单元。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、计算机软件或者二者的结合来实现，为了清楚地说明硬件和软件的可互换性，在上述说明中已经按照网元一般性地描述了各示例的组成及步骤。这些网元究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的网元，但是这种实现不应认为超出本申请的范围。
本申请实施例提供的方法及相关装置是参照本申请实施例提供的方法流程图和/或结构示意图来描述的，具体可由计算机程序指令实现方法流程图和/或结构示意图的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。这些计算机程序指令可提供到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或结构示意图一个方框或多个方框中指定的功能的装置。这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或结构示意图一个方框或多个方框中指定的功能。这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或结构示意一个方框或多个方框中指定的功能的步骤。
以上所揭露的仅为本申请较佳实施例而已，当然不能以此来限定本申请之权利范围，因此依本申请权利要求所作的等同变化，仍属本申请所涵盖的范围。

Claims (27)

  1. 一种数据处理方法，其特征在于，包括：
    会话管理网元接收边缘应用服务器发现网元发送的域名系统消息报告；所述域名系统消息报告包含至少两个边缘应用服务器地址；
    所述会话管理网元选择目标数据网络接入标识符，将所述至少两个边缘应用服务器地址中，与所述目标数据网络接入标识符具有映射关系的边缘应用服务器地址，作为分流边缘应用服务器地址；
    所述会话管理网元根据所述分流边缘应用服务器地址生成中间用户面网元的分流规则。
  2. 根据权利要求1所述的方法，其特征在于，所述会话管理网元选择目标数据网络接入标识符，包括：
    所述会话管理网元从所述至少两个边缘应用服务器地址中，获取目标边缘应用服务器地址；
    所述会话管理网元将与所述目标边缘应用服务器地址具有映射关系的数据网络接入标识符，作为目标数据网络接入标识符。
  3. 根据权利要求1所述的方法，其特征在于，所述会话管理网元选择目标数据网络接入标识符，包括：
    会话管理网元获取与所述至少两个边缘应用服务器地址分别具有映射关系的数据网络接入标识符，得到一个或多个待选择数据网络接入标识符；
    会话管理网元查询所述一个或多个待选择数据网络接入标识符分别对应的边缘锚点用户面网元的负载情况；
    会话管理网元根据所述负载情况在所述一个或多个待选择数据网络接入标识符中，确定目标数据网络接入标识符。
  4. 根据权利要求1所述的方法，其特征在于，所述会话管理网元选择目标数据网络接入标识符，包括：
    所述会话管理网元获取与所述至少两个边缘应用服务器地址分别具有映射关系的数据网络接入标识符，得到一个或多个待选择数据网络接入标识符；
    所述会话管理网元获取所述一个或多个待选择数据网络接入标识符分别对应的边缘锚点用户面网元在目标时间段内的预测平均负载情况；
    所述会话管理网元根据所述预测平均负载情况在所述一个或多个待选择数据网络接入标识符中，确定目标数据网络接入标识符。
  5. 根据权利要求1所述的方法，其特征在于，所述会话管理网元选择目标数据网络接入标识符，包括：
    所述会话管理网元获取与所述至少两个边缘应用服务器地址分别具有映射关系的数据网络接入标识符，得到一个或多个待选择数据网络接入标识符；
    所述会话管理网元根据轮询机制，从所述一个或多个待选择数据网络接入标识符中，确定目标数据网络接入标识符。
  6. 根据权利要求1-5中任一项所述的方法，其特征在于，还包括：
    所述会话管理网元建立中间用户面网元与所述目标数据网络接入标识符对应的边缘锚点用户面网元之间的分流路径；
    所述会话管理网元向所述中间用户面网元下发所述分流规则，以使所述中间用户面网元基于所述分流规则以及所述分流路径将终端设备访问所述分流边缘应用服务器地址的业务访问请求转发至所述边缘锚点用户面网元；所述边缘锚点用户面网元用于将所述业务访问请求转发至所述分流边缘应用服务器地址对应的边缘应用服务器。
  7. 根据权利要求1-6中任一项所述的方法，其特征在于，还包括：
    所述会话管理网元将所述分流边缘应用服务器地址发送给所述边缘应用服务器发现网元，以使所述边缘应用服务器发现网元将所述分流边缘应用服务器地址发送给终端设备。
  8. 一种数据处理方法，其特征在于，包括：
    边缘应用服务器发现网元接收域名系统服务器发送的域名系统响应消息；所述域名系统响应消息包含至少两个边缘应用服务器地址；
    所述边缘应用服务器发现网元选择目标数据网络接入标识符，从所述至少两个边缘应用服务器地址中，将与所述目标数据网络接入标识符具有映射关系的边缘应用服务器地址，作为分流边缘应用服务器地址；
    所述边缘应用服务器发现网元将所述分流边缘应用服务器地址和所述目标数据网络接入标识符发送给会话管理网元，以使所述会话管理网元根据所述分流边缘应用服务器地址生成中间用户面网元的分流规则，建立所述中间用户面网元与所述目标数据网络接入标识符对应的边缘锚点用户面网元之间的分流路 径。
  9. 根据权利要求8所述的方法，其特征在于，还包括：
    所述边缘应用服务器发现网元在所述分流规则生成且所述分流路径建立后，将所述分流边缘应用服务器地址发送给终端设备。
  10. 一种数据处理方法，其特征在于，包括：
    中间用户面网元接收会话管理网元下发的分流规则；所述分流规则是根据分流边缘应用服务器地址生成的；所述分流规则用于将终端设备访问所述分流边缘应用服务器地址的业务访问请求转发至目标数据网络接入标识符对应的边缘锚点用户面网元；所述目标数据网络接入标识符是由所述会话管理网元在接收到边缘应用服务器发现网元发送的域名系统消息报告后，所选择得到的；所述域名系统消息报告包含至少两个边缘应用服务器地址，所述分流边缘应用服务器地址是指所述至少两个边缘应用服务器地址中，与所述目标数据网络接入标识符具有映射关系的边缘应用服务器地址；
    所述中间用户面网元基于所述分流规则以及分流路径将终端设备访问所述分流边缘应用服务器地址的业务访问请求转发至所述目标数据网络接入标识符对应的边缘锚点用户面网元，以使所述边缘锚点用户面网元将所述业务访问请求转发至所述分流边缘应用服务器地址对应的边缘应用服务器；所述分流路径是由所述会话管理网元建立的中间用户面网元与所述目标数据网络接入标识符对应的边缘锚点用户面网元之间的分流路径。
  11. 根据权利要求10所述的方法，其特征在于，所述中间用户面网元基于所述分流规则以及分流路径将终端设备访问所述分流边缘应用服务器地址的业务访问请求转发至所述目标数据网络接入标识符对应的边缘锚点用户面网元，包括：
    所述中间用户面网元接收所述终端设备发送的目标业务访问请求；所述目标业务访问请求中携带有目标边缘应用服务器地址；
    所述中间用户面网元若在所述分流边缘应用服务器地址中查找到和所述目标边缘应用服务器地址相同的边缘应用服务器地址，则通过所述分流规则以及所述分流路径将所述目标业务访问请求转发至所述目标数据网络接入标识符对应的边缘锚点用户面网元，以使所述边缘锚点用户面网元将所述目标业务访问请求转发至所述目标边缘应用服务器地址对应的边缘应用服务器。
  12. 根据权利要求10或11所述的方法，其特征在于，所述分流边缘应用服务器地址对应的边缘应用服务器用于为所述终端设备提供边缘应用服务；
    所述分流边缘应用服务器地址的数量为至少两个，至少两个分流边缘应用服务器地址包括第一分流边缘应用服务器地址和第二分流边缘应用服务器地址；所述第二分流边缘应用服务器地址是在通过所述第一分流边缘应用服务器地址对所述边缘应用服务访问失败后，由所述终端设备再次发起的业务访问请求中所携带的边缘应用服务器地址。
  13. 一种网元装置，其特征在于，包括：
    报告接收模块，用于会话管理网元接收边缘应用服务器发现网元发送的域名系统消息报告；所述域名系统消息报告包含至少两个边缘应用服务器地址；
    标识符选择模块，用于选择目标数据网络接入标识符；
    地址选择模块，用于将所述至少两个边缘应用服务器地址中，与所述目标数据网络接入标识符具有映射关系的边缘应用服务器地址，作为分流边缘应用服务器地址；
    规则生成模块，用于根据所述分流边缘应用服务器地址生成中间用户面网元的分流规则。
  14. 根据权利要求13所述的装置，其特征在于，所述标识符选择模块，包括：
    第一获取单元，用于从所述至少两个边缘应用服务器地址中，获取目标边缘应用服务器地址；
    第一确定单元，用于将与所述目标边缘应用服务器地址具有映射关系的数据网络接入标识符，作为目标数据网络接入标识符。
  15. 根据权利要求13所述的装置，其特征在于，所述标识符选择模块，包括：
    第二获取单元，用于获取与所述至少两个边缘应用服务器地址分别具有映射关系的数据网络接入标识符，得到一个或多个待选择数据网络接入标识符；
    查询单元，用于查询一个或多个待选择数据网络接入标识符分别对应的边缘锚点用户面网元的负载情况；
    第二确定单元，用于根据所述负载情况在所述一个或多个待选择数据网络接入标识符中，确定目标数据网络接入标识符。
  16. 根据权利要求13所述的装置，其特征在于，标识符选择模块，包括：
    第三获取单元，用于获取与所述至少两个边缘应用服务器地址分别具有映射关系的数据网络接入标识符，得到一个或多个待选择数据网络接入标识符；
    预测单元，用于获取所述一个或多个待选择数据网络接入标识符分别对应的边缘锚点用户面网元在目 标时间段内的预测负载平均情况；
    第三确定单元，用于根据所述预测负载平均情况在所述一个或多个待选择数据网络接入标识符中，确定目标数据网络接入标识符。
  17. 根据权利要求13所述的装置，其特征在于，所述标识符选择模块，包括：
    轮询单元，用于获取与所述至少两个边缘应用服务器地址分别具有映射关系的数据网络接入标识符，得到一个或多个待选择数据网络接入标识符；
    轮询单元，还用于根据轮询机制，从所述一个或多个待选择数据网络接入标识符中，确定目标数据网络接入标识符。
  18. 根据权利要求13所述的装置，其特征在于，所述网元装置，还包括：
    路径建立模块，用于建立中间用户面网元与目标数据网络接入标识符对应的边缘锚点用户面网元之间的分流路径；
    规则下发模块，用于向所述中间用户面网元下发分流规则，以使所述中间用户面网元基于所述分流规则以及所述分流路径将终端设备访问所述分流边缘应用服务器地址的业务访问请求转发至所述边缘锚点用户面网元；所述边缘锚点用户面网元用于将所述业务访问请求转发至所述分流边缘应用服务器地址对应的边缘应用服务器。
  19. 根据权利要求13所述的装置，其特征在于，所述网元装置，还包括：
    地址发送模块，用于将所述分流边缘应用服务器地址发送给所述边缘应用服务器发现网元，以使所述边缘应用服务器发现网元将所述分流边缘应用服务器地址发送给终端设备。
  20. 一种网元装置，其特征在于，包括：
    接收模块，用于边缘应用服务器发现网元接收域名系统服务器发送的域名系统响应消息；所述域名系统响应消息包含至少两个边缘应用服务器地址；
    标识符选择模块，用于选择目标数据网络接入标识符；
    地址选择模块，用于从所述至少两个边缘应用服务器地址中，将与所述目标数据网络接入标识符具有映射关系的边缘应用服务器地址，作为分流边缘应用服务器地址；
    发送模块，用于将所述分流边缘应用服务器地址和所述目标数据网络接入标识符发送给会话管理网元，以使所述会话管理网元根据所述分流边缘应用服务器地址生成中间用户面网元的分流规则，建立所述中间用户面网元与目标数据网络接入标识符对应的边缘锚点用户面网元之间的分流路径。
  21. 根据权利要求20所述的装置，其特征在于，上述网元装置，还包括：
    响应发送模块，用于在所述分流规则生成且所述分流路径建立后，将所述分流边缘应用服务器地址发送给终端设备。
  22. 一种网元装置，其特征在于，包括：
    规则接收模块，用于中间用户面网元接收会话管理网元下发的分流规则；所述分流规则是根据分流边缘应用服务器地址生成的；所述分流规则用于将终端设备访问所述分流边缘应用服务器地址的业务访问请求转发至目标数据网络接入标识符对应的边缘锚点用户面网元；所述目标数据网络接入标识符是由所述会话管理网元在接收到边缘应用服务器发现网元发送的域名系统消息报告后，所选择得到的；所述域名系统消息报告包含至少两个边缘应用服务器地址，所述分流边缘应用服务器地址是指所述至少两个边缘应用服务器地址中，与所述目标数据网络接入标识符具有映射关系的边缘应用服务器地址；
    所述网元装置，还包括：
    请求转发模块，用于基于所述分流规则以及分流路径将终端设备访问所述分流边缘应用服务器地址的业务访问请求转发至所述目标数据网络接入标识符对应的边缘锚点用户面网元，以使所述边缘锚点用户面网元将所述业务访问请求转发至所述分流边缘应用服务器地址对应的边缘应用服务器；所述分流路径是由所述会话管理网元建立的中间用户面网元与所述目标数据网络接入标识符对应的边缘锚点用户面网元之间的分流路径。
  23. 根据权利要求22所述的装置，其特征在于，所述请求转发模块，包括：
    接收单元，用于接收所述终端设备发送的目标业务访问请求；所述目标业务访问请求中携带有目标边缘应用服务器地址；
    转发单元，用于若在所述分流边缘应用服务器地址中查找到和所述目标边缘应用服务器地址相同的边缘应用服务器地址，则通过所述分流规则以及所述分流路径将所述目标业务访问请求转发至所述目标数据网络接入标识符对应的边缘锚点用户面网元，以使所述边缘锚点用户面网元将所述目标业务访问请求转发至所述目标边缘应用服务器地址对应的边缘应用服务器。
  24. 根据权利要求22或23所述的装置，其特征在于，所述分流边缘应用服务器地址对应的边缘应用服务器用于为所述终端设备提供边缘应用服务；所述分流边缘应用服务器地址的数量为至少两个，至少两个分流边缘应用服务器地址包括第一分流边缘应用服务器地址和第二分流边缘应用服务器地址；所述第二 分流边缘应用服务器地址是在通过所述第一分流边缘应用服务器地址对所述边缘应用服务访问失败后，由所述终端设备再次发起的业务访问请求中所携带的边缘应用服务器地址。
  25. 一种网元设备，其特征在于，包括：处理器、存储器以及网络接口；
    所述处理器与所述存储器、所述网络接口相连，其中，所述网络接口用于提供数据通信功能，所述存储器用于存储程序代码，所述处理器用于调用所述程序代码，以使所述网元设备执行权利要求1-12任一项所述的方法。
  26. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质中存储有计算机程序，所述计算机程序适于由处理器加载并执行权利要求1-12任一项所述的方法。
  27. 一种计算机程序产品，其特征在于，所述计算机程序产品包括计算机指令，所述计算机指令适于由处理器加载并执行权利要求1-12任一项所述的方法。
PCT/CN2022/102056 2021-07-23 2022-06-28 一种数据处理方法、网元设备以及可读存储介质 WO2023000935A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP22845100.1A EP4247049A1 (en) 2021-07-23 2022-06-28 Data processing method, network element device, and readable storage medium
US18/327,938 US20230308951A1 (en) 2021-07-23 2023-06-02 Data processing method, network element device, and readable storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110839104.1 2021-07-23
CN202110839104.1A CN113596191B (zh) 2021-07-23 2021-07-23 一种数据处理方法、网元设备以及可读存储介质

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/327,938 Continuation US20230308951A1 (en) 2021-07-23 2023-06-02 Data processing method, network element device, and readable storage medium

Publications (1)

Publication Number Publication Date
WO2023000935A1 true WO2023000935A1 (zh) 2023-01-26

Family

ID=78249520

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/102056 WO2023000935A1 (zh) 2021-07-23 2022-06-28 一种数据处理方法、网元设备以及可读存储介质

Country Status (4)

Country Link
US (1) US20230308951A1 (zh)
EP (1) EP4247049A1 (zh)
CN (2) CN113596191B (zh)
WO (1) WO2023000935A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116056240A (zh) * 2023-04-03 2023-05-02 阿里巴巴（中国）有限公司 资源配置系统、方法及设备
CN116367204A (zh) * 2023-05-31 2023-06-30 阿里巴巴（中国）有限公司 用户设备业务处理方法、电子设备、存储介质及系统

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20220059539A (ko) * 2019-09-18 2022-05-10 텔레폰악티에볼라겟엘엠에릭슨(펍) 모바일 에지 컴퓨팅에서의 로컬 애플리케이션 서버 검색 방법 및 장치
CN117177266A (zh) * 2020-04-28 2023-12-05 华为技术有限公司 一种地址获取方法及装置
CN113596191B (zh) * 2021-07-23 2023-05-26 腾讯科技（深圳）有限公司 一种数据处理方法、网元设备以及可读存储介质
CN116260795A (zh) * 2021-12-10 2023-06-13 华为技术有限公司 选择边缘应用服务器的方法和装置
CN114339727B (zh) * 2021-12-29 2023-08-15 中国联合网络通信集团有限公司 边缘平台、配置方法、装置、终端及存储介质
CN116566950A (zh) * 2022-01-28 2023-08-08 维沃移动通信有限公司 Ip地址确定方法及装置、标识确定方法及装置、及网元
CN117014987A (zh) * 2022-04-29 2023-11-07 华为技术有限公司 通信方法及装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109275160A (zh) * 2017-07-17 2019-01-25 华为技术有限公司 数据分流方法、设备及系统
WO2019083223A1 (ko) * 2017-10-25 2019-05-02 에스케이텔레콤 주식회사 단말장치 및 데이터 송수신장치, 그 장치의 동작 방법
CN110912835A (zh) * 2019-11-08 2020-03-24 腾讯科技（深圳）有限公司 业务分流方法、装置及系统
CN112584437A (zh) * 2019-09-30 2021-03-30 中国移动通信有限公司研究院 一种数据分流方法及装置
CN113596191A (zh) * 2021-07-23 2021-11-02 腾讯科技（深圳）有限公司 一种数据处理方法、网元设备以及可读存储介质

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8775564B1 (en) * 2013-12-31 2014-07-08 Limelight Networks, Inc. Time based CDN traffic allocation
CN110351777B (zh) * 2018-04-03 2022-12-06 华为技术有限公司 指示业务分流的方法和装置
CN111083737B (zh) * 2018-10-19 2021-04-16 大唐移动通信设备有限公司 一种边缘mec中数据的分流方法和装置
CN111866773B (zh) * 2019-04-29 2021-09-03 大唐移动通信设备有限公司 一种数据的获取方法和装置
CN114946214A (zh) * 2020-01-07 2022-08-26 上海诺基亚贝尔股份有限公司 在本地访问数据网络的情况下解析域名的方法和装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109275160A (zh) * 2017-07-17 2019-01-25 华为技术有限公司 数据分流方法、设备及系统
WO2019083223A1 (ko) * 2017-10-25 2019-05-02 에스케이텔레콤 주식회사 단말장치 및 데이터 송수신장치, 그 장치의 동작 방법
CN112584437A (zh) * 2019-09-30 2021-03-30 中国移动通信有限公司研究院 一种数据分流方法及装置
CN110912835A (zh) * 2019-11-08 2020-03-24 腾讯科技（深圳）有限公司 业务分流方法、装置及系统
CN113596191A (zh) * 2021-07-23 2021-11-02 腾讯科技（深圳）有限公司 一种数据处理方法、网元设备以及可读存储介质

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 5G System Enhancements for Edge Computing; Stage 2 (Release 17)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 23.548, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. V0.2.0, 30 April 2021 (2021-04-30), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , pages 1 - 46, XP052000915 *
HUAWEI, NOKIA, NOKIA SHANGHAI BELL, CHINA MOBILE, ZTE, FUTUREWEI, NTT DOCOMO, LENOVO, INTERDIGITAL INC.: "EAS Discovery for Session Breakout connectivity model", 3GPP DRAFT; S2-2100116, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. e-meeting; 20210224 - 20210309, 18 February 2021 (2021-02-18), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052172463 *
See also references of EP4247049A1

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116056240A (zh) * 2023-04-03 2023-05-02 阿里巴巴（中国）有限公司 资源配置系统、方法及设备
CN116056240B (zh) * 2023-04-03 2023-06-23 阿里巴巴（中国）有限公司 资源配置系统、方法及设备
CN116367204A (zh) * 2023-05-31 2023-06-30 阿里巴巴（中国）有限公司 用户设备业务处理方法、电子设备、存储介质及系统
CN116367204B (zh) * 2023-05-31 2023-09-12 阿里巴巴（中国）有限公司 用户设备业务处理方法、电子设备、存储介质及系统

Also Published As

Publication number Publication date
EP4247049A1 (en) 2023-09-20
US20230308951A1 (en) 2023-09-28
CN113596191B (zh) 2023-05-26
CN116405461A (zh) 2023-07-07
CN113596191A (zh) 2021-11-02

Similar Documents

Publication Publication Date Title
WO2023000935A1 (zh) 一种数据处理方法、网元设备以及可读存储介质
WO2020259509A1 (zh) 一种应用迁移方法及装置
WO2023000940A1 (zh) 数据处理方法、装置、网元设备、存储介质及程序产品
CN110896553B (zh) 多接入边缘计算方法和平台、通信系统
JP7427082B2 (ja) サービスオフロード方法、装置、システム、電子機器、及びコンピュータプログラム
WO2023000936A1 (zh) 一种数据处理方法、网元设备以及可读存储介质
WO2022048261A1 (zh) 边缘应用发现方法及装置、边缘应用服务支持方法及装置
WO2023015815A1 (zh) 物联网终端接入系统、方法、装置及存储介质
JP6395867B2 (ja) ＯｐｅｎＦｌｏｗ通信方法及びシステム、制御部、並びにサービスゲートウェイ
WO2021169291A1 (zh) 发布路由的方法、网元、系统及设备
US11777795B2 (en) Local breakout of user plan function at enterprise 5G radio access network
WO2022105807A1 (zh) 服务实例部署方法、跨域互访通道建立方法及相关装置
CN112968965B (zh) Nfv网络节点的元数据服务方法、服务器及存储介质
CN114629912B (zh) 基于mec的通信传输方法及装置
CN111315037B (zh) 通信链路建立方法、装置、计算机设备及存储介质
WO2020211538A1 (zh) 一种数据传输方法及装置
KR20220005936A (ko) 네트워크 노드 및 네트워크 노드 간 메시지 전송 방법
CN112994996B (zh) 家庭网络共享方法、mec服务器、计算机设备及介质
EP4287689B1 (en) Method for using a terminal device in a telecommunications network, wherein, regarding a specific user equipment functionality, the telecommunications network initializes or provides a logical user equipment entity or functionality, system for using a terminal device in a telecommunications network, terminal device, program and computer-readable medium
CN113556742B (zh) 一种网络架构及分流策略配置方法
WO2023185286A1 (zh) 一种通信方法及装置
CN117395738A (zh) 网络接入方法、装置、设备、系统、存储介质和程序产品
CN116866985A (zh) 数据转发方法、网络系统及计算机可读取存储介质
KR102288478B1 (ko) 분산 클라우드 인프라에서 서비스 가속화 방법 및 그 시스템
CN117295111A (zh) 数据传输方法、装置、upf实体及通信实体

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2022845100

Country of ref document: EP

Effective date: 20230612

NENP Non-entry into the national phase

Ref country code: DE