CN114827239A - Bidirectional session holding method and device based on 8583 protocol - Google Patents
Bidirectional session holding method and device based on 8583 protocol Download PDFInfo
- Publication number
- CN114827239A CN114827239A CN202210608610.4A CN202210608610A CN114827239A CN 114827239 A CN114827239 A CN 114827239A CN 202210608610 A CN202210608610 A CN 202210608610A CN 114827239 A CN114827239 A CN 114827239A
- Authority
- CN
- China
- Prior art keywords
- client
- protocol
- virtual service
- session
- load balancing
- 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.)
- Withdrawn
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/12—Avoiding congestion; Recovering from congestion
- H04L47/125—Avoiding congestion; Recovering from congestion by balancing the load, e.g. traffic engineering
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/143—Termination or inactivation of sessions, e.g. event-controlled end of session
- H04L67/145—Termination or inactivation of sessions, e.g. event-controlled end of session avoiding end of session, e.g. keep-alive, heartbeats, resumption message or wake-up for inactive or interrupted session
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/26—Special purpose or proprietary protocols or architectures
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computing Systems (AREA)
- Computer Security & Cryptography (AREA)
- Health & Medical Sciences (AREA)
- Cardiology (AREA)
- General Health & Medical Sciences (AREA)
- Computer And Data Communications (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The present disclosure relates to a bidirectional session maintaining method and device based on 8583 protocol, the method includes: creating a first virtual service and a second virtual service, wherein the first virtual service is used for establishing long connection with a client, and the second virtual service is used for establishing connection with a real server; acquiring an 8583 protocol request message sent by a client through a first virtual service; acquiring client identification information in the 8583 protocol message and creating a session maintaining table item based on the client identification information, wherein the session maintaining table item comprises common characteristic information of the 8583 protocol request message; distributing the 8583 protocol request message to a real server through a first virtual service based on a load balancing strategy; receiving response messages of the real server through the second virtual service, wherein the response messages all comprise common characteristic information of the 8583 protocol request message; and extracting the common characteristic information in the response message, and after the common characteristic information is successfully matched in the session holding list item, the second virtual service sends the response message to the client.
Description
Technical Field
The present disclosure relates to the field of load balancing technologies, and in particular, to a bidirectional session holding method and apparatus based on 8583 protocol.
Background
Load balancing, namely, access traffic or tasks are guided to a plurality of servers or network devices for processing in a balanced manner, so as to achieve the purposes of increasing the bandwidth of the devices and the servers, increasing throughput, enhancing data processing capacity, and improving availability and stability of services. When load balancing equipment is deployed between a client and a server, multiple connections may be forwarded to different servers for processing, and at this time, if there is no session information synchronization mechanism between the servers, other servers may not recognize the user identity, which causes an abnormality in interaction between the user and an application system. For example, in most e-commerce applications or online systems that require user authentication, a single client and server often go through several interactions to complete a transaction or a request. Because the several interactive processes are closely related, when a server performs one of the interactive steps, the processing result of the previous interactive process or the processing results of the previous interactive processes often need to be known, so that when the server performs the next operation, all the related interactive processes need to be completed by one server and cannot be dispersed to different servers by the load balancer.
The above-mentioned series of related interactive processes may be completed by multiple sessions of one connection from the client to the server, or may be completed by multiple sessions in multiple different connections between the client and the server. For example, in the case of multiple sessions with different connections, the most typical example is http-based access, where a client may need multiple clicks to complete a transaction, and a new click may generate a request to reuse the connection established by the previous click or a newly created connection.
The application of various session holding methods in the load balancing device can well solve the problems, such as cookie session holding, source IP session holding, HASH session holding and the like. The essence of the above-mentioned types of session holding methods is to form a mechanism on the load balancer, which can identify the correlation of the interaction process between the client and the server, so as to ensure that the access request with correlation can be distributed to one server while realizing load balancing.
The POS machine product used in the organizations such as the bank and the like uses the scenes that the client establishes long connection with the server load balancing equipment, the equipment needs to distribute the session to different servers for the 8583 protocol request on the long connection, and the 8583 protocol message replied by the requested servers needs to be sent to the client sending the request through the same connection session. Current session-holding mechanisms cannot meet this requirement.
Therefore, a method and an apparatus for bidirectional session maintenance based on 8583 protocol are needed, which can solve the problem that after long connection request messages are load balanced to different servers, response messages are sent to clients through the same session.
Disclosure of Invention
In view of the above, the present disclosure provides a bidirectional session holding method and apparatus based on 8583 protocol. According to an aspect of the present disclosure, a bidirectional session holding method based on 8583 protocol is provided, the method comprising: creating a first virtual service and a second virtual service in a load balancing device, wherein the first virtual service is used for establishing long connection between the load balancing device and a client, and the second virtual service is used for establishing connection between the load balancing device and a real server; receiving data traffic sent by a client through long connection through the first virtual service and acquiring a plurality of 8583 protocol request messages included in the data traffic based on the data traffic; acquiring identification information of a client included in a 8583 protocol message according to a 8583 protocol rule, and creating a session holding table item based on the acquired identification information of the client, wherein the session holding table item includes common characteristic information of a plurality of 8583 protocol request messages; sending the 8583 protocol request messages to each designated real server through the first virtual service based on a load balancing strategy; receiving response messages aiming at 8583 protocol request messages sent by the appointed real servers through the second virtual service, wherein the response messages all comprise the common characteristic information which is included in the plurality of 8583 protocol request messages and aimed at by the appointed real servers; and extracting the common characteristic information included in the response message, and after the common characteristic information is successfully matched in the session maintaining table item, the second virtual service sends the response message to the client through the connection with the client corresponding to the matched client identifier.
According to the bidirectional session keeping method based on the 8583 protocol, after the session is established between the first virtual service and the real server, a new session is not established any more, and the session is reused when the real server needs to receive a 8583 protocol request message of a new client.
According to the bidirectional session keeping method based on the 8583 protocol, after the 8583 protocol request message is sent to each appointed real server based on the load balancing strategy, no new connection is established between the load balancing equipment and each appointed real server, and each connection is reused when each appointed real server needs to receive the 8583 protocol request message of a new client.
According to the bidirectional session holding method based on the 8583 protocol, when data traffic sent by a client through a long connection is received through the first virtual service and a plurality of 8583 protocol request messages included in the client are obtained based on the data traffic, the received data traffic is split based on a byte identification length preset by the client to obtain the 8583 protocol request messages.
The bidirectional session holding method based on the 8583 protocol according to the present disclosure, wherein the identification information of the client includes an IP address and a port number of the client.
According to another aspect of the present disclosure, a bidirectional session holding apparatus based on 8583 protocol is provided, the apparatus comprising: the virtual service creating component is used for creating a first virtual service and a second virtual service in the load balancing equipment, wherein the first virtual service is used for establishing long connection between the load balancing equipment and a client, and the second virtual service is used for establishing connection between the load balancing equipment and a real server; a request message obtaining component, configured to receive, through the first virtual service, data traffic sent by a client via a long connection, and obtain, based on the data traffic, a plurality of 8583 protocol request messages included in the request message; a session holding table item creating component, configured to obtain identification information of a client included in a 8583 protocol packet according to a 8583 protocol rule, and create a session holding table item based on the obtained identification information of the client, where the session holding table item includes common feature information of the plurality of 8583 protocol request packets; the load balancing component is used for sending the plurality of 8583 protocol request messages to each designated real server through the first virtual service based on a load balancing strategy; a response message receiving component, configured to receive, through the second virtual service, response messages that are sent by each designated real server and are directed to 8583 protocol request messages, where the response messages all include the common characteristic information included in the plurality of 8583 protocol request messages that are commonly directed to the designated real servers; and the response message forwarding component is used for extracting the common characteristic information included in the response message, and after the common characteristic information is successfully matched in the session holding list item, the second virtual service sends the response message to the client after connecting with the client corresponding to the matched client identifier.
According to the bidirectional session holding device based on the 8583 protocol, after the session is established between the first virtual service and the real server, a new session is not established any more, and the session is reused when the real server needs to receive a 8583 protocol request message of a new client.
According to the bidirectional session holding device based on the 8583 protocol, after the 8583 protocol request message is sent to each designated real server based on the load balancing strategy, no new connection is established between the load balancing equipment and each designated real server, and each connection is reused when each designated real server needs to receive the 8583 protocol request message of a new client.
According to the bidirectional session holding device based on 8583 protocol of the present disclosure, the request packet obtaining component is further configured to: when receiving data traffic sent by a client through long connection through the first virtual service and acquiring a plurality of 8583 protocol request messages included in the client based on the data traffic, splitting the received data traffic based on a byte identification length preset by the client to acquire the 8583 protocol request messages.
The bidirectional session holding apparatus based on the 8583 protocol according to the present disclosure, wherein the identification information of the client includes an IP address and a port number of the client.
In summary, the method and the device for holding the bidirectional session based on the 8583 protocol realize bidirectional session holding through the session holding table item of the cross-virtual service and the session multiplexing function, and solve the problem that the 8583 protocol response message of each server is sent to the client through the same session after the long connection 8583 protocol request message of the client is sent to different servers.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.
Drawings
The above and other objects, features and advantages of the present application will become more apparent by describing in detail exemplary embodiments thereof with reference to the attached drawings. The drawings described below are only some embodiments of the present application, and other drawings may be derived from those drawings by those skilled in the art without inventive effort.
Fig. 1 is a flow chart illustrating a bidirectional session holding method based on 8583 protocol according to an embodiment of the disclosure.
FIG. 2 is a diagram illustrating an example scenario of a bidirectional session holding method based on the 8583 protocol according to an embodiment of the present disclosure.
Fig. 3 is a schematic diagram of a bidirectional session holding apparatus based on 8583 protocol according to an embodiment of the disclosure.
Detailed Description
Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art. The same reference numerals denote the same or similar parts in the drawings, and thus, a repetitive description thereof will be omitted.
Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the disclosure. One skilled in the relevant art will recognize, however, that the subject matter of the present disclosure can be practiced without one or more of the specific details, or with other methods, components, devices, steps, and so forth. In other instances, well-known methods, systems, implementations, or operations have not been shown or described in detail to avoid obscuring aspects of the present disclosure.
The block diagrams shown in the figures are functional entities only and do not necessarily correspond to physically separate entities. I.e. these functional entities may be implemented in the form of software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor means and/or microcontroller means.
The flow charts shown in the drawings are merely illustrative and do not necessarily include all of the contents and operations/steps, nor do they necessarily have to be performed in the order described. For example, some operations/steps may be decomposed, and some operations/steps may be combined or partially combined, so that the actual execution sequence may be changed according to the actual situation.
It is to be understood by those skilled in the art that the drawings are merely schematic representations of exemplary embodiments, and that the blocks or processes shown in the drawings are not necessarily required to practice the present disclosure and are, therefore, not intended to limit the scope of the present disclosure.
Load balancing is to guide access traffic or tasks to multiple servers or network devices for processing in a balanced manner, so as to achieve the purposes of increasing the bandwidth of the devices and servers, increasing throughput, enhancing data processing capacity, and improving availability and stability of services.
The 8583 protocol is a communication protocol based on the packet format of the international standard for ISO8583 messages. 8583 the packet is composed of 128 field fields each having a uniform specification and having a fixed length and a variable length. 8583 the front part of the packet is a bitmap, which is a key substitute for the field determined by the unpacking. The 8583 protocol is mostly used in the development of POS.
Session maintenance refers to a mechanism on a load balancer that identifies the dependencies of interactions between clients and servers, and also ensures that a series of associated access requests are distributed to a machine while load balancing is performed.
Fig. 1 is a flow chart illustrating a bidirectional session holding method based on 8583 protocol according to an embodiment of the disclosure. FIG. 2 is a diagram illustrating an example scenario of a bidirectional session holding method based on the 8583 protocol according to an embodiment of the present disclosure.
As shown in fig. 1, in step S102, a first virtual service and a second virtual service are created. Specifically, a first virtual service and a second virtual service are created in a load balancing device, the first virtual service is used for establishing a long connection between the load balancing device and a client, and the second virtual service is used for establishing a connection between the load balancing device and a real server.
More specifically, as shown in fig. 2, a virtual service VS1 and a virtual service VS2 are created on the load balancing device, wherein the client 1 establishes a long connection with a virtual service VS1 in the load balancing device, and the server 1, the server 2, and the server 3 establish a connection with the load balancing device through the virtual service VS 2.
In step S104, a request packet sent by the client is obtained through the first virtual service. Specifically, data traffic sent by a client through a long connection is received through the first virtual service, and a plurality of 8583 protocol request messages included in the data traffic are obtained based on the data traffic.
More specifically, as shown in fig. 2, the load balancing device receives, through a first virtual service VS1, data traffic carrying an 8583 protocol packet sent by a client 1, and acquires the 8583 protocol packet included in the data traffic based on the received data traffic.
In step S106, load balancing processing is performed. The method comprises the steps of obtaining identification information of a client included in a 8583 protocol message according to 8583 protocol rules, and creating a session holding table item based on the obtained identification information of the client, wherein the session holding table item includes common characteristic information of a plurality of 8583 protocol request messages.
More specifically, the virtual service VS1 in the load balancing device collects the tag information capable of identifying the client 1 information in the received 8583 protocol message according to the rule of the 8583 protocol, and creates a session holding table entry according to the collected tag information of the client 1, where the session holding table entry simultaneously stores the IP and port information of the client 1 (for session holding use in searching for the client information).
In step S108, load balancing processing is performed. Specifically, the 8583 protocol request messages are sent to the designated real servers through the first virtual service based on a load balancing policy.
More specifically, the virtual service VS1 in the load balancing device is distributed to the backend servers according to the configured load balancing algorithm (the disclosed embodiment adopts a polling method by default). As shown in fig. 2, virtual service VS1 in the load balancing appliance distributes the request of client 1 to server 1, server 2, and server 3.
In step S110, a response message is received through the second virtual service. Specifically, response messages sent by each designated real server and aiming at the 8583 protocol request messages are received through the second virtual service, and each response message includes the common characteristic information included in the plurality of 8583 protocol request messages which are aimed at by each designated real server.
More specifically, for a request sent by the client 1 to a server through a long connection established with the virtual service VS1 in the load balancing device, the load balancing device sends the request to different servers through a load balancing algorithm, and 8583 protocol response messages of the servers for the requests all carry contents with the same characteristics in a request message of the client 1. As shown in fig. 2, that is, the 8583 response message replied by the server 1 to the client 1, the 8583 response message replied by the server 2 to the client 1, and the 8583 response message replied by the server 3 to the client 1 all carry the contents with the same characteristics in the request message of the client 1.
In step S112, the second virtual service forwards the response packet to the client based on the session maintenance entry. Specifically, the second virtual service forwards the response packet to the client based on the session holding list item, extracts the common feature information included in the response packet, and sends the response packet to the client after the common feature information is successfully matched in the session holding list item and the second virtual service connects with the client corresponding to the matched client identifier.
More specifically, as shown in fig. 2, the response messages sent by the server 1, the server 2, and the server 3 to the client 1 are requests sent by the server 1, the server 2, and the server 3 through the virtual service VS2 of the load balancing device, and after receiving the requests, the virtual service VS2 of the load balancing device establishes a connection with the client 1 to reply to the 8583 protocol message.
More specifically, when the virtual service VS2 in the load balancing device receives the 8583 protocol packet sent by each server, the feature information of the received 8583 protocol packet is extracted, then the extracted feature information is searched and compared with the feature information in the session holding table entry created by the client 1 accessing the virtual service VS1 in the load balancing device, and if the table entry with the same value as the feature information is searched in the session holding table entry, the virtual service VS2 in the load balancing device schedules the received response packet of the server to the client 1 corresponding to the IP and the port number stored in the matched session holding table entry.
According to the bidirectional session keeping method based on the 8583 protocol, after the session is established between the first virtual service and the real server, a new session is not established any more, and the session is reused when the real server needs to receive a 8583 protocol request message of a new client.
More specifically, for a virtual service in a load balancing device, it establishes only one session with a real service (i.e., a real server). After the session is established, requests sent by different clients to the server multiplex the session.
In the process of message interaction between the client and the server, session maintenance entries created by different virtual services in the load balancing device can be hit by other virtual services, so as to realize the function of bidirectional session maintenance.
According to the bidirectional session maintaining method based on the 8583 protocol, after the 8583 protocol request message is sent to each designated real server based on the load balancing strategy, no new connection is established between the load balancing device and each designated real server, and each connection is reused when each designated real server needs to receive the 8583 protocol request message of a new client.
More specifically, after the client 2 establishes a long connection with the virtual service VS1 of the load balancing device, the load balancing device sends the received 8583 protocol message sent by the client 2 to a different server according to the configured load balancing algorithm. Each server establishes only one connection with the load balancing device. The request of the client 2 sends 8583 protocol request message to the server by multiplexing the connection established when the client 1 requests.
According to the bidirectional session maintaining method based on the 8583 protocol, when data traffic sent by a client through a long connection is received through the first virtual service and a plurality of 8583 protocol request messages included in the data traffic are obtained based on the data traffic, the received data traffic is split based on a byte identification length preset by the client to obtain the 8583 protocol request messages.
More specifically, the client 1 sends data with the same byte identifier length to the virtual service VS1 of the load balancing device through a long connection established with the load balancing device, and the load balancing device splits the data sent by the client 1 into 8583 protocol request messages with the same length according to the byte identifier length after receiving data traffic.
According to the bidirectional session holding method based on the 8583 protocol, the identification information of the client comprises the IP address and the port number of the client.
Fig. 3 is a schematic diagram of a bidirectional session holding apparatus based on 8583 protocol according to an embodiment of the disclosure, the apparatus including: virtual service creation component 302, request message acquisition component 304, session maintenance entry creation component 306, load balancing component 308, reply message receiving component 310, and reply message forwarding component 312.
A virtual service creation component 302, configured to create a first virtual service and a second virtual service in a load balancing device, where the first virtual service is used to establish a long connection between the load balancing device and a client, and the second virtual service is used to establish a connection between the load balancing device and a real server;
a request message obtaining component 304, configured to receive, through the first virtual service, data traffic sent by a client via a long connection, and obtain, based on the data traffic, a plurality of 8583 protocol request messages included in the request message;
a session holding table creation component 306, configured to obtain identification information of a client included in a 8583 protocol packet according to a 8583 protocol rule, and create a session holding table based on the obtained identification information of the client, where the session holding table includes common feature information of the plurality of 8583 protocol request packets;
a load balancing component 308, configured to send the 8583 protocol request messages to each designated real server through the first virtual service based on a load balancing policy;
a response message receiving component 310, configured to receive, through the second virtual service, response messages that are sent by each designated real server and are directed to 8583 protocol request messages, where each of the response messages includes the common characteristic information included in the plurality of 8583 protocol request messages that are commonly directed to the designated real servers;
and the response message forwarding component 312 is configured to extract the common feature information included in the response message, and after the common feature information is successfully matched in the session holding table, the second virtual service sends the response message to the client through connection with the client corresponding to the matched client identifier.
According to the bidirectional session holding device based on the 8583 protocol, after the session is established between the first virtual service and the real server, a new session is not established any more, and the session is reused when the real server needs to receive a 8583 protocol request message of a new client.
According to the bidirectional session holding device based on the 8583 protocol in the embodiment of the present disclosure, after sending the 8583 protocol request packet to each designated real server based on the load balancing policy, the load balancing device does not establish a new connection with each designated real server any more, and each designated real server multiplexes each connection when it needs to receive the 8583 protocol request packet of the new client.
According to the bidirectional session holding apparatus based on 8583 protocol in the embodiment of the present disclosure, the request packet obtaining component 304 is further configured to: when receiving data traffic sent by a client through long connection through the first virtual service and acquiring a plurality of 8583 protocol request messages included in the client based on the data traffic, splitting the received data traffic based on a byte identification length preset by the client to acquire the 8583 protocol request messages.
The bidirectional session holding device based on the 8583 protocol according to the embodiment of the present disclosure, wherein the identification information of the client includes an IP address and a port number of the client.
In summary, the bidirectional session maintaining method and device based on the 8583 protocol disclosed by the invention realize bidirectional session maintaining through the session maintaining table item crossing virtual services and the session multiplexing function, and solve the problem that after a long connection 8583 protocol request message of a client is sent to different servers, a 8583 protocol response message of each server is sent to the client through the same session.
In general, in order to realize that a client long connection request message is sent to different servers, and a server reply message is sent to the client through the same session, according to the disclosure, a long connection is first established between the client 1 and a virtual service VS1 of a load balancing device, data with the same byte identifier length is sent to a virtual service VS1 of the load balancing device through the long connection client 1, the load balancing device splits the data sent by the client 1 into 8583 protocol messages with the same length according to the byte identifier length, and the virtual service VS1 of the load balancing device is distributed to a background server according to a configured load balancing algorithm (default polling). For data packet load balancing device virtual service VS1, tag information that can identify client 1 information is collected according to the rules of the 8583 protocol. And creating a session holding table direction through the tag information, wherein the table direction simultaneously stores the ip and port information of the client (the session holding is used for searching the client information). Next, requests sent to different servers over the long connection established by the virtual service VS1 of the client 1 and the load balancing device are sent to different servers through a load balancing algorithm, and 8583 protocol reply messages of the respective servers for the requests carry contents with the same characteristics in the request message of the client 1. Each server and load balancing device establishes a connection with the virtual service VS 2. When the virtual service VS2 of the load balancing device receives the 8583 protocol messages sent by each server, extracting message characteristic information, searching and comparing the message characteristic information with special information in a session holding table direction created by the virtual service VS1 accessed by the client 1, and if the characteristic values of the table directions are the same, scheduling the reply messages of the servers to the client 1 corresponding to the ip and the port stored in the matched session holding table direction by the virtual service VS2 of the load balancing device. Then, for the virtual service of the load balancing device, the virtual service establishes only one session with the real service (i.e., server). After the session is established, the requests sent by different clients to the server all multiplex the session. Then, in the process of completing the message interaction between the client and the server, the session holding table created by different virtual services of the load balancing device may be hit by other virtual services, so as to implement the function of bidirectional session holding, for the reply message from each server to the client 1, the reply message is a request sent by each server through the virtual service VS2 of the load balancing device, and after receiving the request, the virtual service VS2 of the load balancing device establishes a connection with the client 1 to reply the 8583 message. Finally, after the client 2 establishes a long connection with the virtual service VS1 of the load balancing device, the load balancing device sends an 8583 message to a different server according to the configured load balancing algorithm. Each server establishes only one connection with the load balancing device. The requests of different clients send 8583 protocol request messages to the server by multiplexing the connection. Thus, it is ensured that the response message of the 8583 request message distributed by the client to each server returns to the client through the same session, and bidirectional session holding is realized by exaggerating the session holding table of the virtual service and the session multiplexing function.
The software product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
The computer readable storage medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A readable storage medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a readable storage medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Program code for carrying out operations of the present application may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and 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).
Those skilled in the art will appreciate that the modules described above may be distributed in the apparatus as described in the embodiments, and that corresponding changes may be made in one or more apparatus that are unique from the embodiments. The modules of the above embodiments may be combined into one module, or further split into multiple sub-modules.
Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution according to the embodiment of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which can be a personal computer, a server, a mobile terminal, or a network device, etc.) to execute the method according to the embodiment of the present application.
Exemplary embodiments of the present application are specifically illustrated and described above. It is to be understood that the application is not limited to the details of construction, arrangement, or method of implementation described herein; on the contrary, the intention is to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.
Claims (10)
1. A bidirectional session holding method based on 8583 protocol, comprising:
creating a first virtual service and a second virtual service in a load balancing device, wherein the first virtual service is used for establishing long connection between the load balancing device and a client, and the second virtual service is used for establishing connection between the load balancing device and a real server;
receiving data traffic sent by a client through long connection through the first virtual service and acquiring a plurality of 8583 protocol request messages included in the data traffic based on the data traffic;
acquiring identification information of a client included in a 8583 protocol message according to a 8583 protocol rule, and creating a session holding table item based on the acquired identification information of the client, wherein the session holding table item includes common characteristic information of a plurality of 8583 protocol request messages;
sending the plurality of 8583 protocol request messages to each appointed real server through the first virtual service based on a load balancing strategy;
receiving response messages aiming at 8583 protocol request messages sent by the appointed real servers through the second virtual service, wherein the response messages all comprise the common characteristic information which is included in the plurality of 8583 protocol request messages and aimed at by the appointed real servers;
and extracting the common characteristic information included in the response message, and after the common characteristic information is successfully matched in the session holding list item, the second virtual service sends the response message to the client through the connection with the client corresponding to the matched client identifier.
2. The bidirectional session holding method based on 8583 protocol according to claim 1, wherein,
after the session is established between the first virtual service and the real server, no new session is established any more, and the session is reused when the real server needs to receive the 8583 protocol request message of the new client.
3. The bidirectional session-keeping method based on 8583 protocol according to claim 1, wherein after sending 8583 protocol request message to each designated real server based on load balancing policy,
and no new connection is established between the load balancing equipment and each appointed real server, and each connection is multiplexed when each appointed real server needs to receive the 8583 protocol request message of the new client.
4. The bidirectional session holding method based on 8583 protocol according to claim 1, wherein, when receiving data traffic sent by a client via a long connection through the first virtual service and obtaining a number of 8583 protocol request messages included therein based on the data traffic,
and splitting the received data traffic based on the byte identification length preset by the client to obtain the 8583 protocol request message.
5. The bidirectional session holding method based on 8583 protocol according to claim 1, wherein,
the identification information of the client includes an IP address and a port number of the client.
6. A bidirectional session holding apparatus based on 8583 protocol, comprising:
the virtual service creating component is used for creating a first virtual service and a second virtual service in the load balancing equipment, wherein the first virtual service is used for establishing long connection between the load balancing equipment and a client, and the second virtual service is used for establishing connection between the load balancing equipment and a real server;
a request message obtaining component, configured to receive, through the first virtual service, data traffic sent by a client via a long connection, and obtain, based on the data traffic, a plurality of 8583 protocol request messages included in the request message;
a session holding table item creating component, configured to obtain identification information of a client included in a 8583 protocol packet according to a 8583 protocol rule, and create a session holding table item based on the obtained identification information of the client, where the session holding table item includes common feature information of the plurality of 8583 protocol request packets;
the load balancing component is used for sending the plurality of 8583 protocol request messages to each designated real server through the first virtual service based on a load balancing strategy;
a response message receiving component, configured to receive, through the second virtual service, response messages that are sent by each designated real server and are directed to 8583 protocol request messages, where the response messages all include the common characteristic information included in the plurality of 8583 protocol request messages that are commonly directed to the designated real servers;
and the response message forwarding component is used for extracting the common characteristic information included in the response message, and after the common characteristic information is successfully matched in the session holding list item, the second virtual service sends the response message to the client after connecting with the client corresponding to the matched client identifier.
7. The two-way session holding apparatus based on 8583 protocol according to claim 6, wherein,
after the session is established between the first virtual service and the real server, no new session is established any more, and the session is reused when the real server needs to receive the 8583 protocol request message of the new client.
8. The bidirectional session holding apparatus based on 8583 protocol according to claim 6, wherein after sending 8583 protocol request message to each designated real server based on load balancing policy,
and no new connection is established between the load balancing equipment and each appointed real server, and each connection is multiplexed when each appointed real server needs to receive the 8583 protocol request message of the new client.
9. The bidirectional session holding device based on 8583 protocol as claimed in claim 6, wherein the request message acquiring component is further configured to: when receiving data traffic sent by a client via a long connection through the first virtual service and obtaining a number of 8583 protocol request messages included in the client based on the data traffic,
and splitting the received data traffic based on the byte identification length preset by the client to obtain the 8583 protocol request message.
10. The two-way session holding apparatus based on 8583 protocol according to claim 6, wherein,
the identification information of the client includes an IP address and a port number of the client.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210608610.4A CN114827239A (en) | 2022-05-31 | 2022-05-31 | Bidirectional session holding method and device based on 8583 protocol |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210608610.4A CN114827239A (en) | 2022-05-31 | 2022-05-31 | Bidirectional session holding method and device based on 8583 protocol |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114827239A true CN114827239A (en) | 2022-07-29 |
Family
ID=82519557
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210608610.4A Withdrawn CN114827239A (en) | 2022-05-31 | 2022-05-31 | Bidirectional session holding method and device based on 8583 protocol |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114827239A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115334174A (en) * | 2022-08-22 | 2022-11-11 | 卡斯柯信号有限公司 | Multichannel matching method and communication method based on Subset-037 protocol |
| CN116016535A (en) * | 2023-01-04 | 2023-04-25 | 上海弘积信息科技有限公司 | Load balancing system for controlling local application |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7277945B1 (en) * | 2001-09-12 | 2007-10-02 | Cisco Technology, Inc. | System and method for maintaining seamless session operation |
| US20080072226A1 (en) * | 2006-06-22 | 2008-03-20 | American Express Travel Related Services Co., Inc. A New York Corporation | Systems, Methods, and Computer Program Products for Transaction Based Load Balancing |
| 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 |
| US20160373520A1 (en) * | 2015-06-22 | 2016-12-22 | Vmware, Inc. | Sticky session data migration |
| CN108769257A (en) * | 2018-06-28 | 2018-11-06 | 新华三信息安全技术有限公司 | A kind of server switching method and device |
| CN112565441A (en) * | 2020-12-11 | 2021-03-26 | 北京天融信网络安全技术有限公司 | Data communication method and electronic equipment |
| CN113691589A (en) * | 2021-07-27 | 2021-11-23 | 杭州迪普科技股份有限公司 | Message transmission method, device and system |
| CN114024968A (en) * | 2021-08-20 | 2022-02-08 | 绿盟科技集团股份有限公司 | Message sending method and device based on intermediate equipment and electronic equipment |
| CN114338689A (en) * | 2021-12-30 | 2022-04-12 | 中国工商银行股份有限公司 | Session holding method, apparatus, device, medium, and program product |
-
2022
- 2022-05-31 CN CN202210608610.4A patent/CN114827239A/en not_active Withdrawn
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7277945B1 (en) * | 2001-09-12 | 2007-10-02 | Cisco Technology, Inc. | System and method for maintaining seamless session operation |
| US20080072226A1 (en) * | 2006-06-22 | 2008-03-20 | American Express Travel Related Services Co., Inc. A New York Corporation | Systems, Methods, and Computer Program Products for Transaction Based Load Balancing |
| 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 |
| US20160373520A1 (en) * | 2015-06-22 | 2016-12-22 | Vmware, Inc. | Sticky session data migration |
| CN108769257A (en) * | 2018-06-28 | 2018-11-06 | 新华三信息安全技术有限公司 | A kind of server switching method and device |
| CN112565441A (en) * | 2020-12-11 | 2021-03-26 | 北京天融信网络安全技术有限公司 | Data communication method and electronic equipment |
| CN113691589A (en) * | 2021-07-27 | 2021-11-23 | 杭州迪普科技股份有限公司 | Message transmission method, device and system |
| CN114024968A (en) * | 2021-08-20 | 2022-02-08 | 绿盟科技集团股份有限公司 | Message sending method and device based on intermediate equipment and electronic equipment |
| CN114338689A (en) * | 2021-12-30 | 2022-04-12 | 中国工商银行股份有限公司 | Session holding method, apparatus, device, medium, and program product |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115334174A (en) * | 2022-08-22 | 2022-11-11 | 卡斯柯信号有限公司 | Multichannel matching method and communication method based on Subset-037 protocol |
| CN115334174B (en) * | 2022-08-22 | 2024-02-06 | 卡斯柯信号有限公司 | Multi-channel matching method and communication method based on Subset-037 protocol |
| CN116016535A (en) * | 2023-01-04 | 2023-04-25 | 上海弘积信息科技有限公司 | Load balancing system for controlling local application |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9501345B1 (en) | Method and system for creating enriched log data | |
| JP4363847B2 (en) | Digital TV application protocol for interactive TV | |
| US9245117B2 (en) | Method and system for comparing different versions of a cloud based application in a production environment using segregated backend systems | |
| US9246819B1 (en) | System and method for performing message-based load balancing | |
| CN114827239A (en) | Bidirectional session holding method and device based on 8583 protocol | |
| EP1859597B1 (en) | Method for communication between an application and a client | |
| CN101711470A (en) | A system and method for creating a list of shared information on a peer-to-peer network | |
| US11025738B2 (en) | Systems and methods for determining a destination location for transmission of packetized data in a network system based on an application server attribute | |
| US10659443B2 (en) | Methods and apparatus for obtaining a scoped token | |
| US20210021688A1 (en) | Network access method and device for edge router | |
| CN112187491A (en) | Server management method, device and equipment | |
| CN111917825A (en) | Heterogeneous system data interaction method and device | |
| CN113055470B (en) | Service request distribution method and system | |
| CN112202744B (en) | Multi-system data communication method and device | |
| CN114239072A (en) | Block chain node management method and block chain network | |
| CN107147497B (en) | Information processing method and device | |
| CN111600929B (en) | Transmission line detection method, routing strategy generation method and proxy server | |
| CN113129008A (en) | Data processing method and device, computer readable medium and electronic equipment | |
| CN111800518A (en) | Client IP address insertion method and device | |
| US9912757B2 (en) | Correlation identity generation method for cloud environment | |
| CN113271300B (en) | Authentication system and method | |
| CN111190664A (en) | Method and system for generating page | |
| CN115361166A (en) | Access request processing method based on distributed cloud service and related equipment | |
| CN114615315A (en) | Communication method, device, equipment and storage medium for online conversation | |
| CN108366136A (en) | A kind of analysis method and device of domain name |
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 | ||
| WW01 | Invention patent application withdrawn after publication |
Application publication date: 20220729 |
|
| WW01 | Invention patent application withdrawn after publication |