CN111953700A

CN111953700A - Session keeping method and device

Info

Publication number: CN111953700A
Application number: CN202010833150.6A
Authority: CN
Inventors: 秦真; 沈力; 黄文蕾; 施经纬
Original assignee: Industrial and Commercial Bank of China Ltd ICBC
Current assignee: Industrial and Commercial Bank of China Ltd ICBC
Priority date: 2020-08-18
Filing date: 2020-08-18
Publication date: 2020-11-17
Anticipated expiration: 2040-08-18
Also published as: CN111953700B

Abstract

The application provides a session keeping method and a session keeping device, which can be used in the financial field or other fields, and the method comprises the following steps: receiving a target request message which is sent by a target IPv6/IPv4 dual-stack client and contains Cookie information; determining a target Web container corresponding to a target IPv6/IPv4 dual-stack client according to a preset session holding list item and Cookie information, and sending a target request message to the target Web container so that the target Web container processes the target request message, wherein the target Web container is the same as a Web container when processing an initial request message of the target IPv6/IPv4 dual-stack client; and sending the processing result of the target request message to the target IPv6/IPv4 dual-stack client. The method and the device can avoid the session maintenance invalidation caused by the network switching of the IPv6 and the IPv4, can improve the effectiveness of the session maintenance, and further can improve the reliability of the user transaction process.

Description

Session keeping method and device

Technical Field

The present application relates to the field of data processing technologies, and in particular, to a session holding method and apparatus.

Background

With The development of information technology, The global Internet based on The IPv4 Protocol faces The problems of network address consumption, service quality being difficult to guarantee, and The like, and for this reason, The Internet Engineering Task Force (IETF for short) designs an IPv6 Protocol (Internet Protocol version 6) to replace The existing IPv4 Protocol (Internet Protocol version 4 ). The IPv6 protocol is greatly modified and functionally expanded, and provides an almost unlimited address space, stronger network security, etc., and it is a necessary trend that IPv6 gradually replaces IPv 4. Meanwhile, IPv6 and IPv4 networks will be in parallel as normal.

At the initial stage of IPv6 network construction and popularization, in a scenario where an IPv6 network is unstable and an IPv6 request is overtime or a user network environment is switched and the switched network does not support IPv6 (for example, a 4G network is switched to a Wifi network), a user internet access channel is automatically switched from IPv6 to IPv4, and a request for maintaining a conventional Cookie session is routed to an IPv4 server hung under a soft load (instead of an IPv6 server under an original IPv6 network), so that the conventional Cookie-based session is kept invalid and a transaction is failed.

Disclosure of Invention

Aiming at the problems in the prior art, the application provides a session maintaining method and device, which can avoid session maintaining failure caused by network switching of IPv6 and IPv4, improve the effectiveness of session maintaining and further improve the reliability of a user transaction process.

In order to solve the technical problem, the present application provides the following technical solutions:

in a first aspect, the present application provides a session holding method, including:

receiving a target request message which is sent by a target IPv6/IPv4 dual-stack client and contains Cookie information;

determining a target Web container corresponding to the target IPv6/IPv4 dual-stack client according to a preset session holding list item and the Cookie information, and sending the target request message to the target Web container so that the target Web container processes the target request message, wherein the target Web container is the same as a Web container used for processing an initial request message of the target IPv6/IPv4 dual-stack client;

and sending the processing result of the target request message to the target IPv6/IPv4 dual-stack client.

Further, the sending the target request packet to the target Web container includes: determining a target Web container corresponding to the target IPv6/IPv4 dual-stack client according to a preset session holding list item and the Cookie information; if the IP protocols of the IP addresses corresponding to the target Web container and the Cookie information are different, applying a preset protocol conversion relation to convert the IP protocol of the IP address corresponding to the Cookie information into the IP protocol of the IP address corresponding to the target Web container; and applying the IP address converted by the IP protocol corresponding to the Cookie information to send the target request message to a target Web container.

Further, before the receiving the target request packet containing the Cookie information sent by the target IPv6/IPv4 dual-stack client, the method further includes: receiving an initial request message sent by the target IPv6/IPv4 dual-stack client; determining a Web container corresponding to the target IPv6/IPv4 dual-stack client according to a load balancing algorithm so that the Web container processes the initial request message; generating Cookie information corresponding to the target IPv6/IPv4 dual-stack client, and sending the Cookie information and the processing result of the initial request message to the target IPv6/IPv4 dual-stack client.

Further, the Cookie information includes: client identification and Cookie effective time; correspondingly, after generating the Cookie information corresponding to the target IPv6/IPv4 dual-stack client, the method further includes: and updating the session holding list item by applying the client identification, the Cookie effective time and the container identification of the Web container.

Further, the receiving a target request packet containing Cookie information sent by a target IPv6/IPv4 dual-stack client includes: and if the target request message is a request message sent based on an IPv4 protocol, receiving the target request message by applying a corresponding IPv4 virtual address.

Further, the receiving a target request packet containing Cookie information sent by a target IPv6/IPv4 dual-stack client includes: and if the target request message is a request message sent based on an IPv6 protocol, receiving the target request message by applying a corresponding IPv6 virtual address.

In a second aspect, the present application provides a session holding apparatus comprising:

the receiving module is used for receiving a target request message which is sent by a target IPv6/IPv4 dual-stack client and contains Cookie information;

the processing module is used for determining a target Web container corresponding to the target IPv6/IPv4 dual-stack client according to a preset session holding list item and the Cookie information, and sending the target request message to the target Web container so that the target Web container processes the target request message, wherein the target Web container is the same as a Web container used for processing an initial request message of the target IPv6/IPv4 dual-stack client;

and the sending module is used for sending the processing result of the target request message to the target IPv6/IPv4 dual-stack client.

Further, the processing module includes: the protocol conversion unit is used for applying a preset protocol conversion relationship if the IP protocols of the IP addresses corresponding to the target Web container and the Cookie information are different, and converting the IP protocol of the IP address corresponding to the Cookie information into the IP protocol of the IP address corresponding to the target Web container; and the sending unit is used for applying the IP address converted by the IP protocol corresponding to the Cookie information and sending the target request message to the target Web container.

In a third aspect, the present application provides an electronic device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the processor implements the session holding method when executing the program.

In a fourth aspect, the present application provides a computer readable storage medium having stored thereon computer instructions that, when executed, implement the session-keeping method.

According to the technical scheme, the application provides a session maintaining method and device. Wherein, the method comprises the following steps: receiving a target request message which is sent by a target IPv6/IPv4 dual-stack client and contains Cookie information; determining a target Web container corresponding to the target IPv6/IPv4 dual-stack client according to a preset session holding list item and the Cookie information, and sending the target request message to the target Web container so that the target Web container processes the target request message, wherein the target Web container is the same as a Web container used for processing an initial request message of the target IPv6/IPv4 dual-stack client; the processing result of the target request message is sent to the target IPv6/IPv4 dual-stack client, so that the failure of session maintenance caused by switching of IPv6 and IPv4 networks can be avoided, the effectiveness of session maintenance can be improved, and the reliability of a user transaction process can be improved; specifically, the mixed deployment of the container based on the IPv4 address and the IPv6 address on the session holding device can solve the problem that the client transaction cannot be normally processed under the condition that an IPv6 network is unstable or the environment of the client network changes. Its advantages are as follows: 1. the hybrid deployment of the Web container with the IPv4 address and the Web container with the IPv6 address is realized, a large address pool is formed and exposed to the session holding device, and when the IP address of the client drifts, the soft load server can load the client request to the original Web container, so that the usability of transaction can be improved. 2. In the initial stage of IPv6 network construction and popularization, under the condition that the IPv6 network stability cannot be guaranteed, the client request is automatically distributed to the address pool of the IPv4 through the session maintaining device, and the session maintaining device is transparent to the client, so that the transaction can be continuously processed, and the transaction experience of the client can be further improved.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.

FIG. 1 is a flow chart illustrating a session maintaining method in an embodiment of the present application;

fig. 2 is a flowchart illustrating steps 201 to 202 of the session maintaining method in the embodiment of the present application;

fig. 3 is a flowchart illustrating steps 001 to 004 of the session maintaining method in the embodiment of the present application;

FIG. 4 is a schematic structural diagram of a session holding apparatus in an embodiment of the present application;

FIG. 5 is a logic diagram of a session maintenance system in an example application of the present application;

FIG. 6 is a schematic structural diagram of an IPv6/IPv4 dual-stack client in an application example of the application;

FIG. 7 is a schematic diagram of a soft load server in an application example of the present application;

FIG. 8 is a schematic structural diagram of a Web container in an application example of the present application;

FIG. 9 is a flow chart illustrating a session holding method in an application example of the present application;

fig. 10 is a schematic block diagram of a system configuration of an electronic device according to an embodiment of the present application.

Detailed Description

In order to make those skilled in the art better understand the technical solutions in the present specification, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

In consideration of the insufficiency of the traditional Cookie session maintaining function, the application provides a session maintaining method and a device, the addresses of the Web containers of IPv6 and IPv4 are mixed and deployed in an address pool, after a client requests to access to the session maintaining device for the first time, the session maintaining device does not distinguish the Web containers with different addresses of background IPv4 and IPv6, and the access request is distributed to any Web container in the background through a load balancing algorithm. In the subsequent access process, if the address of the client is switched between IPv6 and IPv4, the session holding device identifies the original Web container to which the request belongs according to the Cookie information and IP protocol conversion carried by the request of the client, and accurately routes the request of the client to the original Web container for processing, so that the problem of failure of traditional Cookie session holding caused by network switching between IPv6 and IPv4 can be solved.

Specifically, the virtual address for externally providing a service is a virtual address of the session holding apparatus; the session holding device background mixedly mounts the Web containers of IPv6 and IPv 4. When a client initiates an access request for the first time, because the request message does not carry Cookie information, the session holding device distributes the client request to one of the Web containers in the background according to a load balancing strategy (usually, the minimum number of links, polling, the shortest response time and the like). After the Web container finishes processing the request, the data message returns to the session holding device, the session holding device inserts the Cookie information into the data message and then returns the data packet to the client, and the client stores the Cookie information locally. In the subsequent transaction process, the client requests to carry Cookie information to communicate with the server, if the client is subjected to network switching between IPv6 and IPv4, and when the session holding device is accessed again within the Cookie effective time, the session holding device reads the Cookie information and forwards the request to the same Web container through the IPv6 and IPv4 address conversion of the session holding device, so that session holding is realized, and the transaction is continuously processed.

It should be noted that the session holding method and apparatus disclosed in the present application may be used in the financial field, and may also be used in any field other than the financial field.

The following examples are intended to illustrate the details.

In order to avoid the failure of session maintenance due to network handover between IPv6 and IPv4, and improve the effectiveness of session maintenance, and thus improve the reliability of the user transaction process, the present embodiment provides a session maintenance method in which the execution subject is a session maintenance device, where the session maintenance device includes, but is not limited to, a server, and referring to fig. 1, the method specifically includes the following contents:

step 100: and receiving a target request message which is sent by a target IPv6/IPv4 dual-stack client and contains Cookie information.

Specifically, the target IPv6/IPv4 dual stack client is configured with an IPv6 address and an IPv4 address, dynamically allocated by the client operating system, and generally prefers the IPv6 address, and is automatically degraded to the IPv4 network under the condition that the IPv6 network is not available. The request message may be a financial transaction request message, such as a transfer or payment.

Step 200: and determining a target Web container corresponding to the target IPv6/IPv4 dual-stack client according to a preset session holding list item and the Cookie information, and sending the target request message to the target Web container so that the target Web container processes the target request message, wherein the target Web container is the same as the Web container used for processing the initial request message of the target IPv6/IPv4 dual-stack client.

Specifically, the preset session holding list item may include a correspondence between the client, the Web container, and the Cookie valid time; the container identifier of the target Web container corresponding to the target IPv6/IPv4 dual-stack client may be obtained from the preset session holding entry according to the client identifier in the Cookie information. The target Web container can be an IPv6 Web container and can also be an IPv4 Web container. The target Web container is the same as the Web container when the initial request message of the target IPv6/IPv4 dual-stack client is processed, and the requests from the same client can be distributed to the same Web container. The target Web container may be provided in the session holding apparatus or may be provided in a separate server.

The table structure of the preset session holding table entry may be as shown in table 1.

TABLE 1

Step 300: and sending the processing result of the target request message to the target IPv6/IPv4 dual-stack client.

In order to send request packets corresponding to different IP protocols to the same Web container, avoid session interruption, and improve the validity of session maintenance, referring to fig. 2, in an embodiment of the present application, sending the target request packet to the target Web container in step 200 includes:

step 201: and if the IP protocols of the IP addresses corresponding to the target Web container and the Cookie information are different, applying a preset protocol conversion relation to convert the IP protocol of the IP address corresponding to the Cookie information into the IP protocol of the IP address corresponding to the target Web container.

Specifically, if the IP address corresponding to the target Web container and the IP protocol of the client IP address corresponding to the Cookie information are different, protocol conversion is performed. The client IP address corresponding to the Cookie information may be determined in the session holding apparatus according to the Cookie information.

Step 202: and applying the IP address converted by the IP protocol corresponding to the Cookie information to send the target request message to a target Web container.

In particular, the IP protocol may be the IPv6 protocol or the IPv4 protocol; the target IPv6/IPv4 dual-stack client application IP protocol is communicated with the session holding device, which IP protocol is specifically applied by the client is determined by a client operating system, and mainstream operating systems are all IPv6 in priority, and the IP protocol is automatically degraded into an IPv4 network under the condition that the IPv6 network is not available. The difference between the IP protocols of the IP addresses corresponding to the target Web container and the Cookie information may include: the IP protocol corresponding to the IP address of the target Web container is an IPv4 protocol, and the IP protocol of the IP address corresponding to the Cookie information is an IPv6 protocol; may also include: and the IP protocol corresponding to the IP address of the target Web container is an IPv6 protocol, and the IP protocol corresponding to the IP address in the Cookie information is an IPv4 protocol. Specifically, the preset protocol conversion relationship includes a corresponding relationship between an IPv4 virtual server IP address, an IPv6 virtual server IP address and a container identifier, where the IP addresses of multiple IPv6/IPv4 dual-stack clients respectively correspond to the IP addresses, where the IPv4 virtual server IP address, that is, the IPv4 virtual address, is used to receive a client request based on an IPv4 protocol sent by the IPv6/IPv4 dual-stack client, and the IPv6 virtual server IP address, that is, the IPv6 virtual address, is used to receive a client request based on an IPv6 protocol sent by the IPv6/IPv4 dual-stack client. The virtual server IP address can be returned to the client by domain name resolution; the structure of the preset protocol conversion relationship may be as shown in table 2, and the actual content may be set as required:

TABLE 2

To further improve the effectiveness of session maintenance, in an embodiment of the present application, referring to fig. 3, before step 100, the method further includes:

step 001: and receiving an initial request message sent by the target IPv6/IPv4 dual-stack client.

Specifically, the initial request packet is an access request when the target IPv6/IPv4 dual-stack client accesses the session holding apparatus for the first time, where the access request does not carry Cookie information.

Step 002: and determining the Web container corresponding to the target IPv6/IPv4 dual-stack client according to a load balancing algorithm so that the Web container processes the initial request message.

Specifically, the load balancing algorithm may be one of a minimum number of connections, a minimum response time, polling, and priority-based, and preferably the minimum number of connections, and may determine the Web container to which the request packet is allocated and processed. The Web container may be deployed in a Web container pool in the session holding apparatus, where the Web container pool includes an IPv6 Web container and an IPv4 Web container.

The specific description of the load balancing algorithm is shown in table 3:

TABLE 3

Step 003: generating Cookie information corresponding to the target IPv6/IPv4 dual-stack client, and sending the Cookie information and the processing result of the initial request message to the target IPv6/IPv4 dual-stack client.

Specifically, after the Cookie information is inserted into the processing result of the initial request packet, a data packet may be sent to the target IPv6/IPv4 dual-stack client, and the Cookie information is stored locally at the client, so that when the session holding apparatus is accessed next time, the Cookie information is applied to determine the Web container corresponding to the target IPv6/IPv4 dual-stack client.

In order to further improve the reliability of the session holding entry and further improve the effectiveness of session holding by using the reliable session holding entry, in an embodiment of the present application, the Cookie information includes: client identification and Cookie effective time; correspondingly, referring to fig. 3, after generating Cookie information corresponding to the target IPv6/IPv4 dual-stack client in step 003, the method further includes:

step 004: and updating the session holding list item by applying the client identification, the Cookie effective time and the container identification of the Web container.

Specifically, the client identifier may be a client ID generated by applying a hash algorithm, and used for distinguishing different clients; the container identifier may be an IP address, a port number, of a Web container, and is used to distinguish different Web containers, store the client identifier and the container identifier of the Web container in the session holding table entry, so that when receiving a request packet of the target IPv6/IPv4 dual-stack client next time, the updated session holding table entry is applied to determine a Web container corresponding to the target IPv6/IPv4 dual-stack client, so as to ensure that corresponding Web containers are the same when the same client processes request packets of different times. The Cookie effective time can be set according to actual needs, and is preferably 10 minutes.

Because the IPv4 protocol is incompatible with the IPv6 protocol, in order to ensure the reliability of communication between the target IPv6/IPv4 dual-stack client and the session holding apparatus, and further improve the validity of session holding, in an embodiment of the present application, step 100 includes:

and if the target request message is a request message sent based on an IPv4 protocol, receiving the target request message by applying a corresponding IPv4 virtual address.

Because the IPv4 protocol is incompatible with the IPv6 protocol, in order to ensure the reliability of communication between the target IPv6/IPv4 dual-stack client and the session holding apparatus, and further improve the validity of session holding, the receiving of the target request packet containing Cookie information sent by the target IPv6/IPv4 dual-stack client includes:

and if the target request message is a request message sent based on an IPv6 protocol, receiving the target request message by applying a corresponding IPv6 virtual address.

In order to obtain reliable Cookie information and further apply the reliable Cookie information to improve reliability of session maintenance, in an application example of the present application, the preset session maintenance entry includes: client identification, container identification and Cookie valid time;

correspondingly, after the step 300, the method further includes: step 400: updating the Cookie valid time corresponding to the target IPv6/IPv4 dual-stack client in the preset session holding list item; step 500: and sending the Cookie effective time to the target IPv6/IPv4 dual-stack client so that the target IPv6/IPv4 dual-stack client saves the Cookie effective time to the Cookie information and sends a next request message within the Cookie effective time.

From the software aspect, in order to avoid session maintaining failure due to network handover between IPv6 and IPv4, improve effectiveness of session maintaining, and further improve reliability of user transaction process, the present application provides an embodiment of a session maintaining apparatus for implementing all or part of contents in the session maintaining method, and referring to fig. 4, the session maintaining apparatus specifically includes the following contents:

the receiving module 10 is configured to receive a target request packet containing Cookie information sent by a target IPv6/IPv4 dual-stack client.

And the processing module 20 is configured to determine, according to a preset session holding list item and the Cookie information, a target Web container corresponding to the target IPv6/IPv4 dual-stack client, and send the target request packet to the target Web container, so that the target Web container processes the target request packet, where the target Web container is the same as a Web container used for processing an initial request packet of the target IPv6/IPv4 dual-stack client.

A sending module 30, configured to send the processing result of the target request packet to the target IPv6/IPv4 dual-stack client.

In one embodiment of the present application, the processing module includes:

and the protocol conversion unit is used for applying a preset protocol conversion relationship if the IP protocols of the IP addresses corresponding to the target Web container and the Cookie information are different, and converting the IP protocol of the IP address corresponding to the Cookie information into the IP protocol of the IP address corresponding to the target Web container.

And the sending unit is used for applying the IP address converted by the IP protocol corresponding to the Cookie information and sending the target request message to the target Web container.

The embodiment of the session holding apparatus provided in this specification may be specifically configured to execute the processing procedure of the embodiment of the session holding method, and its functions are not described herein again, and refer to the detailed description of the embodiment of the session holding method.

In order to avoid the session maintaining failure caused by the network switching between the IPv6 and the IPv4, and improve the effectiveness of session maintaining, and thus improve the reliability of the user transaction process, the present application provides a session maintaining system, see fig. 5, which includes: IPv6/IPv4 dual-stack client 1, soft load server 2 and Web container 3; the IPv6/IPv4 dual-stack client 1 and the soft load server 2 are connected through an IPv6/IPv4 dual-stack network, the soft load server 2 and the Web container 3 are connected through an IPv6/IPv4 dual-stack network, the dual-stack network comprises a wired network and a wireless network, such as WiFi and 4G, the Web container 3 can be an IPV4 Web container or an IPV6 Web container, and the function realized by the soft load server 2 is equivalent to the session holding device. The specific description is as follows:

IPv6/IPv4 dual-stack client 1 is used for accessing application systems by clients through dual-stack networks.

The soft load Server 2 receives a dual-stack client HTTP request from an externally exposed Virtual Server IP address (VS), allocates a client HTTP request to a rear-end hybrid-deployed Web container pool according to a load balancing algorithm (such as a minimum connection number, a minimum response time, and the like) when a rear-end IPv6 Web container (RS) and an IPv4 Web container are hybrid-deployed in the Web container pool, and allocates a request from the same client to the same rear-end Web container according to a session maintenance algorithm configured by a user.

And the Web container 3 receives the client HTTP request distributed by the soft load equipment, and returns the processing result to the soft load server after the processing is finished.

Fig. 6 is a schematic structural diagram of an IPv6/IPv4 dual-stack client 1 in this application example, and as shown in fig. 6, the dual-stack client 1 includes an IPv4 address unit 11, an IPv6 address unit 12, and a Cookie management unit 13. Wherein:

the IPv4 address unit 11 communicates with a service end, i.e., a soft load server, using an IPv4 protocol. The dual stack client itself has two IP addresses (one IPv4 and one IPv6) that are dynamically assigned by the client operating system. The specific IP address used for communication is determined by the client operating system, and the mainstream operating system is IPv6 in priority. And automatically degrading to the IPv4 network under the condition that the IPv6 network is not communicated, and is transparent to clients. The IPv4 protocol used by the IPv4 address unit 11 and the IPv6 protocol used by the IPv6 address unit 12 are incompatible and cannot communicate with each other.

The IPv6 address unit 12 communicates with the server side by using an IPv6 protocol. The dual stack client itself has two IP addresses (one IPv4 and one IPv6) that are dynamically assigned by the client operating system. The specific IP address used for communication is determined by the client operating system, and the mainstream operating system is IPv6 in priority. And automatically degrading to the IPv4 network under the condition that the IPv6 network is not communicated, and is transparent to clients. The IPv6 protocol used by the IPv6 address unit 12 and the IPv4 protocol used by the IPv4 address unit 11 are incompatible and cannot communicate with each other.

And the Cookie management unit 13 reads the locally stored Cookie information, and if the effective Cookie information exists, the Cookie management unit carries the Cookie information to access the soft load server. And if the HTTP message returned by the soft load server contains the response head of the Set-Cookie, updating the Cookie information stored locally.

Fig. 7 is a schematic structural diagram of the soft load server 2 in this application example, and as shown in fig. 7, the soft load server includes a user request receiving unit 21, a load balancing algorithm unit 22, an IP address hybrid deployment unit 23, a Cookie inserting unit 24, and a Cookie session holding unit 25.

The user request receiving unit 21 exposes a virtual server IP address to the outside, the virtual IPv6 address is used for receiving an IPv6 client HTTP request, and the virtual IPv4 address is used for receiving an IPv4 client HTTP request.

The load balancing algorithm unit 22 determines, according to a load balancing algorithm, for example, the minimum number of connections, the minimum response time, polling, and the like, that the client HTTP request is allocated to the Web container managed by the IP address hybrid deployment unit 23 for processing.

And the IP address hybrid deployment unit 23 is configured to combine the IPv4 address and the IPv6 address of the backend Web container into an IP hybrid deployed address pool, where the address pool serves as an allocation range for client HTTP request processing. The IP address hybrid deployment unit 23 maintains the mapping relationship between the VS address of IPv4 protocol, the VS address of IPv6 protocol, and the rear-end IPv4, IPv6 Web containers, when the user request reaches the VS address of IPv4 or IPv6, allocates any rear-end Web container according to the mapping relationship to process the client request, and if the container IP protocol and the client IP protocol are not consistent, the load balancing server performs protocol conversion. In general, the IP address mixing deployment unit 23 reads data in the Web container registration information storage component by the configuration management tool to acquire and update the IP address mixing pool it maintains in real time.

The Cookie insertion unit 24 generates a client ID by using a hash algorithm, and writes the client ID into an HTTP message through a Set-Cookie response packet and returns the HTTP message to the client.

And the Cookie session holding unit 25 is responsible for distributing the request of the same client ID to the same Web container for processing and refreshing the session holding effective time so as to realize session holding. The Cookie session holding unit judges whether the client carries Cookie information, reads the user ID in the Cookie information, and acquires a session holding list item (shown in the following table) of the user ID. The session holding table item represents the corresponding relation between the client and the Web container, and the Web container can be an IPv6 Web container or an IPv4 Web container through the unique identification of an IP address, namely a port number.

Fig. 8 is a schematic structural diagram of the Web container 3 in the present application example. As shown in fig. 8, the Web container includes a user request receiving unit 31, a container addressing unit 32, and a container request processing unit 33.

The user request receiving unit 31 is configured to expose the IP address + service port of the host to the outside, and is configured to receive the user request forwarded from the soft load server.

The container addressing unit 32 manages a correspondence between the "host IP address + service port" and the "container private address + service port", and is used to request an addressing process to the container.

And a container request processing unit 33, configured to process the user request and return a result.

In combination with the session maintaining system provided by the above application example, the application also provides an application example of a session maintaining method, referring to fig. 9, the processing flow is as follows:

step S101: the IPv6 address unit sends the client HTTP request using the IPv6 address: the dual stack client sends the HTTP request using the IPv6 address.

Step S102: the user request receiving unit receives the client request using the virtual address of the IPv 6.

Step S103: and the load balancing algorithm unit distributes the request to one Web container in the address pool of the mixed deployment according to the load balancing strategy.

Step S104: : the Cookie inserting unit generates a client ID, and the Cookie session maintaining unit records the client request distribution result and updates the session maintaining list item.

Step S105: the Web container receives and processes the client request: and returns the processing result to the soft load server.

Step S106: and the Cookie inserting unit inserts the client ID into the Cookie in the return message.

Step S107: and the client receives the return of the load balancing server and stores the Cookie information.

Step S108: the double-stack client end generates IP address drift: multiple HTTP request interactions may exist in one complete transaction process, the network IPv6 is unstable when a certain HTTP request is made, and IP address drift occurs in the dual-stack client.

Step S109: and the Cookie management unit reads the locally valid Cookie information.

Step S110: the IPv4 address unit sends the client HTTP request (containing a Cookie) using the IPv4 address.

Step S111: the user request receiving unit receives the client request using the IPv4 virtual address.

Step S112: and the Cookie session holding unit reads Cookie information in the HTTP request and acquires a session holding list item corresponding to the user ID.

Step S113: and the load balancing algorithm unit distributes according to the session maintaining table items.

Step S114: the Web container receives, processes and returns the client request.

Step S115: the Cookie session holding unit updates the session holding table entry, such as the Cookie valid time and the like.

Step S116: and the client receives the Cookie information returned by the load balancing server and updates the Cookie information stored locally.

As can be seen from the above description, the session maintaining method and apparatus provided by the present application can avoid session maintaining failure caused by network switching between IPv6 and IPv4, can improve the validity of session maintaining, and can further improve the reliability of the user transaction process; specifically, the mixed deployment of the container based on the IPv4 address and the IPv6 address on the session holding device can solve the problem that the client transaction cannot be normally processed under the condition that an IPv6 network is unstable or the environment of the client network changes. Its advantages are as follows: 1. the hybrid deployment of the Web container with the IPv4 address and the Web container with the IPv6 address is realized, a large address pool is formed and exposed to the session holding device, and when the IP address of the client drifts, the soft load server can load the client request to the original Web container, so that the usability of transaction can be improved. 2. In the initial stage of IPv6 network construction and popularization, under the condition that the IPv6 network stability cannot be guaranteed, the client request is automatically distributed to the address pool of the IPv4 through the session maintaining device, and the session maintaining device is transparent to the client, so that the transaction can be continuously processed, and the transaction experience of the client can be further improved.

In terms of hardware, in order to avoid session maintaining failure due to network handover between IPv6 and IPv4, improve effectiveness of session maintaining, and further improve reliability of a user transaction process, the present application provides an embodiment of an electronic device for implementing all or part of contents in the session maintaining method, where the electronic device specifically includes the following contents:

a processor (processor), a memory (memory), a communication Interface (Communications Interface), and a bus; the processor, the memory and the communication interface complete mutual communication through the bus; the communication interface is used for realizing information transmission between the session holding device and relevant equipment such as a user terminal and the like; the electronic device may be a desktop computer, a tablet computer, a mobile terminal, and the like, but the embodiment is not limited thereto. In this embodiment, the electronic device may be implemented with reference to the embodiment for implementing the session maintaining method and the embodiment for implementing the session maintaining apparatus in the embodiments, and the contents thereof are incorporated herein, and repeated details are not repeated.

Fig. 10 is a schematic block diagram of a system configuration of an electronic device 9600 according to an embodiment of the present application. As shown in fig. 10, the electronic device 9600 can include a central processor 9100 and a memory 9140; the memory 9140 is coupled to the central processor 9100. Notably, this fig. 10 is exemplary; other types of structures may also be used in addition to or in place of the structure to implement telecommunications or other functions.

In one or more embodiments of the present application, the session-holding function can be integrated into the central processor 9100. The central processor 9100 may be configured to control as follows:

As can be seen from the above description, the electronic device provided in the embodiment of the present application can avoid session maintenance failure caused by network handover between IPv6 and IPv4, improve the effectiveness of session maintenance, and further improve the reliability of the user transaction process.

In another embodiment, the session holding apparatus may be configured separately from the central processor 9100, for example, the session holding apparatus may be configured as a chip connected to the central processor 9100, and the session holding function is realized by the control of the central processor.

As shown in fig. 10, the electronic device 9600 may further include: a communication module 9110, an input unit 9120, an audio processor 9130, a display 9160, and a power supply 9170. It is noted that the electronic device 9600 also does not necessarily include all of the components shown in fig. 10; in addition, the electronic device 9600 may further include components not shown in fig. 10, which can be referred to in the prior art.

As shown in fig. 10, a central processor 9100, sometimes referred to as a controller or operational control, can include a microprocessor or other processor device and/or logic device, which central processor 9100 receives input and controls the operation of the various components of the electronic device 9600.

The memory 9140 can be, for example, one or more of a buffer, a flash memory, a hard drive, a removable media, a volatile memory, a non-volatile memory, or other suitable device. The information relating to the failure may be stored, and a program for executing the information may be stored. And the central processing unit 9100 can execute the program stored in the memory 9140 to realize information storage or processing, or the like.

The input unit 9120 provides input to the central processor 9100. The input unit 9120 is, for example, a key or a touch input device. Power supply 9170 is used to provide power to electronic device 9600. The display 9160 is used for displaying display objects such as images and characters. The display may be, for example, an LCD display, but is not limited thereto.

The memory 9140 can be a solid state memory, e.g., Read Only Memory (ROM), Random Access Memory (RAM), a SIM card, or the like. There may also be a memory that holds information even when power is off, can be selectively erased, and is provided with more data, an example of which is sometimes called an EPROM or the like. The memory 9140 could also be some other type of device. Memory 9140 includes a buffer memory 9141 (sometimes referred to as a buffer). The memory 9140 may include an application/function storage portion 9142, the application/function storage portion 9142 being used for storing application programs and function programs or for executing a flow of operations of the electronic device 9600 by the central processor 9100.

The memory 9140 can also include a data store 9143, the data store 9143 being used to store data, such as contacts, digital data, pictures, sounds, and/or any other data used by an electronic device. The driver storage portion 9144 of the memory 9140 may include various drivers for the electronic device for communication functions and/or for performing other functions of the electronic device (e.g., messaging applications, contact book applications, etc.).

The communication module 9110 is a transmitter/receiver 9110 that transmits and receives signals via an antenna 9111. The communication module (transmitter/receiver) 9110 is coupled to the central processor 9100 to provide input signals and receive output signals, which may be the same as in the case of a conventional mobile communication terminal.

Based on different communication technologies, a plurality of communication modules 9110, such as a cellular network module, a bluetooth module, and/or a wireless local area network module, may be provided in the same electronic device. The communication module (transmitter/receiver) 9110 is also coupled to a speaker 9131 and a microphone 9132 via an audio processor 9130 to provide audio output via the speaker 9131 and receive audio input from the microphone 9132, thereby implementing ordinary telecommunications functions. The audio processor 9130 may include any suitable buffers, decoders, amplifiers and so forth. In addition, the audio processor 9130 is also coupled to the central processor 9100, thereby enabling recording locally through the microphone 9132 and enabling locally stored sounds to be played through the speaker 9131.

Embodiments of the present application further provide a computer-readable storage medium capable of implementing all steps in the session holding method in the foregoing embodiments, where the computer-readable storage medium stores thereon a computer program, and when the computer program is executed by a processor, the computer program implements all steps of the session holding method in the foregoing embodiments, for example, when the processor executes the computer program, the processor implements the following steps:

As can be seen from the above description, the computer-readable storage medium provided in the embodiment of the present application can avoid session maintenance failure due to network handover between IPv6 and IPv4, improve the effectiveness of session maintenance, and further improve the reliability of the user transaction process.

In the present application, each embodiment of the method is described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. Reference is made to the description of the method embodiments.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

The principle and the implementation mode of the present application are explained by applying specific embodiments in the present application, and the description of the above embodiments is only used to help understanding the method and the core idea of the present application; meanwhile, for a person skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.

Claims

1. A session maintenance method, comprising:

2. The session holding method according to claim 1, wherein said sending the target request packet to the target Web container comprises:

if the IP protocols of the IP addresses corresponding to the target Web container and the Cookie information are different, applying a preset protocol conversion relation to convert the IP protocol of the IP address corresponding to the Cookie information into the IP protocol of the IP address corresponding to the target Web container;

and applying the IP address converted by the IP protocol corresponding to the Cookie information to send the target request message to a target Web container.

3. The session holding method according to claim 1, wherein before receiving the target request packet containing Cookie information sent by the target IPv6/IPv4 dual-stack client, the method further comprises:

receiving an initial request message sent by the target IPv6/IPv4 dual-stack client;

determining a Web container corresponding to the target IPv6/IPv4 dual-stack client according to a load balancing algorithm so that the Web container processes the initial request message;

generating Cookie information corresponding to the target IPv6/IPv4 dual-stack client, and sending the Cookie information and the processing result of the initial request message to the target IPv6/IPv4 dual-stack client.

4. The session holding method according to claim 3, wherein the Cookie information comprises: client identification and Cookie effective time;

correspondingly, after generating the Cookie information corresponding to the target IPv6/IPv4 dual-stack client, the method further includes:

and updating the session holding list item by applying the client identification, the Cookie effective time and the container identification of the Web container.

5. The session holding method of claim 1, wherein the receiving the target request packet containing Cookie information sent by the target IPv6/IPv4 dual-stack client comprises:

6. The session holding method of claim 1, wherein the receiving the target request packet containing Cookie information sent by the target IPv6/IPv4 dual-stack client comprises:

7. A session-holding apparatus, comprising:

8. The session holding apparatus according to claim 7, wherein the processing module comprises:

the protocol conversion unit is used for applying a preset protocol conversion relationship if the IP protocols of the IP addresses corresponding to the target Web container and the Cookie information are different, and converting the IP protocol of the IP address corresponding to the Cookie information into the IP protocol of the IP address corresponding to the target Web container;

9. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the session holding method of any one of claims 1 to 6 when executing the program.

10. A computer readable storage medium having computer instructions stored thereon that, when executed, implement the session-keeping method of any of claims 1 to 6.