WO2018112759A1

WO2018112759A1 - Resource access method, apparatus and system

Info

Publication number: WO2018112759A1
Application number: PCT/CN2016/111121
Authority: WO
Inventors: 陈华东; 张艳平
Original assignee: 华为技术有限公司
Priority date: 2016-12-20
Filing date: 2016-12-20
Publication date: 2018-06-28

Abstract

A resource access method, apparatus and system for improving resource access efficiency. The method comprises: a first network device receives a device address request message of a terminal device, the device address request message comprising a domain name corresponding to a resource requested to access by the terminal device; the first network device determines mobile communication network location identifier information of the terminal device; the first network device determines the address of a target device located in the mobile communication network according to the domain name and the mobile communication network location identifier information, the target device being used for storing resources; and the first network device sends a device address response message of the terminal device, the device address response message being used for indicating the address of the target device.

Description

Method, device and system for accessing resources

Technical field

The present application relates to the field of communications, and in particular, to a method, an apparatus, and a system for accessing resources.

Background technique

With the development of the Long Term Evolution (LTE) system, a Content Delivery Network (CDN) has a cache server deployed at a gateway at various edges, wherein the cache server can cache the Internet (English: Internet). Resources in the remote server. The purpose is to enable the terminal device to obtain the required content in the vicinity, to solve the congestion of the Internet, and to improve the response speed of the user to visit the website. The terminal device can obtain resources from the cache server at the periphery.

With the development of the CDN, there are cases where multiple servers cache the resources that the terminal device needs to access. How to select a suitable server to provide resources for the terminal device becomes an urgent problem to be solved.

Summary of the invention

The application provides a method, device and system for accessing resources, which can improve the efficiency of accessing resources.

The first aspect provides a method for accessing a resource, where the first network device receives a device address request message of the terminal device, where the device address request message includes a domain name corresponding to the resource requested by the terminal device; Determining, by the first network device, mobile communication network location identification information of the terminal device; the first network device determining, according to the domain name and the mobile communication network location identification information, an address of a target device located in the mobile communication network, The target device is configured to store the resource; the first network device sends a device address response message of the terminal device, and the device address response message is used to indicate an address of the target device.

In the embodiment of the present application, after receiving the device address request message of the terminal device, the first network device may select the mobile terminal in the mobile communication network according to the device address request message and the mobile communication network location identification information of the terminal device. Target devices, thereby improving the efficiency of users' access to resources and the efficiency of managing global network traffic.

In a possible implementation, the determining a mobile communication network location identifier of the terminal device The information includes: the first network device acquires terminal device identification information of the terminal device; the first network device sends the terminal device identification information of the terminal device to a mobile communication network control plane network element; A network device receives the mobile communication network location identification information from the mobile communication network control plane network element, and the mobile communication network location identification information is determined by the mobile communication network control plane network element according to the IP address information.

In a possible implementation, the device address request message includes mobile communication network location identification information of the terminal device.

In a possible implementation, the mobile communication network location identifier information is added by the terminal device or the access network device to the device address request message.

In a possible implementation manner, the mobile communication network location identifier information is any one of the following information: an access network cell identifier accessed by the terminal device, a base station identifier and a location of the terminal device accessing The tracking area location identifier of the terminal device.

In a possible implementation manner, the first network device is a domain name system DNS server.

In a possible implementation manner, the first network device receives a device address request message of the terminal device, where the first network device receives the device address request message by using a DNS server; And sending, by the device, the device address response packet of the terminal device, where the first network device sends the device address response packet by using the DNS server.

In a possible implementation, the method further includes: determining, by the first network device, whether the domain name belongs to a preset domain name set, where a device for storing a resource corresponding to the domain name set is located in a mobile communication network; Determining, by the first network device, location information of the mobile communication network of the terminal device, where the first network device determines the location of the mobile communication network of the terminal device, where the domain name belongs to the domain name set Identification information.

The second aspect provides a method for accessing a resource, where the access network device receives a device address request message sent by the terminal device, where the device address request message includes a resource corresponding to the resource requested by the terminal device. a domain name; the access network device adds the mobile communication network location identifier information of the terminal device in the device address request message; the access network device sends the device address request message to the first network device.

After receiving the device address request message of the terminal device, the access network device may add the mobile communication network location identification information of the terminal device to the device, and send the information to the first network device. Selecting a target device located in the mobile communication network according to the mobile communication network location identification information of the terminal device according to the first network device, thereby improving the efficiency of the user acquiring resources and allocating the global network. Traffic management efficiency.

In a third aspect, a network device is provided for performing the method of any of the first aspect or the first aspect of the first aspect. In particular, the apparatus comprises means for performing the method of any of the above-described first aspect or any of the possible implementations of the first aspect.

In a fourth aspect, an access network device is provided for performing the method in any of the foregoing possible implementations of the second aspect or the second aspect. In particular, the apparatus comprises means for performing the method of any of the above-described first or second aspects of the second aspect.

In a fifth aspect, a communication system is provided, the communication system comprising the network device of the above third aspect and the access network device of the above fourth aspect.

A sixth aspect provides a network device, including a memory for storing a program, a communication interface for communicating with other devices, and a processor for executing a program in the memory, when the program is executed, when The processor is operative to perform the method of the first aspect when the program is executed.

In a seventh aspect, an access network device is provided, including a memory for storing a program, a communication interface for communicating with other devices, and a processor for executing a program in the memory when the program is executed The processor is operative to perform the method of the second aspect when the program is executed.

According to an eighth aspect, a communication system is provided, the communication system comprising the network device of the sixth aspect, and the access network device of the seventh aspect. ,

In a ninth aspect, a system chip is provided, the system chip comprising means for performing the method of the first aspect.

In a tenth aspect, a system chip is provided, the system chip comprising means for performing the method of the second aspect.

In an eleventh aspect, a communication system is provided, the communication system comprising the system chip of the above ninth aspect, and the system chip of the above tenth aspect.

DRAWINGS

FIG. 1 is a schematic diagram of a possible application scenario of an embodiment of the present application.

FIG. 2(a) is a schematic structural diagram of a possible system architecture of an embodiment of the present application.

FIG. 2(b) is a schematic structural diagram of a possible system architecture according to still another embodiment of the present application.

FIG. 2(c) is a schematic structural diagram of a possible system architecture according to still another embodiment of the present application.

FIG. 3 is a schematic diagram of a domain name system according to an embodiment of the present application.

4 is a schematic flowchart of a method for accessing resources in an embodiment of the present application.

FIG. 5 is a schematic flowchart of a method for accessing resources according to still another embodiment of the present application.

FIG. 6 is a schematic flowchart diagram of a method for accessing resources according to still another embodiment of the present application.

FIG. 7 is a schematic flowchart diagram of a method for accessing resources according to still another embodiment of the present application.

FIG. 8 is a schematic flowchart diagram of a method for accessing resources according to still another embodiment of the present application.

FIG. 9 is a schematic flowchart diagram of a method for accessing resources according to another embodiment of the present application.

FIG. 10 is a schematic flowchart diagram of a method for accessing resources according to another embodiment of the present application.

FIG. 11 is a schematic flowchart diagram of a method for accessing resources according to another embodiment of the present application.

FIG. 12 is a schematic structural diagram of a network device according to an embodiment of the present application.

FIG. 13 is a schematic structural diagram of an access network device according to an embodiment of the present application.

FIG. 14 is a schematic structural diagram of a network device according to another embodiment of the present application.

FIG. 15 is a schematic structural diagram of an access network device according to another embodiment of the present application.

detailed description

The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings.

The network architecture and the service scenario described in the embodiments of the present application are for the purpose of more clearly illustrating the technical solutions of the embodiments of the present application, and do not constitute a limitation of the technical solutions provided by the embodiments of the present application. The technical solutions provided by the embodiments of the present application are equally applicable to similar technical problems.

As shown in FIG. 1, the terminal device accesses an Internet Protocol (IP) service network through a Radio Access Network (RAN) and a Core Network (CN), such as a multimedia subsystem (IP Multimedia System). , IMS) network, Packet Switched Streaming Service (Packet Switched Streaming Service, Simple PSS) network. The technical solution described in this application can be applied to a Long Term Evolution (LTE) system, or other wireless communication systems using various radio access technologies, for example, using Code Division Multiple Access (CDMA), and frequency. Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (Single Carrier Frequency) A system of access technologies such as Division Multiple Access (SC-FDMA). In addition, it can also be applied to subsequent evolution systems of the LTE system, such as the fifth generation (5th) Generation, 5G) systems, etc. For the sake of clarity, only the LTE system is taken as an example here. In the LTE system, an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) is used as a radio access network, and an Evolved Packet Core (EPC) is used as a core network. The terminal device accesses the IMS network through E-UTRAN and EPC.

In the embodiments of the present application, the terms "network" and "system" are often used interchangeably, but those skilled in the art can understand the meaning thereof.

The terminal device involved in the embodiments of the present application may include various handheld devices having wireless communication functions, in-vehicle devices, wearable devices, computing devices, or other processing devices connected to the wireless modem, and various forms of user devices (User Equipment, UE), mobile station (MS), terminal, terminal device, and the like. For convenience of description, in the embodiment of the present application, the devices mentioned above are collectively referred to as terminal devices.

A base station (BS) related to an embodiment of the present application is a device deployed in a radio access network to provide a wireless communication function for a terminal device. The base station may include various forms of macro base stations, micro base stations, relay stations, access points, and the like. In systems with different radio access technologies, the names of devices with base station functionality may vary. For example, in an LTE network, an evolved NodeB (eNB or eNodeB) is called a Node B or the like in a 3rd generation (3G) network. For convenience of description, in the embodiment of the present application, the foregoing apparatus for providing a wireless communication function for a terminal device is collectively referred to as a base station or a BS.

Optionally, in the embodiment of the present application, the mobile communication network may include a radio access network and a core network. The radio access network mainly provides access network services for mobile terminals, and the core network mainly provides switching and transmission services for various services. For example, the mobile communication network may include a network of access network devices, gateway devices, and the like. The access network device includes a base station, and the gateway device may include a Serving Gateway (SGW), a Packet Gateway (PGW), a Distributed Gateway (DGW), and the like.

2(a) to 2(c) show schematic structural diagrams of one possible system architecture 200 of an embodiment of the present application. As shown in FIG. 2(a) to FIG. 2(c), the terminal device accesses the SGW through the base station, and accesses the PGW through the SGW, where the Mobility Management Entity (MME) is used as the control plane network element. The MME is configured to connect to the base station and the SGW through the port, and the MME is configured to transmit signaling of the control plane to the base station and the SGW. Optionally, the PGW can be connected to a local (Local) Domain Name System (DNS) server. Those skilled in the art will appreciate that the above system architecture is merely an example. For example, a DNS server is not necessarily deployed in a PGW. It can also be deployed wherever any packet can be routed.

Optionally, a first network module may be introduced in the system architecture 200, and the first network module may be connected to the DNS server or located in the DNS server. The first network module may select a server within the mobile communication network for the terminal device based on the mobile communication network location identification information of the terminal device. The mobile communication network location identification information may be location identification information for indicating the terminal device within the mobile communication network.

Optionally, a second network module may also be introduced in the system network architecture 200. The second network module may be disposed in the DNS server or disposed outside the DNS server. The second network module may be configured to determine, according to a predetermined packet processing rule, whether the DNS request packet is processed by the second network module, and send the DNS packet to the first network if it is determined that the second network module processes the packet. Module.

Optionally, in the embodiment of the present application, the first network module may be referred to as an In-Network Global Server Load Balance (IN-GSLB) module. The second network module may also be referred to as an IN-GSLB Forwarding Element (FE) module.

Optionally, the system architecture 200 can also introduce a third network module. The third network module can be responsible for flow related signaling control. For example, the third network module can perform signaling interaction with the first network module and the second network module. Optionally, the third network module may send a message processing rule to the first network module and the second network module. Optionally, in the embodiment of the present application, the foregoing third network module may also be referred to as a flow controller (FC) module.

Optionally, the division of the foregoing network module is only a logical function division, and the actual implementation may have another division manner. For example, the first network module and the second network module may be separate network modules, or may be integrated into the same network module. The integrated network module can be placed in a DNS server.

Alternatively, the cache server can be deployed at the gateway. Or the cache server can also be deployed in a Mobile edging computing (MEC) node. Figure 2(a) shows the system architecture in which the cache server is deployed on the gateway. 2(b) and 2(c) show the system architecture in which the buffer is deployed in the MEC.

In Figure 2(a), the GW can be a lightweight packet gateway. The lightweight packet gateway can be connected to a cache server within the mobile communication network. The lightweight packet gateway may be a gateway with data routing and forwarding functions. The lightweight packet gateway may also be called a lightweight PGW. Do not qualify its name. For example, the lightweight packet gateway may not include a charging function, and the lightweight packet gateway may send charging information generated when the terminal device accesses the resource through the lightweight packet gateway to the PGW, and the PGW performs charging. Among them, a cache server is usually deployed at a PGW, a lightweight packet gateway, and the like. The gateway can be deployed in conjunction with the cache server or deployed separately.

As shown in FIG. 2(b), the MEC can be connected between the base station and the SGW. Alternatively, as shown in FIG. 2(c), the MEC may also be connected to the base station by means of suspension. The MEC can also deploy a cache server. And the MEC can be deployed in combination with the cache server, or it can be deployed separately.

It should be noted that FIG. 2( a ) to FIG. 2( c ) are only used as an example. When the solution of the embodiment of the present application is applied to a 2G or 3G network architecture, the function of the foregoing SGW may be served by a general packet radio technology. The Serving General Packet Radio Service Support Node (SGSN) is completed, and the function of the PGW can be completed by a Gateway General Packet Radio Service Support Node (GGSN).

3 is a schematic diagram of a Domain Name System (DNS) in the prior art. As shown in FIG. 3, after the DNS request packet containing the domain name sent by the terminal device is sent to the local DNS server, the local DNS server parses the DNS request packet. If the local server fails in the local area file and cache resolution, the local DNS server will send the DNS request message to the root DNS server. After receiving the DNS request message, the root DNS server will determine who the domain name is authorized to manage after receiving the request from the root DNS server, and will return an IP responsible for the top-level domain name server to the local DNS server. After the local DNS server receives the IP information, it will contact the server responsible for the domain. After receiving the request, the server responsible for the domain will find the address of the next-level DNS server of the administrative domain to the local DNS server if it cannot resolve it. When the local DNS server receives this address, it will find the domain server, repeat the above actions, and query until the host address corresponding to the domain name is found. The numerical sequence number in FIG. 3 is used to indicate the step of domain name resolution.

According to the method for the domain name resolution described above, in the prior art, the local DNS server first searches locally whether to cache the resource requested by the DNS request message. If there is no cache resource locally, the DNS request packet is sent directly to the root DNS server to request the root DNS server to parse the DNS request packet. The IP address of the domain name obtained by the root DNS server is usually the server of the content provider or the cache of the server of the content provider. server. Correspondingly, the host IP address returned by the root DNS server is located on a fixed network, which may be remotely issued by DNS. The requested terminal device is far away, which is disadvantageous for the terminal device to obtain resources nearby, and is not conducive to making full use of the server at the edge of the network and reasonably allocating global network traffic.

With the development of the CDN network, the cache server of the cache resource is continuously deployed to all edges, or the cache server in the mobile communication network also caches resources in the remote server that the terminal device requests to access. For example, a cache server can be deployed at each gateway in the mobile communication network. If the terminal device can preferentially acquire resources from the server in the mobile communication network, the efficiency of accessing the resources can be improved, and the management of the global network traffic can be optimized.

Based on the situation, the embodiment of the present application provides a method for accessing a resource, and the central idea is that after receiving the DNS request message of the terminal device, the network device may perform the request according to the DNS request message and the terminal device. The location identification information in the communication network selects a target server in the mobile communication network for the terminal device, thereby improving the efficiency of the user acquiring the resource and the management efficiency of allocating the global network traffic.

FIG. 4 is a schematic flowchart of a method 400 for accessing resources according to an embodiment of the present application. The method of Figure 4 can be performed by a first network device. The first network device may be a device or a physical device that includes the second network module in the system architecture 200 of FIG. 2. The method 400 includes:

S401. The first network device receives a device address request message of the terminal device, where the device address request message includes a domain name corresponding to the resource requested by the terminal device.

Optionally, the device address request message may include a DNS request message.

Alternatively, the first network device may be a device that includes a first network module in system architecture 200. Optionally, the first network device may further include a second network module in the system architecture 200. The first network device can be a DNS server. Alternatively, the first network device may be located outside the DNS server, and may obtain a device address request message of the terminal device from the DNS server.

Optionally, in a case where the first network device is located outside the DNS server, the first network device may receive the device address request message through the DNS server.

Optionally, after acquiring the device address request packet, the first network device may perform the offload processing on the device address request packet according to the pre-stored offloading and processing rule. The first network device may determine, according to the offloading and processing rules, that the second network module in the first network device processes the device address request message. Alternatively, it is determined that the device address request message is processed according to the domain name resolution method shown in FIG. 3.

The offloading and processing rules may include an index of resources cached by the cache server within the mobile communication network. For example, the offloading and processing rules can include a preset set of domain names. Among them, for storage The device of the resource corresponding to the domain name set is located in the mobile communication network. The first network device may request, according to the device address, whether the domain name in the packet belongs to the domain name set, and query whether the server in the mobile communication network caches the resource requested by the device address request message. If the server in the mobile communication network caches the resource requested by the device address request message, the first network device may further determine the mobile communication network location identification information of the terminal device. Optionally, if the server in the mobile communication network does not cache the resource requested by the device address request message, the device address request message may be processed according to the method shown in FIG. 3.

S402. The first network device determines mobile communication network location identification information of the terminal device.

The first network device obtains the mobile communication network location identification information of the terminal device, so as to determine the target device located in the mobile communication network corresponding to the device address request message according to the mobile communication network location information and the domain name included in the device address request message. The target device may be a device that stores a resource that the terminal device requests to access.

Optionally, the mobile communication network location identification information of the terminal device may be an address that can represent the geographic location of the terminal device in the mobile communication network. For example, the mobile communication network location identifier information may be an access network cell identifier accessed by the terminal device, a base station identifier accessed by the terminal device, or a tracking area location identifier of the terminal device. For example, the access network cell identifier may include an Evolved Universal Terrestrial Radio Access Network (E-UTRAN Cell Global Identifier or simply "ECGI").

Optionally, the first network device has multiple manners of acquiring mobile communication network location identification information of the terminal device. Next, the manner of obtaining the location identification information of the mobile communication network of the terminal device will be introduced.

In the first mode, the terminal device may add the mobile communication network location identifier information of the terminal device in the DNS extension (English: extension) in the sent device address request message. The first network device may obtain the mobile communication network location identification information of the terminal device by using the device address request message.

In the second mode, the device address request message will pass through the network device such as the access network device, the SGW, or the PGW in the process of being sent from the terminal device to the first network device. The access network device includes a base station. The terminal device may not add the mobile communication network location identification information of the terminal device when transmitting the device address request message, but the access network device or the PGW receives the device address request message sent by the terminal device, and then requests the device address request message. The device adds the location identification information of the mobile communication network of the terminal device, and sends the device address request message to the next hop device until the first network device receives the device address request message, and obtains the terminal from the device address request message. Equipment shift Mobile communication network location identification information.

In the third mode, the first network device may acquire the mobile communication network location identification information of the terminal device by using the mobile communication network control plane network element. The mobile communication network control plane network element may comprise an MME. After the first network device receives the device address request message, if it is determined that the device address request message does not include the mobile communication network location identifier information of the terminal device, the first network device may send a request to the mobile communication network control plane network element. The message is used to query the mobile communication network control plane network element for the mobile communication network location identification information of the terminal device. The request message may include terminal device identification information of the terminal device. The terminal device identification information is used to indicate the identity of the terminal device. For example, the terminal device identification information may include at least one of the following information: an IP address of the terminal device, an International Mobile Subscriber Identification Number (IMSI) of the terminal device, and a globally unique temporary UE identifier of the terminal device (Globally Unique Temporary UE Identity (GUTI), the mobile station integrated services digital network number (MSISDN) of the terminal device.

As an example, the terminal device identification information of the terminal device may be obtained from the device address request message, or the device address request message may include the terminal device identification information of the terminal device. The network element of the mobile communication network control plane may query the location identification information of the mobile communication network of the terminal device according to the terminal device identification information of the terminal device, and send the location identification information of the mobile communication network of the terminal device to the first network device.

S403. The first network device determines an address of a target device located in the mobile communication network according to the domain name and the location identifier information of the mobile communication network, where the target device is configured to store the resource.

Optionally, the first network device may determine, according to the domain name and the mobile communication network location identifier information of the terminal device, the target device corresponding to the domain name. As a preferred solution, the first network device may determine that the device that is closer to the location of the terminal device is the target device. Wherein determining the address of the target device may include determining an IP address of the target device.

Optionally, the target device may be a server. The first network device can manage servers within a certain geographical area. When selecting the target server corresponding to the domain name, the location information of the mobile communication network of the terminal device is considered, for example, the server closer to the terminal device is preferentially selected.

S404. The first network device sends a device address response packet of the terminal device, where the device address response message is used to indicate an address of the target device.

Optionally, the device address response message may include an IP address of the target device.

Optionally, the first network device may send the DNS response packet to the terminal device, so that The target device is determined by the terminal device, and the resource is acquired from the target device.

Optionally, in a case where the first network device is located outside the DNS server, the first network device may send the device address response message through the DNS server.

The method for accessing resources of the embodiment of the present application is described above with reference to FIG. 1 to FIG. 4 . A specific example of a method for accessing resources will be described below with reference to FIG. 5 to FIG. 11. It should be noted that the examples of FIG. 5 to FIG. 11 are merely for helping those skilled in the art to understand the embodiment of the present application, and not to The application examples are limited to the specific numerical values or specific scenarios illustrated. A person skilled in the art will be able to make various modifications or changes in the embodiments according to the examples of FIG. 5 to FIG. 11 , and such modifications or variations are also within the scope of the embodiments of the present application.

FIG. 5 is a schematic flowchart of a method 500 for accessing resources according to an embodiment of the present application. Method 500 can be performed by a device in system architecture 200. The IN-GSLB module in FIG. 5 may be the first network device in the method 400. Alternatively, the IN-GSLB module and the IN-GSLB FE module can be integrated into one module. The integrated module can be the first network device in method 400. For convenience of description, the IN-GSLB module and the IN-GSLB FE module are described in FIG. 5 as discrete modules. Also, the IN-GSLB module is located in the DNS server. As shown in FIG. 5, method 500 includes:

S501: The FC module sends the offloading and processing rules to the IN-GSLB FE module in advance.

S502: The terminal device sends a DNS request message, and the DNS request message is sent to the local DNS server via the eNB, the SGW, and the PGW.

S503: The IN-GSLB FE module in the local DNS server performs the offloading judgment according to the rules issued by the FC module.

S504. If it is determined that the processing is sent to the IN-GSLB module, the DNS request message and the terminal device identification information of the terminal device are sent to the IN-GSLB module together; or the terminal device identifier may be sent only to the IN-GSLB module. The identifier of the content request. Optionally, if it is determined that the processing is not to be sent to the IN-GSLB module, the DNS resolution process is performed according to the method shown in FIG. 3.

S505, the IN-GSLB module receives the local DNS server (which contains the IN-GSLB FE mode) After the DNS request message sent by the block, the location identification information of the mobile communication network of the terminal device is first obtained. For example, it can be the ECGI of the terminal device.

S506. The IN-GSLB module selects a server in the appropriate mobile communication network to serve the terminal device according to the location identification information of the mobile communication network of the terminal device. For example, a server that is closer to the location of the terminal device is selected to serve the terminal device.

S507, the IN-GSLB module returns the server selection result in the mobile communication network to the local DNS server.

S508: After receiving the selection result message of the IN-GSLB module, the local DNS server returns a DNS response message to the PGW for subsequent processing if the server selects successfully; optionally, if the server selection in the DNS response message is unsuccessful, Then, it is processed according to the DNS resolution process in the prior art shown in FIG.

In the embodiment of the present application, the IN-GSLB module introduced in the system architecture may provide resources for the terminal device to select a server in the mobile communication network according to the DNS request message and the mobile communication network location identification information of the terminal device, thereby improving The efficiency with which users obtain resources and the efficiency with which global network traffic is allocated.

FIG. 6 is a schematic flowchart of a method 600 for accessing resources according to an embodiment of the present application. Method 600 can be performed by a device in system architecture 200. The IN-GSLB module in FIG. 6 may be the first network device in the method 400. Alternatively, the IN-GSLB module and the IN-GSLB FE module can be integrated into one module. The integrated module can be the first network device in method 400. For convenience of description, the IN-GSLB module and the IN-GSLB FE module are described in FIG. 6 as discrete modules. Also, the IN-GSLB module is located in the DNS server.

In the method of FIG. 6, the IN-GSLB module requests the MME for the ECGI corresponding to the IP address of the terminal device in the case where it is determined that the DNS request message does not carry the address information in the mobile communication network of the terminal device. After obtaining the corresponding ECGI according to the IP address of the terminal device, the MME returns the corresponding ECGI information to the IN-GSLB module. As shown in FIG. 6, method 600 includes:

S601: The FC module sends the offloading and processing rules to the IN-GSLB FE module in advance.

S602: The terminal device sends a DNS request message, and the DNS request message is sent to the local DNS server via the eNB, the SGW, and the PGW, and the DNS request message includes an IP address of the terminal device.

S603: The IN-GSLB FE module in the local DNS server performs the offloading judgment according to the rules issued by the FC module.

S604, if it is determined that the processing is sent to the IN-GSLB module, the local DNS server will The DNS request message and the IP address of the terminal device are sent to the IN-GSLB module. Alternatively, it is also possible to transmit only the identity of the terminal device identification and the content request to the IN-GSLB module.

S605. After receiving the DNS request packet sent by the local DNS server (that is, the DNS server that includes the IN-GSLB FE module), the IN-GSLB module determines whether the DNS request packet contains the ECGI information. If the DNS request message does not contain the ECGI information, it is determined that the ECGI information of the terminal device needs to be obtained.

S606. If it is determined that the ECGI of the terminal device needs to be acquired, the IN-GSLB module sends a message to the MME requesting to acquire the ECGI corresponding to the IP address of the terminal device.

S607. The MME queries the corresponding ECGI according to the IP address of the terminal device.

S608. The MME returns the ECGI information corresponding to the IP address of the terminal device to the IN-GSLB module.

S609: The IN-GSLB module selects a server (ie, a target server) in a suitable mobile communication network to serve the terminal device according to the domain name included in the ECGI and the DNS request message of the terminal device.

S610, the IN-GSLB module returns the target server selection result to the local DNS server;

S611: After receiving the selection result message sent by the IN-GSLB module, the local DNS server returns a DNS response message to the PGW if the server selects successfully, until the DNS message is sent to the terminal device.

In the embodiment of the present application, an IN-GSLB module is introduced in the system architecture, and the ECGI corresponding to the terminal device is obtained from the MME, and the terminal device is selected in the mobile communication network according to the DNS request message and the ECGI of the terminal device. The target server, thereby improving the efficiency of users' access to resources and the efficiency of managing global network traffic.

FIG. 7 is a schematic flowchart diagram of a method 700 for accessing resources according to an embodiment of the present application. Method 700 can be performed by a device in system architecture 200. The IN-GSLB module in FIG. 7 may be the first network device in the method 400. Alternatively, the IN-GSLB module and the IN-GSLB FE module can be integrated into one module. The integrated module can be the first network device in method 400. For convenience of description, the IN-GSLB module and the IN-GSLB FE module are described in FIG. 7 as discrete modules. Also, the IN-GSLB module is located in the DNS server.

In the method of FIG. 7, the PGW may inform the first network device of the ECGI information. As shown in FIG. 7, method 700 includes:

S701: The FC module sends the offloading and processing rules to the IN-GSLB FE module in advance.

S702: The terminal device sends a DNS request message, and the DNS request message is sent to the local DNS server via the eNB, the SGW, and the PGW, and the DNS request message includes an IP address of the terminal device.

S703: The PGW determines whether the DNS request message includes the ECGI information of the terminal device, and if yes, sends the ECGI information and the DNS request message to the local DNS server.

S704: The IN-GSLB FE module in the local DNS server performs the offloading judgment according to the rules issued by the FC module.

S705: If it is determined that the processing is sent to the IN-GSLB module, the IN-GSLB FE module sends the DNS request message and the ECGI of the terminal device to the IN-GSLB module. Alternatively, it is also possible to transmit only the identity of the terminal device identification and the content request to the IN-GSLB module.

S706: The IN-GSLB module selects a server (ie, a target server) in the appropriate mobile communication network to serve the terminal device according to the domain name included in the ECGI and the DNS request message of the terminal device.

S707, the IN-GSLB module returns the target server selection result to the local DNS server;

S708: After receiving the selection result message sent by the IN-GSLB module, if the server selects successfully, the local DNS server returns a DNS response message to the PGW until the DNS message is sent to the terminal device.

In the embodiment of the present application, the PGW can add the ECGI of the terminal device in the DNS response message, so that the IN-GSLB module selects the target server in the mobile communication network for the terminal device according to the DNS request message and the ECGI of the terminal device. , thereby improving the efficiency of users to obtain resources and the management efficiency of allocating global network traffic.

FIG. 8 is a schematic flowchart of a method 800 for accessing resources according to an embodiment of the present application. Method 800 can be performed by a device in system architecture 200. The IN-GSLB module in FIG. 8 may be the first network device in the method 400. Alternatively, the IN-GSLB module and the IN-GSLB FE module can be integrated into one module. The integrated module can be the first network device in method 400. For convenience of description, the IN-GSLB module and the IN-GSLB FE module are described in FIG. 8 as discrete modules. Also, the IN-GSLB module is located in the DNS server. In the method of FIG. 8, the ECGI of the terminal device is added to the DNS request message by the access network device (eg, the eNB). As shown in FIG. 8, method 800 includes:

S801: The FC module sends the offloading and processing rules to the IN-GSLB FE module in advance.

S802: The terminal device sends a DNS request message, and the DNS request message is sent to the local DNS server via the eNB, the SGW, and the PGW, and the DNS request message includes an IP address of the terminal device.

S803. The eNB adds ECGI information to the DNS packet. For example, the eNB can add ECGI information using the DNS extension function.

S804. The eNB sends the modified DNS request message to the local DNS server via the SGW and the PGW.

S805. The IN-GSLB FE module in the local DNS server performs the traffic distribution judgment according to the rules issued by the FC module.

S806. If it is determined that the processing is sent to the IN-GSLB module, the IN-GSLB FE module sends the DNS packet to the IN-GSLB module.

S807: The IN-GSLB module selects a server (ie, a target server) in a suitable mobile communication network to serve the terminal device according to the domain name included in the ECGI and the DNS request message of the terminal device.

S808, the IN-GSLB module returns the target server selection result to the local DNS server;

S809. After receiving the selection result message sent by the IN-GSLB module, the local DNS server returns a DNS response message to the PGW if the server selects successfully, until the DNS message is sent to the terminal device.

In the embodiment of the present application, the base station adds the ECGI of the terminal device in the DNS request message, so that the IN-GSLB module selects the target server in the mobile communication network for the terminal device according to the DNS request message and the ECGI of the terminal device, thereby Improve the efficiency of users' access to resources and the efficiency of managing global network traffic.

FIG. 9 is a schematic flowchart of a method 900 for accessing resources according to an embodiment of the present application. Method 900 can be performed by a device in system architecture 200. The IN-GSLB module in FIG. 9 may be the first network device in the method 400. Alternatively, the IN-GSLB module and the IN-GSLB FE module can be integrated into one module. The integrated module can be the first network device in method 400. For convenience of description, the IN-GSLB module and the IN-GSLB FE module are described in FIG. 9 as discrete modules. Also, the IN-GSLB module is located in the DNS server.

In the method of FIG. 9, the terminal device may add the ECGI of the terminal device in the DNS request message, so that the IN-GSLB module acquires the ECGI of the terminal device. As shown in FIG. 9, method 900 includes:

S901: The FC module sends the offloading and processing rules to the IN-GSLB FE module in advance.

S902: The terminal device sends a DNS request message, and the DNS extension function in the DNS request message carries the ECGI information of the terminal device.

S903. The DNS request message with the added ECGI is sent to the local DNS server via the eNB, the SGW, and the PGW.

S904: The IN-GSLB FE module in the local DNS server performs the offloading judgment according to the rules issued by the FC module.

S905. If it is determined that the processing is sent to the IN-GSLB module, the DNS request message is sent to the IN-GSLB module.

S906, the IN-GSLB module selects a server (ie, a target server) in the appropriate mobile communication network to serve the terminal device according to the domain name included in the ECGI and the DNS request message of the terminal device.

S907: The IN-GSLB module replies the target server selection result to the local DNS server.

S908: After receiving the selection result message sent by the IN-GSLB module, the local DNS server returns a DNS response message to the PGW if the server selects successfully, until the DNS message is sent to the terminal device.

In the embodiment of the present application, the terminal device adds the ECGI of the terminal device in the DNS request message, so that the IN-GSLB module selects the target server in the mobile communication network for the terminal device according to the DNS request message and the ECGI of the terminal device. Thereby improving the efficiency of the user to obtain resources and the management efficiency of allocating global network traffic.

FIG. 10 is a schematic flowchart diagram of a method 1000 for accessing resources according to an embodiment of the present application. FIG. 10 shows a method for a first network device to select a target server according to an embodiment of the present application. The method of Figure 10 can be applied to the various embodiments shown in Figures 4-9. The first network device may be an IN-GSLB module of the system architecture 200 or a device including an IN-GSLB module.

S1001, the IN-GSLB module receives the DNS request message and the ECGI information of the terminal device;

S1002: The IN-GSLB module determines the location of the terminal device according to the ECGI information of the terminal device, and comprehensively performs load balancing, quality of service (QoS), and the like in the vicinity of the terminal device location for server selection.

S1003. The IN-GSLB module determines whether a suitable server is selected within a range of the location of the terminal device. If not, the server selection is performed within all servers managed by the IN-GSLB; if the determination result is yes, the local DNS server is replied that the server selection in the mobile communication network is successful, and the local DNS server is notified to reply the DNS response message to the terminal device. .

In S1004, if the result of the determination in the S1003 part is NO, the IN-GSLB module performs server selection in all servers managed by the IN-GSLB module.

S1005: The IN-GSLB module determines whether the server is managed by the IN-GSLB module to select a suitable target server: if not, the local DNS server is replied to the server selection failure in the mobile communication network, and the local DNS server is notified to continue to the mobile communication network. If the judgment result is yes, the local DNS server is replied that the server selection in the mobile communication network is successful, and the local DNS server is notified to reply the DNS response message to the terminal device.

In the embodiment of the present application, after acquiring the location identification information of the mobile communication network of the terminal device, the IN-GSLB module performs server selection in the mobile communication network according to the location identification information, for example, preferentially selecting the server in the vicinity of the location of the terminal device, if The server is selected in the range of all servers managed by the IN-GSLB module, and the result is returned to the local DNS server, thereby improving the efficiency of the user to obtain resources and the efficiency of allocating global network traffic.

FIG. 11 is a schematic flowchart diagram of a method 1100 for accessing resources according to an embodiment of the present application. FIG. 11 illustrates a method of adding ECGI information by using a DNS extension function in an embodiment of the present application. The method of Figure 11 can be applied to the embodiment shown in Figure 8 or Figure 9. The method 1100 of Figure 11 can be performed by a base station (eNB), a terminal device, or other device having a DNS extension function. For the sake of brevity, the following will describe the eNB as an example. Method 1100 includes:

S1101: The eNB receives the packet.

S1102: The eNB uses the DNS extension function to determine whether the received packet is a DNS request packet. For example, the eNB can determine whether it is a DNS request packet according to the destination port number of the packet.

S1103: If the packet is a DNS request packet, the ECGI information of the terminal device may be added in the DNS extension area.

S1104. If it is determined that it is not a DNS request message, the original message remains unchanged.

In the embodiment of the present application, the destination port number of the packet is used to determine whether the received packet is a DNS request packet, and in the case that the packet is a DNS request packet, the DNS extension function is used in the DNS request packet. Add ECGI information.

The method for accessing resources in the embodiment of the present application is described in detail above with reference to FIG. 1 to FIG. The apparatus of the embodiment of the present application will be described below with reference to FIGS. 12 to 15.

FIG. 12 shows a schematic block diagram of a network device 1200 in an embodiment of the present application. Network device 1200 can perform the steps performed by the first network device in the methods of FIGS. 1 through 11. The network device 1200 includes a communication unit 1210 and a processing unit 1220.

The processing unit 1220 is configured to receive, by the communication unit 1210, a device location of the terminal device. An address request message, the device address request message includes a domain name corresponding to the resource requested by the terminal device, and a mobile communication network location identification information of the terminal device; and the domain name and the mobile communication network according to the Position identification information, determining an address of a target device located in the mobile communication network, the target device is configured to store the resource; and transmitting, by the communication unit, a device address response message of the terminal device, the device address response report The text is used to indicate the address of the target device.

It should be understood that the network device 1200 herein is embodied in the form of a functional unit. The term "unit" herein may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor for executing one or more software or firmware programs (eg, a shared processor, a proprietary processor, or a group). Processors, etc.) and memory, merge logic, and/or other suitable components that support the described functionality. In an optional example, those skilled in the art may understand that the network device 1200 may be specifically the first network device in the foregoing embodiment, and the network device 1200 may be configured to perform each of the foregoing method embodiments corresponding to the first network device. Processes and/or steps, to avoid repetition, will not be repeated here.

FIG. 13 shows a schematic block diagram of an access network device 1300 of an embodiment of the present application. The access network device 1300 can perform the steps performed by the access network device in the methods of FIGS. 1 through 11. The access network device 1300 includes: a communication unit 1310 and a processing unit 1320,

The processing unit 1320 is configured to receive, by the communication unit 1310, a device address request message sent by the terminal device, where the device address request message includes a domain name corresponding to the resource requested by the terminal device, and the device address Adding mobile communication network location identification information of the terminal device to the request message; and transmitting the device address request message to the access network device by using the communication unit 1310.

It should be understood that the access network device 1300 herein is embodied in the form of a functional unit. The term "unit" herein may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor for executing one or more software or firmware programs (eg, a shared processor, a proprietary processor, or a group). Processors, etc.) and memory, merge logic, and/or other suitable components that support the described functionality. In an optional example, those skilled in the art may understand that the access network device 1300 may be specifically the access network device in the foregoing embodiment, and the access network device 1300 may be used to perform the foregoing method and the access network. The various processes and/or steps corresponding to the device are not repeated here to avoid repetition.

FIG. 14 shows a schematic block diagram of a network device 1400 of an embodiment of the present application. Internet equipment 1400 can perform the steps performed by the first network device in the methods of FIGS. 1 through 11. Network device 1400 includes:

a memory 1410, configured to store a program;

a communication interface 1420, configured to communicate with other devices;

The processor 1430 is configured to execute a program stored in the memory 1410. When the program is executed, the processor 1430 is configured to receive, by using the communication interface 1420, a device address request message of the terminal device, where the device address request message is received. The text includes a domain name corresponding to the resource requested by the terminal device; and determining mobile communication network location identification information of the terminal device; and determining a target located in the mobile communication network according to the domain name and the mobile communication network location identification information An address of the device, the target device is configured to store the resource; and the device address response message of the terminal device is sent by the communication unit, where the device address response message is used to indicate an address of the target device.

It should be understood that the network device 1400 may be specifically the first network device in the foregoing embodiment, and may be used to perform various steps and/or processes corresponding to the first network device in the foregoing method embodiments. Optionally, the memory 1430 can include read only memory and random access memory and provides instructions and data to the processor. A portion of the memory may also include a non-volatile random access memory. For example, the memory can also store information of the device type. The processor 1410 can be configured to execute instructions stored in a memory, and when the processor 1410 executes instructions stored in the memory, the processor 1410 is configured to perform the various steps of the method embodiment corresponding to the first network device And / or process.

FIG. 15 shows a schematic block diagram of an access network device 1500 according to an embodiment of the present application. Access network device 1500 can perform the steps performed by the access network device in the methods of FIGS. 1 through 11. Access network device 1500 includes:

a memory 1510, configured to store a program;

a communication interface 1520, configured to communicate with other devices;

The processor 1530 is configured to execute a program stored in the memory 1510. When the program is executed, the processor 1530 is configured to receive, by using the communication interface 1520, a device address request message sent by the terminal device, where the device address request is received. The message includes a domain name corresponding to the resource that the terminal device requests to access; and adding the mobile communication network location identifier information of the terminal device in the device address request message; and sending the first network device to the first network device by using the communication unit The device address requests a message.

It should be understood that the access network device 1500 may be specifically the access network device in the foregoing embodiment, and It can be used to perform various steps and/or processes corresponding to the access network device in the foregoing method embodiments. Optionally, the memory 1530 can include read only memory and random access memory and provides instructions and data to the processor. A portion of the memory may also include a non-volatile random access memory. For example, the memory can also store information of the device type. The processor 1510 can be configured to execute instructions stored in a memory, and when the processor 1510 executes instructions stored in the memory, the processor 1510 is configured to perform the various steps of the method embodiments corresponding to the access network device described above and / or process.

Additionally, the terms "system" and "network" are used interchangeably herein. The term "and/or" in this context is merely an association describing the associated object, indicating that there may be three relationships, for example, A and / or B, which may indicate that A exists separately, and both A and B exist, respectively. B these three situations. In addition, the character "/" in this article generally indicates that the contextual object is an "or" relationship.

It should be understood that in the embodiment of the present application, "B corresponding to A" means that B is associated with A, and B can be determined according to A. However, it should also be understood that determining B from A does not mean that B is only determined based on A, and that B can also be determined based on A and/or other information.

Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the various examples described in connection with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both, for clarity of hardware and software. Interchangeability, the composition and steps of the various examples have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods to implement the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present application.

A person skilled in the art can clearly understand that, for the convenience and brevity of the description, the specific working process of the system, the device and the unit described above can refer to the corresponding process in the foregoing method embodiment, and details are not described herein again.

In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units or components may be combined or may be Integrate into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication through some interface, device or unit. The letter connection can also be electrical, mechanical or other form of connection.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the embodiments of the present application.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a standalone product, can be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be in essence or part of the contribution to the prior art, or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium. There are a number of instructions for causing a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the method of various embodiments of the present application. The foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like. .

The technical features and descriptions in the above embodiments are used in order to make the application documents clear and clear, and can be understood to be applicable to other embodiments, and will not be further described in other embodiments.

The foregoing is only a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto, and any equivalents can be easily conceived by those skilled in the art within the technical scope disclosed in the present application. Modifications or substitutions are intended to be included within the scope of the present application. Therefore, the scope of protection of this application should be determined by the scope of protection of the claims.

Claims

A method for accessing a resource, comprising:

Receiving, by the first network device, a device address request message of the terminal device, where the device address request message includes a domain name corresponding to the resource requested by the terminal device;

Determining, by the first network device, mobile communication network location identification information of the terminal device;

Determining, by the first network device, an address of a target device located in the mobile communication network according to the domain name and the location identifier information of the mobile communication network, where the target device is configured to store the resource;

The first network device sends a device address response message of the terminal device, where the device address response message is used to indicate an address of the target device.
The method of claim 1, wherein the determining the mobile communication network location identification information of the terminal device comprises:

The first network device acquires terminal device identification information of the terminal device;

Transmitting, by the first network device, terminal device identification information of the terminal device to a mobile communication network control plane network element;

Receiving, by the first network device, the mobile communication network location identifier information from the mobile communication network control plane network element, where the mobile communication network location identifier information is the mobile communication network control plane network element according to the IP address information definite.
The method of claim 1, wherein the device address request message comprises mobile communication network location identification information of the terminal device.
The method of claim 3, wherein the mobile communication network location identification information is added to the device address request message by the terminal device or the access network device.
The method according to any one of claims 1 to 4, wherein the mobile communication network location identification information is any one of the following information: an access network cell identifier and a location accessed by the terminal device The base station identifier accessed by the terminal device and the tracking area location identifier of the terminal device.
The method according to any one of claims 1 to 5, wherein the first network device is a domain name system DNS server.
The method according to any one of claims 1 to 5, wherein the first network device receives a device address request message of the terminal device, including: the first network device receiving the device through a DNS server Address request message;

And sending, by the first network device, the device address response packet of the terminal device, where the first network device sends the device address response packet by using the DNS server.
The method according to any one of claims 1 to 7, wherein the method further comprises:

Determining, by the first network device, whether the domain name belongs to a preset domain name set, where the device for storing the resource corresponding to the domain name set is located in the mobile communication network;

Determining, by the first network device, location information of the mobile communication network of the terminal device, where the first network device determines the location of the mobile communication network of the terminal device, where the domain name belongs to the domain name set Identification information.
A method for accessing a resource, comprising:

The access network device receives the device address request message sent by the terminal device, where the device address request message includes a domain name corresponding to the resource requested by the terminal device;

Adding, by the access network device, location information of the mobile communication network of the terminal device in the device address request message;

The access network device sends the device address request message to the first network device.
The method according to claim 9, wherein the mobile communication network location identification information is any one of the following information: an access network cell identifier accessed by the terminal device, and the terminal device accessing The base station identifier and the tracking area location identifier of the terminal device.
A network device, comprising: a communication unit and a processing unit,

The processing unit is configured to receive, by the communication unit, a device address request message of the terminal device, where the device address request message includes a domain name corresponding to the resource requested by the terminal device, and determine a mobile communication of the terminal device Network location identification information; and determining an address of a target device located in the mobile communication network according to the domain name and the mobile communication network location identification information, the target device is configured to store the resource; and transmitting the location by using the communication unit And a device address response message of the terminal device, where the device address response message is used to indicate an address of the target device.
The network device according to claim 1, wherein the processing unit is configured to acquire, by the processing unit, terminal device identification information of the terminal device, in determining the location information of the mobile communication network of the terminal device. Transmitting, by the communication unit, terminal device identification information of the terminal device to a mobile communication network control plane network element; and receiving, by the communication unit, the mobile communication network location identifier from the mobile communication network control plane network element Information, the mobile communication network location identification information is determined by the mobile communication network control plane network element according to the IP address information.
The network device of claim 11 wherein said device address request The message includes mobile communication network location identification information of the terminal device.
The network device according to claim 13, wherein the mobile communication network location identification information is added by the terminal device or the access network device to the device address request message.
The network device according to any one of claims 11 to 14, wherein the mobile communication network location identification information is any one of the following information: an access network cell identifier accessed by the terminal device, The base station identifier accessed by the terminal device and the tracking area location identifier of the terminal device.
The network device according to any one of claims 11 to 15, wherein the network device is a domain name system DNS server.
The network device according to any one of claims 11 to 15, wherein the processing unit is specifically configured to receive, by the communication unit, a DNS server by using the communication unit in the device address request message of the receiving terminal device. The device address request message; the processing unit is configured to send the device address response message by using the communication unit by using the communication unit, in the sending the device address response message of the terminal device.
The network device according to any one of claims 11 to 17, wherein the processing unit is further configured to determine whether the domain name belongs to a preset domain name set, where The device of the resource is located in the mobile communication network and determines the mobile communication network location identification information of the terminal device, including: when the domain name belongs to the domain name set, the first network device determines the mobile device Communication network location identification information.
An access network device, comprising: a communication unit and a processing unit,

The processing unit is configured to receive, by the communication unit, a device address request message sent by the terminal device, where the device address request message includes a domain name corresponding to the resource requested by the terminal device, and the device address request message Adding mobile communication network location identification information of the terminal device; and transmitting, by the communication unit, the device address request message to the first network device.
The access network device according to claim 19, wherein the mobile communication network location identification information is any one of the following information: an access network cell identifier accessed by the terminal device, and the terminal device The base station identifier of the access and the tracking area location identifier of the terminal device.