CN117097801A

CN117097801A - Access method and system, CDN node, electronic equipment and storage medium

Info

Publication number: CN117097801A
Application number: CN202310921514.XA
Authority: CN
Inventors: 佘江宁
Original assignee: Wangsu Science and Technology Co Ltd
Current assignee: Wangsu Science and Technology Co Ltd
Priority date: 2023-07-25
Filing date: 2023-07-25
Publication date: 2023-11-21

Abstract

The embodiment of the application relates to the technical field of communication and discloses an access method and system, CDN nodes, electronic equipment and a storage medium. The access method is applied to CDN nodes and comprises the following steps: receiving an access request carrying user information and a target URL sent by a client; under the condition that the access request is determined to be in a waiting state according to the user information and the target URL, sending locally cached waiting room page data to the client side, and enabling the client side to present the waiting room page according to the waiting room page data; and in the case that the access request is determined to be in the connection permission state according to the user information and the target URL, forwarding the access request to a source station pointed by the target URL, and responding to the access request by the source station. At least to facilitate simultaneously guaranteeing the timeliness of the access requests.

Description

Access method and system, CDN node, electronic equipment and storage medium

Technical Field

The embodiment of the application relates to the technical field of communication, in particular to an access method and system, a CDN node, electronic equipment and a storage medium.

Background

Sudden increases in the incoming traffic of a web site may cause the web site to crash or the web site to severely degrade, such as slow loading of the web site. Resulting in a poor user experience and thus loss of sales for the retailer. To solve the above problems, a virtual waiting room technology has been developed, which is to shunt redundant users to waiting room pages when the traffic of a website is about to reach a bottleneck, so that user requests are sequentially processed and responded by a target website.

However, the access to the website is currently achieved based on the virtual waiting room technology with low timeliness, resulting in poor user experience.

Disclosure of Invention

The embodiment of the application provides an access method and system, CDN nodes, electronic equipment and storage media, which are at least beneficial to improving the timeliness of access requests, thereby improving user experience.

According to some embodiments of the present application, an aspect of the embodiments of the present application provides an access method, applied to a CDN node, the method including: receiving an access request sent by a client, wherein the access request carries user information and a target URL; under the condition that the access request is determined to be in a waiting state according to the user information and the target URL, sending locally cached waiting room page data to the client side, and enabling the client side to present the waiting room page according to the waiting room page data; and under the condition that the access request is determined to be in a connection permission state according to the user information and the target URL, forwarding the access request to a source station pointed by the target URL for the source station to respond to the access request.

According to some embodiments of the present application, another aspect of the embodiments of the present application further provides a CDN node, including: an edge application module and a waiting room page module; the edge application module is connected with the waiting room page module; the edge application module is used for realizing the access method according to any one of the above; the waiting room page module is used for maintaining locally cached waiting room page data of the CDN node so as to provide the locally cached waiting room page data for the edge application module.

According to some embodiments of the present application, another aspect of the embodiments of the present application further provides an access system, including: several CDN nodes as described previously.

According to some embodiments of the present application, another aspect of the embodiments of the present application further provides an electronic device, including: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the access method as described in any one of the embodiments above.

According to some embodiments of the present application, there is also provided a computer readable storage medium storing a computer program which, when executed by a processor, implements an access method as in any of the embodiments above.

The technical scheme provided by the embodiment of the application has at least the following advantages:

under the condition that an access request is received and the access request is determined to be in a waiting state according to user information and a target URL carried by the access request, the CDN node sends locally cached waiting room page data to the client instead of the waiting room page data acquired by returning to a source or accessing a third-party website and the like, so that the presentation of the waiting room page can be accelerated based on the local cache of the CDN node, and timeliness is ensured. And the processing pressure of the source station on the access request is shared by the processing of the access request by each CDN node, so that the bearing capacity of the access request is improved, the problems of unbalanced load and even unavailable service can be reduced, the adverse effect of the problems on the processing of the access request is reduced, and the timeliness of the access request is further improved.

Drawings

One or more embodiments are illustrated by way of example and not limitation in the figures of the accompanying drawings, in which like references indicate similar elements, and in which the figures of the drawings are not to be taken in a limiting sense, unless otherwise indicated.

FIG. 1 is a flow chart of an access method provided in an embodiment of the application;

FIG. 2 is another flow chart of an access method provided in an embodiment of the application;

FIG. 3 is another flow chart of an access method provided in an embodiment of the application;

FIG. 4 is another flow chart of an access method provided in an embodiment of the application;

FIG. 5 is another flow chart of an access method provided in an embodiment of the application;

FIG. 6 is another flow chart of an access method provided in an embodiment of the application;

FIG. 7 is another flow chart of an access method provided in an embodiment of the application;

FIG. 8 is another flow chart of an access method provided in an embodiment of the application;

FIG. 9 is another flow chart of an access method provided in an embodiment of the application;

FIG. 10 is a schematic diagram of a CDN node according to an embodiment of the present application;

FIG. 11 is a schematic diagram of another CDN node according to an embodiment of the present application;

FIG. 12 is a schematic diagram of an access system provided in an embodiment of the application;

fig. 13 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Detailed Description

According to the background technology, the timeliness of the access request is difficult to ensure when the website is accessed based on the virtual waiting room technology, and the user experience is affected.

The reasons for the above problems are found to be at least: the current virtual waiting room technology-based access to websites mainly relates to a centralized bill center-based virtual waiting room technology, which generally takes numbers from the bill center according to user initiated access, and then access requests are allowed to access websites under the condition of taking the numbers. However, the processing capacity of the bill center is limited, and it is difficult to process all received requests in time, and even the overflow may be caused by too many requests, which seriously affects the efficiency of taking numbers and the efficiency of accessing websites, so that the timeliness of the requests is poor. And, whether there is a sudden increase in traffic or not, it can introduce significant access latency and can also result in poor timeliness of the request.

In order to solve the above problems, the embodiments of the present application provide an access method and system, a CDN node, an electronic device, and a storage medium, where the CDN node processes an access request of a user, so that acceleration of processing the access request can be achieved based on a CDN architecture, particularly, the CDN node locally caches page data of a waiting room, so that a flow entering the waiting room can be accelerated, response delay is further reduced, read-write timeliness is improved, and by sharing a bearing pressure and a processing pressure of a source station to each CDN node, it is beneficial to reduce the access pressure of the page of the waiting room, improve the bearing capacity of the access request, facilitate timely processing of the access request, and also improve timeliness of the access request.

For the purpose of making the objects, technical solutions and advantages of the embodiments of the present application more apparent, the embodiments of the present application will be described in detail below with reference to the accompanying drawings. However, it will be understood by those of ordinary skill in the art that in various embodiments of the present application, numerous specific details are set forth in order to provide a thorough understanding of the present application. However, the claimed technical solution of the present application can be realized without these technical details and various changes and modifications based on the following embodiments.

The following embodiments are divided for convenience of description, and should not be construed as limiting the specific implementation of the present application, and the embodiments can be mutually combined and referred to without contradiction.

An aspect of the present application provides an access method applied to a content delivery network (Content Delivery Network, CDN) node. In some cases, the method is particularly applied to an edge application module in a CDN node. In this way, the access method provided by the embodiment of the application can be deployed into the CDN node in an edge application mode, and the CDN node equipment is not required to be changed, so that the cost is saved, the implementation difficulty is reduced, and the upgrading iteration of the method can be realized more efficiently and conveniently.

In some embodiments, the flow of the access method is as shown in fig. 1, and at least comprises the following steps:

step 101, receiving an access request sent by a client, wherein the access request carries user information and a target URL.

In the embodiment of the application, the user information can be any one or any information capable of uniquely determining a user, such as a user account name, a device identifier of a client, and the like. The target uniform resource locator (Uniform Resource Locator, URL) is the URL that the access request wants to access, where URL is the address pointing to the web site that the access request wants to access.

In some cases, the target URL may be any URL of a website providing a waiting room page, that is, it is not necessary to determine whether the website that the received access request needs to access provides a waiting mechanism, which is more efficient. In some cases, any URL may be used, and the website to which the URL points is not limited. At this time, whether the corresponding processing is performed or not can be determined by judging whether the website to be accessed by the received access request provides a waiting mechanism or not, so that the CDN node can uniformly receive and process the website whether the website is provided with a waiting room service or not, and the CDN node does not need to additionally set another process special for processing the access request initiated to the website which is not provided with the waiting room service, thereby realizing the uniformity of the processing processes of the requests for accessing different types of websites.

It will be appreciated that in the case where the target URL is any URL, the source station to which it points may be a website that provides waiting room services, or may be a website that does not provide waiting room services. At this time, the CDN node may be configured according to actual requirements, so that the CDN node may determine which type of URL needs to execute to continue to execute the subsequent step 102 and so on, so as to provide waiting room service, which type of URL does not need to execute to continue to execute the subsequent step 102 and so on, and may directly determine whether to return to the source according to a general response procedure of the CDN node, that is, by determining whether the access request hits in a cache.

That is, in some embodiments, after step 101, the access method further comprises: receiving a request sent by a client, analyzing a target URL carried by the request, detecting whether a source station pointed by the target URL is a website for providing waiting room service, and executing step 102 or step 103 under the condition that the source station pointed by the target URL is detected to be the website for providing waiting room service; in the event that the source station pointed to by the target URL is detected to be a website which does not provide waiting room service, detecting whether the access request is cached for hit or not so as to determine whether the access request is forwarded to a superior CDN node or the source station.

The form of the access request is not limited in the embodiment of the present application, and may be any form of request for initiating access to a URL, such as a hypertext transfer protocol (Hyper Text Transfer Protocol, HTTP) request, and the like, which will not be described in detail herein.

The access method is applied to the CDN node, so that the access request initiated by the client can be accelerated, balanced in load and the like based on the CDN node, the processing efficiency of the access request is improved compared with that of a centralized bill center, the processing pressure of the source station pointed by the target URL is born by the CDN node, the processing pressure of the source station is reduced, the bearing capacity of the access request is improved as a whole, access delay caused by poor bearing capacity is avoided, and therefore timeliness of the access request is improved.

Step 102, sending the locally cached waiting room page data to the client for the client to present the waiting room page according to the waiting room page data under the condition that the access request is determined to be in a waiting state according to the user information and the target URL.

In this embodiment, the waiting state characterizes a state in which the access request cannot be responded to by the source station immediately, that is, the access request needs to enter the waiting room to wait for a period of time before being responded to by the source station.

The embodiment does not limit the waiting room page data, and the waiting room page data can be any page data which can be perceived by a user to be in a waiting state after being presented.

In some embodiments, the waiting room pages may be shared by different users, i.e., the waiting room page data for different users is the same. Therefore, the data volume of waiting room page data to be maintained in CDN nodes can be reduced, the processing flow is simplified, and the processing efficiency is improved.

In some embodiments, the waiting room pages may also be different according to users, or according to the characteristics of the groups to which the users belong, so that different waiting room pages, that is, customized waiting room pages, are presented for different users at the client, that is, different waiting room services can be provided for the users, which is beneficial to improving the diversity and quality of service and improving the user experience.

Based on this, in some embodiments, as shown in fig. 2, in the case that the result of the query is that the access request is in a waiting state, the access method further includes the following steps:

step 104, determining custom page data according to custom reference information, wherein the custom reference information comprises at least one of the following information: connection conditions of user information and access requests.

The present embodiment does not limit the customized page data, but may be any page data related to the current access request, and at least some of the page customized data corresponding to the access request is different.

Accordingly, while sending the locally cached waiting room page data to the client, the access method further comprises the following steps: and sending the custom page data to the client.

In this way, at the client, it will be able to render a customized waiting room page from the waiting room page data and the custom page data. Meanwhile, the waiting room page data are stored independently, instead of being stored repeatedly based on different users, so that occupation of the waiting room page data to CDN cache is reduced.

In some examples, the page customization data may be specific information of the connection condition of the access request, and after the page customization data is presented, the current waiting number of the target URL, the waiting position of the access request, and the like can be displayed.

Therefore, the waiting room page data is locally buffered at the CDN node, so that the waiting room page data can be obtained without returning to the source or accessing a third party, acceleration based on the CDN node is realized, and timeliness of the access request is improved.

And step 103, forwarding the access request to a source station pointed by the target URL, and responding to the access request by the source station under the condition that the access request is determined to be in a connection permission state according to the user information and the target URL.

In this embodiment, the allowed connection state characterizes a state where the access request can be responded to by the source station immediately, i.e. the access request does not need to enter a waiting room to wait, but can be responded to by the source station immediately.

The present embodiment is not limited to an implementation manner of determining the state of the access request according to the user information and the target URL.

In some embodiments, as shown in fig. 3, after forwarding the access request to the source station pointed to by the target URL, the access method further comprises the steps of:

step 105, triggering a step of determining a target client after finishing the access to the target URL based on the access request; among other clients that are currently presenting a waiting room page based on access to a target URL, the time at which the target client requests access is earliest.

The target client described in the above embodiments is exemplified below for better understanding by those skilled in the art.

Assuming that k+1 access requests initiate access to the source station pointed by the target URL in a short time, and after the k access requests access the source station pointed by the target URL, the number of the requests accessed by the source station pointed by the target URL reaches the maximum number of the requests which can be borne, when the response of the request appears in the current accessed requests of the source station pointed by the target URL is completed, the step of taking the client which initiates the k+1 access requests as the corresponding target client is triggered because the k+1 access requests are the earliest of the remaining requests which still request access to the source station pointed by the target URL.

The embodiments of the present application do not limit how the earliest time of access request is determined and how the time of access request is recorded.

In some embodiments, the data table may be configured to record the time of access requested by each access request, and specifically, the recorded time may be a writing time of information related to the access request, so that when the source station pointed to by the target URL generates a request for completing the response, the target client is determined according to the recorded time.

In some embodiments, the access request may be given a sequence number according to the access time of each access request, where the reference number of the request that requests access before is small, and the reference number of the request that requests access after is large, so that when the source station pointed by the target URL presents a request that the response is completed, the target client may be determined according to the sequence number, which is not described in detail herein.

The information such as the time of access requested by each access request may be saved through a database, such as a local database of the CDN node, or an external database that may be accessed by invoking a related service, and so on.

And step 106, forwarding the request of the target client to the source station pointed by the target URL.

That is, the prior request will respond in advance, and respond to the access request according to the sequence of the request, so as to ensure the fairness of the service, and facilitate improving the user experience.

It can be understood that if the responses of the N access requests are completed simultaneously or near simultaneously, at this time, the resources of the source station corresponding to the N access requests are free and can be used to respond to another N access requests, and the other N access requests are still determined in the manner provided in the above embodiment, so that the N access requests of the previous request access will be preferentially forwarded to the source station pointed by the target URL, so that the previous request will be responded, ensuring the fairness of the service, and being beneficial to improving the user experience.

Of course, the foregoing is merely a specific illustration, and in some embodiments, the user information may also carry a priority identifier, and at this time, the target client may also be determined according to the priority indicated by the priority identifier. It will be appreciated that in order to better serve users, differentiated services may also be provided for different users, such as prioritizing them, in favor of meeting the higher timeliness requirements of a particular user for access requests.

In some embodiments, the waiting room page data carries data for timing triggering a request to access the target URL, so that the client, after receiving the waiting room page data, will timing trigger an access request to the target URL based on the data carried by the waiting room page data. Based on this, as shown in fig. 4, after sending the locally cached waiting room page data to the client, the access method further includes the following steps:

step 107, the receiving client side waits for the access initiated by the room page data timing to determine the state of the access request again and execute the corresponding steps according to the state of the access request until the access request is forwarded to the source station.

That is, the system also provides a function of timing refreshing in a waiting state, and timely finds the transition from the waiting state to the connection permission state of the access request by inquiring for a plurality of times, thereby timely realizing the response of the source station to the access request and avoiding overlong waiting time. The access request can be responded in time, and the user experience is improved.

It should be noted that, the client initiates access at regular time based on the waiting room page data, because the relevant data (it can be understood that the data is program code data in general) is carried in the waiting room page data, the action of initiating access again is automatically triggered to be implemented, so that the response to the access request can be timely implemented without perception of the user, and the client is not required to be changed, which is beneficial to improving user experience and reducing implementation cost and implementation difficulty.

Of course, the above-mentioned operation of triggering to initiate access again may be implemented under the condition that relevant data is not carried in the waiting room page data, and at this time, the client may initiate access to the target URL at regular time by using a program deployed by itself to implement a relevant function, which is beneficial to reducing the number of waiting room page data that needs to be maintained locally by the CDN node and reducing the occupation of storage space of the CDN node.

It should be noted that, in the process of determining the state of the access request at regular time and executing the corresponding steps according to the state of the access request, if the access request is still in a waiting state, it may also be detected whether the page data to be presented changes, if so, the changed page data is sent to the client, and if not, the data does not occur. If the connection condition of the target URL is detected to be changed, page data corresponding to the changed connection condition is sent to the client, otherwise, no action is performed. That is, the waiting condition is synchronized to the client in real time, so that the user can know the waiting condition in real time, and the user experience is improved.

In some embodiments, after sending the locally cached waiting room page data to the client, the access method further comprises the steps of: monitoring whether the client initiates access based on waiting room page data at regular time; and under the condition that the access initiated by the client based on the waiting room page data timing is not monitored within the first preset time period, updating the record corresponding to the access request so as to delete the record corresponding to the access request.

It will be appreciated that the user may give up accessing the target URL while waiting. When the user gives up access, the user may click on a give up access button provided by the waiting room page, and then the client notifies the CDN node of the give up request, and so on. At this time, if the CDN nodes are still refreshed at regular time, resource waste may be caused. Therefore, the above embodiment is beneficial to accurately adjusting redundancy of the waiting room by monitoring whether to initiate access again, finding out in time that the user gives up the access and making a deletion, and ensuring whether the queued user is still waiting for the source station pointed by the access target URL.

It should be noted that, the foregoing embodiment does not limit the value of the first preset duration, and may be determined according to the waiting requirement of the user, the number of waiting connections allowed by the source station, and the like. Of course, besides monitoring whether access is initiated again, whether the client terminal is connected in an interrupted manner, whether the client terminal sends a relevant message for giving up access or not, and the like can be monitored, so that relevant processing can be timely performed, resource waste is avoided, and the details are omitted.

In some embodiments, as shown in fig. 5, after forwarding the access request to the source station pointed to by the target URL, the access method further comprises the steps of:

and step 108, under the condition that the client side does not monitor that the client side initiates access based on the user information and the target URL within the second preset time period, updating the record corresponding to the access request so as to delete the record corresponding to the access request.

That is, after the connection is implemented, a valid time, that is, a second preset duration, is defined for the connection, and when access is initiated again within the valid time, the connection can still be used to continue to access the source station pointed by the target URL, and when the valid time is exceeded, the connection is not maintained, and the resources occupied by the connection are provided for other connections to be used, so that the connection can be effectively utilized, adverse effects on other connections can be reduced, and overlong occupation time of resources of the source station by a single connection is avoided, thereby being beneficial to establishment of other connections. The user experience is improved, and the recording pressure of the request information is reduced.

It should be noted that, in this embodiment, the specific value of the second preset duration is not limited, and may be determined according to the processing pressure of the source station, the number of requests currently in the waiting state, and the like, which will not be described in detail herein.

According to the access method provided by the embodiment, under the condition that the access request is received and the access request is determined to be in the waiting state according to the user information and the target URL carried by the access request, the CDN node sends the waiting room page data of the local cache to the client instead of the waiting room page data acquired by returning to the source or accessing a third-party website and the like, so that the presentation of the waiting room page can be accelerated based on the local cache of the CDN node, and timeliness is ensured. And the processing pressure of the source station on the access request is shared by the processing of the CDN nodes on the access request, so that the bearing capacity of the access request is improved, the problems of unbalanced load and even unavailable service can be reduced, and the timeliness of the access request is further improved.

In addition, the access method implemented on the CDN nodes can be actually regarded as that the function of the ticket center sinks from the ticket center to each CDN node close to the user side, compared with the currently provided virtual waiting room technology based on the centralized ticket center. Wherein, with respect to the ticket center, CDN nodes may be considered edges. That is, the access method provided by the embodiment of the application is realized by deploying the function of the bill center to the CDN node positioned at the edge of the user in the form of edge application, so that the access request can be received through the CDN node, the access request is driven to be processed locally on the CDN node, the delay of the access request is reduced, the timeliness of the access request is improved, and the processing pressure is reduced.

In addition to the aforementioned virtual waiting room technology based on a centralized ticket center, there is currently also a virtual waiting room technology based on a regional ticket center. When the access to the website is realized, firstly, the access initiated by the user is to the bill service provider in the area to which the user belongs to take the number, the bill service providers in different areas independently maintain the respective bill queues, and then, under the condition of taking the number, the access request is allowed to access the website. At this time, data consistency cannot be ensured, so that waiting room functions cannot be synchronously opened or closed, load imbalance of websites may be caused, and even service is not available.

To address the above, in some embodiments, CDN nodes are deployed with local databases that remain data synchronized with local databases of other CDN nodes. The local database is a database deployed locally on the CDN node.

Accordingly, as shown in fig. 6, after receiving the access request sent by the client, the access method further includes:

step 109, according to the user information and the target URL, a query is performed in the local database to determine whether the access request is in a waiting state.

In this embodiment, the local database stores user information, a target URL, and connection conditions related to the target URL, such as a user identifier, whether the user has established a connection with the target URL currently, a maximum number of connections allowed by the target URL currently, a maximum number of waiting connections allowed by the target URL currently, and so on, which will not be described in detail herein.

In this way, each CDN node synchronizes the data among the local databases, so that the global consistency of the user information, the target URL and related information thereof does not occur, and the problems of access errors and the like caused by idle unused numbers or different requests allocated with the same number among the numbers in use (i.e., the serial numbers of the requests waiting for the current access request) can be avoided.

In some embodiments, the querying in the local database based on the user information and the target URL may be achieved by: inquiring whether a client corresponding to the user information is in a state of establishing connection with the target URL or not in a local database according to the user information and the target URL; and under the condition that the client corresponding to the user information is not in a state of establishing connection with the target URL, inquiring the connection condition of the target URL in a local database according to the target URL. Accordingly, after the query is performed in the local database according to the user information and the target URL, the access method further includes: and determining whether the access request is in a waiting state according to the connection condition of the target URL.

It should be noted that, the client may initiate access to different URLs in a short time, i.e. the local database may have connection states of the same user information about multiple URLs. When a client initiates access to a target URL, namely, an access request carrying the target URL is sent, whether connection between the client and the corresponding URL exists among the connections of the plurality of URLs or not by the same user information exists in a local database, and at the moment, whether the client corresponding to the user information is in a connection establishment state with the target URL or not is inquired, and other URLs are not needed. Based on this, in some embodiments, the local database has relevant information about whether a specific URL establishes a connection between the client and the URL, where there is no interference of multiple URLs, and no query using the target URL is required, which will not be described in detail herein.

In some embodiments, according to the connection condition of the target URL, determining whether the access request is in a waiting state may be implemented by: determining that the access request is in a connection permission state under the condition that the connection of the target URL is not full; in the case where the connection of the target URL is full, the access request is determined to be in a waiting state.

To facilitate a better understanding of the above embodiments by those skilled in the art, the following will illustrate the querying and determining the status of an access request.

First, according to user information and a target URL, whether a client corresponding to the user information establishes connection with a source station pointed by the target URL or not is determined. If yes, the access initiated by the client can be directly responded, and the access request is in an operation connection state without waiting; if not, it is necessary to further confirm whether the source station to which the target URL points can access the access request. Specifically, firstly, inquiring the number of the current accessed requests of the source station pointed by the target URL, namely the connection condition of the target URL, according to the target URL; and then determining whether the upper limit of the number of requests which can be carried by the source station pointed by the target URL is reached or not according to the number of the accessed requests of the source station pointed by the inquired target URL, namely determining whether the connection of the target URL is full or not. If yes, determining that the access request is in a waiting state, and if not, determining that the access request is in an operation connection state.

That is, the above embodiment makes the request to be processed by the source station pointed by the target URL not exceed its carrying capacity by the upper limit of the number of requests that can be carried by the source station pointed by the target URL, so as to ensure that the source station pointed by the target URL can respond to the connected request with enough resources, avoid excessively long waiting time or invalid waiting time of the user, improve the response quality, and further improve the user experience. Of course, the foregoing is merely illustrative of the query and the determination of the state of the access request based on the query result, and may be implemented in other embodiments or examples in other manners, which will not be described herein in detail.

It should be noted that, when the number of access requests in the waiting state is too large, the waiting time of the subsequent access requests entering the waiting state may be too long. At this time, in order to further avoid the excessively long waiting time of the user, a rejecting state may be set for the access request, specifically, the number of the access requests of the source station pointed by the target URL reaches the upper limit, and after the request in the waiting state reaches the upper limit, the received access request is not in the waiting state but is in the rejecting state.

In some embodiments, the data in the local database of the CDN node is stored in a Key-Value (KV) form, that is, the local database is a KV database, so that the query can be completed more efficiently, and the data maintenance of the local database and the data center is facilitated.

Based on this, in some embodiments, as shown in fig. 7, querying in the local database according to the user information and the target URL may include the following steps:

step 1091, generating a user identifier according to the user information, where the user identifier is used to uniquely identify the user information.

The user identifier is not limited in this embodiment, and may be a character string or a label, which will not be described in detail herein.

Step 1092, query is performed in the local database according to the user identification and the target URL.

Correspondingly, the access method further comprises the steps of:

in step 1010, in case of failure in querying according to the user identifier, querying the local database for the connection condition of the target URL and updating the user identifier, the target URL and the connection condition of the target URL in KV form.

In this embodiment, the target URL is an address pointing to the website to be accessed. The connection condition of the target URL may be one or more of the connection number, the waiting connection number, the upper limit of the connection number, etc. of the target URL, or may be a status flag bit for indicating whether the upper limit of the connection number is reached or whether the upper limit of the waiting connection number is reached, etc., which will not be described in detail herein.

It can be understood that the user information may include various information, the efficiency of querying through the various information is relatively low, and the user information is converted into the user identification of the unique identification user information and then written into the local database in KV form, so that the querying can be simplified, the querying efficiency is improved, the maintenance difficulty is reduced, and the error probability is reduced.

Of course, the local database is KV database and is merely an example of a local database, and in some embodiments, the local database may also be an online transaction (On-Line Transaction Processing, OLTP) database, or the like.

In some embodiments, data synchronization between local databases of each CDN node is achieved through the same data center that they are commonly connected to. That is, the local database of each CDN node may be considered as a plurality of edge databases centered on the data center, except that the databases are distributed across different CDN nodes. In this way, the data synchronization between the local databases of each CDN node is realized through the push mechanism and the subscription mechanism of the data center.

In some embodiments, as shown in fig. 8, the access method further comprises:

in step 1011, when the local database is updated, the updated data is sent to the data center, so that the data center pushes the received updated data to the local databases of other CDN nodes subscribed to the updated data.

That is, data synchronization is allowed from the local database to the data center to the local database.

It should be noted that, the present embodiment does not limit the case of sending updates to the local database, and may be any update caused by a corresponding change in data sending in the local database due to a related change of an access request on a CDN node where the local database is located. For example, writing information related to a certain access request, deleting information related to a certain access request, changing a certain access request from a waiting state to a connection-allowed state, and the like may be the case where a local database transmits an update.

For example, since the procedure of forwarding the request of the target client to the source station pointed by the target URL in step 106 provided in the foregoing embodiment is essentially that the target client transitions from the waiting state to the connection permission state, it is necessary to update the waiting state corresponding to the target client to the connection permission state in time, and at this time, if the state information corresponding to the user is saved based on the local database, it is presented that the local database is updated with data.

It will be appreciated that, in addition to the situation where the local database changes actively, there may be situations where the local database changes passively, i.e. the data of the data center changes first. At this time, the data center actively transmits data to each local database to realize data synchronization. If the connection condition of the target URL changes, the source station notifies the data center of the change, and at the moment, the data center also notifies each local database of the change.

Based on this, in some embodiments, as shown in fig. 9, the access method further includes:

step 1012, receiving the synchronous data pushed by the data center through the local database and synchronizing to the local database under the condition that the connection condition of the target URL is changed, wherein the synchronous data is obtained by the data center according to the change of the connection condition of the target URL.

That is, data synchronization from the data center to the local databases of each CDN node is allowed.

In some embodiments, data synchronization is allowed between the local database of the CDN node to the local database of each other CDN node, and data synchronization is allowed between the data center to the local database of each CDN node.

It should be noted that the foregoing is merely illustrative of the data pushing and subscribing process between the data center and each local database, and may be implemented in other manners in some embodiments, for example, timing synchronization data, etc., which will not be described herein.

The above steps of the methods are divided, for clarity of description, and may be combined into one step or split into multiple steps when implemented, so long as they include the same logic relationship, and they are all within the protection scope of this patent; it is within the scope of this patent to add insignificant modifications to the algorithm or flow or introduce insignificant designs, but not to alter the core design of its algorithm and flow.

Another aspect of the embodiments of the present application further provides a CDN node, as shown in fig. 10, where CDN node 1000 includes: an edge application module 1001 and a waiting room page module 1003; the edge application module 1001 is connected to the waiting room page module 1003, respectively.

The edge application module 1001 is configured to implement the access method provided in any one of the foregoing embodiments;

the waiting room page module 1003 is configured to maintain locally cached waiting room page data of the CDN node 1000, so as to provide the locally cached waiting room page data to the edge application module 1001.

It should be noted that, in the foregoing embodiment, by disposing the edge application module 1001 on the CDN node 1000, after the CDN node receives the access request, the edge application module 1001 drives itself and the waiting room page module 1003 to implement corresponding actions, so as to cooperate with each other to complete the access method provided in any one of the foregoing method embodiments.

That is, the CDN node provided in the embodiment of the present application is actually formed by deploying the function of the ticket center to the CDN node located on the user side (i.e., the edge) in the form of edge application, and at this time, the CDN node can be driven to locally process the access request by receiving the access request, thereby reducing the delay of the access request, improving the timeliness of the access request, and simultaneously reducing the processing pressure.

In some embodiments, as shown in fig. 11, CDN node 1000 further includes an edge database service module 1002.

The local database 1004 is deployed in the edge database service module 1002, and data synchronization is performed between the local database 1004 deployed in the edge database service module 1002 and the local databases 1004 deployed in the edge database service modules 1002 of other CDN nodes 1000;

the edge database service module 1002 is connected to the edge application module 1001, and is configured to maintain a local database of the CDN node 1000, so as to provide a database service to the edge application module 1001.

In this way, through the data synchronization of the local databases among the CDN nodes 1000, the strong consistency of information such as global request states is ensured, the access accuracy is favorably provided, and the problem of overlong waiting time caused by wrong number fetching, number jumping and the like is avoided.

In some embodiments, as shown in fig. 12, the edge database service module of the CDN node 1000 is connected to the same data center 2000 as the edge database service modules 1002 of other CDN nodes 1000 through an on-premise local database 1004.

It should be noted that, in the case where the local database is disposed outside the edge database service module 1002, the local database may subscribe only to the data center 2000 for the relevant data of the access request described in the above embodiment, so as to efficiently synchronize and alleviate the processing pressure of the local database.

In this way, through the data center 2000, the CDN nodes 1000 can implement data synchronization with concise deployment and low difficulty, which is beneficial to widely applying various different access scenarios and reducing cost.

It is to be noted that this embodiment is a node embodiment corresponding to the method embodiment, and this embodiment may be implemented in cooperation with the method embodiment. The related technical details mentioned in the method embodiment are still valid in this embodiment, and in order to reduce repetition, they are not described here again. Accordingly, the related technical details mentioned in the present embodiment may also be applied in the method embodiment.

In another aspect, an embodiment of the present application further provides an access system, as shown in fig. 11, where the access system includes: a number of CDN nodes 1000 as described in any of the embodiments above.

It should be noted that, in fig. 12, in order to present the relationship between the CDN nodes 1000 in the system, a case where each CDN node 1000 is deployed with an edge database service module 1002, and the edge database service modules 1002 are connected to the same data center 2000 through respective internal deployed local databases 1004 to maintain data synchronization is illustrated. The database 2000 may be considered as a part of the access system, or may be considered as another structure independent of the access system, and will not be described herein.

However, in some embodiments, the access system may not implement data synchronization through the data center 2000, and the edge database service module 1002 of each CDN node 1000 is not required to connect to the data center 2000 through the respective local database 1004.

It should be noted that this embodiment is a system embodiment corresponding to the node embodiment, and this embodiment may be implemented in conjunction with the method embodiment. The related technical details mentioned in the method embodiment are still valid in this embodiment, and in order to reduce repetition, they are not described here again. Accordingly, the related technical details mentioned in the present embodiment may also be applied in the method embodiment.

The embodiments described above will be exemplified below for better understanding by those skilled in the art.

In the case that the client 3000 needs to access the target URL, a corresponding access request is generated, the edge application module 1001 receives the access request sent by the client 3000, parses the target URL carried by the access request, and then the edge application module 1001 detects, according to the preconfigured information, whether the source station pointed by the target URL is provided with the waiting room service.

In the case where the source station pointed by the target URL is provided with a waiting room service, the edge application module 1001 forwards the access request to the edge database service module 1002, and the edge database service module 1002 generates a user identifier according to the user information and performs a query in the deployed local database 1004 based on the user identifier, and returns the data obtained by the query to the edge application module 1001.

The edge application module 1001 first determines whether the query fails after receiving the query result.

If the query fails, it indicates that the access request has no record, and the edge application module 1001 further determines according to the connection condition of the target URL, that is, the connection number of the target URL and the waiting connection number. Specifically:

determining that the access request is in a refused state under the condition that the connection number of the target URL and the waiting connection number reach the upper limit, and refusing the access request; when the number of connections of the target URL reaches the upper limit and the number of waiting connections does not reach the upper limit, determining that the access request is in a waiting state, acquiring waiting room page data from the waiting room page module 1003, and returning the waiting room page data to the client 3000; and if the connection number of the target URL and the waiting connection number do not reach the upper limit, determining that the access request is in a connection permission state, forwarding the access request to the source station 4000 pointed by the target URL, and responding to the access request by the source station 4000.

In the case of failed query, the local database 1004 may also be written with user information, the target URL, and the connection condition of the queried target URL, and may be synchronized to other CDN nodes 1000 through subscription and push functions of the data center.

If the query is successful, it indicates that the access request has a record, and the edge application module 1001 further determines whether the access request is in a connected state. Specifically:

if in the connected state, the edge application module 1001 determines that the access request is in a connection-enabled state, forwards the access request to the source station 4000 pointed to by the target URL, and the source station 4000 responds to the access request. If not, the edge application module 1001 further determines according to the connection condition of the target URL, that is, the connection number of the target URL. Specifically:

when the number of connections of the target URL reaches the upper limit, the edge application module 1001 determines that the access request is in a waiting state, and forwards the access request to the waiting room page module 1003; if the connection number of the target URL does not reach the upper limit, the access request is determined to be in a connection permission state, and the access request is forwarded to the source station 4000 pointed to by the target URL, and the source station 4000 responds to the access request.

When the access request has no record, the edge application module 1001 further notifies the edge database service module 1002 to write information such as the user identifier and the state of the access request into the local database 1004 in KV after determining the state of the access request. In the case where the access request is queried for a wait state and it is determined that the access request is currently in a connection-allowed state, the edge application module 1001 notifies the edge database service module 1002 to update the state of the access request in the local database 1004.

When the data in the local database 1004 is updated, the edge database service module 1002 will report the updated data to the data center 2000, so that the data center 2000 will send the updated data to the edge database service modules 1002 of other CDN nodes 1000, thereby implementing the update of the local databases 1004 of other CDN nodes.

The client 3000, after receiving the waiting room page data returned by the waiting room page module 1003, will initiate the access request again at regular time, and the edge application module 1001 will perform the above steps again until the access request is forwarded to the source station 4000 pointed to by the target URL. Meanwhile, the edge application module 1001 sets a timeout time, i.e. a first preset duration, for the access request after returning the waiting room page data to the client 300, and considers that the user exits waiting once the client is not refreshed within the timeout time.

In addition, the edge application module 1001 sets a timeout period, i.e. a second preset duration, for the access request after the access request is changed from the waiting state to the connection permission state, and once the request carrying the user information and the target URL is received within the timeout period, notifies the edge database service module 1002 to delete the information related to the access request in the local database 1004.

After the current access request finishes responding, it is determined that the client 3000 corresponding to the earliest record time in the request waiting for accessing the target URL recorded in the local database 1004 is the target client, the edge application module 1001 forwards the access request corresponding to the target client to the source station 4000 pointed to by the target URL, and notifies the edge database service module 1002 to modify the state of the access request corresponding to the target client in the local database 1004 to be the connection permission state. And as described above, the state of the access request corresponding to the target client is synchronized to the local database 1004 of other CDN nodes in the allowed connection state.

Of course, the above examples do not relate to all the above embodiments, and the above embodiments may be combined into the above examples without contradiction, and will not be described here again.

It should be noted that, each module involved in this embodiment is a logic module, and in practical application, one logic unit may be one physical unit, or may be a part of one physical unit, or may be implemented by a combination of multiple physical units. In addition, in order to highlight the innovative part of the present application, units less closely related to solving the technical problem presented by the present application are not introduced in the present embodiment, but it does not indicate that other units are not present in the present embodiment.

Another aspect of the embodiment of the present application further provides an electronic device, as shown in fig. 13, including: at least one processor 1301; and a memory 1302 communicatively coupled to the at least one processor 1301; the memory 1302 stores instructions executable by the at least one processor 1301, the instructions being executable by the at least one processor 1301 to enable the at least one processor 1301 to perform the access method described in any of the method embodiments described above.

Where memory 1302 and processor 1301 are connected by a bus, the bus may comprise any number of interconnected buses and bridges, the buses connecting the various circuits of the one or more processors 1301 and memory 1302 together. The bus may also connect various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface between the bus and the transceiver. The transceiver may be one element or may be a plurality of elements, such as a plurality of receivers and transmitters, providing a means for communicating with various other apparatus over a transmission medium. The data processed by the processor 1301 is transmitted over a wireless medium via an antenna, which further receives the data and transmits the data to the processor 1301.

Processor 1301 is responsible for managing the bus and general processing and may provide various functions including timing, peripheral interfaces, voltage regulation, power management, and other control functions. And memory 1302 may be used to store data used by processor 1301 in performing operations.

Another aspect of the embodiments of the present application also provides a computer-readable storage medium storing a computer program. The computer program implements the above-described method embodiments when executed by a processor.

That is, it will be understood by those skilled in the art that all or part of the steps in implementing the methods of the embodiments described above may be implemented by a program stored in a storage medium, where the program includes several instructions for causing a device (which may be a single-chip microcomputer, a chip or the like) or a processor (processor) to perform all or part of the steps in the methods of the embodiments of the application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

It will be understood by those of ordinary skill in the art that the foregoing embodiments are specific examples of carrying out the application and that various changes in form and details may be made therein without departing from the spirit and scope of the application.

Claims

1. An access method, applied to a CDN node, comprising:

receiving an access request sent by a client, wherein the access request carries user information and a target URL;

under the condition that the access request is determined to be in a waiting state according to the user information and the target URL, sending locally cached waiting room page data to the client side, and enabling the client side to present the waiting room page according to the waiting room page data;

and under the condition that the access request is determined to be in a connection permission state according to the user information and the target URL, forwarding the access request to a source station pointed by the target URL for the source station to respond to the access request.

2. The access method according to claim 1, wherein the CDN nodes are deployed with local databases that are kept data-synchronized with local databases of other CDN nodes;

after receiving the access request sent by the client, the method further comprises:

and according to the user information and the target URL, inquiring in a local database to determine whether the access request is in a waiting state.

3. The access method according to claim 2, wherein the local databases of the CDN nodes are connected to the same data center as the local databases of other CDN nodes;

the method further comprises the steps of:

and under the condition that the local database is updated, sending the updated data to the data center, and pushing the received updated data to the local databases of the other CDN nodes subscribing to the updated data by the data center.

4. An access method according to claim 3, characterized in that the method further comprises:

and under the condition that the connection condition of the target URL is changed, receiving synchronous data pushed by the data center through a local database and synchronizing the synchronous data to the local database, wherein the synchronous data is obtained by the data center according to the change of the connection condition of the target URL.

5. The access method according to claim 2, wherein the data in the local database of the CDN node is stored in the form of a key value, and the querying in the local database according to the user information and the target URL includes:

generating a user identifier according to the user information, wherein the user identifier is used for uniquely identifying the user information;

Inquiring in a local database according to the user identification and the target URL;

the method further comprises the steps of:

and under the condition that the query according to the user identification fails, querying the connection condition of the target URL in a local database and updating the connection condition of the user identification, the target URL and the target URL into the local database in the form of key values.

6. The access method according to claim 2, wherein said querying in a local database based on said user information and said target URL comprises:

inquiring whether the client corresponding to the user information is in a state of establishing connection with the target URL in a local database according to the user information and the target URL;

under the condition that the client corresponding to the user information is not in a state of establishing connection with the target URL, inquiring the connection condition of the target URL in a local database according to the target URL;

after the query is performed in the local database according to the user information and the target URL, the method further includes:

and determining whether the access request is in a waiting state according to the connection condition of the target URL.

7. The access method according to claim 6, wherein the determining whether the access request is in a waiting state according to the connection condition of the target URL includes:

determining that the access request is in a connection permission state under the condition that the connection of the target URL is not full;

and determining that the access request is in a waiting state when the connection of the target URL is full.

8. The access method according to any one of claims 1 to 7, wherein in the case where the access request is determined to be in a waiting state from the user information and the target URL, the method further comprises:

determining custom page data based on custom reference information, the custom reference information including at least one of: the connection condition of the user information and the access request;

while the locally cached waiting room page data is sent to the client, the method further comprises:

and sending the customized page data to the client.

9. The access method according to any one of claims 1 to 7, wherein after said forwarding the access request to the source station to which the target URL points, the method further comprises:

Triggering a step of determining a target client after the access to the target URL based on the access request is ended; among other clients currently presenting the waiting room page based on access to the target URL, the target client requesting access is the earliest;

forwarding the request of the target client to the source station pointed to by the target URL.

10. The access method of claim 9, wherein after the step of triggering the determination of the target client, the method further comprises:

and updating the waiting state corresponding to the target client to an allowed connection state.

11. The access method according to any one of claims 1 to 7, wherein the waiting room page data carries data for triggering a request to access the target URL at a timing, and wherein after the locally cached waiting room page data is transmitted to the client, the method further comprises:

and receiving access initiated by the client based on the waiting room page data at fixed time to determine the state of the access request again and execute corresponding steps according to the state of the access request until the access request is forwarded to the source station.

12. The access method of claim 11, wherein after the sending of the locally cached waiting room page data to the client, the method further comprises:

monitoring whether the client initiates access based on the waiting room page data at regular time;

and under the condition that the access initiated by the client based on the waiting room page data in a timing manner is not monitored within a first preset time period, updating the record corresponding to the access request so as to delete the record corresponding to the access request.

13. The access method according to any one of claims 1 to 7, wherein after said forwarding the access request to the source station to which the target URL points, the method further comprises:

and under the condition that the client side does not monitor that the client side initiates access based on the user information and the target URL within a second preset time period, updating the record corresponding to the access request so as to delete the record corresponding to the access request.

14. A CDN node, comprising: an edge application module and a waiting room page module; the edge application module is connected with the waiting room page module;

The edge application module is configured to implement the access method according to any one of claims 1 to 13;

the waiting room page module is used for maintaining locally cached waiting room page data of the CDN node so as to provide the locally cached waiting room page data for the edge application module.

15. The CDN node of claim 14, further comprising an edge database service module;

the edge database service module is internally provided with a local database, and the local database arranged in the edge database service module is in data synchronization with the local databases arranged in the edge database service modules of other CDN nodes;

the edge database service module is connected with the edge application module and used for maintaining a local database deployed inside so as to provide database services for the edge application module.

16. The CDN node of claim 15, wherein the edge database service module of the CDN node is connected to the same data center as the edge database service modules of other CDN nodes through an on-premise local database.

17. An access system, comprising: the CDN node of any one of claims 14 to 16.

18. An electronic device, comprising:

at least one processor; the method comprises the steps of,

a memory communicatively coupled to the at least one processor; wherein,

the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the access method of any one of claims 1 to 13.

19. A computer readable storage medium storing a computer program, wherein the computer program when executed by a processor implements the access method according to any one of claims 1 to 13.