WO2016180188A1

WO2016180188A1 - Distributed link establishment method, apparatus and system

Info

Publication number: WO2016180188A1
Application number: PCT/CN2016/079674
Authority: WO
Inventors: 李剑鹏
Original assignee: 中兴通讯股份有限公司
Priority date: 2015-10-09
Filing date: 2016-04-19
Publication date: 2016-11-17
Also published as: CN106572132A; CN106572132B

Abstract

A distributed link establishment method, apparatus and system. The method comprises: receiving a link establishment request packet of an initiation end; according to a pre-set dynamic distribution table, acquiring a valid link establishment request packet of a destination address and a destination port from the link establishment request packet; and, according to a pre-set load sharing table, forwarding the valid link establishment request packet to a serving node with a minimum load for link establishment. The technical solution of the present invention realizes the even distribution of link establishment request packets, thereby enabling loads of various serving nodes of a server cluster to reach a balance, increasing a response speed of the server cluster and bringing a better service experience to a user.

Description

Distribution chain building method, device and system

Technical field

This paper relates to the field of distribution chain building technology, and in particular to a distribution chain building method, device and system.

Background technique

At present, mobile and telecom core networks usually use server clusters to provide services, such as HLR (Home Location Register) and IMS (IP Multimedia Subsystem), which improve data processing efficiency through a distributed architecture. When acquiring the services provided by the HLR and the IMS, the user first needs to establish a TCP (Transmission Control Protocol) link with the HLR and the IMS to communicate with the server cluster.

In a distributed system, the server cluster plans the access users in advance according to the user's IP address and port number range, and can evenly distribute the user's service requirements to each service node in the cluster for processing. After the user initiates the link establishment request, the server cluster forwards the user's link establishment request to the corresponding service node according to the user's IP address and port number range according to the prior planning, and the service node provides the service.

However, with the continuous expansion and development of services, the service requirements of users are also increasing. When the server cluster cannot know the IP address and port number range of the user in advance, the distribution and establishment of the related technologies cannot quickly access the user request. Affects the user experience.

For example, when the user's mobile terminal requests the triggering service from the IMS, since the IP address and port of the mobile terminal are dynamically allocated, the IMS server cannot allocate the service node according to the IP address of the mobile terminal, which may cause the mobile terminal to fail. After accessing the IMS server, or after the mobile terminal successfully accesses the IMS server, the load of the service requests processed by the service nodes of the IMS server is seriously unbalanced, and some service nodes are running at full capacity, some service nodes are vacant, waste resources, and the whole is reduced. The responsiveness of the core network.

Summary of the invention

The main object of the present invention is to provide a distribution chain building method, device and system, aiming at solving In the related art, the server cluster has an unbalanced load and a slow response.

In order to achieve the above objectives, the following technical solutions are adopted:

A distribution chain building method, the distribution chain building method comprising the following steps:

Receiving a link establishment request message of the initiator;

Obtaining a legitimate link request message of the destination address and the destination port from the link request packet according to the preset dynamic sub-publishing;

According to the preset load sharing table, the legal link request message is forwarded to the service node with the least load to establish a chain.

Optionally, before the step of receiving the link establishment request message of the initiator, the method further includes:

Deploying the dynamic sub-publishing, the dynamic sub-publishing records a preset legal link establishment destination address and a destination port;

The dynamic load parameter of the service node is obtained, and the load sharing table is generated.

Optionally, after the step of forwarding the legal chain-building request packet to the service node with the least load, according to the preset load sharing table, the method further includes:

The distribution link information is stored, and a distribution session table is generated, where the distribution session table is used for distribution of subsequent messages of the initiator.

Optionally, after the step of obtaining the legal connection request packet of the destination address and the destination port from the link establishment request packet, the method further includes:

Determining, according to the distribution session table, whether the originating end has been built;

If the initiator is configured to perform the chaining, the service node that has been linked with the initiator is obtained according to the session, and the legal link request message is forwarded to the obtained The service node performs chain building;

If the initiator does not perform the chain establishment, the step of forwarding the legal chain-building request packet to the service node with the least load is performed according to the preset load sharing table.

A distribution chain building device, the distribution chain building device comprising a receiving module, a screening module and a forwarding module, wherein

The receiving module is configured to: receive a link establishment request message of the initiator end;

The filtering module is configured to: obtain a legal connection request packet of the destination address and the destination port from the link request packet according to the preset dynamic segmentation;

The forwarding module is configured to: forward the legal link request message to the service node with the least load to establish a chain according to the preset load sharing table.

Optionally, the distribution chaining device further includes a deployment module and an acquisition module, where

The deployment module is configured to: deploy the dynamic sub-publishing, and the dynamic sub-publishing records a preset legal link establishment destination address and a destination port;

The acquiring module is configured to: acquire dynamic load parameters of each service node, and generate the load sharing table.

Optionally, the distribution chaining device further includes a storage module, wherein

The storage module is configured to: store the current distribution link information, and generate a distribution session table, where the distribution session table is used for distribution of subsequent messages of the initiator.

Optionally, the distribution chaining device further includes a determination module, wherein

The determining module is configured to: determine, according to the distribution session table, whether the originating end has been built;

The forwarding module is further configured to: if the originating end performs chain building, obtain a service node that has been linked with the originating end according to the session, and obtain the legal chain-building request The packet is forwarded to the obtained service node for chain construction; if the originating end is not chained, the legal chain-building request packet is forwarded to the service with the least load according to the preset load sharing table. The node is built.

A distribution chain building system includes an initiator and a server, wherein:

The initiator is configured to: send a link request message;

The server includes an access side and a service side;

The access side includes any of the above-mentioned distribution and chain building devices;

The service side is configured to: receive the link establishment request message, and establish a link with the initiator end.

Optionally, the service side includes:

At least one service node, at least one of the service nodes is configured to: send a dynamic load parameter to the access side, receive a link establishment request message forwarded by the access side, and according to the link establishment request message The initiator is configured to receive a subsequent packet of the originating end forwarded by the access side.

The method, device and system for distributing and establishing a link according to the technical solution of the present invention receive a link request message of the originating end through the access side of the server cluster; and obtain the destination address from the link request message according to the preset dynamic sub-publishing A valid request for establishing a link with the destination port. Then, according to the preset load sharing table, the legal chain-building request packet is forwarded to the service node with the least load to establish a chain. Distribution. The technical solution of the invention realizes the uniform distribution of the link requesting packets, thereby balancing the load of the service nodes of the server cluster, avoiding waste of resources caused by load imbalance, reducing the burden of the server cluster, and accelerating the server cluster. The responsiveness enhances the overall performance of the server cluster and gives users a better business experience.

BRIEF abstract

1 is a schematic flow chart of a first embodiment of a method for distributing and constructing a chain according to the present invention;

2 is a schematic flow chart of a second embodiment of a method for distributing and constructing a chain according to the present invention;

3 is a schematic flowchart of a third embodiment of a method for distributing and constructing a chain according to the present invention;

4 is a schematic flowchart of a fourth embodiment of a method for distributing and constructing a chain according to the present invention;

5 is a schematic diagram of functional modules of a first embodiment of a distribution chain building device of the present invention;

6 is a schematic diagram of functional modules of a second embodiment of a distribution chain building device of the present invention;

7 is a schematic diagram of functional modules of a third embodiment of a distribution chain building device of the present invention;

8 is a schematic diagram of functional modules of a fourth embodiment of a distribution chain building device of the present invention;

9 is a schematic block diagram of a first embodiment of a distribution chain building system of the present invention;

10 is a schematic diagram of an application scenario for a mobile phone client to request a service from an IMS core network according to an embodiment of the present invention;

Figure 11 is a block diagram showing a second embodiment of the distribution chain building system of the present invention.

The implementation, functional features, and advantages of the present invention will be further described in conjunction with the embodiments.

Preferred embodiment of the invention

The following is an overview of the topics detailed in this document. This Summary is not intended to limit the scope of the claims.

It is understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

The main solution of the embodiment of the present invention is: receiving a link establishment request message of the originating end; and obtaining a legal link establishment request message of the destination address and the destination port from the link establishment request message according to the preset dynamic sub-publishing; According to the preset load sharing table, the legal link request message is forwarded to the service node with the least load to establish a chain.

When the address and port range of the related technology are uncertain, the server cluster may fail to access or the load of each service node is unbalanced, resulting in slow service response and affecting the user experience.

The present invention provides a solution for the server cluster access side to uniformly distribute the link establishment request to each service node without knowing the address and port information of the initiator, thereby realizing load balancing of the service nodes of the server cluster. Improve the overall response speed of the server.

Referring to FIG. 1 , a first embodiment of the method for distributing and constructing a chain of the present invention provides a method for distributing and building a chain, and the method for distributing and building a chain includes:

Step S10: Receive a link establishment request message of the initiator.

The embodiments of the present invention are mainly applied to a distributed system, and a user accesses a service cluster by establishing a chain with a server cluster. The application scenario of the present invention may be that the user terminal initiates the establishment of the link-in service cluster, and the third-party server may initiate the establishment of the link-in service cluster, or may be the terminal-building access service of the service cluster intranet, and may be flexibly applied according to actual needs.

In this embodiment, a PCT link is established between a user client and a core network, and the core network is accessed. Bright. Of course, the application scenario of the present invention is not limited to the PCT chain.

When the client needs to obtain the services of the core network, the client needs to establish a PCT link with the core network as the initiator. The access side of the core network server cluster receives the link establishment request packet, and distributes the link establishment request message to the service node for establishing a link and providing a service.

In some embodiments, the initiator sends a TCP SYN (synchronous) message to establish a link.

The TCP SYN packet carries the local address of the originating end, the local port, and the destination address and destination port of the current link. It can also carry other information, such as this service request, and can be flexibly set according to actual needs.

The initiator can use WiMax (Worldwide Interoperability for Microwave Access), WLAN (Wireless Local Area Networks), HSPDA (High Speed Downlink Packet Access), network cable, or 3G. The communication technology communicates with the core network and accesses the core network.

The access side receives the TCP SYN packet from the initiator. It should be noted that the access side may be a PC (personal computer), an interface board, or other devices with network packet forwarding capabilities, which can be flexibly set according to actual needs.

Step S20: According to the preset dynamic sub-publishing, obtain a legal chain-building request message of the destination address and the destination port from the link-building request message.

After receiving the TCP SYN packet from the initiating end, the access side resolves the TCP SYN of the initiating end, and obtains the destination address and destination port of the initiating link of the initiating end to determine whether the current TCP SYN packet is legal.

The access side preset has dynamic sub-publishing, and the dynamic sub-publishing records the destination address and destination port of the core network allowing access services.

The access side publishes the pre-deployed dynamic sub-distribution, and queries whether the destination address and destination port of the current TCP SYN packet are in dynamic sub-publishing.

If the destination address and the destination port of the TCP SYN packet are not in the dynamic sub-publishing, the TCP SYN packet is invalid and discarded.

If the destination address and the destination port of the current TCP SYN packet are in dynamic distribution, the TCP SYN packet is valid and can continue to be built.

Therefore, the access side obtains a legitimate link request message of the destination address and the destination port.

Step S30: Forward the legal link request message to the service node with the least load according to the preset load sharing table to establish a chain.

After the access side obtains a valid TCP SYN packet, the access side needs to forward the TCP SYN packet to the service node for chain establishment.

In some embodiments, the access side queries the preset load sharing table.

The load sharing table is dynamically generated, and the load status of each service node in the cluster is recorded, and the dynamic update is performed in real time.

The access side selects the service node with the lowest current load.

The access side adopts a load sharing policy, and forwards the current TCP SYN packet to the selected service node to complete the distribution of the link establishment request message, and the selected service node performs TCP negotiation with the initiator.

If the selected service node and the initiator TCP are successfully negotiated, the non-TCP packets of the subsequent service node and the initiator are directly forwarded by the access side to the current serving node.

Of course, the present invention is not limited to the construction of a user terminal and a server cluster, and can also be applied to a distribution chain within a server cluster.

For example, in the embodiment, the terminal that needs to obtain the service is used as the initiator, and the initiator sends the link request message.

Within the server cluster, each terminal has a uniquely identifiable identifier, such as a virtual IP address and port, so that the access side can identify different terminals based on the identifier.

The access side receives the link establishment request message of the initiator, and then publishes the destination IP address and port of the initiator connection request according to the preset dynamic distribution.

If the destination IP address and port of the initiator connection request are not found, the link request packet is discarded.

If the destination IP address and port of the initiator connection request are successfully found, the access side selects the service node with the least load according to the preset load sharing table, and forwards the link request message to the selected service. node.

The selected service node is chained with the initiator and provides corresponding services.

In this embodiment, the server cluster access side receives the link establishment request message of the originating end; according to the preset dynamic sub-publishing, the source link request packet of the destination address and the destination port is obtained from the link establishment request message; Then, according to the preset load sharing table, the legal chain-building request packet is forwarded to the service node with the least load to establish a chain, and the access chain-building request is uniformly distributed. In this embodiment, the uniform distribution of the request packets is implemented, so that the load of the service nodes of the server cluster is balanced, the waste of resources caused by the load imbalance is avoided, the burden of the server cluster is reduced, and the response of the server cluster is accelerated. Speed, enhances the overall performance of the server cluster, and brings a better business experience to users.

Optionally, referring to FIG. 2, the second embodiment of the method for distributing and constructing a chain of the present invention provides a method for distributing a chain. According to the embodiment shown in FIG. 1 , before the step S10, the method further includes:

Step S40: Deploying the dynamic sub-publishing, and the dynamic sub-publishing records a preset legal link establishment destination address and a destination port.

In this embodiment, the server cluster is pre-configured with a server address and port that allows access to the service.

The access side records the server address and port that the local end allows to access the service as dynamic sub-publishing, and is deployed on the access side as the address and port for providing services.

The dynamic sub-publishing may include an IP address and a port for the server cluster to provide services to the external network, and the external network user terminal obtains the service; the dynamic sub-publishing may also include the virtual IP address and port of each terminal in the server cluster, and is used in the cluster. The terminal can obtain the service; the dynamic sub-publishing can also include other identification information for identifying and finding the server providing the service, which can be flexibly set according to actual needs.

When the initiator initiates a link establishment request to the server cluster, the access side queries the dynamic sub-publishing to find the destination address and destination port carried in the link-building request packet.

If the access side finds the destination address and the destination port carried in the link establishment request packet of the originating end in the dynamic sub-publishing, the destination address and destination port carried by the originating end of the link establishment request packet are allowed by the server cluster. The incoming address and the port determine that the originating request packet is valid.

If the access destination does not find the destination address and the destination port carried in the link-building request packet of the initiator, the destination address and destination port of the link-building request packet of the initiator can be compared with the current server cluster. The address and port of the service provided do not match, so the server cluster cannot The initiator builds the chain. On the access side, the link-building request packet of the originating end is regarded as an invalid packet and is discarded.

Step S50: Obtain a dynamic load parameter of each service node, and generate the load sharing table.

In this embodiment, the access side acquires load parameters of each service node in the cluster, and generates a load sharing table.

In a cluster server, the load status of each service node changes according to the real-time processing status. Therefore, each service node actively reports the load parameters of each service node to the access side in real time, and is used by the access side to generate a load sharing table.

The load parameter of each service node includes the load status of each service node, and the load status of each service node may be the number of TCP links on each service node, or may be the CPU usage rate and memory occupancy rate of each service node. The parameter can also be other parameters that identify the load status of each service node, and can be flexibly set according to actual needs.

The load parameters of each service node also include service requests that each service node can handle.

Thereby, the access side obtains a load sharing table updated in real time. The load sharing table records the load parameters of each service node in the cluster, and is used to select the service node with the smallest load.

Therefore, when the access side distributes the link establishment request message according to the preset load sharing table, the service node capable of processing the service request of the originating end is selected; the access side selects the service node capable of processing the service request of the originating end. The service node with the least load forwards the current link request message.

In this embodiment, the access side deploys dynamic sub-publishing, and records the default legal link establishment destination address and destination port; the access side acquires dynamic load parameters of each service node, and generates a load sharing table, which is used according to each service node. The load parameters are all related to the distribution link request message. In this embodiment, the access side obtains a valid link-building request message through the dynamic sub-publishing screening, selects the service node with the least load through the load sharing table, and evenly distributes the link request message, thereby realizing the load balancing of the server cluster and reducing the load. The burden of the server cluster accelerates the response speed of the server cluster, enhances the overall performance of the server cluster, and brings a better business experience to the user.

Optionally, referring to FIG. 3, a third embodiment of the method for distributing and constructing a chain of the present invention provides a method for distributing and constructing a chain, based on the embodiment shown in FIG. 1 or FIG. 2 (the present invention is illustrated by using FIG. 1). Step After S30, it also includes:

Step S60: Store the current distribution link information, and generate a distribution session table, where the distribution session table is used for the distribution of subsequent messages of the initiator.

After the link-building request packet is forwarded to the corresponding service node, the access side stores the information of the current distribution link and generates a distribution session table.

In some embodiments, after the access side forwards the link establishment request message, the related information of the current link establishment is stored.

The access side can store the local address, the local port, the destination address, the destination port, and the destination service node identification information of the packet forwarding information as the current distribution link information to generate the distribution session table. .

After obtaining the relevant information of the current building chain, the access side generates a session segment and publishes it dynamically, and records the link establishment information in real time for the dynamic generation of the session segmentation.

The session sub-publishing can be used to forward the non-chain-building request packets of the subsequent initiator. Specifically, when the initiating end performs a session with the serving node, first, when the access side receives the non-building request message of the same originating end, the query session is published, and the service node that has been established with the initiating end is obtained.

The access side forwards the current packet to the obtained service node.

After receiving the packet, the service node performs corresponding processing to provide services to the initiator.

In this embodiment, the access side generates a distribution session table by using the current distribution link information to be used for subsequent distribution of the same originating end message. In this embodiment, when the initiating end establishes a chain with the serving node, when the access side receives the subsequent non-established link request message from the initiating end, the access side can directly forward to the corresponding service node according to the distribution session table, thereby alleviating the server cluster. The burden accelerates the response speed of the server cluster, enhances the overall performance of the server cluster, and brings a better business experience to the user.

Optionally, referring to FIG. 4, the fourth embodiment of the method for distributing and constructing a chain of the present invention provides a method for distributing and building a chain. After the step S20, the method further includes:

Step S70: Determine, according to the distribution session table, whether the originating end has been built.

After obtaining the valid link-building request packet on the access side, check whether the initiator has established a chain with the server cluster according to the dynamically generated distribution session table.

In some embodiments, the access side searches for the local address and the local port of the current initiator. Whether the sending session table records the destination service node identification information of the current originating link-building packet forwarding.

If the access side successfully finds the destination service node identifier information of the current initiator connection packet forwarding in the distribution session table, it determines that the initiator has been chained with the server cluster;

If the access side does not successfully find the destination service node identifier information of the current originating link-building packet forwarding in the distribution session table, it determines that the originating end has not been chained with the server cluster.

Thereby, the access side obtains the determination result.

Step S80: If the initiating end has been built, the service node that has been linked with the initiating end is obtained according to the session, and the legal chain-building request packet is forwarded to the The obtained service node performs chaining; if the originating end has not been chained, the process proceeds to step S30.

If the initiator and the server cluster are connected to each other, the access side publishes the service node identification information that has been chained with the current initiator, and forwards the link request packet to the obtained information according to the identifier information. The service node is constructed by the obtained service node and the initiator.

If the initiator and the server cluster have not been chained, the access side forwards the link request packet to the service node with the least load according to the preset load sharing table, and completes the distribution of the link request packet. The selected service node performs TCP negotiation with the initiator.

In this embodiment, the access side determines, according to the distribution session table, whether the initiator has been built. If the initiator performs the link establishment, the access side reports the link establishment request according to the preset load sharing table. The file is forwarded to the service node that has been chained with the initiator. If the initiator does not perform the link establishment, the access side forwards the link request packet to the load according to the preset load sharing table. The smallest service node is built. In this embodiment, the request for the establishment of the link establishment link is distributed to the service node that has been chained with the initiator, and the processing load of other service nodes in the cluster is reduced and balanced. The load of each service node in the cluster avoids the waste of resources caused by repeated packet distribution, accelerates the response speed of the server cluster, enhances the overall performance of the server cluster, and brings a better service experience to the user.

Referring to FIG. 5, a first embodiment of the distribution chain-building device of the present invention provides a distribution chain-building device, and the distribution chain-building device includes:

The receiving module 100 is configured to: receive a link establishment request message of the initiator.

In this embodiment, a PCT link is established between the user client and the core network, and the core network is accessed for example. Of course, the application scenario of the present invention is not limited to the PCT chain.

The receiving module 100 receives the TCP SYN packet of the initiator. It should be noted that the distribution chain-building device of the present invention may be located on a PC (personal computer), or on an interface board, or on other devices with network packet forwarding capabilities, and may be flexibly set according to actual needs. set.

The screening module 200 is configured to: obtain a legal link request message from the destination address and the destination port from the link establishment request message according to the preset dynamic distribution.

After the receiving module 100 receives the TCP SYN packet of the originating end, the screening module 200 parses the TCP SYN of the initiating end, and obtains the destination address and the destination port of the initiating end of the initiating end, and sets the following to determine whether the current TCP SYN packet is legal.

The screening module 200 is pre-deployed with dynamic sub-publishing, and the dynamic sub-publishing records allow the core network to be connected. Destination address and destination port of the service.

The screening module 200 queries the pre-deployed dynamic sub-publishing to query whether the destination address and the destination port of the current TCP SYN packet are in the dynamic sub-publishing.

Therefore, the screening module 200 obtains a legitimate link request message of the destination address and the destination port.

The forwarding module 300 is configured to: forward the legal link request message to the service node with the least load to establish a chain according to the preset load sharing table.

After the screening module 200 obtains a valid TCP SYN packet, the forwarding module 300 needs to forward the TCP SYN packet to the service node for establishing a link.

In some embodiments, the forwarding module 300 queries the preset load sharing table.

The forwarding module 300 selects the service node with the lowest current load.

The forwarding module 300 uses the load sharing policy to forward the current TCP SYN packet to the selected service node, and completes the distribution of the link establishment request message, and the selected service node performs TCP negotiation with the initiator.

If the selected service node and the initiator TCP are successfully negotiated, the non-TCP packets of the subsequent service node and the initiator are directly forwarded by the forwarding module 300 to the current serving node.

Of course, the distribution chaining device of the present invention is not limited to the construction of the user terminal and the server cluster, and can also be applied to the distribution and establishment of the server cluster.

Within the server cluster, each terminal has a uniquely identifiable identifier, such as a virtual IP address and port, such that the distribution chaining device of the present invention can identify different terminals based on the identification.

The receiving module 100 receives the link establishment request message of the initiator, and then the screening module 200 according to the preset The dynamic sub-publishing is to find the destination IP address and port of the initiator connection request.

If the destination IP address and the port of the initiator connection request are not successfully found, the screening module 200 discards the link establishment request packet;

If the destination IP address and the port of the initiator connection request are successfully found, the forwarding module 300 selects the service node with the least load according to the preset load sharing table, and forwards the link request message to the selected service. node.

In this embodiment, the server cluster receiving module 100 receives the link establishment request message of the originating end; the screening module 200 obtains the legal connection request of the destination address and the destination port from the link establishment request message according to the preset dynamic sub-publishing message. The forwarding module 300 forwards the legal link-building request packet to the service node with the least load according to the preset load sharing table, and implements the chain-building request to uniformly distribute the access-building request. In this embodiment, the uniform distribution of the request packets is implemented, so that the load of the service nodes of the server cluster is balanced, the waste of resources caused by the load imbalance is avoided, the burden of the server cluster is reduced, and the response of the server cluster is accelerated. Speed, enhances the overall performance of the server cluster, and brings a better business experience to users.

Optionally, referring to FIG. 6, the second embodiment of the distribution chain-building device of the present invention provides a distribution chain-building device. According to the embodiment shown in FIG. 5, the distribution chain-building device further includes:

The deployment module 400 is configured to: deploy the dynamic sub-publishing, and the dynamic sub-publishing records a preset legal link establishment destination address and a destination port.

The deployment module 400 records the server address and port that the local end allows access to the service as dynamic sub-publishing, and is deployed in the screening module 200 as the address and port for providing the service.

When the initiator initiates a link establishment request to the server cluster, the screening module 200 queries the dynamic sub-publishing to find the destination address and destination port carried in the link-building request packet.

If the filtering module 200 finds the destination address and the destination port carried in the link establishment request packet of the originating end in the dynamic sub-publishing, the destination address and the destination port carried by the originating end of the link-building request packet are allowed by the server cluster. The filtering module 200 determines that the initiator establishes the chain request message legally.

If the filtering module 200 does not find the destination address and the destination port carried in the link establishment request packet of the originating end in the dynamic sub-publishing, the destination address and the destination port of the link-building request packet of the originating end, and the current server cluster can The address and port of the service provided do not match, so the server cluster cannot be chained with the initiator. The screening module 200 treats the link establishment request message of the originating end as an illegal packet and performs discard processing.

The obtaining module 500 is configured to: acquire dynamic load parameters of each service node, and generate the load sharing table.

In this embodiment, the obtaining module 500 acquires load parameters of each service node in the cluster, and generates a load sharing table.

Thereby, the acquisition module 500 obtains a load sharing table updated in real time. The load sharing table records the load parameters of each service node in the cluster, and is used to select the service node with the smallest load.

Therefore, when the forwarding module 300 distributes the link establishment request message according to the preset load sharing table, first, the service node capable of processing the service request of the originating end is selected; and then, the forwarding module 300 is capable of processing the service request service of the originating end. In the node, the service node with the least load is selected to forward the request for establishing the link.

In this embodiment, the deployment module 400 dynamically publishes and records the preset legal link destination. The obtaining module 500 obtains the dynamic load parameters of each service node, generates a load sharing table, and sets the load request message according to the load parameters of each service node. In this embodiment, the distribution chain-building device obtains the legal chain-building request message through the dynamic sub-publishing screening, selects the service node with the least load through the load sharing table, and evenly distributes the chain-building request message, thereby realizing the load balancing of the server cluster and reducing the load. The burden of the server cluster accelerates the response speed of the server cluster, enhances the overall performance of the server cluster, and brings a better business experience to the user.

Optionally, referring to FIG. 7, the third embodiment of the distribution chain-building device of the present invention provides a distribution chain-building device, based on the embodiment shown in FIG. 5 or FIG. 6 (the invention is illustrated by using FIG. 5). The distribution chaining device also includes:

The storage module 600 is configured to: store the current distribution link information, and generate a distribution session table, where the distribution session table is used for the distribution of subsequent messages of the initiator.

After the forwarding module 300 forwards the link request message to the corresponding service node, the storage module 600 stores the information of the current link establishment and generates a distribution session table.

In some embodiments, after the forwarding module 300 forwards the link request message, the storage module 600 stores the related information of the current link.

The storage module 600 can store the local address, the local port, the destination address, the destination port, and the destination service node identifier information of the packet forwarding information as the current distribution link information, and generate a distribution session table. .

After obtaining the related information of the current link establishment, the storage module 600 generates a session sub-publishing and dynamically updates, and records the link-building information in real time for dynamic generation of the session sub-publishing.

The session sub-publishing can be used to forward the non-chain-building request packets of the subsequent initiator. Specifically, when the initiating end performs a session with the serving node, first, when the receiving module 100 receives the non-building request message of the same originating end, the forwarding module 300 queries the session sub-publishing and obtains the service node that has been established with the initiating end.

The forwarding module 300 forwards the current message to the obtained service node.

In this embodiment, the storage module 600 generates a distribution session table for storing the subsequent initiating end messages by storing the current distribution link information. This embodiment implements the initiator and service section. When the point is established, the receiving module 100 can directly forward the non-chain-building request message to the initiating end, and can be directly forwarded to the corresponding service node by the forwarding module 300 according to the distribution session table, thereby reducing the burden on the server cluster and speeding up the server. The response speed of the cluster enhances the overall performance of the server cluster and provides users with a better business experience.

Optionally, referring to FIG. 8, the fourth embodiment of the distribution chain-building device of the present invention provides a distribution chain-building device. The distribution chain-building device further includes:

The determining module 700 is configured to: determine, according to the distribution session table, whether the originating end has been built.

After the filtering module 200 obtains the valid link establishment request message, the determining module 700 searches whether the initiator has established a chain with the server cluster according to the dynamically generated distribution session table.

In some embodiments, the determining module 700 searches the distribution session table according to the local address of the current originating end and the local port to record the destination service node identification information of the current originating link-building packet forwarding.

If the determining module 700 successfully finds the destination service node identifier information of the current originating link-building packet forwarding in the distribution session table, it is determined that the initiator end has been chained with the server cluster;

If the determining module 700 does not successfully find the destination service node identifier information of the current originating link-building packet forwarding in the distribution session table, it is determined that the originating end has not been chained with the server cluster.

Thereby, the determination module 700 obtains the determination result.

The forwarding module 300 is further configured to: if the initiator performs chaining, obtain a service node that has been chained with the initiator according to the session, and establish the legal The chain request packet is forwarded to the obtained service node for chain establishment; if the initiator is not chained, the legal chain-building request packet is forwarded to the minimum load according to the preset load sharing table. The service node is chained.

If the initiator and the server cluster are connected to each other, the forwarding module 300 publishes the service node identification information that has been chained with the current initiator, and forwards the link request packet to the obtained information according to the identifier information. The service node is constructed by the obtained service node and the initiator.

If the initiator and the server cluster are not chained, the forwarding module 300 forwards the link request packet to the service node with the least load according to the preset load sharing table. The distribution of the message is sought, and the selected service node performs TCP negotiation with the originating end.

In this embodiment, the determining module 700 determines whether the originating end has been built according to the distribution session table. If the originating end performs the chain building, the accessing unit 300 of the forwarding module 300 will build the current load according to the preset load sharing table. The chain request packet is forwarded to the service node that has been chained with the initiator. If the initiator does not perform the link establishment, the forwarding module 300 will set the link request packet according to the preset load sharing table. Forward to the least loaded service node for chaining. In this embodiment, the request for the establishment of the link establishment link is distributed to the service node that has been chained with the initiator, and the processing load of other service nodes in the cluster is reduced and balanced. The load of each service node in the cluster avoids the waste of resources caused by repeated packet distribution, accelerates the response speed of the server cluster, enhances the overall performance of the server cluster, and brings a better service experience to the user.

Referring to FIG. 9, a first embodiment of the distribution chain building system of the present invention provides a distribution chain building system, where the distribution chain building system includes an initiator A and a server B, wherein:

The initiator A is configured to send a link establishment request message.

In this embodiment, the terminal that initiates the link establishment request and obtains the service to the server cluster serves as the initiator.

According to the application scenario of the present invention, the originating terminal A can be divided into an external network terminal and an intranet terminal.

The external network terminal is a terminal such as a mobile terminal or a server that obtains a server cluster service outside the server cluster. The external network terminal can pass WiMax (Worldwide Interoperability for Microwave Access), WLAN (Wireless Local Area Networks), HSPDA (High Speed Downlink Packet Access), network cable, or Communication technologies such as 3G communicate with server clusters. For example, a broadband mobile terminal may obtain a service from a core network element by using a TCP protocol through a broadband network.

The intranet terminal is a terminal or node that obtains services within the server cluster. For example, a node in the core network needs to request a directory service from the UDS, and the UDS server provides the IP address and port of the local end. When the node requests the service, Server B will establish a link on the corresponding UDS server node according to the load sharing and provide related services.

The server B includes an access side B1 and a service side B2;

The access side B1 includes a receiving module 100, a screening module 200, a forwarding module 300, a deployment module 400, an obtaining module 500, a storage module 600, and a determining module 700;

The service side B2 is configured to receive the link establishment request message and establish a chain with the initiator end A.

The server B includes an access side B1 and a service side B2. The access side B1 is configured to receive the link establishment request message of the initiator A and distribute it to the service side B2, and receive the response of the service side B2 and forward it to the initiator A.

The service side B2 is configured to receive and respond to the message distributed by the access side B1, and provide the corresponding service to the initiator A.

It should be noted that the function of receiving packets and forwarding packets on the access side may be implemented by the same physical hardware or by different physical hardware combinations.

Referring to FIG. 10, an application scenario of the present invention is used for requesting a service from a mobile phone client to an IMS core network.

In this application scenario, the originating end A includes a plurality of mobile phone clients, and the mobile phone client requests the service service of the call restriction limiting function.

The mobile phone client accesses the IMS core network through the TCP link, and the interface board serves as the access side B1 to receive the link request message of the mobile phone client and distribute it. The interface board performs session management based on SIP-I (Session Initiation Protocol). In this embodiment, a spare interface board SIP-I is included for handling an emergency situation.

The BSF/AP network element in the IMS core network serves as the service side B2 to provide trigger services for the mobile phone client.

Specifically, Client-1, Client-2, and Client-N are used to represent the mobile client of each request service.

Client-1, Client-2, and Client-N request the IMS core network to enable the call restriction function. This function needs to initiate a request to the BSF/AP network element through the HTTP protocol. Client-1, Client-2, and Client-N need to establish a TCP link with the BSF/AP network element before the HTTP request is initiated.

As an implementation manner, first, Client-1, Client-2, ..., Client-N send a TCP SYN link establishment request message to the IMS core network.

After receiving the SYN packet sent by the mobile phone client, the interface board parses the destination IP address and port in the packet, and checks whether Client-1, Client-2, Client-N is the local end according to the preset dynamic distribution. The address and port that are allowed to access.

If the address and port are not allowed to be accessed, the interface board discards the SYN packet.

If the address and the port are allowed to be accessed by the local device, the interface board searches for the SMP (Symmetric Multi Processing) in the BSF/AP network element according to the preset load sharing table to obtain the service processing nodes. SMP-1, SMP-2...SMP-N.

The interface board is the link of Client-1, Client-2, and Client-N. The service load node SMP with the smallest load is selected according to the load sharing table. It should be noted that the service processing node SMP selected by the interface board for Client-1, Client-2, Client-N, or the like may be the same or different.

The interface board forwards the SYN packets of Client-1, Client-2, and Client-N to the corresponding service processing node SMP.

The selected service processing node SMP performs a TCP three-way handshake with the initiators Client-1, Client-2, ... Client-N, respectively, and completes the TCP link establishment. The interface board records the session of each mobile client and generates a session sub-publish.

The interface board receives the call-opening request message initiated by Client-1, Client-2, and Client-N. According to the IP address and port of each mobile client, the interface is published according to the session. The client establishes the linked service processing node SMP and forwards the request message to the obtained service processing node SMP.

After receiving the call restriction request, each service processing node SMP processes the mobile client request and sends the processing result back to the mobile client.

In this embodiment, the distribution chain building system includes an initiator A and a server B. The initiator A initiates the link establishment request, and the server B uniformly distributes the link establishment request message through the access side B1, so that the service side B2 can uniformly process the link establishment request and the service request of the initiator A. This embodiment implements load balancing of the server cluster, reduces the burden on the server cluster, speeds up the response speed of the server cluster, enhances the overall performance of the server cluster, and brings a better service experience to the user.

Optionally, referring to FIG. 11, the second embodiment of the distribution chain-building system of the present invention provides a distribution chain-building system. Based on the embodiment shown in FIG. 9, the service side B2 includes:

Each of the service nodes B21, the service node B21 is configured to send the dynamic load parameter to the access side B1, and receive the link establishment request message forwarded by the access side, and according to the link establishment request message Establishing a chain with the initiator A, and receiving subsequent packets of the originating end forwarded by the access side.

In the present embodiment, the service side B2 includes each service node B21 that provides a service.

Each service node B21 updates the load parameter in real time and reports it to the access side B1 in real time for the generation of the access side B1 load sharing table.

The load parameter of each service node B21 includes the load status of each service node, and the load status of each service node may be the number of TCP links on each service node, or the CPU usage rate, memory occupancy rate, etc. of each service node. The technical parameters may also be other parameters that identify the load status of each service node, and can be flexibly set according to actual needs.

Each serving node B21 listens to the access side B1, and provides the access side B1 with service information that can be processed by each service node B21, and identification information of each service node B21, such as an IP address and a port. The access side B1 can acquire the interception information of each service node B21, and obtain the service information and the representation information that each service node B21 can process.

Therefore, the access side B1 can obtain the service node capable of processing the originating service request according to the service request of the link establishment request message and the interception information of each service node B21.

The service node with the smallest load is selected from the service nodes capable of processing the originating service request, and the message is forwarded according to the identification information of each service node B21.

After receiving the link establishment request message forwarded by the access side B1, each service node B21 establishes a link according to the link establishment request message through the access side B1 and the originating end A, and receives the subsequent message forwarded by the access side B1 and initiates the message. End A provides the corresponding service.

The application scenario of the present invention is used to obtain a service from a third-party application server to the core network, and an example is illustrated.

In this application scenario, the service side B2 is a UDS distributed database system of a core network HLR (Home Location Register) network element, the access side B1 is a UDS interface board, and the originating end A is a third-party application server. Such as AS server.

UDS provides a TCP-based directory query service for the AS server. The AS server accesses the UDS through a standard LDAP (Lightweight Directory Access Protocol) interface.

As an implementation manner, first, when the AS server acquires the directory service from the UDS, the AS server already knows the service IP address and port number of the UDS server. The AS server needs to establish a TCP link before querying the directory.

After receiving the TCP link request from the AS server, the UDS interface board firstly determines whether the TCP connection request packet of the AS server is legal according to the preset dynamic distribution.

If the TCP connection request packet of the AS server is valid, the UDS interface board queries whether the AS server has been chained with the UDS server according to the distribution session table.

If the AS server has not been built with the UDS server, the UDS interface board will query the link load of each UDS service node according to the preset load sharing table, select the service node with the least load, and forward the chain connection request of the AS server to the selection. The service node, the service node and the AS server forward the packet through the interface board to complete the TCP three-way handshake construction process.

After the link is successfully established, the AS server sends a query directory data request message to the server UDS through the TCP link. After receiving the query directory data request message, the UDS interface board queries the specific IP address and port number of the service node according to the TCP link. The service node forwards the request to the corresponding service node.

The service node receives the subsequent message of the initiator A forwarded by the access side B1, provides a directory query service, and responds the query result to the AS server.

In this embodiment, the service side B2 includes each service node B21 that provides the service, and each service node B21 sends the dynamic load parameter to the access side B1 for the generation of the access side B1 load sharing table; each service node B21 receives The link-building request packet forwarded by the access side B1 is chained with the initiator A according to the link-building request message. This embodiment implements load balancing of service nodes in the server cluster, reduces the burden on the server cluster, speeds up the response speed of the server cluster, enhances the overall performance of the server cluster, and brings a better service experience to the user.

The embodiment of the invention also discloses a computer program, comprising program instructions, when the program instruction is executed by the server, so that the server can execute any of the above-mentioned distribution and construction methods.

The embodiment of the invention also discloses a carrier carrying the computer program.

Other aspects will be apparent upon reading and understanding the drawings and detailed description.

One of ordinary skill in the art will appreciate that all or part of the steps of the above embodiments may be used. The computer program can be implemented in a computer readable storage medium, the computer program being executed on a corresponding hardware platform (such as a system, device, device, device, etc.), when executed, including One or a combination of the steps of the method embodiments.

Alternatively, all or part of the steps of the above embodiments may also be implemented by using an integrated circuit. These steps may be separately fabricated into individual integrated circuit modules, or multiple modules or steps may be fabricated into a single integrated circuit module. achieve. Thus, the invention is not limited to any specific combination of hardware and software.

The devices/function modules/functional units in the above embodiments may be implemented by a general-purpose computing device, which may be centralized on a single computing device or distributed over a network of multiple computing devices.

When each device/function module/functional unit in the above embodiment is implemented in the form of a software function module and sold or used as a stand-alone product, it can be stored in a computer readable storage medium. The above mentioned computer readable storage medium may be a read only memory, a magnetic disk or an optical disk or the like.

Variations or substitutions are readily conceivable within the scope of the present invention by those skilled in the art and are within the scope of the present invention. Therefore, the scope of the invention should be determined by the scope of the claims.

Industrial applicability

The technical solution of the invention realizes the uniform distribution of the link requesting packets, thereby balancing the load of the service nodes of the server cluster, avoiding waste of resources caused by load imbalance, reducing the burden of the server cluster, and accelerating the server cluster. The responsiveness enhances the overall performance of the server cluster and gives users a better business experience. Therefore, the present invention has strong industrial applicability.

Claims

A distribution chain building method, the distribution chain building method comprising the following steps:

Receiving a link establishment request message of the initiator;

Obtaining a legitimate link request message of the destination address and the destination port from the link request packet according to the preset dynamic sub-publishing;

According to the preset load sharing table, the legal link request message is forwarded to the service node with the least load to establish a chain.
The method of claim chaining according to claim 1, wherein before the step of receiving the link establishment request message of the initiator, the method further comprises:

Deploying the dynamic sub-publishing, the dynamic sub-publishing records a preset legal link establishment destination address and a destination port;

The dynamic load parameter of the service node is obtained, and the load sharing table is generated.
The distribution chain-building method according to claim 1 or 2, wherein after the step of forwarding the legal chain-building request message to the service node with the least load according to the preset load sharing table, The method also includes:

The distribution link information is stored, and a distribution session table is generated, where the distribution session table is used for distribution of subsequent messages of the initiator.
The method of claim 3, wherein the step of obtaining a valid link-building request message of the destination address and the destination port from the link-building request message according to the preset dynamic share publication The method also includes:

Determining, according to the distribution session table, whether the originating end has been built;

If the initiator is configured to perform the chaining, the service node that has been linked with the initiator is obtained according to the session, and the legal link request message is forwarded to the obtained The service node performs chain building;

If the initiator does not perform the chain establishment, the step of forwarding the legal chain-building request packet to the service node with the least load is performed according to the preset load sharing table.
A distribution chain building device, the distribution chain building device comprising a receiving module, a screening module and a forwarding module, wherein

The receiving module is configured to: receive a link establishment request message of the initiator end;

The filtering module is configured to: obtain a legal connection request packet of the destination address and the destination port from the link request packet according to the preset dynamic segmentation;

The forwarding module is configured to: forward the legal link request message to the service node with the least load to establish a chain according to the preset load sharing table.
The distribution chain-building device according to claim 5, wherein the distribution chain-building device further comprises a deployment module and an acquisition module, wherein

The deployment module is configured to: deploy the dynamic sub-publishing, and the dynamic sub-publishing records a preset legal link establishment destination address and a destination port;

The acquiring module is configured to: acquire dynamic load parameters of each service node, and generate the load sharing table.
The distribution chain-building device according to claim 5 or 6, wherein the distribution chain-building device further comprises a storage module, wherein

The storage module is configured to: store the current distribution link information, and generate a distribution session table, where the distribution session table is used for distribution of subsequent messages of the initiator.
The distribution chain-building device according to claim 7, wherein said distribution chain-building device further comprises a determination module, wherein

The determining module is configured to: determine, according to the distribution session table, whether the originating end has been built;

The forwarding module is further configured to: if the originating end performs chain building, obtain a service node that has been linked with the originating end according to the session, and obtain the legal chain-building request The packet is forwarded to the obtained service node for chain construction; if the originating end is not chained, the legal chain-building request packet is forwarded to the service with the least load according to the preset load sharing table. The node is built.
A distribution chain building system includes an initiator and a server, wherein:

The initiator is configured to: send a link request message;

The server includes an access side and a service side;

The access side includes the distribution chain building device according to any one of claims 5-8;

The service side is configured to: receive the link establishment request message, and establish a link with the initiator end.
The distribution chain building system of claim 9, wherein the service side comprises:

At least one service node, at least one of the service nodes is configured to: send a dynamic load parameter to the access side, receive a link establishment request message forwarded by the access side, and according to the link establishment request message The initiator is configured to receive a subsequent packet of the originating end forwarded by the access side.