CN113452539B - Source station switching method and device, electronic equipment and storage medium - Google Patents
Source station switching method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN113452539B CN113452539B CN202010225023.8A CN202010225023A CN113452539B CN 113452539 B CN113452539 B CN 113452539B CN 202010225023 A CN202010225023 A CN 202010225023A CN 113452539 B CN113452539 B CN 113452539B
- Authority
- CN
- China
- Prior art keywords
- source station
- status code
- request
- backup source
- response
- 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
Links
- 238000000034 method Methods 0.000 title claims abstract description 54
- 238000003860 storage Methods 0.000 title claims abstract description 24
- 230000004044 response Effects 0.000 claims abstract description 150
- 238000004590 computer program Methods 0.000 claims description 10
- 238000010586 diagram Methods 0.000 description 18
- 238000013507 mapping Methods 0.000 description 11
- 238000012545 processing Methods 0.000 description 9
- 230000006870 function Effects 0.000 description 8
- 238000004891 communication Methods 0.000 description 7
- 230000005540 biological transmission Effects 0.000 description 4
- 238000004458 analytical method Methods 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 230000000694 effects Effects 0.000 description 2
- 239000000835 fiber Substances 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000001902 propagating effect Effects 0.000 description 2
- RYGMFSIKBFXOCR-UHFFFAOYSA-N Copper Chemical compound [Cu] RYGMFSIKBFXOCR-UHFFFAOYSA-N 0.000 description 1
- 229910052802 copper Inorganic materials 0.000 description 1
- 239000010949 copper Substances 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000009826 distribution Methods 0.000 description 1
- 230000014509 gene expression Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000003238 somatosensory effect Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
- H04L41/0663—Performing the actions predefined by failover planning, e.g. switching to standby network elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/22—Arrangements for detecting or preventing errors in the information received using redundant apparatus to increase reliability
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/12—Avoiding congestion; Recovering from congestion
- H04L47/125—Avoiding congestion; Recovering from congestion by balancing the load, e.g. traffic engineering
-
- 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/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1004—Server selection for load balancing
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The embodiment of the disclosure discloses a source station switching method, a source station switching device, electronic equipment and a computer readable storage medium. The method is executed on an upper node and comprises the following steps: receiving a first back source request of a first node for requesting a target resource; under the condition that the target resource does not exist in the local cache, sending a second source returning request for requesting the target resource to the main source station; receiving a response status code sent by the main source station in response to the second source returning request, and determining a backup source station corresponding to the response status code according to a corresponding relation between a preset status code and a backup source station and the response status code under the condition that the second source returning request is determined to be failed according to the response status code; and switching the second source returning request to the backup source station corresponding to the response status code to request the target resource again.
Description
Technical Field
The embodiment of the disclosure relates to the technical field of CDNs, and in particular, to a source station switching method and apparatus, an electronic device, and a storage medium.
Background
In the CDN (Content Delivery Network), a layer of intelligent virtual Network based on the existing internet is formed by placing node servers at various places in the Network, and the CDN system can redirect a user's request to a service node closest to the user in real time according to Network traffic, connection of each node, load conditions, and comprehensive information such as a distance to the user and response time. The method aims to enable a user to obtain needed content nearby, most requests are completed at the CDN edge node, the CDN plays a shunting role, the load of a source station is reduced, the problem of network congestion of the Internet is solved, and the response speed of the user for accessing a website is improved.
In the event of a failure such as a network failure that renders the primary source unavailable, it is common for the upper level node to switch the request to the backup source for processing. When the upper node requests the main source station back to the source according to the request of the lower node, a plurality of requests fail, and the main source station is marked as unavailable. The request received by the subsequent upper node is switched to the backup source station. This, however, results in a failure of the back-to-source requests that have already been sent to the primary source station, which can only be switched to the backup source station the next time they are received.
Disclosure of Invention
The embodiment of the disclosure aims to provide a source station switching method, a source station switching device, an electronic device and a computer readable storage medium, and to reduce a source return error by switching a source return request of a primary source station to a backup source station in time.
According to a first aspect of the embodiments of the present disclosure, there is provided a source station switching method, performed at an upper node, the method including:
receiving a first source-returning request of a first node for requesting a target resource;
under the condition that the target resource does not exist in the local cache, sending a second source returning request for requesting the target resource to the main source station;
receiving a response status code sent by the main source station in response to the second back-to-source request, and under the condition that the second back-to-source request fails to be determined according to the response status code,
determining a backup source station corresponding to the response state code according to a corresponding relation between a preset state code and a backup source station and the response state code; and
and switching the second source returning request to a backup source station corresponding to the response state code to request the target resource again.
Optionally, the method further includes:
and sending the response state code to the first node under the condition that the backup source station corresponding to the response state code is not determined according to the corresponding relation between the preset state code and the backup source station and the response state code.
Optionally, the method further includes:
and receiving a response status code sent by the backup source station in response to the second source returning request, and sending the response status code to the first node under the condition that the second source returning request is determined to fail according to the response status code sent by the backup source station.
Optionally, the method further includes:
and under the condition that the target resource exists in the local cache, responding to the first source returning request to send the target resource to the first node.
Optionally, the method further includes:
and under the condition that the second source returning request is determined to be successful according to the response status code, responding to the first source returning request and sending the target resource to the first node.
Optionally, the correspondence between the preset status code and the backup source station includes: the single state code corresponds to a single backup source station, a plurality of different state codes correspond to the same backup source station, the state code in the preset range corresponds to the same backup source station, and the same state code corresponds to at least one of a plurality of different backup source stations.
Optionally, when the response status code conforms to a plurality of different backup source stations corresponding to one status code, the determining, according to the preset correspondence between the status code and the backup source station and the response status code, the backup source station corresponding to the response status code includes:
selecting one backup source station from the plurality of different backup source stations;
and determining the selected backup source station as the backup source station corresponding to the response status code.
Optionally, when the plurality of different backup source stations have ports, the ports corresponding to the plurality of different backup source stations are the same.
Optionally, when the response status code simultaneously conforms to a single backup source station corresponding to a single status code, and a status code in a predetermined range corresponds to the same backup source station, the determining, according to the correspondence between the preset status code and the backup source station and the response status code, the backup source station corresponding to the response status code includes:
and determining the backup source station corresponding to the response state code according to the corresponding relation of the single state code corresponding to the single backup source station.
According to a second aspect of the embodiments of the present disclosure, there is provided a source station switching apparatus, which is executed at an upper node, the apparatus including:
a first receiving module, configured to receive a first source-returning request of a lower node requesting a target resource;
a sending module, configured to send a second source return request requesting the target resource to a primary source station when the target resource does not exist in a local cache;
a second receiving module, configured to receive a response status code sent by the master source station in response to the second source return request;
a determining module, configured to determine, when it is determined that the second request to return to source fails according to the response status code, a backup source station corresponding to the response status code according to a correspondence between a preset status code and the backup source station and the response status code; and
and the switching module is used for switching the second source returning request to the backup source station corresponding to the response state code so as to request the target resource again.
According to a third aspect of the embodiments of the present disclosure, there is provided an electronic apparatus including:
the apparatus according to the second aspect of the embodiments of the present disclosure; or,
a processor and a memory for storing executable instructions for controlling the processor to perform the method according to the first aspect of embodiments of the present disclosure.
According to a fourth aspect of embodiments of the present disclosure, there is provided a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the method according to the first aspect.
According to the embodiment of the disclosure, switching of the backup source station according to the corresponding relationship between the preset state code and the backup source station can be supported, and the current request is switched to the backup source station corresponding to the response state code through the corresponding relationship between the preset state code and the backup source station by the user and the response state code returned by the main source station when the request fails, so that the current request can be switched to the corresponding backup source station to initiate the source return request again. So that the request still takes effect without waiting for switching to the backup source station after the next source returning request is received. Therefore, the switching of the request level can be realized, the source return error is reduced, and the influence of request failure caused by the failure of the main source station is reduced.
Other features of, and advantages with, the disclosed embodiments will become apparent from the following detailed description of exemplary embodiments thereof, which proceeds with reference to the accompanying drawings.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate embodiments of the disclosure and together with the description, serve to explain the principles of the embodiments of the disclosure.
Fig. 1 is a block diagram of a hardware configuration of an electronic device that can be used to implement an embodiment of the present disclosure.
Fig. 2 is a flowchart illustrating steps of a source station switching method according to an embodiment of the disclosure.
Fig. 3 is a CDN back-source request flow chart according to an embodiment of the disclosure.
Fig. 4 is a structure diagram of a CDN upper node according to the embodiment of the present disclosure.
Fig. 5 is a block diagram of a source station switching apparatus according to an embodiment of the present disclosure.
Fig. 6 is a block diagram of a structure of an electronic device according to an embodiment of the present disclosure.
Detailed Description
Various exemplary embodiments of the disclosed embodiments will now be described in detail with reference to the accompanying drawings. It should be noted that: the relative arrangement of parts and steps, numerical expressions, and numerical values set forth in these embodiments do not limit the scope of the embodiments of the present disclosure unless specifically stated otherwise.
The following description of at least one exemplary embodiment is merely illustrative in nature and is in no way intended to limit the embodiments of the disclosure, its application, or uses.
Techniques, methods and apparatus known to those of ordinary skill in the relevant art may not be discussed in detail but are intended to be part of the specification where appropriate.
In all examples shown and discussed herein, any particular value should be construed as merely illustrative, and not limiting. Thus, other examples of the exemplary embodiments may have different values.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be discussed further in subsequent figures.
< hardware configuration >
Fig. 1 is a block diagram showing a hardware configuration of an electronic apparatus 1000 that can implement an embodiment of the present disclosure.
The electronic device 1000 may be a laptop computer, desktop computer, notebook computer, server device, etc.
The server device may be a unitary server or a distributed server across multiple computers or computer data centers. The server may be of various types, such as, but not limited to, a node device of a content distribution network, a storage server of a distributed storage system, a cloud database server, a cloud computing server, a cloud management server, a web server, a news server, a mail server, a message server, an advertisement server, a file server, an application server, an interaction server, a storage server, a database server, a proxy server, or the like. In some embodiments, each server may include hardware, software, or embedded logic components or a combination of two or more such components for performing the appropriate functions supported or implemented by the server. For example, a server, such as a blade server, a cloud server, etc., or may be a group of servers, which may include one or more of the above types of servers, etc.
As shown in fig. 1, the electronic device 1000 may include a processor 1100, a memory 1200, an interface device 1300, a communication device 1400, or may further include a display device 1500, an input device 1600, a speaker 1700, a microphone 1800, and the like. The processor 1100 may be a central processing unit CPU, a microprocessor MCU, or the like, and is configured to execute a computer program. The computer program may be written in an instruction set of architectures such as x86, Arm, RISC, MIPS, SSE, and the like. The memory 1200 includes, for example, a ROM (read only memory), a RAM (random access memory), a nonvolatile memory such as a hard disk, and the like. The interface device 1300 includes, for example, a USB interface, a headphone interface, and the like. The communication device 1400 is capable of wired communication using an optical fiber or a cable, for example, or wireless communication, and specifically may include WiFi communication, bluetooth communication, 2G/3G/4G/5G communication, and the like. The display device 1500 is, for example, a liquid crystal display panel, a touch panel, or the like. The input device 1600 may include, for example, a touch screen, a keyboard, a somatosensory input, and the like. A user can input/output voice information through the speaker 1700 and the microphone 1800.
The electronic device shown in fig. 1 is merely illustrative and is in no way intended to limit the embodiments of the disclosure, their application, or uses. In an embodiment of the present disclosure, the memory 1200 of the electronic device 1000 is configured to store instructions for controlling the processor 1100 to operate so as to execute the source station switching method provided in any one of the embodiments of the present disclosure. It should be understood by those skilled in the art that although a plurality of means are shown for the electronic device 1000 in fig. 1, embodiments of the present disclosure may only refer to some of the means therein, for example, the electronic device 1000 may only refer to the processor 1100 and the storage 1200. The skilled person can design the instructions according to the disclosed embodiments of the present disclosure. How the instructions control the operation of the processor is well known in the art and will not be described in detail herein.
< method example >
In one embodiment of the present disclosure, a source station switching method is provided, which may be performed at an upper node, such as an upper node of a CDN network.
Referring to fig. 2, a flowchart of steps of a source station switching method according to an embodiment of the present disclosure is shown, where the method may be implemented by an electronic device, for example, the electronic device 1000 shown in fig. 1.
As shown in fig. 2, the source station switching method of the embodiment of the present disclosure includes the following steps:
Here, the first node may be an edge node or a middle-layer node of the CDN network, and after receiving the target resource acquisition request of the user and the edge node or the middle-layer node does not have a corresponding target resource, the first node sends a first source return request to the upper-layer node, so as to pull the corresponding target resource to the source station through the upper-layer node. The target resource may be a video file, an audio file, a picture, etc., requested by the user.
And step 104, sending a second source return request for requesting the target resource to the main source station under the condition that the target resource does not exist in the local cache.
The target resource may or may not be stored in the local Cache of the upper node (Cache of the upper node). In step 104, if the local cache does not have the target resource, the upper node is required to request the corresponding primary source station for acquisition.
In one embodiment, the upper node may include a reverse proxy server (Nginx) and a Cache device (Cache), where the Nginx belongs to a front-end module of the upper node and is configured to receive and process a request, the Cache belongs to a back-end module of the upper node and is configured to obtain a target resource of the request from a source station according to the request, to Cache the target resource, and to provide a status code sent by the target resource or the source station to the Nginx of the front end, and to respond to the request by the Nginx and return the request to the lower node.
And 106, receiving a response status code sent by the main source station in response to the second source returning request, and determining a backup source station corresponding to the response status code according to a preset corresponding relationship between the status code and the backup source station and the response status code under the condition that the second source returning request is determined to be failed according to the response status code.
In response to the back-source request sent by the upper node, the primary source station may return a response status code (e.g., status code 200) indicating that the second back-source request target resource is successful and a corresponding requested target resource to the upper node in a state that the primary source station is available. A response status code indicating that the second back-to-source request target resource failed may also be returned to the upper node in a state where the primary source is unavailable, such as when the requesting primary source has a 4xx or 5xx failure. According to different conditions that the main source station is unavailable, the returned response status code of the request failure is different, for example, the response status code is 404, which indicates that the requested page does not exist; the response status code is 403, indicating an illegal access; the response status code is 504, indicating that the requesting source station has timed out, etc.
The preset corresponding relationship between the status code and the backup source station may be configured on a server of a client (e.g., a target resource provider, a platform for jittering, express, etc.), which may be referred to as source station switching configuration hereinafter, and the configuration may be set according to a client requirement and issued to a corresponding device of an upper node. Usually, the source station switching configuration is issued once in the form of a configuration file, and if a client changes the configuration, the configuration will be issued again to an upper node. And the upper layer node stores the received source station switching configuration file in a disk.
In step 106, in an embodiment, when the upper node distinguishes between the Nginx and the Cache, the obtained source station switching configuration may be executed by the upper node Nginx and the Cache together. Specifically, when an upper node Nginx receives a first source returning request sent by a lower node, a source station switching configuration file stored in a disk of the upper node is read into a memory, and a source station switching configuration corresponding to the first source returning request is packaged into a request header specified by the request from the memory, for example, "miss-page" 404:1.1.1.1,500-599:2.2.2.2,3.3.3.3 "," miss-page "represents a request header name, and a switching configuration corresponding to a status code 404 is a backup source station with an IP address of 1.1.1.1; the status codes in the range of 500-.
And the upper node Nginx sends a source returning request containing the request head corresponding to the source station switching configuration to a Cache of the upper node, and the Cache receives the request of the Nginx and analyzes the received request to obtain the corresponding source station switching configuration. The upper-layer node Cache can form a mapping table by the state code obtained by analysis and the corresponding backup source station, can store the mapping table into a memory, can directly read the mapping table from the memory when the mapping table is convenient to use, and releases the mapping table after the mapping table is used up so as to save storage space. Or stored in a disk and permanently stored.
And the upper-layer node Cache sends a second source returning request for requesting the target resource to the main source station, and the main source station returns a corresponding response status code. The upper-layer node Cache can determine that the second source returning request is successful or failed according to the response status code returned by the main source station. Such as the successful response status code 200 or the failed response status code 4xx or 5xx described above.
If the request is not hit, that is, the main source station does not have a target resource corresponding to the request, and the second source returning request fails, the upper-layer node Cache reads a corresponding source station switching configuration mapping table from a disk or a memory to determine whether a corresponding switching backup source station exists in a state code returned by the main source station under the failure condition.
The source station switching configuration records a corresponding relationship between the status code and the backup source station, and the status code may be 4xx or 5xx as described above.
In one embodiment, the correspondence between the preset status code and the backup source station includes: the single state code corresponds to a single backup source station, a plurality of different state codes correspond to the same backup source station, the state code in the preset range corresponds to the same backup source station, and the same state code corresponds to at least one of a plurality of different backup source stations.
When the preset correspondence between the state codes and the backup source stations is configured such that a single state code corresponds to a single backup source station, different state codes corresponding to different backup source stations are included, that is, the correspondence between a plurality of single backup source stations and corresponding single state codes may be included in the configuration.
Specifically, the format of the source station switching configuration includes one or any combination of the following:
a) state code 1: source station 1, status code 2: source station 2
b) Status code 1, status code 2: source station 1
c) Status code 1 to status code 2: source station 1
d) State code 1: source station 1, source station 2
Format a indicates that a single status code corresponds to the configuration of a single backup source station, format b indicates that a plurality of different status codes correspond to the configuration of the same backup source station, format c indicates that status codes in a predetermined range correspond to the configuration of the same backup source station, and format d indicates that the same status code corresponds to the configuration of the plurality of different backup source stations.
In one embodiment, when a plurality of different backup source stations have ports, the ports corresponding to the plurality of different backup source stations are the same.
The backup source station may be an IP (Internet Protocol) or a domain name. The backup source may or may not have a port. If the port is carried, the same status code corresponds to the configuration of a plurality of different backup source stations, the ports of the plurality of backup source stations must be consistent, that is, the ports of the plurality of backup source stations are the same. For example, the ports of the backup source stations are all 80 ports, 43 ports or 8080 ports, and so on. The source station consists of an IP and ports, and if the ports are different, the source station cannot be switched to a plurality of backup source stations according to the switching configuration of the source station. If the backup source station does not have a port, a default port is selected according to the back-to-source protocol.
In step 106, according to the correspondence between the preset status code and the backup source station in the source station switching configuration and the response status code returned by the source station, the backup source station corresponding to the response status code may be determined.
That is, when the upper node determines that the second request to return to the source fails, the corresponding switching backup source station is determined according to the response status code returned by the main source station and the switching configuration of the source station.
In the embodiment where the upper node includes a Nginx and a Cache, as described in step 106 above, the Cache of the upper node may read a corresponding source station switching configuration mapping table from a disk or an internal memory, and in step 108, the Cache may determine, according to the read source station switching configuration mapping table, a backup source station that matches a state code returned by the main source station in the case of the failure.
The upper-level node Cache may determine whether the response status code returned by the main source station corresponds to the backup source station by determining whether the response status code returned by the main source station meets (or satisfies) the switching configuration condition between the status code analyzed in step 106 and the backup source station. And determining the corresponding backup source station under the switching configuration condition that the response state code returned by the main source station is in accordance with the analysis.
In an embodiment, in a case that the response status code conforms to a plurality of different backup source stations corresponding to one status code, the determining, according to a preset correspondence between the status code and the backup source station and the response status code, the backup source station corresponding to the response status code includes:
selecting one backup source station from the plurality of different backup source stations;
and determining the selected backup source station as the backup source station corresponding to the response state code.
That is, in step 106, if the status code returned by the main source station satisfies that the same status code corresponds to multiple backup source stations, the upper node Cache randomly selects one of the multiple backup source stations to perform switching.
In an embodiment, in a case that the response status code simultaneously conforms to a single backup source station corresponding to a single status code and a status code in a predetermined range corresponds to the same backup source station, the determining, according to the correspondence between the preset status code and the backup source station and the response status code, the backup source station corresponding to the response status code includes:
and determining the backup source station corresponding to the response state code according to the corresponding relation of the single state code corresponding to the single backup source station.
That is, in step 106, if the status codes responded by the primary source station when the request fails simultaneously satisfy the precise matching of the status codes (a single status code corresponds to a single backup source station) and the range matching (status codes in a predetermined range correspond to the same backup source station), the precise matching takes effect. The exact match is that a single status code corresponds to a single backup source station, and a single different error status code corresponds to a single different switching backup source station, for example, 5xx switches to backup source station 1, 4xx switches to backup source station 2.
The status codes with the range matching as the predetermined range correspond to the same backup source station, for example, if the status code responded by the primary source station is 504, the corresponding matching configuration is (504: backup source station 1); (500-599: backup source station 2), after the main source station sends the response status code 504, the upper node switches the current source returning request determination to the backup source station 1 corresponding to the exact match, not to the backup source station 2 configured in the range.
In one embodiment, the method further comprises: and sending the response state code to the first node under the condition that the backup source station corresponding to the response state code is not determined according to the corresponding relation between the preset state code and the backup source station and the response state code.
That is, when the second request to return to the source sent to the primary source by the upper node fails, the response status code sent by the primary source does not appear in the source switching configuration, in other words, the response status code returned by the primary source does not meet the analyzed switching configuration condition, and the second request to return to the source cannot be switched to the backup source. The upper node finishes the current first feedback request of the first node, responds to the current first feedback request, sends the response status code sent by the main source station to the first node, and the first node feeds back the response status code to the user of the client so as to inform the user of the reason of the current request failure.
In one embodiment, after switching the second back-to-source request to the backup source station corresponding to the response status code, the method further includes: and receiving a response status code sent by the backup source station in response to the second source returning request, and sending the response status code to the first node under the condition that the second source returning request is determined to fail according to the response status code sent by the backup source station.
As described in step 108, in case that the primary source station fails to request, the source return request is switched to the backup source station to request the target resource again according to the response status code and the source station switching configuration. If the backup source station still has the condition of request error, the upper node directly sends the response status code sent by the backup source station to the first node, and the first node feeds back the response status code to the user of the client to inform the user of the reason of current request failure. That is, the switching to the backup source station is only 1 time, because the time for switching each time is too long, and the re-switching can cause the connection duration to increase, which causes the connection to be piled up and jammed, thereby bringing about serious consequences.
In one embodiment, the method further comprises: and under the condition that the target resource exists in the local cache, responding to the first source returning request to send the target resource to the first node.
That is to say, if the upper node hits the current first source back request, the corresponding target resource content is directly read from the disk and sent to the first node, for example, a middle node or an edge node of the CDN network.
In one embodiment, the method further comprises: and under the condition that the second source returning request is determined to be successful according to the response status code, responding to the first source returning request and sending the target resource to the first node.
That is, if the second back-source request sent by the upper node by the main source station hits, the corresponding target resource acquired from the main source station is sent to the first node.
In one embodiment, the source station switching configuration corresponding to the same domain name is only effective at the upper node and is not transmitted to the nodes of other layers, so that the flexibility of configuration can be improved.
According to the embodiment of the disclosure, when the main source station fails, the current source returning request failing to the main source station can be switched to the corresponding backup source station in time according to the corresponding relation between the response state code returned by the main source station and the preset state code and the backup source station, so that the current request is still effective, and the request is not required to be switched to the backup source station after the source returning request is received next time. Therefore, the switching of the request level can be realized, the source returning errors are reduced, and the influence of the failure of the request caused by the failure of the main source station is reduced.
In addition, the preset state code for switching the source stations in the embodiment of the present disclosure may support multiple matching manners, such as a single backup source station, multiple backup source stations, and a range backup source station, and support personalized configuration for configuring multiple switching conditions at the same time, so that the source stations have a consistent determination standard. Different backup source stations can be switched according to different errors of the source stations, and the control is more flexible. Compared with the prior art that only one corresponding backup source station is configured for the main source station during source station switching, the limitation of the prior backup source station switching is avoided.
< example >
Hereinafter, a source station switching method according to an embodiment of the present disclosure will be described as an example with reference to the flowcharts of fig. 3 to 4. Fig. 3 is a CDN back-source request flow chart according to the embodiment of the present disclosure, and fig. 4 is a CDN upper node structure diagram according to the embodiment of the present disclosure.
As shown in fig. 3, when a user 20 accesses a DNS (Domain Name System) 10, the DNS 10 converts www (World Wide Web) accessed by the user into a nearby IP and provides the nearby IP to the user. The user 20 initiates a request for target resources to the edge node 302 of the CDN network 30, and if the request is hit, the edge node 302 directly responds to the user request and returns the corresponding target resource, thereby completing an Http (hypertext transfer protocol) request. If the request is not hit, that is, the cache of the edge node 302 does not have the target resource corresponding to the request, the edge node 302 needs to send a back-source request to an upper node, for example, the middle node 304 of the CDN network 30, and if the request of the middle node 304 is still not hit, the middle node 304 needs to send a back-source request to the upper node 306 of the CDN network 30, and the upper node 306 sends the back-source request to the source station, which may be regarded as the main source station 40. The solid line shown in the flowchart of fig. 3 is a flow that is necessary for the source-back request (usually, the target resource requested by the user can be acquired at the edge node 302), and the dotted line is an optional flow. If the request at the current layer of the current node is hit, the current node does not send a source returning request to the node at the previous layer of the dotted line process.
In fig. 4, the upper node 306 is divided into a region of Nginx3062 and a region of Cache 3064. The LVS (balanced load System) 50 sends the back source request selection issued by the lower node to Nginx3062 and Cache 3064 of the upper node 306 of one of the groups.
When the Nginx3062 of the upper node 306 receives the back-source request of the middle node 304, the source station switching configuration for recording the corresponding relation between different state codes and the switched backup source station is packaged into a specified request header and is sent to the upper node Cache 3064.
The upper level node Cache 3064 receives the current request of the Nginx3062, and analyzes the request header to obtain the corresponding source station switching configuration. The upper node Cache 3064 forms a mapping table of the corresponding relationship between the state code obtained by the analysis and the corresponding switching backup source station, and stores the mapping table in the memory.
If the request is hit, the upper node Cache 3064 directly reads the target resource content of the request from the disk and sends the target resource content to the Nginx3062 of the local layer. Nginx3062 returns the target resource sent by Cache 3064 to user 20 through middle level node 304, edge node 302.
If the request is not hit, that is, there is no requested target resource in the disk of the upper node, the upper node Cache 3064 sends a back-source request for requesting the target resource to the main source station 40.
The main source station 40 responds to the source returning request and sends a response status code to the Cache 3064 of the upper node 30, and the Cache 3064 can judge whether the source returning request hits or whether the main source station successfully returns the target resource according to the response status code.
If the present request sent to the main source station 40 is hit, i.e. the source returning request is successful, the Cache 3064 receives the target resource sent by the main source station 40, and sends the received target resource to the present layer of Nginx 3062. Nginx3062 returns the target resource obtained from the primary source 40 to the user 20 through the middle tier node 304, the edge node 302.
If the current request sent to the master source station 40 is not hit, that is, the source returning request fails, the master source station 40 has a 4xx or 5xx fault, and after receiving the response status code returned by the master source station 40, the Cache 3064 determines whether the response status code matches with the status code in the analyzed source station switching configuration, that is, whether the same status code can be found from the switching configuration according to the response status code returned by the master source station 40 to determine that the corresponding request switches the backup source station.
If the switching configuration condition is not met, namely the response state code is not matched with the state code of the source station switching configuration, the source returning request is finished, and the Cache 3064 sends the response state code received from the main source station 40 for the last time to the Nginx3062 of the layer. The Nginx3062 returns the response status code returned by the master source station 40 to the user 20 through the middle level node 304, the edge node 302.
If the switching configuration condition is satisfied, that is, when the response status code matches the status code of the source station switching configuration, the upper node Cache 3064 switches the request to the backup source station (for example, the backup source station 1, the backup source station, or the backup source station n, which is determined according to the configuration specifically for switching the backup source station) corresponding to the status code in the source station switching configuration, and initiates the request back to the source again, and requests the target resource from the switched backup source station.
Similarly, if an error still occurs when the request is switched to the backup source station corresponding to the state code, the Cache 3064 directly sends the response state code returned by the corresponding backup source station to the upper node Nginx3062 and ends the request, and the Nginx3062 returns the response state code returned by the backup source station to the user 20 through the middle node 304 and the edge node 302.
< apparatus embodiment >
In another embodiment of the present disclosure, a source station switching apparatus 2000 is provided, as shown in fig. 5, which is a block diagram of a source station switching apparatus according to an embodiment of the present disclosure.
The source station switching apparatus 2000 includes: a first receiving module 2200, a sending module 2300, a second receiving module 2400, a determining module 2600, and a switching module 2700.
The first receiving module 2200 is configured to receive a first source returning request of a first node requesting a target resource, and the sending module 2300 is configured to send a second source returning request of the target resource to a primary source station when the target resource does not exist in a local cache. The second receiving module 2400 is configured to receive a response status code sent by the main source station in response to the second source return request, the determining module 2600 is configured to determine, according to a preset correspondence between a status code and a backup source station and the response status code, a backup source station corresponding to the response status code when the response status code determines that the second source return request fails, and the switching module 2700 is configured to switch the second source return request to the backup source station corresponding to the response status code, so as to request the target resource again.
In one embodiment, the apparatus 2000 further comprises: a first response module (not shown in the figure), configured to send the response status code to the first node according to the correspondence between the preset status code and the backup source station and when the response status code does not determine the backup source station corresponding to the response status code.
In one embodiment, the apparatus 2000 further comprises: a second response module (not shown in the figure), configured to receive a response status code sent by the backup source station in response to the second source returning request after the second source returning request is switched to the backup source station corresponding to the response status code, and send the response status code to the first node when it is determined that the second source returning request fails according to the response status code sent by the backup source station.
In one embodiment, the apparatus 2000 further comprises: a first resource sending module (not shown in the figure), configured to send the target resource to the first node in response to the first source-returning request when the target resource exists in a local cache.
In one embodiment, the apparatus 2000 further comprises: a second resource sending module (not shown in the figure), configured to send the target resource to the first node in response to the first source returning request, when it is determined that the second source returning request is successful according to the response status code.
In one embodiment, the correspondence between the preset status code and the backup source station includes: the single state code corresponds to a single backup source station, a plurality of different state codes correspond to the same backup source station, the state code in the preset range corresponds to the same backup source station, and the same state code corresponds to at least one of a plurality of different backup source stations.
In one embodiment, in the case that the response status code corresponds to one status code corresponding to a plurality of different backup source stations, the determining module 2600 is configured to:
selecting one backup source station from the plurality of different backup source stations;
and determining the selected backup source station as the backup source station corresponding to the response state code.
In one embodiment, when the plurality of different backup source stations have ports, the ports corresponding to the plurality of different backup source stations are the same.
In one embodiment, in a case that the response status code simultaneously conforms to a single status code corresponding to a single backup source and a predetermined range of status codes corresponding to the same backup source, the determining module 2600 is configured to:
and determining the backup source station corresponding to the response state code according to the corresponding relation of the single state code corresponding to the single backup source station.
< electronic apparatus >
According to still another embodiment of the present disclosure, there is also provided an electronic device, and the electronic device 3000 may be the electronic device 1000 shown in fig. 1. Fig. 6 is a block diagram of an electronic device according to an embodiment of the present disclosure.
In one aspect, the electronic device 3000 may include the source station switching apparatus 2000 described above, which is configured to implement the source station switching method according to any embodiment of the present disclosure.
On the other hand, as shown in fig. 6, the electronic device 3000 may include a memory 3200 and a processor 3400, the memory 3200 being for storing executable instructions; the instructions are used to control the processor 3400 to perform the source station switching method described above.
In this embodiment, the electronic device 3000 may be any electronic product or other terminal device having the memory 3200 and the processor 3400, such as a server, a tablet computer, a palmtop computer, a desktop computer, a notebook computer, a workstation, and the like.
< computer-readable storage Medium embodiment >
Finally, according to yet another embodiment of the present disclosure, there is also provided a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements a source station switching method according to any embodiment of the present disclosure.
The disclosed embodiments may be systems, methods, and/or computer program products. The computer program product may include a computer-readable storage medium having computer-readable program instructions embodied thereon for causing a processor to implement aspects of embodiments of the disclosure.
The computer readable storage medium may be a tangible device that can hold and store the instructions for use by the instruction execution device. The computer readable storage medium may be, for example, but not limited to, an electronic memory device, a magnetic memory device, an optical memory device, an electromagnetic memory device, a semiconductor memory device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a Static Random Access Memory (SRAM), a portable compact disc read-only memory (CD-ROM), a Digital Versatile Disc (DVD), a memory stick, a floppy disk, a mechanical coding device, such as punch cards or in-groove projection structures having instructions stored thereon, and any suitable combination of the foregoing. Computer-readable storage media as used herein is not to be construed as transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission medium (e.g., optical pulses through a fiber optic cable), or electrical signals transmitted through electrical wires.
The computer-readable program instructions described herein may be downloaded from a computer-readable storage medium to a respective computing/processing device, or to an external computer or external storage device via a network, such as the internet, a local area network, a wide area network, and/or a wireless network. The network may include copper transmission cables, fiber optic transmission, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. The network adapter card or network interface in each computing/processing device receives computer-readable program instructions from the network and forwards the computer-readable program instructions for storage in a computer-readable storage medium in the respective computing/processing device.
Computer program instructions for carrying out operations for embodiments of the present disclosure may be assembler instructions, Instruction Set Architecture (ISA) instructions, machine-related instructions, microcode, firmware instructions, state setting data, or source or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The computer-readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider). In some embodiments, aspects of the disclosed embodiments are implemented by personalizing an electronic circuit, such as a programmable logic circuit, a Field Programmable Gate Array (FPGA), or a Programmable Logic Array (PLA), with state information of computer-readable program instructions, which can execute the computer-readable program instructions.
Various aspects of the present disclosure are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the disclosure. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer-readable program instructions.
These computer-readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable medium storing the instructions comprises an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.
The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer, other programmable apparatus or other devices implement the functions/acts specified in the flowchart and/or block diagram block or blocks.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions. It is well known to those skilled in the art that implementation by hardware, implementation by software, and implementation by a combination of software and hardware are equivalent.
Having described embodiments of the present disclosure, the foregoing description is intended to be exemplary, not exhaustive, and not limited to the disclosed embodiments. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terminology used herein was chosen in order to best explain the principles of the embodiments, the practical application, or technical improvements to the market, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein. The scope of the embodiments of the present disclosure is defined by the appended claims.
Claims (12)
1. A source station switching method, implemented in an upper node, the method comprising:
receiving a first back source request of a first node for requesting a target resource;
under the condition that the target resource does not exist in the local cache, sending a second source returning request for requesting the target resource to the main source station;
receiving a response status code sent by the main source station in response to the second source returning request, and determining a backup source station corresponding to the response status code according to a corresponding relation between a preset status code and a backup source station and the response status code under the condition that the second source returning request is determined to be failed according to the response status code; and
and switching the second source returning request to a backup source station corresponding to the response state code to request the target resource again.
2. The method of claim 1, wherein the method further comprises:
and sending the response state code to the first node under the condition that the backup source station corresponding to the response state code is not determined according to the corresponding relation between the preset state code and the backup source station and the response state code.
3. The method of claim 1, wherein after switching the second back-source request to the backup source station corresponding to the response status code, the method further comprises:
and receiving a response status code sent by the backup source station in response to the second source returning request, and sending the response status code to the first node under the condition that the second source returning request is determined to fail according to the response status code sent by the backup source station.
4. The method of claim 1, wherein the method further comprises:
and under the condition that the target resource exists in the local cache, responding to the first source returning request and sending the target resource to the first node.
5. The method of claim 1, wherein the method further comprises:
and under the condition that the second source returning request is determined to be successful according to the response status code, responding to the first source returning request and sending the target resource to the first node.
6. The method of claim 1, wherein the correspondence between the preset status code and the backup source station comprises: the single state code corresponds to a single backup source station, a plurality of different state codes correspond to the same backup source station, the state code in the preset range corresponds to the same backup source station, and the same state code corresponds to at least one of a plurality of different backup source stations.
7. The method of claim 6, wherein, in a case that the response status code conforms to a plurality of different backup source stations corresponding to one status code, the determining the backup source station corresponding to the response status code according to the preset correspondence between the status code and the backup source station and the response status code comprises:
selecting one backup source station from the plurality of different backup source stations;
and determining the selected backup source station as the backup source station corresponding to the response state code.
8. The method of claim 6 or 7, wherein when the plurality of different backup source stations have ports, the ports corresponding to the plurality of different backup source stations are the same.
9. The method of claim 6, wherein, in a case that the response status code simultaneously conforms to a single status code corresponding to a single backup source station and a status code in a predetermined range corresponds to the same backup source station, the determining, according to the preset correspondence between the status code and the backup source station and the response status code, the backup source station corresponding to the response status code comprises:
and determining the backup source station corresponding to the response state code according to the corresponding relation of the single state code corresponding to the single backup source station.
10. A source station switching apparatus, implemented at an upper node, the apparatus comprising:
a first receiving module, configured to receive a first fallback request that a first node requests a target resource;
a sending module, configured to send a second source return request requesting the target resource to a primary source station when the target resource does not exist in a local cache;
a second receiving module, configured to receive a response status code sent by the master source station in response to the second source return request;
a determining module, configured to determine, when it is determined that the second request to return to source fails according to the response status code, a backup source station corresponding to the response status code according to a correspondence between a preset status code and the backup source station and the response status code; and
and the switching module is used for switching the second source returning request to the backup source station corresponding to the response state code so as to request the target resource again.
11. An electronic device, comprising:
the apparatus of claim 10; or,
a processor and a memory for storing executable instructions for controlling the processor to perform the method of any one of claims 1 to 9.
12. A computer-readable storage medium, characterized in that a computer program is stored thereon which, when being executed by a processor, carries out the method according to any one of claims 1 to 9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010225023.8A CN113452539B (en) | 2020-03-26 | 2020-03-26 | Source station switching method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010225023.8A CN113452539B (en) | 2020-03-26 | 2020-03-26 | Source station switching method and device, electronic equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113452539A CN113452539A (en) | 2021-09-28 |
| CN113452539B true CN113452539B (en) | 2022-07-19 |
Family
ID=77807607
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010225023.8A Active CN113452539B (en) | 2020-03-26 | 2020-03-26 | Source station switching method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113452539B (en) |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103036967A (en) * | 2012-12-10 | 2013-04-10 | 北京奇虎科技有限公司 | A download management device, method and data download system |
| CN107577550A (en) * | 2017-08-31 | 2018-01-12 | 北京奇安信科技有限公司 | A kind of whether abnormal method and device of response for determining access request |
| CN109286957A (en) * | 2018-08-15 | 2019-01-29 | 网宿科技股份有限公司 | A switching method, device, electronic device and storage medium for a back-to-source link |
| CN109639502A (en) * | 2018-12-30 | 2019-04-16 | 北京奇艺世纪科技有限公司 | Return operated control method and content distributing network |
| US10305955B1 (en) * | 2014-12-08 | 2019-05-28 | Conviva Inc. | Streaming decision in the cloud |
| CN110166800A (en) * | 2019-05-22 | 2019-08-23 | 北京奇艺世纪科技有限公司 | Video returns source method, system, device and computer readable storage medium |
| CN110392094A (en) * | 2019-06-03 | 2019-10-29 | 网宿科技股份有限公司 | A method for acquiring service data and a fusion CDN system |
| CN110825525A (en) * | 2019-11-06 | 2020-02-21 | 湖南快乐阳光互动娱乐传媒有限公司 | Data resource back-source method and device |
| US10581736B1 (en) * | 2018-11-13 | 2020-03-03 | At&T Intellectual Property I, L.P. | Traffic matrix prediction and fast reroute path computation in packet networks |
-
2020
- 2020-03-26 CN CN202010225023.8A patent/CN113452539B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103036967A (en) * | 2012-12-10 | 2013-04-10 | 北京奇虎科技有限公司 | A download management device, method and data download system |
| US10305955B1 (en) * | 2014-12-08 | 2019-05-28 | Conviva Inc. | Streaming decision in the cloud |
| CN107577550A (en) * | 2017-08-31 | 2018-01-12 | 北京奇安信科技有限公司 | A kind of whether abnormal method and device of response for determining access request |
| CN109286957A (en) * | 2018-08-15 | 2019-01-29 | 网宿科技股份有限公司 | A switching method, device, electronic device and storage medium for a back-to-source link |
| US10581736B1 (en) * | 2018-11-13 | 2020-03-03 | At&T Intellectual Property I, L.P. | Traffic matrix prediction and fast reroute path computation in packet networks |
| CN109639502A (en) * | 2018-12-30 | 2019-04-16 | 北京奇艺世纪科技有限公司 | Return operated control method and content distributing network |
| CN110166800A (en) * | 2019-05-22 | 2019-08-23 | 北京奇艺世纪科技有限公司 | Video returns source method, system, device and computer readable storage medium |
| CN110392094A (en) * | 2019-06-03 | 2019-10-29 | 网宿科技股份有限公司 | A method for acquiring service data and a fusion CDN system |
| CN110825525A (en) * | 2019-11-06 | 2020-02-21 | 湖南快乐阳光互动娱乐传媒有限公司 | Data resource back-source method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113452539A (en) | 2021-09-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11095711B2 (en) | DNS Resolution of internal tenant-specific domain addresses in a multi-tenant computing environment | |
| US10455011B2 (en) | Supporting heterogeneous environments during code deployment | |
| US20220318657A1 (en) | Artificial intelligence delivery edge network | |
| US9565265B2 (en) | Method and apparatus for automatically optimizing the loading of images in a cloud-based proxy service | |
| US9451046B2 (en) | Managing CDN registration by a storage provider | |
| EP3895401B1 (en) | Method and system for processing requests for content of a content distribution network | |
| US9313100B1 (en) | Remote browsing session management | |
| CN107181779B (en) | Method, device and system for processing access request | |
| CN112256495A (en) | Data transmission method and device, computer equipment and storage medium | |
| CN106657180B (en) | Information transmission method and device for cloud service, terminal equipment and system | |
| US11310340B2 (en) | Multiple geography service routing | |
| US12074918B2 (en) | Network-based Media Processing (NBMP) workflow management through 5G Framework for Live Uplink Streaming (FLUS) control | |
| US20210281637A1 (en) | Management for a load balancer cluster | |
| WO2022090847A1 (en) | Handling deferrable network requests | |
| JP2016144186A (en) | COMMUNICATION INFORMATION CONTROL DEVICE, RELAY SYSTEM, COMMUNICATION INFORMATION CONTROL METHOD, AND COMMUNICATION INFORMATION CONTROL PROGRAM | |
| US10977141B2 (en) | Systems and methods for handling server failovers | |
| US11381665B2 (en) | Tracking client sessions in publish and subscribe systems using a shared repository | |
| CN113452539B (en) | Source station switching method and device, electronic equipment and storage medium | |
| US11546405B2 (en) | Methods for exposing mainframe data as a web service and devices thereof | |
| CN114500484A (en) | Page rendering method, apparatus, electronic device and readable medium | |
| US11910412B2 (en) | Media sink capabilities description | |
| CN111490886B (en) | Network data processing method and system | |
| CN113259501A (en) | Website access method and device, electronic equipment and readable storage medium | |
| CN113453062A (en) | Video metadata obtaining and processing method, device and system and electronic equipment | |
| CN114253928A (en) | Access method and device for storage file |
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 |