WO2017036238A1 - 一种业务节点的调整方法、装置及设备 - Google Patents

一种业务节点的调整方法、装置及设备 Download PDF

Info

Publication number
WO2017036238A1
WO2017036238A1 PCT/CN2016/086926 CN2016086926W WO2017036238A1 WO 2017036238 A1 WO2017036238 A1 WO 2017036238A1 CN 2016086926 W CN2016086926 W CN 2016086926W WO 2017036238 A1 WO2017036238 A1 WO 2017036238A1
Authority
WO
WIPO (PCT)
Prior art keywords
service node
message
service
changed
node
Prior art date
Application number
PCT/CN2016/086926
Other languages
English (en)
French (fr)
Inventor
耿长剑
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2017036238A1 publication Critical patent/WO2017036238A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements
    • H04W4/14—Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]

Definitions

  • This document relates to, but is not limited to, the field of communications, and relates to a method, device and device for adjusting a service node.
  • the SMS service has an obvious feature, that is, the traffic volume during the holiday is much larger than usual.
  • the traditional short message center should consider the maximum traffic of the service when starting the deployment, and configure the corresponding hardware devices according to the maximum traffic of the service. This will result in a large amount of hardware resources and a waste of resources in the case of normal traffic.
  • the traditional short message center when the business volume of the subsequent office needs to be expanded, it is necessary to purchase new hardware and plan to deploy a new service node, which has a long engineering time.
  • the traditional short message service in the CS (Circuit Switching) domain can only call a message to the same destination user at the same time.
  • each message is fixed in the called user.
  • the home thread of the home node is queued for delivery.
  • the number of internal threads and the thread number of the SMS center node are fixed, so the attribution calculation can be performed by an algorithm, and the number of node numbers and the node number are not fixed, and the policy of the node can only be assigned by the page configuration number. Adding and deleting nodes, the policy of the number of the home node must be adjusted. This will cause the node that has not delivered the successful message cache before the dynamic scaling. It may not be the home node. Also, the short message is timed. If the order submitted by the user is A, B, but the order received by the user is B, A, the whole meaning may be the opposite.
  • the embodiment of the invention provides a method, a device and a device for adjusting a service node, which ensure that adding a service node or deleting a service node number does not affect the processing of the message, and improves the accuracy of message transmission.
  • the change indication request includes indication information that carries a cache message attribution of the service node to be changed, where the service node to be changed includes an added service node or a reduced service node;
  • the parsing, according to the change indication request, the attribution of the cached message of the service node to be changed in the indication information including:
  • the sending according to the attribution of the cached message of the to-be-changed service node, a cache message that is not the service node to be changed, to the home node, including:
  • first cache message of the first service node belongs to the first service node cache message indicated in the home of the first service node, continue scanning for the remaining cache message of the first cache message;
  • first cache message of the first service node does not belong to the cache message of the first service node indicated by the first service node, forwarding the first cache message to the home node, and continuing to scan The remaining cached messages of the first cached message are removed.
  • the method further includes: until it is determined that all cached messages of the first service node are completed.
  • the parsing, according to the change indication request, the attribution of the cached message of the service node to be changed in the indication information including:
  • the attribution is to allocate the cache message of the second service node to all current remaining service nodes according to the pre-configured attribution, where the current All remaining service nodes are nodes of all service nodes except the second service node.
  • the sending according to the attribution of the cached message of the service node to be changed, the cached message that is not the service node to be changed, to the home node, including:
  • the embodiment of the invention further provides a method for adjusting a service node, including:
  • the cache message is sorted according to a time stamp, and the time stamp is a time when the same called number delivery message arrives at the short message center;
  • the method further includes: after the obtaining the first change request of the service node to be changed, generating a rejection response to the first change when the to-be-changed service node performs the last change indication request is not ended.
  • the requested message after the obtaining the first change request of the service node to be changed, generating a rejection response to the first change when the to-be-changed service node performs the last change indication request is not ended. The requested message.
  • the change information of all service node attributions is obtained for the first change request, including:
  • the to-be-changed service node When the to-be-changed service node performs the last change indication request, when the service node to be changed for the first change request is the added first service node, generate a notification message for executing the first change request,
  • the notification message carries an increased node number of the first service node and an increased Internet Protocol IP address used by the first service node.
  • the change information of all the service node attributions is obtained for the first change request, including:
  • the to-be-changed service node executes the last change indication request
  • when the to-be-changed service node for the first change request is the reduced second service node, generating a notification message for executing the first change request,
  • the notification message carries a reduced node number of the second service node
  • An embodiment of the present invention further provides an apparatus for adjusting a service node, including:
  • a first obtaining module configured to acquire a change indication request for changing a service node, where
  • the change indication request includes indication information that carries a cached message attribution of the service node to be changed, where the service node to be changed includes an added service node or a reduced service node;
  • the parsing module is configured to parse the attribution of the cache message of the to-be-changed service node in the indication information according to the change indication request;
  • a second obtaining module configured to acquire a cache message of the service node to be changed
  • the first processing module is configured to send, according to the attribution of the cached message of the service node to be changed, a cache message that is not in the service node to be changed, to the home node, where the cache message is sorted according to a time stamp.
  • the time stamp is the time when the same called number delivers the message to the SMS center.
  • An embodiment of the present invention further provides an apparatus for adjusting a service node, including:
  • a third obtaining module configured to acquire a first change request for changing a service node to be changed, where the to-be-changed service node includes an added service node or a reduced service node;
  • a fourth obtaining module configured to: when the to-be-changed service node executes the last change indication request, obtain, for the first change request, change information of all service node attributions, where the last change indication request includes carrying The indication information of the cached message attribution of the service node to be changed, the cached message is sorted according to a time stamp, and the time stamp is a time when the same called number delivery message arrives at the short message center;
  • the second processing module is configured to generate and send a change indication request according to the change information of all service nodes, wherein the change indication request includes indication information that carries the cache message attribution of the service node to be changed.
  • the embodiment of the present invention further provides a service side device, including an adjustment device of the service node as described above.
  • the embodiment of the invention further provides a proxy device, comprising the adjustment device of the service node as described above.
  • the dynamic expansion and contraction of the service node is implemented by acquiring the change indication request of the service node, and the cache message not belonging to the service node to be changed is sent to the home by the cache message of the service node to be changed.
  • the node also sorts the sent cache messages according to the timing, thereby ensuring the accuracy of the message transmission, so that the adaptive SMS service traffic changes, It is ensured that the addition of the service node or the deletion of the service node number does not affect the processing of the message, and only needs to increase the service node to transmit the message according to the thread; when the service is started, the maximum traffic of the service does not need to be considered, and only the minimum number of nodes for configuring the service operation needs to be installed.
  • the embodiment of the present invention further provides a computer readable storage medium, where the computer readable storage medium stores computer executable instructions, and when the computer executable instructions are executed, implements a method for adjusting a service node.
  • FIG. 1 is a schematic diagram of steps of a method for adjusting a service node according to Embodiment 1 of the present invention
  • FIG. 2 is a flow chart of adding a service node according to Embodiment 4 of the present invention.
  • FIG. 3 is a block diagram of a process for reducing a service node according to Embodiment 6 of the present invention.
  • FIG. 4 is a schematic diagram of steps of a method for adjusting a service node according to Embodiment 7 of the present invention.
  • FIG. 5 is a schematic structural diagram of an apparatus for adjusting a service node according to Embodiment 11 of the present invention.
  • FIG. 6 is a schematic structural diagram of an apparatus for adjusting a service node according to Embodiment 17 of the present invention.
  • the embodiments of the present invention provide a method, device, and device for adjusting service nodes by adding and deleting service nodes in the related art, so that the policy of the number attribution node is adjusted, so that the order of the messages is disordered.
  • the cached messages to be sent are sorted according to the time stamp after reallocation, so that the accuracy of the transmitted message can be guaranteed.
  • the method for adjusting the service node may include:
  • Step 11 Obtain a change indication request for changing a service node, where the change indication request includes indication information that carries a cached message attribution of a service node to be changed, where the service to be changed Points include increased service nodes or reduced service nodes;
  • Step 12 Parse the attribution of the to-be-changed service node cache message in the indication information according to the change indication request;
  • Step 13 Obtain a cache message of the service node to be changed.
  • Step 14 Send, according to the attribution of the cache message of the service node to be changed, a cache message that is not in the service node to be changed, to the home node, where the cache message is sorted according to a time stamp, where the time stamp is The time when the same called number passes the message to the SMS center.
  • step 11 to step 14 of the embodiment of the present invention by acquiring a change indication request of the service node (step 11), dynamic expansion of the service node is implemented, and the cache message of the service node to be changed is attributed (step 12), The cached message that does not belong to the service node to be changed is sent to the home node (step 14), and the sent cached messages are also sorted according to the timing, thereby ensuring the accuracy of the message transmission, so that the adaptive short message service traffic changes and ensures Adding a service node or deleting a service node number does not affect the processing of the message. It only needs to increase the service node to transmit the message according to the thread.
  • the home node After the home node receives the message from another service node, it needs to use the timestamp (SCTS, Service Center Time Stamp) of the original cache message as the key (key).
  • SCTS Service Center Time Stamp
  • the key data which can also be a key factor, is sorted, and the message is stored to the home node, so that there is no situation after the first message is received, and the user experience is improved.
  • the cache message that does not belong to the to-be-changed service node is sent to the home node in step 14 above, and may refer to forwarding the cache message that does not belong to the service node to be changed to the home thread A of the service node to be changed. On the home thread B of the home node.
  • Step 11 Obtain a change indication request for changing a service node, where the change indication request includes indication information that carries a cached message attribution of a service node to be changed, where the service to be changed Points include increased service nodes or reduced service nodes;
  • Step 121 Determine, according to the change indication request, that the service node to be changed in the change indication request is an increased first service node;
  • Step 122 Analyze the attribution of the cache message of the first service node in the indication information, where the attribution is a pre-configured cache message belonging to the first service node in each remaining service node. Giving the first service node, the remaining service node being a node of all service nodes except the first service node;
  • Step 13 Obtain a cache message of the service node to be changed.
  • Step 14 Send, according to the attribution, a cache message that does not belong to the to-be-changed service node, to the home node, where the cached message is sorted according to a time stamp, where the time stamp is the same called number, and the message is sent to the short message. Central time.
  • steps 11 to 14 of the embodiment of the present invention by obtaining a change indication request of the change service node (step 11), it is determined that the service node to be changed in the change indication request is the added first service node (step 121), so that According to the allocation of the cache message to the first service node (step 122), only the minimum number of nodes for configuring the service operation needs to be installed when the service is started, which reduces the engineering planning and deployment workload at the time of the deployment, and realizes rapid deployment of the service.
  • the method for adjusting the service node may include:
  • Step 11 Obtain a change indication request for changing a service node, where the change indication request includes indication information that carries a cached message attribution of a service node to be changed, where the to-be-changed service node includes an added service node or a reduced service node;
  • Step 121 Determine, according to the change indication request, that the service node to be changed in the change indication request is an increased first service node;
  • Step 122 Analyze the attribution of the first service node cache message in the indication information, where the attribution is pre-configured in each remaining service node to belong to the first service node.
  • the cached message is allocated to the first service node, and the remaining service node is a node of all service nodes except the first service node;
  • Step 13 Obtain a cache message of the service node to be changed.
  • Step 141 Determine whether the first cache message of the first service node belongs to a cache message of the first service node indicated by the first service node;
  • Step 142 If the first cache message of the first service node belongs to the first service node cache message indicated by the first service node, continue to scan for the remaining cache of the first cache message. Message; or
  • Step 143 If the first cache message of the first service node does not belong to the cache message of the first service node indicated by the home of the first service node, forward the first cache message to the home node. And continuing to scan for the remaining cached messages of the first cached message.
  • the first service node to be changed in the change indication request is obtained and determined (step 121), so that the cache message may be allocated according to the attribution to the first service node ( Step 122), in order to ensure that the cached message of each service node is correctly located, it is also required to determine a cache message in the first service node (step 141), and determine that each cache message in the first service node does not belong to the first
  • the cached message of the service node is sent to the home node (step 142), so that only the minimum number of nodes for configuring the service operation needs to be installed when the service is started, which reduces the engineering planning and deployment workload during the deployment, and realizes rapid deployment of the service;
  • the service node is automatically added, and no manual intervention is required, thereby realizing flexible configuration of resources and reducing maintenance costs; and being closely integrated with the traditional short message service, and ensuring the dynamic increase of service nodes, ensuring The delivery characteristics of the message
  • the method for adjusting the service node may include:
  • Step 11 Obtain a change indication request for changing a service node, where the change indication request includes indication information that carries a cached message attribution of a service node to be changed, where the to-be-changed service node includes an added service node or a reduced service node;
  • Step 121 Determine, according to the change indication request, that the service node to be changed in the change indication request is an increased first service node;
  • Step 122 Analyze the attribution of the cache message of the first service node in the indication information, where the attribution is a pre-configured cache message belonging to the first service node in each remaining service node. Giving the first service node, the remaining service node being a node of all service nodes except the first service node;
  • Step 13 Obtain a cache message of the service node to be changed.
  • Step 141 Determine whether the first cache message of the first service node belongs to the first service node cache message indicated by the first service node.
  • Step 142 If the first cache message of the first service node belongs to the first service node cache message indicated by the first service node, continue to scan for the remaining cache of the first cache message. Message; or
  • Step 143 If the first cache message of the first service node does not belong to the first service node cache message indicated by the first service node, forward the first cache message to the home node, and continue Scanning the remaining cached messages of the first cached message;
  • Step 15 until it is determined that all cached messages of the first service node are completed.
  • the first service node to be changed in the change indication request is obtained and determined (step 121), so that the cache message may be allocated according to the attribution to the first service node ( Step 122), in order to ensure that the cached message of each service node is correctly located, and determine all cached messages in the first service node, it is also required to determine a cache message in the first service node (step 141), and determine the first service node.
  • Each cache message sends a cache message that does not belong to the first service node to the home node (step 142) until it is determined that all cache messages in the first service node are completed (step 15).
  • the first cache message is a cache message of any one of the first service nodes.
  • an implementation process of adding a service node is as follows.
  • Step 201 In the process of adding the first service node, receiving a change indication request for adding a service node;
  • Step 202 After receiving the change indication request of the service node, the first service node starts scanning the cache message that the first service node does not send successfully, and determines whether the first cache message belongs according to the latest number assignment of the first service node configuration. a first service node; if the first cache message belongs to the first service node, go to step 204; if the first cache message does not belong to the first service node, go to step 203; Step 203. Transfer the first cache message to the home node The ownership thread goes.
  • Step 204 Continue scanning for the remaining other cached messages.
  • the first service node After receiving the cache message forwarded by the other service node, the first service node inserts the cache message into the cache of the first service node.
  • the time stamp of the message center For the message of the same called number, the time stamp of the message center must be strictly followed ( SCTS) to sort;
  • Step 205 Determine whether all cached messages of the first service node are scanned, if the scan is not completed, go to step 202; if the scan is completed, go to step 206;
  • Step 206 After all the cached messages of the first service node are scanned, send a cache processing completion message to the service node with the smallest node number;
  • Step 207 The smallest service node summarizes the cache processing notifications of all service nodes
  • Step 208 Determine that the smallest service node summarizes whether the cache processing of all service nodes is completed, if yes, execute step 209, if not, execute step 207;
  • Step 209 After all the cache processing of all the service nodes is collected, send a notification that the processing of the service node is completed.
  • the method for adjusting the service node may include:
  • Step 11 Obtain a change indication request for changing a service node, where the change indication request includes indication information that carries a cached message attribution of a service node to be changed, where the to-be-changed service node includes an added service node or a reduced service node;
  • Step 123 Determine, according to the change indication request, that the service node to be changed in the change indication request is a reduced second service node;
  • step 124 the attribution of the cache message of the second service node in the indication information is analyzed, where the attribution is that the cache message of the second service node is allocated to all current remaining service nodes according to the pre-configured attribution. All currently remaining service nodes are nodes of all service nodes except the second service node;
  • Step 13 Obtain a cache message of the service node to be changed.
  • Step 14 Send, according to the attribution of the cache message of the service node to be changed, a cache message that is not in the service node to be changed, to the home node, where the cache message is sorted according to a time stamp, where the time stamp is The time when the same called number passes the message to the SMS center.
  • step 11 to step 14 of the embodiment of the present invention the second service node to be changed in the change indication request is obtained (step 123), so that the cache message belongs to the second service node.
  • Allocating step 124
  • sending a cache message that does not belong to the service node to be changed to the home node (step 14), so that when the demand of the subsequent service traffic is reduced, the service node is automatically reduced, and no manual intervention is required.
  • the flexible configuration of the resources reduces the maintenance cost; it is also closely integrated with the traditional short message service, and ensures the delivery characteristics of the message when the service node is dynamically reduced.
  • the method for adjusting the service node may include:
  • Step 11 Obtain a change indication request for changing a service node, where the change indication request includes indication information that carries a cached message attribution of a service node to be changed, where the to-be-changed service node includes an added service node or a reduced service node;
  • Step 123 Determine, according to the change indication request, that the service node to be changed in the change indication request is a reduced second service node;
  • step 124 the attribution of the cache message of the second service node in the indication information is analyzed, where the attribution is that the cache message of the second service node is allocated to all current remaining service nodes according to the pre-configured attribution. All currently remaining service nodes are nodes of all service nodes except the second service node;
  • Step 13 Obtain a cache message of the service node to be changed.
  • Step 144 Generate, according to the change indication request, stop sending, by the second service node, Processing an instruction to cache the message, and receiving a first response message, wherein the first response message is a response to whether the cached message sent before the obtaining the change indication request is successfully sent;
  • Step 145 After receiving the first response message, dump all the bill files stored in the second service node, and determine all caches that are not successfully sent in all response messages of the second service node. Message
  • Step 146 Send, according to the configuration of the change indication request, all the cache messages that are not successfully sent by the second service node to the home node, where the all response messages include the first response message.
  • the second service node to be changed in the change indication request is obtained and determined (step 123), and then may be reallocated according to the cache message attributed to the second service node. (Step 124), and when the service node to be changed is the reduced second service node in the receipt of the change indication request, stop continuing to send the cache message that has not been processed, and receive all response messages (step 144), the response message
  • the cached message that is not successfully sent is sent to the home node (step 146), so that when the service traffic needs are reduced, the service node can be automatically reduced, and no manual intervention is required, thereby realizing flexible configuration of resources and reducing maintenance. Cost; also closely integrated with the traditional SMS service, ensuring the delivery characteristics of the message when the service node is dynamically reduced.
  • step 145 after the service processing is stopped for the reduced power-off second service node, the CDRs of the second service node memory that are not written in the CDR file are all dumped (dumped) to the CDR.
  • the CDR list is periodically scanned. If the CDR is still saved in the second service node, power-off is not allowed until all the CDR files are removed. This ensures that the reduced CDRs of the second service node cannot be lost, and the impact on the service is also reduced.
  • an implementation process of reducing a service node according to an embodiment of the present invention is as follows.
  • Step 301 In the process of reducing the second service node, receiving a change indication request for reducing the service node;
  • Step 302 After receiving the request for reducing the service node, the second service node first stops the outgoing cache message.
  • Step 303 The second service node periodically checks the original outgoing cache message and determines the outgoing message. Whether the response of the cached message is all returned; if the response is all returned, then go to step 304; if the corresponding does not all return, go to step 302;
  • Step 304 dump (dump) all the CDR files in the memory into the CDR file
  • Step 305 The second service node starts scanning the unsuccessfully cached message of the second service node, and calculates the home node and the home thread of the cache message according to the latest number assignment of the second service node configuration.
  • Step 306. The second service node sends the cached message that has not been successfully sent to the home thread of the home node of the cached message.
  • Step 307. After the other node forwards the message, the message is inserted into the local cache. For the message of the same called number, the message must be sorted according to the timestamp (SCTS) of the message center.
  • SCTS timestamp
  • Step 308. Determine whether the scanning of all the cached messages of the second service node is completed. If the scanning of all the cached messages is not completed, step 305 is performed. If all the scanning of the cached messages is completed, step 309 is performed;
  • Step 309 Check whether the second service node CDR file is taken away, if all are taken, step 310 is performed;
  • Step 310 After the CDR file of the second service node is all taken, send a notification to reduce the service node processing completion notification.
  • the method for adjusting the service node in this embodiment may include:
  • Step 41 Acquire a first change request for changing a service node to be changed, where the service node to be changed includes an added service node or a reduced service node;
  • Step 42 When the to-be-changed service node executes the last change indication request, the change information of all service node attributions is acquired for the first change request, where the last change indication request includes carrying the And changing the indication information of the cached message attribution of the service node, where the cached message is sorted according to a time stamp, where the time stamp is the time when the same called number delivery message arrives at the short message center;
  • Step 43 Generate and send a change indication according to the change information of all service nodes The request, wherein the change indication request includes indication information carrying the attribution of the service node cache message to be changed.
  • steps 41 to 43 of the embodiment of the present invention after obtaining the first change request for changing the service node to be changed (step 41), determining that the service node to be changed completes the previous change indication request (step 42), generating and transmitting one Changing the indication request (step 43), thereby ensuring the accuracy of the message transmission by generating the attribution indicating the request, thus adaptively responding to the change of the short message service traffic, and ensuring that the addition of the service node or the deletion of the service node number does not affect the processing of the message.
  • the service node needs to increase the traffic of the service according to the thread. When the service is started, the maximum traffic of the service does not need to be considered. Only the minimum number of nodes running the configuration service is installed, which reduces the engineering planning and deployment workload during the deployment, and implements the service. Rapid deployment.
  • Step 41 Acquire a first change request for changing a service node to be changed, where the service node to be changed includes an added service node or a reduced service node;
  • Step 44 When the to-be-changed service node performs the last change indication request is not ended, generating a message rejecting the response to the first change request;
  • Step 42 When the to-be-changed service node performs the end of the last change indication request, obtain, for the first change request, change information of all service node attributions, where the last change indication request includes carrying the And changing the indication information of the cached message attribution of the service node, where the cached message is sorted according to a time stamp, where the time stamp is the time when the same called number delivery message arrives at the short message center;
  • Step 43 Generate and send a change indication request according to the change information of all service node attributions, where the change indication request includes indication information that carries the cached message of the service node to be changed.
  • the first change request for changing the service node to be changed is obtained (step 41). ), when the pending change of the service node execution does not end the last change indication request, the first change request is rejected (step 44), and only the last change is performed.
  • a change indication request can be generated and sent (step 43), so that the change of the SMS service traffic can be adaptively handled, and the addition of the service node or the deletion of the service node number does not affect the processing of the message, and only the service node needs to be added. Threads transmit messages.
  • the service is started, you do not need to consider the maximum traffic of the service. You only need to install the minimum number of nodes to run the configuration service, which reduces the engineering planning and deployment workload during the deployment and enables rapid deployment of services.
  • Step 41 Acquire a first change request for changing a service node to be changed, where the service node to be changed includes an added service node or a reduced service node;
  • Step 421 When the to-be-changed service node performs the last change indication request, when the to-be-changed service node that is the first change request is the added first service node, generate a first change request. a notification message, where the notification message carries an increased node number of the first service node and an increased Internet Protocol Address (IP) address used by the first service node;
  • IP Internet Protocol Address
  • Step 422 Acquire, according to the notification message, the attribution of the cached message in all the service nodes, and allocate a pre-configured cache message belonging to the first service node in each of the remaining service nodes to the first service node.
  • the remaining service node is a node of all service nodes except the first service node;
  • Step 43 Generate and send a change indication request according to the change information of all service node attributions, where the change indication request includes indication information that carries the cached message of the service node to be changed.
  • steps 14 to 43 of the embodiment of the present invention when the service node to be changed executes the last change indication request, the first service node is added to the first change request (step 421), and then cached according to all the service nodes.
  • Step 41 Acquire a first change request for changing a service node to be changed, where the service node to be changed includes an added service node or a reduced service node;
  • Step 423 When the to-be-changed service node executes the last change indication request, when the to-be-changed service node for the first change request is the reduced second service node, generate a first change request. a notification message, where the notification message carries a node number of the reduced second service node;
  • Step 424 Acquire, according to the notification message, the attribution of the cached message in all the service nodes, and allocate the cached message of the second service node to all the remaining service nodes according to the pre-configured attribution, where the current all remaining services are
  • the node is a node of all service nodes except the second service node;
  • Step 43 Generate and send a change indication request according to the change information of all service node attributions, where the change indication request includes indication information that carries the cached message of the service node to be changed.
  • steps 14 to 43 of the embodiment of the present invention when the service node to be changed executes the last change indication request, the second service node of the first change request is executed (step 423), and the message is cached according to all the service nodes.
  • the attribution (step 424), generate and send a change indication request (step 43), so that the cache message of the second service node can be allocated to all current remaining service nodes according to the pre-configured attribution, so that when the subsequent traffic decreases
  • the service node can be automatically reduced, and no manual intervention is required, which realizes flexible configuration of resources and reduces maintenance costs. It is also closely integrated with the traditional short message service, and ensures the delivery characteristics of the message when the service node is dynamically increased. It also guarantees the accuracy of the transmitted message.
  • the adjustment apparatus of the service node in this embodiment may include:
  • the first obtaining module 51 is configured to acquire a change indication request of the change service node, where the change indication request includes indication information that carries the cache message attribution of the service node to be changed, where Determining that the changed service node includes an added service node or a reduced service node;
  • the parsing module 52 is configured to parse the attribution of the to-be-changed service node cache message in the indication information according to the change indication request;
  • the second obtaining module 53 is configured to acquire a cache message of the service node to be changed.
  • the first processing module 54 is configured to send, according to the attribution of the cache message of the service node to be changed, a cache message that does not belong to the service node to be changed, to the home node, where the cache message is sorted according to a time stamp.
  • the time stamp is the time when the same called number delivery message arrives at the short message center.
  • the first obtaining module 51 acquires the change indication request of the changing service node, implements dynamic scaling of the service node, and belongs to the cached message of the service node to be changed by the parsing module 52, and then passes through the first processing module 54.
  • the cached message that is not belong to the service node to be changed is sent to the home node, and the sent cached message is also sorted according to the sequence, thereby ensuring the accuracy of the message sending, so that the adaptive short message service traffic changes, and the service node is added. Or deleting the service node number does not affect the processing of the message. It only needs to increase the service node to transmit the message according to the thread.
  • the maximum traffic of the service is not required to be considered, and only the minimum number of nodes for configuring the service operation needs to be installed, which reduces the number of nodes when the service is started.
  • the engineering planning and deployment workload enables rapid deployment of the business.
  • the apparatus provided by the embodiment of the present invention is a device corresponding to the adjustment method of the service node, and all embodiments of the adjustment method of the service node are applicable to the device, and both can achieve the same or similar benefits. effect.
  • a first obtaining module configured to acquire a change indication request for changing a service node, where the change indication request includes indication information that carries a cached message attribution of the service node to be changed, where the to-be-changed service node includes an added service node or decreases Business node
  • a first parsing sub-module configured to determine, according to the change indication request, that the service node to be changed in the change indication request is an increased first service node
  • a second parsing sub-module configured to parse the attribution of the cache message of the first service node in the indication information, where the attribution is a pre-configured attribution attribute in each remaining service node a cache message of the first service node, which is allocated to the first service node, where the remaining service node is a node of all service nodes except the first service node;
  • a second obtaining module configured to acquire a cache message of the service node to be changed
  • the first processing module is configured to send, according to the attribution of the cached message of the service node to be changed, a cache message that is not in the service node to be changed, to the home node, where the cache message is sorted according to a time stamp.
  • the time stamp is the time when the same called number delivers the message to the SMS center.
  • the adjusting device of the service node may include:
  • a first obtaining module configured to acquire a change indication request for changing a service node, where the change indication request includes indication information that carries a cached message attribution of the service node to be changed, where the to-be-changed service node includes an added service node or decreases Business node
  • a first parsing sub-module configured to determine, according to the change indication request, that the service node to be changed in the change indication request is an increased first service node
  • a second parsing sub-module configured to parse the attribution of the first service node cache message in the indication information, where the attribution is pre-configured in each remaining service node to belong to the first service node Cache a message, which is allocated to the first service node, where the remaining service node is a node of all service nodes except the first service node;
  • a second obtaining module configured to acquire a cache message of the service node to be changed
  • a determining sub-module configured to determine whether the first cache message of the first service node belongs to a cache message of the first service node indicated by the first service node;
  • the scanning continues to remove the first cache The remaining cached message of the message;
  • a first sub-transmission module configured to: if the first cache message of the first service node does not belong to a cache message of the first service node indicated by the first service node, the first cache The message is forwarded to the home node, and the remaining cached messages of the first cached message are scanned.
  • a first obtaining module configured to acquire a change indication request for changing a service node, where the change indication request includes indication information that carries a cached message attribution of the service node to be changed, where the to-be-changed service node includes an added service node or decreases Business node
  • a first parsing sub-module configured to determine, according to the change indication request, that the service node to be changed in the change indication request is an increased first service node
  • a second parsing sub-module configured to parse the attribution of the cache message of the first service node in the indication information, where the attribution is pre-configured in each of the remaining service nodes to belong to the first service node
  • the cached message is allocated to the first service node, and the remaining service node is a node of all service nodes except the first service node;
  • a second obtaining module configured to acquire a cache message of the service node to be changed
  • a determining sub-module configured to determine whether the first cache message of the first service node belongs to the first service node cache message indicated by the first service node;
  • a first sub-transmission module configured to forward the first cache message if the first cache message of the first service node does not belong to the first service node cache message indicated in the home of the first service node Sending to the home node, scanning the remaining cached messages of the first cached message;
  • the determining module is configured to determine that all cached messages of the first service node are completed.
  • a first obtaining module configured to acquire a change indication request for changing a service node, where the change indication request includes indication information that carries a cached message attribution of the service node to be changed, where the to-be-changed service node includes an added service node or decreases Business node
  • a third parsing sub-module configured to determine, according to the change indication request, that the service node to be changed in the change indication request is a reduced second service node;
  • the fourth parsing sub-module is configured to parse the attribution of the cache message of the second service node in the indication information, where the attribution is to allocate the cache message of the second service node to the current according to the pre-configured attribution All remaining service nodes, wherein all current remaining service nodes are nodes of all service nodes except the second service node;
  • a second obtaining module configured to acquire a cache message of the service node to be changed
  • the first processing module is configured to send, according to the attribution of the cached message of the service node to be changed, a cache message that is not in the service node to be changed, to the home node, where the cache message is sorted according to a time stamp.
  • the time stamp is the time when the same called number delivers the message to the SMS center.
  • a first obtaining module configured to acquire a change indication request for changing a service node, where the change indication request includes indication information that carries a cached message attribution of the service node to be changed, where the to-be-changed service node includes an added service node or decreases Business node
  • a third parsing sub-module configured to determine, according to the change indication request, that the service node to be changed in the change indication request is a reduced second service node;
  • the fourth parsing sub-module is configured to parse the attribution of the cache message of the second service node in the indication information, where the attribution is to allocate the cache message of the second service node to the current according to the pre-configured attribution All remaining service nodes, wherein all current remaining service nodes are nodes of all service nodes except the second service node;
  • a second obtaining module configured to acquire a cache message of the service node to be changed
  • the interaction sub-module is configured to generate, according to the change indication request, an instruction to stop the second service node from sending a to-be-processed cache message, and receive a first response message, where the first response message is to obtain the change indication Whether the cached message sent before the request is sent successfully.
  • a fifth parsing sub-module configured to: after receiving the first response message, dump all the bill files stored in the second service node, and determine all responses of the second service node All cached messages in the message that did not send successfully;
  • the second sending submodule is configured to send, according to the configuration of the change indication request, all cached messages that are not successfully sent by the second service node to the home node, where the all response messages include the first response message.
  • the adjustment device of the service node in this embodiment may include:
  • the third obtaining module 61 is configured to acquire a first change request for changing the service node to be changed, where the to-be-changed service node includes an added service node or a reduced service node;
  • the fourth obtaining module 62 is configured to: when the to-be-changed service node executes the last change indication request, obtain, for the first change request, change information of all service node attributions, where the last change indication request includes Carrying the indication information of the cached message attribution of the service node to be changed, the cached message is sorted according to a time stamp, and the time stamp is a time when the same called number delivery message arrives at the short message center;
  • the second processing module 63 is configured to generate and send a change indication request according to the change information of all the service nodes, wherein the change indication request includes indication information that carries the cached message of the service node to be changed.
  • the second processing module 63 After the third change module 61 acquires the first change request of the service node to be changed, and determines that the service node to be changed completes the previous change indication request, the second processing module 63 generates and sends a change indication request. Therefore, by generating the attribution indicating the request, the accuracy of the message transmission is ensured, so that the change of the traffic of the short message service is adaptively handled, and the addition of the service node or the deletion of the service node number does not affect the processing of the message, and only the service node needs to be added. Threads transmit messages. When the service is started, you do not need to consider the maximum traffic of the service. You only need to install the minimum number of nodes to run the configuration service, which reduces the engineering planning and deployment workload during the deployment and enables rapid deployment of services.
  • the apparatus provided by the embodiment of the present invention is a device corresponding to the adjustment method of the service node, and all embodiments of the adjustment method of the service node are applicable to the device, and both can achieve the same or similar benefits. effect.
  • a third obtaining module configured to acquire a first change request for changing a service node to be changed, where the to-be-changed service node includes an added service node or a reduced service node;
  • Generating a module configured to generate a message rejecting the response to the first change request when the to-be-changed service node performs a last change indication request that is not completed;
  • a fourth obtaining module configured to: when the to-be-changed service node executes the last change indication request, obtain, for the first change request, change information of all service node attributions, where the last change indication request includes carrying The indication information of the cached message attribution of the service node to be changed, the cached message is sorted according to a time stamp, and the time stamp is a time when the same called number delivery message arrives at the short message center;
  • the second processing module is configured to generate and send a change indication request according to the change information of all the service nodes, wherein the change indication request includes indication information that carries the cached message of the service node to be changed.
  • a third obtaining module configured to acquire a first change request for changing a service node to be changed, where the to-be-changed service node includes an added service node or a reduced service node;
  • a first generation submodule configured to: when the to-be-changed service node executes the last change indication request, when the to-be-changed service node for the first change request is the added first service node, generate an execution a notification message of the first change request, where the notification message carries an increased node number of the first service node and an increased IP used by the first service node;
  • a first obtaining sub-module configured to acquire, according to the notification message, a home of a cached message in a first service node that is added to all service nodes, and pre-configured in the remaining service node to belong to the first service a cache message of the node, which is allocated to the first service node, where the remaining service node is a node of all service nodes except the first service node;
  • the second processing module is configured to generate and send a change indication request according to the change information of all the service nodes, wherein the change indication request includes indication information that carries the cached message of the service node to be changed.
  • a third obtaining module configured to acquire a first change request for changing a service node to be changed, where the to-be-changed service node includes an added service node or a reduced service node;
  • a second generation sub-module configured to: when the to-be-changed service node executes the last change indication request, when the to-be-changed service node for the first change request is the reduced second service node, generate an execution a notification message of the first change request, where the notification message carries a node number of the reduced second service node;
  • the second obtaining sub-module is configured to: obtain, according to the notification message, the attribution of the cached message in all the service nodes, and allocate the cached message of the second service node to all the remaining service nodes according to the pre-configured attribution, where All current remaining service nodes are nodes of all service nodes except the second service node;
  • the second processing module is configured to generate and send a change indication request according to the change information of all the service nodes, wherein the change indication request includes indication information that carries the cached message of the service node to be changed.
  • This embodiment provides a service side device, including an adjustment device of any one of the foregoing service nodes.
  • the apparatus for adjusting the service node according to the embodiment of the present invention is applied to the service side device. Therefore, the embodiment of the present invention further provides a service side device, where the implementation embodiments of the adjustment device of the service node are both The same technical effects can also be achieved in the embodiment applicable to the service side device.
  • the service-side device After the service-side device is online, the service-side device periodically reports KPI (Key Performance Indicators) data (current traffic, CPU usage and CPU usage, etc.) to the cloud management platform.
  • KPI Key Performance Indicators
  • the cloud management platform is based on the cloud management platform.
  • the KPI data and the configured scheduling policy are used to dynamically expand or shrink the node.
  • the service-side device ensures the special delivery characteristics of the short message.
  • the service side device adds the dynamic scheduling management device OMM_Agent (Operation and Maintenance Module_Agent) module to modify the number of the home node of the page, and the service side device.
  • OMM_Agent Operaation and Maintenance Module_Agent
  • the OMM_Agent is notified to increase the processing of the service node.
  • the service side device receives the request for reducing the service node sent by the OMM_Agent module; finally, after all the local CDR files are taken, , notify OMM_Agent to reduce the completion of the processing of the business node.
  • the embodiment provides a proxy device, including the adjustment device of the service node according to any of the above.
  • the apparatus for adjusting the service node according to the embodiment of the present invention is applied to the proxy device. Therefore, the embodiment of the present invention further provides a proxy device, wherein the implementation embodiments of the adjustment device of the service node are applicable to In the embodiment of the proxy device, the same technical effect can also be achieved.
  • proxy device may include: a service dynamic scheduling management module OMM_Agent, (Operation and Maintenance Module_Agent, operation and maintenance module-agent), which is mainly used for KPI data collection and message interaction with the cloud management platform. Business configuration management, data synchronization, and interaction of messages between services.
  • OMM_Agent Service dynamic scheduling management module
  • OMM_Agent Operaation and Maintenance Module_Agent, operation and maintenance module-agent
  • the cloud management platform After the condition of increasing the service node is satisfied, the cloud management platform notifies the OMM_Agent service to add a node, and the OMM_Agent first performs authentication to determine whether the service node can be added. If the last scheduled task of the service increases or decreases, the service node does not end yet. Authentication denied. If the authentication is passed, the OMM_Agent determines the node number of the adding node (the service number increases from small to large) and the IP used by the service, and feeds it back to the cloud management platform. The cloud management platform creates a new virtual machine and adds the IP used by the service to the network card.
  • the automatic installer of the service is called to install and configure the new node.
  • the new node is automatically started, and then the new section of the OMM_Agent is notified.
  • the OMM_Agent modifies the page node homing policy and other related configurations, and then synchronizes all the service nodes.
  • the OMM_Agent sends a scheduling increase request message to all service nodes.
  • the service-side device scans the local device. All cached messages, if different from the existing node configuration policy, forward the message to the home thread of the user's home node.
  • the other nodes sort the key according to the timestamp (SCTS) of the original message to the SMS center, and store the message to the node.
  • SCTS timestamp
  • the cloud management platform After the condition of the service node is reduced, the cloud management platform notifies the OMM_Agent that the service node needs to go offline. Similar to the process of adding the service node, the OMM_Agent first performs authentication. If the authentication is passed, the OMM_Agent determines the node number of the offline line (the service number is large. The network element at the front end of the device on the service side is not required to send a message to this node.
  • the OMM_Agent modifies the configuration of the page node and other configurations, all the service nodes are synchronized. After the synchronization is successful, the OMM_Agent sends a dynamic service node request to the to-be-powered node. After the service-side device receives the request, the node stops all outgoing messages, and so on. The send buffer is released, that is, after all the responses to the previously sent request come back, all the bills in the memory are cached and dumped to the file. Then scan all local cache messages and forward the message to the home thread of the home node.
  • the OMM_Agent sends a node scheduling notification request message to the service node after modifying the policy of the number home node, and the service node scans in its own cache queue. If there is a message that does not match the existing node attribution policy, Forwarding the message to the home thread of the home node, and deleting it from the node;
  • the service-side device After the processing of the cached message is completed, the service-side device starts to perform the scheduled scan of the CDR file. If all the CDR files are taken, the ID of the virtual machine that needs to reduce the service node is sent to the cloud management platform, and the cloud management platform stops the service. The node releases the virtual machine and reclaims the resources.
  • the cloud management platform monitors that the service side device satisfies the condition of increasing the service node, the service node is added according to the predetermined scheduling policy; if the service side device is monitored to meet the condition of reducing the service node, the service node is reduced according to the predetermined scheduling policy.
  • the above monitoring methods include:
  • the OMM_Agent After the service-side device is online, the OMM_Agent periodically collects KPI data (current traffic, CPU and memory usage, etc.) from the service performance statistics database, and reports it to the cloud management platform.
  • KPI data current traffic, CPU and memory usage, etc.
  • the cloud platform configuration scheduling policy includes parameters such as service traffic, CPU, and memory. If any parameter exceeds the threshold of the added service node, the service node is added; if any parameter is smaller than the threshold of the reduced service node, Reduce business nodes.
  • the cloud management platform increases the step size parameter N (N is greater than or equal to 3), and the scheduling policy must satisfy N times in succession to trigger the scheduling; in order to prevent the number of nodes from being reduced to 0, the service is increased.
  • the minimum number of nodes is set. If the number of nodes is less than or equal to this threshold, the node is no longer reduced.
  • the embodiment of the present invention further provides a computer readable storage medium, where the computer readable storage medium stores computer executable instructions, and when the computer executable instructions are executed, implements a method for adjusting a service node.
  • each module/unit in the above embodiment may be implemented in the form of hardware, for example, by implementing an integrated circuit to implement its corresponding function, or may be implemented in the form of a software function module, for example, executing a program stored in the memory by a processor. / instruction to achieve its corresponding function.
  • This application is not limited to any specific combination of hardware and software.
  • the foregoing technical solution ensures that adding a service node or deleting a service node number does not affect the processing of the message, and improves the accuracy of message transmission.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

一种业务节点的调整方法、装置及设备，其中所述业务节点的调整方法，包括获取更改业务节点的更改指示请求，其中，所述更改指示请求包括携带有待更改业务节点的缓存消息归属的指示信息，所述待更改业务节点包括增加的业务节点或者减少的业务节点；根据所述更改指示请求，解析所述指示信息中所述待更改业务节点的缓存消息的归属；获取所述待更改业务节点的缓存消息；根据所述待更改业务节点的缓存消息的归属，将不属于所述待更改业务节点的缓存消息，发送给归属节点，其中所述缓存消息按照时标进行排序，所述时标为同一被叫号码传递消息到达短信中心的时间。上述技术方案保证了增加业务节点或者删除业务节点号码不影响消息的处理，也提高了消息发送的准确性。

Description

一种业务节点的调整方法、装置及设备 技术领域
本文涉及但不限于通信领域，涉及一种业务节点的调整方法、装置及设备。
背景技术
短信业务有个明显的特点，就是在节假日时的业务量要远远大于平时，传统的短消息中心在开局时要考虑业务的最大流量，根据业务的最大流量，配置相应的硬件设备。这样就会导致，在平时的流量较小的情况下也会占用大量的硬件资源，造成资源的浪费。而且传统的短消息中心，后续局点业务量增大需要扩容的情况下，就要采购新的硬件，规划部署新的业务节点，工程时间很长。
CS(Circuit Switching，电路交换)域传统的短信业务，同一时刻只能向同一个目的用户终呼一条消息，在一个局内有多个业务节点的情况下，每条消息都是在被叫用户固定的归属节点的归属线程排队下发的。短信中心节点内部线程数量和线程号是固定的，因此可以通过一个算法进行归属计算，而节点号数量和节点号不是固定的，只能通过页面配置号码归属节点的策略。增加和删除节点，号码归属节点的策略都要调整，这样就会导致动态伸缩后，以前未下发成功消息缓存的节点，可能已经不是归属节点了。还有，短消息是有时序要求的，如果用户提交的顺序是A、B，但是用户收到的顺序是B、A，这样可能出现整个意思是相反的情况。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本发明实施例提供一种业务节点的调整方法、装置及设备，保证了增加业务节点或者删除业务节点号码不影响消息的处理，提高了消息发送的准确性。
本发明实施例提供的一种业务节点的调整方法，包括：
获取更改业务节点的更改指示请求，其中，所述更改指示请求包括携带有待更改业务节点的缓存消息归属的指示信息，所述待更改业务节点包括增加的业务节点或者减少的业务节点；
根据所述更改指示请求，解析所述指示信息中所述待更改业务节点的缓存消息的归属；
获取所述待更改业务节点的缓存消息；
根据所述待更改业务节点的缓存消息的归属，将不属于所述待更改业务节点的缓存消息发送给归属节点，其中所述缓存消息按照时标进行排序，所述时标为同一被叫号码传递消息到达短信中心的时间。
可选地，所述根据所述更改指示请求，解析所述指示信息中所述待更改业务节点的缓存消息的归属，包括：
根据所述更改指示请求，确定所述更改指示请求中待更改业务节点为增加的第一业务节点；
解析所述指示信息中所述第一业务节点的缓存消息的归属，其中，所述归属为将每个剩余业务节点中预先配置的归属于所述第一业务节点的缓存消息分配给所述第一业务节点，所述剩余业务节点为所有业务节点中除去所述第一业务节点的节点。
可选地，所述根据所述待更改业务节点的缓存消息的归属，将不属于所述待更改业务节点的缓存消息发送给归属节点，包括：
判断所述第一业务节点的第一缓存消息是否属于所述第一业务节点的归属中指示的所述第一业务节点的缓存消息；
如果所述第一业务节点的第一缓存消息属于所述第一业务节点的归属中指示的所述第一业务节点缓存消息，则继续扫描完除去所述第一缓存消息的剩余缓存消息；或者
如果所述第一业务节点的第一缓存消息不属于所述第一业务节点的归属中指示的所述第一业务节点的缓存消息，则将所述第一缓存消息转发给归属节点，继续扫描完除去所述第一缓存消息的剩余缓存消息。
可选地，所述方法还包括：直至判断完成所述第一业务节点的所有缓存消息。
可选地，所述根据所述更改指示请求，解析所述指示信息中所述待更改业务节点的缓存消息的归属，包括：
根据所述更改指示请求，确定所述更改指示请求中待更改业务节点为减少的第二业务节点；
解析所述指示信息中所述第二业务节点的缓存消息的归属，其中，所述归属为将所述第二业务节点的缓存消息按照预先配置的归属分配给当前所有剩余业务节点，所述当前所有剩余业务节点为所有业务节点中除去所述第二业务节点的节点。
可选地，所述根据所述待更改业务节点的缓存消息的归属，将不属于所述待更改业务节点的缓存消息，发送给归属节点，包括：
根据所述更改指示请求，产生停止所述第二业务节点发送待处理缓存消息的指令，并接收第一响应消息，其中所述第一响应消息为在获取所述更改指示请求之前发送的缓存消息是否发送成功的响应；
在接收到所述第一响应消息之后，将所述第二业务节点中存储的所有话单文件转储，并确定所述第二业务节点的全部响应消息中所有未发送成功的缓存消息；
根据所述更改指示请求的配置，将所述第二业务节点所有未发送成功的缓存消息发送给归属节点，其中所述全部响应消息包括所述第一响应消息。
本发明实施例还提供一种业务节点的调整方法，包括：
获取变更待更改业务节点的第一更改请求，其中所述待更改业务节点包括增加的业务节点或者减少的业务节点；
在所述待更改业务节点执行上一个更改指示请求结束时，针对所述第一更改请求，获取所有业务节点归属的变更信息，其中所述上一个更改指示请求包括携带有所述待更改业务节点的缓存消息归属的指示信息，所述缓存消息按照时标进行排序，所述时标为同一被叫号码传递消息到达短信中心的时间；
根据所有业务节点归属的变更信息，生成并发送一个更改指示请求，其中所述更改指示请求包括携带有所述待更改业务节点的缓存消息归属的指示信息。
可选地，所述方法还包括：所述获取变更待更改业务节点的第一更改请求之后，在所述待更改业务节点执行上一个更改指示请求未结束时，生成拒绝响应所述第一更改请求的消息。
可选地，在所述待更改业务节点执行上一个更改指示请求结束时，针对所述第一更改请求，获取所有业务节点归属的变更信息，包括：
在所述待更改业务节点执行上一个更改指示请求结束时，针对所述第一更改请求的待更改业务节点为增加的第一业务节点时，生成一执行所述第一更改请求的通知消息，其中所述通知消息中携带有增加的第一业务节点的节点号及增加的第一业务节点使用的互联网协议IP地址；
根据所述通知消息，获取所有业务节点中缓存消息的归属，并将每个剩余业务节点中预先配置的归属于所述第一业务节点的缓存消息，分配给所述第一业务节点，其中所述剩余业务节点为所有业务节点中除去所述第一业务节点的节点。
可选地，所述在所述待更改业务节点执行上一个更改指示请求结束时，针对所述第一更改请求，获取所有业务节点归属的变更信息，包括：
在所述待更改业务节点执行上一个更改指示请求结束时，针对所述第一更改请求的待更改业务节点为减少的第二业务节点时，生成一执行所述第一更改请求的通知消息，其中所述通知消息中携带有减少的第二业务节点的节点号；
根据所述通知消息，获取所有业务节点中缓存消息的归属，并将所述第二业务节点的缓存消息按照预先配置的归属分配给当前所有剩余业务节点，其中所述当前所有剩余业务节点为所有业务节点中除去所述第二业务节点的节点。
本发明实施例还提供一种业务节点的调整装置，包括：
第一获取模块，设置为获取更改业务节点的更改指示请求，其中，所述 更改指示请求包括携带有待更改业务节点的缓存消息归属的指示信息，所述待更改业务节点包括增加的业务节点或者减少的业务节点；
解析模块，设置为根据所述更改指示请求，解析所述指示信息中所述待更改业务节点的缓存消息的归属；
第二获取模块，设置为获取所述待更改业务节点的缓存消息；
第一处理模块，设置为根据所述待更改业务节点的缓存消息的归属，将不属于所述待更改业务节点的缓存消息，发送给归属节点，其中所述缓存消息按照时标进行排序，所述时标为同一被叫号码传递消息到达短信中心的时间。
本发明实施例还提供一种业务节点的调整装置，包括：
第三获取模块，设置为获取变更待更改业务节点的第一更改请求，其中所述待更改业务节点包括增加的业务节点或者减少的业务节点；
第四获取模块，设置为在所述待更改业务节点执行上一个更改指示请求结束时，针对所述第一更改请求，获取所有业务节点归属的变更信息，其中所述上一个更改指示请求包括携带有所述待更改业务节点的缓存消息归属的指示信息，所述缓存消息按照时标进行排序，所述时标为同一被叫号码传递消息到达短信中心的时间；
第二处理模块，设置为根据所有业务节点归属的变更信息，生成并发送一个更改指示请求，其中所述更改指示请求包括携带有所述待更改业务节点的缓存消息归属的指示信息。
本发明实施例还提供一种业务侧设备，包括如上述的业务节点的调整装置。
本发明实施例还提供一种代理设备，包括如上述的业务节点的调整装置。
本发明实施例的上述技术方案的有益效果如下：
本发明实施例的方案中，通过获取更改业务节点的更改指示请求，实现业务节点的动态伸缩，并通过待更改业务节点的缓存消息归属，将不属于待更改业务节点的缓存消息，发送给归属节点，也将发送的缓存消息按照时序进行排序，从而保证了消息发送的准确性，这样自适应短信业务流量的变化， 并保证增加业务节点或者删除业务节点号码不影响消息的处理，只需要增加业务节点按照线程传送消息；在业务开局时，不需要考虑业务的最大流量，只需要安装配置业务运行的最小节点数，减少了开局时的工程规划和部署工作量，实现了业务的快速部署。本发明实施例还提供一种计算机可读存储介质，所述计算机可读存储介质中存储有计算机可执行指令，所述计算机可执行指令被执行时实现业务节点的调整方法。
在阅读并理解了附图和详细描述后，可以明白其它方面。
附图说明
图1为本发明实施例一的业务节点的调整方法的步骤示意图；
图2为本发明实施例四的增加业务节点流程框图；
图3为本发明实施例六的减少业务节点流程框图；
图4为本发明实施例七的业务节点的调整方法的步骤示意图；
图5为本发明实施例十一的业务节点的调整装置的结构示意图；
图6为本发明实施例十七的业务节点的调整装置的结构示意图。
具体实施方式
为使本发明要解决的技术问题、技术方案和优点更加清楚，下面将结合附图及具体实施例进行详细描述。
本发明实施例针对相关技术中增加和删除业务节点，使得号码归属节点的策略调整，从而让消息的顺序发生顺序错乱的问题，提供一种业务节点的调整方法、装置及设备，将这些重新分配的待发送缓存消息，在重新分配后按照时标进行排序，这样就可以保证传输消息的准确性。
实施例一
如图1所示，该业务节点的调整方法，可以包括：
步骤11，获取更改业务节点的更改指示请求，其中，所述更改指示请求包括携带有待更改业务节点的缓存消息归属的指示信息，所述待更改业务节 点包括增加的业务节点或者减少的业务节点；
步骤12，根据所述更改指示请求，解析所述指示信息中所述待更改业务节点缓存消息的归属；
步骤13，获取所述待更改业务节点的缓存消息；
步骤14，根据所述待更改业务节点的缓存消息的归属，将不属于所述待更改业务节点的缓存消息，发送给归属节点，其中所述缓存消息按照时标进行排序，所述时标为同一被叫号码传递消息到达短信中心的时间。
在本发明实施例的步骤11至步骤14中，通过获取更改业务节点的更改指示请求(步骤11)，实现业务节点的动态伸缩，并通过待更改业务节点的缓存消息归属(步骤12)，将不属于待更改业务节点的缓存消息，发送给归属节点(步骤14)，也将发送的缓存消息按照时序进行排序，从而保证了消息发送的准确性，这样自适应短信业务流量的变化，并保证增加业务节点或者删除业务节点号码不影响消息的处理，只需要增加业务节点按照线程传送消息；在业务开局时，不需要考虑业务的最大流量，只需要安装配置业务运行的最小节点数，减少了开局时的工程规划和部署工作量，实现了业务的快速部署。
需要说明的是：上述归属节点收到其他业务节点转发消息后，需要根据原缓存消息到达短信中心的时标(SCTS，Service Center Time Stamp，服务中心时间戳)为关键字(key)(可以是关键数据，也可以是关键因子)进行排序，将消息存储到该归属节点，这样不会存在先发的消息后收到的情况，提高了用户的体验。
上述步骤14中的将不属于所述待更改业务节点的缓存消息，发送给归属节点，可以是指通过待更改业务节点的归属线程A，将不属于所述待更改业务节点的缓存消息转发至归属节点的归属线程B上。
实施例二
本实施例的业务节点的调整方法，可以包括：
步骤11，获取更改业务节点的更改指示请求，其中，所述更改指示请求包括携带有待更改业务节点的缓存消息归属的指示信息，所述待更改业务节 点包括增加的业务节点或者减少的业务节点；
步骤121，根据所述更改指示请求，确定所述更改指示请求中待更改业务节点为增加的第一业务节点；
步骤122，解析所述指示信息中所述第一业务节点的缓存消息的归属，其中，所述归属为将每个剩余业务节点中预先配置的归属于所述第一业务节点的缓存消息，分配给所述第一业务节点，所述剩余业务节点为所有业务节点中除去所述第一业务节点的节点；
步骤13，获取所述待更改业务节点的缓存消息；
步骤14，根据所述归属，将不属于所述待更改业务节点的缓存消息，发送给归属节点，其中所述缓存消息按照时标进行排序，所述时标为同一被叫号码传递消息到达短信中心的时间。
本发明实施例的步骤11至步骤14中，通过获取更改业务节点的更改指示请求(步骤11)，确定更改指示请求中待更改业务节点为增加的第一业务节点(步骤121)，这样就可以按照归属给第一业务节点分配缓存消息(步骤122)，从而在业务开局时，只需要安装配置业务运行的最小节点数，减少了开局时的工程规划和部署工作量，实现了业务的快速部署；并且在后续业务流量增加时，通过自动增加业务节点，不需要人工干预，实现了资源的灵活配置，减少了维护成本；也与传统的短信业务紧密结合，在业务节点动态增加的情况下，保证了消息的下发特性。
实施例三
该业务节点的调整方法，可以包括：
步骤11，获取更改业务节点的更改指示请求，其中，所述更改指示请求包括携带有待更改业务节点的缓存消息归属的指示信息，所述待更改业务节点包括增加的业务节点或者减少的业务节点；
步骤121，根据所述更改指示请求，确定所述更改指示请求中待更改业务节点为增加的第一业务节点；
步骤122，解析所述指示信息中所述第一业务节点缓存消息的归属，其中，所述归属为将每个剩余业务节点中预先配置的归属于所述第一业务节点 的缓存消息，分配给所述第一业务节点，所述剩余业务节点为所有业务节点中除去所述第一业务节点的节点；
步骤13，获取所述待更改业务节点的缓存消息；
步骤141，判断所述第一业务节点的第一缓存消息是否属于所述第一业务节点的归属中指示的所述第一业务节点的缓存消息；
步骤142，如果所述第一业务节点的第一缓存消息属于所述第一业务节点的归属中指示的所述第一业务节点缓存消息，则继续扫描完除去所述第一缓存消息的剩余缓存消息；或者
步骤143，如果所述第一业务节点的第一缓存消息不属于所述第一业务节点的归属中指示的所述第一业务节点的缓存消息，则将所述第一缓存消息转发给归属节点，继续扫描完除去所述第一缓存消息的剩余缓存消息。
本发明实施例的步骤11至步骤142中，通过获取并确定更改指示请求中待更改业务节点为增加的第一业务节点(步骤121)，这样就可以按照归属给第一业务节点分配缓存消息(步骤122)，为了确保每个业务节点的缓存消息的归属正确，还需要判断第一业务节点中缓存消息(步骤141)，判断第一业务节点中的每条缓存消息，将不属于该第一业务节点的缓存消息发送至归属节点(步骤142)，这样在业务开局时，只需要安装配置业务运行的最小节点数，减少了开局时的工程规划和部署工作量，实现了业务的快速部署；并且在后续业务流量增加时，通过自动增加业务节点，不需要人工干预，实现了资源的灵活配置，减少了维护成本；也与传统的短信业务紧密结合，在业务节点动态增加的情况下，保证了消息的下发特性。
实施例四
该业务节点的调整方法，可以包括：
步骤11，获取更改业务节点的更改指示请求，其中，所述更改指示请求包括携带有待更改业务节点的缓存消息归属的指示信息，所述待更改业务节点包括增加的业务节点或者减少的业务节点；
步骤121，根据所述更改指示请求，确定所述更改指示请求中待更改业务节点为增加的第一业务节点；
步骤122，解析所述指示信息中所述第一业务节点的缓存消息的归属，其中，所述归属为将每个剩余业务节点中预先配置的归属于所述第一业务节点的缓存消息，分配给所述第一业务节点，所述剩余业务节点为所有业务节点中除去所述第一业务节点的节点；
步骤13，获取所述待更改业务节点的缓存消息；
步骤141，判断所述第一业务节点的第一缓存消息是否属于所述第一业务节点的归属中指示的所述第一业务节点缓存消息；
步骤142，如果所述第一业务节点的第一缓存消息属于所述第一业务节点的归属中指示的所述第一业务节点缓存消息，则继续扫描完除去所述第一缓存消息的剩余缓存消息；或者
步骤143，如果所述第一业务节点的第一缓存消息不属于所述第一业务节点的归属中指示的所述第一业务节点缓存消息，将所述第一缓存消息转发给归属节点，继续扫描完除去所述第一缓存消息的剩余缓存消息；
步骤15，直至判断完成所述第一业务节点的所有缓存消息。
本发明实施例的步骤11至步骤15中，通过获取并确定更改指示请求中待更改业务节点为增加的第一业务节点(步骤121)，这样就可以按照归属给第一业务节点分配缓存消息(步骤122)，为了确保每个业务节点的缓存消息的归属正确，并判断第一业务节点中的所有缓存消息，还需要判断第一业务节点中缓存消息(步骤141)，判断第一业务节点中的每条缓存消息，将不属于该第一业务节点的缓存消息发送至归属节点(步骤142)，直至判断完成第一业务节点中的所有缓存消息(步骤15)。这样在业务开局时，只需要安装配置业务运行的最小节点数，减少了开局时的工程规划和部署工作量，实现了业务的快速部署；并且在后续业务流量增加时，通过自动增加业务节点，不需要人工干预，实现了资源的灵活配置，减少了维护成本；也与传统的短信业务紧密结合，在业务节点动态增加的情况下，保证了消息的下发特性。
需要说明的是：上述第一缓存消息为上述第一业务节点中的任何一条缓存消息。
如图2所示，本发明实施例的增加业务节点的实现流程举例如下。
步骤201.在增加第一业务节点流程中，会收到增加业务节点的更改指示请求；
步骤202.第一业务节点收到增加业务节点的更改指示请求后，开始扫描第一业务节点未发送成功的缓存消息，根据最新关于第一业务节点配置的号码归属，判断第一缓存消息是否属于第一业务节点；如果第一缓存消息属于第一业务节点，则转步骤204；如果第一缓存消息不属于第一业务节点，则转步骤203；步骤203.将第一缓存消息转到归属节点的归属线程去.
步骤204.继续扫描剩余的其他缓存消息。第一业务节点收到其他业务节点转发的缓存消息后，要将缓存消息插入到第一业务节点的缓存中，对于同一个被叫号码的消息，一定要严格按照消息到达短信中心的时标(SCTS)进行排序；
步骤205.判断第一业务节点的所有缓存消息是否扫描完成，如果未完成扫描则执行步骤202；如果完成扫描，执行步骤206；
步骤206.在第一业务节点的所有缓存消息扫描完成后，向节点号最小的业务节点发送一条缓存处理完成消息；
步骤207.最小的业务节点汇总所有业务节点的缓存处理通知；
步骤208.判断最小的业务节点汇总所有业务节点的缓存处理是否完成，如果完成则执行步骤209，如果未完成则执行步骤207；
步骤209.在所有业务节点的缓存处理全部收齐后，发送一增加业务节点处理完成的通知。
实施例五
该业务节点的调整方法，可以包括：
步骤11，获取更改业务节点的更改指示请求，其中，所述更改指示请求包括携带有待更改业务节点的缓存消息归属的指示信息，所述待更改业务节点包括增加的业务节点或者减少的业务节点；
步骤123，根据所述更改指示请求，确定所述更改指示请求中待更改业务节点为减少的第二业务节点；
步骤124，解析所述指示信息中所述第二业务节点的缓存消息的归属，其中，所述归属为将所述第二业务节点的缓存消息按照预先配置的归属分配给当前所有剩余业务节点，所述当前所有剩余业务节点为所有业务节点中除去所述第二业务节点的节点；
步骤13，获取所述待更改业务节点的缓存消息；
步骤14，根据所述待更改业务节点的缓存消息的归属，将不属于所述待更改业务节点的缓存消息，发送给归属节点，其中所述缓存消息按照时标进行排序，所述时标为同一被叫号码传递消息到达短信中心的时间。
本发明实施例的步骤11至步骤14中，通过获取并确定更改指示请求中待更改业务节点为减少的第二业务节点(步骤123)，这样就可以按照归属给第二业务节点的缓存消息重新分配(步骤124)，将不属于所述待更改业务节点的缓存消息，发送给归属节点(步骤14)，这样在后续业务流量的需要减少时，通过自动减少业务节点，不需要人工干预，实现了资源的灵活配置，减少了维护成本；也与传统的短信业务紧密结合，在业务节点动态减少的情况下，保证了消息的下发特性。
实施例六
该业务节点的调整方法，可以包括：
步骤11，获取更改业务节点的更改指示请求，其中，所述更改指示请求包括携带有待更改业务节点的缓存消息归属的指示信息，所述待更改业务节点包括增加的业务节点或者减少的业务节点；
步骤123，根据所述更改指示请求，确定所述更改指示请求中待更改业务节点为减少的第二业务节点；
步骤124，解析所述指示信息中所述第二业务节点的缓存消息的归属，其中，所述归属为将所述第二业务节点的缓存消息按照预先配置的归属分配给当前所有剩余业务节点，所述当前所有剩余业务节点为所有业务节点中除去所述第二业务节点的节点；
步骤13，获取所述待更改业务节点的缓存消息；
步骤144，根据所述更改指示请求，产生停止所述第二业务节点发送待 处理缓存消息的指令，并接收第一响应消息，其中所述第一响应消息为在获取所述更改指示请求之前发送的缓存消息是否发送成功的响应；
步骤145，在接收到所述第一响应消息之后，将所述第二业务节点中存储的所有话单文件转储，并确定所述第二业务节点的全部响应消息中所有未发送成功的缓存消息；
步骤146，根据所述更改指示请求的配置，将所述第二业务节点所有未发送成功的缓存消息发送给归属节点，其中所述全部响应消息包括所述第一响应消息。
本发明实施例的步骤11至步骤146中，通过获取并确定更改指示请求中待更改业务节点为减少的第二业务节点(步骤123)，然后可以按照归属给第二业务节点的缓存消息重新分配(步骤124)，并且在收到更改指示请求中待更改业务节点为减少的第二业务节点时，停止继续发送还未处理的缓存消息，并接收所有的响应消息(步骤144)，将响应消息中指示的未发送成功的缓存消息，发送给归属节点(步骤146)，这样在后续业务流量的需要减少时，可以自动减少业务节点，不需要人工干预，实现了资源的灵活配置，减少了维护成本；也与传统的短信业务紧密结合，在业务节点动态减少的情况下，保证了消息的下发特性。
需要说明的是：上述步骤145，对于减少的下电第二业务节点，停止业务处理后，首先将第二业务节点内存中未写入话单文件的话单，全部dump(转储)到话单文件中，然后定时扫描话单目录；如果在第二业务节点还保存有话单，则不允许下电，直到所有话单文件被全部取走。这样保证了减少的第二业务节点的话单不能丢失，也减少了对业务的影响。
如图3所示，本发明实施例的减少业务节点的实现流程举例如下。
步骤301.在减少第二业务节点流程中，会收到减少业务节点的更改指示请求；
步骤302.第二业务节点收到减少业务节点请求后，首先停止外发缓存消息；
步骤303.第二业务节点后续定时查看原先外发的缓存消息，判断外发 的缓存消息的响应是否全部返回了；如果响应全部返回了，则转步骤304；如果相应没有全部返回，则转步骤302；
步骤304，将内存中的所有的话单文件dump(转储)到话单文件中；
步骤305.第二业务节点开始扫描第二业务节点的未发送成功的缓存消息，根据最新关于第二业务节点配置的号码归属，计算缓存消息的归属节点和归属线程；
步骤306.第二业务节点将未发送成功的缓存消息，转到缓存消息的归属节点归属线程去；
步骤307.其他节点的转发消息后，将消息插入到本地缓存中，对于同一个被叫号码的消息，一定要严格按照消息到达短信中心的时标(SCTS)进行排序
步骤308.判断第二业务节点的所有缓存消息的扫描是否完成，如果未完成所有缓存消息的扫描，则执行步骤305，如果完成了所有缓存消息的扫描，则执行步骤309；
步骤309.查看第二业务节点话单文件是否全部被取走，如果全部被取走，则执行步骤310；
步骤310.在第二业务节点的话单文件全部被取以后，发送一通知减少业务节点处理完成通知。
实施例七
如图4所示，本实施例的业务节点的调整方法，可以包括：
步骤41，获取变更待更改业务节点的第一更改请求，其中所述待更改业务节点包括增加的业务节点或者减少的业务节点；
步骤42，在所述待更改业务节点执行上一个更改指示请求结束时，针对所述第一更改请求，获取所有业务节点归属的变更信息，其中所述上一个更改指示请求包括携带有所述待更改业务节点的缓存消息归属的指示信息，所述缓存消息按照时标进行排序，所述时标为同一被叫号码传递消息到达短信中心的时间；
步骤43，根据所有业务节点归属的变更信息，生成并发送一个更改指示 请求，其中所述更改指示请求包括携带有所述待更改业务节点缓存消息归属的指示信息。
本发明实施例的步骤41至步骤43中，通过获取变更待更改业务节点的第一更改请求(步骤41)，判断待更改业务节点完成上一个更改指示请求之后(步骤42)，生成并发送一个更改指示请求(步骤43)，从而通过生成指示请求的归属，保证了消息发送的准确性，这样自适应的应对短信业务流量的变化，并保证增加业务节点或者删除业务节点号码不影响消息的处理，只需要增加业务节点按照线程传送消息；在业务开局时，不需要考虑业务的最大流量，只需要安装配置业务运行的最小节点数，减少了开局时的工程规划和部署工作量，实现了业务的快速部署。
实施例八
本实施例的业务节点的调整方法，可以包括：
步骤41，获取变更待更改业务节点的第一更改请求，其中所述待更改业务节点包括增加的业务节点或者减少的业务节点；
步骤44，在所述待更改业务节点执行上一个更改指示请求未结束时，生成拒绝响应所述第一更改请求的消息；
步骤42，在所述待更改业务节点执行结束上一个更改指示请求时，针对所述第一更改请求，获取所有业务节点归属的变更信息，其中所述上一个更改指示请求包括携带有所述待更改业务节点的缓存消息归属的指示信息，所述缓存消息按照时标进行排序，所述时标为同一被叫号码传递消息到达短信中心的时间；
步骤43，根据所有业务节点归属的变更信息，生成并发送一个更改指示请求，其中所述更改指示请求包括携带有所述待更改业务节点缓存消息归属的指示信息。
本发明实施例中的步骤14至步骤43中，为了保证每个更改指示请求的完整执行，且前后的更改指示请求之间不影响，通过获取变更待更改业务节点的第一更改请求(步骤41)，在待更改业务节点执行未结束上一个更改指示请求时，拒绝响应第一更改请求(步骤44)，只有在执行完成上一个更改 指示请求后，才能生成并发送一个更改指示请求(步骤43)，这样自适应的应对短信业务流量的变化，并保证增加业务节点或者删除业务节点号码不影响消息的处理，只需要增加业务节点按照线程传送消息；在业务开局时，不需要考虑业务的最大流量，只需要安装配置业务运行的最小节点数，减少了开局时的工程规划和部署工作量，实现了业务的快速部署。
实施例九
本实施例的业务节点的调整方法，可以包括：
步骤41，获取变更待更改业务节点的第一更改请求，其中所述待更改业务节点包括增加的业务节点或者减少的业务节点；
步骤421，在所述待更改业务节点执行上一个更改指示请求结束时，针对所述第一更改请求的待更改业务节点为增加的第一业务节点时，生成一执行所述第一更改请求的通知消息，其中所述通知消息中携带有增加的第一业务节点的节点号及增加的第一业务节点使用的互联网协议(IP，Internet Protocol Address)地址；
步骤422，根据所述通知消息，获取所有业务节点中缓存消息的归属，并将每个剩余业务节点中预先配置的归属于所述第一业务节点的缓存消息，分配给所述第一业务节点，其中所述剩余业务节点为所有业务节点中除去所述第一业务节点的节点；
步骤43，根据所有业务节点归属的变更信息，生成并发送一个更改指示请求，其中所述更改指示请求包括携带有所述待更改业务节点缓存消息归属的指示信息。
本发明实施例中的步骤14至步骤43中，在待更改业务节点执行结束上一个更改指示请求时，执行第一更改请求的增加第一业务节点(步骤421)，然后根据所有业务节点中缓存消息的归属(步骤422)，生成并发送一个更改指示请求(步骤43)，这样就可以按照归属给第一业务节点分配缓存消息，这样在后续业务流量增加时，可以自动增加业务节点，不需要人工干预，实现了资源的灵活配置，减少了维护成本；也与传统的短信业务紧密结合，在业务节点动态增加的情况下，保证了消息的下发特性。
实施例十
本实施例的业务节点的调整方法，可以包括：
步骤41，获取变更待更改业务节点的第一更改请求，其中所述待更改业务节点包括增加的业务节点或者减少的业务节点；
步骤423，在所述待更改业务节点执行上一个更改指示请求结束时，针对所述第一更改请求的待更改业务节点为减少的第二业务节点时，生成一执行所述第一更改请求的通知消息，其中所述通知消息中携带有减少的第二业务节点的节点号；
步骤424，根据所述通知消息，获取所有业务节点中缓存消息的归属，并将所述第二业务节点的缓存消息按照预先配置的归属分配给当前所有剩余业务节点，其中所述当前所有剩余业务节点为所有业务节点中除去所述第二业务节点的节点；
步骤43，根据所有业务节点归属的变更信息，生成并发送一个更改指示请求，其中所述更改指示请求包括携带有所述待更改业务节点缓存消息归属的指示信息。
本发明实施例中的步骤14至步骤43中，在待更改业务节点执行结束上一个更改指示请求时，执行第一更改请求的减少第二业务节点(步骤423)，根据所有业务节点中缓存消息的归属(步骤424)，生成并发送一个更改指示请求(步骤43)，这样就可以按照预先配置的归属将第二业务节点的缓存消息分配给当前所有剩余业务节点，这样在后续业务流量减少时，可以自动减少业务节点，不需要人工干预，实现了资源的灵活配置，减少了维护成本；也与传统的短信业务紧密结合，在业务节点动态增加的情况下，保证了消息的下发特性，也可以保证传输消息的准确性。
实施例十一
如图5所示，本实施例的业务节点的调整装置，可以包括：
第一获取模块51，设置为获取更改业务节点的更改指示请求，其中，所述更改指示请求包括携带有待更改业务节点的缓存消息归属的指示信息，所 述待更改业务节点包括增加的业务节点或者减少的业务节点；
解析模块52，设置为根据所述更改指示请求，解析所述指示信息中所述待更改业务节点缓存消息的归属；
第二获取模块53，设置为获取所述待更改业务节点的缓存消息；
第一处理模块54，设置为根据所述待更改业务节点的缓存消息的归属，将不属于所述待更改业务节点的缓存消息，发送给归属节点，其中所述缓存消息按照时标进行排序，所述时标为同一被叫号码传递消息到达短信中心的时间。
在本发明实施例中，通过第一获取模块51获取更改业务节点的更改指示请求，实现业务节点的动态伸缩，并通过解析模块52待更改业务节点的缓存消息归属，然后经第一处理模块54将不属于待更改业务节点的缓存消息，发送给归属节点，也将发送的缓存消息按照时序进行排序，从而保证了消息发送的准确性，这样自适应短信业务流量的变化，并保证增加业务节点或者删除业务节点号码不影响消息的处理，只需要增加业务节点按照线程传送消息；在业务开局时，不需要考虑业务的最大流量，只需要安装配置业务运行的最小节点数，减少了开局时的工程规划和部署工作量，实现了业务的快速部署。
需要说明的是，本发明实施例提供的装置是对应的上述业务节点的调整方法的装置，则上述业务节点的调整方法的所有实施例均适用于该装置，且均能达到相同或相似的有益效果。
实施例十二
本实施例的业务节点的调整装置，可以包括：
第一获取模块，设置为获取更改业务节点的更改指示请求，其中，所述更改指示请求包括携带有待更改业务节点的缓存消息归属的指示信息，所述待更改业务节点包括增加的业务节点或者减少的业务节点；
第一解析子模块，设置为根据所述更改指示请求，确定所述更改指示请求中待更改业务节点为增加的第一业务节点；
第二解析子模块，设置为解析所述指示信息中所述第一业务节点的缓存消息的归属，其中，所述归属为将每个剩余业务节点中预先配置的归属于所 述第一业务节点的缓存消息，分配给所述第一业务节点，所述剩余业务节点为所有业务节点中除去所述第一业务节点的节点；
第二获取模块，设置为获取所述待更改业务节点的缓存消息；
第一处理模块，设置为根据所述待更改业务节点的缓存消息的归属，将不属于所述待更改业务节点的缓存消息，发送给归属节点，其中所述缓存消息按照时标进行排序，所述时标为同一被叫号码传递消息到达短信中心的时间。
实施例十三
该业务节点的调整装置，可以包括：
第一获取模块，设置为获取更改业务节点的更改指示请求，其中，所述更改指示请求包括携带有待更改业务节点的缓存消息归属的指示信息，所述待更改业务节点包括增加的业务节点或者减少的业务节点；
第一解析子模块，设置为根据所述更改指示请求，确定所述更改指示请求中待更改业务节点为增加的第一业务节点；
第二解析子模块，设置为解析所述指示信息中所述第一业务节点缓存消息的归属，其中，所述归属为将每个剩余业务节点中预先配置的归属于所述第一业务节点的缓存消息，分配给所述第一业务节点，所述剩余业务节点为所有业务节点中除去所述第一业务节点的节点；
第二获取模块，设置为获取所述待更改业务节点的缓存消息；
判断子模块，设置为判断所述第一业务节点的第一缓存消息是否属于所述第一业务节点的归属中指示的所述第一业务节点的缓存消息；
确定子模块，设置为如果所述第一业务节点的第一缓存消息属于所述第一业务节点的归属中指示的所述第一业务节点的缓存消息，则继续扫描完除去所述第一缓存消息的剩余缓存消息；或者
第一子发送模块，设置为如果所述第一业务节点的第一缓存消息不属于所述第一业务节点的归属中指示的所述第一业务节点的缓存消息，则将所述第一缓存消息转发给归属节点，继续扫描完除去所述第一缓存消息的剩余缓存消息。
实施例十四
本实施例的业务节点的调整装置，可以包括：
第一获取模块，设置为获取更改业务节点的更改指示请求，其中，所述更改指示请求包括携带有待更改业务节点的缓存消息归属的指示信息，所述待更改业务节点包括增加的业务节点或者减少的业务节点；
第一解析子模块，设置为根据所述更改指示请求，确定所述更改指示请求中待更改业务节点为增加的第一业务节点；
第二解析子模块，设置为解析所述指示信息中所述第一业务节点的缓存消息的归属，其中，所述归属为将每个剩余业务节点中预先配置的归属于所述第一业务节点的缓存消息，分配给所述第一业务节点，所述剩余业务节点为所有业务节点中除去所述第一业务节点的节点；
第二获取模块，设置为获取所述待更改业务节点的缓存消息；
判断子模块，设置为判断所述第一业务节点的第一缓存消息是否属于所述第一业务节点的归属中指示的所述第一业务节点缓存消息；
确定子模块，设置为如果所述第一业务节点的第一缓存消息属于所述第一业务节点的归属中指示的所述第一业务节点缓存消息，则继续扫描完除去所述第一缓存消息的剩余缓存消息；或者
第一子发送模块，设置为如果所述第一业务节点的第一缓存消息不属于所述第一业务节点的归属中指示的所述第一业务节点缓存消息，将所述第一缓存消息转发给归属节点，继续扫描完除去所述第一缓存消息的剩余缓存消息；
判断模块，设置为直至判断完成所述第一业务节点的所有缓存消息。
实施例十五
本实施例的业务节点的调整装置，可以包括：
第一获取模块，设置为获取更改业务节点的更改指示请求，其中，所述更改指示请求包括携带有待更改业务节点的缓存消息归属的指示信息，所述待更改业务节点包括增加的业务节点或者减少的业务节点；
第三解析子模块，设置为根据所述更改指示请求，确定所述更改指示请求中待更改业务节点为减少的第二业务节点；
第四解析子模块，设置为解析所述指示信息中所述第二业务节点的缓存消息的归属，其中，所述归属为将所述第二业务节点的缓存消息按照预先配置的归属分配给当前所有剩余业务节点，所述当前所有剩余业务节点为所有业务节点中除去所述第二业务节点的节点；
第二获取模块，设置为获取所述待更改业务节点的缓存消息；
第一处理模块，设置为根据所述待更改业务节点的缓存消息的归属，将不属于所述待更改业务节点的缓存消息，发送给归属节点，其中所述缓存消息按照时标进行排序，所述时标为同一被叫号码传递消息到达短信中心的时间。
实施例十六
本实施例的业务节点的调整装置，可以包括：
第一获取模块，设置为获取更改业务节点的更改指示请求，其中，所述更改指示请求包括携带有待更改业务节点的缓存消息归属的指示信息，所述待更改业务节点包括增加的业务节点或者减少的业务节点；
第三解析子模块，设置为根据所述更改指示请求，确定所述更改指示请求中待更改业务节点为减少的第二业务节点；
第四解析子模块，设置为解析所述指示信息中所述第二业务节点的缓存消息的归属，其中，所述归属为将所述第二业务节点的缓存消息按照预先配置的归属分配给当前所有剩余业务节点，所述当前所有剩余业务节点为所有业务节点中除去所述第二业务节点的节点；
第二获取模块，设置为获取所述待更改业务节点的缓存消息；
交互子模块，设置为根据所述更改指示请求，产生停止所述第二业务节点发送待处理缓存消息的指令，并接收第一响应消息，其中所述第一响应消息为在获取所述更改指示请求之前发送的缓存消息是否发送成功的响应；
第五解析子模块，设置为在接收到所述第一响应消息之后，将所述第二业务节点中存储的所有话单文件转储，并确定所述第二业务节点的全部响应 消息中所有未发送成功的缓存消息；
第二发送子模块，设置为根据所述更改指示请求的配置，将所述第二业务节点所有未发送成功的缓存消息发送给归属节点，其中所述全部响应消息包括所述第一响应消息。
实施例十七
如图6所示，本实施例的业务节点的调整装置，可以包括：
第三获取模块61，设置为获取变更待更改业务节点的第一更改请求，其中所述待更改业务节点包括增加的业务节点或者减少的业务节点；
第四获取模块62，设置为在所述待更改业务节点执行上一个更改指示请求结束时，针对所述第一更改请求，获取所有业务节点归属的变更信息，其中所述上一个更改指示请求包括携带有所述待更改业务节点的缓存消息归属的指示信息，所述缓存消息按照时标进行排序，所述时标为同一被叫号码传递消息到达短信中心的时间；
第二处理模块63，设置为根据所有业务节点归属的变更信息，生成并发送一个更改指示请求，其中所述更改指示请求包括携带有所述待更改业务节点缓存消息归属的指示信息。
本发明实施例中，通过第三获取模块61获取变更待更改业务节点的第一更改请求，判断待更改业务节点完成上一个更改指示请求之后，经第二处理模块63生成并发送一个更改指示请求，从而通过生成指示请求的归属，保证了消息发送的准确性，这样自适应的应对短信业务流量的变化，并保证增加业务节点或者删除业务节点号码不影响消息的处理，只需要增加业务节点按照线程传送消息；在业务开局时，不需要考虑业务的最大流量，只需要安装配置业务运行的最小节点数，减少了开局时的工程规划和部署工作量，实现了业务的快速部署。
需要说明的是，本发明实施例提供的装置是对应的上述业务节点的调整方法的装置，则上述业务节点的调整方法的所有实施例均适用于该装置，且均能达到相同或相似的有益效果。
实施例十八
本实施例的业务节点的调整装置，可以包括：
第三获取模块，设置为获取变更待更改业务节点的第一更改请求，其中所述待更改业务节点包括增加的业务节点或者减少的业务节点；
生成模块，设置为在所述待更改业务节点执行上一个更改指示请求未结束时，生成拒绝响应所述第一更改请求的消息；
第四获取模块，设置为在所述待更改业务节点执行结束上一个更改指示请求时，针对所述第一更改请求，获取所有业务节点归属的变更信息，其中所述上一个更改指示请求包括携带有所述待更改业务节点的缓存消息归属的指示信息，所述缓存消息按照时标进行排序，所述时标为同一被叫号码传递消息到达短信中心的时间；
第二处理模块，设置为根据所有业务节点归属的变更信息，生成并发送一个更改指示请求，其中所述更改指示请求包括携带有所述待更改业务节点缓存消息归属的指示信息。
实施例十九
本实施例的业务节点的调整装置，可以包括：
第三获取模块，设置为获取变更待更改业务节点的第一更改请求，其中所述待更改业务节点包括增加的业务节点或者减少的业务节点；
第一生成子模块，设置为在所述待更改业务节点执行上一个更改指示请求结束时，针对所述第一更改请求的待更改业务节点为增加的第一业务节点时，生成一执行所述第一更改请求的通知消息，其中所述通知消息中携带有增加的第一业务节点的节点号及增加的第一业务节点使用的IP；
第一获取子模块，设置为根据所述通知消息，获取所有业务节点中增加的第一的业务节点中缓存消息的归属，并将每个剩余业务节点中预先配置的归属于所述第一业务节点的缓存消息，分配给所述第一业务节点，其中所述剩余业务节点为所有业务节点中除去所述第一业务节点的节点；
第二处理模块，设置为根据所有业务节点归属的变更信息，生成并发送一个更改指示请求，其中所述更改指示请求包括携带有所述待更改业务节点缓存消息归属的指示信息。
实施例二十
本实施例的业务节点的调整装置，可以包括：
第三获取模块，设置为获取变更待更改业务节点的第一更改请求，其中所述待更改业务节点包括增加的业务节点或者减少的业务节点；
第二生成子模块，设置为在所述待更改业务节点执行上一个更改指示请求结束时，针对所述第一更改请求的待更改业务节点为减少的第二业务节点时，生成一执行所述第一更改请求的通知消息，其中所述通知消息中携带有减少的第二业务节点的节点号；
第二获取子模块，设置为根据所述通知消息，获取所有业务节点中缓存消息的归属，并将所述第二业务节点的缓存消息按照预先配置的归属分配给当前所有剩余业务节点，其中所述当前所有剩余业务节点为所有业务节点中除去所述第二业务节点的节点；
第二处理模块，设置为根据所有业务节点归属的变更信息，生成并发送一个更改指示请求，其中所述更改指示请求包括携带有所述待更改业务节点缓存消息归属的指示信息。
实施例二十一
本实施例提供一种业务侧设备，包括上述任一的业务节点的调整装置。
相应的由于本发明实施例的业务节点的调整装置，应用于业务侧设备，因此，本发明实施例还提供了一种业务侧设备，其中，上述业务节点的调整装置的所述实现实施例均适用于该业务侧设备的实施例中，也能达到相同的技术效果。
需要说明的是：将短消息中心的业务节点全部部署到虚拟机上，在业务开局时，按照最小模型的短消息中心进行部署，不需要考虑节假日的最大业务量。
在后续业务侧设备上线后，业务侧设备定时向云管理平台上报KPI(Key performance indicators，关键性能指标)数据(当前的业务量、中央处理器CPU和内存的占用量等)，云管理平台根据KPI数据和配置的调度策略，动态的扩容或者缩容节点，业务侧设备为了保证短消息特殊的下发特性。
还有，具体在增加第一业务节点流程中，业务侧设备新增动态调度管理设备OMM_Agent(Operation and Maintenance Module_Agent，操作维护模块-代理)模块修改过页面的号码归属节点等配置后，业务侧设备会收到OMM_Agent模块发送的增加业务节点请求；最后，在所有节点的缓存处理全部收齐后，通知OMM_Agent增加业务节点处理完成。
另外，在减少第二业务节点流程中，OMM_Agent模块修改过页面的号码归属节点等配置后，业务侧设备会收到OMM_Agent模块发送的减少业务节点请求；最后，在本地话单文件全部被取以后，通知OMM_Agent减少业务节点处理完成。
实施例二十二
本实施例提供一种代理设备，包括如上述任一的业务节点的调整装置。
相应的由于本发明实施例的业务节点的调整装置，应用于代理设备，因此，本发明实施例还提供了一种代理设备，其中，上述业务节点的调整装置的所述实现实施例均适用于该代理设备的实施例中，也能达到相同的技术效果。
需要说明的是：上述代理设备的作用可以包括：业务新增动态调度管理模块OMM_Agent，(Operation and Maintenance Module_Agent，操作维护模块-代理)，主要用于KPI数据采集，和云管理平台的消息交互，业务配置管理、数据同步、和业务之间消息的交互等。
还有，具体的增加业务节点的流程如下：
当满足增加业务节点的条件后，云管理平台通知OMM_Agent业务要新增节点，OMM_Agent首先做鉴权，判断是否可以增加业务节点，如果业务上次的调度任务增加或者减少业务节点还没有结束，则鉴权拒绝。如果鉴权通过，由OMM_Agent判断加节点的节点号(业务号由小到大增加)和业务使用的IP，并将其反馈给云管理平台。云管理平台创建新的虚拟机，将业务使用的IP添加到网卡上。
在虚拟机创建完成正常启动后，调用业务的自动安装程序安装和配置新的节点，安装配置完成后自动启动新的节点，然后通知OMM_Agent新的节 点已经安装完成，OMM_Agent修改页面节点归属策略等相关配置后，同步所有业务节点，同步成功后，OMM_Agent向所有业务节点发送一条调度增加请求消息，业务侧设备收到增加业务节点请求后，扫描本地的所有缓存消息，如果和现有的节点配置策略不同，则将消息转发到用户归属节点的归属线程去。其他节点收到转发的消息后，根据原消息到达短信中心的时标(SCTS)为key进行排序，将消息存储到本节点。
等所有节点缓存消息处理完成后通知前端网元新节点上线，让前端网元分发消息到新节点，这样新的节点就可以承载业务了。
具体的减少业务节点的流程如下：
当满足减少业务节点条件后，云管理平台通知OMM_Agent有业务节点需要下线，类似增加业务节点流程，OMM_Agent首先做鉴权，如果鉴权通过，由OMM_Agent决定下线的节点号(业务号由大到小减少)，通知业务侧设备前端的网元不要再发送消息到这一个节点上。
OMM_Agent修改页面节点归属等配置后，同步所有业务节点，同步成功后，OMM_Agent向待下电节点发送动态减少业务节点请求，业务侧设备收到该请求后，该节点停止所有外发消息，等所有发送缓冲区释放，也就是所有先前发送请求的响应回来后，将内存中的所有话单缓存dump到文件。然后扫描本地的所有缓存消息，将消息转发到归属节点的归属线程去。
业务动态调度时，OMM_Agent在修改完号码归属节点的策略后，向业务节点发一个节点调度通知请求消息，业务节点在自己的缓存队列中进行扫描，如果存在和现有节点归属策略不符的消息，将消息转发到归属节点的归属线程去，从本节点删除；
等缓存消息处理完成后，业务侧设备开始做话单文件定时扫描，如果话单文件全部被取走，则发送需要减少业务节点的虚拟机的ID号给云管理平台，云管理平台停止该业务节点并释放虚拟机，回收资源。
另外，云管理平台若监控到业务侧设备满足增加业务节点的条件，则根据预定的调度策略增加业务节点；若监控到业务侧设备满足减少业务节点的条件，则根据预定的调度策略减少业务节点。上述监控的方法包括：
1、在业务侧设备上线后，OMM_Agent定时到业务性能统计数据库采集KPI数据(当前的业务量、CPU和内存的占用量等)，并向云管理平台上报。
2、云平台配置调度策略，包括业务流量、CPU、内存等参数，如果任一参数超过设置的增加业务节点的阈值，则增加业务节点；如果任一参数小于设置的减少业务节点的阈值，则减少业务节点。
3、为了防止业务瞬时抖动等因素造成的震荡，云管理平台增加步长参数N(N大于等于3)，调度策略要连续满足N次才能触发调度；为了防止将节点数缩减为0，增加业务最少节点数的设置，如果节点数已经小于等于这个阈值，则不再缩减节点。
本发明实施例还提供一种计算机可读存储介质，所述计算机可读存储介质中存储有计算机可执行指令，所述计算机可执行指令被执行时实现业务节点的调整方法。
本领域普通技术人员可以理解上述方法中的全部或部分步骤可通过程序来指令相关硬件(例如处理器)完成，所述程序可以存储于计算机可读存储介质中，如只读存储器、磁盘或光盘等。可选地，上述实施例的全部或部分步骤也可以使用一个或多个集成电路来实现。相应地，上述实施例中的各模块/单元可以采用硬件的形式实现，例如通过集成电路来实现其相应功能，也可以采用软件功能模块的形式实现，例如通过处理器执行存储于存储器中的程序/指令来实现其相应功能。本申请不限制于任何特定形式的硬件和软件的结合。本领域的普通技术人员应当理解，可以对本申请的技术方案进行修改或者等同替换，而不脱离本申请技术方案的精神和范围，均应涵盖在本申请的权利要求范围当中。
工业实用性
上述技术方案保证了增加业务节点或者删除业务节点号码不影响消息的处理，提高了消息发送的准确性。

Claims (14)

  1. 一种业务节点的调整方法，包括：
    获取更改业务节点的更改指示请求，其中，所述更改指示请求包括携带有待更改业务节点的缓存消息归属的指示信息，所述待更改业务节点包括增加的业务节点或者减少的业务节点；
    根据所述更改指示请求，解析所述指示信息中所述待更改业务节点的缓存消息的归属；
    获取所述待更改业务节点的缓存消息；
    根据所述待更改业务节点的缓存消息的归属，将不属于所述待更改业务节点的缓存消息发送给归属节点，其中所述缓存消息按照时标进行排序，所述时标为同一被叫号码传递消息到达短信中心的时间。
  2. 根据权利要求1所述的业务节点的调整方法，其中，所述根据所述更改指示请求，解析所述指示信息中所述待更改业务节点的缓存消息的归属，包括：
    根据所述更改指示请求，确定所述更改指示请求中待更改业务节点为增加的第一业务节点；
    解析所述指示信息中所述第一业务节点的缓存消息的归属，其中，所述归属为将每个剩余业务节点中预先配置的归属于所述第一业务节点的缓存消息分配给所述第一业务节点，所述剩余业务节点为所有业务节点中除去所述第一业务节点的节点。
  3. 根据权利要求2所述的业务节点的调整方法，其中，所述根据所述待更改业务节点的缓存消息的归属，将不属于所述待更改业务节点的缓存消息发送给归属节点，包括：
    判断所述第一业务节点的第一缓存消息是否属于所述第一业务节点的归属中指示的所述第一业务节点的缓存消息；
    如果所述第一业务节点的第一缓存消息属于所述第一业务节点的归属中指示的所述第一业务节点缓存消息，则继续扫描完除去所述第一缓存消息的剩余缓存消息；或者
    如果所述第一业务节点的第一缓存消息不属于所述第一业务节点的归属中指示的所述第一业务节点的缓存消息，则将所述第一缓存消息转发给归属节点，继续扫描完除去所述第一缓存消息的剩余缓存消息。
  4. 根据权利要求3所述的业务节点的调整方法，所述方法还包括：直至判断完成所述第一业务节点的所有缓存消息。
  5. 根据权利要求1所述的业务节点的调整方法，其中，所述根据所述更改指示请求，解析所述指示信息中所述待更改业务节点的缓存消息的归属，包括：
    根据所述更改指示请求，确定所述更改指示请求中待更改业务节点为减少的第二业务节点；
    解析所述指示信息中所述第二业务节点的缓存消息的归属，其中，所述归属为将所述第二业务节点的缓存消息按照预先配置的归属分配给当前所有剩余业务节点，所述当前所有剩余业务节点为所有业务节点中除去所述第二业务节点的节点。
  6. 根据权利要求5所述的业务节点的调整方法，其中，所述根据所述待更改业务节点的缓存消息的归属，将不属于所述待更改业务节点的缓存消息，发送给归属节点，包括：
    根据所述更改指示请求，产生停止所述第二业务节点发送待处理缓存消息的指令，并接收第一响应消息，其中所述第一响应消息为在获取所述更改指示请求之前发送的缓存消息是否发送成功的响应；
    在接收到所述第一响应消息之后，将所述第二业务节点中存储的所有话单文件转储，并确定所述第二业务节点的全部响应消息中所有未发送成功的缓存消息；
    根据所述更改指示请求的配置，将所述第二业务节点所有未发送成功的缓存消息发送给归属节点，其中所述全部响应消息包括所述第一响应消息。
  7. 一种业务节点的调整方法，包括：
    获取变更待更改业务节点的第一更改请求，其中所述待更改业务节点包括增加的业务节点或者减少的业务节点；
    在所述待更改业务节点执行上一个更改指示请求结束时，针对所述第一更改请求，获取所有业务节点归属的变更信息，其中所述上一个更改指示请求包括携带有所述待更改业务节点的缓存消息归属的指示信息，所述缓存消息按照时标进行排序，所述时标为同一被叫号码传递消息到达短信中心的时间；
    根据所有业务节点归属的变更信息，生成并发送一个更改指示请求，其中所述更改指示请求包括携带有所述待更改业务节点的缓存消息归属的指示信息。
  8. 根据权利要求7所述的业务节点的调整方法，所述方法还包括：所述获取变更待更改业务节点的第一更改请求之后，在所述待更改业务节点执行上一个更改指示请求未结束时，生成拒绝响应所述第一更改请求的消息。
  9. 根据权利要求7或8所述的业务节点的调整方法，其中，在所述待更改业务节点执行上一个更改指示请求结束时，针对所述第一更改请求，获取所有业务节点归属的变更信息，包括：
    在所述待更改业务节点执行上一个更改指示请求结束时，针对所述第一更改请求的待更改业务节点为增加的第一业务节点时，生成一执行所述第一更改请求的通知消息，其中所述通知消息中携带有增加的第一业务节点的节点号及增加的第一业务节点使用的互联网协议IP地址；
    根据所述通知消息，获取所有业务节点中缓存消息的归属，并将每个剩余业务节点中预先配置的归属于所述第一业务节点的缓存消息，分配给所述第一业务节点，其中所述剩余业务节点为所有业务节点中除去所述第一业务节点的节点。
  10. 根据权利要求7或8所述的业务节点的调整方法，其中，所述在所述待更改业务节点执行上一个更改指示请求结束时，针对所述第一更改请求，获取所有业务节点归属的变更信息，包括：
    在所述待更改业务节点执行上一个更改指示请求结束时，针对所述第一更改请求的待更改业务节点为减少的第二业务节点时，生成一执行所述第一更改请求的通知消息，其中所述通知消息中携带有减少的第二业务节点的节点号；
    根据所述通知消息，获取所有业务节点中缓存消息的归属，并将所述第二业务节点的缓存消息按照预先配置的归属分配给当前所有剩余业务节点，其中所述当前所有剩余业务节点为所有业务节点中除去所述第二业务节点的节点。
  11. 一种业务节点的调整装置，包括：
    第一获取模块，设置为获取更改业务节点的更改指示请求，其中，所述更改指示请求包括携带有待更改业务节点的缓存消息归属的指示信息，所述待更改业务节点包括增加的业务节点或者减少的业务节点；
    解析模块，设置为根据所述更改指示请求，解析所述指示信息中所述待更改业务节点的缓存消息的归属；
    第二获取模块，设置为获取所述待更改业务节点的缓存消息；
    第一处理模块，设置为根据所述待更改业务节点的缓存消息的归属，将不属于所述待更改业务节点的缓存消息，发送给归属节点，其中所述缓存消息按照时标进行排序，所述时标为同一被叫号码传递消息到达短信中心的时间。
  12. 一种业务节点的调整装置，包括：
    第三获取模块，设置为获取变更待更改业务节点的第一更改请求，其中所述待更改业务节点包括增加的业务节点或者减少的业务节点；
    第四获取模块，设置为在所述待更改业务节点执行上一个更改指示请求结束时，针对所述第一更改请求，获取所有业务节点归属的变更信息，其中所述上一个更改指示请求包括携带有所述待更改业务节点的缓存消息归属的指示信息，所述缓存消息按照时标进行排序，所述时标为同一被叫号码传递消息到达短信中心的时间；
    第二处理模块，设置为根据所有业务节点归属的变更信息，生成并发送一个更改指示请求，其中所述更改指示请求包括携带有所述待更改业务节点的缓存消息归属的指示信息。
  13. 一种业务侧设备，包括如权利要求11所述的业务节点的调整装置。
  14. 一种代理设备，包括如权利要求12所述的业务节点的调整装置。
PCT/CN2016/086926 2015-08-28 2016-06-23 一种业务节点的调整方法、装置及设备 WO2017036238A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510541424.3A CN106487555A (zh) 2015-08-28 2015-08-28 一种业务节点的调整方法、装置及设备
CN201510541424.3 2015-08-28

Publications (1)

Publication Number Publication Date
WO2017036238A1 true WO2017036238A1 (zh) 2017-03-09

Family

ID=58186544

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/086926 WO2017036238A1 (zh) 2015-08-28 2016-06-23 一种业务节点的调整方法、装置及设备

Country Status (2)

Country Link
CN (1) CN106487555A (zh)
WO (1) WO2017036238A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109246051A (zh) * 2017-05-22 2019-01-18 中兴通讯股份有限公司 灰度发布后链路管理方法、装置、存储介质和计算机设备
WO2019179633A1 (en) 2018-03-23 2019-09-26 Telefonaktiebolaget Lm Ericsson (Publ) Message cache management in a mesh network
CN112764893B (zh) * 2019-11-04 2024-03-26 华为技术有限公司 数据处理方法和数据处理系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101350960A (zh) * 2008-08-12 2009-01-21 华为技术有限公司 基于msc池的负载迁移方法、系统和设备
CN101605308A (zh) * 2009-03-05 2009-12-16 上海闻泰电子科技有限公司 一种短消息的管理方法
CN102143563A (zh) * 2010-07-30 2011-08-03 华为技术有限公司 一种短信中心集群的控制方法、设备及系统
US8607014B2 (en) * 2009-12-22 2013-12-10 At&T Intellectual Property I, L.P. Multi-autonomous system anycast content delivery network
CN103561428A (zh) * 2013-10-10 2014-02-05 东软集团股份有限公司 短信网关集群系统中的节点弹性分配方法及系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101350960A (zh) * 2008-08-12 2009-01-21 华为技术有限公司 基于msc池的负载迁移方法、系统和设备
CN101605308A (zh) * 2009-03-05 2009-12-16 上海闻泰电子科技有限公司 一种短消息的管理方法
US8607014B2 (en) * 2009-12-22 2013-12-10 At&T Intellectual Property I, L.P. Multi-autonomous system anycast content delivery network
CN102143563A (zh) * 2010-07-30 2011-08-03 华为技术有限公司 一种短信中心集群的控制方法、设备及系统
CN103561428A (zh) * 2013-10-10 2014-02-05 东软集团股份有限公司 短信网关集群系统中的节点弹性分配方法及系统

Also Published As

Publication number Publication date
CN106487555A (zh) 2017-03-08

Similar Documents

Publication Publication Date Title
CN109120426B (zh) 一种网络切片管理方法、装置及计算机可读存储介质
JP6881575B2 (ja) 資源割当システム、管理装置、方法およびプログラム
Abu et al. Interest packets retransmission in lossy CCN networks and its impact on network performance
WO2017036238A1 (zh) 一种业务节点的调整方法、装置及设备
WO2021109750A1 (zh) 节点管理方法、装置、设备、存储介质和系统
WO2021000379A1 (zh) 一种网络数据调度方法及边缘节点
CN110727507B (zh) 一种消息的处理方法、装置、计算机设备和存储介质
CN112965839A (zh) 消息传输方法、装置、设备及存储介质
CN110855424B (zh) 一种DPI领域非对称流量xDR合成的方法和装置
CN115086250A (zh) 一种网络靶场分布式流量发生系统与方法
CN111586140A (zh) 一种数据交互的方法及服务器
US9893972B1 (en) Managing I/O requests
US11606415B2 (en) Method, apparatus and system for processing an access request in a content delivery system
CN108632568B (zh) 回看监控视频的方法、装置、电子设备和可读存储介质
WO2017215415A1 (zh) 一种资源控制方法、装置和iptv服务器
US11700189B2 (en) Method for performing task processing on common service entity, common service entity, apparatus and medium for task processing
CN107846476B (zh) 一种信息同步方法、设备及存储介质
CN109005465A (zh) 弹幕消息分发方法、装置、设备及存储介质
CN110620811B (zh) 一种vOLT集群架构下ONU管理方法及系统
WO2017193798A1 (zh) 一种垃圾信息监控方法、装置及通信系统
CN113687962A (zh) 一种请求处理方法、装置、设备及存储介质
CN107995264B (zh) 一种基于消息队列的cdn服务验证码分发方法和系统
CN113691830B (zh) 一种视频流缓存方法及相关装置
CN111314347A (zh) 一种非法流量的处理方法、装置、系统和存储介质
CN115665042B (zh) 数据处理方法、装置、用户平面功能实体及存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16840667

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16840667

Country of ref document: EP

Kind code of ref document: A1