CN109561141B

CN109561141B - CDN node selection method and equipment

Info

Publication number: CN109561141B
Application number: CN201811391682.8A
Authority: CN
Inventors: 张勍; 冯毅; 盛煜; 朱常波; 李先达; 单丽雅
Original assignee: China United Network Communications Group Co Ltd
Current assignee: China United Network Communications Group Co Ltd
Priority date: 2018-11-21
Filing date: 2018-11-21
Publication date: 2020-05-22
Anticipated expiration: 2038-11-21
Also published as: CN109561141A

Abstract

The embodiment of the invention discloses a method and equipment for selecting CDN nodes, which relate to the field of communication and realize the selection of edge CDN nodes for high-priority users, thereby reducing service access time delay. The specific scheme is as follows: the method comprises the steps that a global load balancer receives a DNS request and a terminal identifier sent by an MEC server, a target external CDN node is determined according to a preset rule and the DNS request, the IP address of the target external CDN node is sent to the MEC server, when a pre-stored high-priority identifier set is determined to comprise the terminal identifier, an application message for applying for using the edge CDN node is sent to the MEC server, and a response message for using the edge CDN node sent by the MEC server is received. The embodiment of the invention is used for the process of selecting the CDN node for the terminal.

Description

CDN node selection method and equipment

Technical Field

The embodiment of the invention relates to the field of communication, in particular to a method and equipment for selecting Content Delivery Network (CDN) nodes.

Background

With the development of Mobile internet services and network technologies, a Mobile Edge Computing (MEC) architecture is beginning to emerge. The mobile network Service can be provided by using the MEC architecture, wherein when the CDN Service is provided, a CDN node can be selected by using the MEC architecture so that the terminal can obtain the required content nearby, and the selection of the CDN node can be implemented by using a Domain Name Service (DNS) technology.

In the prior art, the selection process of the CDN nodes is as follows: the MEC server receives a DNS request sent by the terminal, and forwards the DNS request to a corresponding global load balancer via the core network, and the global load balancer may select a node closest to the terminal from a plurality of external CDN nodes connected, and return an Internet Protocol (IP) address of the external CDN node to the terminal via the core network and the MEC server.

The prior art at least has the following technical problems: under the condition of providing the CDN service for the high-priority terminal, although the edge CDN node connected to the MEC server is closer to the terminal, since the edge CDN node is isolated from the external CDN node, and the global load balancer only grasps information of the external CDN node, the CDN node selected for the high-priority terminal is the external CDN node, which may cause a service access delay to be large.

Disclosure of Invention

The invention provides a method and equipment for selecting CDN nodes, which realize the selection of edge CDN nodes for high-priority users, thereby reducing service access time delay.

In order to achieve the purpose, the invention adopts the following technical scheme:

in a first aspect, the present invention provides a CDN node selection method, where the method may include: the method comprises the steps that a global load balancer receives a DNS request sent by an MEC server and an identifier of a terminal, wherein the terminal is a device for sending the DNS request and the identifier to the MEC server; the global load balancer determines a target external CDN node according to a preset rule and a DNS request, and sends an IP address of the target external CDN node to the MEC server; when the global load balancer determines that the pre-stored high-priority identification set comprises the identification, sending an application message for applying for using the edge CDN node to an MEC server; and the global load balancer receives a response message which is sent by the MEC server and uses the edge CDN node.

In a second aspect, the present invention provides a CDN node selection method, where the method may include: the method comprises the steps that an MEC server receives a DNS request sent by a terminal, and determines the identifier of the terminal according to the DNS request; the MEC server sends a DNS request and an identification to a global load balancer corresponding to the DNS request; the MEC server receives the IP address of the target external CDN node sent by the global load balancer and sends the IP address of the target external CDN node to the terminal; the MEC server receives a data request sent by a terminal; the method comprises the steps that when an MEC server determines that an application message sent by a global load balancer is received, whether a target edge CDN node exists in an edge CDN node set or not is judged, the target edge CDN node stores requested data, the edge CDN node in the edge CDN node set is connected with the MEC server, and the application message is a message sent to the MEC server by the global load balancer when a terminal is determined to be a high-priority user according to an identifier; and if the target edge CDN node exists, the MEC server sends the IP address of the target edge CDN node to the terminal and sends a response message using the edge CDN node to the global load balancer.

In a third aspect, the present invention provides a global load balancer, which may include: the device comprises a receiving unit, a determining unit and a sending unit. The receiving unit is used for receiving the DNS request and the identifier of the terminal sent by the MEC server, and the terminal is a device for sending the DNS request and the identifier to the MEC server. And the determining unit is used for determining the target external CDN node according to the preset rule and the DNS request. A sending unit, configured to send an IP address of a target external CDN node to the MEC server; and when the pre-stored high-priority identification set comprises the identification, sending an application message for applying for using the edge CDN node to the MEC server. And the receiving unit is further configured to receive a response message sent by the MEC server and using the edge CDN node.

The specific implementation manner may refer to the first aspect or a behavior function of the global load balancer in the CDN node selection method provided by a possible implementation manner of the first aspect.

In a fourth aspect, there is provided an MEC server comprising: the device comprises a receiving unit, a sending unit, a determining unit and a judging unit. The terminal comprises a receiving unit, a sending unit and a receiving unit, wherein the receiving unit is used for receiving a DNS request sent by the terminal; a determining unit, configured to determine an identifier of the terminal according to the DNS request; a sending unit, configured to send the DNS request and the identifier to a global load balancer corresponding to the DNS request; the receiving unit is further used for receiving the IP address of the target external CDN node sent by the global load balancer; the sending unit is also used for sending the IP address of the target external CDN node to the terminal; the receiving unit is also used for receiving a data request sent by the terminal; the determining unit is further configured to determine that an application message sent by the global load balancer is received, where the application message is a message sent by the global load balancer to the MEC server when the terminal is determined to be a high-priority user according to the identifier; the judging unit is used for judging whether a target edge CDN node exists in the edge CDN node set when the application message is determined to be received, the target edge CDN node stores the requested data, and the edge CDN node in the edge CDN node set is connected with the MEC server; and the sending unit is further configured to send the IP address of the target edge CDN node to the terminal if the IP address exists, and send a response message using the edge CDN node to the global load balancer.

The specific implementation manner may refer to the second aspect or a behavior function of the MEC server in the CDN node selection method provided by a possible implementation manner of the second aspect.

In a fifth aspect, there is provided an MEC server comprising: at least one processor, a memory, a communication interface, and a communication bus. The processor is connected to the memory and the communication interface through a communication bus, the memory is used for storing computer execution instructions, and when the MEC server runs, the processor executes the computer execution instructions stored in the memory, so that the MEC server executes the CDN node selection method according to the second aspect or any one of possible implementation manners of the second aspect.

In a sixth aspect, a global load balancer is provided, comprising: at least one processor, a memory, a communication interface, and a communication bus. The processor is connected with the memory and the communication interface through a communication bus, the memory is used for storing computer execution instructions, and when the global load balancer runs, the processor executes the computer execution instructions stored in the memory, so that the global load balancer executes the method for selecting the CDN node according to the first aspect.

A seventh aspect provides a computer storage medium having stored thereon computer-executable instructions that, when executed on an MEC server, cause the MEC server to perform a method for CDN node selection as defined in the second aspect or any one of the possible implementations of the second aspect.

In an eighth aspect, a global load balancer is provided, on which computer executable instructions are stored, which, when run on the global load balancer, cause the global load balancer to perform the method for selecting a CDN node as in the first aspect.

The method for selecting the CDN node comprises the steps that after a global load balancer receives a DNS request and an identifier of a terminal, a target external CDN node is determined, an IP address of the target external CDN node is sent to an MEC server, when a prestored high-priority identifier set comprises the identifier of the terminal, an application message for using the edge CDN node is sent to the MEC server, the MEC server can return the IP address of the target external CDN node to the terminal, when a data request is received, the target edge CDN node is determined to store data of a user request, the IP address of the target edge CDN node is sent to the terminal, and a response message for using the edge CDN node is sent to the global load balancer. Therefore, the terminal is determined to be a high-priority user through the global load balancer, the edge CDN node storing the data requested by the user is determined through the MEC server, the edge CDN node with a short distance is selected for the high-priority user, and service access time delay is reduced.

Drawings

Fig. 1 is a simplified schematic diagram of a system architecture to which an embodiment of the present invention may be applied;

fig. 2 is a schematic composition diagram of an MEC server according to an embodiment of the present invention;

fig. 3 is a schematic diagram illustrating a global load balancer according to an embodiment of the present invention;

fig. 4 is a flowchart of a CDN node selection method according to an embodiment of the present invention;

fig. 5 is a schematic composition diagram of another MEC server according to an embodiment of the present invention;

fig. 6 is a schematic composition diagram of another MEC server according to an embodiment of the present invention;

fig. 7 is a schematic diagram illustrating a global load balancer according to another embodiment of the present invention;

fig. 8 is a schematic composition diagram of another global load balancer according to an embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. 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 invention.

Fig. 1 is a simplified schematic diagram of a system architecture to which an embodiment of the present invention may be applied, as shown in fig. 1, the system architecture may include: a terminal 11, an MEC server 12, a global load balancer 13, at least one edge CDN node 14, at least one external CDN node 15, a base station 16, and a mobile core network 17.

Wherein, the terminal 11 sends a DNS request to the MEC server 12 via the base station 16, the MEC server 12 determines the identity of the terminal 11 according to the received DNS request, and sends the DNS request and the identity of the terminal 11 to the global load balancer 13. The global load balancer 13 determines a target external CDN node from at least one external CDN node 15, sends an IP address of the target external CDN node to the MEC server 12, and sends an application message for applying for using an edge CDN node to the MEC server 12 when it is determined that the terminal 11 is a high-priority user. The MEC server 12 sends an IP address of a target external CDN node to the terminal 11 through the base station 16, the terminal 11 sends a data request to the MEC server 12 through the base station 16 according to the address, and when the MEC server 12 determines that an application message is received and it is determined that a target edge CDN node storing data requested by the terminal 11 exists in at least one edge CDN node 14, the IP address of the target edge CDN node is returned to the terminal 11 through the base station 16, and a response message using the edge CDN node is sent to the global load balancer 13.

The terminal 11 may be a mobile terminal in a specific implementation, such as a mobile phone and a computer with a mobile terminal, or a portable, pocket, handheld, computer-embedded or vehicle-mounted mobile device, for example, a Personal Communication Service (PCS) phone, a cordless phone, a mobile phone, or the like.

The MEC server 12, connected to at least one edge CDN node 14, may provide rich mobile network services, and in the CDN services, the MEC server 12 may implement a simpler CDN service topology.

The global load balancer 13 is connected to at least one external CDN node 15, grasps information of the at least one external CDN node 15, and corresponds to the DNS request transmitted by the terminal 11.

At least one edge CDN node 14 is an operator's own CDN node, and is isolated from at least one external CDN node 15.

At least one external CDN node 15 is a CDN node belonging to an external CDN service provider.

And the mobile core network 17 is configured to receive the data request sent by the MEC server 12, and send the data request to a target external CDN node.

Fig. 2 is a schematic composition diagram of an MEC server according to an embodiment of the present invention, and as shown in fig. 2, the MEC server may include: at least one processor 21, a memory 22, a communication interface 23, and a communication bus 24.

The following describes each component of the MEC server in detail with reference to fig. 2:

the processor 21 is a control center of the MEC server, and may be a single processor or a collective term for a plurality of processing elements. For example, the processor 21 is a CPU, and may be an Application Specific Integrated Circuit (ASIC), or one or more integrated circuits configured to implement embodiments of the present invention, such as: one or more Digital Signal Processors (DSPs), or one or more Field Programmable Gate Arrays (FPGAs).

In particular implementations, processor 21 may include one or more CPUs such as CPU0 and CPU1 shown in fig. 2 as one example. Also, as an embodiment, the MEC server may include a plurality of processors, such as the processor 21 and the processor 25 shown in fig. 2. Each of these processors may be a Single-core processor (Single-CPU) or a Multi-core processor (Multi-CPU). A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (e.g., computer program instructions).

The Memory 22 may be a Read-Only Memory (ROM) or other type of static storage device that can store static information and instructions, a Random Access Memory (RAM) or other type of dynamic storage device that can store information and instructions, an electrically erasable Programmable Read-Only Memory (EEPROM), a Compact Disc Read-Only Memory (CD-ROM) or other optical Disc storage, optical Disc storage (including Compact Disc, laser Disc, optical Disc, digital versatile Disc, blu-ray Disc, etc.), a magnetic Disc storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to such. The memory 22 may be self-contained and coupled to the processor 21 via a communication bus 24. The memory 22 may also be integrated with the processor 21.

In a particular implementation, the memory 22 is used for storing data in the present invention and software programs for implementing the present invention. The processor 21 may perform various functions of the MEC server by running or executing software programs stored in the memory 22 and calling up data stored in the memory 22.

The communication interface 23 is a device such as any transceiver, and is used for communicating with other devices or communication Networks, such as a Radio Access Network (RAN), a Wireless Local Area Network (WLAN), a global load balancer, and the like. The communication interface 23 may include a receiving unit implementing a receiving function and a transmitting unit implementing a transmitting function.

The communication bus 24 may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, an Extended ISA (enhanced Industry Standard Architecture) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 2, but it is not intended that there be only one bus or one type of bus.

Fig. 3 is a schematic diagram illustrating a global load balancer provided in an embodiment of the present invention, and as shown in fig. 3, the global load balancer may include: at least one processor 31, a memory 32, a communication interface 33, and a communication bus 34.

The following describes each component of the global load balancer in detail with reference to fig. 3:

the processor 31 is a control center of the global load balancer, and may be a single processor or a collective term for multiple processing elements. For example, the processor 21 is a CPU, may be an ASIC, or may be one or more integrated circuits configured to implement embodiments of the present invention, such as: one or more DSPs, or one or more FPGAs.

In particular implementations, processor 31 may include one or more CPUs such as CPU0 and CPU1 shown in fig. 3 as one example. Also, as an embodiment, the global load balancer may include a plurality of processors, such as the processor 31 and the processor 35 shown in fig. 3. Each of these processors may be a single core processor or a multi-core processor. A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (e.g., computer program instructions).

Memory 32 may be, but is not limited to, ROM or other type of static storage device that can store static information and instructions, RAM or other type of dynamic storage device that can store information and instructions, EEPROM, CD-ROM or other optical disk storage, optical disk storage (including compact disk, laser disk, optical disk, digital versatile disk, blu-ray disk, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. The memory 32 may be self-contained and coupled to the processor 31 via a communication bus 34. The memory 32 may also be integrated with the processor 31.

In a particular implementation, the memory 32 is used for storing data and software programs for implementing the present invention. Processor 31 may perform various functions of the global load balancer by running or executing software programs stored in memory 32, as well as invoking data stored in memory 32.

The communication interface 33, using any transceiver or like device, is used for communication with other equipment or communication networks, such as RAN, WLAN, MEC server, etc. The communication interface 33 may include a receiving unit implementing a receiving function and a transmitting unit implementing a transmitting function.

The communication bus 34 may be an ISA bus, a PCI bus, an EISA bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 3, but this does not mean only one bus or one type of bus.

In order to realize selection of an edge CDN node for a high-priority user and reduce service access delay, an embodiment of the present invention provides a CDN node selection method, where as shown in fig. 4, the method may include:

401. the terminal sends a DNS request to the MEC server.

When a user needs to obtain data through the terminal, input operation can be performed on the terminal, so that the terminal can send a DNS request to the MEC server through the base station according to the input of the user.

402. And the MEC server receives the DNS request sent by the terminal and determines the identifier of the terminal according to the DNS request.

After receiving the DNS request sent by the terminal, the MEC server may identify the DNS request, determine that the DNS request is sent by the terminal, and thereby obtain the identifier of the terminal. The identifier of the terminal is used to uniquely identify itself, and may be, for example, an International Mobile Subscriber Identity (IMSI), an International Mobile Equipment Identity (IMEI), or a group organization pre-agreed by the MEC server and the global load balancer, such as an identifier of a member user.

403. The MEC server sends a DNS request and identification to the global load balancer.

After receiving the DNS request and determining the identifier of the terminal, the MEC server may forward the DNS request and the identifier to a global load balancer corresponding to the DNS request.

404. And the global load balancer receives the DNS request sent by the MEC server and the identification of the terminal.

405. And the global load balancer sends an application message to the MEC server when determining that the pre-stored high-priority identification set comprises the identification of the terminal.

After receiving the identifier of the terminal sent by the MEC server, the global load balancer may determine whether the terminal is a high-priority user according to the identifier of the terminal. Specifically, the global load balancer may determine whether the pre-stored high-priority identifier set includes an identifier of the terminal, and if the identifier includes the identifier of the terminal, the terminal is indicated as a high-priority user, and at this time, an application message for applying for using the edge CDN node may be sent to the MEC server. If not, it indicates that the terminal is not a high-priority user, and at this time, an external CDN node may be selected for the terminal, so that the terminal requests data from the external CDN node. Therefore, differentiated CDN service can be provided for users with different levels by judging whether the terminal is a high-priority user or not and selecting a CDN node for the terminal according to a judgment result.

406. And the global load balancer determines a target external CDN node according to a preset rule and a DNS request.

After receiving the DNS request sent by the MEC server, the global load balancer may determine the target external CDN node according to a preset rule and the DNS request. Specifically, the global load balancer may identify a DNS request, determine that the DNS request is sent by an MEC server, thereby obtain an IP address of the MEC server, obtain an IP address of a mobile core network egress network element corresponding to the IP address of the MEC server according to a pre-stored correspondence, and determine, as a target external CDN node, an external CDN node closest to a logical distance of the mobile core network egress network element according to the IP address of the mobile core network egress network element and an IP address of each external CDN node connected to the global load balancer.

It should be noted that the correspondence relationship is a correspondence relationship between an IP address of the MEC server and an IP address of an egress network element of the mobile core network. The egress Network element of the mobile core Network refers to a Network element, such as a packet Data Gateway (P-GW), where the mobile core Network is connected to the internet.

407. The global load balancer sends the IP address of the target external CDN node to the MEC server.

408. And the MEC server receives the IP address of the target external CDN node sent by the global load balancer.

409. And the MEC server sends the IP address of the target external CDN node to the terminal.

The MEC server may send the IP address of the target external CDN node to the terminal, as a response to the terminal sending the DNS request.

410. And the terminal receives the IP address of the target external CDN node sent by the MEC server.

411. The terminal sends a data request to the MEC server.

After receiving the IP address of the target external CDN node sent by the MEC server, the terminal may send a data request to the MEC server according to the IP address to request data required by the user.

412. The MEC server receives a data request sent by a terminal, and judges whether a target edge CDN node exists in an edge CDN node set or not when determining that an application message sent by a global load balancer is received, wherein the target edge CDN node stores the requested data.

And the edge CDN nodes in the edge CDN node set are connected with the MEC server.

After receiving a data request sent by a terminal, the MEC server may determine whether an application message sent by the global load balancer is received for applying for using the edge CDN node. If it is determined that the application message is not received, it indicates that the terminal is not a high-priority user, and it may obtain data from the target external CDN node determined in step 406, at this time, the MEC server may send the data request to the mobile core network, so that the mobile core network sends the data request to the target external CDN node according to the IP address of the target external CDN node included in the data request, and the target external CDN node may return data to the terminal via the mobile core network, the MEC server, and the base station. If the application message is determined to be received, it indicates that the terminal is a high-priority user, and an edge CDN node needs to be selected to provide CDN services, and at this time, the MEC server may determine whether the edge CDN node can provide CDN services by determining whether a target edge CDN node exists in the edge CDN node set, where the target edge CDN node stores data requested by the user. If it is determined that each edge CDN node in the edge CDN node set does not store data requested by the user, it indicates that the edge CDN node cannot provide CDN services, and at this time, the MEC server may send a data request to the mobile core network, so that the mobile core network sends the data request to a target external CDN node. If it is determined that the target edge CDN node exists, indicating that the edge CDN node can provide CDN services, the following steps 413-416 may be performed:

413. and if the target edge CDN node exists in the edge CDN node set, the MEC server sends the IP address of the target edge CDN node to the terminal.

The MEC server may send, to the terminal, an IP address of the target edge CDN node when it is determined that the target edge CDN node exists in the edge CDN node set, as a response to the terminal sending the data request.

414. And the terminal receives the IP address of the target edge CDN node sent by the MEC server.

After receiving the IP address of the target edge CDN node sent by the MEC server, the terminal may send a data request to the MEC server again, so that the MEC server sends the data request to the target edge CDN node.

415. The MEC server sends a response message using the edge CDN node to the global load balancer.

After determining that the target edge CDN node exists, the MEC server may send a response message using the edge CDN node to the global load balancer, and use the response message as a response for the global load balancer to send the application message.

416. And the global load balancer receives a response message which is sent by the MEC server and uses the edge CDN node.

The above description mainly introduces the scheme provided by the embodiment of the present invention from the perspective of interaction of various devices. It is understood that each device, such as MEC server, global load balancer, for implementing the above functions, includes corresponding hardware structures and/or software modules for performing each function. Those of skill in the art will readily appreciate that the present invention can be implemented in hardware or a combination of hardware and computer software, in conjunction with the exemplary algorithm steps described in connection with the embodiments disclosed herein. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

In the embodiment of the present invention, functional modules of the MEC server and the global load balancer may be divided according to the above method, for example, each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. It should be noted that, the division of the modules in the embodiment of the present invention is schematic, and is only a logic function division, and there may be another division manner in actual implementation.

In the case of dividing each functional module by corresponding functions, fig. 5 shows another possible composition diagram of the MEC server involved in the foregoing embodiment, as shown in fig. 5, the MEC server may include: a receiving unit 51, a transmitting unit 52, a determining unit 53, and a judging unit 54.

The receiving unit 51 is configured to support the MEC server to execute the DNS request sent by the receiving terminal in step 402, the data request sent by the receiving terminal in steps 408 and 412 in the CDN node selection method shown in fig. 4.

A sending unit 52, configured to support the MEC server to execute step 403, step 409, step 413, and step 415 in the CDN node selection method shown in fig. 4.

The determining unit 53 is configured to support the MEC server to execute the identifier of the terminal determined in step 402 in the CDN node selection method shown in fig. 4, and determine that an application message sent by the global load balancer is received.

A determining unit 54, configured to support the MEC server to execute the method for selecting a CDN node shown in fig. 4, where the step 412 is to determine whether a target edge CDN node exists in the edge CDN node set, and the target edge CDN node stores the requested data.

It should be noted that all relevant contents of each step related to the above method embodiment may be referred to the functional description of the corresponding functional module, and are not described herein again.

The MEC server provided by the embodiment of the invention is used for executing the selection method of the CDN node, so that the same effect as the selection method of the CDN node can be achieved.

In case of an integrated unit, fig. 6 shows another possible composition diagram of the MEC server involved in the above embodiments. As shown in fig. 6, the MEC server includes: a processing module 61, a communication module 62 and a storage module 63.

The processing module 61 is configured to control and manage actions of the MEC server, for example, the processing module 61 is configured to support the MEC server to execute the determining of the identifier of the terminal in step 402 in fig. 4, the determining whether a target edge CDN node exists in the edge CDN node set in step 412, where the target edge CDN node stores requested data, and/or other processes used in the technology described herein. The communication module 62 is used to support the communication of the MEC server with other network entities, such as a global load balancer. For example, the communication module 62 is configured to support the MEC server to execute the DNS request sent by the receiving terminal in step 402, the data request sent by the receiving terminal in steps 403, 408, 409, and 412, 413, and 415 in fig. 4. And the storage module 63 is used for storing the program codes and data of the MEC server.

The processing module 61 may be the processor in fig. 2. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. A processor may also be a combination of computing functions, e.g., comprising one or more microprocessors, a DSP and a microprocessor, or the like. The communication module 62 may be the communication interface in fig. 2. The storage module 63 may be the memory of fig. 2.

In the case of dividing each functional module by corresponding functions, fig. 7 shows another possible composition diagram of the global load balancer involved in the foregoing embodiments, as shown in fig. 7, the global load balancer may include: a receiving unit 71, a determining unit 72 and a transmitting unit 73.

The receiving unit 71 is configured to support the global load balancer to execute step 404 and step 416 in the CDN node selection method shown in fig. 4.

The determining unit 72 is configured to support the global load balancer to perform step 406 in the CDN node selection method shown in fig. 4.

The sending unit 73 is configured to support the global load balancer to execute steps 405 and 407 in the CDN node selection method shown in fig. 4.

The global load balancer provided by the embodiment of the invention is used for executing the selection method of the CDN node, so that the effect same as that of the selection method of the CDN node can be achieved.

In case of integrated units, fig. 8 shows another possible composition diagram of the global load balancer involved in the above embodiments. As shown in fig. 8, the global load balancer includes: a processing module 81, a communication module 82 and a storage module 83.

Processing module 81 is used to control and manage the actions of the global load balancer, e.g., processing module 81 is used to support the global load balancer to perform step 406 in fig. 4, and/or other processes for the techniques described herein. The communication module 82 is used to support the communication of the global load balancer with other network entities, such as MEC servers. For example, the communication module 82 is configured to support the global load balancer to perform steps 404, 405, 407, and 416 in fig. 4. A storage module 83 for storing program codes and data of the global load balancer.

The processing module 81 may be the processor in fig. 3. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. A processor may also be a combination of computing functions, e.g., comprising one or more microprocessors, a DSP and a microprocessor, or the like. The communication module 82 may be the communication interface of fig. 3. The storage module 83 may be the memory of fig. 3.

Through the above description of the embodiments, it is clear to those skilled in the art that, for convenience and simplicity of description, the foregoing division of the functional modules is merely used as an example, and in practical applications, the above function distribution may be completed by different functional modules according to needs, that is, the internal structure of the device may be divided into different functional modules to complete all or part of the above described functions.

In the embodiments provided in the present invention, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described device embodiments are merely illustrative, and for example, the division of the modules or units is only one logical functional division, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or may be integrated into another device, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may be one physical unit or a plurality of physical units, that is, may be located in one place, or may be distributed in a plurality of different places. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a 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 stand-alone product, may be stored in a readable storage medium. Based on such understanding, the technical solution of the embodiments of the present invention may be essentially or partially contributed to by the prior art, or all or part of the technical solution may be embodied in the form of a software product, where the software product is stored in a storage medium and includes several instructions to enable a device (which may be a single chip, a chip, or the like) or a processor (processor) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: various media capable of storing program codes, such as a U disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.

The above description is only an embodiment of the present invention, but the scope of the present invention is not limited thereto, and any changes or substitutions within the technical scope of the present invention are intended to be covered by the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the appended claims.

Claims

1. A method for selecting CDN nodes of a content delivery network is characterized by comprising the following steps:

a global load balancer receives a Domain Name Service (DNS) request and a terminal identifier sent by a Mobile Edge Computing (MEC) server, wherein the terminal is a device for sending the DNS request and the identifier to the MEC server;

the global load balancer determines a target external CDN node according to a preset rule and the DNS request, and sends an internet protocol IP address of the target external CDN node to the MEC server;

when the global load balancer determines that a pre-stored high-priority identification set comprises the identification, sending an application message for applying for using an edge CDN node to the MEC server; the application message is used for requesting the MEC server to judge whether a target edge CDN node exists in an edge CDN node set or not, and if the target edge CDN node exists, sending an IP address of the target edge CDN node to the terminal; the target edge CDN node stores requested data, and edge CDN nodes in the edge CDN node set are connected with the MEC server;

and the global load balancer receives a response message which is sent by the MEC server and uses the edge CDN node.

2. The CDN node selection method of claim 1, wherein the global load balancer determines a target external CDN node according to a preset rule and the DNS request, comprising:

the global load balancer identifies the DNS request and obtains an IP address of the MEC server;

the global load balancer acquires the IP address of the mobile core network outlet network element corresponding to the IP address of the MEC server according to a pre-stored corresponding relationship, wherein the corresponding relationship comprises the IP address of the MEC server and the IP address of the mobile core network outlet network element;

and the global load balancer determines an external CDN node closest to the mobile core network outlet network element logical distance as the target external CDN node according to the IP address of the mobile core network outlet network element.

3. A method for selecting CDN nodes of a content delivery network is characterized by comprising the following steps:

a mobile edge computing MEC server receives a Domain Name Service (DNS) request sent by a terminal and determines an identifier of the terminal according to the DNS request;

the MEC server sends the DNS request and the identification to a global load balancer corresponding to the DNS request;

the MEC server receives an Internet Protocol (IP) address of a target external CDN node sent by the global load balancer and sends the IP address of the target external CDN node to the terminal;

the MEC server receives a data request sent by the terminal;

when determining to receive an application message sent by the global load balancer, the MEC server judges whether a target edge CDN node exists in an edge CDN node set, the target edge CDN node stores requested data, the edge CDN node in the edge CDN node set is connected with the MEC server, and the application message is a message sent to the MEC server by the global load balancer when determining that the terminal is a high-priority user according to the identifier;

and if the target edge CDN node exists, the MEC server sends the IP address of the target edge CDN node to the terminal and sends a response message using the edge CDN node to the global load balancer.

4. The CDN node selection method of claim 3 further comprising:

if each edge CDN node in the edge CDN node set does not store the requested data, the MEC server sends the data request to a mobile core network, so that the mobile core network sends the data request to the target external CDN node.

5. The CDN node selection method of claim 4 further comprising:

and the MEC server sends the data request to the mobile core network when determining that the application message is not received.

6. A global load balancer, the global load balancer comprising: a receiving unit, a determining unit and a transmitting unit;

the receiving unit is configured to receive a domain name service DNS request and an identifier of a terminal sent by a mobile edge computing MEC server, where the terminal is a device that sends the DNS request and the identifier to the MEC server;

the determining unit is used for determining target external content delivery network CDN nodes according to preset rules and the DNS request;

the sending unit is configured to send an internet protocol IP address of the target external CDN node to the MEC server; when the pre-stored high-priority identification set comprises the identification, sending an application message for applying for using the edge CDN node to the MEC server; the application message is used for requesting the MEC server to judge whether a target edge CDN node exists in an edge CDN node set or not, and if the target edge CDN node exists, sending an IP address of the target edge CDN node to the terminal; the target edge CDN node stores requested data, and edge CDN nodes in the edge CDN node set are connected with the MEC server;

the receiving unit is further configured to receive a response message sent by the MEC server and using the edge CDN node.

7. The global load balancer of claim 6, wherein the determining unit is specifically configured to:

identifying the DNS request, and obtaining an IP address of the MEC server;

acquiring an IP address of an outlet network element of the mobile core network corresponding to the IP address of the MEC server according to a pre-stored corresponding relationship, wherein the corresponding relationship comprises the IP address of the MEC server and the IP address of the outlet network element of the mobile core network;

and determining an external CDN node closest to the mobile core network outlet network element in logical distance as the target external CDN node according to the IP address of the mobile core network outlet network element.

8. A mobile edge computing, MEC, server, the MEC server comprising: the device comprises a receiving unit, a sending unit, a determining unit and a judging unit;

the receiving unit is used for receiving a Domain Name Service (DNS) request sent by a terminal;

the determining unit is used for determining the identifier of the terminal according to the DNS request;

the sending unit is configured to send the DNS request and the identifier to a global load balancer corresponding to the DNS request;

the receiving unit is further configured to receive an internet protocol IP address of a target external content delivery network CDN node sent by the global load balancer;

the sending unit is further configured to send the IP address of the target external CDN node to the terminal;

the receiving unit is further configured to receive a data request sent by the terminal;

the determining unit is further configured to determine that an application message sent by the global load balancer is received, where the application message is a message sent by the global load balancer to the MEC server when the terminal is determined to be a high-priority user according to the identifier;

the judging unit is configured to judge whether a target edge CDN node exists in an edge CDN node set when the application message is determined to be received, where the target edge CDN node stores requested data, and an edge CDN node in the edge CDN node set is connected to the MEC server;

the sending unit is further configured to send the IP address of the target edge CDN node to the terminal and send a response message using the edge CDN node to the global load balancer if the IP address exists.

9. The MEC server of claim 8,

the sending unit is further configured to send the data request to a mobile core network if each edge CDN node in the edge CDN node set does not store requested data, so that the mobile core network sends the data request to the target external CDN node.

10. The MEC server of claim 9,

the sending unit is further configured to send the data request to the mobile core network when it is determined that the application message is not received.

11. A mobile edge computing, MEC, server, the MEC server comprising: a processor, a memory, a communication interface, and a communication bus;

the processor is connected to the memory and the communication interface through the communication bus, the memory is used for storing computer execution instructions, and when the MEC server runs, the processor executes the computer execution instructions stored in the memory, so that the MEC server executes the CDN node selection method according to any one of claims 3 to 5.

12. A global load balancer, the global load balancer comprising: a processor, a memory, a communication interface, and a communication bus;

the processor is connected to the memory and the communication interface through the communication bus, the memory is used for storing computer-executable instructions, and when the global load balancer runs, the processor executes the computer-executable instructions stored in the memory, so that the global load balancer executes the selection method of the CDN node according to claim 1 or 2.

13. A computer storage medium comprising computer executable instructions that, when run on a mobile edge computing, MEC, server, cause the MEC server to perform the CDN node selection method of any one of claims 3-5.

14. A computer storage medium comprising computer-executable instructions that, when run on a global load balancer, cause the global load balancer to perform the CDN node selection method of claim 1 or 2.