Application addressing method, system and storage medium

By working in tandem with the LDNSR and the edge gateway, the edge gateway address is directly fed back, simplifying the configuration of network traffic splitting rules, solving the problem of overlapping IP address ranges in edge computing, and enabling efficient application expansion and routing design.

CN114598676BActive Publication Date: 2024-11-22CHINA TELECOM CORP LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202011302294.5
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-11-19
Publication Date
2024-11-22
Estimated Expiration
2040-11-19

AI Technical Summary

Technical Problem

In edge computing scenarios, existing technologies require frequent updates to network traffic splitting rules, and the overlapping IP address ranges when MEC is deployed in a private network environment lead to complex routing designs, making it difficult to achieve efficient application expansion.

Method used

When LDNSR determines that the application type is an edge application that retains domain name information for business flows, it directly feeds back the edge gateway address. The edge gateway determines the actual address based on the domain name information and sets the traffic splitting identification rule to the edge gateway's IP address through the edge UPF, which simplifies network traffic splitting configuration and avoids IP address segment overlap.

Benefits of technology

It reduces the processing burden of LDNSR and local DNS, reduces the configuration and execution burden of edge UPF, improves the flexibility of MEC application expansion, and simplifies route design.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114598676B_ABST
    Figure CN114598676B_ABST
Patent Text Reader

Abstract

The present disclosure proposes an application addressing method, system and storage medium, which relate to the field of communication technology. An application addressing method disclosed in the present disclosure includes: a local domain name system resolver LDNSR determines the application type corresponding to the edge application domain name system DNS request from the terminal; when it is determined that the application type is an edge application that reserves domain name information for business flows, the address of the edge gateway corresponding to the terminal location is fed back so that the terminal sends an application access request to the edge gateway; when the edge gateway receives the application access request, it determines the actual address of the application according to the domain name information carried in the application access request; the edge gateway forwards the application access request to the actual address of the application. Through such a method, the LDNSR can reduce the processing burden of the LDNSR and the local DNS for edge applications that reserve domain name information for business flows that account for the majority of the network, reduce the configuration burden and execution burden of the edge UPF, and reduce the difficulty of expansion.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to an application addressing method, system and storage medium. Background Art

[0002] In the edge computing scenario, application servers are deployed in multiple locations or in a private network. The network needs to identify and judge edge applications, and divert and address user access requests to the nearest service node. In the 3GPP standard research (3GPP TR 23.748), the DNS (Domain Name System) request sent by the terminal is first sent to the centrally set LDNSR (Local Domain Name System Resolver). The LDNSR interacts with the SMF (Session Management Function) to obtain the terminal location, and further forwards the request to the local DNS as a proxy based on the terminal location and the pre-set local DNS mapping relationship. The local DNS provides domain name resolution for MEC (Multi-access Edge Computing) applications deployed in the local area, and resolves different IP addresses for each application. The LDNSR triggers the SMF to issue the corresponding diversion strategy for the local application based on the IP (Internet Protocol) address in the received response packet. Summary of the invention

[0003] One purpose of the present disclosure is to simplify the configuration of network diversion rules and reduce the complexity of application expansion.

[0004] According to one aspect of some embodiments of the present disclosure, an application addressing method is proposed, including: LDNSR determines the application type corresponding to the edge application DNS request from the terminal; when it is determined that the application type is an edge application that reserves domain name information for a business flow, the address of the edge gateway corresponding to the terminal location is fed back so that the terminal sends an application access request to the edge gateway; when the edge gateway receives the application access request, the edge gateway determines the actual address of the application according to the domain name information carried in the application access request; the edge gateway forwards the application access request to the actual address of the application.

[0005] In some embodiments, the application addressing method further includes: the edge gateway establishing a connection between the terminal and an application server corresponding to the access address of the application.

[0006] In some embodiments, the application addressing method further includes: an edge UPF (User Plane Function) receives an application access request from a terminal and forwards it to an edge gateway.

[0007] In some embodiments, when the application type is determined to be an application that reserves domain name information for business flows, the address of the edge gateway corresponding to the terminal location is fed back, including: LDNSR obtaining the terminal location information through SMF; LDNSR determining whether the application type corresponding to the edge application DNS request is an edge application that reserves domain name information for business flows; if the application type is determined to be an edge application that reserves domain name information for business flows, the address of the corresponding edge gateway is determined based on the area where the terminal is located; when LDNSR determines that the edge diversion policy for the terminal in the corresponding area has been issued, the DNS response carrying the address of the edge gateway is fed back to the terminal.

[0008] In some embodiments, when the application type is determined to be an edge application that retains domain name information for a business flow, the address of the edge gateway corresponding to the feedback terminal location also includes: when the LDNSR determines that the edge diversion policy for the terminal in the corresponding area has not been issued, the user plane reselection policy of the user plane path for edge diversion is sent to the SMF to request the establishment of the edge diversion; the SMF performs edge PSA (Protocol Data Unit Session Anchor) insertion according to the user plane reselection policy, and configures the diversion strategy of the edge UPF; the edge UPF sets the diversion identification rule to match the target address as the IP address of the edge gateway according to the diversion strategy.

[0009] In some embodiments, the application addressing method also includes: when the LDNSR determines that the application type is an application that retains domain name information for a non-business flow, the LDNSR determines the corresponding local DNS based on the terminal location, and forwards the edge application DNS request to the local DNS; the local DNS determines the access address of the application based on the edge application DNS request, and feeds it back to the LDNSR; the LDNSR triggers the SMF to issue a diversion strategy based on 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 based on the access address of the application.

[0010] In some embodiments, the application addressing method also includes: when the SMF receives an initial session establishment request from the terminal, it sets the LDNSR corresponding to the terminal location as the DNS server of the terminal and anchors the terminal session to the central UPF.

[0011] Through this method, LDNSR can directly feedback the address of the edge gateway for edge applications that retain domain name information for the majority of business flows in the network, without having to query the address of the specific application in the local DNS, reducing the processing burden of LDNSR and local DNS; for such edge applications, the diversion identification rules of the edge UPF connected to the terminal are set to the address of the edge gateway, reducing the configuration burden and execution burden of the edge UPF; avoiding the problem of overlapping IP address segments of the MEC private network when MEC is deployed in a private network environment and the edge UPF is connected to multiple MEC platforms, improving the flexibility of edge application expansion in each MEC and reducing the difficulty of expansion.

[0012] According to one aspect of some embodiments of the present disclosure, an application addressing system is proposed, including: an LDNSR, configured to determine the application type corresponding to an edge application DNS request from a terminal; when it is determined that the application type is an edge application that reserves domain name information for a business flow, feedback the address of an edge gateway corresponding to the terminal location so that the terminal sends an application access request to the edge gateway; the edge gateway, configured to, when receiving an application access request, determine the actual address of the application based on the domain name information carried in the application access request; and forward the application access request to the actual address of the application.

[0013] In some embodiments, the application addressing system further includes: an edge UPF configured to receive an application access request from a terminal and forward it to an edge gateway.

[0014] In some embodiments, the LDNSR is configured to obtain terminal location information through the SMF; determine whether the application type corresponding to the edge application DNS request is an edge application that reserves domain name information for a business flow; if it is determined that the application type is an edge application that reserves domain name information for a business flow, determine the address of the corresponding edge gateway according to the area where the terminal is located; when it is determined that the edge diversion policy for the terminal in the corresponding area has been issued, feedback a DNS response carrying the address of the edge gateway to the terminal; when it is determined that the edge diversion policy for the terminal in the corresponding area has not been issued, send a user plane reselection policy requesting the SMF to establish a user plane path for edge diversion; the application addressing system also includes: SMF, configured to feedback terminal location information to the LDNSR; perform edge PSA insertion according to the user plane reselection policy, and configure the diversion strategy of the edge UPF; the edge UPF, configured to set the diversion identification rule according to the diversion strategy to match the target address as the IP address of the edge gateway.

[0015] In some embodiments, the LDNSR is also configured to, when determining that the application type is an application that reserves domain name information for a non-business flow, determine the corresponding local DNS based on the terminal location, and forward the edge application DNS request to the local DNS; trigger the SMF to issue a diversion strategy based on the access address of the application fed back by the local DNS, and feed back the access address of the application to the user terminal, so that the terminal sends an application access request based on the access address of the application; the application addressing system also includes: a local DNS, which is configured to determine the access address of the edge application based on the edge application DNS request, and feed it back to the LDNSR.

[0016] According to one aspect of some embodiments of the present disclosure, an application addressing system is proposed, including: a memory; and a processor coupled to the memory, wherein the processor is configured to execute any one of the above application addressing methods based on instructions stored in the memory.

[0017] In such an application addressing system, LDNSR can directly feedback the address of the edge gateway for applications that retain domain name information for the majority of business flows in the network, without having to query the address of the specific application in the local DNS, reducing the processing burden of LDNSR and local DNS; for such applications, the diversion identification rules of the edge UPF connected to the terminal are all set to match the target address as the address of the edge gateway, reducing the configuration burden and execution burden of the edge UPF; avoiding the problem of overlapping IP address segments of the MEC private network when MEC is deployed in a private network environment and the edge UPF is connected to multiple MEC platforms, improving the flexibility of edge application expansion in each MEC and reducing the difficulty of expansion.

[0018] According to one aspect of some embodiments of the present disclosure, a computer-readable storage medium is provided, on which computer program instructions are stored, and when the instructions are executed by a processor, the steps of any one of the above application addressing methods are implemented.

[0019] By executing instructions on such a computer-readable storage medium, LDNSR can directly feedback the address of the edge gateway for edge applications that retain domain name information for the majority of business flows in the network, without having to query the address of the specific application in the local DNS, thereby reducing the processing burden of LDNSR and local DNS; for such applications, the diversion identification rules of the edge UPF connected to the terminal are set to match the target address as the address of the edge gateway, thereby reducing the configuration burden and execution burden of the edge UPF; avoiding the problem of overlapping IP address segments of the MEC private network when MEC is deployed in a private network environment and the edge UPF is connected to multiple MEC platforms, thereby improving the flexibility of edge application expansion in each MEC and reducing the difficulty of expansion. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] The drawings described herein are used to provide a further understanding of the present disclosure and constitute a part of the present disclosure. The illustrative embodiments of the present disclosure and their descriptions are used to explain the present disclosure and do not constitute an improper limitation on the present disclosure. In the drawings:

[0021] Figure 1 Flowcharts of some embodiments of the application addressing method of the present disclosure.

[0022] Figure 2 Flowcharts of other embodiments of the application addressing method disclosed herein.

[0023] Figure 3 The present invention is a signaling flow chart of some further embodiments of the application addressing method disclosed in the present invention.

[0024] Figure 4 Schematic diagram of some embodiments of an application addressing system for the present disclosure.

[0025] Figure 5 A schematic diagram of the network structure of some embodiments of the application addressing system disclosed in the present invention.

[0026] Figure 6 Schematic diagrams of other embodiments of the application addressing system disclosed in the present invention.

[0027] Figure 7 Schematic diagrams of some further embodiments of the application addressing system disclosed herein.

[0028] Figure 8 Schematic diagrams of some further embodiments of the application addressing system disclosed herein. DETAILED DESCRIPTION

[0029] The technical solution of the present disclosure is further described in detail below through the accompanying drawings and embodiments.

[0030] The inventors found that in the related technology, with the expansion of applications deployed on MEC, the network needs to add local diversion identification rules based on the IP address of the application; in order to accurately resolve the IP address of the local application according to the user's location, the domain name resolution request of the local application needs to be forwarded to the local DNS and the domain name resolution service is implemented by the local DNS; in addition, since the MEC deployment environment may be a private network environment, when multiple MEC platforms are connected behind the edge UPF, in order to ensure correct routing, the IP address segments of each MEC private network cannot overlap, which brings challenges to network deployment and routing design. When the IP address segment is repeated, the server address needs to be converted again, which makes the implementation complicated.

[0031] The flowcharts of some embodiments of the application addressing method disclosed in the present invention are as follows: Figure 1 shown.

[0032] In step 101, the LDNSR determines the application type corresponding to the edge application DNS request from the terminal. In some embodiments, edge applications can be divided into two categories (assuming they are called Class A and Class B, and the aliases of Class A and Class B in the following text have the same meaning as in this paragraph), where Class A is an edge application that will reserve a domain name in the service flow, and Class B is an application that does not guarantee the reservation of a domain name in the service flow. The inventors found that in actual application, Class A applications account for the majority.

[0033] In step 102, if the application type is class A, step 103 is performed. In some embodiments, if the application type is class B, it can be performed according to the solution in the related art.

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

[0035] In some embodiments, the LDNSR may query the terminal location information through the SMF, and then determine the edge gateway address of the service area corresponding to the terminal location. In some embodiments, the LDNSR pre-stores the corresponding relationship between the service area and the edge gateway address.

[0036] In some embodiments, the LDNSR establishes an edge user plane according to the determined edge gateway address, determines the diversion rules of the edge UPF accessed by the terminal, and implements the diversion of the edge UPF to the edge gateway.

[0037] 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 executed.

[0038] In step 105, the edge gateway determines the access address of the application according to the domain name information carried in the application access request. In some embodiments, the correspondence between the domain name and the access address (such as IP address, port) in the service area is pre-configured in the edge gateway.

[0039] In some embodiments, when the edge UPF receives an application access request from a terminal, it forwards the application access request to the edge gateway.

[0040] 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 the application server corresponding to the actual address of the application, and the terminal and the application server interact through the edge gateway.

[0041] Through this method, LDNSR can directly feedback the address of the edge gateway for applications that retain domain name information for the majority of business flows in the network, without having to query the address of the specific application in the local DNS, reducing the processing burden of LDNSR and local DNS; for such applications, the diversion identification rules of the edge UPF connected to the terminal are all set to match the target address as the address of the edge gateway, reducing the configuration burden and execution burden of the edge UPF; avoiding the problem of overlapping IP address segments of the MEC private network when MEC is deployed in a private network environment and the edge UPF is connected to multiple MEC platforms, improving the flexibility of edge application expansion in each MEC and reducing the difficulty of expansion.

[0042] Flow charts of other embodiments of the application addressing method disclosed in the present invention are as follows: Figure 2 shown.

[0043] In step 201, LDNSR searches for terminal location information through SMF. In some embodiments, LDNSR can be co-located with SMF.

[0044] In step 202, the LDNSR determines the application type corresponding to the edge application DNS request from the terminal.

[0045] In step 203, when the LDNSR determines that the application type is an application for retaining domain name information of a service flow, step 204 is executed.

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

[0047] In step 205, the LDNSR determines whether the edge diversion policy of the terminal in the corresponding area has been issued. In some embodiments, if the terminal has accessed the edge gateway of the corresponding area (to access the same or different edge application as the current one), the edge diversion policy has been issued. If it is determined that the edge diversion policy of the terminal in the corresponding area has been issued, step 206 is executed.

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

[0049] 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 based on the diversion strategy of the edge UPF, the application access request is sent to the edge gateway. Since the user wants to access a Class A application, the application access request includes the domain name information of the edge application and the address of the edge gateway.

[0050] 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.

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

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

[0053] Based on the fact that most applications are Class A applications, this method is used to introduce MEC GW to perform secondary distribution of Class A applications based on domain names, which simplifies the configuration of network diversion rules, reduces frequent rule update signaling interactions, and solves the problem of distinguishing routes for multiple private network MEC platforms, simplifying the diversion and addressing implementation of edge applications.

[0054] In some embodiments, Figure 2 As shown, in the above step 205, if the edge diversion strategy of the terminal in the corresponding area has not been issued, that is, the terminal has not accessed the class A edge application in the corresponding area, the following steps 211 to 213 are executed.

[0055] In step 211, a user plane reselection policy for establishing a user plane path for edge offloading is sent to the SMF, carrying the address of the edge gateway.

[0056] In step 212, the SMF performs edge PSA insertion according to the user plane reselection strategy and configures the diversion strategy of the edge UPF.

[0057] In step 213, the edge UPF sets the diversion identification rule to match the IP address of the edge gateway whose target address is according to the diversion strategy.

[0058] Through this method, based on the process of configuring the diversion strategy for edge UPF in related technologies, the edge UPF can be diverted to the edge gateway by carrying the address of the edge gateway. There is no need to improve SMF and UPF, which is conducive to promotion and application.

[0059] In some embodiments, if the application type is determined to be Class B (an application that does not retain domain name information in the service flow) in the above step 203, steps 221 to 223 are executed.

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

[0061] In step 222, the local DNS determines the access address of the application according to the edge application DNS request and feeds it back to the LDNSR.

[0062] In step 223, LDNSR triggers SMF to issue a diversion strategy, which carries the access address of the application. After the configuration is completed, the edge UPF will divert the service flow to the actual access address of the edge application. LDNSR feeds back the actual access address of the application to the user terminal so that the user can send an access request to the access address of the application. The access request is not guaranteed to carry the domain name information of the application.

[0063] 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. To resolve the problem of IP address segment conflicts, the access address of the application provided to the user may be an external address converted from the actual address of the application. The access request initiated by the user based on the access address of the application will be converted to the actual address of the application after reaching the corresponding MEC platform, thereby achieving access to the edge application.

[0064] Through this method, compatibility with Class A and Class B services can be achieved, and the reliability of application addressing can be improved.

[0065] The signaling flow charts of some other embodiments of the application addressing method disclosed in the present invention are as follows: Figure 3 shown.

[0066] In 301, the UE (User Element) establishes an initial session, the SMF assigns the LDNSR to the UE as its DNS server, and anchors the session to the central UPF.

[0067] In 302, the UE accesses an edge application through a domain name and first initiates a DNS request, which is sent to the LDNSR via the central UPF.

[0068] In 303, the LDNSR queries the UE location information through the SMF.

[0069] In 304, the LDNSR determines that the accessed application is a Class A application, and inquires about the corresponding MEC GW address based on the pre-configured correspondence between the service area and the MEC GW address.

[0070] In 305, if the LDNSR determines that the edge diversion strategy has not been issued (the UE does not use edge services in the service area), it initiates a user plane reselection strategy to the SMF, requiring the establishment of a user plane path for edge diversion, and executes the following 306; otherwise, skip 306 and 307 and execute 308.

[0071] In 306, the SMF implements edge PSA insertion and configures the diversion strategy of the edge UPF, where the diversion identification rule is the IP address of the MEC GW.

[0072] In 307, the SMF replies to the LDNSR that the edge user plane has been established.

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

[0074] In 309, the UE initiates an application access request to the IP address responded by the DNS, and the request also carries the domain name of the application. The request is distributed from the edge UPF to the MEC GW through the network.

[0075] In 310, the MEC GW performs the role of an access proxy and queries the internal actual IP of the corresponding edge application according to the URL information in the request.

[0076] 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.

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

[0078] Through this method, for most edge applications, only the diversion strategy of the gateway address can be configured to replace the diversion configuration of all Class A applications, which simplifies the network diversion strategy configuration; LDNSR directly resolves Class A local applications to gateway addresses, and the domain name resolution of Class A applications does not require the participation of local DNS, which simplifies the address resolution configuration; the deletion of Class A applications on MEC and the change of application status do not affect the network diversion strategy and LDNSR configuration, thereby partially realizing the perception of application changes; MEC GW, as an access gateway, shields the actual address of Class A applications and improves the security of applications; the addresses presented to the outside by the MEC platform are greatly reduced, avoiding address conflicts when multiple MEC platforms are connected. The 5G core network only needs to distinguish routes based on the MEC GW address and a small number of Class B application IPs, which simplifies the routing settings.

[0079] Schematic diagrams of some embodiments of the application addressing system disclosed in the present invention are as follows Figure 4 shown.

[0080] LDNSR 41 can determine the application type corresponding to the edge application DNS request from the terminal. In some embodiments, edge applications can be divided into two categories (assuming they are called Class A and Class B), where Class A is an application that reserves domain names in the business flow, and Class B is an application that does not guarantee the reservation of domain names in the business flow. In the case where the application type is determined to be an application that reserves domain name information in the business flow (Class A application), the address of the edge gateway corresponding to the terminal location is fed back so that the terminal sends an application access request to the edge gateway.

[0081] In some embodiments, if the application type is Class B, it can be executed according to the solution in the related art.

[0082] When receiving an application access request, 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. Figure 4 As shown, the application addressing system may also include UPF 43, which can receive application access requests from terminals and forward them to edge gateways.

[0083] In such an application addressing system, LDNSR can directly feedback the address of the edge gateway for applications that retain domain name information for the majority of business flows in the network, without having to query the address of the specific application in the local DNS, reducing the processing burden of LDNSR and local DNS; for such applications, the diversion identification rules of the edge UPF connected to the terminal are all set to match the target address as the address of the edge gateway, reducing the configuration burden and execution burden of the edge UPF; avoiding the problem of overlapping IP address segments of the MEC private network when MEC is deployed in a private network environment and the edge UPF is connected to multiple MEC platforms, improving the flexibility of edge application expansion in each MEC and reducing the difficulty of expansion.

[0084] In some embodiments, LDNSR 41 can also obtain terminal location information through SMF; determine whether the application type corresponding to the edge application DNS request is an application that reserves domain name information for the business flow; if the application type is determined to be an application that reserves domain name information for the business flow, determine the address of the corresponding edge gateway according to the area where the terminal is located; if it is determined that the edge diversion policy of the terminal in the corresponding area has been issued, feedback a DNS response carrying the address of the edge gateway to the terminal; if it is determined that the edge diversion policy of the terminal in the corresponding area has not been issued, send a request to SMF to establish a user plane reselection policy for the user plane path of the edge diversion. Figure 4 As shown, the application addressing system also includes SMF44, which can execute the terminal location subscription in the 5G core network and feedback the terminal location information to LDNSR 41; perform edge PSA insertion according to the user plane reselection strategy, and configure the diversion strategy of the edge UPF. The edge UPF43 can set the diversion identification rule to match the target address as the IP address of the edge gateway according to the diversion strategy.

[0085] Such a system can realize the diversion of edge UPF to edge gateway based on the process of configuring diversion strategy for edge UPF in related technologies by carrying the address of edge gateway, without the need to improve SMF and UPF, which is conducive to promotion and application.

[0086] In some embodiments, LDNSR can also determine the corresponding local DNS according to the terminal location when the application type is determined to be an application that retains domain name information for non-business flows, and forward the edge application DNS request to the local DNS; trigger SMF to issue a diversion strategy based on the application access address fed back by the local DNS, and feed back the application access address to the user terminal so that the terminal can send an application access request based on the application access address. Figure 4 As shown, the application addressing system also includes a local DNS 45, which can determine the actual access address of the application according to the edge application DNS request and feed it back to the LDNSR 41.

[0087] Such a system can achieve compatibility with Class A and Class B services and improve the reliability of application addressing.

[0088] The network structure diagrams of some embodiments of the application addressing system disclosed in the present invention are as follows: Figure 5 As shown, it mainly involves 5GC (5G core network) and MEC platform.

[0089] In 5GC, UPF is the user plane. 5GC implements and ensures that access to edge services is diverted from edge UPF.

[0090] The MEC platform provides the deployment environment and necessary management methods for edge applications.

[0091] The central DNS is the operator's traditional DNS, which provides domain name resolution services for traditional mobile Internet.

[0092] MEC GW is deployed on the MEC platform, receives edge application access requests from the 5G network, and implements access distribution of edge applications deployed on the MEC platform, including distribution by domain name and distribution by IP address.

[0093] Edge applications are applications deployed on the MEC platform.

[0094] SMF implements user plane management.

[0095] LDNSR has the application function of DNS function and provides DNS or DNS proxy function.

[0096] like Figure 5 As shown in the figure, the MEC GW function is set in the MEC platform as a unified interface gateway device for terminals to access edge applications. The LDNSR configures the correspondence between the location and the MEC GW address, and has pre-set the type (Class A or Class B) corresponding to the edge application. When the terminal initiates a DNS request, the LDNSR first determines the application type and performs domain name resolution for Class B applications according to known methods (as shown by the dotted arrow in the figure).

[0097] The domain name resolution request for Class A applications executes the process shown by the arrow in the figure. LDNSR uniformly replies to the corresponding MEC GW address based on the terminal location (the MEC platform and MEC GW have a one-to-one relationship). When the terminal accesses a Class A edge application on the same MEC, it initiates a request to the MEC GW. Therefore, the edge UPF only needs to configure the diversion rules that match the gateway IP, so that for Class A applications, the diversion rules do not need to change with the addition or deletion of applications. MEC GW acts as an access agent. For Class A applications, it addresses the access request based on the domain name information in the access request and forwards it to the actual IP corresponding to the internal application; Class B applications are still distributed by IP address, so that the terminal can access the application service it requests.

[0098] by Figure 6 Taking the domain name and application access process shown in as an example, MEC GW is introduced on the MEC platform as an access proxy.

[0099] When the UE needs to access an application, it first initiates a DNS request. The target address of the DNS request is the address of the LDNSR (assigned to the UE by the SMF when the terminal is registered). The LDNSR interacts with the SMF to obtain the terminal location information; for Class B applications, it is forwarded to the local DNS for domain name resolution according to the known scheme. For Class A applications (such as Application 1 and Application 2 in the figure), the returned address is the same, which is the IP address of the MEC GW in the edge area.

[0100] At the same time, LDNSR triggers SMF (co-established with LDNSR or interacting through signaling) to implement local diversion strategy based on the IP address of the resolution result. For Class A applications, it is only necessary to configure the diversion strategy that matches the IP address of MEC GW.

[0101] When the terminal accesses different applications of Class A, it initiates a request to the MEC GW. The service request of the terminal is diverted locally and sent to the MEC GW via the edge UPF. For Class A applications, the MEC GW performs secondary distribution of the access request based on the domain name information in the request and converts the access target address into the actual internal IP address corresponding to the application.

[0102] In addition, Class B applications are routed directly based on IP addresses, thereby achieving addressing of edge computing applications.

[0103] Such a service addressing system allows most edge applications to only configure the diversion strategy of the gateway address instead of the diversion configuration of all Class A applications, simplifying the network diversion strategy configuration; LDNSR directly resolves Class A local applications to gateway addresses, and the domain name resolution of Class A applications does not require the participation of local DNS, simplifying the address resolution configuration; the deletion of Class A applications on MEC and the change of application status do not affect the network diversion strategy and LDNSR configuration, thereby partially realizing the perception of application changes; MEC GW, as an access gateway, shields the actual address of Class A applications and improves the security of applications; the addresses presented to the outside by the MEC platform are greatly reduced, avoiding address conflicts for multiple MEC platform connections, and only needs to distinguish routes based on the MEC GW address and a small number of Class B application IPs, simplifying the routing settings.

[0104] The structural diagram of an embodiment of the service addressing system disclosed in the present invention is as follows Figure 7 As shown. The service addressing system includes a memory 701 and a processor 702. Among them: the memory 701 can be a disk, a flash memory or any other non-volatile storage medium. The memory is used to store the instructions in the corresponding embodiment of the service addressing method described above. The processor 702 is coupled to the memory 701 and can be implemented as one or more integrated circuits, such as a microprocessor or a microcontroller. The processor 702 is used to execute instructions stored in the memory, which can reduce the processing burden of the LDNSR and the local DNS, reduce the configuration burden and execution burden of the edge UPF, and reduce the difficulty of expansion.

[0105] In one embodiment, it is also possible to Figure 8 As shown, the service addressing system 800 includes a memory 801 and a processor 802. The processor 802 is coupled to the memory 801 via a BUS bus 803. The service addressing system 800 can also be connected to an external storage device 805 via a storage interface 804 to call external data, and can also be connected to a network or another computer system (not shown) via a network interface 806. No detailed description will be given here.

[0106] In this embodiment, by storing data instructions in a memory and then processing the instructions through a processor, the processing burden of LDNSR and local DNS can be reduced, the configuration burden and execution burden of edge UPF can be reduced, and the difficulty of expansion can be reduced.

[0107] In another embodiment, a computer-readable storage medium stores 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. It should be understood by those skilled in the art that the embodiments of the present disclosure may be provided as methods, devices, or computer program products. Therefore, the present disclosure may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present disclosure may take the form of a computer program product implemented on one or more computer-usable non-transient storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0108] The present disclosure is described with reference to flowcharts and / or block diagrams of methods, devices (systems) and computer program products according to embodiments of the present disclosure. It should be understood that each process and / or block in the flowchart and / or block diagram and the combination of processes and / or blocks in the flowchart and / or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0109] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0110] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0111] So far, the present disclosure has been described in detail. In order to avoid obscuring the concept of the present disclosure, some details known in the art are not described. Based on the above description, those skilled in the art can fully understand how to implement the technical solution disclosed here.

[0112] The method and apparatus of the present disclosure may be implemented in many ways. For example, the method and apparatus of the present disclosure may be implemented by software, hardware, firmware, or any combination of software, hardware, and firmware. The above order of steps for 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 otherwise specifically stated. In addition, in some embodiments, the present disclosure may also be implemented as a program recorded in a recording medium, which includes machine-readable instructions for implementing the method according to the present disclosure. Therefore, the present disclosure also covers a recording medium storing a program for executing the method according to the present disclosure.

[0113] Finally, it should be noted that the above embodiments are only used to illustrate the technical solution of the present disclosure rather than to limit it. Although the present disclosure has been described in detail with reference to the preferred embodiments, ordinary technicians in the relevant field should understand that the specific implementation methods of the present disclosure can still be modified or some technical features can be replaced by equivalents without departing from the spirit of the technical solution of the present disclosure, which should be included in the scope of the technical solution for protection of the present disclosure.

Claims

1. An application addressing method, comprising: The local domain name system resolver LDNSR determines the application type corresponding to the edge application domain name system DNS request from the terminal; In the case where it is determined that the application type is an edge application in which the service flow retains the domain name information, the address of the edge gateway corresponding to the terminal location is fed back, including: The LDNSR obtains the terminal location information; The LDNSR determines whether the application type corresponding to the edge application DNS request is an application for which domain name information is reserved for a service flow; If it is determined that the application type is an edge application in which the service flow retains domain name information, the address of the corresponding edge gateway is determined according to the area where the terminal is located; When the LDNSR determines that the edge diversion policy of the terminal in the corresponding area has been issued, the LDNSR feeds back a DNS response carrying the address of the edge gateway to the terminal so that the terminal sends an application access request to the edge gateway; When receiving the application access request, the edge gateway determines the actual address of the application according to the domain name information carried in the application access request; The edge gateway forwards the application access request to the actual address of the application.

2. The method according to claim 1, further comprising: The edge gateway establishes a connection between the terminal and an application server corresponding to the actual address of the application.

3. The method according to claim 1, further comprising: The edge user plane function UPF receives the application access request from the terminal and forwards it to the edge gateway.

4. According to the method of claim 1, the LDNSR obtaining the terminal location information comprises: The LDNSR consults the terminal location information through the session management function SMF.

5. According to the method of claim 4, when determining that the application type is an edge application in which the service flow retains domain name information, the address of the edge gateway corresponding to the feedback terminal location further includes: The LDNSR sends a user plane reselection strategy requesting to establish a user plane path for edge offloading to the SMF when determining that the edge offloading strategy for the terminal in the corresponding area has not been issued; The SMF performs edge protocol data unit session anchor PSA insertion according to the user plane reselection strategy, and configures the diversion strategy of the edge UPF; The edge UPF sets the diversion identification rule according to the diversion strategy to match the target address as the IP address of the edge gateway.

6. The method according to claim 1, further comprising: When the LDNSR determines that the application type is an application that retains domain name information for a non-business flow, determines the corresponding local DNS according to the terminal location, and forwards the edge application DNS request to the local DNS; The local DNS determines the access address of the application according to the edge application DNS request and feeds it back to the LDNSR; The LDNSR triggers the SMF to issue a diversion 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.

7. The method according to claim 1, further comprising: When receiving the initial session establishment request from the terminal, the SMF sets the LDNSR corresponding to the terminal location as the DNS server of the terminal, and anchors the session of the terminal to the central UPF.

8. An application addressing system, comprising: A 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; In the case where it is determined that the application type is an edge application that reserves domain name information for a business flow, the address of the edge gateway corresponding to the terminal location is fed back, including: obtaining terminal location information; judging whether the application type corresponding to the edge application DNS request is an application that reserves domain name information for a business flow; if it is determined that the application type is an edge application that reserves domain name information for a business flow, the address of the corresponding edge gateway is determined according to the area where the terminal location is located; in the case where it is determined that the edge diversion strategy for the terminal in the corresponding area has been issued, a DNS response carrying the address of the edge gateway is fed back to the terminal, so that the terminal sends an application access request to the edge gateway; The edge gateway is configured to, upon receiving the application access request, determine the actual 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.

9. The system according to claim 8, further comprising: The edge user plane function UPF is configured to receive the application access request from the terminal and forward it to the edge gateway.

10. The system according to claim 8, wherein: The LDNSR is configured to query the terminal location information through the session management function SMF; and is also configured to: when it is determined that the edge diversion strategy of the terminal in the corresponding area has not been issued, send a user plane reselection strategy requesting to establish a user plane path for edge diversion to the SMF; Also includes: The SMF is configured to feed back the terminal location information to the LDNSR; perform edge protocol data unit session anchor PSA insertion according to the user plane reselection strategy, and configure the edge UPF diversion strategy; The edge UPF is configured to set the diversion identification rule to match the IP address of the edge gateway whose target address is the IP address of the edge gateway according to the diversion strategy.

11. The system according to claim 8, wherein: The LDNSR is further configured to, when determining that the application type is an edge application that retains domain name information for a non-business flow, determine the corresponding local DNS according to the terminal location, and forward the edge application DNS request to the local DNS; trigger the SMF to issue a diversion strategy according to the access address of the application fed back by the local DNS, and feed 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; Also includes: The local DNS is configured to determine the access address of the application according to the edge application DNS request and feed it back to the LDNSR.

12. An application addressing system, comprising: Memory; as well as A processor coupled to the memory, the processor being configured to execute the method according to any one of claims 1 to 7 based on instructions stored in the memory.

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