WO2021184774A1 - 基于边缘计算的通信方法、装置、存储介质及电子设备 - Google Patents

基于边缘计算的通信方法、装置、存储介质及电子设备 Download PDF

Info

Publication number
WO2021184774A1
WO2021184774A1 PCT/CN2020/126432 CN2020126432W WO2021184774A1 WO 2021184774 A1 WO2021184774 A1 WO 2021184774A1 CN 2020126432 W CN2020126432 W CN 2020126432W WO 2021184774 A1 WO2021184774 A1 WO 2021184774A1
Authority
WO
WIPO (PCT)
Prior art keywords
packet
network address
uplink
address
local edge
Prior art date
Application number
PCT/CN2020/126432
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 EP20925153.7A priority Critical patent/EP4007224B1/en
Priority to ES20925153T priority patent/ES2976452T3/es
Publication of WO2021184774A1 publication Critical patent/WO2021184774A1/zh
Priority to US17/677,740 priority patent/US11616754B2/en

Links

Images

Classifications

    • 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/09—Mapping addresses
    • H04L61/25—Mapping addresses of the same type
    • H04L61/2503—Translation of Internet protocol [IP] addresses
    • H04L61/2514—Translation of Internet protocol [IP] addresses between local and global IP addresses
    • 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/09—Mapping addresses
    • H04L61/25—Mapping addresses of the same type
    • H04L61/2503—Translation of Internet protocol [IP] addresses
    • H04L61/2521—Translation architectures other than single NAT servers
    • H04L61/2535—Multiple local networks, e.g. resolving potential IP address conflicts
    • 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/74—Address processing for routing
    • H04L45/745—Address table lookup; Address filtering
    • 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/09—Mapping addresses
    • H04L61/25—Mapping addresses of the same type
    • H04L61/2503—Translation of Internet protocol [IP] addresses
    • 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/09—Mapping addresses
    • H04L61/25—Mapping addresses of the same type
    • H04L61/2503—Translation of Internet protocol [IP] addresses
    • H04L61/2517—Translation of Internet protocol [IP] addresses using port numbers
    • 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/09—Mapping addresses
    • H04L61/25—Mapping addresses of the same type
    • H04L61/2503—Translation of Internet protocol [IP] addresses
    • H04L61/2521—Translation architectures other than single NAT servers
    • H04L61/2528—Translation at a proxy
    • 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
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2441—Traffic characterised by specific attributes, e.g. priority or QoS relying on flow classification, e.g. using integrated services [IntServ]
    • 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/4541—Directories for service discovery

Definitions

  • This application relates to the field of computer and communication technology, and in particular to a communication method, device, computer storage medium and electronic equipment based on edge computing.
  • Edge Computing is the deployment of Application Server (AS) to a location close to the User Equipment (UE), that is, by deploying an Edge Application Server (Edge Application Server) that is closer to the UE. EAS), so as to minimize the communication delay between the UE and the AS.
  • AS Application Server
  • UE User Equipment
  • Edge Application Server Edge Application Server
  • the embodiments of the present application provide a communication method, device, computer storage medium, and electronic equipment based on edge computing, which can ensure that the UE can access the EAS without modifying or enhancing the UE or AS.
  • the embodiment of the application provides a communication method based on edge computing, including: receiving an uplink Internet Protocol (IP) packet sent by a user equipment, where the destination address of the uplink IP packet is the network address of the target application server According to the network address of the target application server, determine the network address of the local edge server used to respond to the uplink IP packet; modify the destination address of the uplink IP packet to the network address of the local edge server, and forward To the local edge server for processing.
  • IP Internet Protocol
  • An embodiment of the present application also provides a communication method based on edge computing, including: receiving a network address of a target application server sent by a first user plane function entity, where the network address of the target application server is the first user plane function
  • the destination address in the uplink IP packet received by the entity, the uplink IP packet is sent by the user equipment; according to the network address of the target application server, the network address of the local edge server used to respond to the uplink IP packet is determined
  • An embodiment of the present application also provides a communication method based on edge computing, including: receiving a network address of a target application server sent by a first user plane function entity, where the network address of the target application server is the first user plane function
  • the destination address in the uplink IP packet received by the entity, the uplink IP packet is sent by the user equipment; according to the network address of the target application server, the network address of the local edge server used to respond to the uplink IP packet is determined
  • the server sends an upstream IP packet the destination address of the received upstream IP packet is modified to the network address of the local edge server, and forwarded to the local edge server for processing.
  • An embodiment of the present application also provides a communication method based on edge computing, including: receiving a network address of a target application server sent by a first user plane function entity, where the network address of the target application server is the first user plane function
  • the destination address in the uplink IP packet received by the entity, the uplink IP packet is sent by the user equipment; according to the network address of the target application server, the network address of the local edge server used to respond to the uplink IP packet is determined
  • Send an address conversion instruction to the uplink classifier connected to the second user plane functional entity, the address conversion control instruction is used to instruct the uplink classifier to receive the uplink IP sent by the user equipment to the target application server
  • An embodiment of the present application also provides a communication device based on edge computing, including: a first receiving unit configured to receive an uplink IP packet sent by a user equipment, and the destination address of the uplink IP packet is a network address of a target application server; The first determining unit is configured to determine the network address of the local edge server used to respond to the uplink IP packet according to the network address of the target application server; the first sending unit is configured to set the destination address of the uplink IP packet Modified to the network address of the local edge server, and forwarded to the local edge server for processing.
  • An embodiment of the present application also provides a communication device based on edge computing, including: a second receiving unit configured to receive a network address of a target application server sent by a first user plane functional entity, where the network address of the target application server is The destination address in the uplink IP packet received by the first user plane function entity, the uplink IP packet is sent by the user equipment; the second determining unit is configured to determine the destination address according to the network address of the target application server In response to the network address of the local edge server in response to the uplink IP packet; the second sending unit is configured to send an address conversion control instruction to the first user plane functional entity, where the address conversion instruction is used to instruct the first user The plane function entity modifies the destination address of the uplink IP packet to the network address of the local edge server, and forwards it to the local edge server for processing.
  • An embodiment of the present application also provides a communication device based on edge computing, including: a third receiving unit configured to receive a network address of a target application server sent by a first user plane functional entity, where the network address of the target application server is The destination address in the uplink IP packet received by the first user plane function entity, the uplink IP packet is sent by the user equipment; the third determining unit is configured to determine the destination address according to the network address of the target application server In response to the network address of the local edge server in response to the uplink IP packet; the third sending unit is configured to send an address translation control instruction to a second user plane functional entity connected to the local edge server, where the address translation control instruction is used to instruct When the second user plane function entity receives the uplink IP packet sent by the user equipment to the target application server, it modifies the destination address of the received uplink IP packet to the network address of the local edge server, and Forward to the local edge server for processing.
  • a third receiving unit configured to receive a network address of a target application server sent by a first user plane functional
  • An embodiment of the present application also provides a communication device based on edge computing, including: a fourth receiving unit configured to receive a network address of a target application server sent by a first user plane functional entity, where the network address of the target application server is The destination address in the uplink IP packet received by the first user plane function entity, the uplink IP packet is sent by the user equipment; the fourth determining unit is configured to determine the destination address according to the network address of the target application server In response to the network address of the local edge server in response to the uplink IP packet; the fourth sending unit is configured to send an address conversion instruction to the uplink classifier connected to the second user plane functional entity, and the address conversion control instruction is used to instruct all
  • the uplink classifier receives the uplink IP packet sent by the user equipment to the target application server, it modifies the destination address of the received uplink IP packet to the network address of the local edge server, and passes the first 2.
  • the user plane function entity forwards to the local edge server for processing.
  • the embodiment of the present application also provides a computer-readable medium on which a computer program is stored, and when the computer program is executed by a processor, the communication method based on edge computing as described in the above-mentioned embodiment is implemented.
  • An embodiment of the present application also provides an electronic device, including: one or more processors; a memory, configured to store one or more programs, when the one or more programs are executed by the one or more processors At this time, the one or more processors are caused to implement the edge computing-based communication method as described in the foregoing embodiment.
  • the user plane function entity (including the user name function entity as an uplink classifier) compares the user equipment with the target application server. Address translation and forwarding of data packets between the user equipment, that is, the destination address of the uplink IP packet sent by the user equipment to the target application server is modified to the network address of the local edge server and then forwarded to the local edge server, and the local edge server is directed to the upstream IP packet. The source address of the returned downlink IP packet is modified to the network address of the target application server and forwarded to the user equipment, so that the user equipment can access the local edge server without modifying or enhancing the user equipment and the application server.
  • FIG. 1 is an architecture diagram for implementing edge computing provided by an embodiment of the application
  • Figure 2 is another architecture diagram for implementing edge computing provided by an embodiment of the application
  • FIG. 3 is a flowchart of a communication method based on edge computing provided by an embodiment of the application
  • FIG. 4 is a flowchart of determining the network address of a local edge server according to an embodiment of the application
  • FIG. 5 is a flowchart of a communication method based on edge computing provided by an embodiment of the application
  • FIG. 6 is a flowchart of a communication method based on edge computing provided by an embodiment of the application.
  • FIG. 7 is a flowchart of a communication method based on edge computing provided by an embodiment of the application.
  • FIG. 8 is a flowchart of a communication method based on edge computing provided by an embodiment of the application.
  • FIG. 9 is a flowchart of a communication method based on edge computing provided by an embodiment of the application.
  • FIG. 10 is a flowchart of a communication method based on edge computing provided by an embodiment of the application.
  • FIG. 11 is a flowchart of a communication method based on edge computing provided by an embodiment of the application.
  • FIG. 12 is a block diagram of a communication device based on edge computing provided by an embodiment of the application.
  • FIG. 13 is a block diagram of a communication device based on edge computing provided by an embodiment of the application.
  • FIG. 14 is a block diagram of a communication device based on edge computing provided by an embodiment of the application.
  • 15 is a block diagram of a communication device based on edge computing provided by an embodiment of the application.
  • FIG. 16 is a schematic structural diagram of a computer system of an electronic device provided by an embodiment of the application.
  • FIG. 1 and FIG. 2 two architectures for implementing EC are shown in FIG. 1 and FIG. 2.
  • UPF User Plane Function
  • PSA Protocol Data Unit
  • PDU Protocol Data Unit
  • DN Data Network
  • PSA2 deploy EAS on the DN connected to PSA2.
  • NEF is the abbreviation of Network Exposure Function, which is the network open function.
  • Nnef refers to the interface through which NEF provides services.
  • Other network functions (NF) send Nnef through this interface.
  • Service request messages are sent to NEF, and NEF replies to requests or sends notification service messages through this interface;
  • PCF is the abbreviation of Policy Control Function, that is, policy control function
  • Npcf refers to the interface through which PCF provides services, and other NFs send Npcf service requests through this interface The message is sent to the PCF, and the PCF replies to requests and sends notification service messages through this interface;
  • AF is the abbreviation of Application Function, which is the application function.
  • Naf refers to the interface through which the AF provides services. Other NFs send Naf messages to the AF through this interface. AF responds to requests and sends notification service messages through this interface; AMF is short for Access and Mobility Management Function, that is, access and mobility management function. Namf refers to the interface through which AMF provides services. Other NFs send Namf messages to AMF through this interface. At the same time, AMF replies to requests and sends notification service messages through this interface; SMF is the abbreviation of Session Management Function, that is, session management function. Nsmf refers to the interface through which SMF provides services. Through this interface, other NFs send Nsmf messages to SMF, and SMF passes This interface responds to requests and sends notification service messages.
  • the UE and AMF interact through the N1 interface, between AMF and AN through the N2 interface, between SMF and UPF through the N4 interface, between AN and UPF through the N3 interface, and between UPF and DN through the N6 interface.
  • the UPF and UPF interact through the N9 interface.
  • IP Internet Protocol
  • DNS Domain Name System
  • UPF or SMF intercepts the DNS request, and then responds with a DNS pointing to the IP address of the local EAS Respond, so that the UE can establish an IP connection to the local EAS.
  • IP Internet Protocol
  • DNS Domain Name System
  • the disadvantage of this method is that if the UE adopts DNS over Hypertext Transfer Protocol (Hyper Text Transfer Protocol over Secure Socket Layer, HTTPS)/Transport Layer Security (TLS) and other protocols to encrypt DNS interaction messages, because UPF cannot perceive the encrypted DNS interaction protocol, so this method cannot work.
  • the PCF sends a UE Route Selection Policy (URSP) rule to the UE.
  • URSP UE Route Selection Policy
  • the rule for the UE to access the AS when the UE is in a certain location points to a local EAS IP, thereby realizing the UE Establish an IP connection to EAS.
  • the disadvantage of this method is that the URSP rule needs to be enhanced, and the behavior of the UE needs to be modified (that is, this rule can only be used when the UE is in a certain position).
  • the UE first visits the AS of the central node, and then the AS determines the EAS according to the location of the UE or the location of the source IP address of the UE, and then redirects the UE through the application layer redirection (Redirect) or the AF request for user-oriented rerouting.
  • the IP connection is redirected to the local EAS IP.
  • the disadvantage of this method is that the functions of the AS need to be enhanced, or it can only be applied to ASs that support these diversions or support user-oriented rerouting through AF.
  • the embodiment of the present application provides a solution for UE-to-EAS without modifying the UE or AS. This method is not only low in deployment cost, but also the most effective deployment method.
  • FIG. 3 is a flowchart of a communication method based on edge computing provided by an embodiment of the application, and the communication method may be executed by a user plane function entity UPF.
  • the communication method includes at least step S310 to step S330, which are described in detail as follows:
  • step S310 the UPF receives the uplink IP packet sent by the user equipment, and the destination address of the uplink IP packet is the network address of the target application server.
  • the user equipment needs to obtain the network address of the target application server before sending the uplink IP packet.
  • the user equipment may obtain the network address of the target application server in the following manner: the user equipment sends a DNS request to the DNS server through the user plane functional entity, and then the DNS server returns the network address containing the target application server DNS response, and then the user equipment can obtain the network address of the target application server from the DNS response.
  • the DNS request may be based on the User Datagram Protocol (UDP) protocol, the HTTPS protocol, or the TLS protocol.
  • UDP User Datagram Protocol
  • the source address of the upstream IP packet sent by the user equipment is the IP address of the user equipment
  • the destination address is the network address of the target application server
  • the source port value is the port value of the user equipment
  • the destination address is the network address of the target application server.
  • the port value is the port value of the target application server
  • the adopted transport layer protocol does not make any restrictions, such as TCP and UDP protocols.
  • step S320 according to the network address of the target application server, the network address of the local edge server for responding to the upstream IP packet is determined.
  • the solution for the user plane function entity to determine the network address of the local edge server may be as shown in FIG. 4, and includes the following steps S410 to S430:
  • step S410 the domain name list corresponding to the network address of the target application server is queried according to the network address of the target application server.
  • the user plane function entity may send a reverse domain name query request to the DNS server according to the network address of the target application server, and then receive the reverse domain name query response returned by the DNS server, from which the reverse domain name query response Obtain the domain name list corresponding to the network address of the target application server.
  • the domain name list contains one or more domain names, and multiple refers to at least two.
  • step S420 query to obtain a corresponding target domain name list according to the domain name list, the transport layer protocol used by the uplink IP packet, and the destination port included in the uplink IP packet.
  • a service record (Service Record, SRV) query request and then obtain the target domain name list based on the SRV query response fed back from the edge DNS server.
  • the target domain name list may also include one or more target domain names.
  • the target domain name may be a fully qualified domain name (FQDN), that is, a name with both a host name and a domain name.
  • FQDN fully qualified domain name
  • step S430 the network address list of the local edge server is obtained by querying based on the target domain name list, so as to obtain the network address of the local edge server for responding to the uplink IP packet based on the network address list.
  • an A (IPv4 address record) or AAAA (IPv6 address record) query request may be initiated to the edge DNS server based on the target domain name list to obtain the network address list of the local edge server.
  • IPv4 Internet Protocol version 4
  • AAAA IPv6 address record
  • the network address list may also contain one or more network addresses.
  • the UPF after the UPF queries the network address list of the local edge server, it can report the network address list and the network address of the target application server to the SMF through the N4 interface, so that the SMF can select one for The network address of the local edge server that responds to the upstream IP packet. For example, the network address of the local edge server that is closest to the user equipment can be selected, or the communication delay with the user equipment is the smallest, or the network address of the local edge server with the lightest load can be selected to improve the efficiency of edge communication.
  • the user plane function entity may also report the network address of the target application server to the session management function entity, so that the session management function entity can determine the network address of the local edge server according to the network address of the target application server.
  • the session management function entity may use steps S410 to S430 similar to those shown in FIG. 4 to determine the network address of the local edge server; or the session management function entity may also be based on the network address of the application server and the local edge server.
  • the mapping relationship between the network addresses of the target application server, the network address of the local edge server that has a mapping relationship with the network address of the target application server is used as the network address of the local edge server; or the session management function entity can also be based on the steps shown in Figure 4 S410 determines the domain name list corresponding to the network address of the target application server, and then uses the network address of the edge server corresponding to the domain name list as the network address of the local edge server according to the domain name list; or the session management function entity can also be based on Figure 4
  • the step S410 and step S420 shown in the step S410 determine the target domain name list, and then based on the mapping relationship between the domain name and the network address of the edge server, the network address list of the edge server that has a mapping relationship with the target domain
  • the user plane function entity may also query the domain name list corresponding to the network address of the target application server according to the network address of the target application server, and then report the domain name list to the session management function entity to enable the session management function
  • the entity determines the network address of the local edge server according to the list of domain names.
  • the session management function entity may use steps S420 and S430 similar to those shown in FIG. 4 to determine the network address of the local edge server; or the session management function entity may also be based on step S420 shown in FIG.
  • step S330 based on the address translation control instruction, the destination address of the upstream IP packet is modified to the network address of the local edge server, and forwarded to the local edge server for processing.
  • the UPF can receive the address translation control instruction sent by the SMF, and the address translation control instruction is used to instruct the user equipment to send the uplink IP of the target application server The destination address of the packet is modified to the network address of the local edge server.
  • the address translation control instruction sent by SMF is also used to instruct UPF to modify the source address of the downstream IP packet returned by the local edge server for the upstream IP packet to the network address of the target application server; then when the UPF receives the local edge server for the upstream IP
  • the source address of the downstream IP packet can be modified to the network address of the target application server and forwarded to the user equipment.
  • SMF can send address conversion control commands to UPF through the N4 interface.
  • the source port value conversion operation before forwarding the upstream IP packet to the local edge server for processing, can also be performed, that is, the source port value of the upstream IP packet is modified to the set identification value and recorded The corresponding relationship between the source port value of the upstream IP packet and the set identification value, and then when the downstream IP packet returned by the local edge server is received, if the destination port value of the downstream IP packet matches the set identification value, the downstream IP The destination port value of the packet is modified to the source port value of the upstream IP packet.
  • PSA1 shown in Figure 2 can send the received uplink IP packet to PSA2 through the data channel between PSA1 and PSA2, or PSA1 can also send the uplink IP received by PSA1 The packet is sent to SMF first, and then sent to PSA2 by SMF.
  • PSA2 a new target user plane functional entity
  • PSA2 can modify the destination address of the upstream IP packet to the network address of the local edge server, and forward it to the local edge server for processing (it should be noted that PSA2 also needs to receive the address translation sent by SMF Control instructions before address conversion processing can be performed).
  • PSA2 modifies the source address of the downlink IP packet to the network address of the target application server, and forwards it to the UE without passing through PSA1.
  • the PSA1 shown in Figure 2 can send the received uplink IP packet to the UL CL through the data channel between the received uplink IP packet and the UL CL, or PSA1 can also send the received uplink IP packet to the UL CL.
  • the packet is sent to SMF first, and then sent to UL CL by SMF.
  • the UL CL can modify the target address of the upstream IP packet to the network address of the local edge server, and forward it to the local edge server through PSA2 for processing (it should be noted that UL CL also needs to receive it
  • the address conversion control command sent by SMF can then be processed for address conversion).
  • the local edge server returns a downlink IP packet to PSA2
  • PSA2 the local edge server
  • UL CL modifies the source address of the downlink IP packet to the network address of the target application server and forwards it to the UE. There is no need to go through PSA1 again.
  • FIG. 5 shows a flowchart of a communication method based on edge computing according to an embodiment of the present application.
  • the communication method may be executed by SMF, and the communication method may be applied to the EC architecture shown in FIG. 1.
  • the communication method at least includes steps S510 to S530, which are described in detail as follows:
  • step S510 the SMF receives the network address of the target application server sent by the first user plane function entity.
  • the network address of the target application server is the destination address in the uplink IP packet received by the first user plane function entity.
  • the packet is sent by the user equipment.
  • the network address of the target application server is obtained by the user equipment by sending a DNS request to the DNS server, and then obtained from the DNS response returned by the DNS server.
  • step S520 the network address of the local edge server for responding to the uplink IP packet is determined according to the network address of the target application server.
  • the session management function entity may use steps S410 to S430 similar to those shown in FIG. 4 to determine the network address of the local edge server; or the session management function entity may also be based on the network address of the application server and The mapping relationship between the network addresses of the local edge server, the network address of the local edge server that has a mapping relationship with the network address of the target application server is used as the network address of the local edge server; or the session management function entity can also be based on the one shown in Figure 4
  • step S410 shown the domain name list corresponding to the network address of the target application server is determined, and then according to the domain name list, the network address of the edge server corresponding to the domain name list is used as the network address of the local edge server; or the session management function entity may also The target domain name list is determined based on the steps S410 and S420 shown in FIG.
  • the network address list of the edge server that has a mapping relationship with the target domain name list is used as the target domain name list.
  • the network address list of the local edge server in response to the upstream IP packet.
  • the closest to the user equipment and the communication delay with the user equipment can be selected from the multiple network addresses.
  • the network address of the smallest or lightest local edge server to improve the efficiency of edge communication.
  • an address conversion control instruction is sent to the first user plane functional entity, where the address conversion instruction is used to instruct the first user plane functional entity to modify the destination address of the uplink IP packet to the local edge server Network address and forwarded to the local edge server for processing.
  • the address conversion instruction is also used to instruct the first user plane function entity to modify the source address of the downlink IP packet to the target when receiving the downlink IP packet returned by the local edge server for the uplink IP packet The network address of the application server and forwarded to the user device.
  • the technical solution of the embodiment shown in FIG. 5 is applied to the EC architecture shown in FIG. 1.
  • the first user plane functional entity is the UPF (PSA) shown in FIG. All are implemented by UPF.
  • FIG. 6 shows a flowchart of a communication method based on edge computing according to an embodiment of the present application.
  • the communication method may be executed by SMF, and the communication method may be applied to the EC architecture shown in FIG. 2.
  • the communication method at least includes steps S610 to S630, which are described in detail as follows:
  • step S610 the network address of the target application server sent by the first user plane function entity is received, where the network address of the target application server is the destination address in the uplink IP packet received by the first user plane function entity, and the uplink IP packet It is sent by the user device.
  • the network address of the target application server is obtained by the user equipment by sending a DNS request to the DNS server, and then obtained from the DNS response returned by the DNS server.
  • step S620 the network address of the local edge server for responding to the uplink IP packet is determined according to the network address of the target application server.
  • the session management function entity may use steps S410 to S430 similar to those shown in FIG. 4 to determine the network address of the local edge server; or the session management function entity may also be based on the network address of the application server and The mapping relationship between the network addresses of the local edge server, the network address of the local edge server that has a mapping relationship with the network address of the target application server is used as the network address of the local edge server; or the session management function entity can also be based on the one shown in Figure 4
  • step S410 shown the domain name list corresponding to the network address of the target application server is determined, and then according to the domain name list, the network address of the edge server corresponding to the domain name list is used as the network address of the local edge server; or the session management function entity may also The target domain name list is determined based on the steps S410 and S420 shown in FIG.
  • the network address list of the edge server that has a mapping relationship with the target domain name list is used as the target domain name list.
  • the network address list of the local edge server in response to the upstream IP packet.
  • the closest to the user equipment and the communication delay with the user equipment can be selected from the multiple network addresses.
  • the network address of the smallest or lightest local edge server to improve the efficiency of edge communication.
  • step S630 an address conversion control instruction is sent to the second user plane function entity connected to the local edge server, and the address conversion control instruction is used to instruct the second user plane function entity to receive the uplink from the user equipment to the target application server.
  • the destination address of the received upstream IP packet is modified to the network address of the local edge server, and forwarded to the local edge server for processing.
  • the address translation control instruction is also used to instruct the second user plane function entity to modify the source address of the downlink IP packet to when receiving the downlink IP packet returned by the local edge server for the uplink IP packet The network address of the target application server and forwarded to the user device.
  • the technical solution of the embodiment shown in FIG. 6 is applied to the EC architecture shown in FIG. 2.
  • the first user plane functional entity is PSA1 shown in FIG. 2
  • the second user plane functional entity is PSA2 shown in FIG. .
  • the SMF may also send an instruction message to PSA1 to instruct PSA1 to forward the received uplink IP packet sent by the user equipment to the target application server to PSA2, and PSA2 will modify the destination address of the uplink IP packet It is the network address of the local edge server and forwarded to the local edge server for processing.
  • PSA2 modifies the source address of the downlink IP packet to the network address of the target application server and forwards it to the UE without passing through PSA1.
  • the SMF may also send an instruction message to the UL CL connected to the PSA2 to instruct the UL CL to send the data packet between the user equipment and the target application server to the PSA2 for forwarding processing.
  • PSA2 modifies the destination address of the uplink IP packet to the network address of the local edge server, and forwards it to the local edge server for processing.
  • PSA2 modifies the source address of the downlink IP packet to the network address of the target application server, and forwards it to the UE without passing through PSA1 again.
  • FIG. 7 shows a flowchart of a communication method based on edge computing according to an embodiment of the present application.
  • the communication method may be executed by SMF, and the communication method may be applied to the EC architecture shown in FIG. 2.
  • the communication method includes at least step S710 to step S730, which are described in detail as follows:
  • step S710 the network address of the target application server sent by the first user plane function entity is received, where the network address of the target application server is the destination address in the uplink IP packet received by the first user plane function entity, and the uplink IP packet It is sent by the user device.
  • the network address of the target application server is obtained by the user equipment by sending a DNS request to the DNS server, and then obtained from the DNS response returned by the DNS server.
  • step S720 the network address of the local edge server for responding to the uplink IP packet is determined according to the network address of the target application server.
  • the session management function entity may use steps S410 to S430 similar to those shown in FIG. 4 to determine the network address of the local edge server; or the session management function entity may also be based on the network address of the application server and The mapping relationship between the network addresses of the local edge server, the network address of the local edge server that has a mapping relationship with the network address of the target application server is used as the network address of the local edge server; or the session management function entity can also be based on the one shown in Figure 4
  • step S410 shown the domain name list corresponding to the network address of the target application server is determined, and then according to the domain name list, the network address of the edge server corresponding to the domain name list is used as the network address of the local edge server; or the session management function entity may also The target domain name list is determined based on the steps S410 and S420 shown in FIG.
  • the network address list of the edge server that has a mapping relationship with the target domain name list is used as the target domain name list.
  • the network address list of the local edge server in response to the upstream IP packet.
  • the closest to the user equipment and the communication delay with the user equipment can be selected from the multiple network addresses.
  • the network address of the smallest or lightest local edge server to improve the efficiency of edge communication.
  • step S730 an address conversion instruction is sent to the uplink classifier connected to the second user plane functional entity, and the address conversion control instruction is used to instruct the uplink classifier to, when receiving the uplink IP packet sent by the user equipment to the target application server, Modify the destination address of the received uplink IP packet to the network address of the local edge server, and forward it to the local edge server for processing through the second user plane functional entity.
  • the address translation control instruction is also used to instruct the upstream classifier to modify the source address of the downstream IP packet to the target application server when receiving the downstream IP packet returned by the local edge server for the upstream IP packet Network address and forwarded to the user’s device.
  • the technical solution of the embodiment shown in FIG. 7 is applied to the EC architecture shown in FIG. 2.
  • the first user plane functional entity is PSA1 shown in FIG. 2, and the second user plane functional entity is PSA2 shown in FIG. 2.
  • the uplink classifier is the UL CL shown in Figure 2.
  • the SMF may also send an instruction message to PSA1 to instruct PSA1 to forward the received uplink IP packet sent by the user equipment to the target application server to UL CL, and then UL CL will transfer the uplink IP packet
  • the destination address is modified to the network address of the local edge server, and forwarded to the local edge server through PSA2 for processing.
  • PSA2 forwards the downlink IP packet to UL CL, and then UL CL modifies the source address of the uplink IP packet to the network address of the target application server and forwards it To the UE, there is no need to go through PSA1.
  • the SMF may also send an instruction message to the UL CL to instruct the UL CL to send the data packet between the user equipment and the target application server to the PSA2 for forwarding processing.
  • the SMF may also send an instruction message to the UL CL to instruct the UL CL to send the data packet between the user equipment and the target application server to the PSA2 for forwarding processing.
  • UL CL after UL CL receives the uplink IP packet sent by the UE, it modifies the destination address of the uplink IP packet to the network address of the local edge server, and then sends it to PSA2, which then forwards it to the local edge server for processing.
  • PSA2 forwards the downlink IP packet to UL CL, and then UL CL modifies the source address of the downlink IP packet to the network address of the target application server and forwards it to the UE, which is also not required Go through PSA1 again.
  • the communication method based on edge computing includes the following steps:
  • step S801 the UE establishes a PDU session with PSA1 through SMF.
  • the network will allocate an IP address to the UE.
  • the UE initiates the process of establishing a PDU session with reference to section 4.3.2 of TS23.502 of the 3rd Generation Partnership Project (3rd Generation Partnership Project, 3GPP) protocol.
  • the SMF instructs PSA1 to query the local edge server address of the destination IP address of the upstream IP packet.
  • step S802 the UE obtains the IP address IPas of the AS through the DNS server.
  • the UE can send a DNS request.
  • PSA1 forwards the uplink IP packet to the target IP address, that is, the DNS server.
  • the DNS response feedback from the DNS server the downlink IP packet reaches PSA1 PSA1 determines the UE according to the destination address of the downlink IP packet, and then forwards it to the UE, and the UE can obtain the IP address IPas of the AS from it.
  • the DNS request may be based on the UDP protocol, the HTTPS protocol, or the TLS protocol.
  • step S803 the UE sends an uplink IP packet (source IPue, destination IPas, source port PORTue, destination port PORTas, transport layer protocol (such as TCP protocol)) to PSA1.
  • source IPue destination IPas, source port PORTue, destination port PORTas, transport layer protocol (such as TCP protocol)
  • Step S804 PSA1 sends a reverse domain name query request to the DNS server.
  • SMF According to the command in S801 that SMF requires PSA1 to query the local edge server address of the destination IP address of the upstream IP packet, it sends a reverse domain name query request to the DNS server.
  • the reverse domain name query request contains the destination address of the upstream IP packet. That is, the IP address IPas of the AS.
  • step S805 the DNS server returns a reverse domain name query response to the PSA1, and the reverse domain name query response includes the domain name list Asx.
  • Step S806 PSA1 sends an SRV query request to the edge DNS server.
  • PSA1 sends an SRV query request to the edge DNS server.
  • the SRV query request includes the domain name A, the destination port PORTas, and the transport layer protocol used by the upstream IP packet.
  • the transport layer protocol is obtained from the Protocol field in the upstream IP packet header, such as the TCP protocol).
  • Step S807 the edge DNS server returns an SRV query response to PSA1.
  • the edge DNS server returns an SRV query response for each item A to the PSA1, and the SRV query response contains the domain name (L-AS domain name) of the local edge server.
  • step S806 and step S807 are based on each item in the domain name list Asx, the transport layer protocol used by the upstream IP packet, and the destination port number of the upstream IP packet to obtain the complete domain name.
  • For each item A send an SRV query request to the edge DNS server, and the edge DNS server will feed back the SRV query response for each item A's SRV query request.
  • SRV query By performing SRV query on each item in the domain name list Asx, if multiple complete domain names are queried, a domain name list (L-AS domain name list) containing multiple complete domain names can be obtained. Note that for some items, the query may return the domain name without corresponding local edge server.
  • Step S808 PSA1 sends an A or AAAA query request to the edge DNS server.
  • PSA1 sends the L-AS domain name to the edge DNS server (if multiple L-AS domain names form an L-AS domain name list, you need to use the same L-AS domain name for each item in the L-AS domain name list. Operation) A or AAAA query request. Among them, if IPue and IPas are IPv4, an A query request is initiated; if IPue and IPas are IPv6, an AAAA query request is initiated.
  • step S809 the edge DNS server returns an A or AAAA query response to PSA1.
  • the edge DNS server returns an A or AAAA query response containing the IP address of the local edge server (ie, L-IPas) to the PSA1.
  • the A or AAAA query response can include an IP address list (L-IPas list). It is possible to obtain multiple L-IPas by separately querying the domain name list.
  • steps S806 to S809 can be implemented by the PSA1 directly interacting with the edge DNS server, or can be implemented by the PSA1 interacting with the edge DNS server through SMF (that is, forwarding by SMF).
  • PSA1 reports the IPas and L-IPas lists, and SMF determines the final L-IPas.
  • PSA1 reports the destination IP address IPas and the L-IPas obtained from the query to the SMF through the N4 interface (if an L-IPas is obtained from the query, it also needs to be reported), so that the SMF can select the one closest to the UE or the communication delay between the UE and the UE. , Or L-IPas with the lightest load.
  • step S811 the SMF sends an N4 session command to PSA1.
  • SMF sends an N4 session command to PSA1 to enable PSA1 to perform NAT (Network Address Translation) conversion and data forwarding operations of the destination IP address, that is, to detect and replace the destination IP address IPas of the UE's uplink IP packet with L -IPas and continue uplink forwarding; detect and replace the source IP address L-IPas of the UE's downlink IP packet with IPas and continue downlink forwarding.
  • NAT Network Address Translation
  • step S812 the PSA1 detects and converts the destination IP address IPas of the uplink IP packet sent by the UE into L-IPas according to the SMF command.
  • step S813 the PSA1 sends an upstream IP packet (source IPue, destination L-IPas, source port PORTue, destination port PORTas, transport layer protocol) to the edge server EAS.
  • an upstream IP packet source IPue, destination L-IPas, source port PORTue, destination port PORTas, transport layer protocol
  • PSA1 sends the upstream IP packet (source IPue, destination L-IPas, source port PORTue, destination port PORTas, transport layer protocol) converted from the destination IP address to the edge server EAS through the N6 interface according to the SMF command.
  • upstream IP packet source IPue, destination L-IPas, source port PORTue, destination port PORTas, transport layer protocol
  • step S814 EAS returns a downlink IP packet (source L-IPas, destination IPue, source port PORTas, destination port PORTue, transport layer protocol) to PSA1 for the uplink IP packet.
  • step S815 the PSA1 detects and converts the source IP address L-IPas in the downstream IP packet into IPas according to the SMF command.
  • Step S816, PSA1 sends a downlink IP packet (source IPas, destination IPue, source port PORTas, destination port PORTue, transport layer protocol) to the UE.
  • source IPas, destination IPue, source port PORTas, destination port PORTue, transport layer protocol source IPas, destination IPue, source port PORTas, destination port PORTue, transport layer protocol
  • the PSA1 sends the downstream IP packet (source IPas, destination IPue, source port PORTas, destination port PORTue, transport layer protocol) converted from the source IP address to the UE according to the SMF command.
  • source IPas, destination IPue, source port PORTas, destination port PORTue, transport layer protocol converted from the source IP address to the UE according to the SMF command.
  • steps S812 and S815 not only perform address conversion processing on the uplink IP packet received in step S803, but also perform address conversion processing on all subsequent data packets between the UE and the AS.
  • step S812 the conversion of the source port PORTue can also be added, and the source port value PORTue and the destination IPas address in the detected and converted upstream IP packet have changed.
  • step S815 The reverse NAT conversion is to detect and convert the destination port and source L-IPas address in the downstream IP packet into PORTue and IPas.
  • PSA1 detects that the destination IP of the uplink IP packet is IPas, and then Replace the destination IP address IPas of the upstream IP packet with L-IPas, replace the source port value PORTue with the set identification value (such as PortIDValue1), and then replace the converted upstream IP packet (source IPue, destination L-IPas, source port PortIDValue1) , Destination port PORTas, transport layer protocol) is sent to the edge server EAS through the N6 interface.
  • PSA1 When PSA1 receives the downstream IP packet returned by EAS (source L-IPas, destination IPue, source port PORTas, destination port PortIDValue1, transport layer protocol), it detects that the destination port value of the downstream IP packet is PortIDValue1 and the destination IP is IPue , And then replace the destination port value of the downstream IP packet with PORTue, replace the source IP address L-IPas in the downstream IP packet with IPas, and then replace the converted downstream IP packet (source IPas, destination IPue, source port PORTas, destination Port PORTue, transport layer protocol) is sent to the UE.
  • EAS source L-IPas, destination IPue, source port PORTas, destination port PortIDValue1, transport layer protocol
  • step S900 is used to replace steps S804 to S810 shown in Fig. 8.
  • Step S900 includes the following steps:
  • step S9001 PSA1 sends an N4 session report to SMF.
  • PSA1 sends an N4 session report to SMF, reporting the destination address IPas contained in the upstream IP packet.
  • step S9002 the SMF detects and maps the destination address IPas to the EAS IP address L-IPas according to the configuration information.
  • SMF can directly map IPas to L-IPas according to the configuration information on SMF; or SMF can perform the query process similar to step S804 and step S805 shown in Figure 8, and then according to the configuration on SMF The information is mapped to obtain L-IPas; or the SMF can perform a query process similar to that shown in step S804 to step S807 shown in FIG. 8, and then map to obtain L-IPas according to the configuration information on the SMF.
  • the SMF can also perform the query process similar to that shown in step S804 to step S809 shown in FIG. 8 to obtain L-IPas.
  • the communication method based on edge computing includes the following steps:
  • Step S1001 which includes steps S801-S810 shown in FIG. 8 or steps S801-S900 shown in FIG. 9. That is, it detects and determines L-IPas based on the uplink IP packets (source IPue, destination IPas, source port PORTue, destination port PORTas, transport layer protocol) sent by the UE.
  • uplink IP packets source IPue, destination IPas, source port PORTue, destination port PORTas, transport layer protocol
  • step S1002 it is determined that it is necessary to access the EAS through UL CL, and the UPF with UL CL function is selected and inserted.
  • SMF determines that it needs to access EAS through UL CL according to the determined L-IPas address, and selects and inserts a UPF with UL CL function.
  • step S1003 it is determined that it is necessary to access the EAS through UL CL, and the UPF with PSA function, namely PSA2, is selected and inserted.
  • SMF determines that it needs to access EAS through UL CL, and selects and inserts a UPF with PSA function, namely PSA2.
  • step S1002 and step S1003 please refer to the section 4.3.5.4 Addition of additional PDU Session Anchor and Branching Point or UL CL (adding additional PDU session anchor and branch point or UL-CL) in the 3GPP standard TS23.502.
  • Step S1004 PSA1 forwards the UE uplink IP packet to PSA2.
  • Step S1004 is to forward the uplink IP packets that are buffered on PSA1 and sent by the UE to the AS to PSA2.
  • Data Forwarding There are two mechanisms for Data Forwarding here. One is to establish a Data Forwarding tunnel (channel) between PSA1 and PSA2, which is directly sent from PSA1 to PSA2; the other method is to set up a Data Forwarding tunnel between PSA1 and PSA2; Two data forwarding tunnels are established between them, which are forwarded from PSA1 to SMF, and then from SMF to PSA2.
  • the data cached on PSA1 may be one IP data packet or multiple IP data packets.
  • step S1005 the SMF sends an N4 session command to the UL CL, so that the UL CL forwards the data packet from the UE to the AS to PSA2.
  • step S1006 the SMF sends an N4 session command to the PSA2, so that the PSA2 performs NAT conversion and commutation operations.
  • it means detecting and replacing the destination IP address IPas of the UE's uplink IP packet with L-IPas and continuing the uplink forwarding; detecting and replacing the source IP address L-IPas of the UE's downlink IP packet with IPas and continuing the downlink forwarding.
  • Step S1007 detecting and converting the destination IP address IPas of the upstream IP packet into L-IPas.
  • PSA2 detects and converts the destination IP address IPas of the upstream IP packet to L-IPas according to the SMF command.
  • Step S1008 Send an uplink IP packet to EAS.
  • PSA2 sends the upstream IP packet (source IPue, destination L-IPas, source port PORTue, destination port PORTas, and transport layer protocol) converted from the destination IP address to EAS according to the SMF command.
  • upstream IP packet source IPue, destination L-IPas, source port PORTue, destination port PORTas, and transport layer protocol
  • step S1009 EAS returns a downlink IP packet to PSA2.
  • EAS returns downstream IP packets (source L-IPas, destination IPue, source port PORTas, destination port PORTue, transport layer protocol) to PSA2 for upstream IP packets.
  • Step S1010 detecting and converting the source IP address L-IPas of the downstream IP packet into IPas.
  • the PSA2 detects and converts the source IP address L-IPas of the downstream IP packet into IPas according to the SMF command.
  • Step S1011 Send the downlink IP packet to the UE.
  • the PSA2 sends the downstream IP packet (source IPas, destination IPue, source port PORTas, destination port PORTue, transport layer protocol) converted from the source IP address to the UE according to the SMF command.
  • source IPas, destination IPue, source port PORTas, destination port PORTue, transport layer protocol converted from the source IP address to the UE according to the SMF command.
  • the subsequent PSA2 will perform a reverse NAT conversion operation between the UE and EAS. That is, detect and convert the destination IP address IPas in the uplink IP packet sent by the UE to the AS to L-IPas and then send it to EAS, and detect and convert the source IP address L-IPas in the downlink IP packet fed back by EAS to IPas Sent to the UE.
  • the conversion of the source port PORTue can also be added, and the source port value PORTue and the destination in the detected and converted upstream IP packet IPas addresses have all changed.
  • the destination port and source L-IPas addresses in the downstream IP packets are converted into PORTue and IPas.
  • the edge computing-based communication method includes the following steps:
  • Step S1101 Detect and determine L-IPas based on the uplink IP packet sent by the UE.
  • This step S1101 includes steps S801-S810 shown in FIG. 8 or steps S801-S900 shown in FIG. 9. That is, it detects and determines L-IPas based on the uplink IP packets (source IPue, destination IPas, source port PORTue, destination port PORTas, transport layer protocol) sent by the UE.
  • step S1102 the SMF determines that it needs to access the EAS through UL CL, and selects and inserts a UPF with UL CL function.
  • SMF determines that it needs to access EAS through UL CL, and selects and inserts a UPF with UL CL function.
  • step S1103 the SMF determines that it needs to access the EAS through UL CL, and selects and inserts a UPF (PSA2) with PSA function.
  • PSA2 UPF
  • SMF determines that it needs to access EAS through UL CL, and selects and inserts a UPF with PSA function, namely PSA2.
  • step S1102 and step S1103 please refer to the section 4.3.5.4 Addition of additional PDU Session Anchor and Branching Point or UL CL (adding additional PDU session anchor and branch point or UL-CL) in the 3GPP standard TS23.502.
  • step S1104 the PSA1 forwards the uplink IP packet of the UE to the UL CL.
  • step S1104 is to forward the uplink IP packet data buffered on the PSA1 and sent to the AS by the UE to the UL CL.
  • Data Forwarding There are two mechanisms for Data Forwarding here. One is to establish a Data Forwarding tunnel between PSA1 and UL CL, which is directly sent from PSA1 to UL CL; the other method is to set up a Data Forwarding tunnel between PSA1 and UL CL; Two data forwarding tunnels are established between them, which are forwarded by PSA1 to SMF, and then forwarded by SMF to UL CL.
  • the data cached on PSA1 may be one IP data packet or multiple IP data packets.
  • step S1105 the SMF sends an N4 session command to the UL CL, so that the UL CL forwards the data packet from the UE to the AS to PSA2.
  • Step S1106 The SMF sends an N4 session command to the UL CL, so that the UL CL performs NAT translation and commutation operations.
  • Step S1107 detecting and converting the destination IP address IPas of the upstream IP packet into L-IPas.
  • UL CL detects and converts the destination IP address IPas of the upstream IP packet to L-IPas according to the SMF command.
  • Step S1108 Send the upstream IP packet converted from the destination IP address to PSA2, and PSA2 forwards it to EAS.
  • UL CL sends the converted upstream IP packet (source IPue, destination L-IPas, source port PORTue, destination port PORTas, and transport layer protocol) after the destination IP address conversion to PSA2 according to the SMF command, and then forwards it to EAS by PSA2.
  • source IPue destination L-IPas, source port PORTue, destination port PORTas, and transport layer protocol
  • Step S1109 EAS returns a downlink IP packet to PSA2, and the downlink IP packet is forwarded by PSA2 to UL CL.
  • EAS returns a downlink IP packet (source L-IPas, destination IPue, source port PORTas, destination port PORTue, transport layer protocol) to PSA2 for uplink IP packets, and the downlink IP packet is forwarded by PSA2 to UL CL.
  • source L-IPas destination IPue
  • source port PORTas source port PORTue
  • transport layer protocol transport layer protocol
  • Step S1110 detecting and converting the source IP address L-IPas of the downstream IP packet into IPas.
  • UL CL detects and converts the source IP address L-IPas of the downstream IP packet into IPas according to the SMF command.
  • Step S1111 Send the downlink IP packet converted from the source IP address to the UE.
  • UL CL sends the downstream IP packets (source IPas, destination IPue, source port PORTas, destination port PORTue, transport layer protocol) converted from the source IP address to the UE according to the SMF command.
  • the subsequent UL CL will perform a reverse NAT translation operation between the UE and EAS. That is, it detects and converts the destination IP address IPas in the uplink IP packet sent by the UE to the AS to L-IPas and then sends it to PSA2, which is forwarded to EAS by PSA2.
  • the source IP address L-IPas is converted to IPas and sent to the UE.
  • the conversion of the source port PORTue can also be added, and the source port value PORTue in the detected and converted upstream IP packet The destination IPas address has changed.
  • the reverse NAT conversion of the downstream IP packet is to detect and convert the destination port and source IP address L-IPas in the downstream IP packet to PORTue and IPas.
  • Fig. 12 shows a block diagram of a communication device based on edge computing according to an embodiment of the present application.
  • the communication device may be set inside a user plane functional entity.
  • a communication device 1200 based on edge computing includes: a first receiving unit 1202, a first determining unit 1204, and a first sending unit 1206.
  • the first receiving unit 1202 is configured to receive an uplink IP packet sent by the user equipment, and the destination address of the uplink IP packet is the network address of the target application server; the first determining unit 1204 is configured to receive the network address of the target application server according to the network address of the target application server. , Determine the network address of the local edge server used to respond to the uplink IP packet; the first sending unit 1206 is configured to modify the destination address of the uplink IP packet to the network address of the local edge server, and forward it to the The local edge server performs processing.
  • the first determining unit 1204 is configured to: query the domain name list corresponding to the network address of the target application server according to the network address of the target application server; according to the domain name list, the uplink IP address The transport layer protocol used by the packet and the destination port contained in the upstream IP packet are queried to obtain the corresponding target domain name list; the network address list of the local edge server is queried based on the target domain name list to obtain based on the network address list The network address of the local edge server used to respond to the uplink IP packet.
  • the first determining unit 1204 is configured to initiate a service record SRV query to the edge domain name system DNS server according to the domain name list, the transport layer protocol used by the uplink IP packet, and the destination port To obtain the target domain name list; query the edge DNS server to obtain the network address list of the local edge server based on the target domain name list.
  • the first determining unit 1204 is configured to: report the network address list and the network address of the target application server to the session management function entity, so that the session management function entity is The network address of the local edge server that is used to respond to the uplink IP packet is selected from the network address list.
  • the first determining unit 1204 is configured to: report the network address of the target application server to the session management function entity, so that the session management function entity can be based on the network address of the target application server. Determine the network address of the local edge server; or query the domain name list corresponding to the network address of the target application server according to the network address of the target application server, and report the domain name list to the session management function entity, so that the The session management function entity determines the network address of the local edge server according to the domain name list.
  • the first receiving unit 1202 is further configured to: receive an address translation control instruction sent by the session management function entity, where the address translation control instruction is used to instruct to send the user equipment to the target application
  • the destination address of the upstream IP packet of the server is modified to the network address of the local edge server.
  • the address translation control instruction is further used to instruct to modify the source address of the downstream IP packet returned by the local edge server for the upstream IP packet to the network address of the target application server;
  • the first receiving unit 1202 is further configured to: receive a downlink IP packet returned by the local edge server for the uplink IP packet, where the source address of the downlink IP packet is the network address of the local edge server; and the first sending unit 1206 It is also configured to: modify the source address of the downlink IP packet to the network address of the target application server, and forward it to the user equipment.
  • the first sending unit 1206 is further configured to: before forwarding to the local edge server for processing, modify the source port value of the upstream IP packet to a set identification value, and record all The corresponding relationship between the source port value of the upstream IP packet and the set identifier value; upon receiving the downstream IP packet returned by the local edge server, if the destination port value of the downstream IP packet and the set identifier If the values match, the destination port value of the downstream IP packet is modified to the source port value of the upstream IP packet.
  • the first sending unit 1206 is configured to: directly send the uplink IP packet to the target User plane functional entity, so that the target user plane functional entity modifies the destination address of the uplink IP packet to the network address of the local edge server, and forwards it to the local edge server for processing; or
  • the IP packet is sent to the target user plane function entity through the session management function entity, so that the target user plane function entity modifies the destination address of the uplink IP packet to the network address of the local edge server and forwards it to all The local edge server performs processing.
  • the first sending unit 1206 is configured to: directly send the uplink IP packet to the uplink classifier , So that the upstream classifier modifies the destination address of the upstream IP packet to the network address of the local edge server, and forwards it to the local edge server through the target user plane function entity connected to the local edge server Process; or send the uplink IP packet to the uplink classifier through the session management function entity, so that the uplink classifier can modify the destination address of the uplink IP packet to the network address of the local edge server, and pass The target user plane function entity connected to the local edge server is forwarded to the local edge server for processing.
  • Fig. 13 shows a block diagram of a communication device based on edge computing according to an embodiment of the present application.
  • the communication device may be set inside a session management functional entity.
  • a communication device 1300 based on edge computing includes: a second receiving unit 1302, a second determining unit 1304, and a second sending unit 1306.
  • the second receiving unit 1302 is configured to receive the network address of the target application server sent by the first user plane function entity, where the network address of the target application server is in the uplink IP packet received by the first user plane function entity Destination address, the uplink IP packet is sent by the user equipment;
  • the second determining unit 1304 is configured to determine the network address of the local edge server used to respond to the uplink IP packet according to the network address of the target application server;
  • the second sending unit 1306 is configured to send an address translation control instruction to the first user plane functional entity, where the address translation instruction is used to instruct the first user plane functional entity to modify the destination address of the uplink IP packet to the The network address of the local edge server is forwarded to the local edge server for processing.
  • the address translation instruction is also used to instruct the first user plane function entity to transfer the downlink IP packet returned by the local edge server for the uplink IP packet.
  • the source address of the downlink IP packet is modified to the network address of the target application server and forwarded to the user equipment.
  • the second determining unit 1304 is configured to query the domain name list corresponding to the network address of the target application server according to the network address of the target application server; The transport layer protocol used by the packet and the destination port included in the uplink IP packet are searched to obtain a list of target domain names that can respond to the uplink IP packet; and the network address list of the local edge server is obtained based on the search of the target domain name list.
  • the second determining unit 1304 is configured to: based on the mapping relationship between the network address of the application server and the network address of the local edge server, there is a mapping relationship with the network address of the target application server.
  • the network address of the local edge server is used as the network address of the local edge server.
  • the second determining unit 1304 is configured to query the domain name list corresponding to the network address of the target application server according to the network address of the target application server;
  • the network address of the edge server in the domain name list is used as the network address of the local edge server.
  • the second determining unit 1304 is configured to query the domain name list corresponding to the network address of the target application server according to the network address of the target application server;
  • the transport layer protocol used by the packet and the destination port contained in the upstream IP packet are queried to obtain the corresponding target domain name list; based on the mapping relationship between the domain name and the network address of the edge server, there will be a mapping relationship with the target domain name list
  • the network address list of the edge server is used as the network address list of the local edge server in response to the uplink IP packet.
  • the second determining unit 1304 is further configured to: if the network address list of the local edge server contains multiple network addresses, select a distance from the user from the multiple network addresses.
  • Fig. 14 shows a block diagram of a communication device based on edge computing according to an embodiment of the present application.
  • the communication device may be set inside a session management functional entity.
  • a communication device 1400 based on edge computing includes: a third receiving unit 1402, a third determining unit 1404, and a third sending unit 1406.
  • the third receiving unit 1402 is configured to receive the network address of the target application server sent by the first user plane function entity, where the network address of the target application server is in the uplink IP packet received by the first user plane function entity Destination address, the uplink IP packet is sent by the user equipment;
  • the third determining unit 1404 is configured to determine the network address of the local edge server used to respond to the uplink IP packet according to the network address of the target application server;
  • the third sending unit 1406 is configured to send an address translation control instruction to a second user plane functional entity connected to the local edge server, where the address translation control instruction is used to instruct the second user plane functional entity to send an address from the user equipment When sending the uplink IP packet to the target application server, modify the destination address of the received uplink IP packet to the network address of the local edge server, and forward it to the local edge server for processing.
  • the address translation control instruction is also used to instruct the second user plane function entity to transfer all the downstream IP packets returned by the local edge server for the upstream IP packets.
  • the source address of the downlink IP packet is modified to the network address of the target application server and forwarded to the user equipment.
  • the third sending unit 1406 is further configured to send an instruction message to the first user plane function entity to instruct the first user plane function entity to send the received user equipment
  • the uplink IP packet for the target application server is forwarded to the second user plane functional entity.
  • the third sending unit 1406 is further configured to send an instruction message to the uplink classifier connected to the second user plane functional entity to instruct the uplink classifier to connect the user equipment with The data packets between the target application servers are sent to the second user plane functional entity for forwarding processing.
  • Fig. 15 shows a block diagram of a communication device based on edge computing according to an embodiment of the present application.
  • the communication device may be set inside a session management functional entity.
  • a communication device 1500 based on edge computing includes: a fourth receiving unit 1502, a fourth determining unit 1504, and a fourth sending unit 1506.
  • the fourth receiving unit 1502 is configured to receive the network address of the target application server sent by the first user plane function entity, where the network address of the target application server is in the uplink IP packet received by the first user plane function entity Destination address, the uplink IP packet is sent by the user equipment;
  • the fourth determining unit 1504 is configured to determine the network address of the local edge server used to respond to the uplink IP packet according to the network address of the target application server;
  • the four sending unit 1506 is configured to send an address conversion instruction to the uplink classifier connected to the second user plane functional entity, where the address conversion control instruction is used to instruct the uplink classifier to send the user equipment to the target
  • the address translation control instruction is further used to instruct the uplink classifier to transfer the downlink IP packet to the uplink IP packet when it receives the downlink IP packet returned by the local edge server.
  • the source address of the packet is modified to the network address of the target application server and forwarded to the user equipment.
  • the fourth sending unit 1506 is further configured to send an instruction message to the first user plane function entity to instruct the first user plane function entity to send the received user equipment
  • the uplink IP packet for the target application server is forwarded to the uplink classifier.
  • the fourth sending unit 1506 is further configured to send an instruction message to the uplink classifier to instruct the uplink classifier to transfer data between the user equipment and the target application server The packet is sent to the second user plane functional entity for forwarding processing.
  • Fig. 16 shows a schematic structural diagram of a computer system suitable for implementing an electronic device according to an embodiment of the present application.
  • the computer system 1600 includes a central processing unit (Central Processing Unit, CPU) 1601, which can be loaded to a random storage unit according to a program stored in a read-only memory (Read-Only Memory, ROM) 1602 or from the storage part 1608.
  • Access memory (Random Access Memory, RAM) 1603 programs to execute various appropriate actions and processing, for example, execute the methods described in the foregoing embodiments.
  • RAM 1603 various programs and data required for system operation are also stored.
  • the CPU 1601, the ROM 1602, and the RAM 1603 are connected to each other through a bus 1604.
  • An Input/Output (I/O) interface 1605 is also connected to the bus 1604.
  • the following components are connected to the I/O interface 1605: input part 1606 including keyboard, mouse, etc.; including output part 1607 such as cathode ray tube (Cathode Ray Tube, CRT), liquid crystal display (LCD), etc., and speakers, etc. ; A storage part 1608 including a hard disk, etc.; and a communication part 1609 including a network interface card such as a LAN (Local Area Network) card and a modem.
  • the communication section 1609 performs communication processing via a network such as the Internet.
  • the driver 1610 is also connected to the I/O interface 1605 as needed.
  • a removable medium 1611 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 1610 as needed, so that the computer program read from it is installed into the storage portion 1608 as needed.
  • the process described above with reference to the flowchart can be implemented as a computer software program.
  • the embodiments of the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a computer program for executing the method shown in the flowchart.
  • the computer program may be downloaded and installed from the network through the communication part 1609, and/or installed from the removable medium 1611.
  • CPU central processing unit
  • the computer-readable medium shown in the embodiment of the present application may be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two.
  • the computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the above.
  • Computer-readable storage media may include, but are not limited to: electrical connections with one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable removable Erasable Programmable Read Only Memory (EPROM), flash memory, optical fiber, portable compact disk read-only memory (Compact Disc Read-Only Memory, CD-ROM), optical storage device, magnetic storage device, or any suitable of the above The combination.
  • the computer-readable storage medium may be any tangible medium that contains or stores a program, and the program may be used by or in combination with an instruction execution system, apparatus, or device.
  • a computer-readable signal medium may include a data signal propagated in a baseband or as a part of a carrier wave, and a computer-readable computer program is carried therein.
  • This propagated data signal can take many forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing.
  • the computer-readable signal medium may also be any computer-readable medium other than the computer-readable storage medium.
  • the computer-readable medium may send, propagate, or transmit the program for use by or in combination with the instruction execution system, apparatus, or device .
  • the computer program contained on the computer-readable medium can be transmitted by any suitable medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.
  • each block in the flowchart or block diagram may represent a module, program segment, or part of the code, and the above-mentioned module, program segment, or part of the code includes one or more executables for realizing the specified logic function. instruction.
  • the functions marked in the block may also occur in a different order from the order marked in the drawings. For example, two blocks shown in succession can actually be executed substantially in parallel, or they can sometimes be executed in the reverse order, depending on the functions involved.
  • each block in the block diagram or flowchart, and the combination of blocks in the block diagram or flowchart can be implemented by a dedicated hardware-based system that performs the specified functions or operations, or can be implemented by It is realized by a combination of dedicated hardware and computer instructions.
  • the units described in the embodiments of the present application may be implemented in software or hardware, and the described units may also be provided in a processor. Among them, the names of these units do not constitute a limitation on the unit itself under certain circumstances.
  • the embodiments of the present application also provide a computer-readable medium.
  • the computer-readable medium may be included in the electronic device described in the foregoing embodiment; or it may exist alone without being assembled into the electronic device.
  • the above-mentioned computer-readable medium carries one or more programs, and when the above-mentioned one or more programs are executed by an electronic device, the electronic device realizes the method described in the above-mentioned embodiment.
  • modules or units of the device for action execution are mentioned in the above detailed description, this division is not mandatory.
  • the features and functions of two or more modules or units described above may be embodied in one module or unit.
  • the features and functions of a module or unit described above can be further divided into multiple modules or units to be embodied.
  • the example embodiments described here can be implemented by software, or can be implemented by combining software with necessary hardware. Therefore, the technical solution according to the embodiments of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, U disk, mobile hard disk, etc.) or on the network , Including several instructions to make a computing device (which can be a personal computer, a server, a touch terminal, or a network device, etc.) execute the method according to the embodiment of the present application.
  • a non-volatile storage medium which can be a CD-ROM, U disk, mobile hard disk, etc.
  • Including several instructions to make a computing device which can be a personal computer, a server, a touch terminal, or a network device, etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请的实施例提供了一种基于边缘计算的通信方法、装置、计算机存储介质及电子设备。该基于边缘计算的通信方法包括：接收用户设备发送的上行网际互连协议(IP)包，所述上行IP包的目的地址为目标应用服务器的网络地址；根据所述目标应用服务器的网络地址，确定用于响应所述上行IP包的本地边缘服务器的网络地址；将所述上行IP包的目的地址修改为所述本地边缘服务器的网络地址，并转发至所述本地边缘服务器进行处理。

Description

基于边缘计算的通信方法、装置、存储介质及电子设备
相关申请的交叉引用
本申请基于申请号为202010179051.0、申请日为2020年03月15日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本申请涉及计算机及通信技术领域，尤其涉及一种基于边缘计算的通信方法、装置、计算机存储介质及电子设备。
背景技术
边缘计算(Edge Computing，EC)是将应用服务器(Application Server，AS)部署到离用户设备(User Equipment，UE)近的位置，即通过部署距离UE位置较近的边缘应用服务器(Edge Application server，EAS)，从而实现UE与AS的通信时延最小化。
然而，为了保证UE能够访问本地的EAS，相关技术中的方案通常需要修改或者增强UE或AS，这种方案具有较大的局限性。
发明内容
本申请实施例提供了一种基于边缘计算的通信方法、装置、计算机存储介质及电子设备，能够保证无需修改或增强UE或AS的前提下，实现UE对EAS的访问。
本申请实施例提供了一种基于边缘计算的通信方法，包括：接收用户设备发送的上行网际互连协议(Internet Protocol，IP)包，所述上行IP包的目的地址为目标应用服务器的网络地址；根据所述目标应用服务器的网络地址，确定用于响应所述上行IP包的本地边缘服务器的网络地址；将所述上行IP包的目的地址修改为所述本地边缘服务器的网络地址，并转发至所述本地边缘服务器进行处理。
本申请实施例还提供了一种基于边缘计算的通信方法，包括：接收第一用户面功能实体发送的目标应用服务器的网络地址，所述目标应用服务器的网络地址是所述第一用户面功能实体接收到的上行IP包中的目的地址，所述上行IP包是由用户设备发送的；根据所述目标应用服务器的网络地址，确定用于响应所述上行IP包的本地边缘服务器的网络地址；向所述第一用户面功能实体发送地址转换控制指令，所述地址转换指令用于指示所述第一用户面功能实体将所述上行IP包的目的地址修改为所述本地边缘服务器的网络地址，并转发至所述本地边缘服务器进行处理。
本申请实施例还提供了一种基于边缘计算的通信方法，包括：接收第一用户面功能实体发送的目标应用服务器的网络地址，所述目标应用服务器的网络地址是所述第一用户面功能实体接收到的上行IP包中的目的地址，所述上行IP包是由用户设备发送的；根据所述目标应用服务器的网络地址，确定用于响应所述上行IP包的本地边缘服务器的网络地址；向与本地边缘服务器相连的第二用户面功能实体发送地址转换控制指令，所述地址转换控制指令用于指示所述第二用户面功能实体在接收到所述用户设备发送给所述目标应用服务器的上行IP包时，将接收到的上行IP包的目的地址修改为所述本 地边缘服务器的网络地址，并转发给所述本地边缘服务器进行处理。
本申请实施例还提供了一种基于边缘计算的通信方法，包括：接收第一用户面功能实体发送的目标应用服务器的网络地址，所述目标应用服务器的网络地址是所述第一用户面功能实体接收到的上行IP包中的目的地址，所述上行IP包是由用户设备发送的；根据所述目标应用服务器的网络地址，确定用于响应所述上行IP包的本地边缘服务器的网络地址；向连接至第二用户面功能实体的上行分类器发送地址转换指令，所述地址转换控制指令用于指示所述上行分类器在接收到所述用户设备发送给所述目标应用服务器的上行IP包时，将接收到的上行IP包的目的地址修改为所述本地边缘服务器的网络地址，并通过所述第二用户面功能实体转发给所述本地边缘服务器进行处理。
本申请实施例还提供了一种基于边缘计算的通信装置，包括：第一接收单元，配置为接收用户设备发送的上行IP包，所述上行IP包的目的地址为目标应用服务器的网络地址；第一确定单元，配置为根据所述目标应用服务器的网络地址，确定用于响应所述上行IP包的本地边缘服务器的网络地址；第一发送单元，配置为将所述上行IP包的目的地址修改为所述本地边缘服务器的网络地址，并转发至所述本地边缘服务器进行处理。
本申请实施例还提供了一种基于边缘计算的通信装置，包括：第二接收单元，配置为接收第一用户面功能实体发送的目标应用服务器的网络地址，所述目标应用服务器的网络地址是所述第一用户面功能实体接收到的上行IP包中的目的地址，所述上行IP包是由用户设备发送的；第二确定单元，配置为根据所述目标应用服务器的网络地址，确定用于响应所述上行IP包的本地边缘服务器的网络地址；第二发送单元，配置为向所述第一用户面功能实体发送地址转换控制指令，所述地址转换指令用于指示所述第一用户面功能实体将所述上行IP包的目的地址修改为所述本地边缘服务器的网络地址，并转发至所述本地边缘服务器进行处理。
本申请实施例还提供了一种基于边缘计算的通信装置，包括：第三接收单元，配置为接收第一用户面功能实体发送的目标应用服务器的网络地址，所述目标应用服务器的网络地址是所述第一用户面功能实体接收到的上行IP包中的目的地址，所述上行IP包是由用户设备发送的；第三确定单元，配置为根据所述目标应用服务器的网络地址，确定用于响应所述上行IP包的本地边缘服务器的网络地址；第三发送单元，配置为向与本地边缘服务器相连的第二用户面功能实体发送地址转换控制指令，所述地址转换控制指令用于指示所述第二用户面功能实体在接收到所述用户设备发送给所述目标应用服务器的上行IP包时，将接收到的上行IP包的目的地址修改为所述本地边缘服务器的网络地址，并转发给所述本地边缘服务器进行处理。
本申请实施例还提供了一种基于边缘计算的通信装置，包括：第四接收单元，配置为接收第一用户面功能实体发送的目标应用服务器的网络地址，所述目标应用服务器的网络地址是所述第一用户面功能实体接收到的上行IP包中的目的地址，所述上行IP包是由用户设备发送的；第四确定单元，配置为根据所述目标应用服务器的网络地址，确定用于响应所述上行IP包的本地边缘服务器的网络地址；第四发送单元，配置为向连接至第二用户面功能实体的上行分类器发送地址转换指令，所述地址转换控制指令用于指示所述上行分类器在接收到所述用户设备发送给所述目标应用服务器的上行IP包时，将接收到的上行IP包的目的地址修改为所述本地边缘服务器的网络地址，并通过所述第二用户面功能实体转发给所述本地边缘服务器进行处理。
本申请实施例还提供了一种计算机可读介质，其上存储有计算机程序，所述计算机程序被处理器执行时实现如上述实施例中所述的基于边缘计算的通信方法。
本申请实施例还提供了一种电子设备，包括：一个或多个处理器；存储器，配置为 存储一个或多个程序，当所述一个或多个程序被所述一个或多个处理器执行时，使得所述一个或多个处理器实现如上述实施例中所述的基于边缘计算的通信方法。
应用本申请实施例提供的基于边缘计算的通信方法、装置、计算机存储介质及电子设备，通过由用户面功能实体(包含了作为上行分类器的用户名功能实体)对用户设备与目标应用服务器之间的数据包进行地址转换及转发处理，即将用户设备发送给目标应用服务器的上行IP包的目的地址修改为本地边缘服务器的网络地址后转发至本地边缘服务器，以及将本地边缘服务器针对上行IP包返回的下行IP包的源地址修改为目标应用服务器的网络地址并转发给用户设备，使得无需对用户设备和应用服务器进行修改或增强，就可以实现用户设备对本地边缘服务器的访问。
附图说明
图1为本申请实施例提供的实现边缘计算的一种架构图；
图2为本申请实施例提供的实现边缘计算的另一种架构图；
图3为本申请实施例提供的基于边缘计算的通信方法的流程图；
图4为本申请实施例提供的确定本地边缘服务器的网络地址的流程图；
图5为本申请实施例提供的基于边缘计算的通信方法的流程图；
图6为本申请实施例提供的基于边缘计算的通信方法的流程图；
图7为本申请实施例提供的基于边缘计算的通信方法的流程图；
图8为本申请实施例提供的基于边缘计算的通信方法的流程图；
图9为本申请实施例提供的基于边缘计算的通信方法的流程图；
图10为本申请实施例提供的基于边缘计算的通信方法的流程图；
图11为本申请实施例提供的基于边缘计算的通信方法的流程图；
图12为本申请实施例提供的基于边缘计算的通信装置的框图；
图13为本申请实施例提供的基于边缘计算的通信装置的框图；
图14为本申请实施例提供的基于边缘计算的通信装置的框图；
图15为本申请实施例提供的基于边缘计算的通信装置的框图；
图16为本申请实施例提供的电子设备的计算机系统的结构示意图。
具体实施方式
现在将参考附图更全面地描述示例实施方式。然而，示例实施方式能够以多种形式实施，且不应被理解为限于在此阐述的范例；相反，提供这些实施方式使得本申请将更加全面和完整，并将示例实施方式的构思全面地传达给本领域的技术人员。
此外，所描述的特征、结构或特性可以以任何合适的方式结合在一个或更多实施例中。在下面的描述中，提供许多具体细节从而给出对本申请的实施例的充分理解。然而，本领域技术人员将意识到，可以实践本申请的技术方案而没有特定细节中的一个或更多，或者可以采用其它的方法、组元、装置、步骤等。在其它情况下，不详细示出或描述公知方法、装置、实现或者操作以避免模糊本申请的各方面。
附图中所示的方框图仅仅是功能实体，不一定必须与物理上独立的实体相对应。即，可以采用软件形式来实现这些功能实体，或在一个或多个硬件模块或集成电路中实现这些功能实体，或在不同网络和/或处理器装置和/或微控制器装置中实现这些功能实体。
附图中所示的流程图仅是示例性说明，不是必须包括所有的内容和操作/步骤，也不是必须按所描述的顺序执行。例如，有的操作/步骤还可以分解，而有的操作/步骤可以合并或部分合并，因此实际执行的顺序有可能根据实际情况改变。
在本申请的一个实施例中，实现EC的两个架构如图1和图2所示。其中，图1是将用户面功能(User Plane Function，UPF)/PSA(分组数据单元(Protocol Data Unit，PDU)Session Anchor，PDU会话锚点)部署在接入网(Access Network，AN)附近，同时将EAS部署在与PSA相连的数据网络(Data Network，DN)。图2是在UPF/PSA1部署在中心位置时，在近AN处部署一个作为上行分类器/分支点(Uplink Classifier/Branching Point，UL CL/BP)的UPF，然后分出一个近AN的UPF/PSA2，将EAS部署在与PSA2相连的DN。
在图1和图2所示的实施例中，NEF是Network Exposure Function的简称，即为网络开放功能，Nnef是指NEF提供服务的接口，通过这个接口其它网络功能(Network Function，NF)发送Nnef服务请求消息给NEF，同时NEF通过这个接口回复请求或发送通报服务消息；PCF是Policy Control Function的简称，即策略控制功能，Npcf是指PCF提供服务的接口，通过这个接口其它NF发送Npcf服务请求消息给PCF，同时PCF通过这个接口回复请求与发送通报服务消息；AF是Application Function的简称，即为应用功能，Naf是指AF提供服务的接口，通过这个接口其它NF发送Naf消息给AF，同时AF通过这个接口回复请求与发送通报服务消息；AMF是Access and Mobility Management Function的简称，即接入和移动性管理功能，Namf是指AMF提供服务的接口，通过这个接口其它NF发送Namf消息给AMF，同时AMF通过这个接口回复请求与发送通报服务消息；SMF是Session Management Function的简称，即会话管理功能，Nsmf是指SMF提供服务的接口，通过这个接口其它NF发送Nsmf消息给SMF，同时SMF通过这个接口回复请求与发送通报服务消息。UE与AMF之间通过N1接口交互，AMF与AN之间通过N2接口交互，SMF与UPF之间通过N4接口交互，AN与UPF之间通过N3接口交互，UPF与DN之间通过N6接口交互，UPF与UPF之间通过N9接口交互。
为了实现UE对本地EAS的访问，相关技术中提出了很多方案，其基本策略是利用如下的一些方法：
1)UE在进行域名系统(Domain Name System，DNS)查询一个AS的网际互连协议(Internet Protocol，IP)地址时，UPF或SMF截获DNS的请求，然后回复一个指向本地EAS的IP地址的DNS响应，这样UE就可以建立到本地EAS的IP连接。但是这种方法的缺点在于若UE采用DNS over超文本传输安全协议(Hyper Text Transfer Protocol over Secure Socket Layer，HTTPS)/安全传输层协议(Transport Layer Security，TLS)等加密DNS交互消息的协议，因UPF不能感知加密的DNS交互协议，则这种方法不能工作。
2)PCF给UE发送一个用户设备路由选择策略(UE Route Selection Policy，URSP)Rule，在这个URSP Rule中，将UE在某一位置时要访问AS的规则指向一个本地EAS的IP，从而实现UE向EAS建立IP连接。但是，这种方法的缺点是需要增强URSP规则，并且需要修改UE的行为(即UE在一定位置时，才能使用这个规则)。
3)UE先访问中心节点的AS，然后AS根据UE所在的位置或UE的源IP地址所在的位置确定出EAS，然后通过应用层转向(Redirect)或通过AF请求用户面重路由的方式将UE的IP连接转向到本地EAS的IP上。但是，这种方法的缺点是需要增强AS的功能，或只对支持这些转向或支持通过AF请求用户面重路由的方式的AS才能适用。
由于UE的数量非常大，任何对于UE修改或增强的方案的部署成本都是非常高的。而对于修改或增加AS的方案，因为AS通常是由互联网公司或垂直行业的应用，他们不受运营商控制，因此他们可能不同意或不愿意修改或增强他们的AS。因此，本申请 的实施例提供了一种不需要修改UE或AS就可以是先UE对EAS的方案，这种方式不仅部署成本低，而且部署方式最为有效。
图3为本申请实施例提供的基于边缘计算的通信方法的流程图，该通信方法可以由用户面功能实体UPF来执行。参照图3所示，该通信方法至少包括步骤S310至步骤S330，详细介绍如下：
在步骤S310中，UPF接收用户设备发送的上行IP包，该上行IP包的目的地址为目标应用服务器的网络地址。
在本申请的一个实施例中，用户设备在发送上行IP包之前需要获取到目标应用服务器的网络地址。在一些实施例中，用户设备可以通过如下方式获取到目标应用服务器的网络地址：用户设备通过用户面功能实体向DNS服务器发送DNS的请求，然后由DNS服务器返回包含有目标应用服务器的网络地址的DNS响应，进而用户设备可以从该DNS响应中获取到目标应用服务器的网络地址。在一些实施例中，该DNS请求可以是基于用户数据报协议(User Datagram Protocol，UDP)协议、HTTPS协议或者是基于TLS协议的。
在本申请的一个实施例中，用户设备发送的上行IP包的源地址即为用户设备的IP地址，目的地址即为目标应用服务器的网络地址，源端口值即为用户设备的端口值，目的端口值即为目标应用服务器的端口值，所采用的传输层协议不作任何的限定，如是TCP、UDP协议等。
在步骤S320中，根据目标应用服务器的网络地址，确定用于响应上行IP包的本地边缘服务器的网络地址。
在本申请的一个实施例中，用户面功能实体确定本地边缘服务器的网络地址的方案可以如图4所示，包括如下步骤S410至步骤S430：
在步骤S410中，根据目标应用服务器的网络地址查询目标应用服务器的网络地址对应的域名列表。
在本申请的一个实施例中，用户面功能实体可以根据目标应用服务器的网络地址向DNS服务器发送反向域名查询请求，然后接收DNS服务器返回的反向域名查询响应，从该反向域名查询响应中获取到目标应用服务器的网络地址对应的域名列表。其中，该域名列表中包含有一个或者多个域名，多个指的是至少两个。
在步骤S420中，根据域名列表、上行IP包所使用的传输层协议和上行IP包中包含的目的端口查询得到对应的目标域名列表。
在本申请的一个实施例中，可以根据域名列表、所使用的传输层协议(如TCP或UDP协议，此协议可以从IP包头的Protocol域得到)和目的端口向边缘DNS服务器发起服务记录(Service Record，SRV)查询请求，然后基于从边缘DNS服务器反馈的SRV查询响应获取到目标域名列表。类似地，该目标域名列表中也可以包含有一个或者多个目标域名。其中，目标域名可以是全限定域名(Fully Qualified Domain Name，FQDN)，即同时带有主机名和域名的名称。
在步骤S430中，基于目标域名列表查询得到本地边缘服务器的网络地址列表，以基于所述网络地址列表获取用于响应所述上行IP包的本地边缘服务器的网络地址。
在本申请的一个实施例中，可以基于目标域名列表向边缘DNS服务器发起A(IPv4地址记录)或AAAA(IPv6地址记录)查询请求，以查询得到本地边缘服务器的网络地址列表。其中，若用户设备和目标应用服务器的IP地址为网际互联协议版本4(Internet Protocol version 4，IPv4)，则发起A查询请求；若用户设备和目标应用服务器的IP地址为网际互联协议版本6(Internet Protocol version 6，IPv6)，则发起AAAA查询请求。类似地，该网络地址列表中也可以包含有一个或者多个网络地址。
在本申请的一个实施例中，UPF在查询得到本地边缘服务器的网络地址列表之后，可以将该网络地址列表及目标应用服务器的网络地址通过N4接口上报给SMF，以供SMF从中选择一个用于响应上行IP包的本地边缘服务器的网络地址。比如可以选择距离用户设备最近的，或者选择与用户设备之间的通信时延最小的或者选择负载最轻的本地边缘服务器的网络地址，以提高边缘通信的效率。
在本申请的一个实施例中，用户面功能实体还可以将目标应用服务器的网络地址上报给会话管理功能实体，以使会话管理功能实体根据目标应用服务器的网络地址确定本地边缘服务器的网络地址。
在一些实施例中，会话管理功能实体可以采用类似于图4所示的步骤S410至步骤S430来确定本地边缘服务器的网络地址；或者会话管理功能实体也可以基于应用服务器的网络地址与本地边缘服务器的网络地址之间的映射关系，将与目标应用服务器的网络地址存在映射关系的本地边缘服务器的网络地址作为本地边缘服务器的网络地址；或者会话管理功能实体也可以基于图4中所示的步骤S410来确定出目标应用服务器的网络地址对应的域名列表，然后根据该域名列表，将对应于域名列表的边缘服务器的网络地址作为本地边缘服务器的网络地址；或者会话管理功能实体也可以基于图4中所示的步骤S410和步骤S420确定出目标域名列表，然后基于域名与边缘服务器的网络地址之间的映射关系，将与目标域名列表存在映射关系的边缘服务器的网络地址列表作为用于响应上行IP包的本地边缘服务器的网络地址列表。
在本申请的一个实施例中，用户面功能实体还可以根据目标应用服务器的网络地址查询目标应用服务器的网络地址对应的域名列表，然后将域名列表上报给会话管理功能实体，以使会话管理功能实体根据域名列表确定本地边缘服务器的网络地址。在一些实施例中，会话管理功能实体可以采用类似于图4中所示的步骤S420和步骤S430来确定本地边缘服务器的网络地址；或者会话管理功能实体也可以基于图4中所示的步骤S420确定出目标域名列表，然后基于域名与边缘服务器的网络地址之间的映射关系，将与目标域名列表存在映射关系的边缘服务器的网络地址列表作为用于响应上行IP包的本地边缘服务器的网络地址列表。
继续参照图3所示，在步骤S330中，基于地址转换控制指令，将上行IP包的目的地址修改为本地边缘服务器的网络地址，并转发至本地边缘服务器进行处理。
在本申请的一个实施例中，如果是图1所示的EC架构，那么UPF可以接收SMF发送的地址转换控制指令，该地址转换控制指令用于指示将用户设备发送给目标应用服务器的上行IP包的目的地址修改为本地边缘服务器的网络地址。同时，SMF发送的地址转换控制指令还用于指示UPF将本地边缘服务器针对上行IP包返回的下行IP包的源地址修改为目标应用服务器的网络地址；那么当UPF接收到本地边缘服务器针对上行IP包返回的下行IP包(该下行IP包的源地址为本地边缘服务器的网络地址)时，可以将下行IP包的源地址修改为目标应用服务器的网络地址，并转发至用户设备。其中，SMF可以通过N4接口向UPF发送地址转换控制指令。
在本申请的一个实施例中，在将上行IP包转发至本地边缘服务器进行处理之前，还可以进行源端口值的变换操作，即将上行IP包的源端口值修改为设定标识值，并记录上行IP包的源端口值与设定标识值的对应关系，然后在接收到本地边缘服务器返回的下行IP包时，若下行IP包的目的端口值与设定标识值相匹配，则将下行IP包的目的端口值修改为上行IP包的源端口值。这种方式可以解决用户设备进行多个并发连接时，多个并发连接之间不会出现混淆。
在本申请的一个实施例中，如果是图2所示的EC架构，即使用了一个新的连接至本地边缘服务器的目标用户面功能实体(即PSA2)时，那么当确定出本地边缘服务器 的网络地址之后，图2中所示的PSA1可以将接收到的上行IP包通过与PSA2之间的数据通道将PSA1接收到的上行IP包发送给PSA2，或者PSA1也可以将PSA1接收到的上行IP包先发给SMF，然后由SMF再发送给PSA2。当上行IP包到达PSA2之后，可以由PSA2将上行IP包的目标地址修改为本地边缘服务器的网络地址，并转发至本地边缘服务器进行处理(需要说明的是，PSA2也需要接收SMF发送的地址转换控制指令，然后才能够进行地址转换处理)。在这种系统架构下，当本地边缘服务器返回下行IP包到达PSA2之后，PSA2将下行IP包的源地址修改为目标应用服务器的网络地址，并转发至UE，不需要再经过PSA1。
在本申请的一个实施例中，如果是图2所示的EC架构，即使用了一个新的连接至本地边缘服务器的目标用户面功能实体(即PSA2)时，那么当确定出本地边缘服务器的网络地址之后，图2中所示的PSA1可以将接收到的上行IP包通过与UL CL之间的数据通道将接收到的上行IP包发送给UL CL，或者PSA1也可以将接收到的上行IP包先发给SMF，然后由SMF再发送给UL CL。当上行IP包到达UL CL之后，可以由UL CL将上行IP包的目标地址修改为本地边缘服务器的网络地址，并通过PSA2转发至本地边缘服务器进行处理(需要说明的是，UL CL也需要接收SMF发送的地址转换控制指令，然后才能够进行地址转换处理)。在这种系统架构下，当本地边缘服务器返回下行IP包到达PSA2后，由PSA2转发至UL CL，然后UL CL将下行IP包的源地址修改为目标应用服务器的网络地址，并转发至UE，同样不需要再经过PSA1。
图5示出了根据本申请的一个实施例的基于边缘计算的通信方法的流程图，该通信方法可以由SMF来执行，该通信方法可以应用于如图1所示的EC架构。参照图5所示，该通信方法至少包括步骤S510至步骤S530，详细介绍如下：
在步骤S510中，SMF接收第一用户面功能实体发送的目标应用服务器的网络地址，该目标应用服务器的网络地址是第一用户面功能实体接收到的上行IP包中的目的地址，该上行IP包是由用户设备发送的。
在本申请的一个实施例中，目标应用服务器的网络地址是由用户设备通过向DNS服务器发送DNS的请求，然后从DNS服务器返回的DNS响应中获取到的。
在步骤S520中，根据目标应用服务器的网络地址，确定用于响应上行IP包的本地边缘服务器的网络地址。
在本申请的一个实施例中，会话管理功能实体可以采用类似于图4所示的步骤S410至步骤S430来确定本地边缘服务器的网络地址；或者会话管理功能实体也可以基于应用服务器的网络地址与本地边缘服务器的网络地址之间的映射关系，将与目标应用服务器的网络地址存在映射关系的本地边缘服务器的网络地址作为本地边缘服务器的网络地址；或者会话管理功能实体也可以基于图4中所示的步骤S410来确定出目标应用服务器的网络地址对应的域名列表，然后根据该域名列表，将对应于域名列表的边缘服务器的网络地址作为本地边缘服务器的网络地址；或者会话管理功能实体也可以基于图4中所示的步骤S410和步骤S420确定出目标域名列表，然后基于域名与边缘服务器的网络地址之间的映射关系，将与目标域名列表存在映射关系的边缘服务器的网络地址列表作为用于响应上行IP包的本地边缘服务器的网络地址列表。
在本申请的一个实施例中，如果得到的本地边缘服务器的网络地址列表中包含有多个网络地址，则可以这多个网络地址中选择距离用户设备最近、与用户设备之间的通信时延最小或负载最轻的本地边缘服务器的网络地址，以提高边缘通信的效率。
继续参照图5所示，在步骤S530中，向第一用户面功能实体发送地址转换控制指令，该地址转换指令用于指示第一用户面功能实体将上行IP包的目的地址修改为本地边缘服务器的网络地址，并转发至本地边缘服务器进行处理。在本申请的一些实施例中， 该地址转换指令还用于指示第一用户面功能实体在接收到本地边缘服务器针对上行IP包返回的下行IP包时，将下行IP包的源地址修改为目标应用服务器的网络地址，并转发至用户设备。
图5所示实施例的技术方案应用于图1所示的EC架构，第一用户面功能实体即为图1中所示的UPF(PSA)，其中上行IP包及下行IP包的地址修改操作全部由UPF来实现。
图6示出了根据本申请的一个实施例的基于边缘计算的通信方法的流程图，该通信方法可以由SMF来执行，该通信方法可以应用于如图2所示的EC架构。参照图6所示，该通信方法至少包括步骤S610至步骤S630，详细介绍如下：
在步骤S610中，接收第一用户面功能实体发送的目标应用服务器的网络地址，该目标应用服务器的网络地址是第一用户面功能实体接收到的上行IP包中的目的地址，该上行IP包是由用户设备发送的。
在本申请的一个实施例中，目标应用服务器的网络地址是由用户设备通过向DNS服务器发送DNS的请求，然后从DNS服务器返回的DNS响应中获取到的。
在步骤S620中，根据目标应用服务器的网络地址，确定用于响应上行IP包的本地边缘服务器的网络地址。
在本申请的一个实施例中，会话管理功能实体可以采用类似于图4所示的步骤S410至步骤S430来确定本地边缘服务器的网络地址；或者会话管理功能实体也可以基于应用服务器的网络地址与本地边缘服务器的网络地址之间的映射关系，将与目标应用服务器的网络地址存在映射关系的本地边缘服务器的网络地址作为本地边缘服务器的网络地址；或者会话管理功能实体也可以基于图4中所示的步骤S410来确定出目标应用服务器的网络地址对应的域名列表，然后根据该域名列表，将对应于域名列表的边缘服务器的网络地址作为本地边缘服务器的网络地址；或者会话管理功能实体也可以基于图4中所示的步骤S410和步骤S420确定出目标域名列表，然后基于域名与边缘服务器的网络地址之间的映射关系，将与目标域名列表存在映射关系的边缘服务器的网络地址列表作为用于响应上行IP包的本地边缘服务器的网络地址列表。
在本申请的一个实施例中，如果得到的本地边缘服务器的网络地址列表中包含有多个网络地址，则可以这多个网络地址中选择距离用户设备最近、与用户设备之间的通信时延最小或负载最轻的本地边缘服务器的网络地址，以提高边缘通信的效率。
在步骤S630中，向与本地边缘服务器相连的第二用户面功能实体发送地址转换控制指令，该地址转换控制指令用于指示第二用户面功能实体在接收到用户设备发送给目标应用服务器的上行IP包时，将接收到的上行IP包的目的地址修改为本地边缘服务器的网络地址，并转发给本地边缘服务器进行处理。在本申请的一个实施例中，该地址转换控制指令还用于指示第二用户面功能实体在接收到本地边缘服务器针对上行IP包返回的下行IP包时，将下行IP包的源地址修改为目标应用服务器的网络地址，并转发至用户设备。
图6所示实施例的技术方案应用于图2所示的EC架构，第一用户面功能实体即为图2中所示的PSA1，第二用户面功能实体即为图2中所示的PSA2。在本申请的一个实施例中，SMF还可以向PSA1发送指令消息，以指示PSA1将接收到的用户设备发送给目标应用服务器的上行IP包转发至PSA2，由PSA2将上行IP包的目的地址修改为本地边缘服务器的网络地址，并转发给本地边缘服务器进行处理。在这种情况下，当本地边缘服务器返回下行IP包到达PSA2之后，PSA2将下行IP包的源地址修改为目标应用服务器的网络地址，并转发至UE，不需要再经过PSA1。
在本申请的一个实施例中，SMF还可以向与PSA2相连的UL CL发送指令消息， 以指示UL CL将用户设备与目标应用服务器之间的数据包发送至PSA2进行转发处理。在这种情况下，当UL CL将UE发送的上行IP包转发至PSA2之后，PSA2将上行IP包的目的地址修改为本地边缘服务器的网络地址，并转发给本地边缘服务器进行处理。当本地边缘服务器返回下行IP包到达PSA2之后，PSA2将下行IP包的源地址修改为目标应用服务器的网络地址，并转发至UE，同样不需要再经过PSA1。
图7示出了根据本申请的一个实施例的基于边缘计算的通信方法的流程图，该通信方法可以由SMF来执行，该通信方法可以应用于如图2所示的EC架构。参照图7所示，该通信方法至少包括步骤S710至步骤S730，详细介绍如下：
在步骤S710中，接收第一用户面功能实体发送的目标应用服务器的网络地址，该目标应用服务器的网络地址是第一用户面功能实体接收到的上行IP包中的目的地址，该上行IP包是由用户设备发送的。
在本申请的一个实施例中，目标应用服务器的网络地址是由用户设备通过向DNS服务器发送DNS的请求，然后从DNS服务器返回的DNS响应中获取到的。
在步骤S720中，根据目标应用服务器的网络地址，确定用于响应上行IP包的本地边缘服务器的网络地址。
在本申请的一个实施例中，会话管理功能实体可以采用类似于图4所示的步骤S410至步骤S430来确定本地边缘服务器的网络地址；或者会话管理功能实体也可以基于应用服务器的网络地址与本地边缘服务器的网络地址之间的映射关系，将与目标应用服务器的网络地址存在映射关系的本地边缘服务器的网络地址作为本地边缘服务器的网络地址；或者会话管理功能实体也可以基于图4中所示的步骤S410来确定出目标应用服务器的网络地址对应的域名列表，然后根据该域名列表，将对应于域名列表的边缘服务器的网络地址作为本地边缘服务器的网络地址；或者会话管理功能实体也可以基于图4中所示的步骤S410和步骤S420确定出目标域名列表，然后基于域名与边缘服务器的网络地址之间的映射关系，将与目标域名列表存在映射关系的边缘服务器的网络地址列表作为用于响应上行IP包的本地边缘服务器的网络地址列表。
在本申请的一个实施例中，如果得到的本地边缘服务器的网络地址列表中包含有多个网络地址，则可以这多个网络地址中选择距离用户设备最近、与用户设备之间的通信时延最小或负载最轻的本地边缘服务器的网络地址，以提高边缘通信的效率。
在步骤S730中，向连接至第二用户面功能实体的上行分类器发送地址转换指令，该地址转换控制指令用于指示上行分类器在接收到用户设备发送给目标应用服务器的上行IP包时，将接收到的上行IP包的目的地址修改为本地边缘服务器的网络地址，并通过第二用户面功能实体转发给本地边缘服务器进行处理。在本申请的一个实施例中，该地址转换控制指令还用于指示上行分类器在接收到本地边缘服务器针对上行IP包返回的下行IP包时，将下行IP包的源地址修改为目标应用服务器的网络地址，并转发至用户设备。
图7所示实施例的技术方案应用于图2所示的EC架构，第一用户面功能实体即为图2中所示的PSA1，第二用户面功能实体即为图2中所示的PSA2，上行分类器即为图2中所示的UL CL。在本申请的一个实施例中，SMF还可以向PSA1发送指令消息，以指示PSA1将接收到的用户设备发送给目标应用服务器的上行IP包转发至UL CL，然后由UL CL将上行IP包的目的地址修改为本地边缘服务器的网络地址，并通过PSA2转发给本地边缘服务器进行处理。在这种情况下，当本地边缘服务器返回下行IP包到达PSA2之后，PSA2将下行IP包转发给UL CL，然后由UL CL将上行IP包的源地址修改为目标应用服务器的网络地址，并转发至UE，不需要再经过PSA1。
在本申请的一个实施例中，SMF还可以向UL CL发送指令消息，以指示UL CL将 用户设备与目标应用服务器之间的数据包发送至PSA2进行转发处理。在这种情况下，当UL CL接收到UE发送的上行IP包之后，将上行IP包的目的地址修改为本地边缘服务器的网络地址，然后发送至PSA2，由PSA2转发给本地边缘服务器进行处理。当本地边缘服务器返回下行IP包到达PSA2之后，PSA2将下行IP包转发给UL CL，然后由UL CL将下行IP包的源地址修改为目标应用服务器的网络地址，并转发至UE，同样不需要再经过PSA1。
上述实施例分别从用户面功能实体UPF和会话管理功能实体SMF的角度对本申请实施例的技术方案进行了阐述，以下结合图8至图11，从各个实体交互的角度对本申请实施例的技术方案的实现细节进行详细阐述：
在本申请的一个实施例中，基于图1所示的EC架构，如图8所示，根据本申请实施例的基于边缘计算的通信方法，包括如下步骤：
步骤S801，UE通过SMF和PSA1建立了一个PDU会话。
这里，UE通过SMF和PSA1建立PDU会话后，网络会分配一个IP地址给UE。其中，UE发起PDU会话建立过程可以参照第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)协议TS23.502的章节4.3.2。在PDU会话建立过程中，SMF命令PSA1要进行上行IP包的目的IP地址的本地边缘服务器地址的查询。
步骤S802，UE通过DNS服务器获得AS的IP地址IPas。
在实际实施时，UE可以发送DNS请求，该DNS请求上行IP包到达PSA1之后，PSA1将此上行IP包转发至目标IP地址，即DNS服务器，当DNS服务器反馈的DNS响应下行IP包到达PSA1后，由PSA1根据下行IP包的目的地址确定出此UE，然后转发至UE，进而UE可以从中获取到AS的IP地址IPas。在一些实施例中，该DNS请求可以是基于UDP协议、HTTPS协议或者是基于TLS协议的。
步骤S803，UE发送上行IP包(源IPue,目的IPas,源端口PORTue,目的端口PORTas,传输层协议(如TCP协议))到达PSA1。
步骤S804，PSA1发送反向域名查询请求给DNS服务器。
根据S801中SMF要求PSA1进行上行IP包的目的IP地址的本地边缘服务器地址的查询的命令，向DNS服务器发送反向域名查询请求，该反向域名查询请求中包含有上行IP包的目的地址，即AS的IP地址IPas。
步骤S805，DNS服务器向PSA1返回反向域名查询响应，该反向域名查询响应中包含有域名列表Asx。
步骤S806，PSA1向边缘DNS服务器发送SRV查询请求。
在实际实施时，对于域名列表Asx中的每一项A，PSA1向边缘DNS服务器分别发送SRV查询请求，该SRV查询请求中包含有域名A、目的端口PORTas和上行IP包所使用的传输层协议(该传输层协议由上行IP包头中的Protocol域得到，如TCP协议)。
步骤S807，边缘DNS服务器向PSA1返回SRV查询响应。
边缘DNS服务器向PSA1返回针对每一项A的SRV查询响应，该SRV查询响应中包含有本地边缘服务器的域名(L-AS域名)。
其中，步骤S806和步骤S807是根据域名列表Asx中的每一项、上行IP包所使用的传输层协议和上行IP包的目的端口号查询得到完整的域名，即PSA1需要针对域名列表Asx中的每一项A，都向边缘DNS服务器发送SRV查询请求，边缘DNS服务器会针对每一项A的SRV查询请求反馈SRV查询响应。通过对域名列表Asx中的每一项进行SRV查询，如果查询到多个完整的域名，则可以得到一个包含多个完整域名的域名列表(L-AS域名列表)。注意，有些项的查询可能返回无对应的本地边缘服务器的域名。
步骤S808，PSA1向边缘DNS服务器发送A或AAAA查询请求。
PSA1向边缘DNS服务器发送包含有L-AS域名(若有多个L-AS域名形成了一个L-AS域名列表，则需要对L-AS域名列表中的每一项L-AS域名采用相同的操作)的A或AAAA查询请求。其中，若IPue和IPas为IPv4，则发起A查询请求；若IPue和IPas为IPv6，则发起AAAA查询请求。
步骤S809，边缘DNS服务器向PSA1返回A或AAAA查询响应。
边缘DNS服务器向PSA1返回包含有本地边缘服务器IP地址(即L-IPas)的A或AAAA查询响应。当然，如果查询到多个本地边缘服务器的IP地址，则A或AAAA查询响应中可以包含一个IP地址列表(L-IPas列表)。通过域名列表的分别查询，将可能得到多个L-IPas。
需要说明的是：步骤S806至步骤S809可以是PSA1直接与边缘DNS服务器进行交互来实现的，也可以是PSA1与边缘DNS服务器通过SMF进行交互来实现的(即由SMF进行转发)。
S810，PSA1上报IPas及L-IPas列表，SMF确定最终的L-IPas。
PSA1通过N4接口向SMF上报目的IP地址IPas及其查询得到的L-IPas(如果查询得到一个L-IPas也需要上报)，让SMF从中选择距离UE最近的或者与UE之间的通信时延最小，或者负载最轻的L-IPas。
步骤S811，SMF向PSA1发送N4会话命令。
这里，SMF向PSA1发送N4会话命令以使PSA1进行目的IP地址的NAT(Network Address Translation，网络地址转换)转换与数据转发操作，即检测并对UE的上行IP包的目的IP地址IPas替换为L-IPas并继续上行转发；检测并对于UE的下行IP包的源IP地址L-IPas替换为IPas并继续下行转发。
步骤S812，PSA1依据SMF的命令，检测并将UE发送的上行IP包的目的IP地址IPas转换为L-IPas。
步骤S813，PSA1发送上行IP包(源IPue,目的L-IPas,源端口PORTue,目的端口PORTas,传输层协议)给边缘服务器EAS。
在实际实施时，PSA1依据SMF的命令，将目的IP地址转换后的上行IP包(源IPue,目的L-IPas,源端口PORTue,目的端口PORTas,传输层协议)通过N6接口发送给边缘服务器EAS。
步骤S814，EAS针对上行IP包向PSA1返回下行IP包(源L-IPas,目的IPue,源端口PORTas,目的端口PORTue,传输层协议)。
步骤S815，PSA1依据SMF的命令，检测并将下行IP包中的源IP地址L-IPas转换为IPas。
步骤S816，PSA1发送下行IP包(源IPas,目的IPue,源端口PORTas,目的端口PORTue,传输层协议)给UE。
PSA1依据SMF的命令，将源IP地址转换后的下行IP包(源IPas,目的IPue,源端口PORTas,目的端口PORTue,传输层协议)发送给UE。
需要说明的是：步骤S812和步骤S815不仅仅是针对步骤S803中接收到的上行IP包进行地址转换处理，而可以是针对此后UE与AS之间的所有数据包都进行地址转换处理。同时，在步骤S812中，也可以增加对源端口PORTue的转换，则检测并转换后的上行IP包中的源端口值PORTue与目的IPas地址都发生了变化，在这种情况下，步骤S815中的反向NAT转换，则是检测并将下行IP包中的目的端口与源L-IPas地址转换为PORTue与IPas。
在实际实施时，当UE发送的上行IP包(源IPue,目的IPas,源端口PORTue,目的端口PORTas,传输层协议)到达PSA1后，PSA1检测到该上行IP包的目的IP为IPas，然 后将上行IP包的目的IP地址IPas替换为L-IPas、将源端口值PORTue替换为设定标识值(如PortIDValue1)，然后将转换后的上行IP包(源IPue,目的L-IPas,源端口PortIDValue1,目的端口PORTas,传输层协议)通过N6接口发送给边缘服务器EAS。当PSA1接收到EAS返回的下行IP包(源L-IPas,目的IPue,源端口PORTas,目的端口PortIDValue1,传输层协议)之后，检测到该下行IP包的目的端口值为PortIDValue1，目的IP为IPue，进而将下行IP包的目的端口值替换为PORTue，将下行IP包中的源IP地址L-IPas替换为IPas，然后将转换后的下行IP包(源IPas,目的IPue,源端口PORTas,目的端口PORTue,传输层协议)发送给UE。
在图8所示的实施例中，得到本地边缘服务器的IP地址L-IPas的过程是通过步骤S804至步骤S810来实现的。在本申请的其它实施例中，也可以通过配置的方式来实现。比如图9所示，通过步骤S900替代了图8中所示的步骤S804至步骤S810。步骤S900中包含有如下步骤：
步骤S9001，PSA1向SMF发送N4会话报告。
在实际实施时，PSA1向SMF发送N4会话报告，以上报上行IP包中包含的目的地址IPas。
步骤S9002，SMF根据配置信息检测并将目的地址IPas映射到EAS的IP地址L-IPas上。
在实际实施时，SMF可以根据SMF上的配置信息直接将IPas映射得到L-IPas；或者SMF可以执行类似于图8中所示的步骤S804和步骤S805所示的查询过程，然后根据SMF上配置信息映射得到L-IPas；或者SMF可以执行类似于图8中所示的步骤S804至步骤S807所示的查询过程，然后根据SMF上配置信息映射得到L-IPas。当然，SMF还可以执行类似于图8中所示的步骤S804至步骤S809所示的查询过程来得到L-IPas。
在本申请的一个实施例中，基于图2所示的EC架构，如图10所示，根据本申请实施例的基于边缘计算的通信方法，包括如下步骤：
步骤S1001，该步骤S1001包含了图8中所示的步骤S801-S810或图9中所示的步骤S801-S900。即检测并基于UE发送的上行IP包(源IPue,目的IPas,源端口PORTue,目的端口PORTas,传输层协议)确定出L-IPas。
步骤S1002，确定需要通过UL CL的方式接入到EAS，选择并插入具有UL CL功能的UPF。
在实际实施时，SMF根据确定的L-IPas地址，确定需要通过UL CL的方式接入到EAS，选择并插入一个具有UL CL功能的UPF。
步骤S1003，确定需要通过UL CL的方式接入到EAS，选择并插入具有PSA功能的UPF，即PSA2。
SMF根据确定的L-IPas地址，确定需要通过UL CL的方式接入到EAS，选择并插入一个具有PSA功能的UPF，即PSA2。
其中步骤S1002和步骤S1003的详细过程可以参照3GPP标准TS23.502中4.3.5.4Addition of additional PDU Session Anchor and Branching Point or UL CL(添加额外的PDU会话锚点和分支点或UL-CL)章节。
步骤S1004，PSA1将UE上行IP包转发给PSA2。
需要说明的是：步骤S1004是将缓存在PSA1上的由UE发送给AS的上行IP包Data Forwarding(数据转发)到PSA2上。这里的Data Forwarding有两种机制，一种是通过在PSA1与PSA2之间建立Data Forwarding的Tunnel(通道)，即由PSA1直接发送给PSA2；另外一种方式是在PSA1与SMF、SMF与PSA2之间分别建立两段Data Forwarding的Tunnel，即由PSA1转发给SMF，再由SMF转发给PSA2。其中，PSA1 上缓存的数据可能是一个IP数据包，也可能是多个IP数据包。
步骤S1005，SMF向UL CL发送N4会话命令，以使UL CL上行转发UE到AS的数据包到PSA2。
步骤S1006，SMF向PSA2发送N4会话命令，以使PSA2进行NAT转换与换向操作。
这里，也就是检测并对UE的上行IP包的目的IP地址IPas替换为L-IPas并继续上行转发；检测并对于UE的下行IP包的源IP地址L-IPas替换为IPas并继续下行转发。
步骤S1007，检测并将上行IP包的目的IP地址IPas转换为L-IPas。
在实际实施时，PSA2依据SMF的命令，检测并将上行IP包的目的IP地址IPas转换为L-IPas。
步骤S1008，发送上行IP包给EAS。
在实际实施时，PSA2依据SMF的命令，将目的IP地址转换后的上行IP包(源IPue,目的L-IPas,源端口PORTue,目的端口PORTas,传输层协议)发送给EAS。
步骤S1009，EAS向PSA2返回下行IP包。
在实际实施时，EAS针对上行IP包向PSA2返回下行IP包(源L-IPas,目的IPue,源端口PORTas,目的端口PORTue,传输层协议)。
步骤S1010，检测并将下行IP包的源IP地址L-IPas转换为IPas。
这里，PSA2依据SMF的命令，检测并将下行IP包的源IP地址L-IPas转换为IPas。
步骤S1011，将下行IP包发送给UE。
在实际实施时，PSA2依据SMF的命令，将源IP地址转换后的下行IP包(源IPas,目的IPue,源端口PORTas,目的端口PORTue,传输层协议)发送给UE。
同时，需要注意的是：后续PSA2会在UE与EAS之间执行反向NAT转换操作。即检测并将UE发送给AS的上行IP包中的目的IP地址IPas转换为L-IPas然后发送给EAS，并检测并将EAS反馈的下行IP包中的源IP地址L-IPas转换为IPas后发送给UE。
此外，类似于图8所示的实施例，在对上行IP包进行地址转换操作时，也可以增加对源端口PORTue的转换，则检测并转换后的上行IP包中的源端口值PORTue与目的IPas地址都发生了变化，在这种情况下，检测并对下行IP包进行反向NAT转换时是将下行IP包中的目的端口与源L-IPas地址转换为PORTue与IPas。
在本申请的一个实施例中，基于图2所示的EC架构，如图11所示，根据本申请实施例的基于边缘计算的通信方法，包括如下步骤：
步骤S1101，检测并基于UE发送的上行IP包确定出L-IPas。
该步骤S1101包含了图8中所示的步骤S801-S810或图9中所示的步骤S801-S900。即检测并基于UE发送的上行IP包(源IPue,目的IPas,源端口PORTue,目的端口PORTas,传输层协议)确定出L-IPas。
步骤S1102，SMF确定需要通过UL CL的方式接入到EAS，选择并插入一个具有UL CL功能的UPF。
SMF根据确定的L-IPas地址，确定需要通过UL CL的方式接入到EAS，选择并插入一个具有UL CL功能的UPF。
步骤S1103，SMF确定需要通过UL CL的方式接入到EAS，选择并插入一个具有PSA功能的UPF(PSA2)。
SMF根据确定的L-IPas地址，确定需要通过UL CL的方式接入到EAS，选择并插入一个具有PSA功能的UPF，即PSA2。
其中步骤S1102和步骤S1103的详细过程可以参照3GPP标准TS23.502中4.3.5.4 Addition of additional PDU Session Anchor and Branching Point or UL CL(添加额外的 PDU会话锚点和分支点或UL-CL)章节。
步骤S1104，PSA1将UE的上行IP包转发给UL CL。
需要说明的是：步骤S1104是将缓存在PSA1上的由UE发送给AS的上行IP包Data Forwarding到UL CL上。这里的Data Forwarding有两种机制，一种是通过在PSA1与UL CL之间建立Data Forwarding的Tunnel，即由PSA1直接发送给UL CL；另外一种方式是在PSA1与SMF、SMF与UL CL之间分别建立两段Data Forwarding的Tunnel，即由PSA1转发给SMF，再由SMF转发给UL CL。其中，PSA1上缓存的数据可能是一个IP数据包，也可能是多个IP数据包。
步骤S1105，SMF向UL CL发送N4会话命令，以使UL CL上行转发UE到AS的数据包到PSA2。
步骤S1106，SMF向UL CL发送N4会话命令，以使UL CL进行NAT转换与换向操作。
即检测并对UE的上行IP包目的IP地址IPas替换为L-IPas并继续上行转发；检测并对于UE的下行IP包的源IP地址L-IPas替换为IPas并继续下行转发。
步骤S1107，检测并将上行IP包的目的IP地址IPas转换为L-IPas。
UL CL依据SMF的命令，检测并将上行IP包的目的IP地址IPas转换为L-IPas。
步骤S1108，将目的IP地址转换后的上行IP包发送给PSA2，由PSA2转发给EAS。
UL CL依据SMF的命令，将目的IP地址转换后的上行IP包(源IPue,目的L-IPas,源端口PORTue,目的端口PORTas,传输层协议)发送给PSA2，由PSA2转发给EAS。
步骤S1109，EAS向PSA2返回下行IP包，该下行IP包由PSA2转发至UL CL。
EAS针对上行IP包向PSA2返回下行IP包(源L-IPas,目的IPue,源端口PORTas,目的端口PORTue,传输层协议)，该下行IP包由PSA2转发至UL CL。
步骤S1110，检测并将下行IP包的源IP地址L-IPas转换为IPas。
UL CL依据SMF的命令，检测并将下行IP包的源IP地址L-IPas转换为IPas。
步骤S1111，将源IP地址转换后的下行IP包发送给UE。
UL CL依据SMF的命令，将源IP地址转换后的下行IP包(源IPas,目的IPue,源端口PORTas,目的端口PORTue,传输层协议)发送给UE。
同时，需要注意的是：后续UL CL会在UE与EAS之间执行反向NAT转换操作。即检测并将UE发送给AS的上行IP包中的目的IP地址IPas转换为L-IPas然后发送给PSA2，由PSA2转发给EAS，检测并将通过PSA2转发的由EAS反馈的下行IP包中的源IP地址L-IPas转换为IPas后发送给UE。
此外，类似于图8所示的实施例，在检测并对上行IP包进行地址转换操作时，也可以增加对源端口PORTue的转换，则检测并转换后的上行IP包中的源端口值PORTue与目的IPas地址发生了变化，在这种情况下，对下行IP包进行反向NAT转换时是检测并将下行IP包中的目的端口与源IP地址L-IPas转换为PORTue与IPas。
本申请上述实施例的技术方案针对图1和图2所示的两种EC架构，不管UE的IP地址是IPv4还是IPv6都可以在无需对UE和AS进行修改或增强的前提下，实现UE对EAS的访问，这使得EC有重大的应用价值，将广泛应用于游戏加速、视频加速与V2X(vehicle to Everything，车辆对外界)业务中。
以下介绍本申请的装置实施例，可以用于执行本申请上述实施例中的基于边缘计算的通信方法。对于本申请装置实施例中未披露的细节，请参照本申请上述的基于边缘计算的通信方法的实施例。
图12示出了根据本申请的一个实施例的基于边缘计算的通信装置的框图，该通信装置可以设置在用户面功能实体内部。
参照图12所示，根据本申请的一个实施例的基于边缘计算的通信装置1200，包括：第一接收单元1202、第一确定单元1204和第一发送单元1206。
其中，第一接收单元1202配置为接收用户设备发送的上行IP包，所述上行IP包的目的地址为目标应用服务器的网络地址；第一确定单元1204配置为根据所述目标应用服务器的网络地址，确定用于响应所述上行IP包的本地边缘服务器的网络地址；第一发送单元1206配置为将所述上行IP包的目的地址修改为所述本地边缘服务器的网络地址，并转发至所述本地边缘服务器进行处理。
在本申请的一些实施例中，第一确定单元1204配置为：根据所述目标应用服务器的网络地址查询所述目标应用服务器的网络地址对应的域名列表；根据所述域名列表、所述上行IP包所使用的传输层协议和所述上行IP包中包含的目的端口查询得到对应的目标域名列表；基于所述目标域名列表查询得到本地边缘服务器的网络地址列表，以基于所述网络地址列表获取用于响应所述上行IP包的本地边缘服务器的网络地址。
在本申请的一些实施例中，第一确定单元1204配置为：根据所述域名列表、所述上行IP包所使用的传输层协议和所述目的端口向边缘域名系统DNS服务器发起服务记录SRV查询，得到所述目标域名列表；基于所述目标域名列表从所述边缘DNS服务器中查询得到所述本地边缘服务器的网络地址列表。
在本申请的一些实施例中，第一确定单元1204配置为：将所述网络地址列表及所述目标应用服务器的网络地址上报给会话管理功能实体，以使所述会话管理功能实体从所述网络地址列表中选择用于响应所述上行IP包的本地边缘服务器的网络地址。
在本申请的一些实施例中，第一确定单元1204配置为：将所述目标应用服务器的网络地址上报给会话管理功能实体，以使所述会话管理功能实体根据所述目标应用服务器的网络地址确定所述本地边缘服务器的网络地址；或根据所述目标应用服务器的网络地址查询所述目标应用服务器的网络地址对应的域名列表，将所述域名列表上报给会话管理功能实体，以使所述会话管理功能实体根据所述域名列表确定所述本地边缘服务器的网络地址。
在本申请的一些实施例中，第一接收单元1202还配置为：接收会话管理功能实体发送的地址转换控制指令，所述地址转换控制指令用于指示将所述用户设备发送给所述目标应用服务器的上行IP包的目的地址修改为所述本地边缘服务器的网络地址。
在本申请的一些实施例中，所述地址转换控制指令还用于指示将所述本地边缘服务器针对所述上行IP包返回的下行IP包的源地址修改为所述目标应用服务器的网络地址；第一接收单元1202还配置为：接收所述本地边缘服务器针对所述上行IP包返回的下行IP包，所述下行IP包的源地址为所述本地边缘服务器的网络地址；第一发送单元1206还配置为：将所述下行IP包的源地址修改为所述目标应用服务器的网络地址，并转发至所述用户设备。
在本申请的一些实施例中，第一发送单元1206还配置为：在转发至所述本地边缘服务器进行处理之前，将所述上行IP包的源端口值修改为设定标识值，并记录所述上行IP包的源端口值与所述设定标识值的对应关系；在接收到所述本地边缘服务器返回的下行IP包时，若所述下行IP包的目的端口值与所述设定标识值相匹配，则将所述下行IP包的目的端口值修改为所述上行IP包的源端口值。
在本申请的一些实施例中，当使用了一个新的连接至所述本地边缘服务器的目标用户面功能实体时，第一发送单元1206配置为：将所述上行IP包直接发送给所述目标用户面功能实体，以使所述目标用户面功能实体将所述上行IP包的目的地址修改为所述本地边缘服务器的网络地址，并转发至所述本地边缘服务器进行处理；或者将所述上行IP包通过会话管理功能实体发送给所述目标用户面功能实体，以使所述目标用户面功能 实体将所述上行IP包的目的地址修改为所述本地边缘服务器的网络地址，并转发至所述本地边缘服务器进行处理。
在本申请的一些实施例中，当使用了一个新的连接至所述本地边缘服务器的目标用户面功能实体时，第一发送单元1206配置为：将所述上行IP包直接发送给上行分类器，以使所述上行分类器将所述上行IP包的目的地址修改为所述本地边缘服务器的网络地址，并通过与所述本地边缘服务器相连的目标用户面功能实体转发至所述本地边缘服务器进行处理；或者将所述上行IP包通过会话管理功能实体发送给上行分类器，以使所述上行分类器将所述上行IP包的目的地址修改为所述本地边缘服务器的网络地址，并通过与所述本地边缘服务器相连的目标用户面功能实体转发至所述本地边缘服务器进行处理。
图13示出了根据本申请的一个实施例的基于边缘计算的通信装置的框图，该通信装置可以设置在会话管理功能实体内部。
参照图13所示，根据本申请的一个实施例的基于边缘计算的通信装置1300，包括：第二接收单元1302、第二确定单元1304和第二发送单元1306。
其中，第二接收单元1302配置为接收第一用户面功能实体发送的目标应用服务器的网络地址，所述目标应用服务器的网络地址是所述第一用户面功能实体接收到的上行IP包中的目的地址，所述上行IP包是由用户设备发送的；第二确定单元1304配置为根据所述目标应用服务器的网络地址，确定用于响应所述上行IP包的本地边缘服务器的网络地址；第二发送单元1306配置为向所述第一用户面功能实体发送地址转换控制指令，所述地址转换指令用于指示所述第一用户面功能实体将所述上行IP包的目的地址修改为所述本地边缘服务器的网络地址，并转发至所述本地边缘服务器进行处理。
在本申请的一些实施例中，所述地址转换指令还用于指示所述第一用户面功能实体在接收到所述本地边缘服务器针对所述上行IP包返回的下行IP包时，将所述下行IP包的源地址修改为所述目标应用服务器的网络地址，并转发至所述用户设备。
在本申请的一些实施例中，第二确定单元1304配置为：根据所述目标应用服务器的网络地址查询所述目标应用服务器的网络地址对应的域名列表；根据所述域名列表、所述上行IP包所使用的传输层协议和所述上行IP包中包含的目的端口查询得到能够响应所述上行IP包的目标域名列表；基于所述目标域名列表查询得到所述本地边缘服务器的网络地址列表。
在本申请的一些实施例中，第二确定单元1304配置为：基于应用服务器的网络地址与本地边缘服务器的网络地址之间的映射关系，将与所述目标应用服务器的网络地址存在映射关系的本地边缘服务器的网络地址作为所述本地边缘服务器的网络地址。
在本申请的一些实施例中，第二确定单元1304配置为：根据所述目标应用服务器的网络地址查询所述目标应用服务器的网络地址对应的域名列表；根据所述域名列表，将对应于所述域名列表的边缘服务器的网络地址作为所述本地边缘服务器的网络地址。
在本申请的一些实施例中，第二确定单元1304配置为：根据所述目标应用服务器的网络地址查询所述目标应用服务器的网络地址对应的域名列表；根据所述域名列表、所述上行IP包所使用的传输层协议和所述上行IP包中包含的目的端口查询得到对应的目标域名列表；基于域名与边缘服务器的网络地址之间的映射关系，将与所述目标域名列表存在映射关系的边缘服务器的网络地址列表作为用于响应所述上行IP包的本地边缘服务器的网络地址列表。
在本申请的一些实施例中，第二确定单元1304还配置为：若所述本地边缘服务器的网络地址列表中包含有多个网络地址，则从所述多个网络地址中选择距离所述用户设备最近、与所述用户设备之间的通信时延最小或负载最轻的本地边缘服务器的网络地址。
图14示出了根据本申请的一个实施例的基于边缘计算的通信装置的框图，该通信装置可以设置在会话管理功能实体内部。
参照图14所示，根据本申请的一个实施例的基于边缘计算的通信装置1400，包括：第三接收单元1402、第三确定单元1404和第三发送单元1406。
其中，第三接收单元1402配置为接收第一用户面功能实体发送的目标应用服务器的网络地址，所述目标应用服务器的网络地址是所述第一用户面功能实体接收到的上行IP包中的目的地址，所述上行IP包是由用户设备发送的；第三确定单元1404配置为根据所述目标应用服务器的网络地址，确定用于响应所述上行IP包的本地边缘服务器的网络地址；第三发送单元1406配置为向与本地边缘服务器相连的第二用户面功能实体发送地址转换控制指令，所述地址转换控制指令用于指示所述第二用户面功能实体在接收到所述用户设备发送给所述目标应用服务器的上行IP包时，将接收到的上行IP包的目的地址修改为所述本地边缘服务器的网络地址，并转发给所述本地边缘服务器进行处理。
在本申请的一些实施例中，所述地址转换控制指令还用于指示所述第二用户面功能实体在接收到所述本地边缘服务器针对所述上行IP包返回的下行IP包时，将所述下行IP包的源地址修改为所述目标应用服务器的网络地址，并转发至所述用户设备。
在本申请的一些实施例中，第三发送单元1406还配置为：向所述第一用户面功能实体发送指令消息，以指示所述第一用户面功能实体将接收到的所述用户设备发送给所述目标应用服务器的上行IP包转发至所述第二用户面功能实体。
在本申请的一些实施例中，第三发送单元1406还配置为：向与所述第二用户面功能实体相连的上行分类器发送指令消息，以指示所述上行分类器将所述用户设备与所述目标应用服务器之间的数据包发送至所述第二用户面功能实体进行转发处理。
图15示出了根据本申请的一个实施例的基于边缘计算的通信装置的框图，该通信装置可以设置在会话管理功能实体内部。
参照图15所示，根据本申请的一个实施例的基于边缘计算的通信装置1500，包括：第四接收单元1502、第四确定单元1504和第四发送单元1506。
其中，第四接收单元1502配置为接收第一用户面功能实体发送的目标应用服务器的网络地址，所述目标应用服务器的网络地址是所述第一用户面功能实体接收到的上行IP包中的目的地址，所述上行IP包是由用户设备发送的；第四确定单元1504配置为根据所述目标应用服务器的网络地址，确定用于响应所述上行IP包的本地边缘服务器的网络地址；第四发送单元1506配置为向连接至第二用户面功能实体的上行分类器发送地址转换指令，所述地址转换控制指令用于指示所述上行分类器在接收到所述用户设备发送给所述目标应用服务器的上行IP包时，将接收到的上行IP包的目的地址修改为所述本地边缘服务器的网络地址，并通过所述第二用户面功能实体转发给所述本地边缘服务器进行处理。
在本申请的一些实施例中，所述地址转换控制指令还用于指示所述上行分类器在接收到所述本地边缘服务器针对所述上行IP包返回的下行IP包时，将所述下行IP包的源地址修改为所述目标应用服务器的网络地址，并转发至所述用户设备。
在本申请的一些实施例中，第四发送单元1506还配置为：向所述第一用户面功能实体发送指令消息，以指示所述第一用户面功能实体将接收到的所述用户设备发送给所述目标应用服务器的上行IP包转发至所述上行分类器。
在本申请的一些实施例中，第四发送单元1506还配置为：向所述上行分类器发送指令消息，以指示所述上行分类器将所述用户设备与所述目标应用服务器之间的数据包发送至所述第二用户面功能实体进行转发处理。
图16示出了适于用来实现本申请实施例的电子设备的计算机系统的结构示意图。
需要说明的是，图16示出的电子设备的计算机系统1600仅是一个示例，不应对本申请实施例的功能和使用范围带来任何限制。
如图16所示，计算机系统1600包括中央处理单元(Central Processing Unit，CPU)1601，其可以根据存储在只读存储器(Read-Only Memory，ROM)1602中的程序或者从存储部分1608加载到随机访问存储器(Random Access Memory，RAM)1603中的程序而执行各种适当的动作和处理，例如执行上述实施例中所述的方法。在RAM 1603中，还存储有系统操作所需的各种程序和数据。CPU 1601、ROM 1602以及RAM 1603通过总线1604彼此相连。输入/输出(Input/Output，I/O)接口1605也连接至总线1604。
以下部件连接至I/O接口1605：包括键盘、鼠标等的输入部分1606；包括诸如阴极射线管(Cathode Ray Tube，CRT)、液晶显示器(Liquid Crystal Display，LCD)等以及扬声器等的输出部分1607；包括硬盘等的存储部分1608；以及包括诸如LAN(Local Area Network，局域网)卡、调制解调器等的网络接口卡的通信部分1609。通信部分1609经由诸如因特网的网络执行通信处理。驱动器1610也根据需要连接至I/O接口1605。可拆卸介质1611，诸如磁盘、光盘、磁光盘、半导体存储器等等，根据需要安装在驱动器1610上，以便于从其上读出的计算机程序根据需要被安装入存储部分1608。
特别地，根据本申请的实施例，上文参考流程图描述的过程可以被实现为计算机软件程序。例如，本申请的实施例包括一种计算机程序产品，其包括承载在计算机可读介质上的计算机程序，该计算机程序包含用于执行流程图所示的方法的计算机程序。在这样的实施例中，该计算机程序可以通过通信部分1609从网络上被下载和安装，和/或从可拆卸介质1611被安装。在该计算机程序被中央处理单元(CPU)1601执行时，执行本申请的系统中限定的各种功能。
需要说明的是，本申请实施例所示的计算机可读介质可以是计算机可读信号介质或者计算机可读存储介质或者是上述两者的任意组合。计算机可读存储介质例如可以是但不限于电、磁、光、电磁、红外线、或半导体的系统、装置或器件，或者任意以上的组合。计算机可读存储介质的更具体的例子可以包括但不限于：具有一个或多个导线的电连接、便携式计算机磁盘、硬盘、随机访问存储器(RAM)、只读存储器(ROM)、可擦式可编程只读存储器(Erasable Programmable Read Only Memory，EPROM)、闪存、光纤、便携式紧凑磁盘只读存储器(Compact Disc Read-Only Memory，CD-ROM)、光存储器件、磁存储器件、或者上述的任意合适的组合。在本申请中，计算机可读存储介质可以是任何包含或存储程序的有形介质，该程序可以被指令执行系统、装置或者器件使用或者与其结合使用。而在本申请中，计算机可读的信号介质可以包括在基带中或者作为载波一部分传播的数据信号，其中承载了计算机可读的计算机程序。这种传播的数据信号可以采用多种形式，包括但不限于电磁信号、光信号或上述的任意合适的组合。计算机可读的信号介质还可以是计算机可读存储介质以外的任何计算机可读介质，该计算机可读介质可以发送、传播或者传输用于由指令执行系统、装置或者器件使用或者与其结合使用的程序。计算机可读介质上包含的计算机程序可以用任何适当的介质传输，包括但不限于：无线、有线等等，或者上述的任意合适的组合。
附图中的流程图和框图，图示了按照本申请各种实施例的系统、方法和计算机程序产品的可能实现的体系架构、功能和操作。其中，流程图或框图中的每个方框可以代表一个模块、程序段、或代码的一部分，上述模块、程序段、或代码的一部分包含一个或多个用于实现规定的逻辑功能的可执行指令。也应当注意，在有些作为替换的实现中，方框中所标注的功能也可以以不同于附图中所标注的顺序发生。例如，两个接连地表示的方框实际上可以基本并行地执行，它们有时也可以按相反的顺序执行，这依所涉及的 功能而定。也要注意的是，框图或流程图中的每个方框、以及框图或流程图中的方框的组合，可以用执行规定的功能或操作的专用的基于硬件的系统来实现，或者可以用专用硬件与计算机指令的组合来实现。
描述于本申请实施例中所涉及到的单元可以通过软件的方式实现，也可以通过硬件的方式来实现，所描述的单元也可以设置在处理器中。其中，这些单元的名称在某种情况下并不构成对该单元本身的限定。
本申请实施例还提供了一种计算机可读介质，该计算机可读介质可以是上述实施例中描述的电子设备中所包含的；也可以是单独存在，而未装配入该电子设备中。上述计算机可读介质承载有一个或者多个程序，当上述一个或者多个程序被一个该电子设备执行时，使得该电子设备实现上述实施例中所述的方法。
应当注意，尽管在上文详细描述中提及了用于动作执行的设备的若干模块或者单元，但是这种划分并非强制性的。实际上，根据本申请的实施方式，上文描述的两个或更多模块或者单元的特征和功能可以在一个模块或者单元中具体化。反之，上文描述的一个模块或者单元的特征和功能可以进一步划分为由多个模块或者单元来具体化。
通过以上的实施方式的描述，本领域的技术人员易于理解，这里描述的示例实施方式可以通过软件实现，也可以通过软件结合必要的硬件的方式来实现。因此，根据本申请实施方式的技术方案可以以软件产品的形式体现出来，该软件产品可以存储在一个非易失性存储介质(可以是CD-ROM，U盘，移动硬盘等)中或网络上，包括若干指令以使得一台计算设备(可以是个人计算机、服务器、触控终端、或者网络设备等)执行根据本申请实施方式的方法。

Claims (37)

  1. 一种基于边缘计算的通信方法，所述方法由电子设备执行，所述方法包括：
    接收用户设备发送的上行网际互连协议IP包，所述上行IP包的目的地址为目标应用服务器的网络地址；
    根据所述目标应用服务器的网络地址，确定用于响应所述上行IP包的本地边缘服务器的网络地址；
    将所述上行IP包的目的地址修改为所述本地边缘服务器的网络地址，并转发至所述本地边缘服务器进行处理。
  2. 根据权利要求1所述的方法，其中，所述根据所述目标应用服务器的网络地址，确定用于响应所述上行IP包的本地边缘服务器的网络地址，包括：
    根据所述目标应用服务器的网络地址，查询所述目标应用服务器的网络地址对应的域名列表；
    根据所述域名列表、所述上行IP包所使用的传输层协议和所述上行IP包中包含的目的端口查询得到对应的目标域名列表；
    基于所述目标域名列表查询得到本地边缘服务器的网络地址列表，以基于所述网络地址列表，获取用于响应所述上行IP包的本地边缘服务器的网络地址。
  3. 根据权利要求2所述的方法，其中，所述根据所述域名列表、所述上行IP包所使用的传输层协议和所述上行IP包中包含的目的端口查询得到对应的目标域名列表，包括：
    根据所述域名列表、所述上行IP包所使用的传输层协议和所述目的端口向边缘域名系统DNS服务器发起服务记录SRV查询，得到所述目标域名列表；
    所述基于所述目标域名列表查询得到所述本地边缘服务器的网络地址列表，包括：
    基于所述目标域名列表从所述边缘DNS服务器中查询得到所述本地边缘服务器的网络地址列表。
  4. 根据权利要求2或3所述的方法，其中，所述基于所述网络地址列表，获取用于响应所述上行IP包的本地边缘服务器的网络地址，包括：
    将所述网络地址列表及所述目标应用服务器的网络地址上报给会话管理功能实体，以使所述会话管理功能实体从所述网络地址列表中选择用于响应所述上行IP包的本地边缘服务器的网络地址。
  5. 根据权利要求1所述的方法，其中，所述根据所述目标应用服务器的网络地址，确定用于响应所述上行IP包的本地边缘服务器的网络地址，包括：
    将所述目标应用服务器的网络地址上报给会话管理功能实体，以使所述会话管理功能实体根据所述目标应用服务器的网络地址，确定所述本地边缘服务器的网络地址；或根据所述目标应用服务器的网络地址，查询所述目标应用服务器的网络地址对应的域名列表，将所述域名列表上报给会话管理功能实体，以使所述会话管理功能实体根据所述域名列表确定所述本地边缘服务器的网络地址。
  6. 根据权利要求1所述的方法，其中，所述将所述上行IP包的目的地址修改为所述本地边缘服务器的网络地址之前，所述方法还包括：
    接收会话管理功能实体发送的地址转换控制指令，所述地址转换控制指令用于指示将所述用户设备发送给所述目标应用服务器的上行IP包的目的地址，修改为所述本地边缘服务器的网络地址。
  7. 根据权利要求6所述的方法，其中，所述地址转换控制指令还用于指示将所述本地边缘服务器针对所述上行IP包返回的下行IP包的源地址，修改为所述目标应用服务器的网络地址；所述方法还包括：
    接收所述本地边缘服务器针对所述上行IP包返回的下行IP包，所述下行IP包的源地址为所述本地边缘服务器的网络地址；
    将所述下行IP包的源地址修改为所述目标应用服务器的网络地址，并转发至所述用户设备。
  8. 根据权利要求1所述的方法，其中，所述方法还包括：
    在转发至所述本地边缘服务器进行处理之前，将所述上行IP包的源端口值修改为设定标识值，并记录所述上行IP包的源端口值与所述设定标识值的对应关系；
    在接收到所述本地边缘服务器返回的下行IP包时，若所述下行IP包的目的端口值与所述设定标识值相匹配，则将所述下行IP包的目的端口值修改为所述上行IP包的源端口值。
  9. 根据权利要求1所述的方法，其中，当使用了一个新的连接至所述本地边缘服务器的目标用户面功能实体时，将所述上行IP包的目的地址修改为所述本地边缘服务器的网络地址，并转发至所述本地边缘服务器进行处理，包括：
    将所述上行IP包直接发送给所述目标用户面功能实体，以使所述目标用户面功能实体将所述上行IP包的目的地址修改为所述本地边缘服务器的网络地址，并转发至所述本地边缘服务器进行处理；或者
    将所述上行IP包通过会话管理功能实体发送给所述目标用户面功能实体，以使所述目标用户面功能实体将所述上行IP包的目的地址修改为所述本地边缘服务器的网络地址，并转发至所述本地边缘服务器进行处理。
  10. 根据权利要求1所述的方法，其中，当使用了一个新的连接至所述本地边缘服务器的目标用户面功能实体时，将所述上行IP包的目的地址修改为所述本地边缘服务器的网络地址，并转发至所述本地边缘服务器进行处理，包括：
    将所述上行IP包直接发送给上行分类器，以使所述上行分类器将所述上行IP包的目的地址修改为所述本地边缘服务器的网络地址，并通过与所述本地边缘服务器相连的目标用户面功能实体，转发至所述本地边缘服务器进行处理；或者
    将所述上行IP包通过会话管理功能实体发送给上行分类器，以使所述上行分类器将所述上行IP包的目的地址修改为所述本地边缘服务器的网络地址，并通过与所述本地边缘服务器相连的目标用户面功能实体转发至所述本地边缘服务器进行处理。
  11. 一种基于边缘计算的通信方法，所述方法由电子设备执行，所述方法包括：
    接收第一用户面功能实体发送的目标应用服务器的网络地址，所述目标应用服务器的网络地址是所述第一用户面功能实体接收到的上行IP包中的目的地址，所述上行IP包是由用户设备发送的；
    根据所述目标应用服务器的网络地址，确定用于响应所述上行IP包的本地边缘服务器的网络地址；
    向所述第一用户面功能实体发送地址转换控制指令，所述地址转换指令用于指示所述第一用户面功能实体将所述上行IP包的目的地址修改为所述本地边缘服务器的网络地址，并转发至所述本地边缘服务器进行处理。
  12. 根据权利要求11所述的方法，其中，所述地址转换指令还用于指示所述第一用户面功能实体在接收到所述本地边缘服务器针对所述上行IP包返回的下行IP包时，将所述下行IP包的源地址修改为所述目标应用服务器的网络地址，并转发至所述用户设备。
  13. 根据权利要求11所述的方法，其中，所述根据所述目标应用服务器的网络地址，确定用于响应所述上行IP包的本地边缘服务器的网络地址，包括：
    根据所述目标应用服务器的网络地址查询所述目标应用服务器的网络地址对应的域名列表；
    根据所述域名列表、所述上行IP包所使用的传输层协议和所述上行IP包中包含的目的端口查询得到对应的目标域名列表；
    基于所述目标域名列表查询得到用于响应所述上行IP包的本地边缘服务器的网络地址列表。
  14. 根据权利要求11所述的方法，其中，所述根据所述目标应用服务器的网络地址，确定用于响应所述上行IP包的本地边缘服务器的网络地址，包括：
    基于应用服务器的网络地址与本地边缘服务器的网络地址之间的映射关系，将与所述目标应用服务器的网络地址存在映射关系的本地边缘服务器的网络地址作为所述本地边缘服务器的网络地址。
  15. 根据权利要求11所述的方法，其中，所述根据所述目标应用服务器的网络地址，确定用于响应所述上行IP包的本地边缘服务器的网络地址，包括：
    根据所述目标应用服务器的网络地址，查询所述目标应用服务器的网络地址对应的域名列表；
    根据所述域名列表，将对应于所述域名列表的边缘服务器的网络地址作为所述本地边缘服务器的网络地址。
  16. 根据权利要求11所述的方法，其中，所述根据所述目标应用服务器的网络地址，确定用于响应所述上行IP包的本地边缘服务器的网络地址，包括：
    根据所述目标应用服务器的网络地址，查询所述目标应用服务器的网络地址对应的域名列表；
    根据所述域名列表、所述上行IP包所使用的传输层协议和所述上行IP包中包含的目的端口查询得到对应的目标域名列表；
    基于域名与边缘服务器的网络地址之间的映射关系，将与所述目标域名列表存在映射关系的边缘服务器的网络地址列表，作为用于响应所述上行IP包的本地边缘服务器的网络地址列表。
  17. 根据权利要求13或16所述的方法，其中，若所述本地边缘服务器的网络地址列表中包含有多个网络地址，则从所述多个网络地址中选择距离所述用户设备最近、与所述用户设备之间的通信时延最小或负载最轻的本地边缘服务器的网络地址。
  18. 一种基于边缘计算的通信方法，所述方法由电子设备执行，所述方法包括：
    接收第一用户面功能实体发送的目标应用服务器的网络地址，所述目标应用服务器的网络地址，是所述第一用户面功能实体接收到的上行IP包中的目的地址，所述上行IP包是由用户设备发送的；
    根据所述目标应用服务器的网络地址，确定用于响应所述上行IP包的本地边缘服务器的网络地址；
    向与本地边缘服务器相连的第二用户面功能实体发送地址转换控制指令，所述地址转换控制指令用于指示所述第二用户面功能实体在接收到所述用户设备发送给所述目标应用服务器的上行IP包时，将接收到的上行IP包的目的地址修改为所述本地边缘服务器的网络地址，并转发给所述本地边缘服务器进行处理。
  19. 根据权利要求18所述的方法，其中，所述地址转换控制指令还用于指示所述第二用户面功能实体在接收到所述本地边缘服务器针对所述上行IP包返回的下行IP包 时，将所述下行IP包的源地址修改为所述目标应用服务器的网络地址，并转发至所述用户设备。
  20. 根据权利要求18所述的方法，其中，所述方法还包括：
    向所述第一用户面功能实体发送指令消息，以指示所述第一用户面功能实体将接收到的所述用户设备发送给所述目标应用服务器的上行IP包转发至所述第二用户面功能实体。
  21. 根据权利要求18所述的方法，其中，所述方法还包括：
    向与所述第二用户面功能实体相连的上行分类器发送指令消息，以指示所述上行分类器将所述用户设备与所述目标应用服务器之间的数据包发送至所述第二用户面功能实体进行转发处理。
  22. 一种基于边缘计算的通信方法，所述方法由电子设备执行，所述方法包括：
    接收第一用户面功能实体发送的目标应用服务器的网络地址，所述目标应用服务器的网络地址是所述第一用户面功能实体接收到的上行IP包中的目的地址，所述上行IP包是由用户设备发送的；
    根据所述目标应用服务器的网络地址，确定用于响应所述上行IP包的本地边缘服务器的网络地址；
    向连接至第二用户面功能实体的上行分类器发送地址转换指令，所述地址转换控制指令用于指示所述上行分类器在接收到所述用户设备发送给所述目标应用服务器的上行IP包时，将接收到的上行IP包的目的地址修改为所述本地边缘服务器的网络地址，并通过所述第二用户面功能实体转发给所述本地边缘服务器进行处理。
  23. 根据权利要求22所述的方法，其中，所述地址转换控制指令还用于指示所述上行分类器在接收到所述本地边缘服务器针对所述上行IP包返回的下行IP包时，将所述下行IP包的源地址修改为所述目标应用服务器的网络地址，并转发至所述用户设备。
  24. 根据权利要求22所述的方法，其中，所述方法还包括：
    向所述第一用户面功能实体发送指令消息，以指示所述第一用户面功能实体将接收到的所述用户设备发送给所述目标应用服务器的上行IP包，转发至所述上行分类器。
  25. 根据权利要求22所述的方法，其中，所述方法还包括：
    向所述上行分类器发送指令消息，以指示所述上行分类器将所述用户设备与所述目标应用服务器之间的数据包，发送至所述第二用户面功能实体进行转发处理。
  26. 一种基于边缘计算的通信装置，所述装置包括：
    第一接收单元，配置为接收用户设备发送的上行IP包，所述上行IP包的目的地址为目标应用服务器的网络地址；
    第一确定单元，配置为根据所述目标应用服务器的网络地址，确定用于响应所述上行IP包的本地边缘服务器的网络地址；
    第一发送单元，配置为将所述上行IP包的目的地址修改为所述本地边缘服务器的网络地址，并转发至所述本地边缘服务器进行处理。
  27. 一种基于边缘计算的通信装置，所述装置包括：
    第二接收单元，配置为接收第一用户面功能实体发送的目标应用服务器的网络地址，所述目标应用服务器的网络地址是所述第一用户面功能实体接收到的上行IP包中的目的地址，所述上行IP包是由用户设备发送的；
    第二确定单元，配置为根据所述目标应用服务器的网络地址，确定用于响应所述上行IP包的本地边缘服务器的网络地址；
    第二发送单元，配置为向所述第一用户面功能实体发送地址转换控制指令，所述地址转换指令用于指示所述第一用户面功能实体将所述上行IP包的目的地址修改为所述本地边缘服务器的网络地址，并转发至所述本地边缘服务器进行处理。
  28. 一种基于边缘计算的通信装置，所述装置包括：
    第三接收单元，配置为接收第一用户面功能实体发送的目标应用服务器的网络地址，所述目标应用服务器的网络地址是所述第一用户面功能实体接收到的上行IP包中的目的地址，所述上行IP包是由用户设备发送的；
    第三确定单元，配置为根据所述目标应用服务器的网络地址，确定用于响应所述上行IP包的本地边缘服务器的网络地址；
    第三发送单元，配置为向与本地边缘服务器相连的第二用户面功能实体发送地址转换控制指令，所述地址转换控制指令用于指示所述第二用户面功能实体在接收到所述用户设备发送给所述目标应用服务器的上行IP包时，将接收到的上行IP包的目的地址修改为所述本地边缘服务器的网络地址，并转发给所述本地边缘服务器进行处理。
  29. 一种基于边缘计算的通信装置，所述装置包括：
    第四接收单元，配置为接收第一用户面功能实体发送的目标应用服务器的网络地址，所述目标应用服务器的网络地址是所述第一用户面功能实体接收到的上行IP包中的目的地址，所述上行IP包是由用户设备发送的；
    第四确定单元，配置为根据所述目标应用服务器的网络地址，确定用于响应所述上行IP包的本地边缘服务器的网络地址；
    第四发送单元，配置为向连接至第二用户面功能实体的上行分类器发送地址转换指令，所述地址转换控制指令用于指示所述上行分类器在接收到所述用户设备发送给所述目标应用服务器的上行IP包时，将接收到的上行IP包的目的地址修改为所述本地边缘服务器的网络地址，并通过所述第二用户面功能实体转发给所述本地边缘服务器进行处理。
  30. 一种计算机可读介质，其上存储有计算机程序，所述计算机程序被处理器执行时实现如权利要求1至10中任一项所述的基于边缘计算的通信方法。
  31. 一种计算机可读介质，其上存储有计算机程序，所述计算机程序被处理器执行时，实现如权利要求11至17中任一项所述的基于边缘计算的通信方法。
  32. 一种计算机可读介质，其上存储有计算机程序，所述计算机程序被处理器执行时，实现如权利要求18至21中任一项所述的基于边缘计算的通信方法。
  33. 一种计算机可读介质，其上存储有计算机程序，所述计算机程序被处理器执行时，实现如权利要求22至25中任一项所述的基于边缘计算的通信方法。
  34. 一种电子设备，所述电子设备包括：一个或多个处理器；
    存储器，配置为存储一个或多个程序，当所述一个或多个程序被所述一个或多个处理器执行时，使得所述一个或多个处理器实现如权利要求1至10中任一项所述的基于边缘计算的通信方法；或实现如权利要求11至17中任一项所述的基于边缘计算的通信方法；或实现如权利要求18至21中任一项所述的基于边缘计算的通信方法；或实现如权利要求22至25中任一项所述的基于边缘计算的通信方法。
  35. 一种电子设备，所述电子设备包括：一个或多个处理器；
    存储器，配置为存储一个或多个程序，当所述一个或多个程序被所述一个或多个处理器执行时，使得所述一个或多个处理器实现如权利要求11至17中任一项所述的基于边缘计算的通信方法。
  36. 一种电子设备，所述电子设备包括：一个或多个处理器；
    存储器，配置为存储一个或多个程序，当所述一个或多个程序被所述一个或多个处理器执行时，使得所述一个或多个处理器实现如权利要求18至21中任一项所述的基于边缘计算的通信方法。
  37. 一种电子设备，所述电子设备包括：一个或多个处理器；
    存储器，配置为存储一个或多个程序，当所述一个或多个程序被所述一个或多个处理器执行时，使得所述一个或多个处理器实现如权利要求22至25中任一项所述的基于边缘计算的通信方法。
PCT/CN2020/126432 2020-03-15 2020-11-04 基于边缘计算的通信方法、装置、存储介质及电子设备 WO2021184774A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP20925153.7A EP4007224B1 (en) 2020-03-15 2020-11-04 Communication methods and electronic device
ES20925153T ES2976452T3 (es) 2020-03-15 2020-11-04 Métodos de comunicación y dispositivo electrónico
US17/677,740 US11616754B2 (en) 2020-03-15 2022-02-22 Communication method and apparatus based on edge computing, storage medium, and electronic device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010179051.0A CN111343092B (zh) 2020-03-15 2020-03-15 基于边缘计算的通信方法、装置、介质及电子设备
CN202010179051.0 2020-03-15

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/677,740 Continuation US11616754B2 (en) 2020-03-15 2022-02-22 Communication method and apparatus based on edge computing, storage medium, and electronic device

Publications (1)

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

Family

ID=71187358

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/126432 WO2021184774A1 (zh) 2020-03-15 2020-11-04 基于边缘计算的通信方法、装置、存储介质及电子设备

Country Status (5)

Country Link
US (1) US11616754B2 (zh)
EP (1) EP4007224B1 (zh)
CN (2) CN111343092B (zh)
ES (1) ES2976452T3 (zh)
WO (1) WO2021184774A1 (zh)

Families Citing this family (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113841372A (zh) * 2019-05-10 2021-12-24 三星电子株式会社 边缘计算系统中获得和管理移动终端的位置信息的方法和装置
CN111343092B (zh) * 2020-03-15 2021-10-22 腾讯科技（深圳）有限公司 基于边缘计算的通信方法、装置、介质及电子设备
CN117177266A (zh) * 2020-04-28 2023-12-05 华为技术有限公司 一种地址获取方法及装置
CN113965545A (zh) * 2020-07-03 2022-01-21 华为技术有限公司 Dns请求的解析方法、通信装置及通信系统
CN113973098A (zh) * 2020-07-06 2022-01-25 华为技术有限公司 一种域名系统请求的发送方法及装置
CN114095562B (zh) * 2020-07-31 2024-10-15 中国电信股份有限公司 边缘应用发现方法、系统以及增强防火墙
CN114079956A (zh) * 2020-08-07 2022-02-22 中国电信股份有限公司 业务保障方法、系统、存储介质和服务提供系统
US20240015529A1 (en) * 2020-08-14 2024-01-11 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for user plane path management
EP4207820A1 (en) * 2020-09-30 2023-07-05 Huawei Technologies Co., Ltd. Method and apparatus for dynamically triggering instantiation of edge application server
CN112562356A (zh) * 2020-11-18 2021-03-26 联通智网科技有限公司 车场协同式自主泊车方法、装置、计算机设备和存储介质
US12126592B2 (en) * 2020-12-26 2024-10-22 Intel Corporation Neutral host edge services
WO2022157667A1 (en) * 2021-01-21 2022-07-28 Telefonaktiebolaget Lm Ericsson (Publ) Distance-based selection
US20240056415A1 (en) * 2021-02-10 2024-02-15 Lenovo (Beijing) Limited Dns configuration provisioning
WO2022205384A1 (en) * 2021-04-01 2022-10-06 Huawei Technologies Co., Ltd. Devices and methods for ue application context relocation in an edge network
US11665097B2 (en) * 2021-04-27 2023-05-30 Verizon Patent And Licensing Inc. Methods and systems for differentiating MEC flows using IP header signaling
CN113795014B (zh) * 2021-08-05 2022-11-18 华为技术有限公司 发现边缘应用服务器的方法及装置
CN116267035A (zh) * 2021-10-18 2023-06-20 北京小米移动软件有限公司 边缘服务器的路由选择方法、装置、通信设备及存储介质
CN113890864B (zh) * 2021-10-19 2024-06-14 京东科技信息技术有限公司 数据包处理方法、装置、电子设备和存储介质
CN115297179B (zh) * 2022-07-25 2024-03-08 天翼云科技有限公司 一种数据传输方法及装置
CN118250334A (zh) * 2022-12-22 2024-06-25 维沃软件技术有限公司 计算服务的实现方法、装置、通信设备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107113343A (zh) * 2014-12-31 2017-08-29 三星电子株式会社 在无线通信系统中分配服务器的方法和装置
CN109218455A (zh) * 2017-06-30 2019-01-15 华为技术有限公司 一种应用实例地址的转换方法和装置
US20190372837A1 (en) * 2018-06-02 2019-12-05 Verizon Patent And Licensing Inc. Systems and methods for localized and virtualized radio access networks
CN111343092A (zh) * 2020-03-15 2020-06-26 腾讯科技（深圳）有限公司 基于边缘计算的通信方法、装置、介质及电子设备

Family Cites Families (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6976090B2 (en) * 2000-04-20 2005-12-13 Actona Technologies Ltd. Differentiated content and application delivery via internet
US7660296B2 (en) * 2005-12-30 2010-02-09 Akamai Technologies, Inc. Reliable, high-throughput, high-performance transport and routing mechanism for arbitrary data flows
US9106468B1 (en) * 2009-01-30 2015-08-11 Sprint Communications Company L.P. Transferring media objects from one device to another device
US9055117B1 (en) * 2011-09-27 2015-06-09 Amazon Technologies, Inc. Distributed network address translation
JP2014112768A (ja) * 2012-12-05 2014-06-19 Hitachi Ltd 自動障害対応キャッシュシステム及びキャッシュサーバの障害対応処理方法並びにキャッシュマネージャ
US9792716B2 (en) 2014-06-13 2017-10-17 Arcsoft Inc. Enhancing video chatting
CN106488504B (zh) * 2015-08-28 2019-12-24 华为技术有限公司 网络系统和网络通信的方法
US10826868B2 (en) * 2016-03-29 2020-11-03 T-Mobile Usa, Inc. NAT aware DNS
US11444850B2 (en) * 2016-05-02 2022-09-13 Huawei Technologies Co., Ltd. Method and apparatus for communication network quality of service capability exposure
WO2017197564A1 (zh) * 2016-05-16 2017-11-23 华为技术有限公司 切换过程中的通信方法和装置
US10778779B2 (en) * 2016-06-17 2020-09-15 Huawei Technologies Co., Ltd. Method and system for session management for ultra reliable and low latency communications in high mobility scenarios
US10531420B2 (en) * 2017-01-05 2020-01-07 Huawei Technologies Co., Ltd. Systems and methods for application-friendly protocol data unit (PDU) session management
US10616106B2 (en) * 2017-12-06 2020-04-07 Futurewei Technologies, Inc. Establishing virtual network routes in a computer network
US10904947B2 (en) * 2018-05-16 2021-01-26 Huawei Technologies Co., Ltd. Message and system for application function influence on traffic routing
CN112512090B (zh) * 2019-03-15 2022-07-19 腾讯科技（深圳）有限公司 通信处理方法、装置、计算机可读介质及电子设备
CN110198307B (zh) * 2019-05-10 2021-05-18 深圳市腾讯计算机系统有限公司 一种移动边缘计算节点的选择方法、装置及系统
CN110198363B (zh) * 2019-05-10 2021-05-18 深圳市腾讯计算机系统有限公司 一种移动边缘计算节点的选择方法、装置及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107113343A (zh) * 2014-12-31 2017-08-29 三星电子株式会社 在无线通信系统中分配服务器的方法和装置
CN109218455A (zh) * 2017-06-30 2019-01-15 华为技术有限公司 一种应用实例地址的转换方法和装置
US20190372837A1 (en) * 2018-06-02 2019-12-05 Verizon Patent And Licensing Inc. Systems and methods for localized and virtualized radio access networks
CN111343092A (zh) * 2020-03-15 2020-06-26 腾讯科技（深圳）有限公司 基于边缘计算的通信方法、装置、介质及电子设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4007224A4 *

Also Published As

Publication number Publication date
EP4007224A1 (en) 2022-06-01
CN111343092B (zh) 2021-10-22
EP4007224A4 (en) 2022-11-16
ES2976452T3 (es) 2024-08-01
CN114124817A (zh) 2022-03-01
EP4007224B1 (en) 2024-03-06
US11616754B2 (en) 2023-03-28
US20220182358A1 (en) 2022-06-09
CN111343092A (zh) 2020-06-26
CN114124817B (zh) 2023-03-14

Similar Documents

Publication Publication Date Title
WO2021184774A1 (zh) 基于边缘计算的通信方法、装置、存储介质及电子设备
US11863448B2 (en) Method and apparatus for traffic optimization in virtual private networks (VPNs)
WO2020259509A1 (zh) 一种应用迁移方法及装置
EP2381647B1 (en) Session migration in content-centric networks
US9742859B2 (en) Network traffic management using port number redirection
US10104633B1 (en) Active position driven mobility content delivery in information centric networks
Mastorakis et al. Towards service discovery and invocation in data-centric edge networks
WO2018113504A1 (zh) 一种用户面锚点选择方法及装置
US11799827B2 (en) Intelligently routing a response packet along a same connection as a request packet
US10862804B2 (en) Redirecting data packets between overlay network and underlay network
US7236476B2 (en) mSCTP based handover of a mobile device between non-intersecting networks
WO2024021414A1 (zh) 数据传输
WO2024021405A1 (zh) 一种数据传输系统和方法
WO2023072291A1 (zh) 一种多跳中继连接建立方法、装置、设备及介质
CN112055083B (zh) 请求处理方法、装置、电子设备和介质
TW202249465A (zh) 使用網際網路協定網路於蜂巢式資料封包路由的裝置
CN114980262A (zh) 接入网关的选择方法及装置、存储介质、电子设备
US11616716B1 (en) Connection ownership gossip for network packet re-routing
KR101158794B1 (ko) ＶｏＩＰ 서비스 제공 방법 및 세션 보더 컨트롤러 서버
CN116963312A (zh) 基于iOS设备的数据传输方法、装置、设备及存储介质
CN116418794A (zh) 适用于http3服务的cdn调度方法、装置、系统、设备及介质
CN116846840A (zh) 多域纯IPv6网络中业务流量的交互方法、装置、设备和介质
CN117527875A (zh) 会话转发方法、装置、计算机可读介质及电子设备
Mattsson Mobile Data Communication based on Host Identity Protocol (HIP)
WO2014032734A1 (en) Determination of correct location information server

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020925153

Country of ref document: EP

Effective date: 20220228

NENP Non-entry into the national phase

Ref country code: DE