CN114143287A

CN114143287A - Domain name server processing method and device

Info

Publication number: CN114143287A
Application number: CN202010814130.4A
Authority: CN
Inventors: 刘棠青; 王丹
Original assignee: China Mobile Communications Group Co Ltd; China Mobile Communications Ltd Research Institute
Current assignee: China Mobile Communications Group Co Ltd; China Mobile Communications Ltd Research Institute
Priority date: 2020-08-13
Filing date: 2020-08-13
Publication date: 2022-03-04

Abstract

The embodiment of the application provides a domain name server processing method and a domain name server processing device, wherein the method comprises the following steps: acquiring a DNS request forwarded by UPF; selecting a DNS server and/or UPF; forwarding the DNS request to the selected DNS server and/or UPF. In the embodiment of the application, the function of the existing network element is directly enhanced, so that no network element needs to be added, and no new interface design management problem caused by the new network element exists, and the whole mechanism is completed by the network element of an operator without depending on a third party.

Description

Domain name server processing method and device

Technical Field

The embodiment of the application relates to the technical field of communication, in particular to a domain name server processing method and device.

Background

Application program (app) addressing of a core network of a fifth generation mobile communication technology (5th generation, 5G) is to pre-configure an address of a Domain Name Server (DNS) resolution Server to a terminal, and the terminal accesses to acquire the app address according to the configured DNS resolution Server address. In the edge network, in order to ensure the service quality, part of apps needs to find an application server closest to the terminal for the terminal.

At present, various DNS processing schemes are proposed, which are roughly divided into three schemes, wherein the first scheme needs to add a new network element to solve the problem, the second scheme needs to greatly modify the existing network element although the new network element is not needed, and the third scheme needs to rely on a third party to position a proper application server.

Disclosure of Invention

An object of the embodiments of the present application is to provide a method and an apparatus for processing a domain name server, so as to solve a problem how to perform domain name server processing in a 5G network by using an existing network element.

In a first aspect, a DNS processing method applied to SMF is provided, including:

acquiring a DNS request forwarded by a user plane function UPF;

selecting a DNS server and/or UPF;

forwarding the DNS request to the selected DNS server and/or UPF.

Optionally, the selecting a DNS server and/or a UPF includes:

and selecting the DNS server and/or the UPF according to the policy information acquired from the PCF.

Optionally, the method further comprises:

triggering an uplink classifier insertion procedure or a UPF handover procedure.

Optionally, the forwarding the DNS request to the UPF includes:

and replacing the destination address in the DNS request with the address of the DNS server selected by the SMF, and forwarding the DNS request to the UPF.

Optionally, the method further comprises:

and sending the address of the DNS server to the UPF.

Optionally, the method further comprises:

sending first information of UPF node granularity to the UPF through an N4 session establishment flow;

the first information includes: fully qualified domain name FQDN, terminal position information and DNS server address;

and the SMF maintains second information in a range, wherein the second information comprises FQDN, terminal position information and DNS server address.

In a second aspect, a DNS processing method is provided, which is applied to UPF, and includes:

acquiring a DNS request;

and inserting ECS information of the client terminal mask of the extended public domain name system into the DNS request, and forwarding the DNS request to a DNS server.

Optionally, the method further comprises:

the ECS information includes DNAI information or terminal location information.

Optionally, the method further comprises:

the DNS request is identified by applying information detection or identifying port information such as FQDN.

Optionally, the method further comprises:

and obtaining the DNAI information from the SMF.

Optionally, the method further comprises:

and acquiring the terminal position information from the SMF, or acquiring the terminal position information from the local.

Optionally, the method further comprises:

and replacing the destination address in the DNS request with the address of the DNS server selected by the UPF, and replacing the source address of the response message of the DNS request with the initial DNS server address.

Optionally, the method further comprises:

through an N4 session establishment procedure, obtaining first information of UPF node granularity sent by an SMF, where the first information includes: FQDN, terminal position information and DNS server address;

Optionally, the DNS server address is provided from a third party by an application function influence (AF notify) flow.

In a fourth aspect, a DNS processing apparatus applied to SMF is provided, including:

the first acquisition module is used for acquiring a DNS request forwarded by the UPF;

a selection module for selecting a DNS server and/or UPF;

and the first sending module is used for forwarding the DNS request to the selected DNS server and/or UPF.

In a fifth aspect, there is provided an SMF, comprising: a processor, a memory and a program stored on the memory and executable on the processor, which program, when executed by the processor, carries out the steps of the DNS processing method according to the first aspect.

In a sixth aspect, a DNS processing apparatus applied to UPF is provided, including:

the second acquisition module is used for acquiring the DNS request;

and the second sending module is used for inserting the DNS request into the ECS information and forwarding the DNS request to the DNS server.

In a seventh aspect, a UPF is provided, including: a processor, a memory and a program stored on the memory and executable on the processor, which when executed by the processor, performs the steps of the DNS processing method according to the second aspect.

In an eighth aspect, there is provided a readable storage medium having stored thereon a computer program which, when executed by a processor, performs steps comprising a method according to the first or second aspect.

In the embodiment of the application, the existing network elements are directly and simply enhanced in function, so that no network element needs to be added, no new interface design management problem caused by the new network element is caused, and the whole mechanism is finished by the network element of an operator without depending on a third party.

Drawings

Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the application. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:

fig. 1 is a flowchart of a domain name server processing method according to an embodiment of the present application;

fig. 2 is a second flowchart of a domain name server processing method according to an embodiment of the present application;

FIG. 3 is a flowchart of a first embodiment;

FIG. 4 is a flowchart of the second embodiment;

FIG. 5 is a flowchart according to a fourth embodiment;

FIG. 6 is a flowchart of the fifth embodiment;

FIG. 7 is a flowchart of a sixth embodiment;

fig. 8 is a schematic diagram of a domain name server processing apparatus according to an embodiment of the present application;

FIG. 9 is a schematic diagram of an SMF of an embodiment of the present application;

fig. 10 is a second schematic diagram of a domain name server processing apparatus according to an embodiment of the present application;

FIG. 11 is a schematic representation of a UPF according to an embodiment of the present application;

FIG. 12 is a flowchart of a sixth embodiment.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, embodiments of the present application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

The terms "comprises," "comprising," or any other variation thereof, in the description and claims of this application, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus. Furthermore, the use of "and/or" in the specification and claims means that at least one of the connected objects, such as a and/or B, means that three cases, a alone, B alone, and both a and B, exist.

In the embodiments of the present application, words such as "exemplary" or "for example" are used to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" or "e.g.," is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word "exemplary" or "such as" is intended to present concepts related in a concrete fashion.

The terms "system" and "network" are often used interchangeably. CDMA systems may implement Radio technologies such as CDMA2000, Universal Terrestrial Radio Access (UTRA), and so on. UTRA includes Wideband CDMA (Wideband Code Division Multiple Access, WCDMA) and other CDMA variants. TDMA systems may implement radio technologies such as Global System for Mobile communications (GSM). The OFDMA system can implement radio technologies such as Ultra Mobile Broadband (UMB), evolved-UTRA (E-UTRA)), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX)), IEEE 802.20, Flash-OFDM, and the like. UTRA and E-UTRA are parts of the Universal Mobile Telecommunications System (UMTS). LTE and higher LTE (e.g., LTE-A) are new UMTS releases that use E-UTRA. UTRA, E-UTRA, UMTS, LTE-A, and GSM are described in documents from an organization named "third Generation Partnership Project" (3 GPP). CDMA2000 and UMB are described in documents from an organization named "third generation partnership project 2" (3GPP 2). The techniques described herein may be used for both the above-mentioned systems and radio technologies, as well as for other systems and radio technologies.

Referring to fig. 1, an execution subject of the method may be a Session Management Function (SMF), and the specific steps include: step 101-step 103.

Step 101: acquiring a DNS request forwarded by a user plane function UPF;

step 102: selecting a DNS server and/or UPF;

for example, the DNS server and/or UPF may be selected based on policy information obtained from the PCF.

Optionally, policy information (alternatively referred to as a policy table) is maintained and updated by the PCF and stored in the PCF and SMF.

The policy information includes: a mapping relationship between a Fully Qualified Domain Name (FQDN), a Data Network Access Identifier (DNAI), and a DNS server address (DNS server address), such that the SMF can select an appropriate DNS server address and DNAI based on the UE location and the FQDN requested by the user.

The FQDN, the APP server address and the DNS server address are provided by the AF, the PCF maps DNAI, the FQDN and the DNS server address into a table of per UE based on the subscription information of the UE, and the table is provided for the SMF.

Step 103: forwarding the DNS request to the selected DNS server and/or UPF.

For example, the destination address in the DNS request is replaced with the address of the DNS server selected by the SMF, and the DNS request is forwarded to the UPF.

In this embodiment of the present application, optionally, the method further includes: triggering ULCL inserting flow or UPF switching flow.

In this embodiment of the present application, optionally, the method further includes: and sending the address of the selected DNS server to the UPF.

In this embodiment of the present application, optionally, the method further includes: sending first information of UPF node granularity to the UPF through an N4 session establishment procedure, wherein the first information comprises: FQDN, terminal position information and DNS server address;

In the embodiment of the application, the SMF enhances the existing function of supporting DNS to process DNS requests, and selects a proper Local DNS server and/or PSA for the UE DNS request based on a locally stored PCF policy table. If a new PSA is selected, a PSA switch/ULCL insert flow is performed, the SMF modifies the DNS request destination address, and sends the DNS request to the L-DNS through the user plane tunnel. If the PSA is not changed, the DNS request is sent to the C-DNS for resolution directly through the user plane of the original PSA.

In the embodiment of the application, the existing network elements are directly and simply enhanced in function, so that no network element needs to be added, no new interface design management problem caused by the new network element is caused, and the whole mechanism is completed by the network element of an operator, so that the third party does not need to be relied on.

Referring to fig. 2, an embodiment of the present application provides a DNS processing method, where an execution main body of the method may be a UPF, and the method includes the specific steps of:

step 201: acquiring a DNS request;

the DNS request is identified, for example, by DPI inspection or identifying port information.

Step 202: inserting the DNS request into extended public domain name system client-subnet (ECS) information, and forwarding the DNS request to a DNS server.

In this embodiment of the application, optionally, the ECS information includes the DNAI information or terminal location information.

In this embodiment of the present application, optionally, the method further includes: and obtaining the DNAI information from the SMF.

In this embodiment of the present application, optionally, the method further includes: and acquiring the terminal position information from the SMF, or acquiring the terminal position information from the local.

In this embodiment of the present application, optionally, the method further includes: and replacing the destination address in the DNS request with the address of the DNS server selected by the UPF, and replacing the source address of the response message of the DNS request with the initial DNS server address.

In this embodiment of the present application, optionally, the method further includes: through an N4 session establishment procedure, obtaining first information of UPF node granularity sent by an SMF, where the first information includes: FQDN, terminal position information and DNS server address;

Examples of the present application will be described below with reference to examples 1 to 7.

Example 1: SMF enhancements handle Domain Name Server (DNS) requests in the case of Uplink Classifier (ULCL) plug-in/distributed Platform Security Architecture (PSA) handover. .

Referring to fig. 3, the specific process is as follows:

step 1: the UE sends a DNS request to PSA 1.

Step 2: PSA1 detects a DNS request and forwards the DNS request to the SMF.

And step 3: the SMF queries the policy table obtained from the PCF and selects the most appropriate DNAI and/or PSA based on the UE location and the requested FQDN.

If the UE supports the ULCL, performing a ULCL insertion procedure; if not, a PSA switch procedure is performed.

In the ULCL insertion or PSA switching flow, the SMF sends the DNS server address table of the UPF node granularity to the UPF through N4 session establishment (session initialization).

And 4, step 4: the destination address in the DNS request is replaced with the address of the DNS server selected by the SMF and forwarded to the Local (Local) PSA/PSA 2.

And 5: local PSA/PSA2 sends DNS requests to a Local DNS server (L-DNS server).

Step 6: the Local DNS server searches a proper application program server (APP server) according to the FQDN, the resolution result is sent to Local PSA/PSA2, the Local PSA/PSA2 replaces the source address with a core DNS server (C-DNS server) address according to a DNS server address table acquired from the SMF when the ULCL is inserted or PSA is switched, and the source address is sent to the UE.

And 7: the UE performs data interworking with the EAS.

Example 2: the SMF enhancements handle DNS requests without switching PSAs.

Referring to fig. 4, the specific process is as follows:

step 1: the UE sends a DNS request to the UPF.

Step 2: the UPF detects that it is a DNS request and forwards the DNS request to the SMF.

According to the UE strategy, the SMF discovers that the UE does not support the ULCL. The policy table retrieved from the PCF is queried and the most appropriate DNAI and PSA are selected based on the requested FQDN.

And step 3: the SMF query results do not require switching of the PSA, and the DNS request is forwarded to the UPF.

And 4, step 4: the UPF sends DNS requests to a core DNS (C-DNS) server.

And 5: and the C-DNS server sends the DNS resolution result to the UPF, and the UPF forwards the DNS resolution result to the UE.

Step 6: the UE performs data interworking with the EAS.

Example 3: the PCF generates a corresponding DNS resolution policy according to information provided by an Application Function (AF).

The specific process is as follows:

step 1: the AF sends the information about the association of the FQDN, the address of the application server (app server address), and the address of the DNS server (such as the IP address of the DNS server) to the PCF through an application function influence (AF notify) flow.

Step 2: based on the subscription information of the UE, the PCF app server address maps the DNAI and FQDN, and the DNS server address (e.g. DNS server IP address) to a policy table for each (per) UE, and provides the policy table to the SMF.

And step 3: the policy table is maintained and updated by PCF, and is stored in PCF and SMF

See table 1 for one form of policy table.

Table 1:

FQDN	DNAI	DNS
			FQDN1	DNAI1	DNS server ip address1
FQDN1	DNAI2	DNS server ip address2
			FQDN1	DNAI3	DNS server ip address3
FQDN2	DNAI1	DNS server ip address1
			FQDN2	DNAI2	DNS server ip address4
FQDN2	DNAI5	DNS server ip address5
			……	……	……
FQDN n	DNAI	1				DNS server ip address1
			FQDN n	DNAI n	DNS server ip address n

example 4: under the condition of distributed UPF deployment, the UPF enhances the processing of DNS requests.

Referring to fig. 5, the specific process is as follows:

step 1: the UE sends a DNS request to the UPF.

Step 2: the UPF requests the SMF for corresponding DNAI information.

And step 3: the SMF returns DNAI information.

And 4, step 4: the UPF detects a DNS request (as NAT) and populates the DNAI with (EDNS-Client-Subnet, ECS).

And 5: the UPF sends the DNS request to the DNS server.

Step 6: the DNS server selects EAS with proper position based on DNAI in the ECS, returns the result to the UPF, and the UPF (as NAT) returns the analysis result to the UE.

And 7: the UE performs data interworking with the EAS.

Example 5: UpF enhanced handling of DNS requests in ULCL cases

Referring to fig. 6, the specific process is as follows:

step 0: and in the ULCL inserting process, configuring a shunting strategy of DNS request for all local unloading.

Step 1: the UE sends a DNS request to the ULCL.

Step 2: the UPF (local PSA) requests corresponding DNAI information from the SMF.

And step 3: the SMF returns DNAI information.

And 4, step 4: ULCL detects that it is a DNS request, forwards it to Local PSA (acting as NAT), and populates the ECS with DNAI.

And 5: the Local PSA sends a DNS resolution to the DNS server.

Step 6: the DNS server selects EAS with proper position based on DNAI in the ECS, and returns the result to Local PSA (acting as NAT), and the Local PSA returns the resolved result to the UE.

And 7: the UE performs data interworking with the EAS.

Example 6:

for the "pre-established" ULCL/L-PSA scenario, the SMF performs ULCL/L-PSA selection and insertion based on UE location and sets uplink filtering rules on the ULCL. The local DNS address is provided to the UE by the ePCO in the PDU session modification command, as needed.

Referring to fig. 7, the specific steps are as follows:

step 0: during PDU session establishment, the UPF obtains from the SMF the FQDN and UE location information for the DNS server IP address associated with each UPF.

Step 1: the UE sends a DNS request containing the requested FQDN.

Step 2: the UPF extracts the FQDN from the DNS request. If the application server has subscribed to the Edge application server discovery service, the UPF will trigger EAS discovery.

And step 3: the UPF retrieves the UE location information and DNAI from the SMF.

And 4, step 4: the UPF selects a DNS server based on the UE location information and the FQDN based on the information obtained from the SMF in step 0.

Step 5a-6 a: the UPF modifies the target IP address of the DNS query to the target DNS server IP address and forwards it to the target DNS server. The DNS server returns a DNS response including the EAS IP address. The UPF modifies the source IP address to a C-DNS server and forwards the response to the UE.

Step 5b-6 b: if the UPF cannot find the DNS server in step 4, the UPF adds the UE location information and/or DNAI in the DNS request for DNS client subnet option and sends it to the C-DNS. The C-DNS returns a DNS response including the EAS IP address.

And 7: the UPF extracts the EAS IP address and notifies the SMF of the EAS IP address in a DNS response. SMF determines whether to trigger ULCL/BP insertion or PSA replacement based on UE location and EAS IP address

And 8: the operator selects one of the following options for the DNS request according to the deployment requirements:

option 1, the DNS request is directed to the local PSA. In the ULCL insertion procedure, the local DNS server IP address is provided to the UE by the ePCO. Or may be modified by the local UPF.

Option 2, the DNS request may be directed to the local PSA according to the FQDN in the ULCL rule. The local DNS server IP address may be provided to the UE by the ePCO during the ULCL insertion process. Modifications may also be made by local UPF.

This option may increase network consumption and is applicable in cases where the L-DNS does not have a direct connection with the C-DNS.

Option 3, DNS requests are routed to the central PSA, which is the existing mechanism in R15.

Example 6:

if the third party does not provide the DNS server IP address, then discovery of the EAS is as shown in FIG. 12. The AF provides EAS deployment information to the UDR through an application function influence (AF influence) flow. This includes the DNS server IP address associated with the UE location. During PDU session establishment, the SMF obtains information from the PCF (PCC rule). In the PDU session setup procedure, the address of the DNS server is provided by the SMF to the UE through the PCO.

After PDU session establishment, the SMF will trigger the ULCL/BP insertion procedure depending on the UE's location and subscription. The ULCL rule is provided by the SMF based on the location of the UE relative to the DNS server address.

Referring to fig. 12, the specific steps are as follows:

step 1: the UE sends a DNS request containing the requested FQDN.

Step 2: the DNS request may be identified by a destination IP address (DoH, DoT) or port number (DoT) and forwarded by UPF to C-DNS or L-DNS according to the ULCL rules. And the source IP address of the firewall after passing through the NAT indicates the position of the UE.

And step 3: the DNS server returns a DNS response to the UE.

Referring to fig. 8, an embodiment of the present application provides a DNS processing apparatus, which is applied to SMF, where the apparatus 800 includes:

a first obtaining module 801, configured to obtain a DNS request forwarded by a UPF;

a selection module 802 for selecting a DNS server and/or UPF;

a first sending module 803, configured to forward the DNS request to the selected DNS server and/or UPF.

In this embodiment of the application, the selecting module 802 is further configured to: and selecting the DNS server and/or the UPF according to the policy information acquired from the PCF.

In an embodiment of the present application, the apparatus 800 further includes: and the triggering module is used for triggering the ULCL inserting flow or the UPF switching flow.

In this embodiment of the present application, the first sending module 803 is further configured to: and replacing the destination address of the DNS request with an address corresponding to DNAI, and forwarding the DNS request to the UPF.

In this embodiment of the present application, the first sending module 803 is further configured to: and sending the address of the selected DNS server to the UPF.

In this embodiment of the present application, the first sending module 803 is further configured to: sending first information of UPF node granularity to the UPF through an N4 session establishment flow;

The DNS processing apparatus provided in the embodiment of the present invention may execute the method embodiment shown in fig. 1, and the implementation principle and the technical effect are similar, which are not described herein again.

Referring to fig. 9, fig. 9 is a structural diagram of an SMF applied in an embodiment of the present invention, and as shown in fig. 9, a UPF800 includes: a processor 901, a transceiver 902, a memory 903, and a bus interface, wherein:

in one embodiment of the present invention, the UPF900 further comprises: a program stored on the memory 903 and executable on the processor 901, which when executed by the processor 901 performs the steps in the embodiment shown in fig. 1.

In fig. 9, the bus architecture may include any number of interconnected buses and bridges, with one or more processors represented by processor 901 and various circuits of memory represented by memory 903 being linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 902 may be a number of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium, it being understood that the transceiver 902 is an optional component.

The processor 901 is responsible for managing a bus architecture and general processing, and the memory 903 may store data used by the processor 901 in performing operations.

The SMF provided in the embodiment of the present invention may implement the method embodiment shown in fig. 1, which has similar implementation principles and technical effects, and this embodiment is not described herein again.

Referring to fig. 10, an embodiment of the present application provides a DNS processing apparatus, which is applied to UPF, where the apparatus 1000 includes:

a second obtaining module 1001, configured to obtain a DNS request;

the second sending module 1002 is configured to forward the DNS request carrying the DNAI information or the terminal location information to a DNS server.

In the embodiment of the present application, the apparatus 1000 further includes: an inserting module, configured to insert extended public domain name system Client-side mask (EDNS-Client-Subnet, ECS) information into the obtained DNS request, where the ECS information includes the DNAI information or the terminal location information.

In this embodiment of the application, the second obtaining module 1001 is further configured to: the DNS request is identified by DPI inspection or identification of port information.

In this embodiment of the application, the second obtaining module 1001 is further configured to: and obtaining the DNAI information from the SMF.

In this embodiment of the application, the second obtaining module 1001 is further configured to: and acquiring the terminal position information from the SMF, or acquiring the terminal position information from the local.

In the embodiment of the present application, the apparatus 1000 further includes:

a third obtaining module, configured to obtain an address of the DNS server selected by the SMF;

a replacing module, configured to replace a destination address in the DNS request with an address of the DNS server selected by the SMF, and replace a source address of a response message of the DNS request with an initial DNS server address.

a fourth obtaining module, configured to obtain, through an N4 session establishment procedure, first information of a UPF node granularity sent by an SMF, where the first information includes: fully qualified domain name FQDN, terminal position information and DNS server address;

In the embodiment of the present application, the DNS server address is provided from a third party by an application function influence (AF influx) process.

The DNS processing apparatus provided in the embodiment of the present invention may execute the method embodiment shown in fig. 2, and the implementation principle and the technical effect are similar, which are not described herein again.

Referring to fig. 11, fig. 11 is a structural diagram of a UPF applied in an embodiment of the present invention, and as shown in fig. 11, a UPF1100 includes: a processor 1101, a transceiver 1102, a memory 1103, and a bus interface, wherein:

in one embodiment of the present invention, the UPF1100 further comprises: a program stored on the memory 1103 and executable on the processor 1101, the program, when executed by the processor 1101, implementing the steps in the embodiment shown in fig. 2.

In fig. 11, the bus architecture may include any number of interconnected buses and bridges, with one or more processors, represented by processor 1101, and various circuits, represented by memory 1103, linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 1102 may be a plurality of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium, it being understood that the transceiver 1102 is an optional component.

The processor 1101 is responsible for managing the bus architecture and general processing, and the memory 1103 may store data used by the processor 1101 in performing operations.

The UPF provided by the embodiment of the present invention may implement the method embodiment shown in fig. 2, and the implementation principle and the technical effect are similar, which are not described herein again.

The steps of a method or algorithm described in connection with the disclosure herein may be embodied in hardware or may be embodied in software instructions executed by a processor. The software instructions may consist of corresponding software modules that may be stored in RAM, flash memory, ROM, EPROM, EEPROM, registers, hard disk, a removable hard disk, a compact disk, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. Of course, the storage medium may also be integral to the processor. The processor and the storage medium may reside in an ASIC. In addition, the ASIC may be carried in a core network interface device. Of course, the processor and the storage medium may reside as discrete components in a core network interface device.

Those skilled in the art will recognize that in one or more of the examples described above, the functions described herein may be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer.

The above-mentioned embodiments, objects, technical solutions and advantages of the present application are further described in detail, it should be understood that the above-mentioned embodiments are only examples of the present application, and are not intended to limit the scope of the present application, and any modifications, equivalent substitutions, improvements and the like made on the basis of the technical solutions of the present application should be included in the scope of the present application.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, embodiments of the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

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

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

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

It will be apparent to those skilled in the art that various changes and modifications may be made in the embodiments of the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the embodiments of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to encompass such modifications and variations.

Claims

1. A domain name server DNS processing method is applied to a Session Management Function (SMF), and is characterized by comprising the following steps:

acquiring a DNS request forwarded by a user plane function UPF;

selecting a DNS server and/or UPF;

forwarding the DNS request to the selected DNS server and/or UPF.

2. The method of claim 1, wherein selecting the DNS server and/or the UPF comprises:

3. The method of claim 1, further comprising:

4. The method of claim 1, wherein forwarding the DNS request to the UPF comprises:

5. The method of claim 1, further comprising:

and sending the address of the DNS server to the UPF.

6. The method of claim 1, further comprising:

7. A DNS processing method is applied to UPF and is characterized by comprising the following steps:

acquiring a DNS request;

8. The method of claim 7, further comprising:

the ECS information includes DNAI information or terminal location information.

9. The method of claim 7, further comprising:

10. The method of claim 7, further comprising:

and obtaining the DNAI information from the SMF.

11. The method of claim 7, further comprising:

12. The method of claim 7, further comprising:

13. The method of claim 7, further comprising:

14. The method of claim 13, wherein the DNS server address is provided from a third party through an application function influencing flow.

15. A DNS processing device applied to SMF is characterized by comprising:

a selection module for selecting a DNS server and/or UPF;

16. An SMF, comprising: processor, memory and program stored on the memory and executable on the processor, which when executed by the processor implements the steps of the DNS processing method according to any of the claims 1 to 6.

17. A DNS processing device applied to UPF is characterized by comprising:

the second acquisition module is used for acquiring the DNS request;

18. A UPF, comprising: processor, memory and program stored on the memory and executable on the processor, which when executed by the processor implements the steps of the DNS processing method according to any of the claims 7 to 14.

19. A readable storage medium, having stored thereon a computer program which, when being executed by a processor, carries out steps comprising the method according to any one of claims 1 to 14.