CN110392069B - CDN service scheduling processing method and CDN server - Google Patents

CDN service scheduling processing method and CDN server Download PDF

Info

Publication number
CN110392069B
CN110392069B CN201810346347.XA CN201810346347A CN110392069B CN 110392069 B CN110392069 B CN 110392069B CN 201810346347 A CN201810346347 A CN 201810346347A CN 110392069 B CN110392069 B CN 110392069B
Authority
CN
China
Prior art keywords
parameter
cdn server
response message
url
cdn
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201810346347.XA
Other languages
Chinese (zh)
Other versions
CN110392069A (en
Inventor
张毅
李从娟
李晋
李峰
韩磊
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN201810346347.XA priority Critical patent/CN110392069B/en
Priority to PCT/CN2019/080178 priority patent/WO2019201072A1/en
Publication of CN110392069A publication Critical patent/CN110392069A/en
Application granted granted Critical
Publication of CN110392069B publication Critical patent/CN110392069B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources

Abstract

The invention discloses a CDN service scheduling processing method, which comprises the following steps: after receiving a URL sent by user equipment, analyzing the URL to obtain parameters of the URL; when a first parameter exists in the parameters of the URL, sending a parameter conversion request to a second CDN server to request to convert the first parameter into a second parameter; receiving a first response message sent by the second CDN server and responding to the parameter conversion request, wherein the first response message comprises the second parameter; and acquiring the content requested to be acquired by the user equipment according to the second parameter and the parameter which can be identified by the first CDN server in the parameters of the URL. The embodiment of the invention realizes the universality and the universality of the locally provided service, and improves the access speed of the user because the redirection and the forwarding of the service are not needed during the service processing.

Description

CDN service scheduling processing method and CDN server
Technical Field
The invention relates to the field of internet, in particular to a CDN service scheduling processing method and a CDN server.
Background
A Content Delivery Network (CDN) is an overlay network superimposed on an IP network, and caches content on a node close to a user network location, and optimizes a transmission path from the content to a user to avoid network congestion, thereby achieving fast acquisition and access of the content.
When the user equipment accesses the website to request to acquire the content, the user equipment acquires the IP address corresponding to the website domain name. When the network domain name is delivered to a CDN server for service hosting, the IP address corresponding to the website domain name points to a CDN scheduling system. The CDN scheduling system sends the IP address of a CDN server for providing service hosting for the website to the user equipment in a redirection mode. The user sends a Uniform Resource Locator (URL) to the CDN server according to the IP address of the CDN server, and requests to acquire content corresponding to the URL. And the CDN server acquires corresponding content according to the received URL and sends the content corresponding to the URL to the user equipment. Since the URL parameters are very freely specified, and there is no uniform specification requirement for the parameter names and parameter values, the actually used URL parameters are diversified due to different implementation methods of Content Providers (CPs), that is, the parameters in the URL are greatly different due to different CPs. Therefore, when the CDN server receives and analyzes the URL parameter, there is a content corresponding to the URL cached in the CDN server, and since the CDN server cannot identify the parameter of the URL, the content and the operation requested by the user equipment cannot be determined.
In the prior art, a CDN server has an adaptation scheme stored in a configuration file form, where the adaptation scheme is a relationship table between parameters in a URL and content and operation. And the CDN server receives and analyzes the parameters in the URL and acquires the content corresponding to the URL according to the adaptive scheme. The scheme solves the problem that the CDN server cannot acquire the content corresponding to the URL cached in the CDN server because the URL parameter cannot be identified. However, due to the fact that there are many adaptive recipes, the specific implementation of the content needs to be understood in depth, and the adaptive scheme needs to be updated according to the change of the implementation method, which results in the need to understand and become familiar with the content during the business processing, and the need of providing general business functions cannot be provided.
Disclosure of Invention
The embodiment of the invention provides a CDN service scheduling processing method and a CDN server, which realize the universality and universality of locally provided services, and improve the access speed of users because the redirection and forwarding of the services are not required during service processing.
In a first aspect, an embodiment of the present invention provides a CDN service scheduling processing method, including:
after receiving a Uniform Resource Locator (URL) sent by user equipment, analyzing the URL to obtain parameters of the URL;
when a first parameter exists in the parameters of the URL, sending a parameter conversion request to a second CDN server to request to convert the first parameter into a second parameter; the parameter conversion request comprises the first parameter, the first parameter is a parameter which cannot be identified by a first CDN server in the parameters of the URL, and the second parameter is a parameter which can be identified by the first CDN server;
receiving a first response message sent by the second CDN server and responding to the parameter conversion request, wherein the first response message is used for indicating that the parameter conversion is successful and comprises the second parameter;
and acquiring target content according to the second parameter and the parameter which can be identified by the first CDN server in the parameters of the URL, wherein the target content is the content requested to be acquired by the user equipment.
In a possible embodiment, the parameter conversion request is a hypertext transfer protocol HTTP request command, and the first response message is an HTTP response message.
In a possible embodiment, after the obtaining the target content, the method further includes:
and sending the target content to the user equipment.
In a possible embodiment, after sending the parameter conversion request to the second CDN server, the method further includes:
and receiving a second response message which is sent by the second CDN server and used for responding to the parameter conversion request, wherein the second response message is used for indicating that the parameter conversion is failed, and the second response message is an HTTP response message.
In a possible embodiment, after receiving a second response message sent by the second CDN server in response to the parameter conversion request, the method further includes:
and sending a feedback message to the user equipment, wherein the feedback message is used for indicating that the target content cannot be acquired.
In a second aspect, an embodiment of the present invention provides a CDN service scheduling processing method, including:
receiving a parameter conversion request sent by a first CDN server, wherein the parameter conversion request is used for indicating that a first parameter is converted into a second parameter; the parameter conversion request comprises the first parameter, the first parameter is a parameter which cannot be identified by the first CDN server in parameters of a Uniform Resource Locator (URL), and the second parameter is a parameter which can be identified by the first CDN server;
converting the first parameter according to a preset mode to obtain a second parameter;
sending a first response message for responding to the parameter conversion request to the first CDN server, wherein the first response message comprises the second parameter.
In a possible embodiment, the converting the first parameter according to a preset manner to obtain the second parameter includes:
and querying a parameter corresponding relation table according to the first parameter to obtain the second parameter, wherein the parameter corresponding relation table comprises a corresponding relation between the first parameter and the second parameter.
In a possible embodiment, the parameter conversion request is a HTTP request command, and the first response message is a first HTTP response message.
In a possible embodiment, the method further comprises:
when the second parameter is not obtained by querying the parameter correspondence table according to the first parameter, sending a second response message for responding to the parameter conversion request to the first CDN server, wherein the second response message is used for indicating that the parameter conversion fails; the second response message is an HTTP response message.
In a third aspect, an embodiment of the present invention provides a CDN server, including:
the device comprises a receiving unit, a processing unit and a processing unit, wherein the receiving unit is used for analyzing a Uniform Resource Locator (URL) after receiving the URL sent by user equipment to obtain parameters of the URL;
the sending unit is used for sending a parameter conversion request to a second CDN server to request to convert the first parameter into a second parameter when the first parameter exists in the parameters of the URL; the parameter conversion request comprises the first parameter, the first parameter is a parameter which cannot be identified by a first CDN server in the parameters of the URL, and the second parameter is a parameter which can be identified by the first CDN server;
the receiving unit is further configured to receive a first response message sent by the second CDN server and used for responding to the parameter conversion request, where the first response message is used to indicate that parameter conversion is successful, and the first response message includes the second parameter;
and an obtaining unit, configured to obtain target content according to a parameter that can be identified by the first CDN server in the second parameter and the parameter of the URL, where the target content is content requested to be obtained by the user equipment.
In a possible embodiment, the parameter conversion request is a hypertext transfer protocol HTTP request command, and the first response message is an HTTP response message.
In a possible embodiment, the sending unit is further configured to:
and after the acquisition unit acquires the target content, transmitting the target content to the user equipment.
In a possible embodiment, the receiving unit is further configured to:
after the sending unit sends a parameter conversion request to a second CDN server, receiving a second response message sent by the second CDN server and responding to the parameter conversion request, wherein the second response message is used for indicating that parameter conversion fails, and the second response message is an HTTP response message.
In a possible embodiment, the sending unit is further configured to:
and after the receiving unit receives a second response message which is sent by the second CDN server and responds to the parameter conversion request, sending a feedback message to the user equipment, wherein the feedback message is used for indicating that the target content cannot be obtained.
In a fourth aspect, an embodiment of the present invention provides a CDN server, including
The receiving unit is used for receiving a parameter conversion request sent by a first CDN server, wherein the parameter conversion request is used for indicating that a first parameter is converted into a second parameter; the parameter conversion request comprises the first parameter, the first parameter is a parameter which cannot be identified by the first CDN server in parameters of a Uniform Resource Locator (URL), and the second parameter is a parameter which can be identified by the first CDN server;
the conversion unit is used for converting the first parameter according to a preset mode to obtain the second parameter;
a sending unit, configured to send, to the first CDN server, a first response message used for responding to the parameter conversion request, where the first response message includes the second parameter.
In a possible embodiment, the conversion unit is specifically configured to:
and querying a parameter corresponding relation table according to the first parameter to obtain the second parameter, wherein the parameter corresponding relation table comprises a corresponding relation between the first parameter and the second parameter.
In a possible embodiment, the parameter conversion request is a HTTP request command, and the first response message is a first HTTP response message.
In a possible embodiment, the sending unit is further configured to:
when the conversion unit queries the parameter correspondence table according to the first parameter to obtain no second parameter, sending a second response message for responding to the parameter conversion request to the first CDN server, where the second response message is used to indicate that parameter conversion fails; the second response message is an HTTP response message.
In a fifth aspect, an embodiment of the present invention provides a CDN server, including:
a memory storing executable program code;
a processor coupled to the processor;
the processor calls the executable program code stored in the memory to perform all or part of the method according to the first aspect, or to perform all or part of the method according to the second aspect.
In a sixth aspect, the present invention provides a computer-readable storage medium storing a computer program, the computer program comprising program instructions that, when executed by a processor, cause the processor to perform all or part of the method according to the first aspect, or perform all or part of the method according to the second aspect.
It can be seen that, in the scheme of the embodiment of the present invention, when a parameter (i.e., a first parameter) that cannot be identified by the first CDN server exists in the parameters of the URL received by the first CDN server, the parameter that cannot be identified by the first CDN server is sent to the second CDN server. The second CDN server converts the parameter that the first CDN server cannot recognize into a parameter (i.e., a second parameter) that the first CDN server recognizes; and returning the parameter identified by the first CDN server to the first CDN server. The first CDN server obtains content (i.e., target content) requested by the user equipment according to the converted parameters and parameters that can be identified in the URL parameters. The service coordination among the CDNs is realized through the expanded command request, the parameters which cannot be identified in the URL parameters are delivered to other CDN servers (namely, a second CDN server) for process conversion processing, the function that a local CDN server (namely, a first CDN server) provides a universal service is realized, the redirection and forwarding of the service are not needed, and the access speed of a user is improved.
These and other aspects of the invention are apparent from and will be elucidated with reference to the embodiments described hereinafter.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a schematic view of an application scenario of a CDN service scheduling processing method according to an embodiment of the present invention;
fig. 2 is a schematic flowchart of a CDN service scheduling processing method according to an embodiment of the present invention;
fig. 3 is a schematic flowchart of another CDN service scheduling processing method according to an embodiment of the present invention;
fig. 4 is an interactive flowchart of another CDN service scheduling processing method according to an embodiment of the present invention;
FIG. 5 is a flow chart illustrating a specific application provided by an embodiment of the present invention;
fig. 6 is a schematic structural diagram of a CDN server according to an embodiment of the present invention;
fig. 7 is a schematic structural diagram of another CDN server according to an embodiment of the present invention;
fig. 8 is a schematic structural diagram of another CDN server according to an embodiment of the present invention.
Detailed Description
In order to make the technical solutions of the present invention better understood, 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.
Referring to fig. 1, fig. 1 is a schematic view of an application scenario of a CDN service scheduling processing method according to an embodiment of the present invention. As shown in fig. 1, the application scenario includes: user equipment 101, a first CDN server 102, and a second CDN server 103.
Data transmission is performed between the user equipment 101 and the first CDN server 102 in a wired manner or a wireless manner; data transmission is performed between the first CDN server 102 and the second CDN server 103 in a wired manner or a wireless manner. For the sake of representation, only double arrows are shown in fig. 1.
The user device 101 is a device for providing voice and/or data connectivity to a user, and may also be a handheld device or a vehicle-mounted device with a wireless connection function. Common terminal devices include: a mobile phone, a tablet computer, a notebook computer, a palm computer, a Mobile Internet Device (MID), an internet of things device, a wearable device (e.g., a smart watch, a smart bracelet, a pedometer), and the like.
The CDN servers (including the first CDN server 102 and the second CDN server 103) are servers of a layer of intelligent virtual network on the existing internet basis, which is formed by placing node servers throughout the network. The basic idea of the CDN is to avoid bottlenecks and links on the internet that may affect the data transmission speed and stability as much as possible, so that the content transmission is faster and more stable. The CDN system can redirect a request of a user to a service node closest to the user in real time according to the network traffic and comprehensive information such as connection of each node, a load condition, a distance to the user, and response time. The method aims to enable the user to obtain the required content nearby, solve the network congestion condition and improve the response speed of the user for accessing the website.
The user device 101 sends a URL to the first CDN server 102 to request the target content, and the first CDN server 102 receives and parses the parameter in the URL. When the parameter that cannot be identified by the first CDN server exists in the URL, the first CDN server 102 sends the parameter that cannot be identified by the URL to the second CDN server 103 to request for parameter conversion. The second CDN server 103 converts the received parameters, and sends the conversion result to the first CDN server 102. The first CDN server 102 obtains a new URL according to the conversion result, obtains the target content according to the new URL, and sends the target content to the user equipment 101.
Referring to fig. 2, fig. 2 is a schematic flowchart of a CDN service scheduling processing method according to an embodiment of the present invention. As shown in fig. 2, the method includes:
s201, after receiving a Uniform Resource Locator (URL) sent by user equipment, a first CDN server analyzes the URL to obtain parameters of the URL.
It should be noted that the URL is a compact representation of the location and access method of the resource available from the internet, and is an address of a standard resource on the internet. Each file on the internet has a unique URL that contains information indicating the location of the file and how the browser should handle it.
Wherein, the complete format of the URL is as follows: "protocol type [/[ credential information required to access a resource @ ] server address [: port number ] ] [/resource level UNIX file path ] file name [? Query ] [ # fragment ID ] ". Wherein @, [: port number ], [? Query ] and [ # fragment ID ] "both belong to the Option Filler. In [? The query ] field will contain a parameter, in "? The "character is the starting point, each parameter is separated by" & "and the parameter name is separated from the data by" & ".
S202, when the first parameter exists in the parameters of the URL, the first CDN server sends a parameter conversion request to a second CDN server to request to convert the first parameter into a second parameter.
The parameter conversion request comprises the first parameter, the first parameter is a parameter which cannot be identified by a first CDN server in the parameters of the URL, and the second parameter is a parameter which can be identified by the first CDN server. The parameter conversion request is an HTTP request command.
Specifically, the parameter conversion request (i.e., the HTTP request command) is URL _ Transform [ URL parameter ]. The URL _ Transform is used for identifying parameter conversion; the URL parameter is the first parameter, which is a parameter that cannot be identified by the first CDN server.
In a feasible embodiment, the first CDN server preprocesses the first parameter in a manner agreed with the second CDN server to obtain a preprocessed first parameter; and then sending the preprocessed first parameter to the second CDN server in the form of the HTTP request command.
S203, the first CDN server receives a first response message sent by the second CDN server and responding to the parameter conversion request, where the first response message is used to indicate that the parameter conversion is successful, and the first response message includes the second parameter.
Wherein, the first response message is an HTTP response message.
Specifically, the first response message is an HTTP response 200, and the response message is used to identify that the second CDN server successfully converts the first parameter into the second parameter. And the Location field of the header of HTTP response 200 contains the second parameter described above, like Location [ second parameter ].
After receiving the HTTP response 200, the first CDN server extracts the second parameter from the Location field of the header.
S204, the first CDN server obtains target content according to the second parameter and the parameter which can be identified by the first CDN server in the parameters of the URL, wherein the target content is the content which is obtained by the user equipment sending the URL to the first CDN server to request to obtain.
The first CDN server obtains the target content according to the second parameter and a parameter that can be identified by the first CDN server from among the parameters of the URL, and then sends the target content to the user equipment.
In a possible embodiment, the first CDN server receives a second response message sent by the second CDN server to respond to the parameter conversion request, where the second response message is used to indicate that parameter conversion fails.
Wherein, the second response message is an HTTP response message. Specifically, the second response message is HTTP response 400.
Further, when receiving a second response message sent by the second CDN server, the first CDN server sends a feedback message to the user equipment, where the feedback message is used to indicate that the first CDN server cannot obtain the target content.
In a possible embodiment, when receiving the second response message sent by the second CDN server, the first CDN server sends the parameter conversion request to a CDN server other than the second CDN server to request conversion of the first parameter into the second parameter.
And after receiving a second response message sent by a CDN server other than the second CDN server, the first CDN server sends a feedback message to the user equipment, where the feedback message is used to indicate that the first CDN server cannot obtain the target content.
It should be noted that, the data transmission between the first CDN server and the second CDN server may be based on other protocols such as a TCP/IP protocol, as well as the HTTP protocol.
It can be seen that, in the scheme of the embodiment of the present invention, when a parameter (i.e., a first parameter) that cannot be identified by the first CDN server exists in the parameters of the URL received by the first CDN server, the parameter that cannot be identified by the first CDN server is sent to the second CDN server. The second CDN server converts the parameter that the first CDN server cannot recognize into a parameter (i.e., a second parameter) that the first CDN server recognizes; and returning the parameter identified by the first CDN server to the first CDN server. The first CDN server obtains content (i.e., target content) requested by the user equipment according to the converted parameters and parameters that can be identified in the URL parameters. The service coordination among the CDNs is realized through the expanded command request, the parameters which cannot be identified in the URL parameters are delivered to other CDN servers (namely, a second CDN server) for process conversion processing, the function that a local CDN server (namely, a first CDN server) provides a universal service is realized, the redirection and forwarding of the service are not needed, and the access speed of a user is improved.
Referring to fig. 3, fig. 3 is a schematic flowchart of a CDN service scheduling processing method according to an embodiment of the present invention. As shown in fig. 3, the method includes:
s301, the second CDN server receives a parameter conversion request sent by the first CDN server, wherein the parameter conversion request is used for indicating that the first parameter is converted into the second parameter.
The parameter conversion request comprises the first parameter, the first parameter is a parameter which cannot be identified by the first CDN server in the parameters of the Uniform Resource Locator (URL), and the second parameter is a parameter which can be identified by the first CDN server.
The URL is a URL transmitted by the user equipment to request the first CDN server to acquire content.
S302, the second CDN server converts the first parameter according to a preset mode to obtain the second parameter.
Wherein the converting the first parameter according to a preset manner to obtain the second parameter includes:
and querying a parameter corresponding relation table according to the first parameter to obtain the second parameter, wherein the parameter corresponding relation table comprises a corresponding relation between the first parameter and the second parameter.
Specifically, the second CDN server is configured with a parameter correspondence table, where the parameter correspondence table includes a correspondence between the first parameter and the second parameter. And the second CDN server inquires the parameter corresponding relation table according to the first parameter so as to acquire the second parameter.
S303, the second CDN server sends, to the first CDN server, a first response message for responding to the parameter conversion request, where the first response message includes the second parameter.
The parameter conversion request is a hypertext transfer protocol (HTTP) request command, and the first response message is a first HTTP response message.
Specifically, the parameter conversion request (i.e., the HTTP request command) is URL _ Transform [ URL parameter ]. The URL _ Transform is used for identifying parameter conversion; the URL parameter is the first parameter, which is a parameter that cannot be identified by the first CDN server.
The first response message may be an HTTP response 200, and the response message is used to identify that the second CDN server successfully converts the first parameter into the second parameter. And the Location field of the header of HTTP response 200 contains the second parameter described above, like Location [ second parameter ].
Further, the method further comprises:
when the second parameter is not obtained by querying the parameter correspondence table according to the first parameter, sending a second response message for responding to the parameter conversion request to the first CDN server, wherein the second response message is used for indicating that the parameter conversion fails; the second response message is an HTTP response message.
The second response message may be HTTP response 400.
It can be seen that, in the solution of the embodiment of the present invention, after receiving the parameter (i.e., the first parameter) that cannot be identified by the first CDN server and sent by the first CDN server, the second CDN server converts the parameter into the parameter (i.e., the second parameter) that is identified by the first CDN server, and then sends the second parameter to the first CDN server. The first CDN server sends the parameters which cannot be identified by the URL to the second CDN server for conversion, the realization mode that the first CDN server does not need to know and be familiar with the content which needs to be obtained by the user equipment is met, the appeal of differential adaptation according to different realization modes of the content is not needed, the universality and universality of the function of the first CDN server are ensured, and the redirection and forwarding of the service are not needed.
Referring to fig. 4, fig. 4 is an interactive flowchart of another CDN service scheduling processing method according to an embodiment of the present invention. As shown in fig. 4, the method includes:
s401, the user equipment sends a domain name resolution request to a DNS scheduling system.
And the domain name resolution request carries the domain name of the website which the user equipment needs to access.
S402, the DNS scheduling system sends a first response message to the user equipment.
Specifically, after receiving the domain name resolution request, the DNS scheduling system obtains the domain name carried in the domain name resolution request, and resolves the domain name to obtain the IP address corresponding to the domain name. The DNS scheduling system sends a first response message to the user equipment to respond to the domain name resolution request, wherein the first response message carries the IP address corresponding to the domain name.
It should be noted that, when the domain name that the user needs to access is already hosted by the CDN, the IP address corresponding to the domain name points to the CDN scheduling system.
S403, the user equipment sends the URL to the CDN scheduling system.
And the user equipment sends the URL to the CDN scheduling system according to the IP address corresponding to the domain name so as to acquire the target content.
S404, the CDN scheduling system sends the IP address of the first CDN server to the user equipment.
After receiving the URL, the CDN scheduling system selects a specific appropriate CDN server, that is, the first CDN server, based on the network traffic of the CDN server and the connection and load conditions of each node and the comprehensive information such as the distance to the user and the response time according to the content domain name and the type corresponding to the URL.
When it is determined that the first CDN server provides content service for the user equipment, the CDN scheduling system sends the IP address of the first CDN server to the user equipment.
S405, the user equipment sends the URL to the first CDN server according to the IP address of the first CDN server to obtain the target content.
Wherein, the target content is the content corresponding to the URL. In other words, the target content is the content that the user equipment needs to acquire.
S406, the first CDN server analyzes the URL to obtain the parameter of the URL.
Wherein, the complete format of the URL is as follows: "protocol type [/[ credential information required to access a resource @ ] server address [: port number ] ] [/resource level UNIX file path ] file name [? Query ] [ # fragment ID ] ". Wherein @, [: port number ], [? Query ] and [ # fragment ID ] "both belong to the Option Filler. In [? The query ] field will contain a parameter, in "? The "character is the starting point, each parameter is separated by" & "and the parameter name is separated from the data by" & ".
S407, the first CDN server determines whether the first parameter exists in the parameters of the URL.
The first parameter is a parameter that cannot be identified by the first CDN server among the parameters of the URL.
Wherein, when the first parameter exists in the parameter of the URL, the first CDN server performs step S408; if the first parameter does not exist in the parameters of the URL, the first CDN server performs step S411.
S408, the first CDN server sends a parameter conversion request to the second CDN server to request to convert the first parameter into the second parameter.
The second parameter is a parameter that can be identified by the first CDN server. The parameter conversion request includes the first parameter.
The parameter conversion request may be an HTTP request command. For example, URL _ Transform [ URL parameter ], which is used to instruct to perform parameter transformation, is the above-mentioned first parameter.
S409, the second CDN server converts the first parameter to obtain a second parameter.
The second CDN server is configured with a parameter correspondence table, where the parameter correspondence table includes a correspondence between a first parameter and a second parameter. And the second CDN server inquires the parameter corresponding relation table according to the first parameter so as to obtain a second parameter corresponding to the first parameter.
And S410, the second CDN server sends a second response message to the first CDN server to indicate that the parameter conversion is successful.
Wherein the second response message includes the second parameter.
Specifically, the second response message may be an HTTP response message, such as HTTP response 200. When the second response message is the HTTP response 200, the Location field of the header of the HTTP response 200 carries the second parameter, which is in the form of Location [ second parameter ].
S411, the first CDN server obtains the target content.
The target content is the content requested to be acquired by the user equipment.
Specifically, when the first parameter does not exist in the parameters of the URL, the first CDN server directly obtains the target content according to the URL; when a first parameter exists in the parameters of the URL and a second parameter sent by the second CDN server is received, the first CDN server obtains the target content according to a parameter of the URL parameter other than the first parameter and the second parameter.
S412, the first CDN server sends the target content to the user equipment.
Specifically, after obtaining the target content, the first CDN server sends the target content to the user equipment to satisfy a request of the user equipment.
In a possible embodiment, when the second CDN server queries the parameter relationship correspondence table according to the first parameter and does not query the second parameter corresponding to the first parameter, the second CDN server sends a third response message to the first CDN server to respond to the parameter conversion request.
Wherein, the third response message is used for indicating the failure of parameter conversion. In particular, the third response message may be an HTTP response message, such as HTTP response 400.
After receiving the third response message, the first CDN server determines that parameter conversion fails, and sends the parameter conversion request to a third CDN server, where the third CDN server is any one of CDN servers except for the first CDN server and the second CDN server. When the CDN servers other than the first CDN server and the second CDN server all send the third response message to the first CDN server, the first CDN server determines that the first parameter cannot be converted into the second parameter, and further cannot acquire the target content. The first CDN server sends a feedback message to the user equipment, where the feedback message is used to indicate that the first CDN server cannot obtain the target content.
The following description specifically illustrates that the user accesses the love art website to watch videos. Suppose that the user equipment accesses the odds and skill website for the first time, and therefore the user equipment does not locally have the DNS resolution result of the odds and skill related website, and a DNS query is triggered in the access process.
The user equipment sends a domain name resolution request to a dispatching system of the DNS, wherein the domain name resolution request carries a domain name 'iqiyi.com' of the Aichi art website. The DNS scheduling system comprises a local DNS and a root DNS, wherein the local DNS and the root DNS acquire an IP address corresponding to the Aichi art website domain name in a recursive mode or an iterative mode and send the IP address to the user equipment. The user equipment acquires the video program list from the content provider website (namely the love art website) corresponding to the IP address, then selects the video content from the video program list, and acquires the video description file corresponding to the target video content. For example, the video description file includes "v.iqiyi.com/FilmName _ seg 1.ts; com/FilmName _ seg2. ts; com/FilmName _ seg3. ts; com/FilmName _ seg4. ts; ".
And after the user equipment initiates a play request, triggering a local initiation DNS analysis request to analyze the domain name 'v.iqiyi.com' where the target video content is located. The DNS scheduling system (including a local DNS and a root DNS) and a DNS of a content provider acquire, in a recursive manner or an iterative manner, an IP address of the CDN hosted by the target video content, where the IP address is usually an IP address of the DNS or the DNS scheduling system of the hosted CDN, and further acquire an IP address of a CDN a server actually serving the user equipment, and send the IP address to the user equipment. And the user equipment sends a first video acquisition request to the CDN A server according to the IP address so as to request to acquire target video fragment content, wherein the target video fragment content is a part of the target video content. The CDN a server returns the target video segment content to the user equipment, and the user equipment can normally play the video content selected by the user, that is, the target video content.
When the user equipment detects that a user drags the video progress bar, the user equipment (generally video playing tool software on the user equipment) positions the position information of the dragged point. And the user equipment sends a second video acquisition request to the CDN A server, wherein the video acquisition request carries the position information of the dragging point. Because the description method of the position information of the dragging point is differentiated due to the implementation of each tool software, the CDN A server cannot identify the position information of the dragging point. When the dragging point position information cannot be identified, the CDN A server cannot determine the video fragment where the video content corresponding to the dragging point is located, and the CDN A server sends a parameter conversion request to a CDN B server to request the CDN B server to convert the dragging point position information. The parameter conversion request carries the position information of the dragging point. And the CDN B server converts the position of the dragging point and returns the converted result to the CDN A server. And the CDN A server acquires the video fragment where the video content corresponding to the dragging point is located according to the converted result, and sends the video fragment to the user equipment. The specific process can be seen in fig. 5. As shown in fig. 5, the dashed line is DNS interaction, implemented as HTTP interaction.
It should be noted that the position information of the drag point may be regarded as the first parameter, and the converted result may be regarded as the second parameter.
Fig. 6 and 6 are schematic structural diagrams of a CDN server according to an embodiment of the present invention. As shown in fig. 6, the CDN server 600 includes:
the receiving unit 601 is configured to, after receiving a uniform resource locator URL sent by a user equipment, parse the URL to obtain a parameter of the URL.
A sending unit 602, configured to send a parameter conversion request to a second CDN server to request to convert a first parameter into a second parameter when the first parameter exists in the parameter of the URL; the parameter conversion request comprises the first parameter, the first parameter is a parameter which cannot be identified by a first CDN server in the parameters of the URL, and the second parameter is a parameter which can be identified by the first CDN server.
Wherein, the parameter conversion request is an HTTP request command.
The receiving unit 601 is further configured to receive a first response message sent by the second CDN server and used for responding to the parameter conversion request, where the first response message is used to indicate that parameter conversion is successful, and the first response message includes the second parameter.
In a possible embodiment, the receiving unit 601 is further configured to:
after the sending unit 602 sends a parameter conversion request to a second CDN server, receiving a second response message sent by the second CDN server and responding to the parameter conversion request, where the second response message is used to indicate that parameter conversion fails, and the second response message is an HTTP response message.
An obtaining unit 603, configured to obtain a target content according to a parameter that can be identified by the first CDN server in the second parameter and the parameter of the URL, where the target content is a content requested to be obtained by the user equipment.
In a possible embodiment, the sending unit 602 is further configured to:
after the obtaining unit 603 obtains the target content, the target content is sent to the user equipment.
In a possible embodiment, the sending unit 602 is further configured to:
and after the receiving unit receives a second response message which is sent by the second CDN server and responds to the parameter conversion request, sending a feedback message to the user equipment, wherein the feedback message is used for indicating that the target content cannot be obtained.
The units (the receiving unit 601, the transmitting unit 602, and the obtaining unit 603) are configured to perform the steps related to the method.
In this embodiment, CDN server 600 is presented in the form of a unit. An "element" may refer to an application-specific integrated circuit (ASIC), a processor and memory that execute one or more software or firmware programs, an integrated logic circuit, and/or other devices that may provide the described functionality. Further, the above receiving unit 601, transmitting unit 602, and acquiring unit 603 can be realized by the processor 801 of the router shown in fig. 8.
Referring to fig. 7, fig. 7 is a schematic structural diagram of another CDN server according to an embodiment of the present invention. As shown in fig. 7, the CDN server 700 includes:
a receiving unit 701, configured to receive a parameter conversion request sent by a first CDN server, where the parameter conversion request is used to instruct to convert a first parameter into a second parameter; the parameter conversion request comprises the first parameter, the first parameter is a parameter which cannot be identified by the first CDN server in the parameters of the Uniform Resource Locator (URL), and the second parameter is a parameter which can be identified by the first CDN server.
The parameter conversion request is an HTTP request command, and the first response message is a first HTTP response message.
A converting unit 702, configured to convert the first parameter according to a preset manner to obtain the second parameter.
Specifically, the conversion unit 702 is specifically configured to:
and querying a parameter corresponding relation table according to the first parameter to obtain the second parameter, wherein the parameter corresponding relation table comprises a corresponding relation between the first parameter and the second parameter.
A sending unit 703 is configured to send a first response message used for responding to the parameter conversion request to the first CDN server, where the first response message includes the second parameter.
In a possible embodiment, the sending unit 703 is further configured to:
when the second parameter is not obtained by querying the parameter correspondence table according to the first parameter, the conversion unit 702 sends a second response message for responding to the parameter conversion request to the first CDN server, where the second response message is used to indicate that parameter conversion fails; the second response message is an HTTP response message.
The units (the receiving unit 701, the converting unit 702, and the transmitting unit 703) are configured to execute the steps related to the method.
In this embodiment, CDN server 700 is presented in the form of a unit. An "element" may refer to an application-specific integrated circuit (ASIC), a processor and memory that execute one or more software or firmware programs, an integrated logic circuit, and/or other devices that may provide the described functionality. Further, the above receiving unit 701, converting unit 702, and transmitting unit 703 may be realized by the processor 801 of the router shown in fig. 8.
As shown in fig. 8, CDN server 800 may be implemented in the structure of fig. 8, and CDN server 800 includes at least one processor 801, at least one memory 802, and at least one communication interface 803. The processor 801, the memory 802 and the communication interface 803 are connected through the communication bus and perform communication with each other.
The processor 801 may be a general purpose Central Processing Unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of programs according to the above schemes.
Communication interface 803 is used for communicating with other devices or communication Networks, such as ethernet, Radio Access Network (RAN), Wireless Local Area Networks (WLAN), etc.
The Memory 802 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.), 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, but is not limited to these. The memory may be self-contained and coupled to the processor via a bus. The memory may also be integral to the processor.
The memory 802 is used for storing application program codes for executing the above schemes, and is controlled by the processor 801 to execute. The processor 801 is used to execute application program code stored in the memory 802.
The code stored in the memory 802 may execute the CDN service scheduling processing method provided in the embodiment shown in fig. 2, for example, after receiving a URL sent by the user equipment, analyze the URL to obtain a parameter of the URL; when a first parameter exists in the parameters of the URL, sending a parameter conversion request to a second CDN server to request to convert the first parameter into a second parameter; the parameter conversion request comprises the first parameter, the first parameter is a parameter which cannot be identified by a first CDN server in the parameters of the URL, and the second parameter is a parameter which can be identified by the first CDN server; receiving a first response message sent by the second CDN server and responding to the parameter conversion request, wherein the first response message is used for indicating that the parameter conversion is successful and comprises the second parameter; and acquiring target content according to the second parameter and the parameter which can be identified by the first CDN server in the parameters of the URL, wherein the target content is the content requested to be acquired by the user equipment.
The codes stored in the memory 802 can also execute the CDN service scheduling processing method provided in the embodiment shown in fig. 3. For example, a parameter conversion request sent by a first CDN server is received, where the parameter conversion request is used to instruct to convert a first parameter into a second parameter; the parameter conversion request comprises the first parameter, the first parameter is a parameter which cannot be identified by the first CDN server in the parameters of the URL, and the second parameter is a parameter which can be identified by the first CDN server; converting the first parameter according to a preset mode to obtain a second parameter; sending a first response message for responding to the parameter conversion request to the first CDN server, wherein the first response message comprises the second parameter.
An embodiment of the present invention further provides a computer storage medium, where the computer storage medium may store a program, and when the program is executed, the program includes some or all of the steps of any CDN service scheduling processing method described in the foregoing method embodiments.
It should be noted that, for simplicity of description, the above-mentioned method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the present invention is not limited by the order of acts, as some steps may occur in other orders or concurrently in accordance with the invention. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required by the invention.
In the foregoing embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus may be implemented in other manners. For example, the above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one type of division of logical functions, and there may be other divisions when actually implementing, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted, or not implemented. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection of some interfaces, devices or units, and may be an electric or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. 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 computer readable memory. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a memory and includes several instructions for causing a computer device (which may be a personal computer, a server, a network device, or the like) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned memory comprises: a U-disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic or optical disk, and other various media capable of storing program codes.
Those skilled in the art will appreciate that all or part of the steps in the methods of the above embodiments may be implemented by associated hardware instructed by a program, which may be stored in a computer-readable memory, which may include: flash Memory disks, Read-Only memories (ROMs), Random Access Memories (RAMs), magnetic or optical disks, and the like.
The above embodiments of the present invention are described in detail, and the principle and the implementation of the present invention are explained by applying specific embodiments, and the above description of the embodiments is only used to help understanding the method of the present invention and the core idea thereof; meanwhile, for a person skilled in the art, according to the idea of the present invention, there may be variations in the specific embodiments and the application scope, and in view of the above, the content of the present specification should not be construed as a limitation to the present invention.

Claims (16)

1. A CDN service scheduling processing method for a content delivery network is characterized by comprising the following steps:
after receiving a Uniform Resource Locator (URL) sent by user equipment, analyzing the URL to obtain parameters of the URL;
when a first parameter exists in the parameters of the URL, sending a parameter conversion request to a second CDN server to request to convert the first parameter into a second parameter; the parameter conversion request comprises the first parameter, the first parameter is a parameter which cannot be identified by a first CDN server in the parameters of the URL, and the second parameter is a parameter which can be identified by the first CDN server; the parameter conversion request is a hypertext transfer protocol (HTTP) request command;
receiving a first response message sent by the second CDN server and responding to the parameter conversion request, wherein the first response message is used for indicating that the parameter conversion is successful and comprises the second parameter; the first response message is an HTTP response message;
and acquiring target content according to the second parameter and the parameter which can be identified by the first CDN server in the parameters of the URL, wherein the target content is the content requested to be acquired by the user equipment.
2. The method of claim 1, wherein after obtaining the target content, the method further comprises:
and sending the target content to the user equipment.
3. The method of claim 1, wherein after sending the parameter translation request to the second CDN server, the method further comprises:
and receiving a second response message which is sent by the second CDN server and used for responding to the parameter conversion request, wherein the second response message is used for indicating that the parameter conversion is failed, and the second response message is an HTTP response message.
4. The method of claim 3, wherein after receiving a second response message sent by the second CDN server in response to the parameter conversion request, the method further comprises:
and sending a feedback message to the user equipment, wherein the feedback message is used for indicating that the target content cannot be acquired.
5. A CDN service scheduling processing method for a content delivery network is characterized by comprising the following steps:
receiving a parameter conversion request sent by a first CDN server, wherein the parameter conversion request is used for indicating that a first parameter is converted into a second parameter; the parameter conversion request comprises the first parameter, the first parameter is a parameter which cannot be identified by the first CDN server in parameters of a Uniform Resource Locator (URL), and the second parameter is a parameter which can be identified by the first CDN server; the parameter conversion request is a hypertext transfer protocol (HTTP) request command;
converting the first parameter according to a preset mode to obtain a second parameter;
sending a first response message for responding to the parameter conversion request to the first CDN server, wherein the first response message comprises the second parameter; the first response message is an HTTP response message.
6. The method of claim 5, wherein the converting the first parameter according to a preset manner to obtain the second parameter comprises:
and querying a parameter corresponding relation table according to the first parameter to obtain the second parameter, wherein the parameter corresponding relation table comprises a corresponding relation between the first parameter and the second parameter.
7. The method of claim 6, further comprising:
when the second parameter is not obtained by querying the parameter correspondence table according to the first parameter, sending a second response message for responding to the parameter conversion request to the first CDN server, wherein the second response message is used for indicating that the parameter conversion fails; the second response message is an HTTP response message.
8. A content delivery network CDN server, comprising:
the device comprises a receiving unit, a processing unit and a processing unit, wherein the receiving unit is used for analyzing a Uniform Resource Locator (URL) after receiving the URL sent by user equipment to obtain parameters of the URL;
the sending unit is used for sending a parameter conversion request to a second CDN server to request to convert the first parameter into a second parameter when the first parameter exists in the parameters of the URL; the parameter conversion request comprises the first parameter, the first parameter is a parameter which cannot be identified by a first CDN server in the parameters of the URL, and the second parameter is a parameter which can be identified by the first CDN server; the parameter conversion request is a hypertext transfer protocol (HTTP) request command;
the receiving unit is further configured to receive a first response message sent by the second CDN server and used for responding to the parameter conversion request, where the first response message is used to indicate that parameter conversion is successful, and the first response message includes the second parameter;
and an obtaining unit, configured to obtain target content according to a parameter that can be identified by the first CDN server in the second parameter and the parameter of the URL, where the target content is content requested to be obtained by the user equipment.
9. The CDN server of claim 8 wherein the sending unit is further configured to:
and after the acquisition unit acquires the target content, transmitting the target content to the user equipment.
10. The CDN server of claim 8 wherein the receiving unit is further configured to:
after the sending unit sends a parameter conversion request to a second CDN server, receiving a second response message sent by the second CDN server and responding to the parameter conversion request, wherein the second response message is used for indicating that parameter conversion fails, and the second response message is an HTTP response message.
11. The CDN server of claim 10 wherein the sending unit is further configured to:
and after the receiving unit receives a second response message which is sent by the second CDN server and responds to the parameter conversion request, sending a feedback message to the user equipment, wherein the feedback message is used for indicating that the target content cannot be obtained.
12. A content delivery network CDN server, comprising:
the receiving unit is used for receiving a parameter conversion request sent by a first CDN server, wherein the parameter conversion request is used for indicating that a first parameter is converted into a second parameter; the parameter conversion request comprises the first parameter, the first parameter is a parameter which cannot be identified by the first CDN server in parameters of a Uniform Resource Locator (URL), and the second parameter is a parameter which can be identified by the first CDN server; the parameter conversion request is a hypertext transfer protocol (HTTP) request command;
the conversion unit is used for converting the first parameter according to a preset mode to obtain the second parameter;
a sending unit, configured to send, to the first CDN server, a first response message used for responding to the parameter conversion request, where the first response message includes the second parameter, and the first response message is a first HTTP response message.
13. The CDN server of claim 12 wherein the conversion unit is specifically configured to:
and querying a parameter corresponding relation table according to the first parameter to obtain the second parameter, wherein the parameter corresponding relation table comprises a corresponding relation between the first parameter and the second parameter.
14. The CDN server of claim 13 wherein the sending unit is further configured to:
when the conversion unit queries the parameter correspondence table according to the first parameter to obtain no second parameter, sending a second response message for responding to the parameter conversion request to the first CDN server, where the second response message is used to indicate that parameter conversion fails; the second response message is an HTTP response message.
15. A CDN server of a content delivery network is characterized by comprising
A memory storing executable program code;
a processor coupled with the memory;
the processor calls the executable program code stored in the memory, performs the method of any of claims 1-4, or performs the method of any of claims 5-7.
16. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program comprising program instructions that, when executed by a processor, cause the processor to perform the method according to any one of claims 1-4, or to perform the method according to any one of claims 5-7.
CN201810346347.XA 2018-04-17 2018-04-17 CDN service scheduling processing method and CDN server Active CN110392069B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201810346347.XA CN110392069B (en) 2018-04-17 2018-04-17 CDN service scheduling processing method and CDN server
PCT/CN2019/080178 WO2019201072A1 (en) 2018-04-17 2019-03-28 Cdn service scheduling processing method and cdn server

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201810346347.XA CN110392069B (en) 2018-04-17 2018-04-17 CDN service scheduling processing method and CDN server

Publications (2)

Publication Number Publication Date
CN110392069A CN110392069A (en) 2019-10-29
CN110392069B true CN110392069B (en) 2021-12-14

Family

ID=68240513

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201810346347.XA Active CN110392069B (en) 2018-04-17 2018-04-17 CDN service scheduling processing method and CDN server

Country Status (2)

Country Link
CN (1) CN110392069B (en)
WO (1) WO2019201072A1 (en)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110958656B (en) * 2019-11-25 2021-09-14 中国联合网络通信集团有限公司 CDN redirection method and system
CN113300867B (en) * 2020-06-29 2022-06-14 阿里巴巴集团控股有限公司 CDN system, information processing method and device, and CDN node
CN112615908B (en) * 2020-12-08 2023-04-18 广东荣文科技集团有限公司 Webpage processing method, electronic equipment and related product
CN114615237B (en) * 2022-03-22 2024-03-29 阿里巴巴（中国）有限公司 Streaming media communication method, system, equipment and storage medium

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104394182A (en) * 2014-03-21 2015-03-04 贵阳朗玛信息技术股份有限公司 Method for realizing content delivery network acceleration and source server
CN105847398A (en) * 2016-04-25 2016-08-10 乐视控股（北京）有限公司 Business scheduling method, scheduling server and business server

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TWI420339B (en) * 2010-11-10 2013-12-21 Ind Tech Res Inst Software authorization system and method
US20120311076A1 (en) * 2011-05-31 2012-12-06 Cisco Technology, Inc. System and method to support different uniform resource locator formats for content on different network elements
US10116729B2 (en) * 2015-10-06 2018-10-30 Verizon Digital Media Services Inc. Dynamic media transformation service in a CDN
CN106372250A (en) * 2016-09-23 2017-02-01 郑州云海信息技术有限公司 Parameter passing method and device capable of starting local application through URL protocol

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104394182A (en) * 2014-03-21 2015-03-04 贵阳朗玛信息技术股份有限公司 Method for realizing content delivery network acceleration and source server
CN105847398A (en) * 2016-04-25 2016-08-10 乐视控股（北京）有限公司 Business scheduling method, scheduling server and business server

Also Published As

Publication number Publication date
WO2019201072A1 (en) 2019-10-24
CN110392069A (en) 2019-10-29

Similar Documents

Publication Publication Date Title
CN109067914B (en) web service proxy method, device, equipment and storage medium
CN108353095B (en) Domain name resolution method, client, edge node and domain name resolution system
CN110392069B (en) CDN service scheduling processing method and CDN server
CN102171673B (en) Cross-layer pipelining optimizations for reduced roundtrips and improving quality of experience
JP5739023B2 (en) System and method using a web proxy server to access a device having an assigned network address
US10630771B1 (en) Content delivery network with network storage and support for on-demand content upload
US8065417B1 (en) Service provider registration by a content broker
US8620999B1 (en) Network resource modification for higher network connection concurrence
JP6054490B2 (en) Method and corresponding system for accessing content in a network
CN110392130B (en) Information processing method based on network, electronic equipment and network system
EP2633667B1 (en) System and method for on the fly protocol conversion in obtaining policy enforcement information
US9705762B2 (en) Systems and methods for detecting device identity at a proxy background
CN110505188B (en) Terminal authentication method, related equipment and authentication system
CN112073545B (en) MP-TCP capability for transmitting server devices using DNS
WO2013154473A1 (en) Method for optimising downloading of data
US20160323365A1 (en) Content delivery method, apparatus, and system
CN106411978B (en) Resource caching method and device
US10129320B2 (en) QoS improvement method, apparatus, and system
US10631145B1 (en) Dynamic provision of application related sponsored data connectivity
CN107135091A (en) A kind of application quality index mapping method, server and client side
EP2850809B1 (en) Providing data to a network terminal
EP1391099A2 (en) Requests in a communication system
EP2957089A1 (en) Systems, methods and computer program products for enabling a communication device to provide session improvement requests to a server of a network operator's access network
CN112003717A (en) Device upgrading method, network device, server, electronic device and storage medium
GB2503289A (en) Network Provisioning involving analysis of subscriber behaviour

Legal Events

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