CN114598676A

CN114598676A - Application addressing method, system and storage medium

Info

Publication number: CN114598676A
Application number: CN202011302294.5A
Authority: CN
Inventors: 刘洁; 林奕琳; 朱红梅; 何宇峰; 刘龙龙; 杨峰义; 张建敏; 曹磊; 王波
Original assignee: China Telecom Corp Ltd
Current assignee: China Telecom Corp Ltd
Priority date: 2020-11-19
Filing date: 2020-11-19
Publication date: 2022-06-07

Abstract

The disclosure provides an application addressing method, system and storage medium, and relates to the technical field of communication. The application addressing method comprises the following steps: the method comprises the steps that a Local Domain Name System Resolver (LDNSR) determines an application type corresponding to an edge application Domain Name System (DNS) request from a terminal; under the condition that the application type is determined to be the edge application of the service flow reserved domain name information, feeding back the address of the edge gateway corresponding to the terminal position so that the terminal can send an application access request to the edge gateway; the method comprises the steps that an edge gateway determines an actual address of an application according to domain name information carried by an application access request under the condition that the edge gateway receives the application access request; the edge gateway forwards the application access request to the actual address of the application. By the method, the LDNSR can reduce the processing load of the LDNSR and the local DNS for the edge application of reserving domain name information for most service flows in the network, reduce the configuration load and the execution load of the edge UPF and reduce the expansion difficulty.

Description

Application addressing method, system and storage medium

Technical Field

The present disclosure relates to the field of communications technologies, and in particular, to an application addressing method, system, and storage medium.

Background

Under the scene of edge computing, an application server is deployed in a multi-point mode or the server is deployed in a private network, the network needs to identify and judge edge application, and an access request of a user is shunted and addressed to a nearest service node. In the standard research of 3GPP (3GPP TR 23.748), a DNS (Domain Name System) request sent by a terminal is first sent to a centrally-located LDNSR (Local Domain Name System Resolver), the LDNSR interacts with a SMF (Session Management Function) to obtain a terminal location, and further forwards the request to a Local DNS in the form of an agent identity according to the terminal location and a preset Local DNS mapping relationship. The local DNS provides domain name resolution for MEC (Multi-access Edge Computing) applications deployed in a local area, resolves different IP addresses for each application, and the LDNSR triggers the SMF to issue a offloading policy corresponding to the local application according to an IP (Internet Protocol) address in a received response packet.

Disclosure of Invention

One object of the present disclosure is to simplify the network offload rule configuration and reduce the complexity of application expansion.

According to an aspect of some embodiments of the present disclosure, there is provided an application addressing method, including: the LDNSR determines an application type corresponding to an edge application DNS request from a terminal; under the condition that the application type is determined to be the edge application of the service flow reserved domain name information, feeding back the address of the edge gateway corresponding to the terminal position so that the terminal can send an application access request to the edge gateway; the method comprises the steps that an edge gateway determines an actual address of an application according to domain name information carried by an application access request under the condition that the application access request is received; the edge gateway forwards the application access request to the actual address of the application.

In some embodiments, applying the addressing method further comprises: the edge gateway establishes a connection between the terminal and an application server corresponding to the access address of the application.

In some embodiments, applying the addressing method further comprises: the edge UPF (User Plane Function) receives an application access request from the terminal and forwards the application access request to the edge gateway.

In some embodiments, in the case that it is determined that the application type is an application for which domain name information is reserved for a service flow, feeding back an address of an edge gateway corresponding to a terminal location includes: the LDNSR acquires terminal position information through the SMF; the LDNSR judges whether the application type corresponding to the edge application DNS request is the edge application of which the service flow reserves domain name information; if the application type is determined to be the edge application of the service flow reserved domain name information, determining the address of the corresponding edge gateway according to the area where the terminal position is located; and the LDNSR feeds back a DNS response carrying the address of the edge gateway to the terminal under the condition of determining that the edge distribution strategy of the terminal in the corresponding area is issued.

In some embodiments, in a case where it is determined that the application type is an edge application that reserves domain name information for a service flow, feeding back an address of an edge gateway corresponding to a terminal location further includes: the LDNSR sends a user plane reselection strategy for requesting to establish a user plane path of the edge shunt to the SMF under the condition that the edge shunt strategy of the terminal in the corresponding area is determined not to be issued; the SMF executes edge PSA (Protocol Data Unit Session Anchor) insertion according to a user plane reselection strategy and configures a shunting strategy of an edge UPF; and the edge UPF sets the distribution identification rule as the IP address of the edge gateway according to the distribution strategy, wherein the matching target address is the IP address of the edge gateway.

In some embodiments, applying the addressing method further comprises: the LDNSR determines a corresponding local DNS according to the terminal position under the condition that the application type is determined to be the application of which the non-service flow reserves the domain name information, and forwards the edge application DNS request to the local DNS; the local DNS determines an application access address according to the edge application DNS request and feeds the application access address back to the LDNSR; the LDNSR triggers the SMF to issue a shunting strategy according to the access address of the application, and feeds back the access address of the application to the user terminal, so that the terminal sends an application access request according to the access address of the application.

In some embodiments, applying the addressing method further comprises: the SMF sets the LDNSR corresponding to the terminal position as the DNS server of the terminal and anchors the session of the terminal in a central UPF under the condition of receiving an initial session establishment request of the terminal.

By the method, the LDNSR can directly feed back the address of the edge gateway for the edge application which reserves domain name information for most service flows in the network without inquiring the address of specific application in the local DNS, thereby reducing the processing burden of the LDNSR and the local DNS; for the edge application, the shunting identification rules of the edge UPF connected with the terminal are all the addresses of the edge gateway, so that the configuration burden and the execution burden of the edge UPF are reduced; the problem that when the MEC is deployed in a private network environment and the edge UPF is connected with a plurality of MEC platforms, the IP address sections of the MEC private networks are overlapped is solved, flexibility of edge application expansion in each MEC is improved, and expansion difficulty is reduced.

According to an aspect of some embodiments of the present disclosure, there is provided an application addressing system, comprising: the LDNSR is configured to determine an application type corresponding to an edge application DNS request from a terminal; under the condition that the application type is determined to be the edge application of the service flow reserved domain name information, feeding back the address of the edge gateway corresponding to the terminal position so that the terminal can send an application access request to the edge gateway; the edge gateway is configured to determine an actual address of an application according to domain name information carried by an application access request under the condition of receiving the application access request; the application access request is forwarded to the actual address of the application.

In some embodiments, the application addressing system further comprises: and the edge UPF is configured to receive the application access request from the terminal and forward the application access request to the edge gateway.

In some embodiments, the LDNSR is configured to obtain terminal location information via SMF; judging whether the application type corresponding to the edge application DNS request is an edge application for reserving domain name information for the service flow; if the application type is determined to be the edge application of the service flow reserved domain name information, determining the address of the corresponding edge gateway according to the area where the terminal position is located; under the condition that the edge distribution strategy of the terminal in the corresponding area is determined to be issued, feeding back a DNS response carrying the address of the edge gateway to the terminal; under the condition that the edge shunting strategy of the terminal in the corresponding area is determined not to be issued, sending a user plane reselection strategy for requesting to establish a user plane path of the edge shunting to the SMF; the application addressing system further comprises: an SMF configured to feed back terminal location information to the LDNSR; performing edge PSA insertion according to a user plane reselection strategy, and configuring a shunting strategy of an edge UPF; and the edge UPF is configured to set the distribution identification rule as the IP address of the edge gateway according to the distribution strategy, wherein the matching target address is the IP address of the edge gateway.

In some embodiments, the LDNSR is further configured to, in the event that the application type is determined to be an application that reserves domain name information for a non-traffic flow, determine a corresponding local DNS according to the terminal location, and forward the edge application DNS request to the local DNS; triggering the SMF to issue a shunting strategy according to the access address of the application fed back by the local DNS, and feeding back the access address of the application to the user terminal so that the terminal can send an application access request according to the access address of the application; the application addressing system further comprises: and the local DNS is configured to determine an access address of the edge application according to the DNS request of the edge application and feed back the access address to the LDNSR.

According to an aspect of some embodiments of the present disclosure, there is provided an application addressing system, comprising: a memory; and a processor coupled to the memory, the processor configured to perform any of the application addressing methods above based on instructions stored in the memory.

In the application addressing system, the LDNSR can directly feed back the address of the edge gateway for the application of reserving domain name information for most service flows in the network without inquiring the address of specific application in the local DNS, thereby reducing the processing burden of the LDNSR and the local DNS; for the application, the distribution identification rules of the edge UPF connected with the terminal are all matched with the target address as the address of the edge gateway, so that the configuration burden and the execution burden of the edge UPF are reduced; the problem that when the MEC is deployed in a private network environment and the edge UPF is connected with a plurality of MEC platforms, the IP address sections of the MEC private networks are overlapped is solved, flexibility of edge application expansion in each MEC is improved, and expansion difficulty is reduced.

According to an aspect of some embodiments of the present disclosure, a computer-readable storage medium is proposed, on which computer program instructions are stored, which instructions, when executed by a processor, implement the steps of any of the application addressing methods above.

By executing the instructions on the computer-readable storage medium, the LDNSR can directly feed back the address of the edge gateway for the edge application which reserves domain name information for the majority of service flows in the network without inquiring the address of specific application in the local DNS, so that the processing burden of the LDNSR and the local DNS is reduced; for the application, the shunting identification rules of the edge UPF connected with the terminal are all matched with the target address as the address of the edge gateway, so that the configuration burden and the execution burden of the edge UPF are reduced; the problem that IP address sections of the MEC private network are overlapped when the MEC is deployed in a private network environment and the edge UPF connects a plurality of MEC platforms is solved, flexibility of edge application expansion in each MEC is improved, and expansion difficulty is reduced.

Drawings

The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this disclosure, illustrate embodiments of the disclosure and together with the description serve to explain the disclosure and not to limit the disclosure. In the drawings:

fig. 1 is a flow diagram of some embodiments of an application addressing method of the present disclosure.

FIG. 2 is a flow chart of further embodiments of an application addressing method of the present disclosure.

Fig. 3 is a signaling flow diagram of further embodiments of an application addressing method of the present disclosure.

Fig. 4 is a schematic diagram of some embodiments of application addressing systems of the present disclosure.

Fig. 5 is a network architecture diagram of some embodiments of an application addressing system of the present disclosure.

FIG. 6 is a schematic diagram of further embodiments of an application addressing system of the present disclosure.

FIG. 7 is a schematic diagram of yet other embodiments of application addressing systems of the present disclosure.

FIG. 8 is a schematic diagram of still further embodiments of application addressing systems of the present disclosure.

Detailed Description

The technical solution of the present disclosure is further described in detail by the accompanying drawings and examples.

The inventor finds that, in the related art, with the expansion of the application deployed on the MEC, the network needs to add a new identification rule for local offload according to the IP address of the application; in order to accurately resolve the IP address of the local application according to the user position, a domain name resolution request of the local application needs to be forwarded to a local DNS, and the local DNS implements domain name resolution service; in addition, because the MEC deployment environment may be a private network environment, when a plurality of MEC platforms are connected behind the edge UPF, the IP address sections of the MEC private networks cannot be overlapped to ensure correct routing, which brings challenges to network deployment and routing design, and when the IP address sections are repeated, address conversion needs to be performed on the server address, which is complex to implement.

A flow diagram of some embodiments of the application addressing method of the present disclosure is shown in fig. 1.

In step 101, the LDNSR determines an application type corresponding to an edge application DNS request from a terminal. In some embodiments, the edge applications may be divided into two categories (assuming that they are referred to as a category a and a category B, and hereinafter, the category a and the category B are referred to as having the same meaning as in this paragraph), where the category a is the edge application that will retain the domain name in the traffic flow, and the category B is the application that does not guarantee to retain the domain name in the traffic flow. The inventor finds that in the practical application process, the class A application accounts for the majority.

In step 102, in the case where the application type is class a, step 103 is executed. In some embodiments, if the application type is class B, it may be executed according to the scheme in the related art.

In step 103, the address of the edge gateway corresponding to the terminal location is fed back.

In some embodiments, the LDNSR may query the location information of the terminal through the SMF, and then determine an edge gateway address of a service area corresponding to the location of the terminal. In some embodiments, LDNSR pre-stores the correspondence between service areas and edge gateway addresses.

In some embodiments, the LDNSR establishes an edge user plane according to the determined edge gateway address, determines a distribution rule of an edge UPF to which the terminal accesses, and realizes distribution of the edge UPF to the edge gateway.

In step 104, the edge GateWay (MEC GateWay, or MEC GW) determines whether an application access request is received. If an application access request is received, step 105 is performed.

In step 105, the edge gateway determines an access address of the application according to domain name information carried in the application access request. In some embodiments, the edge gateway configures the correspondence between the domain name and the access address (e.g., IP address, port) in the service area in advance.

In some embodiments, when the edge UPF receives an application access request from the terminal, the application access request is forwarded to the edge gateway.

In step 106, the edge gateway forwards the application access request to the actual address of the application. In some embodiments, the edge gateway establishes a connection between the terminal and an application server corresponding to the actual address of the application, and the terminal and the application server interact through the edge gateway.

By the method, the LDNSR can directly feed back the address of the edge gateway for the application of reserving domain name information for most service flows in the network without inquiring the address of specific application in the local DNS, thereby reducing the processing burden of the LDNSR and the local DNS; for the application, the distribution identification rules of the edge UPF connected with the terminal are all matched with the target address as the address of the edge gateway, so that the configuration burden and the execution burden of the edge UPF are reduced; the problem that when the MEC is deployed in a private network environment and the edge UPF is connected with a plurality of MEC platforms, the IP address sections of the MEC private networks are overlapped is solved, flexibility of edge application expansion in each MEC is improved, and expansion difficulty is reduced.

A flow chart of further embodiments of the application addressing method of the present disclosure is shown in fig. 2.

In step 201, LDNSR refers to terminal location information through SMF. In some embodiments, LDNSR may be co-located with SMF.

In step 202, the LDNSR determines an application type corresponding to an edge application DNS request from a terminal.

In step 203, the LDNSR performs step 204 in case it is determined that the application type is an application that reserves domain name information for the traffic flow.

In step 204, the LDNSR determines the address of the corresponding edge gateway according to the area where the terminal is located.

In step 205, the LDNSR determines whether the edge offload policy of the terminal in the corresponding area has been issued. In some embodiments, if the terminal accesses an edge gateway of a corresponding area (which may be for accessing the same or different edge application as the current one), the edge offload policy has been issued. And executing step 206 if it is determined that the terminal issues the edge offloading policy in the corresponding area.

In step 206, the LDNSR feeds back the address of the edge gateway corresponding to the terminal location.

In step 207, the edge gateway receives the application access request. In some embodiments, the terminal sends the application access request to the edge UPF, and sends the application access request to the edge gateway based on the offloading policy of the edge UPF. Since the class-a application is to be accessed by the user, the application access request includes the domain name information of the edge application and also includes the address of the edge gateway.

In step 208, the edge gateway determines the actual address of the edge application according to the domain name information carried in the application access request.

In step 209, the edge gateway forwards the application access request to the actual address of the edge application.

In step 210, the edge gateway establishes a connection between the terminal and an application server corresponding to the actual address of the application.

Based on the form that most applications are A-type applications, the MEC GW is introduced to carry out secondary distribution on the A-type applications according to the domain name through the method, so that the configuration of network distribution rules is simplified, frequent rule updating signaling interaction is reduced, the problem that a plurality of private network MEC platforms distinguish routes is solved, and the distribution and addressing implementation of edge applications is simplified.

In some embodiments, as shown in fig. 2, in step 205, if the edge offload policy of the terminal in the corresponding area has not been issued, that is, the terminal has not accessed the class a edge application of the corresponding area, the following steps 211 to 213 are performed.

In step 211, a user plane reselection policy requesting establishment of a user plane path for edge offload is sent to the SMF, and the policy carries an address of an edge gateway.

In step 212, the SMF performs edge PSA insertion according to the user plane reselection policy and configures the offload policy for the edge UPF.

In step 213, the edge UPF sets the offloading identification rule to match the destination address with the IP address of the edge gateway according to the offloading policy.

By the method, based on the process of carrying out distribution strategy configuration on the edge UPF in the related technology, the distribution of the edge UPF to the edge gateway is realized by carrying the address of the edge gateway, the SMF and the UPF do not need to be improved, and the method is favorable for popularization and application.

In some embodiments, if it is determined in step 203 that the application type is class B (an application that does not retain domain name information in a service flow), step 221 to step 223 are performed.

In step 221, a corresponding local DNS is determined according to the terminal location, and the edge application DNS request is forwarded to the local DNS.

In step 222, the local DNS determines the access address of the application from the edge application DNS request and feeds back to the LDNSR.

In step 223, the LDNSR triggers the SMF to issue a splitting policy, where the splitting policy carries an access address of the application, and after configuration is completed, the edge UPF splits the service flow to an actual access address of the edge application. The LDNSR feeds back the actual access address of the application to the user terminal, so that the user sends an access request of the application to the access address of the application, and the access request does not guarantee to carry domain name information of the application.

In some embodiments, the access address of the application may be the actual address of the application. In some embodiments, the actual address of the application may be an internal address, and to resolve the IP address field conflict, the access address of the application provided to the user may be an external address translated from the actual address of the application. An access request initiated by a user according to an access address of an application is converted into an actual address of the application after reaching the corresponding MEC platform, so that the access to the edge application is realized.

By the method, the compatibility of A-type and B-type services can be realized, and the reliability of application addressing is improved.

A signaling flow diagram of further embodiments of the application addressing method of the present disclosure is shown in fig. 3.

In 301, a UE (User Element) establishes an initial session, and an SMF assigns an LDNSR to the UE as its DNS server and anchors the session to a centrally located UPF.

In 302, a UE accesses a certain edge application by means of a domain name, first initiates a DNS request, which is via the center UPF to the LDNSR.

In 303, LDNSR refers to the UE location information through SMF.

In 304, the LDNSR determines that the accessed application is a class a application, and queries a corresponding MEC GW address in combination with a correspondence between a pre-configured service area and a MEC GW address.

In 305, if LDNSR determines that the edge offload policy has not been issued (the UE does not use the edge service in the service area), it initiates a user plane reselection policy to the SMF, and requires to establish a user plane path for edge offload, and executes 306; otherwise 306, 307 are skipped and 308 is performed.

At 306, the SMF implements edge PSA insertion and configures an offload policy for the edge UPF, where the offload identification rule is the IP address of the MEC GW.

In 307, SMF replies that LDNSR edge user plane is established.

In 308, the LDNSR replies a DNS response to the UE, where the IP address is the address of the MEC GW corresponding to the service area where the UE is located.

In 309, the UE initiates an application access request to the IP address of the DNS response, where the request also carries the domain name of the application. The request arrives from the edge UPF to the MEC GW via network forking.

In 310, the MEC GW performs the role of access proxy, querying the internal actual IP of the corresponding edge application according to the URL information in the request.

In 311, the MEC GW performs secondary distribution of the access request according to the domain name information carried in the request, and forwards the request to the queried internal actual IP address, thereby establishing a connection between the UE and the edge application.

In 312, the UE and the edge application perform service interaction to achieve normal access of the application.

By the method, the shunting strategy of configuring the gateway address for most edge applications can replace the shunting configuration of all class-A applications, thereby simplifying the shunting strategy configuration of the network; the LDNSR directly resolves the type A local application into a gateway address, and domain name resolution of the type A application does not need local DNS, so that address resolution configuration is simplified; deletion of class A applications on the MEC and change of application states do not affect the configuration of a network shunting strategy and LDNSR, so that the application change is partially unaware; the MEC GW is used as an access gateway, so that the actual address of the class-A application is shielded, and the application safety is improved; the addresses presented by the MEC platform to the outside are greatly reduced, address conflict of connection of multiple MEC platforms is avoided, and the 5G core network only needs to distinguish routes according to the MEC GW address and a small amount of class B application IP, so that the route setting is simplified.

A schematic diagram of some embodiments of the application addressing system of the present disclosure is shown in fig. 4.

LDNSR 41 is capable of determining the application type to which the edge application DNS request from the terminal corresponds. In some embodiments, the edge applications may be divided into two classes (referred to as class a and class B, where class a is an application that will retain a domain name in a traffic flow, and class B is an application that does not guarantee to retain a domain name in a traffic flow. And under the condition that the application type is determined to be the application (type-A application) for reserving the domain name information for the service flow, feeding back the address of the edge gateway corresponding to the position of the terminal so that the terminal can send an application access request to the edge gateway.

In some embodiments, if the application type is class B, it may be executed according to the scheme in the related art.

The edge gateway 42 can determine the access address of the application according to the domain name information carried in the application access request and forward the application access request to the actual address of the application when receiving the application access request. In some embodiments, as shown in fig. 4, the application addressing system may further include a UPF43, which is capable of receiving an application access request from the terminal and forwarding the application access request to the edge gateway.

In some embodiments, LDNSR 41 is also capable of obtaining terminal location information via SMF; judging whether the application type corresponding to the edge application DNS request is an application for reserving domain name information for the service flow; if the application type is determined to be the application of reserving domain name information for the service flow, determining the address of the corresponding edge gateway according to the area where the terminal position is located; under the condition that the edge distribution strategy of the terminal in the corresponding area is determined to be issued, feeding back a DNS response carrying the address of the edge gateway to the terminal; and under the condition that the edge shunting strategy of the terminal in the corresponding area is determined not to be issued, sending a user plane reselection strategy for requesting to establish a user plane path of the edge shunting to the SMF. As shown in fig. 4, the application addressing system further includes an SMF44, which is capable of performing terminal location subscription in the 5G core network and feeding back terminal location information to the LDNSR 41; and performing edge PSA insertion according to the user plane reselection strategy, and configuring the shunting strategy of the edge UPF. The edge UPF43 can set the offload identification rule to match the destination address to the IP address of the edge gateway according to the offload policy.

The system can realize the shunting of the edge UPF to the edge gateway by carrying the address of the edge gateway based on the process of carrying out shunting strategy configuration on the edge UPF in the related technology, does not need to improve SMF and UPF, and is beneficial to popularization and application.

In some embodiments, the LDNSR is further capable of determining a corresponding local DNS according to a terminal location and forwarding the edge application DNS request to the local DNS in a case where it is determined that the application type is an application in which domain name information is reserved for a non-traffic flow; triggering the SMF to issue a shunting strategy according to the access address of the application fed back by the local DNS, and feeding back the access address of the application to the user terminal, so that the terminal sends an application access request according to the access address of the application. As shown in fig. 4, the application addressing system also includes a local DNS45 that can determine the actual access address of the application from the edge application DNS request and feed back to LDNSR 41.

The system can realize the compatibility of A-type and B-type services and improve the reliability of application addressing.

A schematic diagram of a network architecture of some embodiments of the application addressing system of the present disclosure is shown in fig. 5, mainly involving 5GC (5G core network) and MEC platform.

In 5GC, UPF is the user plane. The 5GC implements and guarantees that access to edge traffic is split from the edge UPF.

The MEC platform provides the deployment environment and necessary management means for edge applications.

The central DNS is a conventional DNS of an operator, and provides a domain name resolution service of a conventional mobile internet.

The MEC GW is deployed on the MEC platform, receives an edge application access request from the 5G network, and implements access distribution of the edge application deployed on the MEC platform, including distribution according to domain names and distribution according to IP addresses.

An edge application is an application deployed on the MEC platform.

SMF implements user plane management.

The LDNSR has an application function of a DNS function and provides a DNS or DNS proxy function.

As shown in fig. 5, the MEC GW function is set in the MEC platform as a gateway device of a unified interface for the terminal to access the edge application. LDNSR configures the corresponding relation between the position and the MEC GW address, and sets the type (A type or B type) corresponding to the edge application in advance. When the terminal initiates a DNS request, the LDNSR first determines the application type, and performs domain name resolution on the class B application according to a known method (as shown by a dotted arrow in the figure).

The process shown by the implementation arrow in the figure is performed on the domain name resolution request of the class a application. And the LDNSR replies corresponding MEC GW addresses in a unified way according to the terminal positions (the MEC platform and the MEC GW are in one-to-one relation). When accessing the A-type edge application on the same MEC, the terminal initiates a request to the MEC GW, so that the edge UPF only needs to configure the distribution rule matched with the gateway IP, and the distribution rule does not need to change along with the addition and deletion of the application for the A-type application. The MEC GW is used as an access agent, addresses the access request according to domain name information in the access request for the class A application, and forwards the access request to an actual IP corresponding to the internal application; and distributing the B-type application according to the IP address so as to realize that the terminal accesses the requested application service.

Taking the domain name and application access process shown in fig. 6 as an example, an MEC GW is introduced as an access agent on the MEC platform.

When the UE needs to access an application, a DNS request is first initiated, and a destination address of the DNS request is an address of LDNSR (the SMF is allocated to the UE when the terminal registers). The LDNSR and the SMF interactively acquire terminal position information; for class B application, forwarding to local DNS for domain name resolution according to known scheme, and for class A application (such as application 1 and application 2 in the figure), the returned addresses are the same and are all IP addresses of MEC GW in the edge region.

And the LDNSR triggers the SMF (which is integrated with the LDNSR or interacts through a signaling) to implement a local distribution strategy according to the IP address of the analysis result, wherein for the class A application, only the distribution strategy matched with the IP address of the MEC GW needs to be configured.

When accessing different applications of class A, the terminal initiates requests to MEC GW. The service request of the terminal is shunted locally and is sent to the MEC GW through the edge UPF. And the MEC GW carries out secondary distribution on the access request according to the domain name information in the request for the class A application and converts the accessed target address into an internal actual IP address corresponding to the application.

In addition, the B-type application is directly routed according to the IP address, so that the addressing of the edge computing application is realized.

The service addressing system enables the shunting strategy of configuring the gateway address for most edge applications to replace the shunting configuration of all class-A applications, thereby simplifying the shunting strategy configuration of the network; the LDNSR directly resolves the type A local application into a gateway address, and domain name resolution of the type A application does not need local DNS, so that address resolution configuration is simplified; deletion of class A applications on the MEC and change of application states do not affect the configuration of a network shunting strategy and LDNSR, so that the application change is partially unaware; the MEC GW is used as an access gateway, so that the actual address of the class-A application is shielded, and the application safety is improved; the addresses presented by the MEC platform to the outside are greatly reduced, the address conflict of the connection of a plurality of MEC platforms is avoided, and the routing is distinguished only according to the MEC GW address and a small amount of class B application IP, so that the routing setting is simplified.

A schematic structural diagram of an embodiment of the disclosed service addressing system is shown in fig. 7. The service addressing system includes a memory 701 and a processor 702. Wherein: the memory 701 may be a magnetic disk, flash memory, or any other non-volatile storage medium. The memory is for storing instructions in the corresponding embodiments of the traffic addressing method above. Processor 702 is coupled to memory 701 and may be implemented as one or more integrated circuits, such as a microprocessor or microcontroller. The processor 702 is configured to execute the instructions stored in the memory, so that processing load of the LDNSR and the local DNS can be reduced, configuration load and execution load of the edge UPF can be reduced, and expansion difficulty can be reduced.

In one embodiment, as also shown in fig. 8, a service addressing system 800 includes a memory 801 and a processor 802. The processor 802 is coupled to the memory 801 by a BUS 803. The service addressing system 800 may also be coupled to an external storage device 805 via a storage interface 804 to facilitate the retrieval of external data, and may also be coupled to a network or another computer system (not shown) via a network interface 806. And will not be described in detail herein.

In the embodiment, the data instructions are stored in the memory, and the instructions are processed by the processor, so that the processing load of the LDNSR and the local DNS can be reduced, the configuration load and the execution load of the edge UPF are reduced, and the expansion difficulty is reduced.

In another embodiment, a computer readable storage medium has stored thereon computer program instructions which, when executed by a processor, implement the steps of the method in the corresponding embodiment of the service addressing method. As will be appreciated by one skilled in the art, embodiments of the present disclosure may be provided as a method, apparatus, or computer program product. Accordingly, the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present disclosure may take the form of a computer program product embodied on one or more computer-usable non-transitory storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present disclosure is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the disclosure. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

Thus far, the present disclosure has been described in detail. Some details that are well known in the art have not been described in order to avoid obscuring the concepts of the present disclosure. It will be fully apparent to those skilled in the art from the foregoing description how to practice the presently disclosed embodiments.

The methods and apparatus of the present disclosure may be implemented in a number of ways. For example, the methods and apparatus of the present disclosure may be implemented by software, hardware, firmware, or any combination of software, hardware, and firmware. The above-described order for the steps of the method is for illustration only, and the steps of the method of the present disclosure are not limited to the order specifically described above unless specifically stated otherwise. Further, in some embodiments, the present disclosure may also be embodied as programs recorded in a recording medium, the programs including machine-readable instructions for implementing the methods according to the present disclosure. Thus, the present disclosure also covers a recording medium storing a program for executing the method according to the present disclosure.

Finally, it should be noted that: the above examples are intended only to illustrate the technical solutions of the present disclosure and not to limit them; although the present disclosure has been described in detail with reference to preferred embodiments, those of ordinary skill in the art will understand that: modifications to the specific embodiments of the disclosure or equivalent substitutions for parts of the technical features may still be made; all such modifications are intended to be included within the scope of the claims of this disclosure without departing from the spirit thereof.

Claims

1. An application addressing method comprising:

the method comprises the steps that a Local Domain Name System Resolver (LDNSR) determines an application type corresponding to an edge application Domain Name System (DNS) request from a terminal;

under the condition that the application type is determined to be the edge application of the service flow reserved domain name information, feeding back the address of an edge gateway corresponding to the position of the terminal so that the terminal can send an application access request to the edge gateway;

the edge gateway determines the actual address of the application according to the domain name information carried by the application access request under the condition of receiving the application access request;

the edge gateway forwards the application access request to the actual address of the application.

2. The method of claim 1, further comprising:

and the edge gateway establishes connection between the terminal and an application server corresponding to the actual address of the application.

3. The method of claim 1, further comprising:

and the edge user plane function UPF receives the application access request from the terminal and forwards the application access request to the edge gateway.

4. The method according to claim 1, wherein the feeding back an address of an edge gateway corresponding to a terminal location when determining that the application type is an application that reserves domain name information for a service flow includes:

the LDNSR refers to the terminal position information through a Session Management Function (SMF);

the LDNSR judges whether the application type corresponding to the edge application DNS request is an application for reserving domain name information for the service flow;

if the application type is determined to be the edge application of the service flow reserved domain name information, determining the address of the corresponding edge gateway according to the area where the terminal position is located;

and the LDNSR feeds back a DNS response carrying the address of the edge gateway to the terminal under the condition of determining that the edge distribution strategy of the terminal in the corresponding area is issued.

5. The method according to claim 4, wherein feeding back an address of an edge gateway corresponding to a terminal location when determining that the application type is an edge application that reserves domain name information for a service flow, further comprises:

the LDNSR sends a user plane reselection strategy requesting to establish a user plane path of edge distribution to the SMF under the condition that the LDNSR determines that the edge distribution strategy of the terminal in the corresponding area is not issued;

the SMF executes the insertion of an edge protocol data unit session anchor point PSA according to the user plane reselection strategy and configures a shunting strategy of an edge UPF;

and the edge UPF sets a distribution identification rule as a matching target address according to the distribution strategy, wherein the matching target address is the IP address of the edge gateway.

6. The method of claim 1, further comprising:

the LDNSR determines a corresponding local DNS according to the terminal position under the condition that the application type is determined to be the application of which the non-service flow reserves domain name information, and forwards the edge application DNS request to the local DNS;

the local DNS determines an application access address according to the edge application DNS request and feeds the application access address back to the LDNSR;

and the LDNSR triggers the SMF to issue a shunting strategy according to the access address of the application, and feeds back the access address of the application to the user terminal so that the terminal can send an application access request according to the access address of the application.

7. The method of claim 1, further comprising:

and the SMF sets the LDNSR corresponding to the terminal position as a DNS server of the terminal under the condition of receiving an initial session establishment request of the terminal, and anchors the session of the terminal in a central UPF.

8. An application addressing system comprising:

the local domain name system resolver LDNSR is configured to determine an application type corresponding to an edge application domain name system DNS request from a terminal; under the condition that the application type is determined to be the edge application of the service flow reserved domain name information, feeding back the address of the edge gateway corresponding to the terminal position so that the terminal can send an application access request to the edge gateway;

the edge gateway is configured to determine an actual address of an application according to domain name information carried by the application access request under the condition that the application access request is received; forwarding the application access request to a real address of the application.

9. The system of claim 8, further comprising:

and the edge user plane function UPF is configured to receive the application access request from the terminal and forward the application access request to the edge gateway.

10. The system of claim 8, wherein,

the LDNSR is configured to refer to terminal location information through a session management function SMF; judging whether the application type corresponding to the edge application DNS request is an edge application for reserving domain name information for a service flow; if the application type is determined to be the edge application of the service flow reserved domain name information, determining the address of the corresponding edge gateway according to the area where the terminal position is located; under the condition that the edge distribution strategy of the terminal in the corresponding area is determined to be issued, feeding back a DNS response carrying the address of the edge gateway to the terminal; under the condition that the edge shunting strategy of the terminal in the corresponding area is not issued, sending a user plane reselection strategy for requesting to establish a user plane path of edge shunting to the SMF;

further comprising:

the SMF is configured to feed back terminal position information to the LDNSR; performing session anchor point PSA (pressure swing adsorption) insertion of an edge protocol data unit according to the user plane reselection strategy, and configuring a shunting strategy of an edge UPF (unified power flow);

and the edge UPF is configured to set a distribution identification rule as an IP address of the edge gateway according to the distribution strategy, wherein the matching target address is the IP address of the edge gateway.

11. The system of claim 8, wherein,

the LDNSR is also configured to determine a corresponding local DNS according to a terminal position and forward the DNS request to the local DNS under the condition that the application type is determined to be the edge application of which the non-service flow reserves domain name information; triggering the SMF to issue a shunting strategy according to the access address of the application fed back by the local DNS, and feeding back the access address of the application to the user terminal so that the terminal can send an application access request according to the access address of the application;

further comprising:

and the local DNS is configured to determine an access address of an application according to the edge application DNS request and feed back the access address to the LDNSR.

12. An application addressing system comprising:

a memory; and

a processor coupled to the memory, the processor configured to perform the method of any of claims 1-7 based on instructions stored in the memory.

13. A computer readable storage medium having stored thereon computer program instructions which, when executed by a processor, implement the steps of the method of any one of claims 1 to 7.