WO2012013057A1 - 一种短信中心集群的控制方法、设备及*** - Google Patents
一种短信中心集群的控制方法、设备及*** Download PDFInfo
- Publication number
- WO2012013057A1 WO2012013057A1 PCT/CN2011/073709 CN2011073709W WO2012013057A1 WO 2012013057 A1 WO2012013057 A1 WO 2012013057A1 CN 2011073709 W CN2011073709 W CN 2011073709W WO 2012013057 A1 WO2012013057 A1 WO 2012013057A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- node device
- short message
- center cluster
- state
- message center
- Prior art date
Links
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]
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks
Definitions
- the present invention relates to the field of communication technologies, and in particular, to a method, device and system for controlling a short message center cluster. Background technique
- SMSC (Shor t me s s s serv ce center ) is a communication device for processing SMS (SMS, Sor t mes sage serv i ce ). After the SMS is submitted to the SMS center, the SMS center will submit the submitted SMS. If the SMS fails to be delivered, the SMS will be cached in the SMS center to wait for a certain period of time before resending.
- the SMS center usually also carries a number of SMS value-added services, which require the SMS Center to work with peripheral components to complete several interactions.
- the SMS center system is usually configured according to the software and hardware conditions required for traffic peak traffic, but in most of the daily life. The amount of short message traffic in time is much lower than the peak traffic, so the continuous operation of the SMS center equipment hardware will cause energy waste to a large extent. Summary of the invention
- Embodiments of the present invention provide a method, a device, and a system for controlling a short message center cluster, which realize energy saving and consumption reduction of the existing short message center system.
- the embodiment of the invention provides a method for controlling a short message center cluster, and the technical solution includes: acquiring state information of each node device in the short message center cluster;
- the embodiment of the invention provides a control device, and the technical solution includes:
- the obtaining module is configured to obtain state information of each node device in the short message center cluster, and the control module is configured to adjust, according to the state information, the number of node devices in the short message center cluster that are in a working state.
- An embodiment of the present invention provides a short message center cluster system, including an access device and at least two node devices;
- the access device is configured to receive a short message, and allocate the short message to a corresponding available node device for processing according to a predetermined routing rule;
- the node device is configured to process a short message service, and report its own state information to the control device, and receive a control instruction issued by the control device according to the state information, and when the control indication is a sleep indication, The state transitions to a sleep state; when the control indicates a wakeup indication, it transitions itself from a sleep state to a control state.
- An embodiment of the present invention provides a short message center cluster control system, including:
- the control device is configured to obtain state information of each node device in the SMS center cluster system, and adjust the number of node devices in the short message center cluster according to the state information; the SMS center cluster system is configured to process the short message service And reporting the status information of each node device to the control device, and receiving, by the control device, a control instruction for adjusting the number of node devices according to the status information, and when the control indication is a sleep indication, Transitioning from a working state to a sleep state; when the control indicates a wakeup indication, transitioning itself from a sleep state to a control state.
- the working state of the node device is managed under the premise of ensuring the normal processing of the short message center service, and the SMS center cluster is adjusted according to the actual load of the short message center cluster.
- the number of working state node devices greatly reduces the energy saving of the short message center.
- FIG. 1 is a flowchart of a method for controlling a short message center cluster according to an embodiment of the present invention
- FIG. 2 is a schematic structural diagram of a short message center cluster system according to an embodiment of the present invention
- FIG. 3 is a schematic structural diagram of a short message center cluster system according to an embodiment of the present invention
- FIG. 4 is a schematic structural diagram of a control device according to an embodiment of the present invention
- FIG. 5 is a schematic structural diagram of a control device according to an embodiment of the present disclosure.
- FIG. 6 is a schematic structural diagram of a short message center cluster control system according to an embodiment of the present invention
- FIG. 7 is an application scenario diagram of a short message center service processing part according to an embodiment of the present invention
- FIG. 8 is a flowchart of an application of a control device to control a sleep of a short message center node device according to an embodiment of the present invention
- FIG. 9 is a flowchart of an application of a control device to control wake-up of a short message center node device according to an embodiment of the present invention
- FIG. 10 is a flowchart of a control device according to an embodiment of the present invention.
- the number of node devices in the short message center cluster in the working state is controlled according to the overall load of the short message center cluster and the busy state of the single node device, thereby implementing non-service in the short message center. Energy saving at peak times.
- FIG. 1 is a schematic diagram of a method for controlling a short message center cluster according to an embodiment of the present invention.
- the present embodiment is described in the perspective of a control device, and the method may include:
- Step 101 The control device acquires the state information of each node device in the SMS center cluster.
- the node device of the SMS center cluster has the short message processing capability of the short message center, and is used for processing the short message.
- the control device uses the communication mode of the timed or real-time interaction to obtain the state information of each node device, where the state information may include the current traffic of the node device and the busy state of the node device; the busy state of the node device may include the software busy state.
- the hardware is busy and idle state;
- the software busy state can be determined by the software busy index of the message processing center node device currently processing message traffic, the number of cached messages, etc.;
- the hardware busy state can pass system CPU usage, memory occupancy rate, network
- the hardware busyness indicators such as the bandwidth usage and the temperature are determined.
- the node device in the SMS center cluster can obtain the hardware busyness indicator of the device by calling the operating system AP I.
- the node device can report its own state information to the control device through the interaction interface with the control device, where the node device can be actively reported or the device can be queried.
- Step 102 The control device adjusts the number of node devices in the short message center cluster according to the status information.
- control device may adjust the number of the node devices in the short message center cluster according to the overall load of the short message center cluster and the busy state of each node device, and the specific process may include: The current traffic of the node device determines the overall load of the SMS center cluster; if the overall load of the SMS center cluster is light, the relatively idle node device is determined according to the busy state of each node device, and the relatively idle node device is indicated to be converted from the working state. If the overall load of the SMS center cluster is heavy, the node device in the sleep state is changed from the sleep state to the working state.
- the busy state reported by each node device may be represented by different levels of busy flags (eg, 0, idle; 1, normal; 2, busy; 3, near limit), in order to control
- the device can directly determine which node devices can sleep according to the received busy identifier, and which node devices can be woken up.
- the number of the working node devices in the short message center cluster is adjusted according to the actual load of the short message center cluster, so that when the actual traffic volume of the short message center cluster is low, some node devices can be put into a dormant state.
- the energy saving and consumption reduction of the SMS center cluster system is realized.
- determining the overall load of the short message center cluster according to the current traffic of each node device may include: calculating overall traffic of the short message center cluster according to current traffic of each node device; when the overall traffic of the short message center cluster is far smaller than the short message center cluster The overall load of the SMS center cluster is light; when the overall traffic of the SMS center cluster is close to the processing capacity of the SMS center cluster; determining the overall load of the SMS center cluster; wherein, the distance is less than and close It is determined by a preset threshold, for example, a first threshold for judging "far less than” and a second threshold for judging "close” are respectively set, when the calculated overall flow of the SMS center cluster is The absolute value of the difference between the traffic that can be processed by the SMS center cluster is less than the first threshold.
- a preset threshold for example, a first threshold for judging "far less than” and a second threshold for judging "close” are respectively set, when the calculated overall flow of the SMS center cluster is The absolute value of the difference between the traffic that can be processed by
- the overall traffic of the SMS center cluster is much smaller than the processing capacity of the SMS center cluster.
- the calculated overall traffic of the SMS center cluster and the SMS center cluster can be The absolute value of the difference of the processed traffic is greater than the second threshold, then Letter overall traffic handling capacity near the center of the cluster of cluster message center; wherein the first width is smaller than the second width value, both of which can be set according to experience.
- the control device may send a message to the relatively idle node device.
- Sleep notification message to indicate that the relatively idle node device is switched from the working state to the sleep state, wherein the sleep notification message can be used to control the relatively idle node device to invoke an operating system API (Application Programming Interface) Sleep operation;
- the control device can wake up the sleeping node device through the remote control mechanism.
- control device may further perform control processing on the subsequent short message sent to the sleeping node device. Specifically, after the node device is switched from the working state to the dormant state, the sleeping node device is deleted from the available node device; or, after the node device transitions from the sleeping state to the working state, the node is converted into the working state. The device is added to the available node device to ensure that the message accessing the SMS center is allocated to the available node device for processing.
- the control device may also control the node device in the current short message center cluster to obtain and process the cached short message generated by the sleepy node device after the node device is switched from the working state to the dormant state, and cache the short message.
- the storage path is a path accessible by all node devices in the SMS center cluster.
- the cached short message may be generated by the node device failing to be delivered before being hibernated.
- the embodiment of the invention provides that the short message routing rule is modified by the control device, and the short message that is supposed to be routed to the sleepy node is allocated to the node device in the current short message center cluster to be processed, thereby ensuring timely processing of the short message. .
- the embodiment of the present invention when there is a node device in the SMS center cluster, the embodiment of the present invention also proposes a corresponding processing strategy for the node device to cache the short message before the sleep, and the control device acquires and controls the node device in the working state of the short message center cluster system.
- the cached short message generated by the sleepy node is processed to ensure timely processing of the cached short message generated by the sleepy node device. As shown in FIG.
- the short message center in the embodiment of the present invention uses a cluster networking mode, and the short message center cluster system includes an access device 22 and at least two node devices 21 (node 1 and node 2);
- the access device and the node device may be a simplified short message center, the access device implements the function of the short message center to access the short message, and the node device implements the function of the short message center to process the short message service.
- the access device is configured to receive the short message, and allocate the short message to the corresponding available node device for processing according to a predetermined routing rule.
- the node device is configured to process the short message service, and is used for reporting the status information of the control device to the control device, and receiving the control instruction issued by the control device according to the status information.
- the control indication is the sleep indication
- the node is converted from the working state to the sleep state;
- the control indication is a wake-up indication, it switches itself from the sleep state to the control state.
- the access device may have one or more.
- two access devices may be configured to receive the short message from the SS7 protocol interface of the signaling network and receive the SMPP protocol from the IP network. SMS of the interface.
- the access device can adjust the short message route according to the working state change of the node device.
- the specific adjustment process may be: after the node device is changed from the working state to the dormant state, the sleeping node device is deleted from the available node device; or, after the node device transitions from the sleeping state to the working state, the device is converted into the working state.
- the node device is added to the available node device.
- each node device in the short message center cluster system can report its own state information to the control device by using a communication mode in a timed or real-time interaction manner, where the state information may include the current traffic of the node device and the busyness of the node device.
- Status; node device busy status includes software busy The idle state and the hardware busy state; the software busy state can be determined by the software busy index of the message processing center node device currently processing the message traffic, the number of cached messages, etc.; the hardware busy state parameter can pass the system CPU usage, memory occupancy The rate, network bandwidth occupancy, temperature, etc. are determined by the hardware busyness indicator.
- the node device of the short message center cluster can obtain the hardware busy idle indicator of the device by calling the operating system API.
- the node device can report its own state information to the control device through the interaction interface with the control device, where the node device can be actively reported or the device can be queried.
- the node device in the short message center cluster system can change itself from the working state to the sleep state by calling the operating system API.
- the node device can also Further disconnect the peripheral device and clear the temporary data inside the program.
- the node device in the SMS center cluster system is changed from the sleep state to the working state, which can be implemented by remote control of the control device.
- the control device can trigger the node device through the power controller on the node device motherboard. After the operating system enters the working state, after the operating system enters the working state, the node device application re-initializes and establishes an interface with peripheral components to complete the wake-up work.
- the cached data of each node device may be separated from the service processing process, so that each node device of the short message center and the cached short message are used. There is a loose coupling relationship between them.
- the short message center cluster system may further include:
- the cache processing device 23 is configured to: after the node device is converted to the sleep state, read back the cached short message generated by the sleepy node device before the sleep, and allocate the cached short message to the node device in the working state.
- the cache processing device is logically separated from the processing of the node device, and can also be physically set independently of the node device.
- the cache processing device may be one or more, and the cache processing device and the node device may be in a many-to-many relationship; after failing to send the short message, the node device may send the failed delivery short message to any cache processing device, and notify the The cache processing device reads back the time of the short message, and the cache processing device caches the short message into a storage device that can be accessed by all the cache processing devices.
- the storage device can be a disk, a hard disk, or the like.
- the cache processing device reads back the short message from the storage device, and sends the short message to any available node device in the short message center cluster system for retransmission.
- the access device, the node device, and the cache processing device in the embodiment of the present invention may all be a computer, where the access device and the node device may be located in the same physical entity.
- the embodiment of the present invention provides a schematic diagram of a control device in the perspective of a control device.
- the control device includes :
- the obtaining module 41 is configured to obtain state information of each node device in the short message center cluster, and the control module 42 is configured to adjust, according to the state information, the number of node devices in the short message cluster that are in a working state.
- the status information may include: a current traffic of the node device and a busy state of the node device; wherein, the busy state of the node device may be determined by a software busy state and a hardware busy state, specifically For the implementation, refer to the description in the embodiment shown in FIG. 1 above.
- control device of the embodiment of FIG. 4 may further include the functional modules of FIG. 5, wherein the control module 42 may specifically include:
- a determining unit 421, configured to determine, according to current traffic of each node device, the short message center cluster Overall load
- the selecting unit 422 is configured to determine, according to the busy state of each node device, a relatively idle node device when the overall load of the SMS center cluster is light;
- the indicating unit 423 is configured to: when the determining unit determines that the overall load of the short message center cluster is light, indicating that the relatively idle node device is switched from the working state to the dormant state; when the determining unit determines that the overall weight of the short message center cluster is heavy, The node device indicating the sleep state is switched from the sleep state to the active state.
- the determining unit 421 may include:
- a calculating subunit 4211 configured to calculate an overall traffic of the short message center cluster according to current traffic of each node device
- the comparison subunit 4212 is configured to compare the overall traffic of the short message center cluster with the processing capability of the short message center cluster. When the overall traffic of the short message center cluster is far less than the processing capability of the short message center cluster, determine the short message center cluster.
- the overall load is light; when the overall traffic of the SMS center cluster is close to the processing capability of the SMS center cluster; determining the overall load of the SMS center cluster; the far less than and close can be determined by a preset threshold.
- the indicating unit 423 is specifically configured to:
- control device may further include:
- the routing module 43 is configured to: after the node device is switched from the working state to the dormant state, delete the sleeping node device from the available node device; or, after the node device transitions from the sleeping state to the working state, the node device is converted into the working state. The node device is added to the available node device.
- control device provided by the embodiment of the present invention can modify the short message routing rule by the routing module, and directly allocate the short message that should be routed to the sleeping node device to the available node device in the working state of the current short message center cluster;
- the SMS routing rule can also be modified by controlling the access device in the SMS center cluster system, and the short message route that should be routed to the sleeping node device is allocated to the available node device in the working state of the current short message center cluster.
- control device may further include:
- the cache processing module 44 is configured to: after the node device is switched from the working state to the dormant state, control the node device in the current short message center cluster to acquire and process the cached short message generated by the sleeping node device; the storage path of the cached short message is A path accessible by all node devices in the SMS center cluster.
- routing module and the cache processing module are optional, and the function of the routing module can also be implemented in the access device of the short message center cluster system, and the cache processing module can also be implemented in the cache processing device of the short message center cluster system. .
- the control device in the embodiment of the present invention may be a computer, and each functional unit in the control device can be operated in the CPU.
- a short message center cluster control system provided by the present invention may include:
- the control device 61 is configured to acquire state information of each node device in the short message center cluster system, and adjust the number of node devices in the short message center cluster according to the state information; the short message center cluster system 62 is configured to process the short message service. And reporting, to the control device, status information of each node device, and receiving, by the control device, a control instruction for adjusting the number of node devices according to the status information, and when the control indication is a sleep indication, converting itself from the working state to the sleep state; When the control indication is a wake-up indication, it transitions itself from a sleep state to a control state.
- the SMS center cluster system For the specific implementation of the SMS center cluster system, reference may be made to the embodiment shown in FIG. 2 and FIG. 3 .
- the control device reference may be made to the embodiments shown in FIG. 4 and FIG. 5 , and details are not described herein again.
- the technical solutions described in the embodiments of the present invention are described in detail by using specific embodiments, and the nodes in the working state of the short message center cluster are adjusted by monitoring the state information of each node device in the short message center cluster. The number of devices, so as to ensure the normal operation of the SMS center business, the energy saving and consumption reduction of the SMS center system is realized.
- the SMS center cluster includes an access layer, an access layer, and a service layer, and an access device in the short message center cluster.
- the 3rd Party Service Access Module responsible for third-party service access and the Signal Access Module responsible for signaling SS7 access are located in Access.
- Layer the SMS App is the node device in the SMS center cluster system
- Storage is the cache processing device in the SMS center cluster
- the SMS App and Storage are located in the Service Layer.
- the storage device may be independently set in each node device, or may be independently set in each node device, but the storage path of the cached short message is a path accessible by all node devices in the short message center cluster, so that the node has a node.
- the Control Module is a control device that can be set in the Service Layer of the short message cluster system.
- the SMS App is responsible for the processing of the short message service, and the storage is responsible for the access of the cached message (specifically, the cached data is stored in the Disk Array shown in FIG. 7 , and the storage path of the cached short message in the Disk Array can be accessed by each Storage module in the short message center cluster;
- the Access Layer includes: a 3rd Party Service Access Module that is responsible for accessing the SMS center set of the third-party service, and is connected to each App node in the SMS center cluster through the Smpp protocol; and is responsible for accessing the SMS Center to the Signal Access Module of the core network through the SS7. Connected to the node device in the SMS center cluster;
- the Control Module monitors the status information of each node in the SMS center and controls the running status of each node in the SMS center. It changes from the working state to the sleep state or from the sleep state to the working state.
- the following specific processes are mainly divided into a process in which the control device sleeps the idle node of the short message center, and a process in which the control device wakes up the sleepy node device (that is, converts the device in the sleep state into a working state), and the specific content will be It is detailed in the corresponding process.
- control device is described as sleeping a relatively idle node device in the short message center cluster.
- the Access Module submits the received short message to each SMS App according to a predetermined rule
- the 3rd party access module receives the short message sent by the third party service to the short message center, and receives the short message sent by the core network to the short message center through the Signal Access module;
- the predetermined rule refers to a shunting rule submitted by the message
- the general short message center supports shunting to different SMSApps according to the number segment of the calling number or according to the ending number of the called number.
- the SMS App first delivers the short message sent by the Access Module. If the delivery fails, the storage is cached in the Disk Array.
- the SMS App and the Control Module communicate with each other through a TCP/IP long connection.
- the SMS App periodically reports the status information of the device to the Control Module.
- the status information includes the current traffic of the current single node device and the node.
- the busy state of the device wherein the busy state of the node device includes the software busy state and the hardware busy state; the software busy state can be determined by the software busy state indicator such as the traffic of the message center node device currently processing the message, the cached message traffic, and the like.
- the hardware busy state can be determined by hardware busyness indicators such as system CPU usage, memory usage, network bandwidth usage, and temperature.
- the short message center node device can obtain the hardware busy state of the device by calling the operating system AP I.
- the busy state of the node device may be represented by different busy indicators, such as: 0, idle; 1, normal; 2, busy; 3, close to the limit, so that the control device directly idles the node device. The status is identified.
- the control module calculates the overall load of the current short message center cluster according to the status information reported by the node device. Specifically, the control module determines the overall load of the current short message center cluster by accumulating according to the current traffic processing of each node device. When the overall traffic of the short message center cluster is far less than the processing capability of the short message center cluster, determining the short message center cluster The overall load is light, and the relatively idle node device is determined according to the busy state of each node device, and the relatively idle node device is changed from the working state to the dormant state;
- the overall traffic of the short message center cluster is close to the processing capability of the short message center cluster, determining that the overall load of the short message center cluster is heavy, and indicating that the node device in the sleep state is switched from the sleep state to the working state;
- the proximity can be determined by a preset threshold, and the specific comparison process can refer to the embodiment shown in FIG. 1.
- the overall traffic of the short message center cluster is far less than the processing capacity of the short message center cluster as an example.
- the Control Module sends an indication that the SMS App goes to sleep through a TCP/IP interface to a relatively idle SMS App.
- the SMS App receives the sleep notification and enters a sleep state.
- the SMS App disconnects the interface with the peripheral module, and clears the temporary data inside the program, and enters the sleep state by calling the API of the operating system; because the SMS App only processes the service, the cache Both the short message and the session index information are stored in the storage module that is set separately from the node device. Therefore, after the SMS App node enters the hibernation state, other SMS applications can continue to process the cached short message and the session without affecting the subsequent normal processing of the short message.
- the access device can adjust the short message routing according to the working state change of the node device.
- the specific adjustment process may be: when the node device is switched from the working state to the dormant state, The sleep node device is deleted from the available node device; or, after the node device transitions from the sleep state to the working state, the node device converted to the working state is added to the available node device.
- the short message from the SS7 protocol interface of the signaling network and the Smpp protocol interface of the IP network are accessed and distributed through the Access Module, in order to ensure the access.
- the short message sent by the Module to the sleeping node device according to the initial routing rule can be processed in time, and the available node device that is currently in the working state can be displayed in the form of a list.
- the SMS App node When the SMS App node is monitored to enter the working state by the sleep state, the The SMS App node joins the list of available node devices.
- the node device When it is detected that the SMS App node device enters the sleep state from the working state, the node device is deleted from the list of available node devices, and the access device can The manner in which polling is evenly distributed between node devices currently in working state ensures the load balancing of available node devices.
- the SMS App2 After receiving the message that the Access Module distributes to the SMS App1, the SMS App2 delivers the message according to the normal processing flow of the message, and then passes the storage cache after the failure;
- the service processing process and the cache data are physically and logically separated in order to ensure that the change of the working state of the SMS App does not affect the processing of the cached short message by the sleepy node.
- the SMS App is responsible for delivering the short message, sending the failure to the Storage module cache, and setting the readback time of the cached SMS on the Storage, so that the SMS App resends the cached SMS; responsible for receiving the cached SMS message distributed from the SMS App and saving it to disk for persistence.
- the Storage will read the cached SMS from the disk and send it to any node available in the SMS App cluster. Resend.
- SMS Appl is in a dormant state, in order to ensure that its cached SMS arrives at the time of readback
- the control module can be re-sent in time, and the Control Module controls the storage module to control the acquired routing rules of the read-back text message to distribute the SMS App1 back-reading SMS to the currently working SMS App.
- SMS App2 to deal with: Specifically, when the Storage module finds that SMS Appl goes to sleep, it modifies the cached SMS readback distribution policy, and after the cached SMS that needs to be resent is read back from the disk, it is not sent to the SMS Appl. And sent to the currently available SMS App2; when the SMS App module enters the sleep state, the interface with the Storage will be disconnected;
- the short message scheduling model is based on the retransmission scheduling and the status report matching of the called number. Therefore, the SMS App needs to cache the short message query message, the message that fails to be cached, and the user start notification AlertSc message. The called number is sent to the Storage module, and the status report message to be matched is sent to the Storage module according to the calling number. After the Storage module reads back the short message, it should be distributed according to the busy status of the SMS App.
- the SMS App2 After receiving the read-back message from the storage, the SMS App2 delivers the message according to the normal processing procedure of the short message, and if the delivery fails, it is buffered by the storage module.
- the Access Module submits the received SMS to the SMS App of each working state. (In this step, the SMS received by the Access Module can refer to the description in step 801 above, and will not be described again.)
- the SMS App of the working state first delivers the short message sent by the Access Module, and if the delivery fails, passes the storage cache;
- the SMS App and the Control Module in the working state of the short message center communicate through the TCP/IP long connection, and the SMS App in the working state periodically (can be 1s) to the Control Module Reporting the status information of the device; (for reporting the status information in this step, refer to the description in step 803 above, and no further details are provided.)
- the Control Module determines the overall load of the SMS center cluster according to the status information reported by the node device in the working state.
- control module determines the overall load of the current short message center cluster by accumulating according to the current traffic processing of each node device.
- the overall load is light, and the relatively idle node device is determined according to the busy state of each node device, and the relatively idle node device is changed from the working state to the dormant state;
- Proximity can be determined by a preset threshold.
- the overall traffic of the short message center cluster is close to the processing capability of the short message center cluster as an example.
- the Control Module sends SMS to the sleeping SMS App through the TCP/IP interface.
- the Control Module control device may specifically notify the sleeping node device to perform the conversion of the running state through an external hardware device.
- the external hardware may be a control board Device Control Board, as shown in FIG. 10, which is a schematic diagram of a short message center cluster control system of the control board, wherein only the node device part is shown in the short message center cluster system, and other parts are not here. show.
- the Device Control Board of the control panel serves as a working state control component of the node device, and connects all the SMS App devices, and has a mouse between the motherboards of the respective SMS App devices.
- the Device Control Board notifies the power control unit on the SMS App main board to wake the device from the sleep state.
- the Control Module when the Control Module needs to wake up an SMS App device, it sends a wakeup notification to the Device Control Board, and the Device Control Board sends a notification to the power control unit of the corresponding SMS App device, triggering the SMS App device and the operating system to enter the work.
- the SMS App application is re-initialized, and an interface with peripheral components is established, and the wake-up work is completed.
- the SMS App receives the activation notification and enters the working state from the sleep state;
- the access device may adjust the short message routing according to the working state change of the node device.
- the specific adjustment process may be: deleting the sleeping node device from the available node device after the node device is changed from the working state to the sleeping state; or After the node device transitions from the sleep state to the working state, the node device that is converted to the working state is added to the available node device.
- the SMS App1 When the SMS center sleep node device SMS App1 enters the working state, the SMS App1 is added to the list of available node devices, and the access device can distribute the received short messages by polling between the currently working node devices. Way to ensure load balancing of available node devices.
- the SMS App1 After receiving the short message sent by the Access Module to the dormant node, the SMS App1 delivers the message according to the normal processing procedure of the short message, and then passes the storage cache after the failure; (in this step, the storage of the cached short message and the processing of the cached short message can be referred to. Description in step 808 above)
- the Control Module modifies the routing rule of the readback short message through the storage module, and controls the cached short message that the storage module will obtain, according to the modified Read back the SMS routing rules, will sleep
- SMS App1 currently active SMS App
- the SMS App1 After receiving the read-back message from the storage, the SMS App1 sends the message according to the normal processing procedure of the short message. If the delivery fails, the storage module caches.
- the control device adjusts the total load of the current short message center cluster and the busy state of the node device, and adjusts the number of node devices in the current short message center cluster, and simultaneously
- the energy saving and consumption reduction effect can be achieved as much as possible.
- the storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).
- ROM read-only memory
- RAM random access memory
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
- Telephonic Communication Services (AREA)
Description
一种短信中心集群的控制方法、 设备及***
本申请要求 2010年 7月 30日递交的申请号为 20101 0242555. 9、 发明名 称为 "一种短信中心集群的控制方法、 设备及***" 的中国专利申请的 优先权, 其全部内容通过引用结合在本申请中。 技术领域
本发明涉及通信技术领域, 更具体的说, 涉及一种短信中心集群的控 制方法、 设备及***。 背景技术
短信中心 ( SMSC , Shor t me s sage serv i ce center )是处理短信业务 ( SMS, shor t mes sage serv i ce ) 的通信设备, 当短信提交到短信中心后, 短信中心对提交的短信进行下发, 若短信下发失败, 则要将该短信緩存在短 信中心以等候一定时间之后再重新发送。 短信中心通常还承载了若干短信增 值业务, 这些业务要求短信中心与周边部件配合完成若干的交互。 目前, 为 了在话务高峰期间保障消息量的正常处理, 运营商在釆购和部署短信中心设 备时, 通常按照话务高峰流量所需的软硬件状况来配置短信中心***, 但在 日常大部分时间中的短信话务量远远低于高峰期的流量, 这样短信中心设备 硬件的不断运行, 在很大程度上就会造成能源的浪费。 发明内容
本发明的实施例提供了一种短信中心集群的控制方法、 设备及***, 实 现了现有短信中心***的节能降耗。
本发明实施例的技术方案如下所述:
本发明实施例提供了一种短信中心集群的控制方法, 技术方案包括: 获取短信中心集群中各节点设备的状态信息;
根据所述状态信息调整所述短消息中心集群中处于工作状态的节点设备
数量。
本发明实施例提供了一种控制设备, 技术方案包括:
获取模块 , 用于获取短信中心集群中各节点设备的状态信息; 控制模块, 用于根据所述状态信息调整所述短消息中心集群中处于工作 状态的节点设备数量。
本发明实施例提供了一种短信中心集群***, 包括接入设备和至少两个 节点设备;
所述接入设备用于接收短信, 并按照预定的路由规则将所述短信分配给 相应的可用节点设备进行处理;
所述节点设备用于处理短信业务, 并向控制设备上报自身的状态信息, 接收所述控制设备根据所述状态信息下发的控制指示, 当所述控制指示为休 眠指示时, 将自身从工作状态转换为休眠状态; 当所述控制指示为唤醒指示 时, 将自身从休眠状态转换为控制状态。
本发明实施例提供了一种短信中心集群控制***, 包括:
控制设备, 用于获取短信中心集群***中各节点设备的状态信息, 并根 据所述状态信息调整所述短消息中心集群中处于工作状态的节点设备数量; 短信中心集群***, 用于处理短信业务, 并向所述控制设备上报各节点 设备的状态信息, 接收所述控制设备根据所述状态信息下发的用于调整节点 设备数量的控制指示, 当所述控制指示为休眠指示时, 将自身从工作状态转 换为休眠状态; 当所述控制指示为唤醒指示时, 将自身从休眠状态转换为控 制状态。
由上述本发明的实施例提供的技术方案可以看出, 其在保证短信中心业 务正常处理的前提下, 对节点设备的工作状态进行管理, 根据短信中心集群 实际的负荷来调整短信中心集群中处于工作状态节点设备的数量, 在很大程 度上实现了短消息中心的节能降耗。 附图说明
为了更清楚地说明本发明实施例的技术方案, 下面将对实施例描述中所
需要使用的附图作简单地介绍, 显而易见地, 下面描述中的附图仅仅是本发 明的一些实施例, 对于本领域普通技术人员来讲, 在不付出创造性劳动性的 前提下, 还可以根据这些附图获得其他的附图。
图 1为本发明实施例提供的短信中心集群的控制方法的流程图: 图 2为本发明实施例提供的短信中心集群***的结构示意图;
图 3为本发明实施例提供的短信中心集群***的具体结构示意图; 图 4为本发明实施例提供的控制设备的结构示意图;
图 5为本发明实施例提供的控制设备的具体结构示意图;
图 6为本发明实施例提供的短信中心集群控制***结构示意图; 图 7为本发明实施例短信中心业务处理部分的应用场景图;
图 8为本发明实施例控制设备控制短信中心节点设备休眠的应用流程图; 图 9为本发明实施例控制设备控制短信中心节点设备唤醒的应用流程图; 图 10为本发明实施例控制设备通知节点设备转换为工作状态的硬件实现 结构图。 具体实施方式
下面将结合本发明实施例中的附图, 对本发明实施例中的技术方案进行 清楚、 完整地描述, 显然, 所描述的实施例仅仅是本发明一部分实施例, 而 不是全部的实施例。 基于本发明中的实施例, 本领域普通技术人员在没有作 出创造性劳动前提下所获得的所有其他实施例, 都属于本发明保护的范围。
本发明实施例在保证短信中心业务正常处理的前提下, 根据短信中心集 群整体负荷和单个节点设备的忙闲状态来调控短信中心集群中处于工作状态 的节点设备数量, 从而实现在短信中心非业务高峰期的节能降耗。
下面结合具体实施例对本发明的技术方案进行说明。
如图 1所示为本发明实施例提供的一种短信中心集群的控制方法,本实施 例以控制设备的角度进行描述, 该方法可以包括:
步骤 101: 控制设备获取短信中心集群中各节点设备的状态信息; 本发明实施例中, 短信中心集群的节点设备具有短信中心的短信处理能 力, 用于对短信进行处理。 控制设备釆用定时或实时交互的通信方式来获得 各节点设备的状态信息, 其中, 状态信息可以包括节点设备的当前流量及节 点设备的忙闲状态; 节点设备忙闲状态可以包括软件忙闲状态及硬件忙闲状 态; 软件忙闲状态可以通过短信中心节点设备当前处理消息的流量, 緩存短 信的数量等软件忙闲指标来确定; 硬件忙闲状态可以通过*** CPU使用率、 内存占用率、 网络带宽占用率、 温度等硬件忙闲指标来确定, 其中, 短信中 心集群的节点设备可以通过调用操作*** AP I的方式获取本设备的硬件忙闲 指标。 本发明实施例中, 节点设备可以通过与控制设备的交互接口向控制设 备上报自身的状态信息, 其中, 可以釆用节点设备主动上报的方式, 也可以 釆用控制设备查询的方式。
步骤 102:控制设备根据状态信息调整短消息中心集群中处于工作状态的 节点设备数量。
在本发明实施例中, 控制设备可以根据短信中心集群的整体负荷以及各 节点设备的忙闲状态来调整短消息中心集群中处于工作状态的节点设备数 量, 具体过程可以包括: 控制设备要根据各节点设备当前流量确定短信中心 集群的整体负荷; 若短信中心集群的整体负荷轻, 则根据各节点设备的忙闲 状态确定相对空闲的节点设备, 并指示相对空闲的节点设备由工作状态转换
为休眠状态; 若短信中心集群的整体负荷重, 则指示处于休眠状态的节点设 备由休眠状态转换为工作状态。
需要说明的是, 在实际操作中各节点设备上报的忙闲状态可以通过示忙 标志的不同等级来表示 (如, 0, 空闲; 1 , 正常; 2, 忙; 3, 接近极限) , 以便控制设备可以直接根据接收到的示忙标识直接确定哪些节点设备可以休 眠, 哪些节点设备可以被唤醒。
本发明实施例中, 由于根据短信中心集群实际的负荷来调整短信中心集 群中处于工作状态节点设备的数量,使得在短信中心集群的实际话务量低时, 部分节点设备可以转为休眠状态, 实现了短信中心集群***的节能降耗。
进一步的, 上述根据各节点设备的当前流量确定所述短信中心集群的整 体负荷可以包括:根据各节点设备的当前流量计算短信中心集群的整体流量; 当短信中心集群的整体流量远小于短信中心集群的处理能力时, 确定所述短 信中心集群的整体负荷轻; 当短信中心集群的整体流量接近短信中心集群的 处理能力时; 确定所述短信中心集群的整体负荷重; 其中, 远小于和接近可 以通过预先设定的阔值来确定, 如, 分别设置用于判断 "远小于" 的第一阔 值和用于判断 "接近" 的第二阔值, 当计算出的短信中心集群的整体流量与 短信中心集群可处理的流量的差值的绝对值小于第一阔值, 则短信中心集群 的整体流量远小于短信中心集群的处理能力; 当计算出的短信中心集群的整 体流量与短信中心集群可处理的流量的差值的绝对值大于第二阔值, 则短信 中心集群的整体流量接近短信中心集群的处理能力; 其中, 第一阔值小于第 二阔值, 两者都可根据经验值来设置。
在本发明一个实施例中, 控制设备可以通过向相对空闲节点设备发送休
眠通知消息来指示相对空闲的节点设备由工作状态转换为休眠状态, 其中, 该休眠通知消息可以用于控制所述相对空闲的节点设备调用操作*** API ( Application Programming Interface, 应用程序编程接口)进行休眠操作; 当需要唤醒时, 控制设备可以通过远程控制机制唤醒处于休眠状态的节点设 备。
在本发明实施例中, 控制设备还可以进一步对后续发往休眠节点设备的 短信进行控制处理。 具体的, 可以在节点设备由工作状态转换为休眠状态后, 通过将休眠节点设备从可用节点设备中删除; 或者, 在有节点设备从休眠状 态转换为工作状态后,将转换为工作状态的节点设备加入到可用节点设备中, 以保证将接入短信中心的消息分配给可用节点设备进行处理。
对于节点设备产生的緩存消息短信, 控制设备还可以在节点设备由工作 状态转换为休眠状态后, 控制当前短信中心集群中处于工作状态的节点设备 获取并处理休眠节点设备产生的緩存短信, 緩存短信的存放路径为所述短信 中心集群中所有节点设备都可访问的路径。 其中, 緩存短信可以是节点设备 在休眠之前因下发失败而产生的。
本发明实施例提通过控制设备对短信路由规则进行修改, 将理应路由至 休眠节点上的短信, 分配给当前短信中心集群中处于工作状态的节点设备上 进行处理, 从而保证了这些短信的及时处理。
此外, 短信中心集群中有节点设备休眠时, 本发明实施例针对该节点设 备在休眠之前緩存短信同样提出了相应的处理策略, 控制设备通过控制短信 中心集群***中处于工作状态的节点设备获取并处理休眠节点产生的緩存短 信, 保证了休眠节点设备产生的緩存短信的及时处理。
如图 2所示, 本发明实施例中的短消息中心釆用集群组网方式, 该短消息 中心集群***包括接入设备 22和至少两个节点设备 21 (节点 1和节点 2 ) ; 其中, 接入设备和节点设备可以是简化的短信中心, 接入设备实现短信 中心接入短信的功能, 节点设备实现短信中心处理短信业务的功能。
具体的, 接入设备用于接收短信, 并按照预定的路由规则将所述短信分 配给相应的可用节点设备进行处理。
节点设备用于处理短信业务, 并用于向控制设备上报自身的状态信息, 接收控制设备根据状态信息下发的控制指示, 当控制指示为休眠指示时, 将 自身从工作状态转换为休眠状态; 当控制指示为唤醒指示时, 将自身从休眠 状态转换为控制状态。
在具体实施例中, 接入设备可以有一个或多个, 一般情况下, 可以设置 两个接入设备, 分别用于接收来自信令网的 SS7协议接口的短信和接收来自 IP网的 SMPP协议接口的短信。 当节点设备的工作状态变化时 (如, 从休眠 状态转为工作状态, 或从工作状态转为休眠状态) , 接入设备可以根据节点 设备的工作状态变化调整短信路由。 具体调整过程可以是, 当节点设备由工 作状态转换为休眠状态后, 将休眠节点设备从可用节点设备中删除; 或者, 在有节点设备从休眠状态转换为工作状态后, 将转换为工作状态的节点设备 加入到可用节点设备中。
本发明实施例中, 短信中心集群***中各节点设备可以釆用定时或实时 交互的通信方式向控制设备上报自身的状态信息, 其中, 状态信息可以包括 节点设备的当前流量及节点设备的忙闲状态; 节点设备忙闲状态包括软件忙
闲状态及硬件忙闲状态; 软件忙闲状态可以通过短信中心节点设备当前处理 消息的流量, 緩存短信的数量等软件忙闲指标来确定; 硬件忙闲状态参数可 以通过*** CPU使用率、 内存占用率、 网络带宽占用率、 温度等来硬件忙闲 指标确定。 在本发明实施例中, 短信中心集群的节点设备可以通过调用操作 *** API的方式获取本设备的硬件忙闲指标。本发明实施例中, 节点设备可以 通过与控制设备的交互接口向控制设备上报自身的状态信息, 其中, 可以釆 用节点设备主动上报的方式, 也可以釆用控制设备查询的方式。
在本发明的一个具体实施例中, 短信中心集群***中的节点设备可以通 过调用操作*** API将自身从工作状态转换为休眠状态, 另外, 节点设备在接 收到控制设备的休眠指示时, 还可以进一步断开与周边设备的接口, 并清除 程序内部的临时数据。 对于唤醒处理, 即将短信中心集群***中的节点设备 从休眠状态转为工作状态, 可以通过控制设备的远程控制来实现, 具体的, 控制设备可以通过节点设备主板上的电源控制器来触发节点设备和操作*** 进入工作状态, 操作***进入工作状态后, 节点设备应用程序重新进行初始 化, 并建立与周边部件的接口, 从而完成唤醒工作。
本发明实施例中, 为了在节点设备休眠后, 可以及时处理休眠节点在休 眠之前产生的緩存短信, 可以将各节点设备的緩存数据与业务处理过程相分 离, 使短信中心各节点设备与緩存短信之间为松耦合关系。
因此, 如图 3所示, 在本发明的一个实施例中, 短信中心集群***还可以 进一步包括:
緩存处理设备 23, 用于在有节点设备转换为休眠状态后, 回读休眠节点 设备在休眠前产生的緩存短信, 并分配给处于工作状态的节点设备。
其中, 緩存处理设备在逻辑上与节点设备的处理相分离, 在物理上也可 以独立于节点设备设置。 緩存处理设备可以是一个或多个, 緩存处理设备与 节点设备可以是多对多的关系; 节点设备在下发短信失败后, 可以将下发失 败的短信发送给任一緩存处理设备, 并告知该緩存处理设备该短信的回读时 间, 緩存处理设备将该短信緩存到可以被所有的緩存处理设备访问的存储设 备中。 该存储设备可以是磁盘、 硬盘等。 当到达该短信的回读时间时, 緩存 处理设备从存储设备中回读该短信, 并将该短信发送给短信中心集群***中 任意可用节点设备进行重发。
需要说明的是, 本发明实施例中的接入设备、 节点设备、 緩存处理设备 都可以是计算机, 其中, 接入设备、 节点设备可以位于同一个物理实体中。
如图 4所示, 基于图 1实施例提出的一种短信中心集群的控制方法, 本发 明实施例以控制设备的角度, 提供了一种控制设备的结构示意图, 本实施例 中, 控制设备包括:
获取模块 41, 用于获取短信中心集群中各节点设备的状态信息; 控制模块 42, 用于根据所述状态信息调整短消息集群中处于工作状态的 节点设备数量。
在本发明一个具体实施例中, 状态信息可以包括: 节点设备的当前流量 及节点设备的忙闲状态; 其中, 节点设备忙闲状态可以通过软件忙闲状态及 硬件忙闲状态来确定的, 具体实现方式可参照上述图 1所示实施例中的描述。
在本发明一个具体实施例中,图 4实施例提出的控制设备具体还可以包括 图 5的各功能模块, 其中, 控制模块 42具体可以包括:
确定单元 421 ,用于根据各节点设备的当前流量确定所述短信中心集群的
整体负荷;
选择单元 422,用于在短信中心集群的整体负荷轻时,根据各节点设备的 忙闲状态确定相对空闲的节点设备;
指示单元 423,用于在所述确定单元确定短信中心集群整体负荷轻时,指 示所述相对空闲的节点设备由工作状态转换为休眠状态; 在所述确定单元确 定短信中心集群整体负荷重时, 指示所述休眠状态的节点设备由休眠状态转 换为工作状态。
在本发明一个具体实施例中, 确定单元 421可以包括:
计算子单元 4211, 用于根据各节点设备的当前流量计算所述短信中心集 群的整体流量;
比较子单元 4212 , 用于比较所述短信中心集群的整体流量与短信中心集 群的处理能力, 当所述短信中心集群的整体流量远小于短信中心集群的处理 能力时, 确定所述短信中心集群的整体负荷轻; 当所述短信中心集群的整体 流量接近短信中心集群的处理能力时;确定所述短信中心集群的整体负荷重; 所述远小于和接近可以通过预先设定的阔值来确定。 上述比较过程可以参考 图 1所示实施例中的描述, 这里不再赘述。
在本发明一个具体实施例中, 指示单元 423具体可以用于:
在确定短信中心集群整体负荷轻时, 向所述相对空闲的节点设备发送休 眠通知消息, 所述休眠通知消息用于控制所述相对空闲的节点设备调用操作 *** API进行休眠操作; 在确定短信中心集群整体负荷重时,通过远程控制机 制唤醒处于休眠状态的节点设备。
在本发明一个具体实施例中, 控制设备还可以包括:
路由模块 43, 用于当节点设备由工作状态转换为休眠状态后, 将休眠节 点设备从可用节点设备中删除; 或者, 在有节点设备从休眠状态转换为工作 状态后, 将转换为工作状态的节点设备加入到可用节点设备中。
需要说明的是, 本发明实施例提出的控制设备可以通过路由模块修改短 信路由规则, 直接将理应路由至休眠节点设备上的短信分配给当前短信中心 集群中处于工作状态的可用节点设备处理;
也可以通过控制短信中心集群***中的接入设备,来修改短信路由规则, 并将理应路由至休眠节点设备上的短信的分配给当前短信中心集群中处于工 作状态的可用节点设备处理。
在本发明一个具体实施例中, 控制设备还可以包括:
緩存处理模块 44, 用于当节点设备由工作状态转换为休眠状态后, 控制 当前短信中心集群中处于工作状态的节点设备获取并处理休眠节点设备产生 的緩存短信; 所述緩存短信的存放路径为所述短信中心集群中所有节点设备 都可访问的路径。
其中, 上述路由模块和緩存处理模块是可选的, 路由模块的功能也可以 放在短信中心集群***的接入设备中实现, 緩存处理模块也可以放在短信中 心集群***的緩存处理设备中实现。
本发明实施例中的控制设备可以是计算机, 控制设备中的各功能单元可 以在 CPU中运行。
需要说明的是, 因为本发明实施例是基于图 1所示的方法实施例获得的, 所以本发明实施例中各功能模块涉及的技术方案与图 1中方法实施例各步骤 对应的技术方案相同或相似,具体请参见上述图 1方法实施例,在此不作赘述。
如图 6所示, 为本发明实施提供的一种短信中心集群控制***, 该***可 以包括:
控制设备 61 , 用于获取短信中心集群***中各节点设备的状态信息, 并 根据状态信息调整所述短消息中心集群中处于工作状态的节点设备数量; 短信中心集群*** 62, 用于处理短信业务, 并向控制设备上报各节点设 备的状态信息, 接收控制设备根据状态信息下发的用于调整节点设备数量的 控制指示, 当控制指示为休眠指示时, 将自身从工作状态转换为休眠状态; 当控制指示为唤醒指示时, 将自身从休眠状态转换为控制状态。
其中, 短信中心集群***的具体实现可以参考图 2和图 3所示实施例, 控 制设备的具体实现可以参考图 4和图 5所示实施例, 这里不再赘述。 为了进一步理解本发明实施例的技术方案, 下面通过具体实施例详细描 述本发明实施例记载的技术方案, 通过监控短信中心集群中各节点设备的状 态信息来调整短信中心集群中处于工作状态的节点设备的数量, 从而保证短 信中心业务正常运行的情况下, 实现短信中心***的节能降耗。 但本发明实 施例的技术方案在实现过程中不限于下述中描述的技术手段。 如图 7所示, 描述了短信中心 SMSC集群控制***的应用场景图, 其中, 短信中心集群包括接入层 Access Layer和业务层 Service Layer, 短信中心集 群中的接入设备(如, 本实施例中负责第三方业务接入的 3rd Party Service Access Module和负责信令 SS7接入的 Signal Access Module )位于 Access
Layer, 图中 SMS App为短信中心集群***中的节点设备, Storage为短信中 心集群中的緩存处理设备, SMS App和 Storage均位于 Service Layer。 其中, Storage可以独立设置于各节点设备之中, 也可独立设置在各节点设备之外, 但緩存短信的存放路径为所述短信中心集群中所有节点设备都可访问的路 径, 以便在有节点设备休眠时, 其生成的緩存短信能够被及时处理。 Control Module为控制设备, 其可设置在短消息集群***的 Service Layer。
SMS App负责短信业务处理, Storage负责緩存短信的存取(具体的, 緩存数据存放在图 7所示的 Disk Array中, Disk Array中緩存短信的存放路径 可被短信中心集群中各 Storage模块访问;
Access Layer包括: 负责第三方业务接入短信中心集的 3rd Party Service Access Module, 并通过 Smpp协议与短信中心集群中的各 App节点连接; 负 责将短信中心通过 SS7接入核心网的 Signal Access Module, 与短信中心集 群中节点设备相连;
Control Module负责监控短信中心各节点设备的状态信息, 并控制短信 中心各节点设备的运行状态, 是由工作状态转换为休眠状态, 还是由休眠状 态转换为工作状态。
在上述对图 7中所示各功能模块进行功能的介绍之后,下面将通过短信中 心业务处理的具体流程来对本发明实施例记载的技术方案进行详细描述。
其中, 在下述具体流程中主要分为控制设备将短信中心空闲节点设备休 眠的过程, 以及控制设备将休眠节点设备唤醒(也就是将处于休眠状态节点 设备转换为工作状态) 的过程, 具体内容将在相应的过程中予以详述。
如图 8所示,描述了控制设备将短信中心集群中相对空闲的节点设备休眠
的具体流程:
801: Access Module将接收到的短信按照预定规则提交到各 SMS App 上处理;
其中, 通过 3rd party access module接收第三方业务发至短信中心的短 信, 通过 Signal Access module接收核心网发至短信中心的短信;
本实施例中, 预定规则是指消息提交的分流规则, 一般短信中心支持按 照主叫号码的号段或者按照被叫号码的尾号来分流到不同的 SMSApp。
802: SMS App首先对 Access Module分配的短信消息进行下发,若下发 失败, 则通过 Storage緩存在 Disk Array中;
803: 短信中心各 SMS App与 Control Module之间通过 TCP/IP长连接通 信, SMS App定期(可以为 1s )向 Control Module上报自身设备的状态信息; 状态信息包括当前单个节点设备的当前流量以及节点设备的忙闲状态, 其中, 节点设备忙闲状态包括软件忙闲状态及硬件忙闲状态; 软件忙闲状态 可以通过短信中心节点设备当前处理消息的流量, 緩存短信的流量等软件忙 闲指标确定; 硬件忙闲状态可以通过*** CPU使用率、 内存占用率、 网络带 宽占用率、 温度等硬件忙闲指标来确定。 本发明实施例中, 短信中心节点设 备可以通过调用操作*** AP I的方式获取本设备的硬件忙闲状态。本实施例中 节点设备忙闲状态可以釆用不同的示忙标识来表示, 如: 0, 空闲; 1 , 正常; 2, 忙; 3, 接近极限, 这样方便控制设备直接对节点设备的忙闲状态进行识 别。
804: Control Module根据节点设备上报的状态信息当前短信中心集群的 整体负荷;
具体的, Control Module根据各节点设备当前流量处理通过累加来确定 当前短信中心集群的整体负荷, 当所述短信中心集群的整体流量远小于短信 中心集群的处理能力时, 确定所述短信中心集群的整体负荷轻, 并根据各节 点设备的忙闲状态确定相对空闲的节点设备, 并指示相对空闲的节点设备由 工作状态转换为休眠状态;
当所述短信中心集群的整体流量接近短信中心集群的处理能力时, 确定 所述短信中心集群的整体负荷重, 并指示处于休眠状态的节点设备由休眠状 态转换为工作状态; 其中, 远小于和接近可以通过预先设定的阔值来确定, 具体比较过程可参考图 1所示实施例。
本实施例以短信中心集群的整体流量远小于短信中心集群的处理能力为 例进行说明。
805: Control Module通过 TCP/IP的接口向相对空闲的 SMS App发送 SMS App进入休眠的指示;
806: SMS App接收到休眠通知, 进入休眠状态;
具体的, SMS App接收到 Control Module发送的休眠通知后, 断开与周 边模块的接口, 并清除程序内部的临时数据, 同时通过调用操作***的 API 进入休眠状态; 由于 SMS App仅处理业务, 緩存短信和会话索引信息都保存 在独立设置于节点设备之外的 Storage模块中, 因此 SMS App节点进入休眠 状态后, 其他 SMS App可以继续处理緩存短信和会话, 不会影响短信消息的 后续正常处理。
807: 接入设备可以根据节点设备的工作状态变化调整短信路由; 具体调整过程可以是, 当节点设备由工作状态转换为休眠状态后, 将休
眠节点设备从可用节点设备中删除; 或者, 在有节点设备从休眠状态转换为 工作状态后, 将转换为工作状态的节点设备加入到可用节点设备中。
进一步的, 当 SMS Appl休眠后, 来自信令网 SS7协议接口和 IP网 Smpp 协议接口的短信均通过 Access Module来接入和分发, 为了保证 Access
Module按照初始路由规则发至休眠节点设备的短信能够被及时处理, 可以将 当前处于工作状态的可用节点设备以列表的形式显示, 当监控到有 SMS App 节点由休眠状态进入工作状态时, 将该 SMS App节点加入到可用节点设备列 表中, 当监控到有 SMS App节点设备由工作状态进入休眠状态时, 将该节点 设备从可用节点设备列表中删除, 接入设备可以通过将接收到的短信在当前 处于工作状态节点设备之间轮询均匀分发的方式来保证可用节点设备的负载 均衡。
808: SMS App2接收到 Access Module分发的理应路由至 SMS App1的 消息后, 按照消息正常处理流程先下发, 失败后则通过 Storage緩存;
具体的, 为了保证 SMS App工作状态变化不影响休眠节点緩存短信的处 理, 本发明实施例中将业务处理过程与緩存数据在物理和逻辑上分离。
物理上 SMS App与 Storage模块之间可以是不对称的多对多关系。
逻辑上, 由 SMS App负责对短信的下发, 下发失败后发送给 Storage模块 緩存, 并在 Storage上设定緩存短信的回读时间, 以使 SMS App对该緩存短 信进行重发; 由 Storage负责接收从 SMS App分配的緩存短信, 并保存到磁 盘中进行持久化, 当緩存短信到达回读时间, 则 Storage从磁盘中将緩存短信 回读, 并发送给 SMS App集群中可用的任意节点进行重发。
809: SMS Appl处于休眠状态, 为了保证其的緩存短信在回读时间到达
时能够被及时重发, Control Module通过对 Storage模块进行控制, 通过控制 Storage模块对获取到的回读短信的路由规则进行修改, 以便将 SMS App1的 回读短信分发给当前处于工作状态的 SMS App (如: SMS App2 )来处理: 具体的, 当 Storage模块发现有 SMS Appl进入休眠后, 修改緩存短信回 读分发策略, 将需要重发的緩存短信从磁盘回读后, 不向该 SMS Appl发送, 而发送到当前可用的 SMS App2上; 当 SMS App模块进入休眠状态后, 将断 开与 Storage之间的接口;
在本发明实施例一中考虑到短信调度模型是基于被叫号码的重发调度和 状态报告匹配, 因此 SMS App需要将緩存短信查询消息、 下发失败需緩存的 消息、 用户开机通知 AlertSc消息按照被叫号码发送到 Storage模块, 将待匹 配的状态报告消息按照主叫号码发送到 Storage模块处理, 而 Storage模块回 读短信后应根据 SMS App的忙闲状态进行分发。
810: SMS App2接收到来自 Storage的回读短信后, 按照短信的正常处 理流程先下发, 若下发失败则通过 Storage模块緩存。
如图 9所示, 描述了控制设备将短信中心休眠节点设备唤醒的具体流程:
901: Access Module将接收到的短信提交到各工作状态的 SMS App处 理; (此步骤中 Access Module接收到的短信可参考上述步骤 801所的描述, 不再赘述)
902:工作状态的 SMS App首先对 Access Module分配的短信消息进行下 发, 若下发失败则通过 Storage緩存;
903: 短信中心工作状态的 SMS App与 Control Module之间通过 TCP/IP 长连接通信, 工作状态下的 SMS App定期 (可以为 1s ) 向 Control Module上
报自身设备的状态信息; (该步骤中上报状态信息可参考上述步骤 803中的描 述, 不再赘述)
904: Control Module根据工作状态下节点设备上报的状态信息确定短信 中心集群的整体负荷;
具体的, Control Module根据各节点设备当前流量处理通过累加来确定 当前短信中心集群的整体负荷, 当所述短信中心集群的整体流量远小于短信 中心集群的处理能力时, 确定所述短信中心集群的整体负荷轻, 并根据各节 点设备的忙闲状态确定相对空闲的节点设备, 并指示相对空闲的节点设备由 工作状态转换为休眠状态;
当所述短信中心集群的整体流量接近短信中心集群的处理能力时, 确定 所述短信中心集群的整体负荷重, 并指示处于休眠状态的节点设备由休眠状 态转换为工作状态; 其中, 远小于和接近可以通过预先设定的阔值来确定。
本实施例以短信中心集群的整体流量接近短信中心集群的处理能力为例 进行说明。
905: Control Module通过 TCP/IP的接口向休眠的 SMS App发送 SMS
App进入工作状态的指示;
其中, Control Module控制设备具体可以通过外部的硬件设备通知休眠 节点设备进行运行状态的转换。 该外部硬件可以是控制板 Device Control Board , 如图 10所示, 为釆用控制板的短信中心集群控制***结构图, 其中 短信中心集群***中仅示出了节点设备部分, 其它部分在此未示出。
具体参见图 10,控制板 Device Control Board作为节点设备的工作状态控 制部件, 连接了所有的 SMS App设备, 并与各 SMS App设备的主板之间有鼠
标、键盘、 电源控制的硬件接口, SMS App处于休眠状态时, Device Control Board通知 SMS App主板上的电源控制单元, 可将设备从休眠状态唤醒。
具体的, 当 Control Module需要将某个 SMS App设备唤醒, 则向 Device Control Board发送唤醒通知, 由 Device Control Board向相应的 SMS App设 备的电源控制单元发送通知, 触发 SMS App设备和操作***进入工作状态, 操作***进入工作状态后, SMS App应用程序重新进行初始化, 并建立与周 边部件的接口, 唤醒工作完成。
906: SMS App接收到激活通知, 由休眠状态进入工作状态;
907: 接入设备可以根据节点设备的工作状态变化调整短信路由; 具体调整过程可以是, 当节点设备由工作状态转换为休眠状态后, 将休 眠节点设备从可用节点设备中删除; 或者, 在有节点设备从休眠状态转换为 工作状态后, 将转换为工作状态的节点设备加入到可用节点设备中。
当短信中心休眠节点设备 SMS App1进入工作状态时, 将该 SMS App1 加入到可用节点设备列表中, 接入设备可以通过将接收到的短信在当前处于 工作状态节点设备之间轮询均勾分发的方式来保证可用节点设备的负载均 衡。
908: SMS App1接收到 Access Module分发的理论路由至休眠节点的短 信后, 按照短信正常处理流程先下发, 失败后则通过 Storage緩存; (此步骤 中緩存短信的存储以及緩存短信的处理可参考上述步骤 808中的描述 )
909:为了保证休眠节点设备的緩存短信在回读时间到达时能够被及时重 发, Control Module通过 Storage模块对回读短信的路由规则进行修改, 控制 Storage模块将获取到的緩存短信, 按照修改后的回读短信路由规则, 将休眠
节点的回读短信分发给当前处于工作状态的 SMS App ( SMS App1 )来处理:
(此步骤中回读短信的路由和处理过程可参考上述步骤 809中所描述的相同, 不再赘述)
910: SMS App1接收到来自 Storage的回读短信后, 按照短信的正常处 理流程先下发, 若下发失败则通过 Storage模块緩存。
通过上述本发明实施例记载的技术方案可知, 控制设备通过监控当前短 信中心集群的整体负荷和节点设备的忙闲状态, 调整当前短信中心集群中处 于工作状态的节点设备的数量, 同时, 当集群流量增加时, 选择能够唤醒某 些休眠节点设备, 提升当前集群的总处理能力, 以应对来自外部增加的流量, 在保证短信中心业务正常处理的前提下, 达到尽可能地节能降耗的效果。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流 程, 是可以通过计算机程序来指令相关的硬件来完成, 所述的程序可存储于 一计算机可读取存储介质中, 该程序在执行时, 可包括如上述各方法的实施 例的流程。 其中, 所述的存储介质可为磁碟、 光盘、 只读存储记忆体 ( Read-Only Memory, ROM )或随机存者 i己忆体( Random Access Memory, RAM )等。 以上所述, 仅为本发明较佳的具体实施方式, 但本发明的保护范围并不 局限于此, 任何熟悉本技术领域的技术人员在本发明揭露的技术范围内, 可 轻易想到的变化或替换, 都应涵盖在本发明的保护范围之内。 因此, 本发明 的保护范围应该以权利要求的保护范围为准。
Claims
1、 一种短信中心集群的控制方法, 其特征在于, 包括:
获取短信中心集群中各节点设备的状态信息;
根据所述状态信息调整所述短信中心集群中处于工作状态的节点设备数 量。
2、 根据权利要求 1所述的方法, 其特征在于, 所述状态信息包括: 节点 设备的当前流量以及节点设备的忙闲状态;
所述根据所述状态信息调整所述短信中心集群中的工作节点设备数量, 包括:
根据各节点设备的当前流量确定所述短信中心集群的整体负荷; 若短信中心集群的整体负荷轻, 则根据各节点设备的忙闲状态确定相对 空闲的节点设备, 并指示相对空闲的节点设备由工作状态转换为休眠状态; 若短信中心集群的整体负荷重, 则指示处于休眠状态的节点设备由休眠 状态转换为工作状态。
3、 根据权利要求 2所述的方法, 其特征在于, 所述根据各节点设备的当 前流量确定所述短信中心集群的整体负荷包括:
根据各节点设备的当前流量计算所述短信中心集群的整体流量; 当所述短信中心集群的整体流量远小于短信中心集群的处理能力时, 确 定所述短信中心集群的整体负荷轻; 当所述短信中心集群的整体流量接近短 信中心集群的处理能力时; 确定所述短信中心集群的整体负荷重; 所述远小 于和接近通过预先设定的阔值来确定。
4、根据权利要求 2或 3中所述的方法, 其特征在于, 所述指示相对空闲的 节点设备由工作状态转换为休眠状态包括:
向所述相对空闲的节点设备发送休眠通知消息, 所述休眠通知消息用于 控制所述相对空闲的节点设备调用操作*** API进行休眠操作。
5、根据权利要求 2至 4中任一所述的方法, 其特征在于, 所述指示处于休 眠状态的节点设备由休眠状态转换为工作状态包括:
通过远程控制机制唤醒处于休眠状态的节点设备。
6、根据权利要求 1至 5中任一所述的方法,其特征在于,所述方法还包括: 当节点设备由工作状态转换为休眠状态后, 将休眠节点设备从可用节点 设备中删除; 或者, 在有节点设备从休眠状态转换为工作状态后, 将转换为 工作状态的节点设备加入到可用节点设备中。
7、根据权利要求 1至 6中任一所述的方法,其特征在于,所述方法还包括: 当节点设备由工作状态转换为休眠状态后, 控制当前短信中心集群中处 于工作状态的节点设备获取并处理休眠节点设备产生的緩存短信; 所述緩存 短信的存放路径为所述短信中心集群中所有节点设备都可访问的路径。
8、 一种控制设备, 其特征在于, 包括:
获取模块 , 用于获取短信中心集群中各节点设备的状态信息;
控制模块, 用于根据所述状态信息调整所述短消息中心集群中处于工作 状态的节点设备数量。
9、 根据权利要求 8所述的设备, 其特征在于, 所述状态信息包括: 节点 设备的当前流量以及节点设备的忙闲状态;
所述控制模块包括:
确定单元, 用于根据各节点设备的当前流量确定所述短信中心集群的整 体负荷;
选择单元, 用于在短信中心集群的整体负荷轻时, 根据各节点设备的忙 闲状态确定相对空闲的节点设备;
指示单元, 用于在所述确定单元确定短信中心集群整体负荷轻时, 指示 所述相对空闲的节点设备由工作状态转换为休眠状态; 在所述确定单元确定 短信中心集群整体负荷重时, 指示所述休眠状态的节点设备由休眠状态转换 为工作状态。
10、 根据权利要求 9所述的设备, 其特征在于, 所述确定单元包括: 计算子单元, 用于根据各节点设备的当前流量计算所述短信中心集群的 整体流量;
比较子单元, 用于比较所述短信中心集群的整体流量与短信中心集群的 处理能力, 当所述短信中心集群的整体流量远小于短信中心集群的处理能力 时, 确定所述短信中心集群的整体负荷轻; 当所述短信中心集群的整体流量 接近短信中心集群的处理能力时; 确定所述短信中心集群的整体负荷重; 所 述远' j、于和接近可以通过预先设定的阔值来确定。
11、 根据权利要求 9至 10中任一项所述的设备, 其特征在于, 所述指示 单元具体用于:
在确定短信中心集群整体负荷轻时, 向所述相对空闲的节点设备发送休 眠通知消息, 所述休眠通知消息用于控制所述相对空闲的节点设备调用操作 *** API进行休眠操作; 在确定短信中心集群整体负荷重时,通过远程控制机 制唤醒处于休眠状态的节点设备。
12、 根据权利要求 8至 11中任一所述的设备, 其特征在于, 所述设备还 包括:
路由模块, 用于当节点设备由工作状态转换为休眠状态后, 将休眠节点 设备从可用节点设备中删除; 或者, 在有节点设备从休眠状态转换为工作状 态后, 将转换为工作状态的节点设备加入到可用节点设备中。
13、 根据权利要求 8至 12中任一所述的设备, 其特征在于, 所述设备还 包括:
緩存处理模块, 用于当节点设备由工作状态转换为休眠状态后, 控制当 前短信中心集群中处于工作状态的节点设备获取并处理休眠节点设备产生的 緩存短信; 所述緩存短信的存放路径为所述短信中心集群中所有节点设备都 可访问的路径。
14、 一种短信中心集群***, 其特征在于, 包括接入设备和至少两个节 点设备;
所述接入设备用于接收短信, 并按照预定的路由规则将所述短信分配给 相应的可用节点设备进行处理;
所述节点设备用于处理短信业务, 并向控制设备上报自身的状态信息, 接收所述控制设备根据所述状态信息下发的控制指示, 当所述控制指示为休 眠指示时, 将自身从工作状态转换为休眠状态; 当所述控制指示为唤醒指示 时, 将自身从休眠状态转换为控制状态。
15、 根据权利要求 14所述的***, 其特征在于, 所述节点设备通过调用 操作*** API将自身从工作状态转换为休眠状态,或根据控制设备的远程控制 将自身从休眠状态转换为工作状态。
16、 根据权利要求 14或 15所述的***, 其特征在于, 所述接入设备还用 于在有节点设备转换为休眠状态后,将休眠节点设备从可用节点设备中删除; 或者, 在有节点设备从休眠状态转换为工作状态后, 将转换为工作状态的节 点设备加入到可用节点设备中。
17、 根据权利要求 15所述的***, 其特征在于, 还包括:
緩存处理设备, 用于在有节点设备转换为休眠状态后, 回读所述休眠节 点设备在休眠前产生的緩存短信, 并分配给处于工作状态的节点设备。
18、 一种短信中心集群控制***, 其特征在于, 包括:
控制设备, 用于获取短信中心集群***中各节点设备的状态信息, 并根 据所述状态信息调整所述短消息中心集群中处于工作状态的节点设备数量; 短信中心集群***, 用于处理短信业务, 并向所述控制设备上报各节点 设备的状态信息, 接收所述控制设备根据所述状态信息下发的用于调整节点 设备数量的控制指示, 当所述控制指示为休眠指示时, 将自身从工作状态转 换为休眠状态; 当所述控制指示为唤醒指示时, 将自身从休眠状态转换为控 制状态。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201010242555.9 | 2010-07-30 | ||
CN2010102425559A CN102143563A (zh) | 2010-07-30 | 2010-07-30 | 一种短信中心集群的控制方法、设备及*** |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2012013057A1 true WO2012013057A1 (zh) | 2012-02-02 |
Family
ID=44410716
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2011/073709 WO2012013057A1 (zh) | 2010-07-30 | 2011-05-05 | 一种短信中心集群的控制方法、设备及*** |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN102143563A (zh) |
WO (1) | WO2012013057A1 (zh) |
Families Citing this family (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102263666B (zh) * | 2011-08-22 | 2018-03-13 | 中兴通讯股份有限公司 | 基于业务流量许可进行业务调度的方法、装置及*** |
CN102299964B (zh) * | 2011-08-30 | 2013-08-07 | 南京邮电大学 | 一种应用于节能型集群***的数据重新部署方法 |
CN104080120B (zh) * | 2013-03-29 | 2018-05-08 | 中兴通讯股份有限公司 | 一种监测方法、装置及短消息中心局点 |
CN103561428B (zh) * | 2013-10-10 | 2017-02-01 | 东软集团股份有限公司 | 短信网关集群***中的节点弹性分配方法及*** |
CN104640090B (zh) * | 2013-11-14 | 2019-06-25 | 中兴通讯股份有限公司 | 短消息前转的异常处理方法及装置 |
CN105338008A (zh) * | 2014-06-10 | 2016-02-17 | 阿尔卡特朗讯 | 一种用于物联网的设备调度方法、设备与*** |
CN105282048B (zh) * | 2014-06-27 | 2020-09-29 | 南京中兴新软件有限责任公司 | 业务通道管理方法、装置及光传输设备 |
CN106155805A (zh) * | 2015-04-14 | 2016-11-23 | 中兴通讯股份有限公司 | ***内节点数的调整方法和装置 |
CN106487555A (zh) * | 2015-08-28 | 2017-03-08 | 中兴通讯股份有限公司 | 一种业务节点的调整方法、装置及设备 |
CN108270837B (zh) * | 2017-01-04 | 2021-04-30 | 北京京东尚科信息技术有限公司 | 一种利用闲置资源的分布式任务调度方法及*** |
CN113391691A (zh) * | 2021-06-03 | 2021-09-14 | 深圳市广和通无线股份有限公司 | 设备唤醒方法、装置、设备及存储介质 |
CN117687348B (zh) * | 2024-02-04 | 2024-05-14 | 科扬环境科技有限责任公司 | 基于物联网的高可靠度的废气处理设备集群的控制方法 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2006058464A1 (fr) * | 2004-12-02 | 2006-06-08 | Zte Corporation | Systeme en grappes de centre de message court et son procede de commande |
CN1859606A (zh) * | 2005-07-24 | 2006-11-08 | 华为技术有限公司 | 一种分流短消息的方法及其*** |
CN1859438A (zh) * | 2005-09-23 | 2006-11-08 | 华为技术有限公司 | 无源光网络用户终端的运行方法 |
CN101715252A (zh) * | 2009-10-27 | 2010-05-26 | 中兴通讯股份有限公司 | 一种群集短信中心及其实现容灾分流的方法 |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101742621A (zh) * | 2008-11-26 | 2010-06-16 | ***通信集团湖南有限公司 | 一种降低基站耗能的方法、装置及*** |
-
2010
- 2010-07-30 CN CN2010102425559A patent/CN102143563A/zh active Pending
-
2011
- 2011-05-05 WO PCT/CN2011/073709 patent/WO2012013057A1/zh active Application Filing
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2006058464A1 (fr) * | 2004-12-02 | 2006-06-08 | Zte Corporation | Systeme en grappes de centre de message court et son procede de commande |
CN1859606A (zh) * | 2005-07-24 | 2006-11-08 | 华为技术有限公司 | 一种分流短消息的方法及其*** |
CN1859438A (zh) * | 2005-09-23 | 2006-11-08 | 华为技术有限公司 | 无源光网络用户终端的运行方法 |
CN101715252A (zh) * | 2009-10-27 | 2010-05-26 | 中兴通讯股份有限公司 | 一种群集短信中心及其实现容灾分流的方法 |
Also Published As
Publication number | Publication date |
---|---|
CN102143563A (zh) | 2011-08-03 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2012013057A1 (zh) | 一种短信中心集群的控制方法、设备及*** | |
WO2021082301A1 (zh) | 一种包括车载以太网的车内混合网络的睡眠与唤醒方法 | |
CN106879038B (zh) | 工作状态切换方法及装置 | |
JP4309168B2 (ja) | ワイヤレスネットワークにおけるチャネルアクセススケジューリングのための方法およびシステム | |
JP5909159B2 (ja) | 制御装置および制御方法 | |
TWI474734B (zh) | 無線通訊裝置之電源管理方法及無線通訊裝置 | |
TW200947888A (en) | Method and apparatus for battery management in a converged wireless transmit/receive unit | |
KR101355065B1 (ko) | 통신 장치에서의 동적 전력 관리 | |
WO2007021115A1 (en) | A method of providing notification for battery power conservation in a wireless communication system | |
WO2021093763A1 (zh) | 一种数据缓存方法和装置 | |
JP2010004550A (ja) | バッテリ動作デバイスのウェイクアップ方法 | |
CN110089164A (zh) | 改进的无线设备的节能模式 | |
WO2015090239A1 (zh) | 通知用户状态的装置、方法和*** | |
JP2015534413A (ja) | ワイヤレス通信における省電力のためのシステムおよび方法 | |
JP2013257886A (ja) | 電力管理のためのアイドル期間報告 | |
CN108551668B (zh) | 信息传输方法、装置、设备及存储介质 | |
WO2011160500A1 (zh) | 一种动态能耗控制方法及***、相关设备 | |
WO2013063972A1 (zh) | 一种通信方法、通信装置及电子设备 | |
JP2015195613A (ja) | 休止タイマーの制御のための方法、装置、および通信システム | |
WO2010078674A1 (zh) | 一种基站节能控制的实现方法及*** | |
JP5150598B2 (ja) | ネットワーク管理装置 | |
CN101998599A (zh) | 一种睡眠模式下业务传输的方法及控制装置 | |
CN102255746B (zh) | 管理计算中心及管理计算中心资源高能效控制策略的方法 | |
JP2014064246A (ja) | トラフィック制御装置及びトラフィック制御プログラム | |
WO2022068553A1 (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: 11811759 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: 11811759 Country of ref document: EP Kind code of ref document: A1 |