CN114598676B - Application addressing method, system and storage medium - Google Patents

Application addressing method, system and storage medium Download PDF

Info

Publication number
CN114598676B
CN114598676B CN202011302294.5A CN202011302294A CN114598676B CN 114598676 B CN114598676 B CN 114598676B CN 202011302294 A CN202011302294 A CN 202011302294A CN 114598676 B CN114598676 B CN 114598676B
Authority
CN
China
Prior art keywords
application
edge
terminal
address
ldnsr
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202011302294.5A
Other languages
Chinese (zh)
Other versions
CN114598676A (en
Inventor
刘洁
林奕琳
朱红梅
何宇峰
刘龙龙
杨峰义
张建敏
曹磊
王波
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Telecom Corp Ltd
Original Assignee
China Telecom Corp Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by China Telecom Corp Ltd filed Critical China Telecom Corp Ltd
Priority to CN202011302294.5A priority Critical patent/CN114598676B/en
Publication of CN114598676A publication Critical patent/CN114598676A/en
Application granted granted Critical
Publication of CN114598676B publication Critical patent/CN114598676B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/141—Setup of application sessions

Landscapes

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

Abstract

The disclosure provides an application addressing method, an application addressing system and a storage medium, and relates to the technical field of communication. An application addressing method of the present disclosure includes: the local domain name system resolver LDNSR determines the application type corresponding to the edge application domain name system DNS request from the terminal; under the condition that the application type is determined to be the edge application of which the service flow reserves domain name information, feeding back the address of the edge gateway corresponding to the position of the terminal so that the terminal sends an application access request to the edge gateway; under the condition that an application access request is received, the edge gateway determines the actual address of the application according to domain name information carried by the application access request; the edge gateway forwards the application access request to the actual address of the application. By the method, LDNSR can save the edge application of domain name information for most of service flows in the network, reduce the processing burden of LDNSR and local DNS, reduce the configuration burden and execution burden of 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
In the scenario of edge computing, an application server is deployed in multiple points or the server is deployed in a private network, and the network needs to identify and judge edge applications, and shunt and address access requests of users to the nearest service node. In the standard research of 3GPP (3 GPP TR 23.748), a DNS (Domain NAME SYSTEM ) request sent by a terminal is first sent to a centrally disposed LDNSR (Local Domain NAME SYSTEM Resolver), LDNSR interacts with an SMF (Session Management Function ) to obtain a terminal location, and further forwards the request to a Local DNS with 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 the local area, resolving different IP addresses for each application, and LDNSR triggers the SMF to issue a corresponding offload policy for the local application according to the IP (Internet Protocol ) address in the received response packet.
Disclosure of Invention
An object of the present disclosure is to simplify network offload rule configuration and reduce complexity of application extension.
According to an aspect of some embodiments of the present disclosure, there is provided an application addressing method, comprising: LDNSR determining an application type corresponding to an edge application DNS request from the terminal; under the condition that the application type is determined to be the edge application of which the service flow reserves domain name information, feeding back the address of the edge gateway corresponding to the position of the terminal so that the terminal sends an application access request to the edge gateway; under the condition that an application access request is received, the edge gateway determines the actual address of the application according to domain name information carried by the application access request; 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 the application access request from the terminal and forwards it to the edge gateway.
In some embodiments, in a case that it is determined that the application type is an application in which the service flow retains domain name information, feeding back an address of an edge gateway corresponding to a terminal position includes: LDNSR acquiring terminal position information through SMF; LDNSR judging whether the application type corresponding to the edge application DNS request is an edge application which reserves domain name information for the service flow; if the application type is determined to be the edge application of which the service flow reserves domain name information, determining the address of the corresponding edge gateway according to the area where the terminal position is located; LDNSR feeding back a DNS response carrying the address of the edge gateway to the terminal under the condition that the terminal is determined to have issued the edge splitting policy of the corresponding area.
In some embodiments, in a case that it is determined that the application type is an edge application where the service flow retains domain name information, feeding back an address of an edge gateway corresponding to the terminal position further includes: LDNSR sending a user plane reselection strategy for requesting to establish a user plane path of edge shunting to the SMF under the condition that the edge shunting strategy of the terminal in the corresponding area is not issued; the SMF executes edge PSA (Protocol Data Unit Session Anchor ) insertion according to the user plane reselection strategy, and configures a diversion strategy of the edge UPF; the edge UPF sets a splitting identification rule as an IP address which is matched with the target address as an edge gateway according to a splitting strategy.
In some embodiments, applying the addressing method further comprises: LDNSR under the condition that the application type is determined to be the application of which the non-service flow reserves domain name information, determining a corresponding local DNS according to the terminal position, and forwarding an edge application DNS request to the local DNS; the local DNS determines the access address of the application according to the DNS request of the edge application and feeds back the access address to LDNSR; LDNSR triggering the SMF to issue a distribution strategy according to the access address of the application, 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.
In some embodiments, applying the addressing method further comprises: under the condition that the SMF receives an initial session establishment request of the terminal, LDNSR corresponding to the terminal position is set as a DNS server side of the terminal, and the session of the terminal is anchored in a central UPF.
By the method, LDNSR can directly feed back the address of the edge gateway for the edge application of which the domain name information is reserved for most of the service flows in the network, and the address of a specific application is not required to be queried in the local DNS, so that the processing burden of LDNSR and the local DNS is reduced; for the edge application, the distribution identification rules of the edge UPF connected by the terminal are set 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 the IP address segments of the MEC private network overlap when the MECs are deployed in the private network environment and the edge UPF is connected with a plurality of MEC platforms is avoided, the flexibility of edge application expansion in each MEC is improved, and the expansion difficulty is reduced.
According to an aspect of some embodiments of the present disclosure, there is provided an application addressing system comprising: LDNSR configured to determine an application type corresponding to an edge application DNS request from the terminal; under the condition that the application type is determined to be the edge application of which the service flow reserves domain name information, feeding back the address of the edge gateway corresponding to the position of the terminal so that the terminal sends an application access request to the edge gateway; the edge gateway is configured to determine the actual address of the application according to domain name information carried by the application access request under the condition that the application access request is received; the application access request is forwarded to the actual address of the application.
In some embodiments, the application addressing system further comprises: the edge UPF is configured to receive an application access request from the terminal and forward to the edge gateway.
In some embodiments LDNSR is configured to obtain terminal location information via SMF; judging whether an application type corresponding to the edge application DNS request is an edge application of which the domain name information is reserved for the service flow; if the application type is determined to be the edge application of which the service flow reserves 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 terminal is determined to have issued an edge shunting strategy in a corresponding area, feeding back a DNS response carrying an address of an edge gateway to the terminal; under the condition that the terminal is not issued in the edge shunting strategy of the corresponding area, sending a user plane reselection strategy for requesting to establish a user plane path of edge shunting to the SMF; the application addressing system further comprises: SMF configured to feed back terminal location information to LDNSR; performing edge PSA insertion according to a user plane reselection strategy, and configuring a splitting strategy of an edge UPF; and the edge UPF is configured to set a splitting identification rule according to a splitting strategy to match the target address with the IP address of the edge gateway.
In some embodiments, LDNSR is further configured to, in the case of determining that the application type is an application for which the non-traffic flow retains domain name information, determine a corresponding local DNS according to the terminal location, forward the edge application DNS request to the local DNS; triggering the SMF to issue a distribution 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; the application addressing system further comprises: the local DNS is configured to determine, according to the edge application DNS request, the access address of the edge application, and feed back to 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 execute any of the application addressing methods above based on instructions stored in the memory.
In the application addressing system, LDNSR can directly feed back the address of the edge gateway for the application of which the domain name information is reserved for most of service flows in the network, and the address of a specific application is not required to be queried in the local DNS, so that the processing burden of LDNSR and the local DNS is reduced; for such applications, the shunting recognition rules of the edge UPF connected by the terminal are set to be the addresses of the edge gateway with the matching target address, so that the configuration burden and the execution burden of the edge UPF are reduced; the problem that the IP address segments of the MEC private network overlap when the MECs are deployed in the private network environment and the edge UPF is connected with a plurality of MEC platforms is avoided, the flexibility of edge application expansion in each MEC is improved, and the expansion difficulty is reduced.
According to an aspect of some embodiments of the present disclosure, a computer-readable storage medium is presented, 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, LDNSR can directly feed back the address of the edge gateway for the edge application of which the domain name information is reserved for most of the service flows in the network, and the address of a specific application is not required to be queried in the local DNS, so that the processing burden of LDNSR and the local DNS is reduced; for such applications, the shunting recognition rules of the edge UPF connected by the terminal are set to be the addresses of the edge gateway with the matching target address, so that the configuration burden and the execution burden of the edge UPF are reduced; the problem that the IP address segments of the MEC private network overlap when the MEC is deployed in the private network environment and the edge UPF is connected with a plurality of MEC platforms is avoided, the flexibility of edge application expansion in each MEC is improved, and the expansion difficulty is reduced.
Drawings
The accompanying drawings, which are included to provide a further understanding of the disclosure, illustrate and explain the present disclosure, and together with the description serve to explain the present disclosure. In the drawings:
fig. 1 is a flow chart of some embodiments of the application addressing method of the present disclosure.
Fig. 2 is a flow chart of other embodiments of the application addressing method of the present disclosure.
Fig. 3 is a signaling flow diagram of further embodiments of the application addressing method of the present disclosure.
Fig. 4 is a schematic diagram of some embodiments of an application addressing system of the present disclosure.
Fig. 5 is a network architecture diagram of some embodiments of the application addressing system of the present disclosure.
Fig. 6 is a schematic diagram of further embodiments of the application addressing system of the present disclosure.
Fig. 7 is a schematic diagram of yet other embodiments of the application addressing system of the present disclosure.
Fig. 8 is a schematic diagram of still other embodiments of the application addressing system of the present disclosure.
Detailed Description
The technical scheme of the present disclosure is described in further detail below through the accompanying drawings and examples.
The inventor discovers that in the related art, with the expansion of an application deployed on the MEC, the network needs to add a recognition rule of local shunting according to the IP address of the application; in order to accurately analyze the IP address of the local application according to the user location, it is necessary to forward the domain name resolution request of the local application to the local DNS and implement the domain name resolution service by the local DNS; 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, in order to ensure correct routing, the IP address fields of each MEC private network cannot be overlapped, which brings challenges to network deployment and routing design, and when the IP address fields are repeated, address conversion needs to be performed on the server address again, so that the implementation is complex.
A flowchart of some embodiments of the application addressing method of the present disclosure is shown in fig. 1.
In step 101, LDNSR determines the application type to which the edge application DNS request from the terminal corresponds. In some embodiments, edge applications may be divided into two classes (hereinafter, class a and class B are referred to as meaning in this paragraph), where class a is an edge application in a traffic flow that will reserve a domain name, and class B is an application in a traffic flow that does not guarantee that the domain name is reserved. The inventors have found that in practical applications, class a applications are the majority.
In step 102, in case the application type is class a, step 103 is performed. In some embodiments, if the application type is class B, it may be performed according to a scheme in the related art.
In step 103, the address of the edge gateway corresponding to the terminal position is fed back.
In some embodiments, LDNSR may query the terminal location information through the SMF, and further determine the edge gateway address of the service area corresponding to the terminal location. In some embodiments LDNSR pre-stores the correspondence of service areas to edge gateway addresses.
In some embodiments, LDNSR establishes an edge user plane according to the determined edge gateway address, determines a splitting rule of an edge UPF accessed by the terminal, and implements splitting of the edge UPF to the edge gateway.
In step 104, the edge gateway (MEC GATEWAY, or mecgw) determines whether an application access request was received. If an application access request is received, step 105 is performed.
In step 105, the edge gateway determines the access address of the application according to the domain name information carried by the application access request. In some embodiments, the correspondence between the domain name and the access address (e.g., IP address, port) in the service area is configured in the edge gateway in advance.
In some embodiments, when the edge UPF receives an application access request from a 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, the terminal and the application server interacting through the edge gateway.
By the method, LDNSR can directly feed back the address of the edge gateway for the application of which the domain name information is reserved for most of the service flows in the network, and the address of a specific application is not required to be queried in the local DNS, so that the processing burden of LDNSR and the local DNS is reduced; for such applications, the shunting recognition rules of the edge UPF connected by the terminal are set to be the addresses of the edge gateway with the matching target address, so that the configuration burden and the execution burden of the edge UPF are reduced; the problem that the IP address segments of the MEC private network overlap when the MECs are deployed in the private network environment and the edge UPF is connected with a plurality of MEC platforms is avoided, the flexibility of edge application expansion in each MEC is improved, and the expansion difficulty is reduced.
A flowchart of further embodiments of the application addressing method of the present disclosure is shown in fig. 2.
In step 201 LDNSR refers to the terminal location information by SMF. In some embodiments LDNSR may be incorporated with the SMF.
In step 202 LDNSR determines the application type to which the edge application DNS request from the terminal corresponds.
In step 203, LDNSR performs step 204 in case it is determined that the application type is an application for which the domain name information is reserved for the traffic flow.
In step 204, LDNSR determines the address of the corresponding edge gateway according to the area where the terminal position is located.
In step 205, LDNSR determines whether an edge splitting policy of the terminal in the corresponding area has been issued. In some embodiments, an edge offload policy is issued if the terminal accesses an edge gateway of the corresponding region (which may be for access to the same or different edge application as the current one). In case it is determined that the edge splitting policy of the terminal in the corresponding area has been issued, step 206 is performed.
In step 206, LDNSR feeds back the address of the edge gateway corresponding to the terminal position.
In step 207, the edge gateway receives an application access request. In some embodiments, the terminal sends an application access request to the edge UPF, which is sent to the edge gateway based on the offloading policy of the edge UPF. Because the user is about to access the class a application, the application access request includes domain name information of the edge application and also includes an 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 by 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 the application server corresponding to the actual address of the application.
Based on the mode that most applications are class A applications, MEC GW is introduced to secondarily distribute class A applications according to domain names, configuration of network distribution rules is simplified, frequent rule update signaling interaction is reduced, meanwhile, the problem that a plurality of private network MEC platforms distinguish routes is solved, and distribution and addressing of edge applications are simplified.
In some embodiments, as shown in fig. 2, in the step 205, if the edge splitting 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 executed.
In step 211, a user plane reselection policy is sent to the SMF requesting that an edge forking user plane path be established, carrying an address of the edge gateway.
In step 212, the SMF performs edge PSA insertion according to the user plane reselection policy and configures a splitting policy of the edge UPF.
In step 213, the edge UPF sets a splitting identification rule according to the splitting policy to match the target address to the IP address of the edge gateway.
By the method, the distribution of the edge UPF to the edge gateway can be realized based on the distribution strategy configuration process of the edge UPF in the related technology by carrying the address of the edge gateway, SMF and UPF improvement are not needed, and popularization and application are facilitated.
In some embodiments, if the application type is determined to be class B (the application that does not retain domain name information in the service flow) in step 203, steps 221 to 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 according to the edge application DNS request, and feeds back to LDNSR.
In step 223, LDNSR triggers the SMF to issue a splitting policy, where the splitting policy carries an access address of an application, and after configuration is completed, the edge UPF splits the traffic flow to an actual access address of the edge application. LDNSR feeding 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 domain name information of the application is not guaranteed to be carried in the access request.
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 solve the problem of the IP address field conflict, the access address of the application provided to the user may be an external address translated according to the actual address of the application. And the access request initiated by the user according to the access address of the application is converted into the 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 allocates LDNSR to the UE as its DNS server and anchors the session at a central UPF.
In 302, the UE accesses an edge application by domain name, first initiates a DNS request via the centers UPF to LDNSR.
At 303 LDNSR, UE location information is consulted by SMF.
In 304, LDNSR determines that the accessed application is a class a application, and queries the corresponding MEC GW address in combination with the corresponding relationship between the preconfigured service area and the MEC GW address.
In 305, if LDNSR determines that the edge splitting policy has not been issued (the UE does not use the edge service in the service area), then a user plane reselection policy is initiated to the SMF, to require that a user plane path for edge splitting be established, and the following 306 is executed; otherwise, the steps 306 and 307 are skipped, and the step 308 is performed.
In 306, the SMF implements edge PSA insertion and configures a splitting policy for edge UPF, where the splitting identification rule is the IP address of the MEC GW.
In 307, the SMF reply LDNSR edge user plane has been established.
In 308, LDNSR replies 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 mecgw via network splitting.
In 310, the MEC GW performs the role of access proxy, querying the internal real IP of the corresponding edge application based on 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 performs service interaction with the edge application to achieve normal access of the application.
By the method, the shunt strategy of only configuring gateway addresses for most edge applications can replace the shunt configuration of all class A applications, and the shunt strategy configuration of the network is simplified; LDNSR directly analyzes the class A local application into a gateway address, and the domain name analysis of the class A application does not need the participation of a local DNS, so that the address analysis configuration is simplified; the deletion of the class A application on the MEC and the change of the application state do not affect the configuration of the network shunt strategy and LDNSR, so that the application change is not perceived; the MEC GW is used as an access gateway, so that the actual address of the class A application is shielded, and the safety of the application is improved; the MEC platform has greatly reduced externally presented addresses, avoids address conflict of multi-MEC platform connection, and the 5G core network only needs to distinguish routes according to MEC GW addresses and a small amount of B-class application IP, thereby simplifying route setting.
A schematic diagram of some embodiments of the application addressing system of the present disclosure is shown in fig. 4.
LDNSR 41 can determine the application type to which the edge application DNS request from the terminal corresponds. In some embodiments, edge applications may be divided into two classes (assumed to be class a, class B), where class a is an application in a traffic flow that will reserve a domain name, and class B is an application in a traffic flow that does not guarantee that the domain name is reserved. And under the condition that the application type is determined to be the application (class A application) of which the domain name information is reserved for the service flow, 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.
In some embodiments, if the application type is class B, it may be performed according to a scheme in the related art.
The edge gateway 42 can determine an access address of the application according to domain name information carried by the application access request and forward the application access request to an actual address of the application when receiving the application access request. In some embodiments, as shown in fig. 4, a UPF 43 may be further included in the application addressing system, and capable of receiving an application access request from a terminal and forwarding the application access request to an edge gateway.
In the application addressing system, LDNSR can directly feed back the address of the edge gateway for the application of which the domain name information is reserved for most of service flows in the network, and the address of a specific application is not required to be queried in the local DNS, so that the processing burden of LDNSR and the local DNS is reduced; for such applications, the shunting recognition rules of the edge UPF connected by the terminal are set to be the addresses of the edge gateway with the matching target address, so that the configuration burden and the execution burden of the edge UPF are reduced; the problem that the IP address segments of the MEC private network overlap when the MECs are deployed in the private network environment and the edge UPF is connected with a plurality of MEC platforms is avoided, the flexibility of edge application expansion in each MEC is improved, and the expansion difficulty is reduced.
In some embodiments LDNSR 41 is also capable of acquiring terminal location information via SMF; judging whether an application type corresponding to the edge application DNS request is an application for reserving domain name information for a service flow; if the application type is determined to be the application of which the service flow reserves 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 terminal is determined to have issued an edge shunting strategy in a corresponding area, feeding back a DNS response carrying an address of an edge gateway to the terminal; and under the condition that the terminal is not issued by the edge shunting strategy of the corresponding area, sending a user plane reselection strategy for requesting to establish the user plane path of the edge shunting to the SMF. As shown in fig. 4, the application addressing system further includes an SMF44, capable of performing terminal location subscription in the 5G core network and feeding back terminal location information to LDNSR f 41; and executing edge PSA insertion according to the user plane reselection strategy, and configuring a diversion strategy of the edge UPF. The edge UPF43 can set the splitting identification rule to match the target address to the IP address of the edge gateway according to the splitting policy.
The system can realize the distribution of the edge UPF to the edge gateway by carrying the address of the edge gateway based on the distribution strategy configuration process of the edge UPF in the related technology, and is favorable for popularization and application without improving the SMF and the UPF.
In some embodiments, LDNSR is further capable of determining a corresponding local DNS according to the terminal location, and forwarding the edge application DNS request to the local DNS in case it is determined that the application type is an application for which the non-traffic flow retains domain name information; triggering the SMF to issue a distribution 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. As shown in fig. 4, the application addressing system further includes a local DNS45, which can determine the actual access address of the application according to the edge application DNS request, and feed back to LDNSR.
The system can realize compatibility of A-type and B-type services and improve reliability of application addressing.
A network architecture diagram of some embodiments of the application addressing system of the present disclosure is shown in fig. 5, mainly involving a 5GC (5G core network) and MEC platform.
In 5GC, UPF is user plane. The 5GC implements and ensures that access to edge traffic is offloaded from the edge UPF.
The MEC platform provides the deployment environment for edge applications and the necessary management means.
The central DNS is a conventional DNS of an operator, and provides a domain name resolution service of the conventional mobile internet.
The MEC GW is deployed on the MEC platform, receives the edge application access request from the 5G network, and implements access distribution of the edge application deployed on the MEC platform, including distribution by domain name and distribution by IP address.
An edge application is an application deployed on the MEC platform.
The SMF implements user plane management.
LDNSR has DNS function applications, providing DNS or DNS proxy functions.
As shown in fig. 5, the MEC platform is internally provided with a MEC GW function as a unified interface gateway device for terminal access edge applications. LDNSR the corresponding relation between the position and the MEC GW address is configured, and the type (A type or B type) corresponding to the edge application is preset. When the terminal initiates a DNS request, LDNSR first determines the application type, and performs domain name resolution (as indicated by the dashed arrow in the figure) on the class B application according to a known method.
The process shown by the arrow in the figure is implemented for the domain name resolution request of the class a application. LDNSR replies corresponding MEC GW addresses (MEC platform and MEC GW are in one-to-one relationship) in a unified way according to the terminal position. When the terminal accesses the class A edge application on the same MEC, the terminal initiates a request to the MEC GW, so that the edge UPF only needs to configure a 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 class A application. The MEC GW is used as an access agent, and for the A-class application, addressing of the access request is carried out according to domain name information in the access request, and the addressing is forwarded to an actual IP corresponding to the internal application; and distributing the B-class application according to the IP address, thereby realizing that the terminal accesses the application service requested by the terminal.
Taking the domain name and application access procedure shown in fig. 6 as an example, a MEC GW is introduced on the MEC platform as an access proxy.
When the UE needs to access the application, a DNS request is first initiated, where the destination address of the DNS request is LDNSR (SMF is allocated to the UE when the terminal is registered). LDNSR interacts with SMF to obtain terminal position information; and forwarding the B-class application to a local DNS according to a known scheme to perform domain name resolution, and returning the same address for the A-class application (such as application 1 and application 2 in the figure) which are the IP addresses of the MEC GWs in the edge area.
LDNSR, triggering the SMF (combined with LDNSR or interacted with through signaling) to implement a local shunting strategy according to the IP address of the analysis result, wherein for the class A application, only the shunting strategy matched with the IP address of the MEC GW needs to be configured.
And when the terminal accesses different applications of the A class, the terminal initiates a request to the MEC GW. The service request of the terminal is split locally, via the edge UPF to the MEC GW. For the A-class application, the MEC GW carries out secondary distribution on the access request according to the domain name information in the request, and converts the accessed target address into an internal actual IP address corresponding to the application.
In addition, the B-class application is directly routed according to the IP address, so that the addressing of the edge computing application is realized.
The service addressing system ensures that the distribution strategy of only configuring gateway addresses for most edge applications can replace the distribution configuration of all class A applications, thereby simplifying the distribution strategy configuration of the network; LDNSR directly analyzes the class A local application into a gateway address, and the domain name analysis of the class A application does not need the participation of a local DNS, so that the address analysis configuration is simplified; the deletion of the class A application on the MEC and the change of the application state do not affect the configuration of the network shunt strategy and LDNSR, so that the application change is not perceived; the MEC GW is used as an access gateway, so that the actual address of the class A application is shielded, and the safety of the application is improved; the MEC platform has greatly reduced externally presented addresses, avoids address conflict of multi-MEC platform connection, only needs to distinguish routes according to MEC GW addresses and a small amount of B-type application IP, and simplifies route setting.
A schematic structural diagram of one embodiment of the disclosed business addressing system is shown in fig. 7. The traffic addressing system comprises a memory 701 and a processor 702. Wherein: memory 701 may be a magnetic disk, flash memory, or any other non-volatile storage medium. The memory is used to store 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 instructions stored in the memory, so that processing burden of LDNSR and processing burden of the local DNS can be reduced, configuration burden and execution burden of the edge UPF can be reduced, and expansion difficulty can be reduced.
In one embodiment, as also shown in FIG. 8, the business 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 connected to external storage 805 via a storage interface 804 for invoking external data, and may also be connected to a network or another computer system (not shown) via a network interface 806. And will not be described in detail herein.
In this embodiment, the data instruction is stored in the memory, and then the processor processes the instruction, so that the processing burden of LDNSR and the local DNS can be reduced, the configuration burden and the execution burden of the edge UPF can be reduced, and the expansion difficulty can be 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 embodiments of the business addressing method. It will be apparent to those skilled in the art that 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, etc.) 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 flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations 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. In order to avoid obscuring the concepts of the present disclosure, some details known in the art are not described. How to implement the solutions disclosed herein will be fully apparent to those skilled in the art from the above description.
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, firmware. The above-described sequence of steps for the method is for illustration only, and the steps of the method of the present disclosure are not limited to the sequence specifically described above unless specifically stated otherwise. Furthermore, in some embodiments, the present disclosure may also be implemented 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 embodiments are merely for illustrating the technical solution of the present disclosure and are not limiting thereof; although the present disclosure has been described in detail with reference to preferred embodiments, those of ordinary skill in the art will appreciate that: modifications may be made to the specific embodiments of the disclosure or equivalents may be substituted for part of the technical features; without departing from the spirit of the technical solutions of the present disclosure, it should be covered in the scope of the technical solutions claimed in the present disclosure.

Claims (13)

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;
And feeding back an address of an edge gateway corresponding to the terminal position under the condition that the application type is determined to be the edge application of which the service flow reserves domain name information, wherein the method comprises the following steps:
The LDNSR acquires terminal position information;
the LDNSR judges whether the application type corresponding to the edge application DNS request is an application of reserving domain name information for the service flow;
if the application type is determined to be the edge application of which the service flow reserves domain name information, determining the address of the corresponding edge gateway according to the area where the terminal position is located;
the LDNSR feeds back a DNS response carrying the address of the edge gateway to the terminal under the condition that the terminal is determined to have issued an edge shunting strategy in a corresponding area, so that the terminal sends an application access request to the edge gateway;
The edge gateway determines 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;
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 of claim 1, the LDNSR obtaining terminal location information comprises:
the LDNSR refers to the terminal location information through the session management function SMF.
5. The method according to claim 4, wherein in the case of determining that the application type is an edge application in which domain name information is reserved for a service flow, feeding back an address of an edge gateway corresponding to a terminal position further includes:
The LDNSR sends a user plane reselection strategy for requesting to establish a user plane path of edge splitting to the SMF under the condition that the edge splitting strategy of the terminal in the corresponding area is not issued;
the SMF executes the PSA insertion of the session anchor point of the edge protocol data unit according to the user plane reselection strategy and configures the diversion strategy of the edge UPF;
And the edge UPF sets a shunting identification rule as a matching target address according to the shunting strategy to be the IP address of the edge gateway.
6. The method of claim 1, further comprising:
if the LDNSR determines that the application type is an application of which the non-service flow reserves domain name information, determining a corresponding local DNS according to the terminal position, and forwarding the edge application DNS request to the local DNS;
The local DNS determines an access address of an application according to the edge application DNS request and feeds back the access address to the LDNSR;
And LDNSR triggering the SMF to issue a distribution strategy according to the access address of the application, 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.
7. The method of claim 1, further comprising:
Under the condition that the SMF receives an initial session establishment request of the terminal, LDNSR corresponding to the terminal position is set as a DNS server side of the terminal, and the session of the terminal is anchored in a central UPF.
8. An application addressing system, comprising:
A local domain name system resolver LDNSR configured to determine an application type corresponding to an edge application domain name system DNS request from the terminal; and feeding back an address of an edge gateway corresponding to the terminal position under the condition that the application type is determined to be the edge application of which the service flow reserves domain name information, wherein the method comprises the following steps: acquiring terminal position information; judging whether the application type corresponding to the edge application DNS request is an application for reserving domain name information for a service flow; if the application type is determined to be the edge application of which the service flow reserves 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 terminal is determined to have issued an edge shunting strategy in a corresponding area, feeding 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;
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; and forwarding the application access request to the actual address of the application.
9. The system of claim 8, further comprising:
an edge user plane function UPF configured to receive said application access request from a terminal and forward to said edge gateway.
10. The system of claim 8, wherein,
Said LDNSR is configured to consult terminal location information via session management function SMF; is also configured to: under the condition that the terminal is not issued in the edge shunting strategy of the corresponding area, sending a user plane reselection strategy of a user plane path for requesting to establish edge shunting to the SMF;
Further comprises:
The SMF is configured to feed back terminal location information to the LDNSR; executing the PSA insertion of the edge protocol data unit session anchor point according to the user plane reselection strategy, and configuring the diversion strategy of the edge UPF;
The edge UPF is configured to set a splitting identification rule as an IP address of the edge gateway as a matching target address according to the splitting strategy.
11. The system of claim 8, wherein,
The LDNSR is further configured to determine a corresponding local DNS according to the terminal location, and forward the edge application DNS request to the local DNS, in the case that the application type is determined to be an edge application for which non-traffic flows retain domain name information; triggering SMF to issue a shunt 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 a user terminal so that the terminal sends an application access request according to the access address of the application;
Further comprises:
The local DNS is configured to determine an access address of an application according to the edge application DNS request, and feed back 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 of claims 1 to 7.
CN202011302294.5A 2020-11-19 2020-11-19 Application addressing method, system and storage medium Active CN114598676B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202011302294.5A CN114598676B (en) 2020-11-19 2020-11-19 Application addressing method, system and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202011302294.5A CN114598676B (en) 2020-11-19 2020-11-19 Application addressing method, system and storage medium

Publications (2)

Publication Number Publication Date
CN114598676A CN114598676A (en) 2022-06-07
CN114598676B true CN114598676B (en) 2024-11-22

Family

ID=81802737

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202011302294.5A Active CN114598676B (en) 2020-11-19 2020-11-19 Application addressing method, system and storage medium

Country Status (1)

Country Link
CN (1) CN114598676B (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115426685A (en) * 2022-08-31 2022-12-02 中国联合网络通信集团有限公司 Access control method, device, equipment and medium for 5G edge computing traffic
CN115297509B (en) * 2022-10-09 2023-01-10 中国移动通信有限公司研究院 A method and system for secondary splitting of edge computing

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108259237A (en) * 2018-01-05 2018-07-06 葛晗 Network access accelerated method, cloud dns server, CE and cloud IP accelerate network system
CN110198307A (en) * 2019-05-10 2019-09-03 深圳市腾讯计算机系统有限公司 A kind of selection method of mobile edge calculations node, apparatus and system

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110896553B (en) * 2018-09-12 2022-11-11 中国电信股份有限公司 Multi-access edge computing method and platform and communication system
US10708716B2 (en) * 2018-10-16 2020-07-07 Cisco Technology, Inc. Methods and apparatus for selecting network resources for UE sessions based on locations of multi-access edge computing (MEC) resources and applications
CN111385369B (en) * 2018-12-28 2021-06-22 华为技术有限公司 Domain name server distribution method and device
CN110198363B (en) * 2019-05-10 2021-05-18 深圳市腾讯计算机系统有限公司 Method, device and system for selecting mobile edge computing node

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108259237A (en) * 2018-01-05 2018-07-06 葛晗 Network access accelerated method, cloud dns server, CE and cloud IP accelerate network system
CN110198307A (en) * 2019-05-10 2019-09-03 深圳市腾讯计算机系统有限公司 A kind of selection method of mobile edge calculations node, apparatus and system

Also Published As

Publication number Publication date
CN114598676A (en) 2022-06-07

Similar Documents

Publication Publication Date Title
US12149584B2 (en) Application relocation method and apparatus
US12120029B2 (en) Method for implementing service continuity and related device
KR102838527B1 (en) Method and apparatus for managing an identifier of a terminal in edge computing service
CN114902634A (en) Apparatus and method for providing information of application server in mobile communication system
US11863519B2 (en) Communication method and apparatus for handling DNS messages
JP2012161078A (en) Method and apparatus for determining server which should respond to service request
US12513109B2 (en) IPV6 address configuration method and routing device
CN105101176A (en) Session binding method, device and system in roaming scene
CN115988482B (en) NF (network Address) accurate addressing method and device for co-construction sharing heterogeneous network roaming scene
US9825951B2 (en) Method and system for distributing service data
CN114598676B (en) Application addressing method, system and storage medium
JP2018152691A (en) Control apparatus
CN116647834B (en) Mobile network communication method and system for low-delay and high-reliability service
CN116528151B (en) 5G dual-domain private network implementation method, system and device and electronic equipment
CN114385314A (en) Internet of things equipment data migration system, method and device and storage medium
US11729142B1 (en) System and method for on-demand edge platform computing
CN117015075A (en) Remote user equipment access methods, devices, equipment, media and program products
CN115412590A (en) Application discovery method, device, system and computer storage medium
CN117692889A (en) End-to-end service processing method, device, equipment and storage medium
CN116709199A (en) A DNS redirection method, device and readable storage medium
CN118828471B (en) Method and device for reducing telephone traffic detour of IMS call in private communication
KR102956072B1 (en) Service function chaining system and method for mobile network
CN119182754B (en) A roaming communication method under a home routing architecture, and related network elements, storage media, and computer program products.
CN114222341B (en) Session connection method and session management functional entity
KR101805811B1 (en) System and method for simultaneously transmitting data in heterogeneous network

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant