WO2017215408A1

WO2017215408A1 - Session switching control method and apparatus and access point device

Info

Publication number: WO2017215408A1
Application number: PCT/CN2017/085344
Authority: WO
Inventors: 刘月清; 钱建阳; 张伟
Original assignee: 中兴通讯股份有限公司
Priority date: 2016-06-14
Filing date: 2017-05-22
Publication date: 2017-12-21
Also published as: CN107508848A

Abstract

The present application discloses a session switching control method and apparatus and an access point device. When determining that a call is established on a service node, storing session information of the call session into a caching device; hence, when session switching is required due to factors like service node fault, a target service node can be determined for each session to be switched from other service nodes except for the service node on which the sessions are established; the target service node is controlled to extract from the caching device the session information of a session to be switched; and the session to be switched is restored according to the extracted session information. Thus, the session is switched from one service node to the other service node, and subsequent messages of the session can be continuously processed after the session is switched. Therefore, when session switching is required due to factors like service node fault, the session is switched to other service nodes from the original service node to be taken over by the other service nodes, thus avoiding lost calls.

Description

Session switching control method, device and access point device

Technical field

The present application relates to the field of communications, for example, to a session switching control method, apparatus, and access point device.

Background technique

With the rapid development of carrier services, operators are increasingly demanding support, reliability, and scalability for online charging of business systems. Online charging is exchanged between the Diameter protocol and the OCS (Online Chaiging System). The user's call starts to send the initial (Initial) message to start charging. During the call, the update message is sent at a predetermined time interval. The end of the call is terminated (Terminal) The message completes the billing. This complete process is called a session of Diameter.

The related service system, as shown in FIG. 1, includes an access node 10, a service cluster 20, a pre-node 30, and an OCS 40 (Online Charging System). That is, the related service system generally adopts a pre-node 30 to complete the protocol processing, and multiple service nodes 20 complete the load sharing. At this time, the pre-node 30 also becomes a bottleneck of system performance, and the pre-node 30 cannot satisfy the continuously expanding service. The increased demand for node traffic. In order to avoid the front node 30 being called the performance bottleneck of the system, another related service system is shown in FIG. 2, the predecessor node is removed, and the protocol processing and service processing are performed at the service node 20. At this time, the access node 10 The session information can be identified, and the message of the same session is sent to the same service node. However, if one of the service nodes has a failure such as downtime or failure, the unprocessed session on the service node cannot be taken over by other service nodes, thereby causing the call. loss.

Summary of the invention

The embodiment of the present disclosure provides a session switching control method, device, and access point device, in which the session on the service node cannot be taken over by other service nodes to cause call loss when the related service node fails.

In order to solve the above problem, an embodiment of the present disclosure provides a session switching control method, including:

After the call is established on the service node, the session information of the session of the call is stored in the cache device;

When it is determined that the session is to be switched, the target service node is determined for the session to be switched, and the control target service node extracts the session information of the session to be switched from the cache device, and restores the handover session according to the extracted session information.

In order to solve the above problem, another embodiment of the present disclosure provides a session switching control apparatus, including:

a cache control module, configured to: after the call is established on the service node, control the service node to store the session information of the session of the call in the cache device;

The switching control module is configured to determine a target service node for the session to be switched when the session switching needs to be performed, and the control target service node extracts session information of the session to be switched from the cache device, and switches the session information according to the extracted session information. The session is restored.

In order to solve the above problem, another embodiment of the present disclosure provides an access point device, including: an access module and a processing module;

The access module is configured to access a call;

The processing module is configured to send the call to the service node, and after the call is established on the service node, control the service node to store session information of the session of the call in the cache device; and determine that session switching is required The target service node is determined for the session to be switched, and the control target service node extracts the session information of the session to be switched from the cache device, and restores the handover session according to the extracted session information.

In order to solve the above problems, another embodiment of the present disclosure provides an access point device including a processor and a memory, and the processor calls a module in the memory to perform the following steps:

Access call

Sending the call to the service node, when the call is established on the service node, storing the session information of the session of the call in the cache device; and determining that the session handover is required, determining the target service node for the session to be switched And controlling the target service node to extract the session information of the session to be switched from the cache device, and recover the handover session according to the extracted session information.

Embodiments of the present disclosure also provide a non-transitory computer readable storage medium storing computer executable instructions arranged to perform the above method.

One of the above technical solutions has the following beneficial effects:

The present disclosure provides a session switching control method, apparatus, and access point device. When it is determined that a call is established on a service node, the session information of the session of the call is first stored in the cache device; When a factor is required to perform session switching, the target service node may be determined for each session to be switched from other service nodes other than the service node where the session is located, and then the target service node is controlled to extract the session of the session to be switched from the cache device. Information, and the switching session is restored according to the extracted session information. This completes the process of switching the session from one service node to another, and can continue to process subsequent messages of the session after the session is switched. Therefore, the solution provided by the embodiment of the present disclosure can be implemented when the session needs to be switched, such as a service node failure, and the session is switched from the original service node to another service node to be taken over by other service nodes, thereby avoiding call loss.

BRIEF abstract

1 is a schematic structural diagram of a related service charging system;

2 is a schematic structural diagram of another related service charging system;

FIG. 3 is a schematic flowchart of a session switching control method according to Embodiment 1 of the present disclosure;

4 is a schematic structural diagram of a session switching control apparatus according to Embodiment 2 of the present disclosure;

FIG. 5 is a schematic structural diagram of an access point device according to Embodiment 3 of the present disclosure;

FIG. 6 is a schematic diagram of buffering session information in a session access process according to Embodiment 4 of the present disclosure;

FIG. 7 is a schematic diagram of session switching when a service node fails according to Embodiment 4 of the present disclosure;

FIG. 8 is a schematic diagram of handover when a single session fails according to Embodiment 4 of the present disclosure; FIG.

FIG. 9 is a schematic diagram of session switching when a service node is upgraded according to Embodiment 4 of the present disclosure;

FIG. 10 is a schematic diagram of session deletion according to Embodiment 4 of the present disclosure;

11 is a schematic structural diagram of a service system according to Embodiment 4 of the present disclosure;

FIG. 12 is a schematic structural diagram of another service system according to Embodiment 4 of the present disclosure;

FIG. 13 is a schematic structural diagram of an access point device according to an embodiment of the present disclosure.

detailed description

The technical solutions in the embodiments of the present disclosure are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present disclosure. It is obvious that the described embodiments are only a part of the embodiments of the present disclosure, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present disclosure without departing from the inventive scope are the scope of the disclosure.

The present disclosure will now be explained by way of embodiments with reference to the accompanying drawings.

Embodiment 1:

In this embodiment, the cache device is set in the system to cache the session information of the called session during the call. When the session needs to be switched, the session information can be provided to other service nodes for the other service nodes to resume the session, and the session is switched to ensure that the session can continue to be processed normally to avoid session loss. The session switching control method provided in this embodiment is shown in FIG. 3, and includes:

S301: After the call is established on the service node, the session information of the session of the call is stored in the cache device.

S302: Determine, when a session handover is required, determine a target service node for the session to be switched.

S303: The control target service node extracts session information of the session to be switched from the cache device, and restores the handover session according to the extracted session information.

It should be understood that the session in this embodiment includes, but is not limited to, an online charging session for a call. The cache device in this embodiment may be various devices that store data, including but not limited to distributed cache clusters. The session information stored in the cache device in this embodiment may include only various service-related information for performing session recovery, and may include other information according to actual application requirements. In addition, in the S301, the session information of the session is stored in the cache device in the S301.

A unique identification identifier (ie, a unique ID of the session, such as a primary key) for identifying the session is stored in the cache device with the session information of the session.

In the present embodiment, when it is detected that at least one of the following cases is detected, it is determined that it is necessary to perform Session switching:

Case 1: The message sending the session to the service node where the session is currently located fails to be sent; this case involves switching when a single session fails to execute. The message for the session sent here may be a message to maintain the session or end the session.

Case 2: The service node carrying the session is faulty; for example, if the service node is down or fails due to a failure, the session currently carried on the service node (these sessions are generally incomplete sessions) need to be switched to other services. Continue processing on the node to avoid causing call loss.

Case 3: The service node hosting the session needs to be upgraded. In this embodiment, when a service node needs to be upgraded, in order to avoid affecting the session currently carried on the service node, each session on the service node to be upgraded may be switched to another service node in advance. This processing mode can be used to gradually upgrade each service node in the service cluster.

Case 2 and Case 3 above involve batch upgrade of all sessions that are currently not completed on a service node. At this point, the incomplete session on a service node may be 0 or 1 or more. In this embodiment, when determining the target service node for the session to be switched, the session to be switched may be determined from the other service nodes (that is, other service nodes except the original session bearer service node to be switched) according to the load balancing principle. Target business node.

In this embodiment, after determining that the session switching needs to be performed, after selecting the target service node for each session to be switched, the control target service node extracts the session information of the session to be switched from the cache device, including:

And sending, to each of the to-be-switched sessions, a session switching request to the corresponding target service node, where the sent session switching request includes a unique identification identifier for indicating that the target service node extracts session information of the to-be-switched session from the cache device. After receiving the session switching request, each target service node may extract the session information of the session to be switched from the cache device according to the unique identification identifier in the session switching request, and perform session recovery processing according to the session information. Each target service node may extract corresponding session information (including various service information for performing session service recovery) according to the unique identification identifier to the buffer corresponding to the cache device, and then store the corresponding data area in the local area to complete the session. restore.

In this embodiment, after controlling a session to be switched from the original service node to another service node, the original service node is also controlled to delete the session information stored locally in the session. For the foregoing case 1 and case 3, the service node may be directly sent to notify the service node to delete the locally stored message of the session that has been switched. For the second case, after detecting that the service node recovers from the fault, the service node is sent a message to notify it to delete the session information of each session stored locally before.

In this embodiment, after detecting the end of a call, the service node where the session controlling the call is currently located deletes the session information of the session in the local and cache devices.

In the solution provided by this embodiment, a cache device is set in the system to cache session information. When the session needs to be switched, the cache device provides session information for other service nodes to restore the session to other service nodes, completes the session switch, and ensures that the session can continue to be processed normally to avoid session loss. It should be understood that the solution provided by the present embodiment is applicable to an online charging system for calling, such as the Diameter protocol applicable to online charging, and the related protocol for other sessions.

The control process shown in FIG. 3 in this embodiment may be completed by a specially configured session switching control device, or may be directly performed by a node in the related service system, for example, directly through an access node. The following examples are given in two cases.

Embodiment 2:

Referring to FIG. 4, the embodiment provides a session switching control apparatus, which can be implemented by various servers or other control terminals, including:

The cache control module 41 is configured to, after the call is established on the service node, control the service node to store the session information of the session of the call in the cache device.

It should be understood that the session in this embodiment includes, but is not limited to, an online charging session for a call. The cache device in this embodiment may be various devices that store data. The session information stored in the cache device in the embodiment includes at least information for performing session recovery. In addition, in order to facilitate accurate searching during session recovery, the cache control module 41 stores the session information of the session in the cache device, including: a unique identification identifier (ie, a unique ID of the session) for identifying the session and session information of the session. The binding is stored in the cache device.

The switching control module 42 is configured to determine a target service node for the session to be switched when the session switching needs to be performed, and control the target service node to extract the session information of the session to be switched from the cache device, and treat the session information according to the extracted session information. Switch sessions to recover.

The session switching control apparatus in this embodiment may be a control device that performs session switching independently of the access node, and may detect a message interaction between the access node and the service node. Thereby detecting whether the call is established or not, it may determine that the call setup is completed after detecting that the service node feeds back the response of the call initial message to the access node. The session switching control device can also determine whether a session fails or whether a service node is faulty by detecting a message interaction between the access node and the service node. It should be understood that the session switching control apparatus in this embodiment may also directly monitor the status of the service node to determine whether it is faulty.

In this embodiment, when the handover control module 42 detects that at least one of the following occurs, it is determined that a session handover is required:

Case 1: The message sending the session to the service node where the session is currently located fails to be sent; this case involves switching when a single session fails to execute.

Case 3: The service node hosting the session needs to be upgraded. In this embodiment, when a service node needs to be upgraded, the handover control module 42 may switch the sessions on the service node to be upgraded to other service nodes in advance in order to avoid the impact on the currently carried session. This processing mode can be used to gradually upgrade each service node in the service cluster.

It should be understood that the handover control module 42 performs batch handover of all sessions currently not completed on the service node for the above case 2 and case 3. At this point, the incomplete session on a service node may be 0 or 1 or more. In the embodiment, when the target control node is determined for the sessions to be switched, the handover control module 42 may wait for other service nodes (that is, other service nodes except the original session bearer service node to be switched) according to the load balancing principle. The switched session determines the target service node.

It should be understood that, when the session switching control apparatus in this embodiment can pass various servers or other control terminals, the above functions of the cache control module 41 and the switching control module 42 can be processed by the processor or the terminal. Implemented.

In this embodiment, after the handover control module 42 determines that the target service node is selected for each session to be switched, the control target service node extracts the session information of the session to be switched from the cache device, including:

The handover control module 42 sends a session handover request to the corresponding target service node for each to-be-switched session, and the sent session handover request includes a unique identification identifier for indicating that the target service node extracts session information of the to-be-switched session from the cache device. After receiving the session switching request, each target service node may extract the session information of the session to be switched from the cache device according to the unique identification identifier in the session switching request, and perform session recovery processing according to the session information.

In this embodiment, after the handover control module 42 controls a session to be switched from the original service node to another service node, the original service node is also controlled to delete the session information stored locally in the session. For the foregoing case 1 and case 3, the handover control module 42 may directly send a message to the service node to delete the locally stored message of the session in which the handover process is performed. For the foregoing case 2, the handover control module 42 may send a message to the service node to detect the session information of each session stored locally before deleting the fault after the service node is recovered from the fault.

In this embodiment, after detecting that a call is over, the handover control module 42 further includes the service node where the session in which the call is currently located deletes the session information of the session in the local and cache devices.

The session switching control apparatus provided in this embodiment controls the cache device to perform session information caching during the call process. When the session needs to be switched, the control cache device provides session information for other service nodes to restore the session to other service nodes, completes the session switch, and ensures that the session can continue to be processed normally to avoid session loss.

Embodiment 3:

Referring to FIG. 5, the embodiment further provides an access point device (hereinafter referred to as an access point), an access module 51 and a processing module 52;

The access module 51 is configured to access the call.

The access module 51 in this embodiment receives the call initial message and sends the received call initial message to the process 52. The access module 51 in this embodiment may only perform the access proxy function when the access protocol is relatively complex, and the access protocol processing portion may be deployed on the service node to complete the processing of the access protocol by the service node. Of course, the access module 51 in this embodiment may directly perform the processing of the access protocol when the capability permits.

It should be understood that the access in this embodiment may be diverse, for example, applied to a third-party deduction service, which may be an http protocol access; and applied to a traditional voice service, which may be a sip protocol access; It is used for Diameter Proxy, which can be accessed by Diameter protocol; it can be applied to the internal message flow of the system, or it can be customized internal protocol access. At this time, the access module 51 completes the function of protocol access.

The processing module 52, in this embodiment, may be a distribution processing module configured to send the call to the service node, and after detecting that the call is established on the service node, control the service node to the session of the call. The session information is stored in the cache device; and when it is determined that the session switch needs to be performed, the target service node is determined for the session to be switched, and the control target service node extracts the session information of the session to be switched from the cache device, and according to the extracted session information. Respond to the switching session.

The processing module 52 sends the call to the service node, for example, sends the received call initial message to the corresponding service node. After receiving the response of the call initial message fed back by the service node, the processing module 52 determines that the call has been established at the service node.

However, it is understood that the session in this embodiment includes, but is not limited to, an online charging session for a call. The cache device in this embodiment may be various devices that store data. The session information stored in the cache device in the embodiment includes at least information for performing session recovery. In addition, in order to facilitate the accurate search in the session recovery, the processing module 52 controls the service node to store the session information of the session in the cache device, including: sending a corresponding notification message to the service node, where the notification message includes the unique identification identifier of the session (also That is, the unique ID of the session). After receiving the notification message, the service node binds the unique identification identifier (ie, the unique ID of the session) used to identify the session to the cache device in the session information of the session. The cache device can be a variety of storage devices, such as a distributed cache cluster.

When the processing module 52 determines the target service node for the session to be switched, the target service node may be determined from the other service nodes except the service node where each session is located for each session to be switched through the load balancing principle.

In this embodiment, when the processing module 52 detects that at least one of the following occurs, it is determined that a session switch needs to be performed:

Case 3: The service node hosting the session needs to be upgraded. In this embodiment, when a service node needs to be upgraded, the processing module 52 may switch the sessions on the service node to be upgraded to other service nodes in advance in order to avoid the impact on the currently-held session of the service node. This processing mode can be used to gradually upgrade each service node in the service cluster.

It should be understood that the processing module 52 performs batch switching on all the sessions currently not completed on the service node for the above case 2 and case 3.

It should be understood that the above functions of the access module 51 and the processing module 52 in this embodiment may be implemented by a processor or a controller of the access point device. It can be implemented by a processor, and the processor can call the module in the access point device memory to complete the foregoing functions of the access module 51 and the processing module 52 in this embodiment.

In this embodiment, the processing module 52, after determining that the session switching needs to be performed, selects the target service node for each session to be switched, and then the control target service node extracts the session information of the session to be switched from the cache device, including:

The processing module 52 sends a session switching request to the corresponding target service node for each to-be-switched session, where the sent session switching request includes a unique identification identifier for indicating that the target service node extracts the session information of the to-be-switched session from the cache device. After receiving the session switching request, each target service node may extract the session information of the session to be switched from the cache device according to the unique identification identifier in the session switching request, and perform session recovery processing according to the session information.

In this embodiment, after the processing module 52 controls a session to be switched from the original service node to another service node, the original service node is also controlled to delete the session information stored locally in the session. For the first case and the third case, the processing module 52 can directly send a message to the service node to delete the locally stored message of the session that has been switched. For the foregoing case 2, the processing module 52 may send a message to the service node to detect the session information of each session stored locally before deleting the fault after the service node is recovered from the fault.

In this embodiment, the processing module 52, when detecting the end of a call, further includes the service node where the session in which the call is currently located deletes the session information of the session in the local and cache devices.

In this embodiment, the access point device controls the cache device to perform session information caching during the call process. When the session needs to be switched, the control cache device provides session information for other service nodes for other service nodes to resume the session, completes the session switch, and ensures that the session can continue to be normal. Reason, to avoid causing session loss.

Embodiment 4:

For a better understanding of the present disclosure, the present disclosure exemplifies the present disclosure by taking a cache device as a distributed cache cluster and an application scenario as an online charging scenario of a call. The service system in this embodiment includes an access node, a service cluster including multiple service nodes, a cache cluster connected to the service cluster, and an OCS (Online Charging System) connected to each service node. The access node includes a call access module (that is, an access module), a distribution processing module (that is, a processing module), and the service node includes a service processing module and a protocol processing module. Based on the above application scenario, the session information is cached in this embodiment, and the session switching process in each case is as follows.

Referring to FIG. 6, the process of caching session information during session access includes:

S601: The distribution processing module of the access node receives the initial call message sent by the call access module, and sends the initial call message to the service processing module of the service node.

S602: The service processing module of the service node completes the service logic processing, generates a charging start message, and sends the message to the protocol processing module.

S603: The protocol processing module of the service node is assembled into a CCR Initial message and sent to the OCS.

S604: The OCS returns a response, and the protocol processing module of the service node forwards the response to the service processing module, and saves the session information of the session in the local memory.

S605: The service processing module logically processes the call, and forwards the call response (that is, the response of the call initial message) to the distribution processing module of the access node.

S606: The distribution processing module of the access node receives the response of the call initial message, determines that the call has been established, and sends a notification message (including the unique identification identifier of the session, which can make the session number) to the service node.

S607: The service node protocol processing module receives the notification message, and stores the session information of the session and the unique identification identifier of the session into the distributed cache cluster.

Referring to FIG. 7, the process of performing batch session switching when detecting a fault of a service node (hereinafter referred to as service node A) includes the following steps:

S701: The distribution processing module of the access node detects that the service node A is down or not.

S702: The distribution processing module of the access node switches the presence session belonging to the service node A to the His service node evenly sends a session switch message carrying the unique identification of the original session.

S703: The protocol processing module of each of the other service nodes retrieves the corresponding session information from the distributed cache cluster, and performs session recovery locally to implement session switching.

S704: The protocol processing module of each of the other service nodes may continue to process subsequent messages of the session originally belonging to the service node A.

S705: The distribution processing module of the access node detects that the service node A recovers, and notifies the protocol processing module of the service node A to delete the session cache in the original memory.

As shown in Figure 8, when a session fails to be sent (still with service node A as an example), the process of switching the session is as follows:

S801: The distribution processing module of the access node prepares to distribute the message, and the message for sending the session fails to the service node A.

S802: The access node distribution processing module sends the session handover message to one of the other service nodes (for example, the service node B), and carries the unique identification identifier of the session.

S803: The protocol processing module of the service node B retrieves session information of the session from the distributed cache to perform session recovery, and implements session switching.

S804: The access node distribution processing module sends a message subsequent to the session to the service node B.

S805: The service node B protocol processing module can continue to process the subsequent session.

S806: The access node distribution processing module notifies the protocol processing module of the service node A to delete the session cache in the original memory.

Referring to FIG. 9 , when the service node is upgraded in this embodiment, the current service node A is upgraded as an example, and the session switching process includes:

S901: The service node A is ready to be upgraded, and the distribution module of the access node updates online service node information that can be used for distribution.

S902: The distribution module of the access node notifies the protocol processing module of the service node A to delete the local session cache.

S903: The distribution processing module of the access node switches the presence session of the service node A, and uniformly sends the session switching message to the protocol processing module of the other node, and carries the unique identification identifier of each session.

S904: The protocol processing module of each of the other service nodes extracts session information from the distributed cache cluster to perform session recovery, and implements handover.

S905: The protocol processing module of each of the other service nodes may continue to process subsequent sessions that originally belong to the service node A.

S906: The other service nodes are sequentially upgraded according to the foregoing method.

S907: After all the service nodes are upgraded, the distribution module of the access node re-updates the service node information.

In this embodiment, when a call ends, the process of deleting the session for the call is as shown in FIG. 10, and includes:

S1001: The distribution processing module of the access node receives the call end message, and sends the message to the service node where the session of the call is located.

S1002: The service processing module of the service node generates an accounting end message, and sends the message to the protocol processing module.

S1003: The protocol processing module of the service node is assembled into a CCR Terminal message and sent to the OCS.

S1004: The OCS returns a response, and the protocol processing module of the service node deletes the session in the in-memory and the distributed cache, and then forwards the response to the service processing module.

S1005: The service processing module of the service node logically processes and forwards the call termination response to the access node.

For a better understanding of the present disclosure, the present disclosure is exemplified below by the access access module of the access node performing the access protocol (taking the Diameter protocol as an example) and only as an access proxy.

The system structure diagram of the processing of the access protocol by the call access module is shown in FIG. 11, and includes: an access node 1, a service cluster 2, a distributed cache cluster 4 connected to the service cluster, and an online charging system OCS3. The access node 1 comprises a call access module 1A, which can be configured to process Diameter server messages. The process of session switching based on the system to implement Diameter Client load balancing is as follows:

The access node receives the caller's access message, and the call access module 1A completes the call access. The distribution processing module 1B performs load sharing on multiple service nodes and sends it to a certain service node (the first service section in the figure). point). After receiving the message of the call access, the service processing module 2A of the service node initiates the charging start CCR Initial, and the protocol processing module 2B of the service node encapsulates the standard Diameter message and sends it to the OCS.

The OCS returns a response, and the protocol processing module 2B saves the session information in the local memory, and forwards the response to the service processing module 2A. The service processing module 2A accesses the called party, and returns the response of the called party to the distribution processing module 1B. The distribution processing module 1B determines that the session has been established, and uses the unique session id to notify the protocol processing module 2B to save the session. After receiving the notification, the protocol processing module 2B stores the session information in the distributed cache cluster 4.

The distribution processing module 1B maintains a heartbeat between the service node and detects whether the service node is operating normally.

During the call, the service node is down or not. If the distribution processing module 1B has detected it, the session shown in Figure 7 is used for session switching. If it has not been detected, but a certain session fails to be sent, the method is as shown in Figure 8. The method shown is for session switching. After the session is switched, the subsequent sessions can continue to be processed on other service nodes.

After the call ends, the distribution processing module 1B of the access node 1 sends the subsequent session to the switched service node, and the service processing module 2A of the service node generates an accounting end message CCR Teminal and forwards it to the protocol processing module 2B for protocol processing. Module 2B is encapsulated as a standard Diameter message and sent to the OCS.

The OCS returns a response, and the protocol processing module 2B deletes the session information saved in the local memory and the session information in the distributed cache, and forwards the response to the service processing module. The service processing module 2A notifies the called party to hang up, and returns the called response to the call. Enter node 1.

Referring to FIG. 12, a schematic diagram of a system structure in which the call access module is only used as an access proxy includes: an access node 1, a service cluster 2, a distributed cache cluster 4 connected to the service cluster, and an online charging system OCS3. The access node 1 includes a call access module 1A, which serves only as an access proxy, hereinafter referred to as an access proxy module. The service cluster 2 includes a first protocol processing module 2C configured to process Diameter server messages, and a second protocol processing module 2D configured to process Diameter client messages. The process of session switching based on the system to implement Diameter Client load balancing is as follows:

The Diameter Client initiates a CCR Initial message, and the access proxy module of the access node completes the Diameter protocol access, and the distribution processing module 1B of the access node implements load sharing on multiple service nodes and sends it to a certain service node (as shown in the figure) Business nodes 1). After receiving the CCR Initial message, the first protocol processing module 2C of the service node performs protocol parsing, and converts the internal message to the service processing module 2A. The service processing module 2A performs the business logic processing and forwards the internal message to the second protocol processing module 2D. The second protocol processing module 2D is encapsulated into a standard Diameter message and sent to the OCS.

The OCS returns a response, the second protocol processing module 2D saves the session information in the local memory, and forwards the response to the service processing module 2A, and the service processing module 2A forwards the message to the first protocol processing module 2C, where the first protocol processing module 2C is in the local memory. The session information is saved and encapsulated and returned to the distribution processing module 1B. At this time, the distribution processing module 1B determines that the session has been established, and notifies the first protocol processing module 2C and the second protocol processing module 2D in the distributed cache cluster 4 using the unique session id. Save the session. The first protocol processing module 2C and the second protocol processing module 2D store the session information in the distributed cache cluster 4.

In the charging process, if the service node is down or not, if the distribution processing module 1B has detected, the session switching is performed in the manner shown in FIG. 7; if it is not detected, but a single session transmission failure is detected, FIG. 8 is adopted. The method shown is for session switching.

After the charging ends, the access node 1 notifies the distribution processing module 1B, and the distribution processing module 1B sends the subsequent session to the other service node, and after the first protocol processing module 2C and the service processing module 2A of the service node process, the second protocol The processing module 2D is encapsulated into a standard Diameter message and sent to the OCS.

After the OCS returns a response, the response message goes from the second protocol processing module 2D to the service processing module 2A to the first protocol processing module 2C to the distribution processing module 1B to the access proxy module and then to the Diameter Client. After receiving the response, the first protocol processing module 2C and the second protocol processing module 2D respectively delete the session information saved in the local memory and the session information in the distributed cache.

The process of session switching when the service system is smoothly upgraded in this embodiment is as follows:

The planning first upgrades the first service node, and the distribution processing module of the access node updates other normal running service nodes online as the load sharing node.

The service processing part of the first service node is partially upgraded, and the incomplete session originally processed at the first service node is taken over by other service nodes through FIG.

After the first service node 1 is successfully upgraded, the other service nodes are upgraded according to the above.

After all the service nodes are successfully upgraded, the distribution processing module of the access node updates all the service nodes online to the normal state.

Embodiments of the present disclosure also provide a non-transitory computer readable storage medium storing a computer Execution of instructions, the computer executable instructions being arranged to perform the method of any of the above embodiments.

The embodiment of the present disclosure further provides a schematic structural diagram of an access point device. Referring to FIG. 13, the electronic device includes:

At least one processor 130, which is exemplified by a processor 130 in FIG. 13; and a memory 131, may further include a communication interface 132 and a bus 133. The processor 130, the communication interface 132, and the memory 131 can complete communication with each other through the bus 133. Communication interface 132 can be used for information transfer. The processor 130 can invoke logic instructions in the memory 131 to perform the methods of the above-described embodiments.

In addition, the logic instructions in the memory 131 described above may be implemented in the form of a software functional unit and sold or used as a stand-alone product, and may be stored in a computer readable storage medium.

The memory 131 is a computer readable storage medium, and can be used to store a software program, a computer executable program, a program instruction/module corresponding to the method in the embodiment of the present disclosure. The processor 130 executes the function application and the data processing by executing the software program, the instruction and the module stored in the memory 131, that is, the session switching control method in the above method embodiment.

The memory 131 may include a storage program area and an storage data area, wherein the storage program area may store an operating system, an application required for at least one function; the storage data area may store data created according to usage of the terminal device, and the like. Further, the memory 131 may include a high speed random access memory, and may also include a nonvolatile memory.

The technical solution of the embodiments of the present disclosure may be embodied in the form of a software product stored in a storage medium, including one or more instructions for causing a computer device (which may be a personal computer, a server, or a network) The device or the like) performs all or part of the steps of the method described in the embodiments of the present disclosure. The foregoing storage medium may be a non-transitory storage medium, including: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and the like. a medium that can store program code, or it can be temporary State storage medium.

When the session switching control scheme of the present disclosure is applied to an online charging system, compared with related technologies, the effect of online charging load balancing is achieved, the performance of the online charging service system is improved, and the business volume can be expanded and expanded in the future. If the service node is increased, the service node is reduced, and the service node is also reduced. The load balancing can reasonably utilize resources to realize the elastic expansion and contraction of the service system. In addition, in general, the service processing part of the service system needs to be upgraded frequently to meet some personalized requirements of the user, and the protocol processing part is relatively stable. After the session switching function is used, the service processing can be smoothly upgraded and the impact on the online service can be reduced. To facilitate the maintenance of business systems.

The above is only the embodiment of the present disclosure, and is not intended to limit the present disclosure in any way. Any simple modification, equivalent change, combination or modification of the above embodiment according to the technical essence of the present disclosure still belongs to the present disclosure. The scope of protection of the technical solution.

Industrial applicability

The session switching control method, device, and access point device provided by the present application can be used to switch the session from the original service node to another service node and be taken over by other service nodes when the service node fails to cause the session to be switched. Causing call loss.

Claims

A session switching control method includes:

After the call is established on the service node, the session information of the session of the call is stored in the cache device;

When it is determined that the session is to be switched, the target service node is determined for the session to be switched, and the control target service node extracts the session information of the session to be switched from the cache device, and restores the handover session according to the extracted session information.
The method of claim 1, wherein when at least one of the following occurs, it is determined that a session switch is required:

The message sending the session to the service node where the session is currently located fails to be sent;

The service node carrying the session is faulty;

The service node hosting the session needs to be upgraded.
The method of claim 1, wherein storing the session information of the session in a cache device comprises:

Binding the unique identification identifier for identifying the session to the session information of the session is stored in the cache device.
The method of claim 1 wherein determining the target service node for the session to be handed over comprises:

The target service node is determined from the other service nodes for the session to be switched according to the load balancing principle.
The method of claim 3, wherein the controlling the target service node to extract the session information of the session to be switched from the cache device comprises:

Sending a session switching request to the corresponding target service node for each to-be-switched session, the session The handover request includes: a unique identification identifier used to indicate that the target service node extracts session information of the session to be switched from the cache device.
The method of any of claims 1-5, further comprising: after the call ends, the service node in which the session controlling the call is currently located deletes the session information of the session in the cache device.
The method of any of claims 1-5, wherein the session is an online charging session for a call.
A session switching control device includes:

a cache control module, configured to: after the call is established on the service node, control the service node to store the session information of the session of the call in the cache device;

The switching control module is configured to determine a target service node for the session to be switched when the session switching needs to be performed, and the control target service node extracts session information of the session to be switched from the cache device, and switches the session information according to the extracted session information. The session is restored.
The apparatus of claim 8, wherein the handover control module determines that a session handover is required when at least one of the following occurs:

The message sending the session to the service node where the session is currently located fails to be sent;

The service node carrying the session is faulty;

The service node hosting the session needs to be upgraded.
An access point device includes: an access module and a processing module;

The access module is configured to access a call;

The processing module is configured to send the call to the service node, and after the call is established on the service node, control the service node to store session information of the session of the call in the cache device; and determine that session switching is required Determine the target service node for the session to be switched, and control the target service. The node extracts the session information of the session to be switched from the cache device, and restores the handover session according to the extracted session information.
The device of claim 10, wherein the handover processing module determines that a session switch is required when at least one of the following occurs:

The message sending the session to the service node where the session is currently located fails to be sent;

The service node carrying the session is faulty;

The service node hosting the session needs to be upgraded.
A non-transitory computer readable storage medium storing computer executable instructions arranged to perform the method of any of claims 1-7.