CN114338689A - Session holding method, apparatus, device, medium, and program product - Google Patents
Session holding method, apparatus, device, medium, and program product Download PDFInfo
- Publication number
- CN114338689A CN114338689A CN202111680316.6A CN202111680316A CN114338689A CN 114338689 A CN114338689 A CN 114338689A CN 202111680316 A CN202111680316 A CN 202111680316A CN 114338689 A CN114338689 A CN 114338689A
- Authority
- CN
- China
- Prior art keywords
- session
- target server
- identifier
- application
- request
- 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.)
- Pending
Links
Images
Abstract
The present disclosure provides a session holding method, apparatus, device, storage medium and program product applied to a load balancing device, relating to the financial field or other fields. The method comprises the following steps: receiving a session request sent by a user operating a first application, wherein the session request comprises a first identifier used for determining the user; establishing an incidence relation between the first identification and a target server address; sending the session request to a target server so that the target server establishes a first session based on the session request; wherein, in a case where the user operates the first application to invoke a second application, the load balancing device maintains the first session with the target server based on the association relationship. The disclosure also provides a session holding method, device, equipment, storage medium and program product applied to the first application and the second application respectively.
Description
Technical Field
The present disclosure relates to the financial and other fields, and more particularly, to a session holding method, apparatus, device, medium, and program product.
Background
Session maintenance, for example, refers to identifying the association of the interaction process between an application and a server, and while load balancing is performed, it is also ensured that a series of related access requests are distributed to the same server in one session. In the related art, the session between the same application and the server is usually maintained, and when two applications access each other, if the two applications stay in the called application for too long, the session may be overtime.
Disclosure of Invention
In view of the above, the present disclosure provides a method, apparatus, device, medium, and program product capable of session maintenance when two applications access each other.
One aspect of the embodiments of the present disclosure provides a session holding method, which is applied to a load balancing device, and includes: receiving a session request sent by a user operating a first application, wherein the session request comprises a first identifier used for determining the user; establishing an incidence relation between the first identification and a target server address; sending the session request to a target server so that the target server establishes a first session based on the session request; wherein, in a case where the user operates the first application to invoke a second application, the load balancing device maintains the first session with the target server based on the association relationship.
According to an embodiment of the present disclosure, the establishing an association relationship between the first identifier and a target server address includes: and generating a second identifier based on the first identifier, and establishing an association relation between the second identifier and the target server address.
According to an embodiment of the present disclosure, in a case where the user operates the first application to invoke a second application, the load balancing device maintaining the first session with the target server based on the association relationship includes: receiving a session maintaining request sent by the second application, wherein the session maintaining request comprises the second identifier and the identifier of the first session; determining the target server address from the incidence relation based on the second identification; sending the session maintenance request to the target server based on the target server address to cause the target server to update the timestamp of the first session according to the identification of the first session to maintain the first session.
According to an embodiment of the present disclosure, after the target server establishes the first session based on the session request, the target server synchronizes the first session to a distributed storage system, and the method further includes: in the event that the session-holding request is not sent to the target server based on the target server address, updating a timestamp of the first session in a distributed storage system based on the identification of the first session to hold the first session.
According to an embodiment of the present disclosure, the establishing an association relationship between the second identifier and the target server address includes: writing the second identification and the target server address into a cookie file, wherein the cookie file corresponds to the session request.
Another aspect of the embodiments of the present disclosure provides a session holding method, applied to a first application, including: sending a session request to a load balancing device in response to a first operation of a user, wherein the session request comprises a first identifier for determining the user; receiving an identification of a first session, wherein the load balancing device is configured to establish an association between the first identification and a target server address, and the target server is configured to establish the first session in response to the session request sent by the load balancing device; in response to a second operation of the user, invoking a second application, wherein in the event of invoking the second application, the load balancing device is configured to maintain the first session with the target server based on the association relationship.
According to an embodiment of the present disclosure, the method further includes receiving a second identifier, specifically including: receiving a cookie file, wherein the cookie file comprises the second identifier and the target server address written by the load balancing device, and the cookie file corresponds to the session request.
According to an embodiment of the present disclosure, the load balancing device is configured to generate a second identifier based on the first identifier, establish an association relationship between the second identifier and a target server address, and the invoking a second application in response to a second operation of the user includes: and sending a call request to the second application in response to the second operation, wherein the call request comprises the second identifier and the identifier of the first session.
Another aspect of the embodiments of the present disclosure provides a session holding method, applied to a second application, including: receiving a call request sent by a user operating a first application, wherein the call request comprises a second identifier and an identifier of a first session; sending a session maintaining request to a load balancing device, wherein the session maintaining request comprises the second identifier and the identifier of the first session, and the load balancing device is configured to maintain the first session with a target server based on the association relationship between the second identifier and the address of the target server after receiving the session maintaining request; wherein the first application is configured to send a session request to the load balancing device before sending the invocation request, wherein the session request includes a first identifier for determining the user; the load balancing device is configured to generate the second identity based on the first identity and establish the association between the second identity and the target server address, the target server being configured to establish the first session in response to a session request sent by the load balancing device.
Another aspect of the embodiments of the present disclosure provides a session holding apparatus, applied to a load balancing device, including: the device comprises a first receiving module, a second receiving module and a processing module, wherein the first receiving module is used for receiving a session request sent by a user operating a first application, and the session request comprises a first identifier used for determining the user; the association establishing module is used for establishing an association relation between the first identifier and the target server address; the first sending module is used for sending the session request to a target server so that the target server establishes a first session based on the session request; wherein, in a case where the user operates the first application to invoke a second application, the load balancing device maintains the first session with the target server based on the association relationship.
Another aspect of the disclosed embodiments provides a session holding apparatus, applied to a first application, including: the second sending module is used for responding to a first operation of a user and sending a session request to the load balancing equipment, wherein the session request comprises a first identifier used for determining the user; a second receiving module, configured to receive an identifier of a first session, wherein the load balancing device is configured to establish an association between the first identifier and an address of a target server, and the target server is configured to establish the first session in response to the session request sent by the load balancing device; and the application calling module is used for calling a second application in response to a second operation of the user, wherein in the case of calling the second application, the load balancing equipment is configured to maintain the first session with the target server based on the incidence relation.
Another aspect of the disclosed embodiments provides a session holding apparatus, applied to a second application, including: a third receiving module, configured to receive a call request sent by a user operating a first application, where the call request includes a second identifier and an identifier of a first session; the third sending module is used for sending a session maintaining request to the load balancing equipment, wherein the session maintaining request comprises the second identifier and the identifier of the first session, and the load balancing equipment is configured to maintain the first session with a target server based on the association relationship between the second identifier and the address of the target server after receiving the session maintaining request; wherein the first application is configured to send a session request to the load balancing device before sending the invocation request, wherein the session request includes a first identifier for determining the user; the load balancing device is configured to generate the second identity based on the first identity and establish the association between the second identity and the target server address, the target server being configured to establish the first session in response to a session request sent by the load balancing device.
Another aspect of the present disclosure provides an electronic device including: one or more processors; memory for storing one or more programs, wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the method as described above.
Another aspect of the present disclosure also provides a computer-readable storage medium having stored thereon executable instructions that, when executed by a processor, cause the processor to perform the method as described above.
Another aspect of the disclosure also provides a computer program product comprising a computer program which, when executed by a processor, implements the method as described above.
One or more of the above embodiments have the following advantageous effects: the load balancing device determines a target server through the received session request and through a load balancing strategy, establishes an association relation between a first identifier in the session request and an address of the target server, and sends the session request to the target server to establish the first session. Even if the user operates the first application to call the second application, the load balancing device can maintain the first session with the target server based on the association relationship, and avoid the problem that the session is overtime due to too long stay in the second application.
Drawings
The foregoing and other objects, features and advantages of the disclosure will be apparent from the following description of embodiments of the disclosure, which proceeds with reference to the accompanying drawings, in which:
fig. 1 schematically illustrates an application scenario diagram of a session holding method according to an embodiment of the present disclosure;
fig. 2 schematically shows a flow chart of a session holding method applied to a load balancing device according to an embodiment of the present disclosure;
FIG. 3 schematically shows a flow chart of maintaining a first session according to an embodiment of the present disclosure;
fig. 4 schematically shows a flow chart of a session holding method applied to a first application according to another embodiment of the present disclosure;
fig. 5 schematically shows a flow chart of a session holding method applied to a second application according to another embodiment of the present disclosure;
FIG. 6 schematically shows a flow chart of a session holding method according to another embodiment of the present disclosure;
fig. 7 schematically shows a block diagram of a session holding apparatus applied to a load balancing device according to an embodiment of the present disclosure;
fig. 8 schematically shows a block diagram of a structure of a session holding apparatus applied to a first application according to an embodiment of the present disclosure;
fig. 9 schematically shows a block diagram of a structure of a session holding apparatus applied to a second application according to an embodiment of the present disclosure;
fig. 10 schematically shows a block diagram of an electronic device adapted to implement a session-keeping method according to an embodiment of the present disclosure.
Detailed Description
Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood that the description is illustrative only and is not intended to limit the scope of the present disclosure. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the disclosure. It may be evident, however, that one or more embodiments may be practiced without these specific details. Moreover, in the following description, descriptions of well-known structures and techniques are omitted so as to not unnecessarily obscure the concepts of the present disclosure.
The related functionality in the first application may be provided by the second application, thus embedding the functionality of the second application in the first application. During the operation of the first application by the user to use the second application, consideration is given to keeping alive the session between the first application and the target server. Because the use of the first application has load balancing, how to distribute a series of related access requests initiated by the second application to the same target server is an urgent problem to be solved.
The embodiment of the disclosure provides a session holding method applied to a load balancing device, which includes: receiving a session request sent by a user operating a first application, wherein the session request comprises a first identification used for determining the user. And establishing an incidence relation between the first identification and the address of the target server. The session request is sent to the target server to cause the target server to establish the first session based on the session request. And under the condition that the user operates the first application to call the second application, the load balancing equipment maintains the first session with the target server based on the incidence relation.
According to the embodiment of the disclosure, the load balancing device may determine, through the received session request, the target server through the load balancing policy, establish an association relationship between the first identifier in the session request and the address of the target server, and send the session request to the target server to establish the first session. Then, under the condition that the user operates the first application to call the second application, the load balancing device can keep the first session with the target server based on the association relationship, and the problem that the session is overtime possibly caused by too long time of staying in the second application is avoided.
It should be noted that the session maintaining method, apparatus, device, medium, and product provided in the embodiments of the present disclosure may be used in load balancing related aspects, and may also be used in various fields other than load balancing technology, such as financial fields. The application fields of the session maintaining method, the session maintaining device, the session maintaining equipment, the session maintaining medium and the session maintaining product provided by the embodiment of the disclosure are not limited.
Fig. 1 schematically shows an application scenario diagram of a session holding method according to an embodiment of the present disclosure.
As shown in fig. 1, the application scenario 100 according to this embodiment may include terminal devices 101, 102, 103, networks 104, 106, a load balancing device 105, a first server 107, a second server 108, and a distributed storage system 109, where the first server 107 may include N servers, such as servers 1071 to 107N. The network 104 is used to provide a medium for communication links between the terminal devices 101, 102, 103 and the load balancing device 105. The network 106 serves as a medium to provide a communication link between the load balancing device 105 and the first server 107 or distributed storage system 109. The networks 104, 106 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.
The user may use the terminal devices 101, 102, 103 to interact with the load balancing device 105 over the network 104 to receive or send messages or the like. The terminal devices 101, 102, 103 may have installed thereon various communication client applications, such as shopping-like applications, web browser applications, search-like applications, instant messaging tools, mailbox clients, social platform software, etc. (by way of example only).
The terminal devices 101, 102, 103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.
The load balancing device 105 may be a F5 load balancer, a Nginx load balancer, or the like, and is configured to perform load balancing on requests from the terminal devices 101, 102, and 103, and distribute the load to N servers in the first server 107.
The first server 107 or the second server 108 may be a server providing various services, such as a background management server (for example only) providing support for websites browsed by users using the terminal devices 101, 102, 103. The background management server may analyze and perform other processing on the received data such as the user request, and feed back a processing result (e.g., a webpage, information, or data obtained or generated according to the user request) to the terminal device.
According to an embodiment of the present disclosure, the first application and the second application may belong to the same main domain, but have different sub-domain names. The terminal devices 101, 102, 103 may have a first application installed therein, and the first server 107 is configured to receive a request from the first application in the terminal devices 101, 102, 103 and provide a data processing service to meet a user's requirement. The second server 108 is configured to receive a request of a second application in the terminal apparatus 101, 102, 103 and provide a data processing service. The distributed storage system 109 may be a nos (network object storage) cloud storage, and is configured to receive synchronization data, such as session data, sent by the first server 107. It should be noted that the second server 108 may also have a corresponding load balancing device, or include N servers, and the disclosure is not limited in particular.
It should be understood that the number of end devices, networks, load balancing devices, distributed storage systems, and servers in fig. 1 are merely illustrative. There may be any number of load balancing devices, distributed storage systems, and servers, as desired for implementation.
The session holding method according to the embodiment of the present disclosure will be described in detail below with fig. 2 to 6 based on the scenario described in fig. 1.
Fig. 2 schematically shows a flowchart of a session holding method applied to a load balancing device according to an embodiment of the present disclosure.
As shown in fig. 2, the session holding method applied to the load balancing apparatus of this embodiment includes operations S210 to S230.
In operation S210, a session request sent by a user operating a first application is received, where the session request includes a first identifier for determining the user.
Referring to fig. 1, for example, a user enters a home page of a first application using a terminal device 101, and the first application may send a session request to a load balancing device 105 to request to obtain data. Such as obtaining home page presentation data, the user account data, latest activity data, etc. The first identifier may be an account identifier of the user logged in the first application, or may be an equipment identifier (such as a MAC address) of the terminal device 101, or may be an identifier of a SIM card installed in the terminal device 101. Since there may be a plurality of terminal apparatuses installed with the first application, the first server 107 provides the data processing service for them collectively. Thus, the first identification may be used to determine the user, and thus the first server 107 or the load balancing device 105 may be directed to return data.
In operation S220, an association relationship between the first identifier and the target server address is established.
Referring to fig. 1, after receiving the session request, the load balancing device 105 may determine the target server based on a load balancing algorithm (e.g., polling, random, etc.), and establish an association relationship between the first identifier and the address of the target server.
In operation S230, a session request is transmitted to the target server, so that the target server establishes a first session based on the session request. And under the condition that the user operates the first application to call the second application, the load balancing equipment maintains the first session with the target server based on the incidence relation.
In an alternative embodiment, the step of establishing an association relationship between the first identifier and the target server address in operation S220 includes generating a second identifier based on the first identifier, and establishing an association relationship between the second identifier and the target server address.
Taking the first identifier as the MAC address of the terminal device 101 as an example, the MAC address may be hashed (for example only) before the first session is established in operation S230, and a unique hash value (i.e., the second identifier) corresponding to the MAC address may be generated. The hash value is a regular non-repetitive character string and can establish a corresponding relation with a unique server.
In another alternative embodiment, the step of establishing an association relationship between the first identifier and the target server address in operation S220 includes generating a second identifier based on the target server address, and establishing an association relationship between the first identifier and the target server address.
Wherein, the salt processing can be carried out on the basis of the address of the target server, and the salt value is a generated random number. Then, the hash operation is performed on the address of the target server and the salt value to generate a unique hash value (i.e., a second identifier) corresponding to the session of the first identifier. The role of the hash value is because the target server may be able to handle different requests of multiple terminal devices. Therefore, the session is more convenient to maintain corresponding to the session of the first identifier. In addition, the above process of generating the second identifier may be implemented by a big ip tool of the load balancing apparatus.
In some embodiments, establishing the association between the second identifier and the target server address may, for example, write the second identifier and the target server address into a cookie file, wherein the cookie file corresponds to the session request. The cookie file is a piece of data which is temporarily stored on the terminal equipment at the server side, and session maintenance is improved on the basis of the cookie file, so that great improvement cost cannot be generated.
The cookie file may be a blank cookie file carried by the terminal device in the session request. Alternatively, the session request does not carry a cookie file, and the load balancing device 105 inserts the cookie file into the session request, where the cookie file includes the written second identifier and the target server address. Alternatively, the session request does not carry a blank cookie file, and when the target server establishes the first session, the cookie file is generated and returned to the load balancing device 105, and the load balancing device 105 writes the second identifier and the address of the target server, in this case, operation S220 is performed after operation S230.
In other embodiments, establishing the association between the first identifier and the target server address may be by the load balancing device 105 generating an association table. In the association table, a correspondence between the first identifier and the corresponding destination server address in each session request may be included.
Although the various operations of the methods are described above in a particular order, embodiments of the disclosure are not so limited, and the operations described above may be performed in other orders as desired. For example, operation S220 may be performed before operation S230 or may be performed after operation S230.
According to the embodiment of the disclosure, the load balancing device may determine, through the received session request, the target server through the load balancing policy, establish an association relationship between the first identifier in the session request and the address of the target server, and send the session request to the target server to establish the first session. Then, under the condition that the user operates the first application to call the second application, the load balancing device can keep the first session with the target server based on the association relationship, and the problem that the session is overtime possibly caused by too long time of staying in the second application is avoided.
Referring to fig. 3, a detailed description is given of a flow of maintaining, by the load balancing apparatus, the first session with the target server based on the association relationship in a case where the user operates the first application to invoke the second application.
Fig. 3 schematically shows a flow chart of maintaining a first session according to an embodiment of the present disclosure.
As shown in fig. 3, the flow of the load balancing apparatus of this embodiment maintaining the first session with the target server based on the association relationship includes operations S310 to S330.
In operation S310, a session maintenance request sent by the second application is received, where the session maintenance request includes the second identifier and the identifier of the first session.
The first application and the second application may belong to different sub-domains under the same main domain, respectively. For example, the main domain name is zhuyu.com, the domain name for the first application may be 1st.zhuyu.com, and the domain name for the second application may be 2nd.zhuyu.com (for example only).
Referring to fig. 1, for example, when a user operates a first application in the terminal device 101 and clicks a function button, the user may jump to a second application to display a page of the second application. Although the user enters the second application, a series of association operations are performed for the user, so a session hold request is sent by the second application across the domain at this time to keep alive the first session established by the first application.
In operation S320, a target server address is determined from the association relationship based on the second identifier.
An alternative embodiment is that the session maintenance request includes a cookie file and an identification of the first session. The cookie file comprises a second identifier generated based on the first identifier and a target server address. Thus, the load balancing device 105 may read the target server address directly from the cookie file. Another optional mode is that the cookie file includes a second identifier generated based on the target server address, and the second identifier is subjected to inverse hash processing in combination with the salt value to obtain the target server address.
In operation S330, a session maintenance request is sent to the target server based on the target server address, so that the target server updates a timestamp of the first session according to the identification of the first session to maintain the first session.
When the target server establishes the first session in response to the session request, the timestamp of the first session is updated. For example, in the session-hold mechanism, a timeout may be assigned accordingly. Taking the timeout time as 120 seconds as an example, when the target server establishes the first session, the target server updates the first session timestamp to zero seconds, and if the target server does not receive a hold request for the first session within 120 seconds, the target server closes the first session. Therefore, in operation S330, the target server updates the timestamp of the first session based on the received session maintenance request, and avoids closing the first session.
According to the embodiment of the disclosure, in the process of cross-domain access of the first application and the second application, the second application sends the session maintaining request to the load balancing device, and the session maintaining request carries the second identifier and the identifier of the first session, so that the load balancing device can send the session maintaining request to the target server to update the timestamp of the first session, and the survival of the first session is maintained.
Referring to fig. 1, the target server is server 1071 as an example. After the server 1071 receives the session request and establishes the first session, the first session may be synchronized to the distributed storage system 109. I.e. the distributed storage system 109 holds the identification of the first session, the session data and the timestamp.
In some embodiments, the first session is maintained by updating a timestamp of the first session in the distributed storage system based on the identification of the first session in the event that the session maintenance request is not sent to the target server based on the target server address.
Taking the IP address (i.e. the address of the target server) drifting of the target server as an example, the IP address drifting refers to, for example, using the shared virtual IP address to realize that when one server (to which the virtual IP originally points) is down, the virtual IP points to another server to take over the work of the down server. For example, when a target server goes down, although the target server address may be directed to another server, the timestamp of the first session is maintained in the target server, in which case a session maintenance request is not sent to the target server to update the timestamp of the first session. Thus, the timestamp of the first session may be updated directly in the distributed storage system.
According to an embodiment of the present disclosure, the distributed storage system may hold session data synchronized by any one of the servers 1071 to 107N. The distributed storage system can be cloud storage, all session data are stored in one data storage pool, and the problem of load balancing device positioning does not exist. The distributed storage system serves as a spare data storage place for the session information and can play a role in solving the problems when the forwarding of the load balancing equipment fails.
Fig. 4 schematically shows a flowchart of a session holding method applied to a first application according to another embodiment of the present disclosure.
As shown in fig. 4, the session holding method applied to the first application of the embodiment includes operations S410 to S430.
In operation S410, a session request is sent to the load balancing device in response to a first operation of a user, where the session request includes a first identifier for determining the user.
Referring to fig. 1, when the user uses the terminal device 101, the first operation may be an operation of entering the first application by the user, or an operation of clicking a button, refreshing, or the like performed after entering the first application.
In operation S420, an identification of a first session is received, wherein the load balancing device is configured to establish an association between the first identification and an address of a target server, and the target server is configured to establish the first session in response to a session request sent by the load balancing device.
In operation S430, a second application is invoked in response to a second operation of the user, wherein in the event of invoking the second application, the load balancing device is configured to maintain the first session with the target server based on the association relationship.
The second operation may be that the user clicks a function button provided by the second application, and the first application jumps to the second application in response to the user clicking.
In some embodiments, the first application may also receive a second identification. For example, a cookie file may be received, the cookie file including the second identification and the target server address written by the load balancing device, the cookie file corresponding to the session request.
Referring to fig. 1, the first application receives the second identifier and the identifier of the first session, and may receive the cookie file transmitted by the load balancing apparatus 105 through the terminal apparatus 101. Wherein the identification of the first session may be written to the cookie file or may exist independently of the cookie file. Alternatively, the terminal device 101 may directly receive the second identifier and the identifier of the first session sent by the target server without going through the load balancing device 105.
In some embodiments, the load balancing device is configured to generate a second identifier based on the first identifier, and establish an association relationship between the second identifier and the target server address, and the invoking the second application in response to the second operation of the user in operation S430 includes: and sending a call request to the second application in response to the second operation, wherein the call request comprises the second identifier and the identifier of the first session. By carrying the second identifier and the identifier of the first session in the call request, the second application can continuously request the interface of the first application (through domain name access) to perform session maintenance.
Fig. 5 schematically shows a flowchart of a session holding method applied to a second application according to another embodiment of the present disclosure.
As shown in fig. 5, the session holding method applied to the second application of the embodiment includes operations S510 to S520.
In operation S510, a call request sent by a user operating a first application is received, where the call request includes a second identifier and an identifier of a first session.
In operation S520, a session maintaining request is sent to the load balancing device, where the session maintaining request includes the second identifier and the identifier of the first session, and the load balancing device is configured to maintain the first session with the target server based on the association relationship between the second identifier and the address of the target server after receiving the session maintaining request.
Wherein the first application is configured to send a session request to the load balancing device before sending the invocation request, wherein the session request includes the first identification for determining the user. The load balancing device is configured to generate a second identity based on the first identity and to establish an association between the second identity and an address of a target server, the target server being configured to establish the first session in response to a session request sent by the load balancing device.
In the following, with reference to fig. 6, an interaction flow among the second application, the first application, the load balancing device, the target server, and the distributed storage system in implementing the session holding method according to the embodiment of the present disclosure is further described.
Fig. 6 schematically shows a flow chart of a session holding method according to another embodiment of the present disclosure. Wherein the distributed storage system is represented by NOS cloud storage.
As shown in fig. 6, the session holding method implementing this embodiment may include operations S601 to S617.
In operation S601, a session request is sent by a first application to a load balancing apparatus in response to a first operation by a user.
The Session refers to Session, is mainly stored in the server side, and is used for identifying the identity of the user. Referring to fig. 1, when the first application in the terminal device 101 sends a request to the server, an HTTP protocol or an HTTP protocol may be used, and both protocols are based on the HTTP protocol when sending a request, and the HTTP protocol is stateless. When the sending request is passed, the connection is newly connected, and the server side cannot identify the user. The first application will transmit a Session identification (Session Id) as identification information when requesting from the server side, and update the timestamp of the Session to keep the Session alive. The user may enter the web page of the first application in the browser in the terminal device 101, or may click the app package of the first application to enter.
For example, the first application is a mobile banking application and the second application is a lottery application. Operation S601 may be performed when the user enters the cell phone banking application using the terminal device 101. The first application and the second application may be different sub-domains under the same main domain.
In operation S602, the load balancing apparatus generates a second identifier based on the first identifier (e.g., MAC address) in the session request, and inserts the second identifier and the target server address into the cookie file. And sending the session request to the target server. The second identifier is used for identifying the user and has uniqueness corresponding to the first identifier.
In operation S603, the target server establishes a first session in response to the session request, and generates an identification and a timestamp for the first session. The data of the first session is then synchronized into the NOS.
In operation S604, the target server returns an identification of the first session, a cookie file, to the first application. The first application may automatically log in to the user's account upon receiving the identification of the first session and the cookie file.
In operation S605, in response to a second operation by the user, an interface of a second application is entered. For example, the user clicks on an active bonus button, may invoke the second application, and jump to the lottery page for the second application. The jumping may refer to displaying a lottery page of the second application in the first application, or switching from the first application to the second application.
In performing operation S605, the first application may send a call request to the second application, where the call request includes the cookie file and the identifier of the first session.
In operation S606, the second application sends a session maintenance request to the load balancing device, where the session maintenance request includes the second identifier and the identifier of the first session.
In operation S607, the load balancing apparatus fetches the address of the target server from the cookie file and transmits the session maintenance request to the target server, so that the target server updates the timestamp of the first session based on the second identifier or the identifier of the first session.
In operation S608, the target server synchronizes the updated first session timestamp into the NOS.
In operation S609, the load balancing apparatus determines whether the timestamp is successfully updated. For example, if the session maintenance request is not transmitted to the target server due to the transmission IP address drift, operations S607 and S608 are not performed, and operation S610 is performed.
In operation S610, the load balancing apparatus updates the timestamp of the first session in the NOS directly based on the session maintenance request. For example, the NOS may determine the stored data for the first session based on the identity of the first session and update the timestamp accordingly. The first session associated therewith may also be determined based on the second identification.
In operation S611, the second application returns to the first application. For example, the user returns to the first application after the second application lottery is completed.
In operation S612, the first application sends a session maintenance request to the load balancing apparatus. The session maintenance request includes a cookie file and an identification of the first session.
In operation S613, the load balancing apparatus fetches the address of the target server from the cookie file and transmits the session maintenance request to the target server, so that the target server updates the timestamp of the first session based on the second identifier or the identifier of the first session.
In operation S614, the target server synchronizes the updated first session timestamp into the NOS.
In operation S615, the load balancing apparatus determines whether the timestamp is successfully updated. For example, if the IP address drift occurs such that the session maintenance request is not transmitted to the target server, operation S613 and operation S614 are not performed, and operation S616 is performed.
In operation S616, the load balancing apparatus updates the timestamp of the first session in the NOS directly based on the session maintenance request.
In operation S617, the NOS may return the data of the first session to enable the user to continue the associated operation, thereby avoiding problems such as a user re-operation or re-login due to disconnection of the first session. For example, after filling the form in the mobile banking application, the user enters the second application lottery. If the first session cannot be kept alive, the data of the filled form may be lost after the user returns to the first application from the second application, so that the user can refill the form, and the user experience is reduced. And the timestamp of the first session is updated in time, so that the first session is kept alive, and therefore, related data can be normally returned from the NOS, and the user can be supported to continue to operate.
The session maintaining method of the embodiment of the disclosure implants the identifier in the cookie file when the session request is forwarded through the load balancing device, and can forward the identifier to the server of the current session through the identification cookie when the session request is requested again, so as to complete the update of the session timestamp, and update the timestamp of the session in the nos. In order to prevent the forwarding error of the load balancing equipment, the nos object cloud is synchronously adopted to store the session information, if the server cannot find the session information or the session information is overtime, the nos object cloud is used for searching the session information, and whether the session information is overtime is judged. Therefore, the problem of maintaining the cross-domain access session of the two applications is solved, and meanwhile, the success rate is ensured.
Based on the session holding method, the disclosure further provides a session holding apparatus applied to the load balancing device, the first application and the second application, respectively. The apparatus will be described in detail below with reference to fig. 7, 8 and 9.
Fig. 7 schematically shows a block diagram of a session holding apparatus 700 applied to a load balancing device according to an embodiment of the present disclosure.
As shown in fig. 7, the session holding apparatus 700 of this embodiment includes a first receiving module 710, an association establishing module 720, and a first transmitting module 730.
The first receiving module 710 may perform operation S710, for example, to receive a session request sent by a user operating a first application, where the session request includes a first identifier used for determining the user.
The association establishing module 720 may perform operation S720, for example, for establishing an association relationship between the first identifier and the target server address.
The first sending module 730 may perform operation S730, for example, to send the session request to the target server, so that the target server establishes the first session based on the session request.
And under the condition that the user operates the first application to call the second application, the load balancing equipment maintains the first session with the target server based on the incidence relation.
Fig. 8 schematically shows a block diagram of a session holding apparatus 800 applied to a first application according to an embodiment of the present disclosure.
As shown in fig. 8, the session holding apparatus 800 of this embodiment includes a second sending module 810, a second receiving module 820, and an application calling module 830.
The second sending module 810 may perform operation S410, for example, to send a session request to the load balancing device in response to a first operation of a user, where the session request includes a first identifier for determining the user.
The second receiving module 820 may perform operation S420, for example, for receiving an identification of a first session, wherein the load balancing device is configured to establish an association between the first identification and an address of a target server, and the target server is configured to establish the first session in response to a session request sent by the load balancing device.
The application invoking module 830 may perform operation S430, for example, for invoking a second application in response to a second operation of the user, wherein in case of invoking the second application, the load balancing device is configured to maintain the first session with the target server based on the association relationship.
Fig. 9 schematically shows a block diagram of a structure of a session holding apparatus 900 applied to a second application according to an embodiment of the present disclosure.
As shown in fig. 9, the session holding apparatus 900 of this embodiment includes a third receiving module 910 and a third sending module 920.
The third receiving module 910 may perform operation S510, for example, to receive a call request sent by a user operating a first application, where the call request includes the second identifier and the identifier of the first session. And
the third sending module 920 may execute operation S520, for example, to send a session maintenance request to the load balancing device, where the session maintenance request includes the second identifier and the identifier of the first session, and the load balancing device is configured to maintain the first session with the target server based on the association relationship between the second identifier and the address of the target server after receiving the session maintenance request.
Wherein the first application is configured to send a session request to the load balancing device before sending the invocation request, wherein the session request includes the first identification for determining the user. The load balancing device is configured to generate a second identity based on the first identity and to establish an association between the second identity and an address of a target server, the target server being configured to establish the first session in response to a session request sent by the load balancing device.
According to the embodiment of the present disclosure, any of the modules in the session holding apparatus 700, the session holding apparatus 800, or the session holding apparatus 900 may be combined into one module to be implemented, or any one of the modules may be split into a plurality of modules. Alternatively, at least part of the functionality of one or more of these modules may be combined with at least part of the functionality of the other modules and implemented in one module. According to an embodiment of the present disclosure, at least one of the session holding apparatus 700, the session holding apparatus 800 or the session holding apparatus 900 may be implemented at least partially as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented in hardware or firmware in any other reasonable manner of integrating or packaging a circuit, or in any one of or a suitable combination of software, hardware and firmware. Alternatively, at least one of the session holding apparatus 700, the session holding apparatus 800 or the session holding apparatus 900 may be at least partly implemented as computer program modules which, when executed, may perform corresponding functions.
Fig. 10 schematically shows a block diagram of an electronic device adapted to implement a session-keeping method according to an embodiment of the present disclosure.
As shown in fig. 10, an electronic device 1000 according to an embodiment of the present disclosure includes a processor 1001 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM)1002 or a program loaded from a storage section 1008 into a Random Access Memory (RAM) 1003. Processor 1001 may include, for example, a general purpose microprocessor (e.g., a CPU), an instruction set processor and/or associated chipset, and/or a special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), among others. The processor 1001 may also include onboard memory for caching purposes. The processor 1001 may include a single processing unit or multiple processing units for performing different actions of a method flow according to embodiments of the present disclosure.
In the RAM1003, various programs and data necessary for the operation of the electronic apparatus 1000 are stored. The processor 1001, ROM 1002, and RAM1003 are connected to each other by a bus 1004. The processor 1001 performs various operations of the method flow according to the embodiments of the present disclosure by executing programs in the ROM 1002 and/or the RAM 1003. Note that the program may also be stored in one or more memories other than the ROM 1002 and the RAM 1003. The processor 1001 may also perform various operations of method flows according to embodiments of the present disclosure by executing programs stored in one or more memories.
The present disclosure also provides a computer-readable storage medium, which may be embodied in the devices/apparatuses/systems described in the above embodiments. Or may exist separately and not be assembled into the device/apparatus/system. The computer-readable storage medium carries one or more programs which, when executed, implement the method according to an embodiment of the disclosure.
According to embodiments of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, which may include, for example but is not limited to: 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 portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. For example, according to embodiments of the present disclosure, a computer-readable storage medium may include the ROM 1002 and/or the RAM1003 described above and/or one or more memories other than the ROM 1002 and the RAM 1003.
Embodiments of the present disclosure also include a computer program product comprising a computer program containing program code for performing the method illustrated in the flow chart. The program code is for causing a computer system to carry out the method according to the embodiments of the disclosure, when the computer program product is run on the computer system.
The computer program performs the above-described functions defined in the system/apparatus of the embodiments of the present disclosure when executed by the processor 1001. The systems, apparatuses, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the present disclosure.
In one embodiment, the computer program may be hosted on a tangible storage medium such as an optical storage device, a magnetic storage device, or the like. In another embodiment, the computer program may also be transmitted in the form of a signal on a network medium, distributed, downloaded and installed via the communication part 1009, and/or installed from the removable medium 1011. The computer program containing program code may be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the foregoing.
In such an embodiment, the computer program may be downloaded and installed from a network through the communication part 1009 and/or installed from the removable medium 1011. The computer program performs the above-described functions defined in the system of the embodiment of the present disclosure when executed by the processor 1001. The systems, devices, apparatuses, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the present disclosure.
In accordance with embodiments of the present disclosure, program code for executing computer programs provided by embodiments of the present disclosure may be written in any combination of one or more programming languages, and in particular, these computer programs may be implemented using high level procedural and/or object oriented programming languages, and/or assembly/machine languages. The programming language includes, but is not limited to, programming languages such as Java, C + +, python, the "C" language, or the like. The program code may execute entirely on the user computing device, partly on the user device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., through the internet using an internet service provider).
The embodiments of the present disclosure have been described above. However, these examples are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Although the embodiments are described separately above, this does not mean that the measures in the embodiments cannot be used in advantageous combination. The scope of the disclosure is defined by the appended claims and equivalents thereof. Various alternatives and modifications can be devised by those skilled in the art without departing from the scope of the present disclosure, and such alternatives and modifications are intended to be within the scope of the present disclosure.
Claims (15)
1. A conversation keeping method is applied to load balancing equipment and comprises the following steps:
receiving a session request sent by a user operating a first application, wherein the session request comprises a first identifier used for determining the user;
establishing an incidence relation between the first identification and a target server address;
sending the session request to a target server so that the target server establishes a first session based on the session request;
wherein, in a case where the user operates the first application to invoke a second application, the load balancing device maintains the first session with the target server based on the association relationship.
2. The method of claim 1, wherein said establishing an association between said first identity and a target server address comprises:
and generating a second identifier based on the first identifier, and establishing an association relation between the second identifier and the target server address.
3. The method of claim 2, wherein the load balancing device maintaining the first session with the target server based on the association relationship if the user operates the first application to invoke a second application comprises:
receiving a session maintaining request sent by the second application, wherein the session maintaining request comprises the second identifier and the identifier of the first session;
determining the target server address from the incidence relation based on the second identification;
sending the session maintenance request to the target server based on the target server address to cause the target server to update the timestamp of the first session according to the identification of the first session to maintain the first session.
4. The method of claim 3, wherein after the target server establishes a first session based on the session request, the target server synchronizes the first session to a distributed storage system, the method further comprising: in the case where the session maintenance request is not sent to the target server based on the target server address,
the timestamp of the first session is updated in a distributed storage system to maintain the first session based on the identification of the first session.
5. The method of claim 2, wherein said establishing an association between said second identity and a target server address comprises:
writing the second identification and the target server address into a cookie file, wherein the cookie file corresponds to the session request.
6. A conversation keeping method is applied to a first application and comprises the following steps:
sending a session request to a load balancing device in response to a first operation of a user, wherein the session request comprises a first identifier for determining the user;
receiving an identification of a first session, wherein the load balancing device is configured to establish an association between the first identification and a target server address, and the target server is configured to establish the first session in response to the session request sent by the load balancing device;
in response to a second operation of the user, invoking a second application, wherein in the event of invoking the second application, the load balancing device is configured to maintain the first session with the target server based on the association relationship.
7. The method according to claim 6, wherein the method further comprises receiving a second identifier, specifically comprising:
receiving a cookie file, wherein the cookie file comprises the second identifier and the target server address written by the load balancing device, and the cookie file corresponds to the session request.
8. The method of claim 7, wherein the load balancing device is configured to generate a second identifier based on the first identifier, establish an association between the second identifier and a target server address, and wherein invoking a second application in response to a second operation by the user comprises:
and sending a call request to the second application in response to the second operation, wherein the call request comprises the second identifier and the identifier of the first session.
9. A session holding method applied to a second application comprises the following steps:
receiving a call request sent by a user operating a first application, wherein the call request comprises a second identifier and an identifier of a first session; and
sending a session maintaining request to a load balancing device, wherein the session maintaining request comprises the second identifier and the identifier of the first session, and the load balancing device is configured to maintain the first session with a target server based on the association relationship between the second identifier and the address of the target server after receiving the session maintaining request;
wherein the first application is configured to send a session request to the load balancing device before sending the invocation request, wherein the session request includes a first identifier for determining the user; the load balancing device is configured to generate the second identity based on the first identity and establish the association between the second identity and the target server address, the target server being configured to establish the first session in response to a session request sent by the load balancing device.
10. A conversation keeping device is applied to load balancing equipment and comprises:
the device comprises a first receiving module, a second receiving module and a processing module, wherein the first receiving module is used for receiving a session request sent by a user operating a first application, and the session request comprises a first identifier used for determining the user;
the association establishing module is used for establishing an association relation between the first identifier and the target server address;
the first sending module is used for sending the session request to a target server so that the target server establishes a first session based on the session request;
wherein, in a case where the user operates the first application to invoke a second application, the load balancing device maintains the first session with the target server based on the association relationship.
11. A session holding apparatus, applied to a first application, comprising:
the second sending module is used for responding to a first operation of a user and sending a session request to the load balancing equipment, wherein the session request comprises a first identifier used for determining the user;
a second receiving module, configured to receive an identifier of a first session, wherein the load balancing device is configured to establish an association between the first identifier and an address of a target server, and the target server is configured to establish the first session in response to the session request sent by the load balancing device;
and the application calling module is used for calling a second application in response to a second operation of the user, wherein in the case of calling the second application, the load balancing equipment is configured to maintain the first session with the target server based on the incidence relation.
12. A session holding apparatus applied to a second application, comprising:
a third receiving module, configured to receive a call request sent by a user operating a first application, where the call request includes a second identifier and an identifier of a first session; and
a third sending module, configured to send a session maintaining request to a load balancing device, where the session maintaining request includes the second identifier and an identifier of the first session, and the load balancing device is configured to maintain the first session with a target server based on an association relationship between the second identifier and a target server address after receiving the session maintaining request;
wherein the first application is configured to send a session request to the load balancing device before sending the invocation request, wherein the session request includes a first identifier for determining the user; the load balancing device is configured to generate the second identity based on the first identity and establish the association between the second identity and the target server address, the target server being configured to establish the first session in response to a session request sent by the load balancing device.
13. An electronic device, comprising:
one or more processors;
a storage device for storing one or more programs,
wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the method of any of claims 1-9.
14. A computer readable storage medium having stored thereon executable instructions which, when executed by a processor, cause the processor to perform the method of any one of claims 1 to 9.
15. A computer program product comprising a computer program which, when executed by a processor, implements a method according to any one of claims 1 to 9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111680316.6A CN114338689A (en) | 2021-12-30 | 2021-12-30 | Session holding method, apparatus, device, medium, and program product |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111680316.6A CN114338689A (en) | 2021-12-30 | 2021-12-30 | Session holding method, apparatus, device, medium, and program product |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114338689A true CN114338689A (en) | 2022-04-12 |
Family
ID=81022232
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111680316.6A Pending CN114338689A (en) | 2021-12-30 | 2021-12-30 | Session holding method, apparatus, device, medium, and program product |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114338689A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114827239A (en) * | 2022-05-31 | 2022-07-29 | 杭州迪普科技股份有限公司 | Bidirectional session holding method and device based on 8583 protocol |
| CN115118762A (en) * | 2022-05-19 | 2022-09-27 | 北京京东乾石科技有限公司 | Session processing method, client and system |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103176853A (en) * | 2011-12-23 | 2013-06-26 | 腾讯科技（深圳）有限公司 | Method and system realizing communication among multiple applications |
| CN103457869A (en) * | 2013-08-28 | 2013-12-18 | 北京星网锐捷网络技术有限公司 | Conversation maintaining method and device |
| CN104811488A (en) * | 2015-04-13 | 2015-07-29 | 深信服网络科技（深圳）有限公司 | Load balancing equipment-based session keeping method and system and load balancing equipment |
| CN105812351A (en) * | 2016-02-23 | 2016-07-27 | 平安科技（深圳）有限公司 | Method and system for sharing session |
| CN107360251A (en) * | 2017-08-16 | 2017-11-17 | 中国工商银行股份有限公司 | Method, system and the load balancing apparatus that session is kept |
| CN110442610A (en) * | 2019-08-05 | 2019-11-12 | 中国工商银行股份有限公司 | The method, apparatus of load balancing calculates equipment and medium |
| CN113206877A (en) * | 2021-04-29 | 2021-08-03 | 工银科技有限公司 | Session keeping method and device |
| CN113452778A (en) * | 2021-06-25 | 2021-09-28 | 中国农业银行股份有限公司 | Session keeping method, device, equipment, system and storage medium |
| CN113489747A (en) * | 2021-08-17 | 2021-10-08 | 中国联合网络通信集团有限公司 | Session connection method, device and terminal |
-
2021
- 2021-12-30 CN CN202111680316.6A patent/CN114338689A/en active Pending
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103176853A (en) * | 2011-12-23 | 2013-06-26 | 腾讯科技（深圳）有限公司 | Method and system realizing communication among multiple applications |
| CN103457869A (en) * | 2013-08-28 | 2013-12-18 | 北京星网锐捷网络技术有限公司 | Conversation maintaining method and device |
| CN104811488A (en) * | 2015-04-13 | 2015-07-29 | 深信服网络科技（深圳）有限公司 | Load balancing equipment-based session keeping method and system and load balancing equipment |
| CN105812351A (en) * | 2016-02-23 | 2016-07-27 | 平安科技（深圳）有限公司 | Method and system for sharing session |
| CN107360251A (en) * | 2017-08-16 | 2017-11-17 | 中国工商银行股份有限公司 | Method, system and the load balancing apparatus that session is kept |
| CN110442610A (en) * | 2019-08-05 | 2019-11-12 | 中国工商银行股份有限公司 | The method, apparatus of load balancing calculates equipment and medium |
| CN113206877A (en) * | 2021-04-29 | 2021-08-03 | 工银科技有限公司 | Session keeping method and device |
| CN113452778A (en) * | 2021-06-25 | 2021-09-28 | 中国农业银行股份有限公司 | Session keeping method, device, equipment, system and storage medium |
| CN113489747A (en) * | 2021-08-17 | 2021-10-08 | 中国联合网络通信集团有限公司 | Session connection method, device and terminal |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115118762A (en) * | 2022-05-19 | 2022-09-27 | 北京京东乾石科技有限公司 | Session processing method, client and system |
| CN114827239A (en) * | 2022-05-31 | 2022-07-29 | 杭州迪普科技股份有限公司 | Bidirectional session holding method and device based on 8583 protocol |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP7252356B2 (en) | MOBILE EDGE COMPUTING NODE SELECTION METHOD, APPARATUS AND SYSTEM AND COMPUTER PROGRAM | |
| US10827008B2 (en) | Integrated user interface for consuming services across different distributed networks | |
| US20190082026A1 (en) | Interface invocation method and apparatus for hybrid cloud | |
| US9069870B2 (en) | Client-side aggregation of context-sensitive request results where results for aggregation are asynchronously produced by multiple servers | |
| US7552219B2 (en) | Methods for sharing session data on a network | |
| CN110351283B (en) | Data transmission method, device, equipment and storage medium | |
| US9426142B2 (en) | Systems and methods for logging into an application on a second domain from a first domain in a multi-tenant database system environment | |
| CN113489772B (en) | Network request processing method and device and electronic equipment | |
| CN114338689A (en) | Session holding method, apparatus, device, medium, and program product | |
| US20130104200A1 (en) | Apparatus and method for controlling access to multiple services | |
| US20050108299A1 (en) | Real-time Web sharing system | |
| CN112131504B (en) | Webpage editing and displaying method, device, equipment and storage medium | |
| CN111611091A (en) | Service calling method, device and medium for business object | |
| EP3298756B1 (en) | Interfacing with servers having different apis to obtain advertisement data | |
| US9729652B2 (en) | Dynamically affinitizing users to a version of a website | |
| CN114221954A (en) | File transmission method and device, electronic equipment and storage medium | |
| US10334014B2 (en) | Accessing connected service resources in a distributed application programming interface | |
| US20130103736A1 (en) | Client side management of http sessions | |
| CN113469736A (en) | Resource distribution control method, device, system, electronic device and storage medium | |
| CN113055348B (en) | Cross-platform data request method and device and electronic equipment | |
| US20230267566A1 (en) | Network based provision of rendering and hosting systems | |
| CN110674435A (en) | Page access method, server, terminal, electronic equipment and readable storage medium | |
| CN105871972A (en) | Video resource distributed cathe method, device and system | |
| CN113590354A (en) | Block chain-based information push method, apparatus, device, medium, and program product | |
| CN114125067A (en) | Front-end and back-end separated gray scale publishing method, front-end server and configuration server |
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 |